Patches item #3184900, was opened at 2011-02-17 15:39
Message generated for change (Tracker Item Submitted) made by adubovikov
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=756078&aid=3184900&group_id=143636

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Alexandr Dubovikov (adubovikov)
Assigned to: Nobody/Anonymous (nobody)
Summary: support for 503 and SRV. RFC 3263

Initial Comment:
RFC 3263 
"For SIP requests, failure occurs if the transaction layer reports a 503 error 
response or a transport failure of some sort (generally,
   due to fatal ICMP errors in UDP or connection failures in TCP).    Failure 
also occurs if the transaction layer times out without ever
   having received any response, provisional or final (i.e., timer B or   timer 
F in RFC 3261 [1] fires).  If a failure occurs, the client
   SHOULD create a new request, which is identical to the previous ..."

unfortanly, sofia try to retransmit method (for example REGISTER) to the same 
destination. The patch try to fix this problem.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=756078&aid=3184900&group_id=143636

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel

Reply via email to