Paul, Sorry. I mistyped UAC. I meant to say UAC. Not UAS. Corrected text:
Thanks for the response. Is there any way to know how many forks were made by a proxy. My application is VoIP. I need to provide some kind of error tone when the UAC determines that the call cannot be landed on any of the forks. Ideally, I would like to know the total number of forks made by the proxy and provide error tone to the voice user when all the forks responsed with error final responsed. Thanks again for your time. - ramesh -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Ramesh Babu Kuppili Sent: Wednesday, February 27, 2013 10:51 AM To: Paul Kyzivat; [email protected] Subject: Re: [Sip-implementors] change in tag field in To header Paul, Thanks for the response. Is there any way to know how many forks were made by a proxy. My application is VoIP. I need to provide some kind of error tone when the UAS determines that the call cannot be landed on any of the forks. Ideally, I would like to know the total number of forks made by the proxy and provide error tone to the voice user when all the forks responsed with error final responsed. Thanks again for your time. - ramesh -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Paul Kyzivat Sent: Wednesday, February 27, 2013 3:50 AM To: [email protected] Subject: Re: [Sip-implementors] change in tag field in To header On 2/27/13 12:38 AM, Ramesh Babu Kuppili wrote: > Hello, > > I am having a problem with the To tag in the incoming "603 Declined" from UAS. > > 1. Outgoing INVITE > - no tag in the To header. > 2. Incoming "183 Session Progress" > - To tag - tag=h7g4Esbg_p65547t1361882364m374065c90075s1_4069438959-13. > Incoming "603 Declined" > - To tag - > tag=h7g4Esbg_p65547t1361882364m374065c90075s1_4069388685-1940037509 > Can the To tag change from "183 Session Progress" to "603 Declined". How do > the UAS handle this? Yes. This is consistent with the request having been forked by a proxy. The 183 came from one fork. Then the 603 came from a different fork. Once this has happened, you generally will get no further response from the first fork. Good Luck, Paul _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
