Response Codes

Description	Total number of a specific INVITE response codes that occurred during Survivability. Each of the response codes are as follows: 1xx --Informational: 100 Trying: This response is used to indicate the next node receives the request and stop the retransmission. This response is sent if there is delay in sending the final response more the 200ms. 180 Ringing: The response is generated if UA receives the INVITE and started the ringing. It may used to initiate local ring back. 181 Call is being Forwarded: This response is indication of call is being forwarded to different destination. 182 Call Queued: The called server is overloaded or temporary unavailable. the server sends this status code to queue the call. When server ready to take the call, it initiates appropriate final response. 183 Call Progress: This response may be used to send extra information for a call which is still being set up. 2xx—Successful Responses 200 OK: Indicates the request was successful. 202 Accepted: Indicates that the request has been accepted for processing, but the processing has not been completed. 3xx—Redirection Response 301 Moved Permanently: The original Request-URI is no longer valid, the new address is given in the Contact header field, and the client should update any records of the original Request-URI with the new value. 302 Moved Temporarily: The client should try at the address in the Contact field. If an Expires field is present, the client may cache the result for that period of time. 305 Use Proxy: The Contact field details a proxy that must be used to access the requested destination. 380 Alternative Service: The call failed, but alternatives are detailed in the message body. 4xx—Client Failure Responses 400 Bad Request: The request could not be understood due to malformed syntax. 401 Unauthorized: The request requires user authentication. This response is issued by UASs and registrars. 403 Forbidden: The server understood the request, but is refusing to fulfill it 404 Not Found: The server has definitive information that the user does not exist at the domain specified in the Request-URI. This status is also returned if the domain in the Request-URI does not match any of the domains handled by the recipient of the request. 405 Method Not Allowed: The method specified in the Request-Line is understood, but not allowed for the address identified by the Request-URI. 406 Not Acceptable: The resource identified by the request is only capable of generating response entities that have content characteristics but not acceptable according to the Accept header field sent in the request. 407 Proxy Authentication Required: The request requires user authentication. This response is issued by proxys
	4xx—Client Failure Responses (continued) 408 Request Timed Out: Couldn't find the user in time. 415 Unsupported Media Type: Request body in a format not supported. 420 Bad Extension: Bad SIP Protocol Extension used, not understood by the server. 421 Extension Required: The server needs a specific extension not listed in the Supported header. 422 Session Interval Too Small: The received request contains a Session-Expires header field with a duration below the minimum timer. 423 Interval Too Brief: Expiration time of the resource is too short. 480 Temporarily Unavailable: Callee currently unavailable. 481 Call/Transaction Does Not Exist: Server received a request that does not match any dialog or transaction. 482 Loop Detected: Server has detected a loop. 483 Too Many Hops: Max-Forwards header has reached the value '0'. 484 Address Incomplete: Request-URI incomplete. 485 Ambiguous: Request-URI is ambiguous. 486 Busy Here: Callee is busy. 487 Request Terminated: Request has terminated by bye or cancel. 488 Not Acceptable Here: Some aspects of the session description of the Request-URI is not acceptable. 489 Bad Event: The server did not understand an event package specified in an Event header field. 491 Request Pending: Server has some pending request from the same dialog.
	5xx—Server Failure Responses 500 Server Internal Error: The server could not fulfill the request due to some unexpected condition. 501 Not Implemented: The server does not have the ability to fulfill the request, such as because it does not recognize the request method. (Compare with 405 Method Not Allowed, where the server recognizes the method but does not allow or support it.) 502 Bad Gateway: The server is acting as a gateway or proxy, and received an invalid response from a downstream server while attempting to fulfill the request. 503 Service Unavailable: The server is undergoing maintenance or is temporarily overloaded and so cannot process the request. A "Retry-After" header field may specify when the client may re attempt its request. 504 Server Time-out: The server attempted to access another server in attempting to process the request, and did not receive a prompt response. 513 Message Too Large: The request message length is longer than the server can process. 580 Precondition Failure: The server is unable or unwilling to meet some constraints specified in the offer. 6xx—Global Failure Responses 600 Busy Everywhere: All possible destinations are busy. Unlike the 486 response, this response indicates the destination knows there are no alternative destinations (such as a voicemail server) able to accept the call. 603 Decline: The destination does not wish to participate in the call, or cannot do so, and additionally the client knows there are no alternative destinations (such as a voicemail server) willing to accept the call. 604 Does Not Exist Anywhere: The server has authoritative information that the requested user does not exist anywhere. 606 Not Acceptable: The user's agent was contacted successfully but some aspects of the session description such as the requested media, bandwidth, or addressing style were not acceptable.
Type	counter
Timer Value (seconds)	N/A
Range	0 to 4294967295
ACLI Show Command	show survivability invite
ACLI Parameter Mapping	For ACLI parameter mappings, see the command “show survivability invite” at SIP Request Method Examples  .