Hi, The lr tag is inserted by a proxy (sipXecs for example) to tell other proxies/clients on the route that he is a loose-routing proxy. (routing according to RFC3261 and not deprecated RFC2543).
A strict-router (RFC2543) requires that the request URI is modified by its URI (in the route field) before a packet is sent to him, he will also always modify the request URI with next route URI even if the next router is loose-router. (request URI is always modified) A loose-router (RFC3261) doesn't require the request URI to be modified before a packet is sent to him, he will only modify the request URI when the next proxy is a strict-router, he will also restore the original request URI if it has been modified by a previous strict-router. (request URI is only modified when a strict-router is/was on the route for backward compatibility) In conclusion strict-routers and loose-routers can interact without any problem. And a loose-router (like sipXecs) has no reason to not indicate that he is one by adding a new parameter. If any ITSP requires this, you should definitely change because he is not compatible with obsolete RFC2543 nor RFC3261. Regards. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
