On Mon, 2010-02-22 at 21:19 +0000, Aaron Clauson wrote: > The problem I have is that the client does not actually know all the > redirects at the point the first one is sent. The client has a human user > pressing buttons to initiate the redirects and there could be gaps of > 1,2,5,10 etc. seconds between subsequent forwards.
Uh, yes? The client will return the first 302 when it knows what the first redirection URI is. It will then immediately receive the INVITE with the "phase=2" parameter. It will then *wait* to answer that INVITE until it knows what the second redirection URI is. Each time the client provides a 302, causing the upstream proxy to send a fork to a destination, the client receives another INVITE, which it will eventually respond to to provide the next response... Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
