Hi As per RFC 3261 ------------------------------------------- 21.3.5 380 Alternative Service
The call was not successful, but alternative services are possible. The alternative services are described in the message body of the response. Formats for such bodies are not defined here, and may be the subject of future standardization. --------------------------------------------- 380 is a valid SIP response. As per the above explanation, call was not successful but some alternate service is possible that is mentioned in the message body of the response. My query is that on receiving 380 response, what should be the possible handling 1. Terminating the call and initiating new request for alternate service after interpreting the message body. 2. Redirecting the Call request to redirect server (if it is provided in the response) Can someone provide a call flow example of 380 response. Regards Anuradha Gupta Aricent -----Original Message----- From: Iñaki Baz Castillo [mailto:i...@aliax.net] 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> "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
