Bob - I have one question about your answer. See inline. Paul
Bob Penfield wrote:
If the client is treating the server as an outbound proxy, by using a preloaded Route header, why would it decide not to use the same preloaded route header when sending to the redirected address?If I understand what you are trying to do, your redirect server is essentially the "outbound proxy" for your client UA. What you want to do is insert a Route header in the request with the address/host of your redirect server (see section 8.1.2 of RFC 3261). Note that this Route header should have the "lr" parameter to conform to the loose routing described in RFC 3261. The Request-URI will be the intended destination (likely matching the To header). The stack should look for the top Route header to determine where to send the request. If there is no Route header, then it sends it to the address/host in the Request-URI. The redirect server should recognize that the Route header is itself and strip it (in accordance with section 16.4). It would then use the Request-URI the figure out where to redirect the request. When the client gets the redirect response, it would replace the Request-URI with the value from the Contact header. The new request would not include the Route header pointing at the redirect server that the original request has so that the stack would send it to the address/host in the Request-URI.
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
