> From: Iñaki Baz Castillo [[email protected]] > > Hi, RFC 3261 states that a proxy should just remove the top most Route > if it contains a value added by it (or if it's a pre-loaded Route in > an initial request pointing to the proxy itself). > > But when a proxy speaks different transport on both "legs" a common > technique is to add two Record-Route (on for each transport) and then > remove both at the same time when an in-dialog request arrives. > > So I wonder: If an initial request contains two pre-loaded Route > headers with values pointing to the proxy, could the proxy remove both > of them? i.e: > > INVITE sip:[email protected] SIP/2.0 > Route: <sip:A.org>, <sip:A:A.org:5060>
The sensible answer is the one from Dmitry Akindinov: > The proxy should remove (after the necessary processing) all topmost > routes that are recognized as its own (on the 16.4 step of rfc3261), > otherwise on the next step (16.5 of rfc3261) it would have to forward > the request to itself. What else would be a good strategy? (Of course, you could have the proxy just remove one Route and then obey the next Route, sending the request back to itself to remove the next Route, but that is inefficient.) BTW, <sip:A:A.org:5060> is not a valid URI. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
