[OpenSER-Devel] [ openser-Bugs-1901434 ] 6xx reply handling

SourceForge.net noreply at sourceforge.net
Mon Feb 25 16:11:32 CET 2008


Bugs item #1901434, was opened at 2008-02-25 17:11
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1901434&group_id=139143

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: modules
Group: ver 1.3.x
Status: Open
Resolution: None
Priority: 7
Private: No
Submitted By: Bogdan-Andrei Iancu (bogdan_iancu)
Assigned to: Bogdan-Andrei Iancu (bogdan_iancu)
Summary: 6xx reply handling

Initial Comment:
I found two bugs in 6xx reply handing in TM:



1) according to RFC3261, no branch should be added after a 6xx reply (no more serial forking):

Chapter 6 Definitions:

   Sequential Search: In a sequential search, a proxy server attempts each contact address in sequence, proceeding to the next one only after the previous has generated a final response.  A 2xx or 6xx class final response always terminates a sequential search. 

16.7 Response Processing (Point 5)

         If a 6xx response is received, it is not immediately forwarded,but the stateful proxy SHOULD cancel all client pending transactions as described in Section 10, and it MUST NOT create any new branches in this context.


2) ignoring bug 1), if after a 6xx reply, a new branch is added in failure route or callback, the pending branches (from the same set with 6xx reply) are not cancelled any more.




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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1901434&group_id=139143



More information about the Devel mailing list