It is an abnormal situation since device indicated a unique branch transaction ID when it wasn't actually unique. Thus the UAS can basically act however it wants.
Processing it as a new transaction for the new call is likely best; however doing so requires a little more intelligence to handle the accidental or malicious duplicate transaction ID. Aspects are discussed within RFC 3261 section 17.2.3. > -----Original Message----- > From: [email protected] [mailto:sip- > [email protected]] On Behalf Of soma bhargava > Sent: Monday, May 11, 2009 9:58 AM > To: [email protected] > Subject: [Sip-implementors] Non-INVITE transaction > > Hi All, > > Please consider the following scenario > > 1. A call has been established between two user agents. > 2. A mid dialog non-INVITE transaction has been processed. > 3. The call is been terminated. > 4. A new call is established. > 5. Now a new non-INVITE request has been sent within 32 secs with branch > id same as previous calls non invite transaction, but other tags are > different. > > Now what should be the server's reaction: > > 1. Should it send response of the previous calls transaction. > 2. Should the server terminate all the transactions as soon as the call > is disconnected and treat this as a new transaction. > 3. Should it send any 4XX response. > > Regards, > Soma > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
