Since the URI scheme is understood by the Server ( Sip: etc) this may not be the right response.
Any other response in the Notifyb which otherwise the Proxy would have sent for such errors 500 Server Internal Error also is a Ok Response :-) > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Arunachalam Venkatraman (arunvenk) > Sent: Monday, May 19, 2008 9:26 AM > To: Paul Kyzivat (pkyzivat); Jitendra Singh Bhadoriya > Cc: [email protected] > Subject: Re: [Sip-implementors] Call Transfer Scenario > :Refer-To Containingincorrect URI > > 416 Unsupported Uri Scheme fits the bill. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Paul Kyzivat (pkyzivat) > Sent: Monday, May 19, 2008 8:41 AM > To: Jitendra Singh Bhadoriya > Cc: [email protected] > Subject: Re: [Sip-implementors] Call Transfer Scenario : > Refer-To Containingincorrect URI > > Assuming this isn't detected until after the response has > been sent for the REFER, then I would send a single NOTIFY > with some suitable error indicating the problem. Of course in > this case you won't actually have received a sip error, so > you will have to simulate one. I am inclined to > > treat it as if you had forwarded the request to a proxy and > the proxy had encountered the error and returned a response to you. > > Its not entirely clear which sip error is most appropriate to > this case. > > I think I would go with 404, but there may be other > reasonable codes to use. > > I see no reason to send a NOTIFY with 100 Trying. > > Paul > > Jitendra Singh Bhadoriya wrote: > > In my scenario the Refer-To URI was in the format > 'sip:[EMAIL PROTECTED] > > > > Where the DNS was not able to resolve the domain-name > 'domain.com' of > > the > > > > Host and so the client was not able to send the request out. > > > > Regards, > > Jitendra. > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On > Behalf Of > > Jitendra Singh Bhadoriya > > Sent: Monday, May 19, 2008 3:27 PM > > To: [email protected] > > Subject: [Sip-implementors] Call Transfer Scenario : Refer-To > > Containingincorrect URI > > > > > > > > > > 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. > > > > 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 > > > _______________________________________________ > 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
