Ошибка 488 sip - Исправление ошибок и поиск оптимальных решений проблем

1xx – информационные ответы

SIP/2.0 100 Trying
Запрос обрабатывается.

SIP/2.0 180 Ringing
Местоположение вызываемого пользователя определено. Выдан сигнал о входящем вызове.

SIP/2.0 181 Call is Being Forwarded
Прокси-сервер переадресует вызов к другому пользователю.

SIP/2.0 182 Call is Queued
Вызываемый абонент временно недоступен. Вызов поставлен в очередь.

SIP/2.0 183 Session Progress
Используется для того, чтобы заранее получить описание сеанса информационного обмена от шлюзов на пути к вызываемому пользователю.

2xx – ответы о завершении запроса

SIP/2.0 200 OK
Успешное завершение.

SIP/2.0 202 Accepted
Запрос принят для обработки. Используется для справки о состоянии обработки.

3xx – сообщения о переадресации

SIP/2.0 300 Multiple Choices
Указывает несколько SIP-адресов, по которым можно найти вызываемого пользователя.

SIP/2.0 301 Moved Permanently
Вызываемый пользователь больше не находится по адресу, указанному в запросе.

SIP/2.0 302 Moved Temporarily
Пользователь временно сменил местоположение (настроена переадресация по SIPUA в т.ч. с VOIP-телефона).

SIP/2.0 305 Use Proxy
Вызываемый пользователь недоступен непосредственно. Входящий вызов должен пройти через прокси-сервер.

SIP/2.0 380 Alternative Service
Запрошенная услуга недоступна, но доступны альтернативные услуги.

4xx – невозможность обработать запрос

SIP/2.0 400 Bad Request
Запрос не распознан из-за синтаксических ошибок или ошибок в сигнализации.

SIP/2.0 401 Unauthorized
Нормальный ответ сервера о том, что пользователь еще не авторизовался. Обычно после этого абонентское оборудование отправляет на сервер новый запрос, содержащий логин и пароль.

SIP/2.0 401 AUTH Error: Stall nonce
1.Разные данные в поле NONCE (шифр пароля), проверить дату/время или проблема с протоколом шифрования
2. Проверить на клиентской стороне не заблокирован ли sipnet.ru (212.53.40.40)
3. Проверить в ВАТС статус присутствия. Должен быть «нет».

SIP/2.0 401 Expired Authorization
Время регистрации истекло.

SIP/2.0 402 Payment Required
Требуется оплата (зарезервирован для использования в будущем).

SIP/2.0 403 No Such User
Нет такого пользователя. Ошибка в номере, логине или пароле.

SIP/2.0 403 No license available
Кончились лицензия на SIP

SIP/2.0 403 You
Нет такого пользователя. Ошибка в номере, логине или пароле.

SIP/2.0 403 User Disabled
Пользователь отключен.

SIP/2.0 403 You do not have the required right
Неверный логин в поле «From»

SIP/2.0 403 Wrong Guess
Ошибка в пароле.

SIP/2.0 403 Conflict
Такой SIP-номер уже используется.

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 403 No Money Left on RFC Account
На счету недостаточно денежных средств для совершения вызова.

SIP/2.0 404 Not found
Вызываемый абонент не найден, нет такого SIP-номера.

SIP/2.0 404 Undefined Reason
Неопределенное направление.

SIP/2.0 404 Unknown user account
Логин и пароль не найдены.

SIP/2.0 404 Out of Order
В заявке на маршрутизацию по этому направлению нет принимающих шлюзов.

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 407 User not found
Проверить ID на CGP

SIP/2.0 408 Request Timeout
Время обработки запроса истекло. Абонента не удалось найти за отведенное время. (Проблема с firewall, нет ответа на Invite от сервера)

SIP/2.0 408 Login timed out
За отведенное время не получен ответ от сервера на запрос авторизации.

SIP/2.0 410 No Route
Вариант «SIP/2.0 403 Empty Route Set». Нет доступа к ресурсу или ресурс по указанному адресу больше не существует.

SIP/2.0 413 Request Entity Too Large
Размер запроса слишком велик для обработки на сервере.

SIP/2.0 415 No Media
Звонок совершается неподдерживаемым кодеком.

SIP/2.0 416 Unsupported Scheme
Сервер не может обработать запрос из-за того, что схема адреса не распознана.

SIP/2.0 420 Bad extension
Неизвестное расширение. Сервер не распознал расширение протокола SIP.

SIP/2.0 421 Extension Required
В заголовке запроса не указано, какое расширение сервер должен применить для его обработки.

SIP/2.0 423 Interval Too Brief
Сервер отклоняет запрос, так как время действия ресурса короткое.

SIP/2.0 480 Invalid Phone Number
Неправильный номер телефона, не соответствует количеству цифр или неправильный код страны или города.

SIP/2.0 480 Destination Not Found In Client Plan
Нет направления в тарифном плане абонента.

SIP/2.0 480 Wrong DB Response
Проблемы с центральной базой данных.

SIP/2.0 480 DB Timeout
Проблемы с центральной базой данных.

SIP/2.0 480 Database Error
Проблемы с центральной базой данных.

SIP/2.0 480 Codec Mismatch
Несоответствие кодеков.

SIP/2.0 480 No Money Left on RFC Account
Недостаточно денежных средств на счету.

SIP/2.0 480 Empty Route Set
Пустое направление. Нет принимающих шлюзов.

SIP/2.0 480 No money left
Недостаточно денежных средств на счету.

SIP/2.0 480 Temporarily Unavailable
Временно недоступное направление. (Возможно статус DND)

SIP/2.0 481 Call Leg/Transaction Does Not Exist
Действие не выполнено. Нормальный ответ при поступлении дублирующего пакета.

SIP/2.0 482 Loop Detected
Обнаружен замкнутый маршрут передачи запроса.

SIP/2.0 483 Too Many Hops
Запрос на своем пути прошел через большее число прокси-серверов, чем разрешено.

