Pranab, What would be the behavior if the route set is combination of strict and loose router? Considering the route set example as below:
Route set = <sip:proxy2.com;lr>,<sip:proxy1.com> Remote target = sip:[email protected] >From UAC, I believe the outgoing request would have Request-URI = sip:[email protected] Route Header = <sip:proxy2.com;lr>, <sip:proxy1.com> However, when the request reaches 'proxy2' and its about to forward it to 'proxy1' then whether 'proxy2' be changing the request URI considering 'proxy1' is strict? With regards, Vivek Gupta On Wed, Nov 7, 2012 at 3:22 PM, Pranab Bohra <[email protected]>wrote: > Hi, > > > > The generic rule for in-dialog requests sent by UA is - > > Loose Router<--------- Top of route-set type ? --------> > Strict router > | > | > | > | > | > | > V > V > ---------------------------------- > ----------------------------------------------------------- > | Request-URI = Remote Target URI| | Request-URI = > First element of route-set | > | && | | > && | > | route-set = As it is | | ( route-set = Rest of > the route-set + Remote Target URI)| > ---------------------------------- > ----------------------------------------------------------- > > > =============================================================== > > In 1st (loose router) case, > > > > route-set = <sip:proxy2.com;lr>,<sip:proxy1.com;lr> > > Remote target URI = sip:[email protected] > > So the outgoing request would have - > > > > Request- URI = sip:[email protected] > Route Header = <sip:proxy2.com;lr>,<sip:proxy1.com;lr> > > > > =============================================================== > > > > In the 2nd (strict router) case, > > > > route-set = <sip:proxy2.com>,<sip:proxy1.com;lr> > > Remote target URI = sip:[email protected] > > So the outgoing request would have - > > > > > > Request- URI = sip:proxy2.com > > Route Header = <sip:proxy1.com;lr>,<sip:[email protected]> > > > > =============================================================== > > > > > > Thanks, > > Pranab > > ________________________________________ > From: [email protected] [ > [email protected]] On Behalf Of Alok 2 > Tiwari [[email protected]] > Sent: Wednesday, November 07, 2012 12:33 PM > To: Vivek Batra; [email protected] > Subject: Re: [Sip-implementors] What will be set in Request-URI with > respect to loose and strict routing > > Hi Vivek, > In first case, request URI will be set as 'sip:[email protected]' and Route > header will have 'sip:proxy2.com' as loose router. > In second case, request URI will be set as 'sip:proxy2.com' and Route > header will have 'sip:[email protected]' as strict router. > > Regards, > Alok Tiwari > Aricent > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of Vivek Batra > Sent: Wednesday, November 07, 2012 11:55 AM > To: [email protected] > Subject: [Sip-implementors] What will be set in Request-URI with respect > to loose and strict routing > > Hi Folks, > > UA1 --> P1 --> P2 --> UA2 > > 1. UA2 gets INVITE message as follows; > > INVITE sip:[email protected] > Contact: sip:[email protected] > Record-Route: <sip:proxy2.com;lr> > Record-Route: <sip:proxy1.com;lr> > > Question is "When UA2 generates any message within dialog say BYE, > Request-URI will be set to 'sip:[email protected]' or 'sip:proxy2.com'? This > is a case where proxy2 follows loose routing. > > 2. UA2 gets the INVITE message as follows; > > INVITE sip:[email protected] > Contact: sip:[email protected] > Record-Route: <sip:proxy2.com> > Record-Route: <sip:proxy1.com;lr> > > Question is "When UA2 generates any message within dialog say BYE, > Request-URI will be set to 'sip:[email protected]' or 'sip:proxy2.com'? This > is a case where proxy2 follows strict routing. > > Will appriecate your comments. > > Best Regards, > Vivek Batra > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > > > > > =============================================================================== > Please refer to http://www.aricent.com/legal/email_disclaimer.html > for important disclosures regarding this electronic communication. > > =============================================================================== > > _______________________________________________ > 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
