Hi Tarun, No, 180 without to tag won't be considered a forked response.
Extract for 3261: The forking of SIP requests means that multiple dialogs can be established from a single request. This also explains the need for the two-sided dialog identifier; without a contribution from the recipients, the originator could not disambiguate the multiple dialogs established from a single request. and in order to have a dialog established, you need To tag. Regards Sameer -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Tarun2 Gupta Sent: Thursday, August 26, 2010 5:25 PM To: [email protected] Cc: Preksha . Subject: [Sip-implementors] Query on Forking Hi All Is 180 response received without TO tag a forked response? If the UAC sends an INVITE request and receives the first 180 response without TO tag and the second 180 response with TO tag Shall the second 180 response be indentified as forked response or not? Scenario: * UAC sends an INVITE request. * UAC receives 100 Trying and 180 response (without To Tag and with SDP, require: 100 rel, RSEQ) for Dialog 1. * UAC sends PRACK and receives 200 OK response for PRACK without TO tag. * UAC again receives 180 response with same SDP as in the last 180 response but contains a To-Tag for Dialog 2. * UAC sends PRACK and receives 200 OK response for PRACK with TO tag. As the initial 18x response was received with out a TO tag ,shall the next 18x response with TO tag be identified as a forked response ? Regards, Tarun Gupta Aricent ________________________________ "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ 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
