SIP response codes are the three-digit numbers a phone system, provider or softphone sends back to say what happened to a request: whether a call is ringing, was answered, was refused, or failed somewhere along the way. Type a code below to see what it means, which standard defines it, and what to check on your PBX or softphone.
You can paste a status line straight from a trace in sngrep or your PBX log.
How SIP response codes are grouped
Every SIP response code falls into one of six classes, set by its first digit. As a result, the class tells you most of what you need before you look up the exact code.
1xx Provisional: the server is handling the request, for example 100 Trying or 180 Ringing. These are not final answers.
2xx Success: the request worked. For a call, 200 OK means it was answered.
3xx Redirection: the user is at another address, given in the Contact header.
4xx Client error: the request failed at this server, for example wrong credentials, an unknown number or no codec in common.
5xx Server error: a server failed to handle a request that was itself valid.
6xx Global failure: the request will fail everywhere, for example the user declined the call.
The SIP response codes you will see most often
On a working business phone system, however, a handful of codes account for nearly all of the traffic in a trace. 100, 180, 183 and 200 belong to normal calls. 401 and 407 are normal too: they are the server asking for credentials, and the phone answers by resending the request with them. Therefore, the codes worth investigating are usually these:
403 Forbidden: the account is not allowed to make this call, or the provider does not accept requests from your IP address.
404 Not Found and 484 Address Incomplete: a number or dial plan problem.
408 Request Timeout and 480 Temporarily Unavailable: the far end could not be reached, often an unregistered phone or an expired NAT binding.
488 Not Acceptable Here: no codec or encryption method in common, which is common between WebRTC clients and PBXs.
503 Service Unavailable: a trunk or route is down, or the server is overloaded. In a browser phone, SIP.js reports a 503 itself when its WebSocket connection fails, so check the WebSocket and its TLS certificate before the PBX (a real case from the Browser Phone project).
How to find the code in your own calls
In most cases, the quickest way to see the response codes for a failing call is a SIP trace. On Linux, sngrep shows each call as a ladder diagram with every request and response. If headers look mangled, or responses arrive with the wrong addresses, a router feature called SIP ALG is a common cause; our guide explains why you should disable SIP ALG for VoIP.
In addition, responses belong to transactions, and transactions belong to dialogs. If the difference is unclear, see SIP dialog vs transaction, or the Siperb knowledge base article on SIP transactions, dialogs and sessions. Codes 428 and 436 to 438, and 607 and 608, relate to caller identity and spam blocking, which our article on STIR/SHAKEN covers.
Sources
The list of codes and their names follows the IANA SIP response codes registry. RFC 3261 defines most of the codes; each entry above links to the RFC that defines it. The notes on what to check reflect common causes on business phone systems and are a starting point, not a diagnosis.
Full list of SIP response codes
1xx: provisional
Code
Name
Meaning
Defined in
100
Trying
The next hop has received the request and is working on it.
RFC 3261
180
Ringing
The called device has received the call and is alerting the user.
RFC 3261
181
Call Is Being Forwarded
The system is forwarding the call to another destination.
RFC 3261
182
Queued
The called party is temporarily unavailable, so the system has queued the call.
RFC 3261
183
Session Progress
Progress information, usually carrying early media such as ringback tones or announcements.
RFC 3261
199
Early Dialog Terminated
One early dialog of a forked call has ended.
RFC 6228
2xx: success
Code
Name
Meaning
Defined in
200
OK
The request succeeded.
RFC 3261
202
Accepted (Deprecated)
The server accepted the request for processing. RFC 6665 deprecates its use for SIP events.
RFC 6665
204
No Notification
A subscription succeeded, but the server will send no notification because the state has not changed.
RFC 5839
3xx: redirection
Code
Name
Meaning
Defined in
300
Multiple Choices
The address resolves to several possible locations, listed in the Contact header.
RFC 3261
301
Moved Permanently
The user is no longer at this address; the new address is in the Contact header.
RFC 3261
302
Moved Temporarily
The user is temporarily at another address, given in the Contact header.
RFC 3261
305
Use Proxy
The caller must send the request through the proxy named in the Contact header.
RFC 3261
380
Alternative Service
The call failed, but alternative services are possible.
RFC 3261
4xx SIP response codes: 400 to 416
Code
Name
Meaning
Defined in
400
Bad Request
The server could not understand the request because of malformed syntax.
RFC 3261
401
Unauthorized
The request requires user authentication.
RFC 3261
402
Payment Required
The standard reserves this code for future use.
RFC 3261
403
Forbidden
The server understood the request but refuses to carry it out.
RFC 3261
404
Not Found
The user does not exist at the domain in the request.
RFC 3261
405
Method Not Allowed
The server understands the method but does not allow it for this address.
RFC 3261
406
Not Acceptable
The resource can only produce responses that the request's Accept headers do not allow.
RFC 3261
407
Proxy Authentication Required
Like 401, but the proxy is asking for credentials.
RFC 3261
408
Request Timeout
No final response arrived in time.
RFC 3261
410
Gone
The user existed once but is no longer available here, and no forwarding address is known.
RFC 3261
412
Conditional Request Failed
A conditional PUBLISH failed because the entity tag did not match.
RFC 3903
413
Request Entity Too Large
The request body is larger than the server will accept.
RFC 3261
414
Request-URI Too Long
The Request-URI is longer than the server will process.
RFC 3261
415
Unsupported Media Type
The message body is in a format the server does not support.
RFC 3261
416
Unsupported URI Scheme
The server does not understand the URI scheme, for example tel: or sips:.
RFC 3261
Client errors 417 to 469
Code
Name
Meaning
Defined in
417
Unknown Resource-Priority
The server did not understand the resource-priority value in the request.
RFC 4412
420
Bad Extension
The server does not support an extension listed in the Require header.
RFC 3261
421
Extension Required
The server needs an extension that the request did not list in Supported.
RFC 3261
422
Session Interval Too Small
The session timer interval in the request is shorter than the server allows.
RFC 4028
423
Interval Too Brief
The expiry time requested, for example on a REGISTER, is too short.
RFC 3261
424
Bad Location Information
The location information in the request is malformed or unsatisfactory.
RFC 6442
425
Bad Alert Message
The server rejected the alert message in the request.
RFC 8876
428
Use Identity Header
The server requires an Identity header and none was present.
RFC 8224
429
Provide Referrer Identity
The server needs a valid Referred-By token.
RFC 3892
430
Flow Failed
A specific connection flow to the user agent failed.
RFC 5626
433
Anonymity Disallowed
The called party does not accept anonymous calls.
RFC 5079
436
Bad Identity Info
The server could not use the identity information in the request.
RFC 8224
437
Unsupported Credential
The server does not support the certificate that signed the call.
RFC 8224
438
Invalid Identity Header
The Identity header failed verification.
RFC 8224
439
First Hop Lacks Outbound Support
The first-hop proxy does not support SIP Outbound.
RFC 5626
440
Max-Breadth Exceeded
Forking the request would exceed the allowed breadth.
RFC 5393
469
Bad Info Package
The server does not support the INFO package in the request.
RFC 6086
More 4xx SIP response codes: 470 to 494
Code
Name
Meaning
Defined in
470
Consent Needed
The recipient must give consent before the request can proceed.
RFC 5360
480
Temporarily Unavailable
The called party exists but cannot be reached right now.
RFC 3261
481
Call/Transaction Does Not Exist
The request refers to a call or transaction the server does not know.
RFC 3261
482
Loop Detected
The server has detected a routing loop.
RFC 3261
483
Too Many Hops
Max-Forwards reached zero before the request arrived.
RFC 3261
484
Address Incomplete
The number dialled is incomplete.
RFC 3261
485
Ambiguous
The address matches more than one user.
RFC 3261
486
Busy Here
The called device is busy.
RFC 3261
487
Request Terminated
The caller cancelled the request before it completed.
RFC 3261
488
Not Acceptable Here
This device cannot accept the session description.
RFC 3261
489
Bad Event
The server does not support the event package in a SUBSCRIBE or NOTIFY.
RFC 6665
491
Request Pending
Another request is already in progress for this dialog.
RFC 3261
493
Undecipherable
The server could not decrypt an S/MIME body.
RFC 3261
494
Security Agreement Required
The server requires a security mechanism agreement.
RFC 3329
5xx: server errors
Code
Name
Meaning
Defined in
500
Server Internal Error
The server hit an unexpected error.
RFC 3261
501
Not Implemented
The server does not support the requested method.
RFC 3261
502
Bad Gateway
A gateway or proxy received an invalid response from the next server.
RFC 3261
503
Service Unavailable
The server is overloaded, under maintenance or cannot handle the request.
RFC 3261
504
Server Time-out
A server did not get a timely response from another server it contacted.
RFC 3261
505
Version Not Supported
The server does not support the SIP version in the request.
RFC 3261
513
Message Too Large
The message is larger than the server can handle.
RFC 3261
555
Push Notification Service Not Supported
The server does not support the push notification service requested.
RFC 8599
580
Precondition Failure
The network could not meet media preconditions, such as reserved bandwidth.
RFC 3312
6xx: global failures
Code
Name
Meaning
Defined in
600
Busy Everywhere
The called party is busy and not reachable anywhere else.
RFC 3261
603
Decline
The called party explicitly rejected the call.
RFC 3261
604
Does Not Exist Anywhere
The user does not exist anywhere.
RFC 3261
606
Not Acceptable
The session description is not acceptable at any location.
RFC 3261
607
Unwanted
The called party marked the call as unwanted.
RFC 8197
608
Rejected
An intermediary, such as a call analytics service, rejected the call.