reSIProcate

Mailing Lists

Source Code

Google Search:



< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

Re: [reSIProcate-users] a problem about matching a transaction

The transaction id / branch id is supposed to be unique.  It is wrong for an endpoint to re-use the same TID in an INVITE that it just recently used in a BYE request.  The stack needs to maintain tracking of the transaction even after the 200 is sent, so that it can properly absorb retransmissions.

"The branch parameter in the topmost Via header field of the request
   is examined.  If it is present and begins with the magic cookie
   "z9hG4bK", the request was generated by a client transaction
   compliant to this specification.  Therefore, the branch parameter
   will be unique across all transactions sent by that client."

Scott
On Thu, Dec 31, 2009 at 12:22 AM, 吴振宇 <ssosun@xxxxxxxxx> wrote:
hi, i have a new problem about matching a transaction.
the  resip stack recieve a bye with a via:
Via: SIP/2.0/UDP
192.168.1.31:10022;branch=z9hG4bK-d8754z-87873e422916574a-1---d8754z-;rport
,then the app send a 200,the transactionstate change to the completed state.
and then receive a new INVITE with a via:
Via: SIP/2.0/UDP
192.168.1.31:10021;branch=z9hG4bK-d8754z-87873e422916574a-1---d8754z-;rport

then the resip stack match the INVITE request to the transaction which
is created by the BYE.

in the rfc3261 17.2.3,i got the information about the  matching a transaction.

maybe resip stack has something wrong with this condition.
_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/