Bob Penfield wrote:
You can do whatever you want, as long as you can figure out what is going on. One way is by having implementation specific knowledge of what the servers you are using do. I suppose you might also be able to figure some things out via the new History mechanism if all the servers you use support it.Paul,I really don't have a problem with a UAC behaving this way for an outbound proxy. I'm more concerned with more complicated UAs like a gateway that selects the proxy/redirect server based on things like the calling & called numbers.
But in general, if you sent your request to an intermediate server that might be a proxy, then it is difficult for you to determine if a 3xx response you get from it came directly from it (so that the new request should bypass the intermediate server), or from someplace downstream (and so should be reissued back to the same intermediate.)
If you are going to try to make this work, then the actions this proxy must take will depend on whether it is going to handle 3xx responses itself, or pass them back to its client. The answers may differ in these two cases, and is one reason why this generally seems like a bad idea.I'm also wondering whether a proxy would have to behave the same way if it inserted a Route header in order to direct the request to a redirect server. Or in the case of a proxy would the "original request" be the request is received (w/o the Route header to the redirect server) instead of the request it sent to the redirect server?
Paul
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
