SIP is based on request/response transactions. Each transaction consists of a SIP request and at least one response. SIP requests and responses may be generated by any SIP user agent; User Agent Clients (UACs), which initiate requests, and User Agent Servers (UASes), which respond to them. Created: July 2018 Permalink: https://wildix.atlassian.net/wiki/x/oxvOAQ |
Extended search being performed may take a significant time so a forking proxy must send a 100 Trying response.
Destination user agent received INVITE, and is alerting user of call.
Servers can optionally send this response to indicate a call is being forwarded.
Indicates that the destination was temporarily unavailable, so the server has queued the call until the destination is available. A server may send multiple 182 responses to update progress of the queue.
This response may be used to send extra information for a call which is still being set up.
Can be used by User Agent Server to indicate to upstream SIP entities (including UAC) that an early dialog has been terminated.
Indicates the request was successful.
Indicates that the request has been accepted for processing, but the processing has not been completed (deprecated).
Indicates the request was successful, but the corresponding response will not be received.
The address resolved to one of several options for the user or client to choose between, which are listed in the message body or the message's Contact fields.
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.
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.
The Contact field details a proxy that must be used to access the requested destination.
The call failed, but alternatives are detailed in the message body.
The request could not be understood due to malformed syntax.
The request requires user authentication. This response is issued by UASs and registrars.
Reserved for future use.
The server understood the request, but is refusing to fulfill it. Sometimes (but not always) this means the call has been rejected by the receiver.
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.
The method specified in the Request-Line is understood, but not allowed for the address identified by the Request-URI.
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.
The request requires user authentication. This response is issued by proxys.
Couldn't find the user in time. The server could not produce a response within a suitable amount of time, for example, if it could not determine the location of the user in time. The client MAY repeat the request without modifications at any later time.
User already registered.
The user existed once, but is not available here any more.
The server will not accept the request without a valid Content-Length (deprecated).
The given precondition has not been met.
Request body too large.
The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret.
Request body in a format not supported.
Request-URI is unknown to the server.
There was a resource-priority option tag, but no Resource-Priority header.
Bad SIP Protocol Extension used, not understood by the server.
The server needs a specific extension not listed in the Supported header.
The received request contains a Session-Expires header field with a duration below the minimum timer.
Expiration time of the resource is too short.
The request's location content was malformed or otherwise unsatisfactory.
The server policy requires an Identity header, and one has not been provided.
The server did not receive a valid Referred-By token on the request.
A specific flow to a user agent has failed, although other flows may succeed. This response is intended for use between proxy devices, and should not be seen by an endpoint (and if it is seen by one, should be treated as a 400 Bad Request response).
The request has been rejected because it was anonymous.
The request has an Identity-Info header, and the URI scheme in that header cannot be dereferenced.
The server was unable to validate a certificate for the domain that signed the request.
The server obtained a valid certificate that the request claimed was used to sign the request, but was unable to verify that signature.
The first outbound proxy the user is attempting to register through does not support the "outbound" feature of RFC 5626, although the registrar does.
If a SIP proxy determines a response context has 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. A client receiving a 440 response can infer that its request did not reach all possible destinations.
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 the UA is willing to receive INFO requests.
The source of the request did not have the permission of the recipient to make such a request.
Callee currently unavailable.
Server received a request that does not match any dialog or transaction.
Server has detected a loop.
Max-Forwards header has reached the value '0'.
Request-URI incomplete.
Request-URI is ambiguous.
Callee is busy.
Request has terminated by bye or cancel.
Some aspect of the session description or the Request-URI is not acceptable, or Codec issue.
The server did not understand an event package specified in an Event header field.
Server has some pending request from the same dialog.
Request contains an encrypted MIME body, which recipient can not decrypt.
The server has received a request that requires a negotiated security mechanism, and the response contains a list of suitable security mechanisms for the requester to choose between, or a digest authentication challenge.
The server could not fulfill the request due to some unexpected condition.
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.)
The server is acting as a gateway or proxy, and received an invalid response from a downstream server while attempting to fulfill the request.
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 reattempt its request.
The server attempted to access another server in attempting to process the request, and did not receive a prompt response.
The SIP protocol version in the request is not supported by the server.
The request message length is longer than the server can process.
The server is unable or unwilling to meet some constraints specified in the offer.
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.
The destination does not wish to participate in the call, or cannot do so, and additionally the destination knows there are no alternative destinations (such as a voicemail server) willing to accept the call.
The server has authoritative information that the requested user does not exist anywhere.
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.
The called party did not want this call from the calling party. Future attempts from the calling party are likely to be similarly rejected.