SIP/2.0 484 Address Incomplete
Принят запрос с неполным адресом.

SIP/2.0 485 Ambiguous
Адрес вызываемого пользователя неоднозначен.

SIP/2.0 486 Busy Here
Абонент занят.

SIP/2.0 487 Request Terminated
Запрос отменен. Обычно приходит при отмене вызова.

SIP/2.0 488 Codec Mismatch
Нет шлюзов с поддержкой заказанного кодека.

SIP/2.0 488 Private IP Address
Адрес RTP media из сетей RFC1918.

SIP/2.0 488 Not acceptable here
Не совпадают кодеки

SIP/2.0 491 Request Pending
Запрос поступил в то время, когда сервер еще не закончил обработку другого запроса, относящегося к тому же диалогу.

SIP/2.0 493 Undeciperable
Сервер не в состоянии подобрать ключ дешифрования. Невозможно декодировать тело S/MIME сообщения.

SIP/2.0 499 Codec Mismatch
Отсутствует кодек.

5xx – ошибки сервера

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 500 Call placing quota exceeded
Превышен CPS.

SIP/2.0 501 Method Not Supported Here
В сервере не реализованы какие-либо функции, необходимые для обслуживания запроса. Метод запроса SIP не поддерживается.

SIP/2.0 502 Bad Gateway
Сервер, функционирующий в качестве шлюза или прокси-сервера, принимает некорректный ответ от сервера, к которому он направил запрос.

SIP/2.0 503 Service Unavailable
Сервер не может в данный момент обслужить вызов вследствие перегрузки или проведения технического обслуживания.

SIP/2.0 504 Server time-out
Сервер не получил ответа в течение установленного промежутка времени от сервера, к которому он обратился для завершения вызова.

SIP/2.0 505 SIP Version not supported
Версия не поддерживается. Сервер не поддерживает эту версию протокола SIP.

SIP/2.0 513 Message too big
Сервер не в состоянии обработать запрос из-за большой длины сообщения.

6xx – глобальная ошибка

SIP/2.0 600 Busy everywhere
Вызываемый пользователь занят и не желает принимать вызов в данный момент.

SIP/2.0 603 Decline
Вызываемый пользователь не желает принимать входящие вызовы, не указывая причину отказа.

SIP/2.0 604 Does Not Exist Anywhere
Вызываемого пользователя не существует.

SIP/2.0 606 Not Acceptable
Соединение с сервером было установлено. Отдельные параметры, такие как тип запрашиваемой информации, полоса пропускания, вид адресации не доступны.

Источник

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 — отказ в обслуживании звонка

Читайте другие страницы сайта.

Источник

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. The choices SHOULD also be listed as Contact fields. Unlike HTTP, the SIP response MAY contain several Contact fields or a list of addresses in a Contact field. UAs MAY use the Contact header field value for automatic redirection or MAY ask the user to confirm a choice. However, this specification does not define any standard for such automatic selection. This status response is appropriate if the callee can be reached at several different locations and the server cannot or prefers not to proxy the request.
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. If the URI cached from the Contact header field fails, the Request-URI from the redirected request MAY be tried again a single time. The temporary URI may have become out-of-date sooner than the expiration time, and a new temporary URI may be available.
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. Servers MAY refuse the connection or drop the request instead of responding with 503 (Service Unavailable).
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. This status response is returned only if the client knows that no other endpoint will answer the request.
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. The choices SHOULD also be listed as Contact fields. Unlike HTTP, the SIP response MAY contain several Contact fields or a list of addresses in a Contact field. UAs MAY use the Contact header field value for automatic redirection or MAY ask the user to confirm a choice. However, this specification does not define any standard for such automatic selection. This status response is appropriate if the callee can be reached at several different locations and the server cannot or prefers not to proxy the request.
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. If the URI cached from the Contact header field fails, the Request-URI from the redirected request MAY be tried again a single time. The temporary URI may have become out-of-date sooner than the expiration time, and a new temporary URI may be available.
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[]

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[]

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. Servers MAY refuse the connection or drop the request instead of responding with 503 (Service Unavailable).
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. This status response is returned only if the client knows that no other endpoint will answer the request.
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 read from UDP:19.2.41.21:5060 —>
INVITE sip:s@1.2.3.4:5060;received=1.2.3.4:41394 SIP/2.0
Via: SIP/2.0/UDP 19.2.41.21;rport;branch=z9hG4bK0gvvQyg961BjS
Route: <sip:s@1.2.3.4:41394>
Max-Forwards: 68
From: «+79262719630» <sip:89262719630@19.2.41.21>;tag=XaggZpUQ1m3vm
To: <sip:s@1.2.3.4:5060;received=1.2.3.4:41394>
Call-ID: 33783cca-387a-1234-798b-002590e5052c
CSeq: 86222354 INVITE
Contact: <sip:mod_sofia@19.2.41.21:5060>
User-Agent: MoLi callswitch1
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 373
X-FS-Support: update_display,send_info
Remote-Party-ID: «+79262719630» <sip:89262719630@19.2.41.21>;party=calling;screen=yes;privacy=off

v=0
o=FreeSWITCH 1453086816 1453086817 IN IP4 19.2.41.21
s=FreeSWITCH
c=IN IP4 19.2.41.21
t=0 0
m=audio 30020 RTP/AVP 8 0 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off — — — —
a=ptime:30
m=audio 30020 RTP/AVP 8 0 18 101
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off — — — —
a=ptime:20
<————->
— (18 headers 16 lines) —
Sending to 19.2.41.21:5060 (NAT)
Using INVITE request as basis request — 33783cca-387a-1234-798b-002590e5052c
Found peer ‘M_010’ for ‘89262719630’ from 19.2.41.21:5060
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
Found RTP audio format 8
Found RTP audio format 0
Found RTP audio format 101
Found audio description format telephone-event for ID 101

