Hi, If I understand your question, you are wanting to know if it is okay for a UAC to release all subsequent 2xx related dialogs and keep the first INVITE 2xx's dialog. The answer is yes. And excluding race conditions, multiple 2xx responses should be rare since the forking proxy must send cancel on the other branches after forwarding a final response; see RFC 3261 section 16.7 number 10.
RFC 3261 section 13.2.2.4: "If, after acknowledging any 2xx response to an INVITE, the UAC does not want to continue with that dialog, then the UAC MUST terminate the dialog by sending a BYE request as described in Section 15." > -----Original Message----- > From: [email protected] [mailto:sip- > [email protected]] On Behalf Of Natasha Goel > Sent: Wednesday, April 02, 2014 7:14 AM > To: [email protected] > Subject: [Sip-implementors] Query on forked responses > > Hi > > Is following a valid scenario? > > When an INVITE client transaction is in the Calling state, on receipt > of Success (200 OK) responses differing only on the tag in the To > header, sends an ACK request with a To header identical to the received > one for each received Success (200 OK) responses. > The call is connected for the 1st received 200 OK response followed by > BYE for other forked 200 OK responses. > > Also, please share any normative references in support of the above? -- This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient and have received this email in error, please notify BroadSoft, Inc. immediately by replying to this message, and destroy all copies of this message, along with any attachment, prior to reading, distributing or copying it. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
