Hello , I have read this response code with respect to emergency services to provide alternate service URN in xml body.
Regards, Sumit Jindal -----Original Message----- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Iñaki Baz Castillo Sent: Friday, March 27, 2009 2:53 PM To: Anuradha Gupta Cc: sip-implementors@lists.cs.columbia.edu Subject: Re: [Sip-implementors] SIP 380 response 2009/3/27 Anuradha Gupta <anuradha.gu...@aricent.com>: > Hi > > What should be the handling for SIP 380 response? Should it be handled as other 3xx response or it should be treated as a call failure. 380 is not a response code, but a warning code defined in: http://tools.ietf.org/html/draft-ietf-sip-sips ------------- Upon receiving a 416 response or a 480 (Temporarily Unavailable) response with a Warning header with warn-code 380 "SIPS Not Allowed", a UAC MUST NOT re-attempt the request by automatically replacing the SIPS scheme with a SIP scheme [...] --------------- -------------- 9. IANA Considerations This specification registers two new warning codes, namely 380 "No SIPS Contacts Registered" and 381 "SIPS Required". The warning codes are defined by the following information, to be included in the Warn- codes sub-registry under http://www.iana.org/assignments/sip-parameters. 380 SIPS Not Allowed: The UAS or proxy cannot process the request because the SIPS scheme is not allowed (e.g., because there are currently no registered SIPS Contacts). 381 SIPS Required: The UAS or proxy cannot process the request because the SIPS scheme is required. ------------- -- Iñaki Baz Castillo <i...@aliax.net> _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
