Sip error 408

 This error means that the phone did not receive a reply from the server(or there is no connectivity with it) and is common with new installations or when changing the network connectivity, i.e. being it 3G/4G or WiFi network.

Check the routing device/ firewall settings

Common reasons include:

• There is typo (or an extra space) in the host/domain name:

• There’s an issue with your internet connectivity
  

Please open your browser and check  if you can visit a random website. If not, you have to fix your internet connectivity issue(s) first. If you are not able to do so yourself, we would suggest contacting your ITSP (internet service provider)

• Your network provider is blocking VoIP calls. (this happens mostly in middle eastern countries)
  •  contact your internet provider and ask if they allow VoIP calls on their network;
  • Use TLS encryption for the SIP signalling, especially when combined with a server running SIP on port 443.(this requires server side support for TLS);
  • use RTP encryption for media;
  • use a third party VPN service;

• Your router is intercepting and changing the packets as they pass through

Be sure to Disable SIP ALG on the router. A list with problematic routers and solutions can be found here http://www.voip-info.org/wiki/view/Routers+SIP+ALG

More detailed instructions:

Zyxel routers: 

Netgear routers:

• A firewall on your device is blocking the traffic

• A NAT router in between the softphone and the server is causing some packets to be dropped

Zoiper has a few settings to trick the server into sending the packets to a different IP address or port.

Please try different settings combinations of STUN (enabled or disabled) or rport for signalling (enabled or disabled).

STUN ON — Rport OFF

STUN ON — Rport ON

STUN OFF — Rport OFF

STUN OFF — Rport ON

Please note that:

A combination that works on one WiFi access point or 3G/4G network might not work on another.

A combination that works one WiFi or cellular network for a specific VoIP server might not work for another one.

If the above fails, please contact your provider or PBX administrator might be able to tweak a server side setting to make things work.

• The PBX or SIP Provider  you are trying to connect to is currently down.

Please contact your provider for further assistance;

• Your PBX is on an internal network, but Zoiper is not on the same network and no VPN is running.

Please make sure Zoiper and the PBX or on the same network or setup a VPN  between the device running Zoiper and your PBX. Please consult with your system administrator for additional help.

Check also if the needed ports by Zoiper are not blocked in your firewall/ routing device.The default ports used by Zoiper are:

SIP port is random above 32000

IAX port is 4569 UDP

RTP port is 8000 and above UDP

Default STUN vallues:

Server hostname /IP :stun.zoiper.com

Port : 3478 UDP/TCP

Refresh period : 30

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
Соединение с сервером было установлено. Отдельные параметры, такие как тип запрашиваемой информации, полоса пропускания, вид адресации не доступны.

Signalling protocols are essential to some of the most commonly used applications on the internet. For example, they’re integral to real-time voice, video, and text-based messaging services.

But if you’re using some of these services, you might run into problems from time to time. For example, you might get a SIP Error 408 message.

If you get a SIP Error 408, it means that the request timed out before it could find the user. That could’ve happened for a few reasons. There might be an issue with your internet connection. Or maybe a network provider is blocking the app that you’re trying to use. You may also want to try reconfiguring your firewall to fix the issue.

What is SIP?

First, let’s make sure we’re all starting on the same page. SIP is an acronym that stands for Session Initiation Protocol. This is a signaling protocol that’s used for initiating, maintaining, and termination real-time sessions. SIP is used for voice, video, and messaging applications, among other purposes.

SIP works in combination with other tools to specify and carry the session media. It was designed to act as the underlying transport layer protocol and to be used with User Datagram Protocol (UDP).

If you’re not a technical person, don’t worry. You don’t need to know all of this to fix a SIP Error message. It’s just worth having the background so that you know why you need SIP to use some of your applications.

What are the major types of SIP codes?

There are quite a few different types of SIP codes that you may see while using various real-time messaging applications. These are split into categories based on the first number in the code.

For example, a code that starts with 1 conveys a provisional response. This is used to show that an attempt is being made to form a connection. For example, code 100 means “Trying” while code 180 means “Ringing”.

Codes beginning with a 2 indicate a successful response while codes beginning with a 3 show a redirection response. This means that the connection isn’t being serviced through your intended channel. This could be happening for a few different reasons, such as a temporary move or a proxy requirement.

SIP codes that begin with 4 indicate a client failure response. So you know that if you see a 4 at the start of your code, something went wrong. The numbers that follow the 4 will tell you the specific reason why your request failed.

Codes that begin with 5 and 6 also indicate connection failures. Codes starting with 5 are for server failure responses. Codes beginning with 6 are for global failure responses.

What is a SIP error 408?