<— Reliably Transmitting (NAT) to 19.2.41.21:5060 —>
SIP/2.0 488 Not acceptable here
Via: SIP/2.0/UDP 19.2.41.21;branch=z9hG4bK0gvvQyg961BjS;received=19.2.41.21;rport=5060
From: «+79262719630» <sip:89262719630@19.2.41.21>;tag=XaggZpUQ1m3vm
To: <sip:s@1.2.3.4:5060;received=1.2.3.4:41394>;tag=as1471402a
Call-ID: 33783cca-387a-1234-798b-002590e5052c
CSeq: 86222354 INVITE
Server: FPBX-2.8.1(1.8.20.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

<————>
Scheduling destruction of SIP dialog ‘33783cca-387a-1234-798b-002590e5052c’ in 6400 ms (Method: INVITE)

<— SIP read from UDP:19.2.41.21:5060 —>
ACK sip:s@1.2.3.4:5060;received=1.2.3.4:41394 SIP/2.0
Via: SIP/2.0/UDP 19.2.41.21;rport;branch=z9hG4bK0gvvQyg961BjS
Route: <sip:s@1.2.3.4:41394>
Max-Forwards: 68
From: «+79262719630» <sip:89262719630@19.2.41.21>;tag=XaggZpUQ1m3vm
To: <sip:s@1.2.3.4:5060;received=1.2.3.4:41394>;tag=as1471402a
Call-ID: 33783cca-387a-1234-798b-002590e5052c
CSeq: 86222354 ACK
Content-Length: 0

<————->
— (9 headers 0 lines) —
Really destroying SIP dialog ‘33783cca-387a-1234-798b-002590e5052c’ Method: ACK

<— SIP read from UDP:19.2.41.21:5060 —>
INVITE sip:s@1.2.3.4:5060;received=1.2.3.4:41394 SIP/2.0
Via: SIP/2.0/UDP 19.2.41.21;rport;branch=z9hG4bK1SNNSS1c4a24m
Route: <sip:s@1.2.3.4:41394>
Max-Forwards: 68
From: «+79262719630» <sip:89262719630@19.2.41.21>;tag=Zv212cXyU6F2B
To: <sip:s@1.2.3.4:5060;received=1.2.3.4:41394>
Call-ID: 337bce93-387a-1234-798b-002590e5052c
CSeq: 86222354 INVITE
Contact: <sip:mod_sofia@19.2.41.21:5060>
User-Agent: MoLie callswitch1
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 373
X-FS-Support: update_display,send_info
Remote-Party-ID: «+79262719630» <sip:89262719630@19.2.41.21>;party=calling;screen=yes;privacy=off

v=0
o=FreeSWITCH 1453097848 1453097849 IN IP4 193.27.41.21
s=FreeSWITCH
c=IN IP4 19.2.41.21
t=0 0
m=audio 18988 RTP/AVP 8 0 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off — — — —
a=ptime:30
m=audio 18988 RTP/AVP 8 0 18 101
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off — — — —
a=ptime:20
<————->
— (18 headers 16 lines) —
Sending to 19.2.41.21:5060 (NAT)
Using INVITE request as basis request — 337bce93-387a-1234-798b-002590e5052c
Found peer ‘Mo_010’ for ‘89262719630’ from 19.2.41.21:5060
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
Found RTP audio format 8
Found RTP audio format 0
Found RTP audio format 101
Found audio description format telephone-event for ID 101

<— Reliably Transmitting (NAT) to 19.2.41.21:5060 —>
SIP/2.0 488 Not acceptable here
Via: SIP/2.0/UDP 19.2.41.21;branch=z9hG4bK1SNNSS1c4a24m;received=19.2.41.21;rport=5060
From: «+79262719630» <sip:89262719630@19.2.41.21>;tag=Zv212cXyU6F2B
To: <sip:s@1.2.3.4:5060;received=1.2.3.4:41394>;tag=as4f0d2223
Call-ID: 337bce93-387a-1234-798b-002590e5052c
CSeq: 86222354 INVITE
Server: FPBX-2.8.1(1.8.20.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

<————>
Scheduling destruction of SIP dialog ‘337bce93-387a-1234-798b-002590e5052c’ in 6400 ms (Method: INVITE)

<— SIP read from UDP:19.2.41.21:5060 —>
ACK sip:s@1.2.3.4:5060;received=1.2.3.4:41394 SIP/2.0
Via: SIP/2.0/UDP 19.2.41.21;rport;branch=z9hG4bK1SNNSS1c4a24m
Route: <sip:s@1.2.3.4:41394>
Max-Forwards: 68
From: «+79262719630» <sip:89262719630@19.2.41.21>;tag=Zv212cXyU6F2B
To: <sip:s@1.2.3.4:5060;received=1.2.3.4:41394>;tag=as4f0d2223
Call-ID: 337bce93-387a-1234-798b-002590e5052c
CSeq: 86222354 ACK
Content-Length: 0

<————->
— (9 headers 0 lines) —
Really destroying SIP dialog ‘337bce93-387a-1234-798b-002590e5052c’ Method: ACK

<— SIP read from UDP:19.2.41.21:5060 —>
INVITE sip:s@1.2.3.4:5060;received=1.2.3.4:41394 SIP/2.0
Via: SIP/2.0/UDP 19.2.41.21;rport;branch=z9hG4bK22eeUmjg1KrQg
Route: <sip:s@1.2.3.4:41394>
Max-Forwards: 68
From: «+79262719630» <sip:89262719630@19.2.41.21>;tag=05Ut47D2rF6mQ
To: <sip:s@1.2.3.4:5060;received=1.2.3.4:41394>
Call-ID: 337f7865-387a-1234-798b-002590e5052c
CSeq: 86222354 INVITE
Contact: <sip:mod_sofia@19.2.41.21:5060>
User-Agent: MoLie callswitch1
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 373
X-FS-Support: update_display,send_info
Remote-Party-ID: «+79262719630» <sip:89262719630@19.2.41.21>;party=calling;screen=yes;privacy=off

v=0
o=FreeSWITCH 1453088024 1453088025 IN IP4 19.2.41.21
s=FreeSWITCH
c=IN IP4 19.2.41.21
t=0 0
m=audio 28812 RTP/AVP 8 0 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off — — — —
a=ptime:30
m=audio 28812 RTP/AVP 8 0 18 101
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off — — — —
a=ptime:20
<————->
— (18 headers 16 lines) —
Sending to 19.2.41.21:5060 (NAT)
Using INVITE request as basis request — 337f7865-387a-1234-798b-002590e5052c
Found peer ‘Mo_010’ for ‘89262719630’ from 19.2.41.21:5060
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
Found RTP audio format 8
Found RTP audio format 0
Found RTP audio format 101
Found audio description format telephone-event for ID 101

Источник

Я настраиваю пользователей «100» и «200», я пытаюсь использовать проект sipml5.

Сервер записывает двух пользователей, пользователя «100» на этом онлайн-Linphone.

Пользователь «200» записывает в sipml5, но для выполнения вызова он показывает эту ошибку:

`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.invitecontext.mediahandler | 4pk6rpr5p1mhfts149uk9t8l09v01c | acquiring local media`

`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.invitecontext.mediahandler | 4pk6rpr5p1mhfts149uk9t8l09v01c | acquired local media streams`

`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.invitecontext.mediahandler | 4pk6rpr5p1mhfts149uk9t8l09v01c | ICE candidate received: candidate:3879386089 1 udp 2122260223 172.16.1.209 60702 typ host generation 0`

`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.invitecontext.mediahandler | 4pk6rpr5p1mhfts149uk9t8l09v01c | ICE candidate received: candidate:3879386089 2 udp 2122260222 172.16.1.209 45410 typ host generation 0`

`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.invitecontext.mediahandler | 4pk6rpr5p1mhfts149uk9t8l09v01c | ICE candidate received: candidate:2847491865 1 tcp 1518280447 172.16.1.209 0 typ host tcptype active generation 0`

`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.invitecontext.mediahandler | 4pk6rpr5p1mhfts149uk9t8l09v01c | ICE candidate received: candidate:2847491865 2 tcp 1518280446 172.16.1.209 0 typ host tcptype active generation 0`

`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.invitecontext.mediahandler | 4pk6rpr5p1mhfts149uk9t8l09v01c | ICE candidate received: candidate:288014909 2 udp 1686052606 189.35.140.74 62060 typ srflx raddr 172.16.1.209 rport 45410 generation 0`

`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.invitecontext.mediahandler | 4pk6rpr5p1mhfts149uk9t8l09v01c | ICE candidate received: candidate:288014909 1 udp 1686052607 189.35.140.74 56282 typ srflx raddr 172.16.1.209 rport 60702 generation 0`

`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.transport | sending WebSocket message:`

`INVITE sip:100@172.16.1.203 SIP/2.0<br>
Via: SIP/2.0/WS cam6bslroe6a.invalid;branch=z9hG4bK7117302
Max-Forwards: 70
To: <sip:100@172.16.1.203>
From: "200" <sip:200@172.16.1.203>;tag=ur4c0oov9u
Call-ID: 4pk6rpr5p1mhfts149uk
CSeq: 7760 INVITE
Contact: <sip:040c805k@cam6bslroe6a.invalid;transport=ws;ob>
Allow: ACK,CANCEL,BYE,OPTIONS,INFO,NOTIFY,INVITE
Content-Type: application/sdp
Supported: outbound
User-Agent: SIP.js/0.7.2
Content-Length: 1777
`

`v=0
o=- 6908994037829104915 2 IN IP4 127.0.0.1
s=-
t=0 0
a=group:BUNDLE audio
a=msid-semantic: WMS Mdtr3XiGc3ZYftGDwxeYDfspP9DqQwSRd17N
m=audio 56282 UDP/TLS/RTP/SAVPF 111 103 104 9 0 8 106 105 13 126
c=IN IP4 189.35.140.74
a=rtcp:62060 IN IP4 189.35.140.74
a=candidate:3879386089 1 udp 2122260223 172.16.1.209 60702 typ host generation 0
a=candidate:3879386089 2 udp 2122260222 172.16.1.209 45410 typ host generation 0
a=candidate:2847491865 1 tcp 1518280447 172.16.1.209 0 typ host tcptype active generation 0
a=candidate:2847491865 2 tcp 1518280446 172.16.1.209 0 typ host tcptype active generation 0
a=candidate:288014909 2 udp 1686052606 189.35.140.74 62060 typ srflx raddr 172.16.1.209 rport 45410 generation 0
a=candidate:288014909 1 udp 1686052607 189.35.140.74 56282 typ srflx raddr 172.16.1.209 rport 60702 generation 0
a=ice-ufrag:FK6gzTOP0l95UM39
a=ice-pwd:1ehRZElxNwmCq6mQpetD78w+
a=fingerprint:sha-256 2C:93:D5:54:53:96:34:18:DA:A6:3C:1A:59:5A:32:6B:3E:70:79:78:85:AC:AA:26:8F:D6:0B:5E:9C:DB:4A:8C
a=setup:actpass
a=mid:audio
a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level
a=extmap:3 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=sendrecv
a=rtcp-mux
a=rtpmap:111 opus/48000/2
a=fmtp:111 minptime=10; useinbandfec=1
a=rtpmap:103 ISAC/16000
a=rtpmap:104 ISAC/32000
a=rtpmap:9 G722/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:106 CN/32000
a=rtpmap:105 CN/16000
a=rtpmap:13 CN/8000
a=rtpmap:126 telephone-event/8000
a=maxptime:60
a=ssrc:2011742822 cname:/+L6wPj8ErBqYw3L
a=ssrc:2011742822 msid:Mdtr3XiGc3ZYftGDwxeYDfspP9DqQwSRd17N dce80b6d-4fed-4409-af6c-275e470a0d73
a=ssrc:2011742822 mslabel:Mdtr3XiGc3ZYftGDwxeYDfspP9DqQwSRd17N
a=ssrc:2011742822 label:dce80b6d-4fed-4409-af6c-275e470a0d73`


`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.transport | received WebSocket text message:`

`SIP/2.0 401 Unauthorized
Via: SIP/2.0/WS cam6bslroe6a.invalid;branch=z9hG4bK7117302;received=172.16.1.209
From: "200" <sip:200@172.16.1.203>;tag=ur4c0oov9u
To: <sip:100@172.16.1.203>;tag=as5f539d65
Call-ID: 4pk6rpr5p1mhfts149uk
CSeq: 7760 INVITE
Server: Asterisk PBX 13.6.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="26be674c"
Content-Length: 0`



`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.transport | sending WebSocket message:`

`ACK sip:100@172.16.1.203 SIP/2.0
Via: SIP/2.0/WS cam6bslroe6a.invalid;branch=z9hG4bK7117302
To: <sip:100@172.16.1.203>;tag=as5f539d65
From: "200" <sip:200@172.16.1.203>;tag=ur4c0oov9u
Call-ID: 4pk6rpr5p1mhfts149uk
Content-Length: 0
CSeq: 7760 ACK`



`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.transport | sending WebSocket message:`

`INVITE sip:100@172.16.1.203 SIP/2.0
Via: SIP/2.0/WS cam6bslroe6a.invalid;branch=z9hG4bK4757152
Max-Forwards: 70
To: <sip:100@172.16.1.203>
From: "200" <sip:200@172.16.1.203>;tag=ur4c0oov9u
Call-ID: 4pk6rpr5p1mhfts149uk
CSeq: 7761 INVITE
Authorization: Digest algorithm=MD5, username="200", realm="asterisk", nonce="26be674c", uri="sip:100@172.16.1.203", response="7c400e75f1605a4893b99438a18b9560"
Contact: <sip:040c805k@cam6bslroe6a.invalid;transport=ws;ob>
Allow: ACK,CANCEL,BYE,OPTIONS,INFO,NOTIFY,INVITE
Content-Type: application/sdp
Supported: outbound
User-Agent: SIP.js/0.7.2
Content-Length: 1777`

`v=0
o=- 6908994037829104915 2 IN IP4 127.0.0.1
s=-
t=0 0
a=group:BUNDLE audio
a=msid-semantic: WMS Mdtr3XiGc3ZYftGDwxeYDfspP9DqQwSRd17N
m=audio 56282 UDP/TLS/RTP/SAVPF 111 103 104 9 0 8 106 105 13 126
c=IN IP4 189.35.140.74
a=rtcp:62060 IN IP4 189.35.140.74
a=candidate:3879386089 1 udp 2122260223 172.16.1.209 60702 typ host generation 0
a=candidate:3879386089 2 udp 2122260222 172.16.1.209 45410 typ host generation 0
a=candidate:2847491865 1 tcp 1518280447 172.16.1.209 0 typ host tcptype active generation 0
a=candidate:2847491865 2 tcp 1518280446 172.16.1.209 0 typ host tcptype active generation 0
a=candidate:288014909 2 udp 1686052606 189.35.140.74 62060 typ srflx raddr 172.16.1.209 rport 45410 generation 0
a=candidate:288014909 1 udp 1686052607 189.35.140.74 56282 typ srflx raddr 172.16.1.209 rport 60702 generation 0
a=ice-ufrag:FK6gzTOP0l95UM39
a=ice-pwd:1ehRZElxNwmCq6mQpetD78w+
a=fingerprint:sha-256 2C:93:D5:54:53:96:34:18:DA:A6:3C:1A:59:5A:32:6B:3E:70:79:78:85:AC:AA:26:8F:D6:0B:5E:9C:DB:4A:8C
a=setup:actpass
a=mid:audio
a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level
a=extmap:3 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=sendrecv
a=rtcp-mux
a=rtpmap:111 opus/48000/2
a=fmtp:111 minptime=10; useinbandfec=1
a=rtpmap:103 ISAC/16000
a=rtpmap:104 ISAC/32000
a=rtpmap:9 G722/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:106 CN/32000
a=rtpmap:105 CN/16000
a=rtpmap:13 CN/8000
a=rtpmap:126 telephone-event/8000
a=maxptime:60
a=ssrc:2011742822 cname:/+L6wPj8ErBqYw3L
a=ssrc:2011742822 msid:Mdtr3XiGc3ZYftGDwxeYDfspP9DqQwSRd17N dce80b6d-4fed-4409-af6c-275e470a0d73
a=ssrc:2011742822 mslabel:Mdtr3XiGc3ZYftGDwxeYDfspP9DqQwSRd17N
a=ssrc:2011742822 label:dce80b6d-4fed-4409-af6c-275e470a0d73`


`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.transaction.ict | z9hG4bK7117302 | Timer D expired for INVITE client transaction z9hG4bK7117302
Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.transport | received WebSocket text message:`

`SIP/2.0 488 Not acceptable here
Via: SIP/2.0/WS cam6bslroe6a.invalid;branch=z9hG4bK4757152;received=172.16.1.209
From: "200" <sip:200@172.16.1.203>;tag=ur4c0oov9u
To: <sip:100@172.16.1.203>;tag=as5f539d65
Call-ID: 4pk6rpr5p1mhfts149uk
CSeq: 7761 INVITE
Server: Asterisk PBX 13.6.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0`



`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.transport | sending WebSocket message:`

`ACK sip:100@172.16.1.203 SIP/2.0
Via: SIP/2.0/WS cam6bslroe6a.invalid;branch=z9hG4bK4757152
To: <sip:100@172.16.1.203>;tag=as5f539d65
From: "200" <sip:200@172.16.1.203>;tag=ur4c0oov9u
Call-ID: 4pk6rpr5p1mhfts149uk
Content-Length: 0
CSeq: 7761 ACK`



    `Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.inviteclientcontext | closing INVITE session 4pk6rpr5p1mhfts149uk9t8l09v01c`

    `Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.invitecontext.mediahandler | 4pk6rpr5p1mhfts149uk9t8l09v01c | closing PeerConnection`

    `Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.transaction.ict | z9hG4bK4757152 | Timer D expired for INVITE client transaction z9hG4bK4757152`

2 ответа

Лучший ответ

488 означает отсутствие совместимости с носителями.

Есть несколько причин для приобретения 488: самая распространенная, у вас нет общих кодеков. Сначала убедитесь, что на вашей звездочке поддерживаются и настроены опусы.

С совместимостью webrtc проблема часто связана с использованием:

UDP/TLS/RTP/SAVPF

Вместо того

RTP/SAVPF

То есть: стандарты webrtc / ietf не полностью определены и продолжают действовать.

Вы можете проверить возможный повторяющийся вопрос / ответ здесь: Freeswitch и webRTC: медиа отклонено с помощью 488

Community
23 Май 2017 в 10:29

У меня возникает эта проблема, когда я получаю телефонные звонки с использованием SRTP. Телефонные звонки падают на телефон с 488. Я могу без проблем совершать исходящие зашифрованные звонки.

sgtcoder
19 Ноя 2019 в 00:29

Источник

From Wikipedia, the free encyclopedia

The Session Initiation Protocol (SIP) is a signalling protocol used for controlling communication sessions such as Voice over IP telephone calls. SIP is based on request/response transactions, in a similar manner to the Hypertext Transfer Protocol (HTTP). Each transaction consists of a SIP request (which will be one of several request methods), and at least one response.^[1]^: p11

SIP requests and responses may be generated by any SIP user agent; user agents are divided into clients (UACs), which initiate requests, and servers (UASes), which respond to them.^[1]^: §8 A single user agent may act as both UAC and UAS for different transactions:^[1]^: p26 for example, a SIP phone is a user agent that will be a UAC when making a call, and a UAS when receiving one. Additionally, some devices will act as both UAC and UAS for a single transaction; these are called Back-to-Back User Agents (B2BUAs).^[1]^: p20

SIP responses specify a three-digit integer response code, which is one of a number of defined codes that detail the status of the request. These codes are grouped according to their first digit as «provisional», «success», «redirection», «client error», «server error» or «global failure» codes, corresponding to a first digit of 1–6; these are expressed as, for example, «1xx» for provisional responses with a code of 100–199.^[1]^: §7.2 The SIP response codes are consistent with the HTTP response codes, although not all HTTP response codes are valid in SIP.^[1]^: §21

SIP responses also specify a «reason phrase», and a default reason phrase is defined with each response code.^[1]^: §7.2 These reason phrases can be varied, however, such as to provide additional information^[1]^{: §21.4.18} or to provide the text in a different language.^[1]^: §20.3

The SIP response codes and corresponding reason phrases were initially defined in RFC 3261.^[1] That RFC also defines a SIP Parameters Internet Assigned Numbers Authority (IANA) registry to allow other RFC to provide more response codes.^[1]^: §27^[2]

This list includes all the SIP response codes defined in IETF RFCs and registered in the SIP Parameters IANA registry as of 27 January 2023. This list also includes SIP response codes defined in obsolete SIP RFCs (specifically, RFC 2543), which are therefore not registered with the IANA; these are explicitly noted as such.

SIP responses may also include an optional Warning header, containing additional details about the response. The Warning contains a separate three-digit code followed by text with more details about the warning.^[1]^: §20.43 The current list of official warnings is registered in the SIP Parameters IANA registry.

1xx—Provisional Responses[edit]

100 Trying: Extended search being performed may take a significant time so a forking proxy must send a 100 Trying response.^[1]^: §21.1.1
180 Ringing: Destination user agent received INVITE, and is alerting user of call.^[1]^: §21.1.2
181 Call is Being Forwarded: Servers can optionally send this response to indicate a call is being forwarded.^[1]^: §21.1.3
182 Queued: 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.^[1]^: §21.1.4
183 Session Progress: This response may be used to send extra information for a call which is still being set up.^[1]^: §21.1.5
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.^[3]

2xx—Successful Responses[edit]

200 OK: Indicates that the request was successful.^[1]^: §21.2.1
202 Accepted: Indicates that the request has been accepted for processing, but the processing has not been completed.^[4]^: §7.3.1^[5] Deprecated.^[6]^: §8.3.1^[2]
204 No Notification: Indicates the request was successful, but the corresponding response will not be received.^[7]

3xx—Redirection Responses[edit]

300 Multiple Choices: 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.^[1]^: §21.3.1
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.^[1]^: §21.3.2
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.^[1]^: §21.3.3
305 Use Proxy: The Contact field details a proxy that must be used to access the requested destination.^[1]^: §21.3.4
380 Alternative Service: The call failed, but alternatives are detailed in the message body.^[1]^: §21.3.5

4xx—Client Failure Responses[edit]

400 Bad Request: The request could not be understood due to malformed syntax.^[1]^: §21.4.1
401 Unauthorized: The request requires user authentication. This response is issued by UASs and registrars.^[1]^: §21.4.2
402 Payment Required: Reserved for future use.^[1]^: §21.4.3
403 Forbidden: The server understood the request, but is refusing to fulfill it.^[1]^: §21.4.4 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.^[1]^: §21.4.5
405 Method Not Allowed: The method specified in the Request-Line is understood, but not allowed for the address identified by the Request-URI.^[1]^: §21.4.6
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.^[1]^: §21.4.7
407 Proxy Authentication Required: The request requires user authentication. This response is issued by proxies.^[1]^: §21.4.8
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.^[1]^: §21.4.9
409 Conflict: User already registered.^[8]^: §7.4.10 Deprecated by omission from later RFCs^[1] and by non-registration with the IANA.^[2]
410 Gone: The user existed once, but is not available here any more.^[1]^{: §21.4.10}
411 Length Required: The server will not accept the request without a valid Content-Length.^[8]^: §7.4.12 Deprecated by omission from later RFCs^[1] and by non-registration with the IANA.^[2]
412 Conditional Request Failed: The given precondition has not been met.^[9]
413 Request Entity Too Large: Request body too large.^[1]^{: §21.4.11}
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.^[1]^{: §21.4.12}
415 Unsupported Media Type: Request body in a format not supported.^[1]^{: §21.4.13}
416 Unsupported URI Scheme: Request-URI is unknown to the server.^[1]^{: §21.4.14}
417 Unknown Resource-Priority: There was a resource-priority option tag, but no Resource-Priority header.^[10]
420 Bad Extension: Bad SIP Protocol Extension used, not understood by the server.^[1]^{: §21.4.15}
421 Extension Required: The server needs a specific extension not listed in the Supported header.^[1]^{: §21.4.16}
422 Session Interval Too Small: The received request contains a Session-Expires header field with a duration below the minimum timer.^[11]
423 Interval Too Brief: Expiration time of the resource is too short.^[1]^{: §21.4.17}
424 Bad Location Information: The request’s location content was malformed or otherwise unsatisfactory.^[12]
425 Bad Alert Message: The server rejected a non-interactive emergency call, indicating that the request was malformed enough that no reasonable emergency response to the alert can be determined.^[13]
428 Use Identity Header: The server policy requires an Identity header, and one has not been provided.^[14]^: p11
429 Provide Referrer Identity: The server did not receive a valid Referred-By token on the request.^[15]
430 Flow Failed: 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).^[16]^: §11.5
433 Anonymity Disallowed: The request has been rejected because it was anonymous.^[17]
436 Bad Identity-Info: The request has an Identity-Info header, and the URI scheme in that header cannot be dereferenced.^[14]^: p11
437 Unsupported Certificate: The server was unable to validate a certificate for the domain that signed the request.^[14]^: p11
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.^[14]^: p12
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.^[16]^: §11.6
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.^[18]
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.^[19]
470 Consent Needed: The source of the request did not have the permission of the recipient to make such a request.^[20]
480 Temporarily Unavailable: Callee currently unavailable.^[1]^{: §21.4.18}
481 Call/Transaction Does Not Exist: Server received a request that does not match any dialog or transaction.^[1]^{: §21.4.19}
482 Loop Detected: Server has detected a loop.^[1]^{: §21.4.20}
483 Too Many Hops: Max-Forwards header has reached the value ‘0’.^[1]^{: §21.4.21}
484 Address Incomplete: Request-URI incomplete.^[1]^{: §21.4.22}
485 Ambiguous: Request-URI is ambiguous.^[1]^{: §21.4.23}
486 Busy Here: Callee is busy.^[1]^{: §21.4.24}
487 Request Terminated: Request has terminated by bye or cancel.^[1]^{: §21.4.25}
488 Not Acceptable Here: Some aspect of the session description or the Request-URI is not acceptable.^[1]^{: §21.4.26}
489 Bad Event: The server did not understand an event package specified in an Event header field.^[4]^: §7.3.2^[6]^: §8.3.2
491 Request Pending: Server has some pending request from the same dialog.^[1]^{: §21.4.27}
493 Undecipherable: Request contains an encrypted MIME body, which recipient can not decrypt.^[1]^{: §21.4.28}
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,^[21]^{: §§2.3.1–2.3.2} or a digest authentication challenge.^[21]^: §2.4

5xx—Server Failure Responses[edit]

500 Internal Server Error: The server could not fulfill the request due to some unexpected condition.^[1]^: §21.5.1
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.)^[1]^: §21.5.2
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.^[1]^: §21.5.3
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 reattempt its request.^[1]^: §21.5.4
504 Server Time-out: The server attempted to access another server in attempting to process the request, and did not receive a prompt response.^[1]^: §21.5.5
505 Version Not Supported: The SIP protocol version in the request is not supported by the server.^[1]^: §21.5.6
513 Message Too Large: The request message length is longer than the server can process.^[1]^: §21.5.7
555 Push Notification Service Not Supported: The server does not support the push notification service identified in a ‘pn-provider’ SIP URI parameter^[22]^: §14.2.1
580 Precondition Failure: The server is unable or unwilling to meet some constraints specified in the offer.^[23]

