> -----Original Message----- > From: Dale Worley [mailto:dwor...@avaya.com] > Sent: Monday, 22 February 2010 4:42 PM > On Thu, 2010-02-18 at 02:50 +0000, Aaron Clauson wrote: > > You should be able to do this in a standard way. > > First, let us assume that an address of the client (which is acting as > UAS in this situation) is <sip:UAS>. > > The incoming request is "METHOD sip:UAS". Once the client obtains the > first redirect URI, <sip:DEST1>, it responds "SIP/2.0 302 Moved > Temp/Contact: sip:DEST1/Contact: <sip:UAS;phase=2>". > > This causes the requestor to fork to <sip:DEST1>, but the requestor > also > forks to <sip:UAS;phase=2>. The latter request goes back to the > client, > bit it is tagged so the client knows to proceed with the second phase > of > processing for the request. >
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. In the meantime I went ahead and used a custom info response of "184 Multiple Redirect" which does the job perfectly. Aaron _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
