response inline. On Wed, 2002-05-29 at 04:51, Attila Sipos wrote: > > > I have a question regarding section "12.2.1.1 Generating the Request" > in RFC2543 bis-09. > > > If the route set is not empty, and its first URI does not contain the > > lr parameter, the UAC MUST place the first URI from the route set > > into the Request-URI, stripping any parameters that are not allowed > > in a Request-URI. The UAC MUST add a Route header field containing > > the remainder of the route set values in order, including all > > parameters. The UAC MUST then place the remote target URI into the > > Route header field as the last value. > > > > For example, if the remote target is sip:user@remoteua and the route > > set contains > > > > <sip:proxy1>,<sip:proxy2>,<sip:proxy3;lr>,<sip:proxy4> > > > > > > The request will be formed with the following Request-URI and Route > > header field: > > > > METHOD sip:proxy1 > > Route: <sip:proxy2>,<sip:proxy3;lr>,<sip:proxy4>,<sip:user@remoteua> > > > > The last sentence in the first paragraph says: > "The UAC MUST then place the remote target URI into the > Route header field as the last value." > > My question: > Is the remote traget URI added to the "route set"?
No. Don't confuse the route set with the set of URIs that appear in a Route header field. The route set and the remote target URI are used together to construct the Route header field values. The remote target URI remains a distinct piece of dialog state so that it can be modified as the dialog progresses (as opposed to the route set which once established cannot be changed). RjS > > > As usual, all help is much appreciated. > > > Regards, > > Attila > > <http://www.vegastream.com> > VegaStream : A World of difference for your Integrated Communications > > _______________________________________________ > Sip-implementors mailing list > [EMAIL PROTECTED] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