SIP Error 408 stands for Request Timeout. This means that the application couldn’t find the user in time. There could be a few different reasons for this. Here are some of the main causes of a SIP Error 408 message:

• Address entered incorrectly
• Your internet isn’t working properly
• Your network provider is blocking the application you want to use
• There’s a firewall on your device that’s blocking the connection
• The application that you’re using is currently experiencing technical difficulties

The fix for your SIP error 408 will depend on what’s causing the problem. For example, if you’ve entered the address incorrectly, you’ll need to correct the mistake to resolve the error.

Alternatively, it’s possible that your internet is causing the problem. In that scenario, you would need to repair your general internet connection to fix the error message.

It’s also possible that the problem is stemming from your network provider blocking the connection. If this is happening, you may want to try using a VPN. VPNs will disguise your internet activity, which can often get you around problems like these.

You might also want to try reconfiguring your device’s firewall. Sometimes this will block the connection from taking place, causing a SIP Error 408. You may need to create an exception in your firewall for the service you’re using.

Finally, it’s also possible that the problem isn’t on your end at all. If you’ve tried all of these solutions and none work, it might just be the application’s fault. In that case, you might want to reach out to them to see when they will fix the issue.

What is a provisional response in SIP?

A provisional response is one of the main messages that you can see while using SIP. The concept of a provisional response is pretty straightforward.

Essentially, this just means that the application you’re using is trying to form the connection. There are several different specific SIP messages that you might see here. Here’s what might be happening when you see a provisional response:

• SIP Code 100 – Trying
• SIP Code 180 – Ringing
• SIP 181 – Call is Being Forwarded
• SIP Code 182 – Queued
• SIP Code 183 – Session Progress
• SIP Code 190 – Early Dialog Terminated

What is SIP call flow?

SIP call flow is what happens to connect two SIP devices or applications. For example, you might be using an internet phone service to contact a friend. When you call them, your phone needs to connect to the other phone before you can speak with your friend.

This is what’s known as SIP call flow. It’s the communication between two SIP devices that lets you connect with someone on the other end. It’s a technical communication that occurs between two devices. One device sends out a SIP request and the other one responds to it.

What is a prack in SIP?

PRACK might sound pretty complicated if you’re not familiar with the term. But it’s actually just an acronym that sounds for Provisional Response Acknowledgement.

This fits into the discussion in a previous section about provisional SIP responses. Essentially, a PRACK is what occurs when one device acknowledges a connection attempt from another.

It’s a broader term that can be used to describe any provision response that a SIP device might have. For example, if you got a 180 Ringing message, that would be a PRACK. A 100 Trying message would be another example of a PRACK.

What is 180 ringing in SIP?

You might get a 180 Ringing message while using a SIP device sometimes. This is exactly what it sounds like. It’s basically the same as what happens when a telephone rings.

Essentially, a 180 Ringing message is a notification that your device is getting an incoming connection request from another. Your SIP device will notify you, through a ring, a message, or some other notification of this connection attempt.

What is the different between 180 ringing and 183 Session Progress?

This can be a bit complicated so let’s take a closer look at precisely what each SIP message means. A 180 Ringing message says that the UA receiving the invite is attempting to alert the user. This may initiate a ringing or some other notification on the receiver’s end.

A 183 Session Progress message is used to convey information about the progress of a call attempt. This is used for calls that are not otherwise classified as something else.

There’s one major difference between these two messages that is worth knowing. Essentially, 180 Ringing tells the UA to create a local dial-tone. The 183 Session Progress message allows for both regional ring-back and carrier announcements as well.

What is 487 request terminated?

The 487 Request Terminated is another message that you might get while using a SIP device. It means that a previous request was terminated. It could be used to show a request that’s been terminated by the user or by an action taken by the application.

This is a response code that will get sent to the client when the client sends a cancel request. It’s something that you might want to keep in mind if you’re someone who uses SIP devices fairly often.

It’s important to note, this isn’t a technical problem. When you see a 487 message, it doesn’t mean that your application isn’t working correctly. It just means that the person you tried to contact declined the request. They could’ve done that on their own or the application they’re using could’ve done it automatically for them.

Is 180 ringing mandatory?

No, 180 ringing is not mandatory. A connection can be formed between two SIP devices without one. With that in mind, the A-side should be prepared to receive a 200 code as the first response. Or, another response, such as a 400 error code could also be the first response between two SIP devices.

What is early media in SIP?

Early media is the ability of two different devices to communicate before a call is actually established. More specifically this occurs when media begins to flow before the call is actually connected.

These channels are used to provide the ringtone that a caller hears. They’re usually not generated by the caller’s endpoint or through any other queuing services. For example, hold music isn’t included in SIP early media.

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]

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

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