SIP ошибки и их значение
SIP/2.0 400 Bad Request — ошибка в сигнализации, скорее всего что-то с настройками оборудования
SIP/2.0 401 Unauthorized — нормальный ответ сервера о том, что пользователь еще неавторизировался, обычно после этого на абонентское оборудование отправляет на сервер логин и пароль
SIP/2.0 401 Expired Authorization — время регистрации истекло
SIP/2.0 403 No Such User — нет такого пользователя, ошибка в номере, логине или пароле
SIP/2.0 403 User Disabled — пользователь отключен
SIP/2.0 403 Wrong Guess — ошибка в пароле
SIP/2.0 403 Forbidden — абонент не зарегистрирован
SIP/2.0 403 Empty Route Set — нет ни одного шлюза в роутинге
SIP/2.0 403 Caller Not Registered — нет такого пользователя
SIP/2.0 403 Out of Look-Ahead Retries — перебор узлов закончен
SIP/2.0 403 Invalid Phone Number — нет такого направления
SIP/2.0 404 Not found — вызываемый абонент не найден, нет такого SIP-номера
SIP/2.0 404 Undefined Reason — неопределенное направление
SIP/2.0 404 Unknown user account — логин и пароль не найдены
SIP/2.0 405 Method Not Allowed — метод не поддерживается, может возникать если пользователь пытается отправлять голосовую почту и т.п.
SIP/2.0 406 No codecs match — неправильная конфигурация кодеков
SIP/2.0 406 Not Acceptable
SIP/2.0 407 Proxy Authentication Required — что-то с регистрацией
SIP/2.0 408 Request Timeout — превышение ожижание ответа на запрос
SIP/2.0 408 Login timed out — за отведенное время не получен ответ от сервера на запрос авторизации
SIP/2.0 410 No Route — вариант SIP/2.0 403 Empty Route Set
SIP/2.0 415 No Media — несоответствие кодеков
SIP/2.0 480 Invalid Phone Number — неправильный номер телефона
SIP/2.0 480 Destination Not Found In Client Plan — направления не существует
SIP/2.0 480 Codec Mismatch — несоответствие кодеков
SIP/2.0 480 Empty Route Set — что-то с маршрутизацией
SIP/2.0 480 No money left — недостаточно денег на счете
SIP/2.0 480 Temporarily Unavailable — временно недоступное направление — попробуйте позвонить позже
SIP/2.0 481 Call Leg/Transaction Does Not Exist — действие не выполнено, нормальный ответ при поступлении дублирующего пакета
SIP/2.0 487 Request Terminated — запрос отменен, обычно приходит при отмене вызова
SIP/2.0 486 Busy Here — абонент занят
SIP/2.0 488 Codec Mismatch — нет шлюзов с поддержкой заказанного кодека
SIP/2.0 488 Private IP Address — адрес RTP media из сетей RFC1918
SIP/2.0 499 Codec Mismatch — отсутствует кодек
SIP/2.0 500 Internal Server Error — внутренняя ошибка сервера
SIP/2.0 500 DB Timeout — нет ответа от базы данных
SIP/2.0 500 Database Error — то же самое, но в другой момент
SIP/2.0 500 Wrong DB Response — неправильный ответ базы данных
SIP/2.0 500 Undefined Reason — неопределенная причина
SIP/2.0 500 account has been moved to a remote system — аккаунт перенесен в удаленную систему (дословно)
SIP/2.0 5хх — проблемы с SoftSwitch-ом
SIP/2.0 603 Decline — отказ в обслуживании звонка
Читайте другие страницы сайта.
- 400 Bad Request (Неправильный запрос)
- 401 Unauthorized (Несанкционированный доступ): Используется только серверами регистрации. Прокси сервера должны требовать авторизацию для прокси сервера — код 407
- 402 Payment Required: Хочу денег (Зарезервировано для будущего использования)
- 403 Forbidden (Запрещено)
- 403 Empty Route Set (нет ни одного шлюза в роутинге)
- 403 Caller Not Registered (вызывающий абонент не зарегистрирован)
- 403 Out of Look-Ahead Retries (перебор узлов закончен)
- 403 Invalid Phone Number (нет такого направления)
- 404 Not Found: (Пользователь не найден)
- 404 Unknown user account: (Неизвестный логин и пароль)
- 405 Method Not Allowed (Метод не поддерживается)
- 406 Not Acceptable (Неприемлемый запрос)
- 407 Proxy Authentication Required (Требуется авторизация для прокси сервера)
- 408 Request Timeout: Таймаут при выполнении запроса (Невозможно найти пользователя за заданное время)
- 408 Login timed out: (за отведенное время не получен ответ от сервера на запрос авторизации)
- 410 Gone (Отсутствует): Пользователь существовал, но в данный момент недоступен.
- 410 No Route (вариант 403 Empty Route Set)
- 413 Request Entity Too Large (Слишком большой запрос)
- 414 Request-URI Too Long (Запрашиваемый URI слишком длинный)
- 415 Unsupported Media Type (Запрашиваемый тип медиаданных не поддерживается)
- 415 No Media (заявленный шлюзом кодек по факту не поддерживается)
- 416 Unsupported URI Scheme (Заданный в URI способ доступа не поддерживается)
- 420 Bad Extension (неизвестное расширение): Используется неизвестное серверу расширение протокола SIP.
- 421 Extension Required (Требуется расширение)
- 423 Interval Too Brief (Слишком короткий интервал)
- 480 Temporarily Unavailable (Временно недоступно)
- 480 Codec Mismatch (отсутствует кодек)
- 480 No money left (недостаточно денег на счете)
- 480 Invalid Phone Number (не правильно набран номер)
- 480 Temporarily Unavailable (временно недоступное направление)
- 481 Call/Transaction Does Not Exist (Вызова/Транзакции не существует)
- 482 Loop Detected (Обнаружено зацикливание)
- 483 Too Many Hops (Слишком много узлов на пути запроса)
- 484 Address Incomplete (Адрес не полный)
- 485 Ambiguous (Не однозначный, сомнительный запрос)
- 486 Busy Here (Занято)
- 487 Request Terminated (Запрос прерван)
- 488 Not Acceptable Here (Не поддерживается)
- 488 Codec Mismatch (нет шлюзов с поддержкой заказанного кодека)
- 488 Private IP Address (адрес RTP media из сетей RFC1918)
- 491 Request Pending (Обработка запроса не закончена)
- 493 Undecipherable (не расшифровать): Невозможно декодировать тело сообщения S/MIME
- 499 Codec Mismatch (отсутствует кодек): Аналогично ошибке 480.
- SIP | Коды ответа SIP протокола | 1xx | 2xx | 3xx | 4xx | 5xx | 6xx
Introduction[]
This article displays SIP error codes and a definition of such codes
Categories of SIP messages[]
- 1xx is ‘Informational’
- 2xx is ‘Success’
- 3xx is a ‘Redirection’
- 4xx is a ‘Client Error’
- 5xx is a ‘Server Error’
- 6xx is a ‘Global Failure’
1xx—Provisional Responses[]
- As mentioned earlier, a 1xx SIP response code can be sent at anytime while a connection is being established. Some of the regularly received codes are
| Message Id | Description | ||
|---|---|---|---|
| 100 Trying | This response indicates that the request has been received by the next-hop server and that some unspecified action is being taken on behalf of this call (for example, a database is being consulted). This response, like all other provisional responses, stops retransmissions of an INVITE by a UAC. The 100 (Trying) response is different from other provisional responses, in that it is never forwarded upstream by a stateful proxy. | ||
| 180 Ringing | Destination user agent received INVITE, and is alerting user of call. | ||
| 181 Call is being forwarded | Servers can optionally send this response to indicate a call is being forwarded. | ||
| 182 QUeued | The called party is temporarily unavailable, but the server has decided to queue the call rather than reject it. When the callee becomes available, it will return the appropriate final status response. The reason phrase MAY give further details about the status of the call, for example, «5 calls queued; expected waiting time is 15 minutes». The server MAY issue several 182 (Queued) responses to update the caller about the status of the queued call. | ||
| 183 Session Progress | The 183 (Session Progress) response is used to convey information about the progress of the call that is not otherwise classified. The Reason-Phrase, header fields, or message body MAY be used to convey more details about the call progress. | ||
| 199 Early Dialog Terminated | Can be used by User Agent Server to indicate to upstream SIP entities (including the User Agent Client (UAC)) that an early dialog has been terminated. |
2xx—Successful Responses[]
The 2xx response codes are used to indicate that a SIP request has been successfully processed. You’ll typically see the following versions:
| Message Id | Description | ||
|---|---|---|---|
| 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. | ||
| 204 No Notification | Indicates the request was successful, but the corresponding response will not be received. |
3xx—Redirection Responses[]
3xx responses give information about the user’s new location, or about alternative services that might be able to satisfy the call.
| Message Id | Description | ||
|---|---|---|---|
| 300 Multiple Choices | The address in the request resolved to several choices, each with its own specific location, and the user (or UA) can select a preferred communication end point and redirect its request to that location.
The response MAY include a message body containing a list of resource characteristics and location(s) from which the user or UA can choose the one most appropriate, if allowed by the Accept request header field. However, no MIME types have been defined for this message body. |
||
| 301 Moved Permanently | The user can no longer be found at the address in the Request-URI, and the requesting client SHOULD retry at the new address given by the Contact header field. The requester SHOULD update any local directories, address books, and user location caches with this new value and redirect future requests to the address(es) listed. | ||
| 302 Moved Temporarily | The requesting client SHOULD retry the request at the new address(es) given by the Contact header field. The Request-URI of the new request uses the value of the Contact header field in the response.
The duration of the validity of the Contact URI can be indicated through an Expires header field or an expires parameter in the Contact header field. Both proxies and UAs MAY cache this URI for the duration of the expiration time. If there is no explicit expiration time, the address is only valid once for recursing, and MUST NOT be cached for future transactions. |
||
| 305 Use Proxy | The requested resource MUST be accessed through the proxy given by the Contact field. The Contact field gives the URI of the proxy. The recipient is expected to repeat this single request via the proxy. 305 (Use Proxy) responses MUST only be generated by UASs. | ||
| 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. |
4xx—Client Failure Responses[]
4xx responses are definite failure responses from a particular server. The client SHOULD NOT retry the same request without modification (for example, adding appropriate authorization). However, the same request to a different server might be successful.
| Message Id | Description | ||
|---|---|---|---|
| 400 Bad Request | The request could not be understood due to malformed syntax. The Reason-Phrase SHOULD identify the syntax problem in more detail, for example, «Missing Call-ID header field». | ||
| 401 Unauthorized | The request requires user authentication. This response is issued by UASs and registrars. | ||
| 402 Payment Required | Reserved for future use. | ||
| 403 Forbidden | 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. | ||
| 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. | ||
| 408 Request Timeout | 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. | ||
| 409 Conflict | User already registered. | ||
| 410 Gone | The user existed once, but is not available here any more. | ||
| 411 Length Required | The server will not accept the request without a valid Content-Length. | ||
| 412 Conditional Request Failed | The given precondition has not been met. | ||
| 413 Request Entity Too Large | The server is refusing to process a request because the request entity-body is larger than the server is willing or able to process. The server MAY close the connection to prevent the client from continuing the request.
If the condition is temporary, the server SHOULD include a Retry-After header field to indicate that it is temporary and after what time the client MAY try again. |
||
| 414 Request-URI Too Long | The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. | ||
| 415 Unsupported Media Type | The server is refusing to service the request because the message body of the request is in a format not supported by the server for the requested method. The server MUST return a list of acceptable formats using the Accept, Accept-Encoding, or Accept-Language header field, depending on the specific problem with the content. | ||
| 416 Unsupported URI Scheme | The server cannot process the request because the scheme of the URI in the Request-URI is unknown to the server. | ||
| 417 Unknown Resource-Priority | There was a resource-priority option tag, but no Resource-Priority header. | ||
| 420 Bad Extension | The server did not understand the protocol extension specified in a Proxy-Require or Require header field. The server MUST include a list of the unsupported extensions in an Unsupported header field in the response. | ||
| 421 Extension Required | The UAS needs a particular extension to process the request, but this extension is not listed in a Supported header field in the request. Responses with this status code MUST contain a Require header field listing the required extensions.
A UAS SHOULD NOT use this response unless it truly cannot provide any useful service to the client. Instead, if a desirable extension is not listed in the Supported header field, servers SHOULD process the request using baseline SIP capabilities and any extensions supported by the client. |
||
| 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 | The server is rejecting the request because the expiration time of the resource refreshed by the request is too short. This response can be used by a registrar to reject a registration whose Contact header field expiration time was too small. | ||
| 424 Bad Location Information | The request’s location content was malformed or otherwise unsatisfactory. | ||
| 428 Use Identity Header | The server policy requires an Identity header, and one has not been provided. | ||
| 429 Provide Referrer Identity | 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). |
||
| 433 Anonymity Disallowed | The request has been rejected because it was anonymous. | ||
| 436 Bad Identity-Info | The request has an Identity-Info header, and the URI scheme in that header cannot be dereferenced. | ||
| 437 Unsupported Certificate | The server was unable to validate a certificate for the domain that signed the request. | ||
| 438 Invalid Identity Header | The server obtained a valid certificate that the request claimed was used to sign the request, but was unable to verify that signature. | ||
| 439 First Hop Lacks Outbound Support | The first outbound proxy the user is attempting to register through does not support the «outbound» feature of RFC 5626, although the registrar does. | ||
| 440 Max-Breadth Exceeded | 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. | ||
| 469 Bad Info Package | 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. | ||
| 470 Consent Needed | The source of the request did not have the permission of the recipient to make such a request. | ||
| 480 Temporarily Unavailable | The callee’s end system was contacted successfully but the callee is currently unavailable (for example, is not logged in, logged in but in a state that precludes communication with the callee, or has activated the «do not disturb» feature). The response MAY indicate a better time to call in the Retry-After header field. The user could also be available elsewhere (unbeknownst to this server). The reason phrase SHOULD indicate a more precise cause as to why the callee is unavailable. This value SHOULD be settable by the UA. Status 486 (Busy Here) MAY be used to more precisely indicate a particular reason for the call failure.
This status is also returned by a redirect or proxy server that recognizes the user identified by the Request-URI, but does not currently have a valid forwarding location for that user. |
||
| 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 | The server received a request with a Request-URI that was incomplete. Additional information SHOULD be provided in the reason phrase.
This status code allows overlapped dialing. With overlapped dialing, the client does not know the length of the dialing string. It sends strings of increasing lengths, prompting the user for more input, until it no longer receives a 484 (Address Incomplete) status response. |
||
| 485 Ambiguous | The Request-URI was ambiguous. The response MAY contain a listing of possible unambiguous addresses in Contact header fields. Revealing alternatives can infringe on privacy of the user or the organization. It MUST be possible to configure a server to respond with status 404 (Not Found) or to suppress the listing of possible choices for ambiguous Request-URIs.
Some email and voice mail systems provide this functionality. A status code separate from 3xx is used since the semantics are different: for 300, it is assumed that the same person or service will be reached by the choices provided. While an automated choice or sequential search makes sense for a 3xx response, user intervention is required for a 485 (Ambiguous) response. |
||
| 486 Busy Here | The callee’s end system was contacted successfully, but the callee is currently not willing or able to take additional calls at this end system. The response MAY indicate a better time to call in the Retry-After header field. The user could also be available elsewhere, such as through a voice mail service. Status 600 (Busy Everywhere) SHOULD be used if the client knows that no other end system will be able to accept this call. | ||
| 487 Request Terminated | The request was terminated by a BYE or CANCEL request. This response is never returned for a CANCEL request itself. | ||
| 488 Not Acceptable Here | The response has the same meaning as 606 (Not Acceptable), but only applies to the specific resource addressed by the Request-URI and the request may succeed elsewhere.
A message body containing a description of media capabilities MAY be present in the response, which is formatted according to the Accept header field in the INVITE (or application/sdp if not present), the same as a message body in a 200 (OK) response to an OPTIONS request. |
||
| 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. | ||
| 493 Undecipherable | The request was received by a UAS that contained an encrypted MIME body for which the recipient does not possess or will not provide an appropriate decryption key. This response MAY have a single body containing an appropriate public key that should be used to encrypt MIME bodies sent to this UA. | ||
| 494 Security Agreement Required | 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. |
5xx—Server Failure Responses[]
5xx responses relate to server error issues and are mostly generated by the likes of proxy servers, location servers, and redirect servers. You’ll be familiar with some of these: — 500 Server Internal Error — 501 Not Implemented — 502 Bad Gateway — 503 Service Unavailable — 504 Server Time-Out
| Message Id | Description | ||
|---|---|---|---|
| 500 Server Internal Error | The server encountered an unexpected condition that prevented it from fulfilling the request. The client MAY display the specific error condition and MAY retry the request after several seconds.
If the condition is temporary, the server MAY indicate when the client may retry the request using the Retry-After header field. |
||
| 501 Not Implemented | The server does not support the functionality required to fulfill the request. This is the appropriate response when a UAS does not recognize the request method and is not capable of supporting it for any user. (Proxies forward all requests regardless of method.)
Note that a 405 (Method Not Allowed) is sent when the server recognizes the request method, but that method is not allowed or supported. |
||
| 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 temporarily unable to process the request due to a temporary overloading or maintenance of the server. The server MAY indicate when the client should retry the request in a Retry-After header field. If no Retry-After is given, the client MUST act as if it had received a 500 (Server Internal Error) response.
A client (proxy or UAC) receiving a 503 (Service Unavailable) SHOULD attempt to forward the request to an alternate server. It SHOULD NOT forward any other requests to that server for the duration specified in the Retry-After header field, if present. |
||
| 504 Server Time-out | The server did not receive a timely response from an external server it accessed in attempting to process the request. 408 (Request Timeout) should be used instead if there was no response within the period specified in the Expires header field from the upstream server. | ||
| 505 Version Not Supported | The server does not support, or refuses to support, the SIP protocol version that was used in the request. The server is indicating that it is unable or unwilling to complete the request using the same major version as the client, other than with this error message. | ||
| 513 Message Too Large | The server was unable to process the request since the message length exceeded its capabilities. | ||
| 580 Precondition Failure | The server is unable or unwilling to meet some constraints specified in the offer. |
6xx—Global Failure Responses[]
Finally, the 6xx response codes relate to Global Error issues. They include: — 600 Busy Everywhere — 603 Decline — 604 Does Not Exist Anywhere — 606 Not Acceptable
| Message Id | Description | ||
|---|---|---|---|
| 600 Busy Everywhere | The callee’s end system was contacted successfully but the callee is busy and does not wish to take the call at this time. The response MAY indicate a better time to call in the Retry-After header field.
If the callee does not wish to reveal the reason for declining the call, the callee uses status code 603 (Decline) instead. This status response is returned only if the client knows that no other end point (such as a voice mail system) will answer the request. Otherwise, 486 (Busy Here) should be returned. |
||
| 603 Decline | The callee’s machine was successfully contacted but the user explicitly does not wish to or cannot participate. The response MAY indicate a better time to call in the Retry-After header field. This status response is returned only if the client knows that no other end point will answer the request. | ||
| 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.
A 606 (Not Acceptable) response means that the user wishes to communicate, but cannot adequately support the session described. The 606 (Not Acceptable) response MAY contain a list of reasons in a Warning header field describing why the session described cannot be supported. |
||
| 607 Unwanted | The called party did not want this call from the calling party. Future attempts from the calling party are likely to be similarly rejected. |
Introduction[]
This article displays SIP error codes and a definition of such codes
Categories of SIP messages[]
- 1xx is ‘Informational’
- 2xx is ‘Success’
- 3xx is a ‘Redirection’
- 4xx is a ‘Client Error’
- 5xx is a ‘Server Error’
- 6xx is a ‘Global Failure’
1xx—Provisional Responses[]
- As mentioned earlier, a 1xx SIP response code can be sent at anytime while a connection is being established. Some of the regularly received codes are
| Message Id | Description | ||
|---|---|---|---|
| 100 Trying | This response indicates that the request has been received by the next-hop server and that some unspecified action is being taken on behalf of this call (for example, a database is being consulted). This response, like all other provisional responses, stops retransmissions of an INVITE by a UAC. The 100 (Trying) response is different from other provisional responses, in that it is never forwarded upstream by a stateful proxy. | ||
| 180 Ringing | Destination user agent received INVITE, and is alerting user of call. | ||
| 181 Call is being forwarded | Servers can optionally send this response to indicate a call is being forwarded. | ||
| 182 QUeued | The called party is temporarily unavailable, but the server has decided to queue the call rather than reject it. When the callee becomes available, it will return the appropriate final status response. The reason phrase MAY give further details about the status of the call, for example, «5 calls queued; expected waiting time is 15 minutes». The server MAY issue several 182 (Queued) responses to update the caller about the status of the queued call. | ||
| 183 Session Progress | The 183 (Session Progress) response is used to convey information about the progress of the call that is not otherwise classified. The Reason-Phrase, header fields, or message body MAY be used to convey more details about the call progress. | ||
| 199 Early Dialog Terminated | Can be used by User Agent Server to indicate to upstream SIP entities (including the User Agent Client (UAC)) that an early dialog has been terminated. |
2xx—Successful Responses[]
The 2xx response codes are used to indicate that a SIP request has been successfully processed. You’ll typically see the following versions:
| Message Id | Description | ||
|---|---|---|---|
| 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. | ||
| 204 No Notification | Indicates the request was successful, but the corresponding response will not be received. |
3xx—Redirection Responses[]
3xx responses give information about the user’s new location, or about alternative services that might be able to satisfy the call.
| Message Id | Description | ||
|---|---|---|---|
| 300 Multiple Choices | The address in the request resolved to several choices, each with its own specific location, and the user (or UA) can select a preferred communication end point and redirect its request to that location.
The response MAY include a message body containing a list of resource characteristics and location(s) from which the user or UA can choose the one most appropriate, if allowed by the Accept request header field. However, no MIME types have been defined for this message body. |
||
| 301 Moved Permanently | The user can no longer be found at the address in the Request-URI, and the requesting client SHOULD retry at the new address given by the Contact header field. The requester SHOULD update any local directories, address books, and user location caches with this new value and redirect future requests to the address(es) listed. | ||
| 302 Moved Temporarily | The requesting client SHOULD retry the request at the new address(es) given by the Contact header field. The Request-URI of the new request uses the value of the Contact header field in the response.
The duration of the validity of the Contact URI can be indicated through an Expires header field or an expires parameter in the Contact header field. Both proxies and UAs MAY cache this URI for the duration of the expiration time. If there is no explicit expiration time, the address is only valid once for recursing, and MUST NOT be cached for future transactions. |
||
| 305 Use Proxy | The requested resource MUST be accessed through the proxy given by the Contact field. The Contact field gives the URI of the proxy. The recipient is expected to repeat this single request via the proxy. 305 (Use Proxy) responses MUST only be generated by UASs. | ||
| 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. |
4xx—Client Failure Responses[]
4xx responses are definite failure responses from a particular server. The client SHOULD NOT retry the same request without modification (for example, adding appropriate authorization). However, the same request to a different server might be successful.
| Message Id | Description | ||
|---|---|---|---|
| 400 Bad Request | The request could not be understood due to malformed syntax. The Reason-Phrase SHOULD identify the syntax problem in more detail, for example, «Missing Call-ID header field». | ||
| 401 Unauthorized | The request requires user authentication. This response is issued by UASs and registrars. | ||
| 402 Payment Required | Reserved for future use. | ||
| 403 Forbidden | 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. | ||
| 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. | ||
| 408 Request Timeout | 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. | ||
| 409 Conflict | User already registered. | ||
| 410 Gone | The user existed once, but is not available here any more. | ||
| 411 Length Required | The server will not accept the request without a valid Content-Length. | ||
| 412 Conditional Request Failed | The given precondition has not been met. | ||
| 413 Request Entity Too Large | The server is refusing to process a request because the request entity-body is larger than the server is willing or able to process. The server MAY close the connection to prevent the client from continuing the request.
If the condition is temporary, the server SHOULD include a Retry-After header field to indicate that it is temporary and after what time the client MAY try again. |
||
| 414 Request-URI Too Long | The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. | ||
| 415 Unsupported Media Type | The server is refusing to service the request because the message body of the request is in a format not supported by the server for the requested method. The server MUST return a list of acceptable formats using the Accept, Accept-Encoding, or Accept-Language header field, depending on the specific problem with the content. | ||
| 416 Unsupported URI Scheme | The server cannot process the request because the scheme of the URI in the Request-URI is unknown to the server. | ||
| 417 Unknown Resource-Priority | There was a resource-priority option tag, but no Resource-Priority header. | ||
| 420 Bad Extension | The server did not understand the protocol extension specified in a Proxy-Require or Require header field. The server MUST include a list of the unsupported extensions in an Unsupported header field in the response. | ||
| 421 Extension Required | The UAS needs a particular extension to process the request, but this extension is not listed in a Supported header field in the request. Responses with this status code MUST contain a Require header field listing the required extensions.
A UAS SHOULD NOT use this response unless it truly cannot provide any useful service to the client. Instead, if a desirable extension is not listed in the Supported header field, servers SHOULD process the request using baseline SIP capabilities and any extensions supported by the client. |
||
| 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 | The server is rejecting the request because the expiration time of the resource refreshed by the request is too short. This response can be used by a registrar to reject a registration whose Contact header field expiration time was too small. | ||
| 424 Bad Location Information | The request’s location content was malformed or otherwise unsatisfactory. | ||
| 428 Use Identity Header | The server policy requires an Identity header, and one has not been provided. | ||
| 429 Provide Referrer Identity | 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). |
||
| 433 Anonymity Disallowed | The request has been rejected because it was anonymous. | ||
| 436 Bad Identity-Info | The request has an Identity-Info header, and the URI scheme in that header cannot be dereferenced. | ||
| 437 Unsupported Certificate | The server was unable to validate a certificate for the domain that signed the request. | ||
| 438 Invalid Identity Header | The server obtained a valid certificate that the request claimed was used to sign the request, but was unable to verify that signature. | ||
| 439 First Hop Lacks Outbound Support | The first outbound proxy the user is attempting to register through does not support the «outbound» feature of RFC 5626, although the registrar does. | ||
| 440 Max-Breadth Exceeded | 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. | ||
| 469 Bad Info Package | 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. | ||
| 470 Consent Needed | The source of the request did not have the permission of the recipient to make such a request. | ||
| 480 Temporarily Unavailable | The callee’s end system was contacted successfully but the callee is currently unavailable (for example, is not logged in, logged in but in a state that precludes communication with the callee, or has activated the «do not disturb» feature). The response MAY indicate a better time to call in the Retry-After header field. The user could also be available elsewhere (unbeknownst to this server). The reason phrase SHOULD indicate a more precise cause as to why the callee is unavailable. This value SHOULD be settable by the UA. Status 486 (Busy Here) MAY be used to more precisely indicate a particular reason for the call failure.
This status is also returned by a redirect or proxy server that recognizes the user identified by the Request-URI, but does not currently have a valid forwarding location for that user. |
||
| 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 | The server received a request with a Request-URI that was incomplete. Additional information SHOULD be provided in the reason phrase.
This status code allows overlapped dialing. With overlapped dialing, the client does not know the length of the dialing string. It sends strings of increasing lengths, prompting the user for more input, until it no longer receives a 484 (Address Incomplete) status response. |
||
| 485 Ambiguous | The Request-URI was ambiguous. The response MAY contain a listing of possible unambiguous addresses in Contact header fields. Revealing alternatives can infringe on privacy of the user or the organization. It MUST be possible to configure a server to respond with status 404 (Not Found) or to suppress the listing of possible choices for ambiguous Request-URIs.
Some email and voice mail systems provide this functionality. A status code separate from 3xx is used since the semantics are different: for 300, it is assumed that the same person or service will be reached by the choices provided. While an automated choice or sequential search makes sense for a 3xx response, user intervention is required for a 485 (Ambiguous) response. |
||
| 486 Busy Here | The callee’s end system was contacted successfully, but the callee is currently not willing or able to take additional calls at this end system. The response MAY indicate a better time to call in the Retry-After header field. The user could also be available elsewhere, such as through a voice mail service. Status 600 (Busy Everywhere) SHOULD be used if the client knows that no other end system will be able to accept this call. | ||
| 487 Request Terminated | The request was terminated by a BYE or CANCEL request. This response is never returned for a CANCEL request itself. | ||
| 488 Not Acceptable Here | The response has the same meaning as 606 (Not Acceptable), but only applies to the specific resource addressed by the Request-URI and the request may succeed elsewhere.
A message body containing a description of media capabilities MAY be present in the response, which is formatted according to the Accept header field in the INVITE (or application/sdp if not present), the same as a message body in a 200 (OK) response to an OPTIONS request. |
||
| 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. | ||
| 493 Undecipherable | The request was received by a UAS that contained an encrypted MIME body for which the recipient does not possess or will not provide an appropriate decryption key. This response MAY have a single body containing an appropriate public key that should be used to encrypt MIME bodies sent to this UA. | ||
| 494 Security Agreement Required | 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. |
5xx—Server Failure Responses[]
5xx responses relate to server error issues and are mostly generated by the likes of proxy servers, location servers, and redirect servers. You’ll be familiar with some of these: — 500 Server Internal Error — 501 Not Implemented — 502 Bad Gateway — 503 Service Unavailable — 504 Server Time-Out
| Message Id | Description | ||
|---|---|---|---|
| 500 Server Internal Error | The server encountered an unexpected condition that prevented it from fulfilling the request. The client MAY display the specific error condition and MAY retry the request after several seconds.
If the condition is temporary, the server MAY indicate when the client may retry the request using the Retry-After header field. |
||
| 501 Not Implemented | The server does not support the functionality required to fulfill the request. This is the appropriate response when a UAS does not recognize the request method and is not capable of supporting it for any user. (Proxies forward all requests regardless of method.)
Note that a 405 (Method Not Allowed) is sent when the server recognizes the request method, but that method is not allowed or supported. |
||
| 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 temporarily unable to process the request due to a temporary overloading or maintenance of the server. The server MAY indicate when the client should retry the request in a Retry-After header field. If no Retry-After is given, the client MUST act as if it had received a 500 (Server Internal Error) response.
A client (proxy or UAC) receiving a 503 (Service Unavailable) SHOULD attempt to forward the request to an alternate server. It SHOULD NOT forward any other requests to that server for the duration specified in the Retry-After header field, if present. |
||
| 504 Server Time-out | The server did not receive a timely response from an external server it accessed in attempting to process the request. 408 (Request Timeout) should be used instead if there was no response within the period specified in the Expires header field from the upstream server. | ||
| 505 Version Not Supported | The server does not support, or refuses to support, the SIP protocol version that was used in the request. The server is indicating that it is unable or unwilling to complete the request using the same major version as the client, other than with this error message. | ||
| 513 Message Too Large | The server was unable to process the request since the message length exceeded its capabilities. | ||
| 580 Precondition Failure | The server is unable or unwilling to meet some constraints specified in the offer. |
6xx—Global Failure Responses[]
Finally, the 6xx response codes relate to Global Error issues. They include: — 600 Busy Everywhere — 603 Decline — 604 Does Not Exist Anywhere — 606 Not Acceptable
| Message Id | Description | ||
|---|---|---|---|
| 600 Busy Everywhere | The callee’s end system was contacted successfully but the callee is busy and does not wish to take the call at this time. The response MAY indicate a better time to call in the Retry-After header field.
If the callee does not wish to reveal the reason for declining the call, the callee uses status code 603 (Decline) instead. This status response is returned only if the client knows that no other end point (such as a voice mail system) will answer the request. Otherwise, 486 (Busy Here) should be returned. |
||
| 603 Decline | The callee’s machine was successfully contacted but the user explicitly does not wish to or cannot participate. The response MAY indicate a better time to call in the Retry-After header field. This status response is returned only if the client knows that no other end point will answer the request. | ||
| 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.
A 606 (Not Acceptable) response means that the user wishes to communicate, but cannot adequately support the session described. The 606 (Not Acceptable) response MAY contain a list of reasons in a Warning header field describing why the session described cannot be supported. |
||
| 607 Unwanted | The called party did not want this call from the calling party. Future attempts from the calling party are likely to be similarly rejected. |
Цитата:
SIP/2.0 400 Bad Request — ошибка в сигнализации, скорее всего что-то с настройками оборудования
SIP/2.0 401 Unauthorized — нормальный ответ сервера о том, что пользователь еще неавторизировался, обычно после этого на абонентское оборудование отправляет на сервер логин и пароль
SIP/2.0 401 Expired Authorization — время регистрации истекло
SIP/2.0 403 No Such User — нет такого пользователя, ошибка в номере, логине или пароле
SIP/2.0 403 User Disabled — пользователь отключен
SIP/2.0 403 Wrong Guess — ошибка в пароле
SIP/2.0 403 Forbidden — абонент не зарегистрирован
SIP/2.0 403 Empty Route Set — нет ни одного шлюза в роутинге
SIP/2.0 403 Caller Not Registered — нет такого пользователя
SIP/2.0 403 Out of Look-Ahead Retries — перебор узлов закончен
SIP/2.0 403 Invalid Phone Number — нет такого направления
SIP/2.0 404 Not found — вызываемый абонент не найден, нет такого SIP-номера
SIP/2.0 404 Undefined Reason — неопределенное направление
SIP/2.0 404 Unknown user account — логин и пароль не найдены
SIP/2.0 405 Method Not Allowed — метод не поддерживается, может возникать если пользователь пытается отправлять голосовую почту и т.п.
SIP/2.0 406 No codecs match — неправильная конфигурация кодеков
SIP/2.0 406 Not Acceptable
SIP/2.0 407 Proxy Authentication Required — что-то с регистрацией
SIP/2.0 408 Request Timeout — превышение ожижание ответа на запрос
SIP/2.0 408 Login timed out — за отведенное время не получен ответ от сервера на запрос авторизации
SIP/2.0 410 No Route — вариант SIP/2.0 403 Empty Route Set
SIP/2.0 415 No Media — несоответствие кодеков
SIP/2.0 480 Invalid Phone Number — неправильный номер телефона
SIP/2.0 480 Destination Not Found In Client Plan — направления не существует
SIP/2.0 480 Codec Mismatch — несоответствие кодеков
SIP/2.0 480 Empty Route Set — что-то с маршрутизацией
SIP/2.0 480 No money left — недостаточно денег на счете
SIP/2.0 480 Temporarily Unavailable — временно недоступное направление — попробуйте позвонить позже
SIP/2.0 481 Call Leg/Transaction Does Not Exist — действие не выполнено, нормальный ответ при поступлении дублирующего пакета
SIP/2.0 487 Request Terminated — запрос отменен, обычно приходит при отмене вызова
SIP/2.0 486 Busy Here — абонент занят
SIP/2.0 488 Codec Mismatch — нет шлюзов с поддержкой заказанного кодека
SIP/2.0 488 Private IP Address — адрес RTP media из сетей RFC1918
SIP/2.0 499 Codec Mismatch — отсутствует кодек
SIP/2.0 500 Internal Server Error — внутренняя ошибка сервера
SIP/2.0 500 DB Timeout — нет ответа от базы данных
SIP/2.0 500 Database Error — то же самое, но в другой момент
SIP/2.0 500 Wrong DB Response — неправильный ответ базы данных
SIP/2.0 500 Undefined Reason — неопределенная причина
SIP/2.0 500 account has been moved to a remote system — аккаунт перенесен в удаленную систему (дословно)
SIP/2.0 5хх — проблемы с SoftSwitch-ом
SIP/2.0 603 Decline — отказ в обслуживании звонка
Цитата:
0x31 Ошибка настройки IP-адреса: Не введен IP-адрес домена.
0x33 Ошибка настройки IP-адреса: Не введено имя пользователя SIP (Авторизация Имя). Появляется, например, при наборе с суффиксом линии, если в базовом блоке соединение для суффикса не настроено.
0x34 Ошибка настройки IP-адреса: Не введен пароль пользователя SIP (Авторизация Пароль).
0x300 С вызываемым абонентом можно связаться по нескольким телефонным номерам. Если оператор IP-телефонии поддерживает эту функцию, список телефонных номеров передается вместе с кодом состояния. Вызывающий абонент может выбрать номер для соединения.
0x301 Постоянная переадресация. Связаться с вызываемым абонентом по этому номеру больше нельзя. Новый номер передается на телефон вместе с кодом состояния, после чего телефон уже не обращается к старому номеру, а сразу набирает новый номер.
0x302 Временная переадресация. На телефон поступает информация, что по набираемому номеру вызываемый абонент временно недоступен. Вызовы переадресуются на определенное время. Сообщается также о продолжительности переадресации.
0x305 Запрос отправлен на другой прокси-сервер, например, на билинговый сервер. Телефон отправит повторный запрос на другой прокси-сервер. Это не перенаправление самого адреса.
0x380 Другая услуга: Запрос или вызов не может быть передан. Однако на телефон отправляются данные о других возможностях соединения.
0x400 Неверный вызов
0x401 Отказано в доступе
0x403 Оператор IP-телефонии не поддерживает запрашиваемую услугу.
0x404 Неверный номер телефона. Невозможно установить соединение с этим номером. Пример: при наборе местного номера не был набран код зоны, хотя оператор IP-телефонии не поддерживает местные вызовы.
0x405 Метод не разрешен.
0x406 Неприемлемо. Запрашиваемая услуга не может быть предоставлена.
0x407 Требуется разрешение на доступ к прокси-серверу.
0x408 Абонент недоступен (например, удален его расчетный счет).
0x410 Оператор IP-телефонии не предоставляет запрашиваемую услугу.
0x413 Сообщение слишком длинное.
0x414 Адрес слишком длинный.
0x415 Формат запроса не поддерживается.
0x416 Неверный URI.
0x420 Неверное окончание.
0x421 Неверное окончание.
0x423 Оператор IP-телефонии не поддерживает запрашиваемую услугу.
0x480 Набранный номер временно недоступен.
0x481 Получатель недоступен.
0x482 Двойной запрос услуги.
0x483 Слишком много «прыжков»: Запрос был отклонен, так как сервер услуг (прокси) решил, что этот запрос уже прошел через слишком большое число серверов услуг. Максимальное число определяется исходным отправителем запроса заранее.
0x484 Неверный номер: В большинстве случаев это значит, что при наборе номера пропущены цифры.
0x485 Набранный URI не уникален и не может быть обработан оператором IP-телефонии.
0x486 Набранный номер занят.
0x487 Общие ошибки: Вызов был отменен до того, как было установлено соединение. Код состояния подтверждает получение сигнала прерывания.
0x488 Сервер не может обработать запрос из-за несовместимости введенных данных описания носителей.
0x491 Сервер уведомляет, что запрос будет обработан после окончания обработки предыдущего запроса.
0x493 Сервер отклонил запрос, потому что телефон не может декодировать сообщение. Вызывающий абонент использовал метод кодирования, который не поддерживается сервером или телефоном вызываемого абонента.
0x500 При выполнении запроса прокси-сервер или принимающее устройство обнаружили ошибку. Поэтому запрос выполнить невозможно. В этом случае программа дозвона или телефон сообщает об ошибке и через несколько секунд повторяет запрос. Продолжительность паузы между двумя запросами может быть передана программе дозвона или на телефон принимающим устройством.
0x501 Запрос не может быть обработан получателем, так как у получателя отсутствуют функции, требуемые вызывающей стороной. Если получатель принимает запрос, но не обрабатывает его из-за отсутствия определенных прав у вызывающей стороны, или если запрос не разрешен в текущем контексте, вместо кода 501 передается код 405.
0x502 В этом случае получатель, передающий код ошибки, является проксисервером или шлюзом, и получил некорректный отклик от своего шлюза, через который этот запрос отправлялся на обработку.
0x503 Приемное устройство или прокси-сервер не может обработать запрос, потому что сервер перегружен или находится на техобслуживании. Если в обозримом будущем запрос можно повторить, сервер посылает сообщение об этом программе дозвона или на телефон.
0x504 Превышено время ожидания на шлюзе.
0x505 Сервер отклоняет запрос, потому что указанная версия протокола SIP не совпадает с версией, которая используется сервером либо устройством SIP, используемым в запросе.
0x515 Сервер отклоняет запрос, потому что превышена допустимая длина сообщения.
0x600 Набранный номер занят.
0x603 Вызываемый абонент отказался от соединения.
0x604 Вызываемый URI не существует.
0x606 Недопустимые настройки связи.
0x701 Вызываемый абонент повесил трубку.
0x703 Соединение прервано из-за превышения длительности разговора.
0x704 Соединение прервано из-за ошибки SIP.
0x705 Неверный сигнал набора.
0x706 Соединение не установлено.
0x751 Сигнал занятой линии: Вызывающий и принимающий абоненты используют разные кодеки.
0x810 Ошибка общего типа на уровне сокета: Пользователь не авторизован.
0x811 Ошибка общего типа на уровне сокета: Неверный номер сокета.
0x812 Ошибка общего типа на уровне сокета: Сокет не подключен.
0x813 Ошибка общего типа на уровне сокета: Ошибка памяти
0x814 Ошибка общего типа на уровне сокета: Сокет недоступен – проверить настройки IP / проблема с соединением / неправильная настройка IP-телефонии.
0x815 Ошибка общего типа на уровне сокета: Незарегистрированное приложение на сокете.
Для памяти…