2007/10/22, Fabio Margarido <[EMAIL PROTECTED]>: > However, my test case shows that when the 200 OK contains Record-Route > headers, the packet destination and the Request-URI in the ACK sent by > Sofia is the URI in the last Record-Route, and not the URI from the > Contact header.
If the last Record-Route contains a URI from a strict router, that is the expected behavior. After the route set is collected from Record-Route header as described in 12.2, the new request will have request-URI from Contact and Route headers reversed from Record-Route. When the request is sent, the top-most route URI is checked. If there is no lr URI parameter in the header (please note the lr URI parameter must be inside <>), the request-URI from Contact header is put last into Route header and the URI from first Route header is used instead. This is described in RFC3261 section 12.1.1 in the middle of page 74. I recall that the stack tries to fix also broken record-route headers, e.g, if there is Record-Route: sip:xyzzy.com;lr the lr is considered as a URL parameter. -- Pekka.Pessi mail at nokia.com ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
