The server does not support the push notification serviced specified in the pn-provider SIP URI parameter. The request message length is longer than the server can process. The SIP protocol version in the request is not supported by the server. The server tried to access another server while trying to process a request, no timely response. The server is in maintenance or is temporarily overloaded and cannot process the request. The server, received an invalid response from a downstream server while trying to fulfill a request. The SIP request method is not implemented here. The server could not fulfill the request due to some unexpected condition. The server has received a request that requires a negotiated security mechanism. UndecipherableRequest contains an encrypted MIME body, which recipient can not decrypt. Server has some pending request from the same dialogue. The server did not understand an event package specified in an Event header field. Some aspects of the session description of the Request-URI are not acceptable. Max-Forwards header has reached the value ‘0’. Server received a request that does not match any dialogue or transaction. The source of the request did not have the permission of the recipient to make such a request. If a SIP UA receives an INFO request associated with an Info Package that the UA has not indicated willingness to receive, the UA MUST send a 469 response, which contains a Recv-Info header field with Info Packages for which UA is willing to receive INFO requests. A client receiving a 440 response can infer that its request did not reach all possible destinations. If a SIP proxy determined a response context had insufficient Incoming Max-Breadth to carry out a desired parallel fork, and the proxy is unwilling/unable to compensate by forking serially or sending a redirect, that proxy MUST return a 440 response. The first outbound proxy doesn’t support the “outbound” feature. Server obtained a valid certificate used to sign a request, was unable to verify the signature. The server was unable to validate a certificate for the domain that signed the request. The request has an Identity-Info header and the URI scheme contained cannot be de-referenced. The request has been rejected because it was anonymous. The server did not receive a valid Referred-By token on the request.Ī specific flow to a user agent has failed, although other flows may succeed. The server policy requires an Identity header, and one has not been provided. The request’s location content was malformed or otherwise unsatisfactory.
The expiration time of the resource is too short. The request contains a Session-Expires header field with a duration below the minimum. The server needs a specific extension not listed in the Supported header. There was a resource-priority option tag, but no Resource-Priority header.īad SIP Protocol Extension used, not understood by the server. Request body is in a non-supported format. Server refuses to service the request, the Req-URI is longer than the server can interpret. The server will not accept the request without a valid content length (deprecated). The user existed once but is not available here anymore. The request requires user authentication. The resource is only capable of generating responses with unacceptable content. The method specified in the Request-Line is understood, but not allowed. The server has definitive information that the user does not exist at the (User not found). The server understood the request but is refusing to fulfill it. This response is issued by UASs and registrars. The request could not be understood due to malformed syntax.
The call failed, but alternatives are detailed in the message body. The Contact field details a proxy that must be used to access the requested destination. The client should try at the address in the Contact field. The original Request URI is no longer valid, the new address is given in the Contact header. The address resolved to one of several options for the user or client to choose between. Indicates that the request was successful but no response will be received. Indicates that the request has been accepted for processing, mainly used for referrals.
Send by the User Agent Server to indicate that an early dialogue has been terminated. This response may be used to send extra information for a call which is still being set up.
Optional, send by Server to indicate a call is being forwarded.ĭestination was temporarily unavailable, the server has queued the call until the destination is available. The Destination User Agent has received the INVITE message and is alerting the user of call. Extended search is being performed so a forking proxy must send a 100 Trying response.