[reSIProcate-users] a problem about matching a transaction

[吴振宇 <ssosun@xxxxxxxxx>]

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.