"to-Tag" is TU specific and must be added by the concerned TU. For Example, if server is behaving as Proxy, the ProxyCore would add "to-Tag" and pass the response to the transaction.
Since, adding "to-Tag" is common across Proxy, Registrar or B2BUA, it can also be added as part of common processing, which is again TU. Cheers! Somesh -----Original Message----- From: [EMAIL PROTECTED] on behalf of Iñaki Baz Castillo Sent: Thu 8/14/2008 6:27 AM To: [email protected] Subject: [Sip-implementors] Who must add the "To tag" to a response Hi, imagine a non specific SIP stack that could have a proxy core, UAS core, B2BUA, registrar, being a stateless proxy... I'm getting a bit crazy to determine which layer must add the "To tag" to the response if it has not, and also how to use the same "To tag" in more responses for the same transaction. Also, it's required to add a "To tag" in a response sent stateless (a 401 for auth for example). Any suggestion please? Thanks. -- Iñaki Baz Castillo _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors EMAIL DISCLAIMER : This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorised distribution or copying is strictly prohibited. If you receive this transmission in error, please notify the sender by reply email and then destroy the message. Opinions, conclusions and other information in this message that do not relate to official business of Mascon shall be understood to be neither given nor endorsed by Mascon. Any information contained in this email, when addressed to Mascon clients is subject to the terms and conditions in governing client contract. Whilst Mascon takes steps to prevent the transmission of viruses via e-mail, we can not guarantee that any email or attachment is free from computer viruses and you are strongly advised to undertake your own anti-virus precautions. Mascon grants no warranties regarding performance, use or quality of any e-mail or attachment and undertakes no liability for loss or damage, howsoever caused. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
