> -----Original Message----- > From: Dale Worley [mailto:dwor...@avaya.com] > Sent: Tuesday, 23 February 2010 6:32 PM > > 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... >
Ah ok, I understand the mechanism you're suggesting. Since that would take extra work on the server and the client I'll be a heretic and stick to my 184 info response approach for the time being. It's not much of a contravention of the standard. A UAS can send back as many info responses as it likes and the standard doesn't forbid a UAC from doing some arbitrary processing when it receives an info response, in this case forking a new call. Aaron _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