6xx—Global Failure Responses[edit]

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.^[1]^: §21.6.1

603 Decline: 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.^[1]^: §21.6.2 The response may indicate a better time to call in the Retry-After header field.

604 Does Not Exist Anywhere: The server has authoritative information that the requested user does not exist anywhere.^[1]^: §21.6.3

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.^[1]^: §21.6.4

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.^[24]

608 Rejected: An intermediary machine or process rejected the call attempt.^[25] This contrasts with the 607 (Unwanted) SIP response code in which a human, the called party, rejected the call. The intermediary rejecting the call should include a Call-Info header with «purpose» value «jwscard», with the jCard^[26] with contact details. The calling party can use this jCard if they want to dispute the rejection.

References[edit]

^ ^a ^b ^c ^d ^e ^f ^g ^h ⁱ ^j ^k ^l ^m ⁿ ^o ^p ^q ^r ^s ^t ^u ^v ^w ^x ^y ^z ^aa ^ab ^ac ^ad ^ae ^af ^ag ^ah ^ai ^aj ^ak ^al ^am ^an ^ao ^ap ^aq ^ar ^as ^at ^au ^av ^aw ^ax ^ay ^az ^ba ^bb ^bc ^bd ^be ^bf ^bg ^bh ^bi ^bj ^bk ^bl Rosenberg, Jonathan; Schulzrinne, Henning; Camarillo, Gonzalo; Johnston, Alan; Peterson, Jon; Sparks, Robert; Handley, Mark; Schooler, Eve (June 2002). SIP: Session Initiation Protocol. IETF. doi:10.17487/RFC3261. RFC 3261.
^ ^a ^b ^c ^d Roach, Adam; Jennings, Cullen; Peterson, Jon; Barnes, Mary (17 April 2013) [Created January 2002]. «Response Codes». Session Initiation Protocol (SIP) Parameters. IANA.
^ Holmberg, Christer (May 2011). Session Initiation Protocol (SIP) Response Code for Indication of Terminated Dialog. IETF. p. 1. Abstract. doi:10.17487/RFC6228. RFC 6228.
^ ^a ^b Roach, Adam B. (June 2002). Session Initiation Protocol (SIP)-Specific Event Notification. IETF. doi:10.17487/RFC3265. RFC 3265.
^ Fielding, Roy T.; Gettys, James; Mogul, Jeffrey C.; Nielsen, Henrik Frystyk; Masinter, Larry; Leach, Paul; Berners-Lee, Tim (June 1999). «202 Accepted». Hypertext Transfer Protocol — HTTP/1.1. IETF. sec. 10.2.3. doi:10.17487/RFC2616. RFC 2616.
^ ^a ^b Roach, Adam (July 2012). SIP-Specific Event Notification. IETF. doi:10.17487/RFC6665. RFC 6665.
^ Niemi, Aki (May 2010). «204 (No Notification) Response Code». In Willis, Dean (ed.). An Extension to Session Initiation Protocol (SIP) Events for Conditional Event Notification. IETF. sec. 7.1. doi:10.17487/RFC5839. RFC 5839.
^ ^a ^b Handley, Mark; Schulzrinne, Henning; Schooler, Eve; Rosenberg, Jonathan (March 1999). SIP: Session Initiation Protocol. IETF. doi:10.17487/RFC2543. RFC 2543.
^ Niemi, Aki, ed. (2004). ««412 Conditional Requset Failed» Response Code». Session Initiation Protocol (SIP) Extension for Event State Publication. IETF. sec. 11.2.1. doi:10.17487/RFC3903. RFC 3903.
^ Schulzrinne, Henning; Polk, James (February 2006). «No Known Namespace or Priority Value». Communications Resource Priority for the Session Initiation Protocol (SIP). IETF. sec. 4.6.2. doi:10.17487/RFC4412. RFC 4412.
^ Donovan, Steve; Rosenberg, Jonathan (April 2005). «422 Response Code Definition». Session Timers in the Session Initiation Protocol (SIP). IETF. sec. 6. doi:10.17487/RFC4028. RFC 4028.
^ Polk, James; Rosen, Brian; Peterson, Jon (December 2011). «424 (Bad Location Information) Response Code». Location Conveyance for the Session Initiation Protocol. IETF. sec. 4.3. doi:10.17487/RFC6442. RFC 6442.
^ Rosen, Brian; Schulzrinne, Henning; Tschofenig, Hannes; Gellens, Randall (September 2020). «425 (Bad Alert Message) Response Code». Non-interactive Emergency Calls. IETF. sec. 5.1. doi:10.17487/RFC8876. RFC 8876.
^ ^a ^b ^c ^d Peterson, Jon; Jennings, Cullen (August 2006). Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP). IETF. doi:10.17487/RFC4474. RFC 4474.
^ Sparks, Robert J. (September 2004). «The 429 Provide Referrer Identity Error Response». The Session Initiation Protocol (SIP) Referred-By Mechanism. IETF. sec. 5. doi:10.17487/RFC3892. RFC 3892.
^ ^a ^b Jennings, Cullen; Mahy, Rohan; Audet, Francois, eds. (October 2009). Managing Client-Initiated Connections in the Session Initiation Protocol (SIP). IETF. doi:10.17487/RFC5626. RFC 5626.
^ Rosenberg, Jonathan (December 2007). «433 (Anonymity Disallowed) Definition». Rejecting Anonymous Requests in the Session Initiation Protocol (SIP). IETF. sec. 5. doi:10.17487/RFC5079. RFC 5079.
^ Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies. IETF. December 2008. doi:10.17487/RFC5393. RFC 5393.
^ Session Initiation Protocol (SIP) INFO Method and Package Framework. IETF. January 2011. doi:10.17487/RFC6086. RFC 6086.
^ Rosenberg, Jonathan; Willis, Dean (October 2008). «Definition of the 470 Response Code». In Camarillo, Gonzalo (ed.). A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP). IETF. sec. 5.9.2. doi:10.17487/RFC5360. RFC 5360.
^ ^a ^b Arkko, Jari; Torvinen, Vesa; Camarillo, Gonzalo; Niemi, Aki; Haukka, Tao (January 2003). Security Mechanism Agreement for the Session Initiation Protocol (SIP). IETF. doi:10.17487/RFC3329. RFC 3329.
^ Push Notification with the Session Initiation Protocol (SIP). IETF. May 2019. doi:10.17487/RFC8599. RFC 8599.
^ Rosenberg, Jonathan (October 2002). «Refusing an offer». In Camarillo, Gonzalo; Marshall, Bill (eds.). Integration of Resource Management and Session Initiation Protocol (SIP). IETF. sec. 8. doi:10.17487/RFC3312. RFC 3312.
^ A SIP Response Code for Unwanted Calls. IETF. July 2017. doi:10.17487/RFC8197. RFC 8197.
^ A Session Initiation Protocol (SIP) Response Code for Rejected Calls. IETF. December 2019. doi:10.17487/RFC8688. RFC 8688.
^ RFC 7095

External links[edit]

Mapping SIP Error Messages to DSS1 codes at the Wayback Machine (archived 2021-04-12)
Session Initiation Protocol (SIP) Parameters Contains a registry of different SIP parameters, including response codes

Источник