On Mon, May 19, 2008 at 3:27 PM, Jitendra Singh Bhadoriya <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > In the call-transfer scenario in which A calls B and B sends REFER to A > to transfer the call to C, but the REFER > > > > Request contains some invalid URI in the Refer-To header, then in this > case how should A respond to the REFER > > > > Request. In this case the A will not be able to send the INVITE to the > target SIP client because the Refer-To URI > > > > Is wrong, so should it send a NOTIFY with (100 trying in the body) and > then a second NOTIFY with some error > > > > Response in this second NOTIFY to the B party. OR should it send a > single NOTIFY with some error response. > If A is unable to send the INVITE to C, he will not get 100 Trying. If he has not got 100 Trying why should he send NOTIFY with 100 Trying body? You can send one NOTIFY with "Subscription-State" terminated with body as "SIP/2.0 400 Bad Request".
You may reject REFER itself with 400 response which is think is most appropriate. Also, I do not see any protocol violation if A sends two NOTIFY request to B with 100 trying status in the first NOTIFY but this messaging is unnecessary. > > Also please tell me what error response should A send to B, in the body > of NOTIFY?? > > > > Thanks & > > Regards, > > Jitendra. > > > > _______________________________________________ > 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
