This is applicable in cases where the intermediate proxy(ies) intend to be in the signalling path.
Your device can route requests if it has a preconfigured outbound proxy or if its using rfc3263 procedures as well. IMO, request routing using Record-Route information would take higher precedence than the other 2 methods. ________________________________________ From: [email protected] [[email protected]] On Behalf Of Pranab Bohra [[email protected]] Sent: Wednesday, July 25, 2012 8:33 PM To: fuliang yuan; [email protected] Subject: Re: [Sip-implementors] could Record-Route be added in Response? Hi, Its legit operation, in fact the route-set on the UAC would be updated from the values of the Record-Route headers in the responses from UAS. Unless there's a Record-Route in the responses, your device would never know what route to use for future in-dialog requests. Thanks, Pranab ________________________________________ From: [email protected] [[email protected]] On Behalf Of fuliang yuan [[email protected]] Sent: Wednesday, July 25, 2012 8:20 PM To: [email protected] Subject: [Sip-implementors] could Record-Route be added in Response? Hi All, Record route is normally added in Request. I have encountered a weird case that INVITE from my sip device did not have Record-Route, but the response of 180 and 200 have Record-Route. I could not find if it is legit to add Record-Route in response from RFC 3261. INVITE without Record-Route ------------------> <----------------- 183 with Record-Route <----------------- 200 with Record-Route Please let me know if it is legit to add Record-Route in response? Thanks in advance, Frank _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors SASKEN BUSINESS DISCLAIMER: This message may contain confidential, proprietary or legally privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Communication Technologies Limited ("Sasken") unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. Read Disclaimer at http://www.sasken.com/extras/mail_disclaimer.html _______________________________________________ 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
