VoIP & SIP error codes
VoIP & SIP faults are reported as a SIP response code. Find yours below, or search for it directly.
Client error (4xx)
- SIP 403ForbiddenYour credentials were accepted but the action was not allowed. A 403 means the system knows who you…
- SIP 480Temporarily UnavailableThe extension exists but nothing is available to ring. On a hosted system this nearly always means the…
- SIP 401UnauthorizedA challenge for credentials, not a failure. One 401 followed by a successful registration is how SIP authentication…
- SIP 404Not FoundThe number or extension you dialled does not exist on the system that answered. On a business phone…
- SIP 408Request TimeoutNo reply arrived before the timer expired. A 408 is a statement that signalling went unanswered, so it…
- SIP 488Not Acceptable HereThe call was acceptable but the audio arrangement was not. A 488 is a media negotiation failure, so…
- SIP 481Call/Transaction Does Not ExistA message arrived for a call the receiving system no longer recognises. It is the signature of SIP…
- SIP 407Proxy Authentication RequiredA proxy in the call path wants credentials before it will route the call. Like a 401 it…
- SIP 486Busy HereThe person you called is busy on this device. It is a healthy response rather than a fault,…
- SIP 487Request TerminatedThe call attempt was cancelled before anyone answered, usually because the caller hung up or because another phone…
- SIP 483Too Many HopsThe call was passed along so many times that a safety counter ran out, which almost always means…
- SIP 484Address IncompleteThe number looks incomplete to the system handling it. On a business phone system that normally means the…
- SIP 400Bad RequestThe request was malformed. Very little SIP equipment sends genuinely broken messages, so when a 400 appears the…
- SIP 415Unsupported Media TypeThe receiving system does not support the format of the message body it was sent. In voice terms…
- SIP 433Anonymity DisallowedThe recipient refuses calls that withhold their number. If your outbound calls are being rejected with this, the…
- SIP 423Interval Too BriefThe handset asked to register for a shorter period than the server allows. It is a straightforward configuration…
- SIP 491Request PendingBoth ends tried to renegotiate the same call at once, so one was asked to wait. It is…
- SIP 405Method Not AllowedThe far end recognises the address but will not accept that kind of request. In practice this shows…
- SIP 420Bad ExtensionYour device insisted on a SIP extension the far end does not understand. It is a negotiation mismatch…
- SIP 482Loop DetectedA server spotted that it had already handled this call and stopped it going round again. Like a…
- SIP 410GoneThe number or extension existed once and has deliberately been withdrawn. It is a more informative version of…
- SIP 421Extension RequiredThe mirror image of a 420: the server needs an extension your device did not offer, and names…
Server error (5xx)
- SIP 503Service UnavailableA server in the path is temporarily unable to handle the call. On a hosted system this most…
- SIP 500Server Internal ErrorA server hit an unexpected internal condition. It is a genuine fault rather than a policy decision, and…
- SIP 504Server Time-outA server did reply, to tell you it could not get an answer from something further along. Unlike…
- SIP 502Bad GatewayA proxy passed your call on and got back something it could not use. It points at the…
- SIP 501Not ImplementedThe server does not support the thing you asked it to do at all. Unlike a 405, which…
Global failure (6xx)
- SIP 603DeclineThe call was actively declined rather than failing. Someone or something chose to reject it, which on outbound…
- SIP 607UnwantedThe recipient marked the call as unwanted. For a legitimate business making outbound calls this is a reputation…
- SIP 608RejectedA network in the middle blocked the call before it reached the recipient, judging it unwanted. Unlike a…
- SIP 604Does Not Exist AnywhereThe number does not exist anywhere, not just on the system that answered. That usually means the number…
- SIP 600Busy EverywhereThe person you called is busy on every device they have. Unlike a 486, which refuses at one…
- SIP 606Not AcceptableThe session as described is not acceptable anywhere for that user. It is the global counterpart of a…
Redirection (3xx)
- SIP 302Moved TemporarilyThe call is being sent somewhere else, and the response says where. This is how call forwarding works,…
- SIP 380Alternative ServiceThe call did not succeed as asked, but an alternative is offered. In UK deployments this most often…
- SIP 301Moved PermanentlyThe address has moved for good, and the response gives the new one. Unlike a 302, which is…
Provisional (1xx)
- SIP 100TryingNot an error. It confirms your request was received and is being worked on, which stops the sending…
- SIP 180RingingNot an error. The destination is ringing. It is useful diagnostically because it proves the call reached a…
- SIP 183Session ProgressAudio is being sent before the call is answered. This is how you hear a network announcement, a…
Success (2xx)
Every other SIP response code
These are the remaining codes in the official registry. They are extension or rarely-used codes that we have not written up, so they are listed here for reference with the document that defines each one.
| Code | Official name | Defined in |
|---|---|---|
| SIP 181 | Call Is Being Forwarded | RFC 3261 section 21.1.3 |
| SIP 182 | Queued | RFC 3261 section 21.1.4 |
| SIP 199 | Early Dialog Terminated | RFC 6228 |
| SIP 202 | Accepted | RFC 6665 |
| SIP 204 | No Notification | RFC 5839 |
| SIP 300 | Multiple Choices | RFC 3261 section 21.3.1 |
| SIP 305 | Use Proxy | RFC 3261 section 21.3.4 |
| SIP 402 | Payment Required | RFC 3261 section 21.4.3 |
| SIP 406 | Not Acceptable | RFC 3261 section 21.4.7 |
| SIP 412 | Conditional Request Failed | RFC 3903 |
| SIP 413 | Request Entity Too Large | RFC 3261 section 21.4.11 |
| SIP 414 | Request-URI Too Long | RFC 3261 section 21.4.12 |
| SIP 416 | Unsupported URI Scheme | RFC 3261 section 21.4.14 |
| SIP 417 | Unknown Resource-Priority | RFC 4412 |
| SIP 422 | Session Interval Too Small | RFC 4028 |
| SIP 424 | Bad Location Information | RFC 6442 |
| SIP 425 | Bad Alert Message | RFC 8876 |
| SIP 428 | Use Identity Header | RFC 8224 |
| SIP 429 | Provide Referrer Identity | RFC 3892 |
| SIP 430 | Flow Failed | RFC 5626 |
| SIP 436 | Bad Identity Info | RFC 8224 |
| SIP 437 | Unsupported Credential | RFC 8224 |
| SIP 438 | Invalid Identity Header | RFC 8224 |
| SIP 439 | First Hop Lacks Outbound Support | RFC 5626 |
| SIP 440 | Max-Breadth Exceeded | RFC 5393 |
| SIP 469 | Bad Info Package | RFC 6086 |
| SIP 470 | Consent Needed | RFC 5360 |
| SIP 485 | Ambiguous | RFC 3261 section 21.4.23 |
| SIP 489 | Bad Event | RFC 6665 |
| SIP 493 | Undecipherable | RFC 3261 section 21.4.28 |
| SIP 494 | Security Agreement Required | RFC 3329 |
| SIP 505 | Version Not Supported | RFC 3261 section 21.5.6 |
| SIP 513 | Message Too Large | RFC 3261 section 21.5.7 |
| SIP 555 | Push Notification Service Not Supported | RFC 8599 |
| SIP 580 | Precondition Failure | RFC 3312 |
Source. Code numbers and official names are taken from the IANA SIP Parameters registry, with each code's definition linked to the RFC that specifies it. Causes and fixes are our own, from supporting UK business phone systems.
Troubleshooting guides
This page explains the code. These guides walk through the fix in detail.