Code Message

100 Trying
180 Ringing
181 Call Is Being Forwarded
182 Queued
183 Session Progress
199 Early Dialog Terminated
200 OK
202 Accepted
204 No Notification
300 Multiple Choices
301 Moved Permanently
302 Moved Temporarily
305 Use Proxy
380 Alternative Service
400 Bad Request

401 Unauthorized
402 Payment Required

403 Forbidden
404 Not Found
405 Method Not Allowed
406 Not Acceptable

407 Proxy Authentication Required

408 Request Timeout

410 Gone
412 Conditional Request Failed

413 Request Entity Too Large

414 Request URI Too Long
415 Unsupported Media Type
416 Unsupported URI Scheme

417 Unknown Resource-Priority

420 Bad Extension

421 Extension Required
422 Session Interval Too Small

423 Interval Too Brief

428 Use Identity Header
429 Provide Referrer Identity

430 Flow Failed

433 Anonymity Disallowed
436 Bad Identity-Info
437 Unsupported Certificate
438 Invalid Identity Header
439 First Hop Lacks Outbound Support
440 Max-Breadth Exceeded
469 Bad Info Package
470 Consent Needed

473 Filtered Destination

476 Destination Unresolvable
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
489 Bad Event
491 Request Pending
493 Undecipherable

494 Security Agreement Required

500 Server Internal Error

501 Not Implemented

502 Bad Gateway

503 Service Unavailable
504 Server Time-out
505 Version Not Supported
513 Message Too Large
580 Precondition Failure
600 Busy Everywhere
603 Declined
604 Does Not Exist Anywhere
606 Not Acceptable
Description
This response indicates that the request has been received by the next-hop server
The UA receiving the INVITE is trying to alert the user
Call forward
Call on hold
Early Media, contains a SDP Body
The dialog was closed during connection setup.
The request has been processed successfully, result is in the response.
The
The request
request has
was been accepted,
executed but willbut
successfully, be executed at a later response
the corresponding time. is deliberately not
sent.
There is no unique destination address for the remote terminal.
The called party is permanently reachable somewhere else.
The called party is temporarily reachable somewhere else.
The specified proxy must be used.
The call was not successful, but alternative services are available.
The SIP request is incorrect.

The authorization is incorrect.

Not yet defined; intended for "not enough credit available".

Refused by the server

The remote terminal was not found or does not exist.
The method of the request (for example, SUBSCRIBE or NOTIFY) is not allowed.
The call options are not allowed.

The proxy needs authorization.

Timeout - The remote peer does not respond within a reasonable time.
The
The desired subscriber
prerequisites can no longer
for processing be reached
the request couldatnot
thebe
specified address.
met because a request required
for this failed.

The message content is too large.

The SIP address (URI) of the request is too long.
The codec is not supported.
The SIP address is incorrect.
The request should be treated with a certain priority, but the server does not understand
the details.

The server does not understand a protocol extension.

The server needs a protocol extension.
The Session Expires value is too low for the server.
The server is rejecting the request because the expiration time of the resource refreshed
by the request is too short
The identity header is missing.
No valid referred by token is specified.
The particular routing failed (proxy internal, endpoints should treat the response like code
400).
The server refuses to process anonymous requests.
The SIP address contained in the identity header is invalid, unavailable, or not supported.
The verifier cannot verify the certificate in the identity header.
The certificate in the identity header is invalid.
The registrar supports outbound feature, but the proxy used does not.
It is no longer possible to derive concurrent forks from the query.
Unsuitable Info-Package - Transmission error, resend.
The server has no access rights to at least one of the specified SIP addresses.

Destination blocked by a blacklist

Domain not resolvable in the server
The called party is currently not reachable.
This connection does not exist (anymore).

A forwarding loop has been detected.

Too many forwarding steps were identified.

The SIP address is incomplete.
The SIP address cannot be uniquely resolved.
The called party is busy.
The call attempt was aborted.
Illegal call attempt.
The server does not know the specified event.
A request from the same dialog is still being processed.
The request contains an encrypted MIME body that the recipient cannot decrypt.
The request requires a security agreement, but does not include a security mechanism
supported by the server.

Internal server error.

The server does not support the SIP request.

The gateway in the SIP request is corrupted.

The server's SIP service is temporarily unavailable.
The server cannot reach another server in a reasonable time.
The SIP protocol version is not supported by the server.
The SIP message is too large for UDP; TCP must be used.
The server cannot or does not want to meet the requirements for processing the request.
All terminal devices of the called subscriber are occupied.
The called party has rejected the call attempt.
The called party no longer exists.
The terminal device of the called party rejects the SIP request as invalid.
Comments
Fundamental to stop the retransmission timers
Usually without early media
No comments
Rarely seen
Early media, usually contains na SDP Body
Rarely seen
Ok
Used for non-invite requests
Rarely seen
Rarely seen
Used on redirect servers
Used on redirect servers
Rarely seen
Rarely seen
Some protocol error, \r\n missing, header missing, mispelled header
Part of the digest authentication. If you receive it once it is normal,
if repeatedly 401, you have an authentication error
May be used in prepaid systems
Refused by server (ACL, Wrong From Domain, Wrong Domain in the
Request-URI)
Missing user or route
No comments
Rarely seen
Part of the digest authentication. If you receive it once it is normal,
if repeatedly 407, you have an authentication error

Usually indicates a connectivity issue. To troubleshoot, get a

capture and check what endpoint is not replying. Proxies generate
internal 408 when they do not receive any provisional response in
less than a few seconds or after receiving a provisional reply they do
not receive another response for as specific timer.
No comments
Rarely seen
Usually when you add headers or data to the request above 1500
bytes in UDP. Try to use TCP or remove headers/codecs
Rarely seen
No comments
Rarely seen

Rarely seen
Some extension such as Timers is required but not supported.
Check the required and supported headers
No comments
Used in SIP Session timers
Registration expiration time is too short or expire time in SIP Session
timers is too low.
Rarely seen
Rarely seen

Rarely seen
Check the From header for anonymous.local
Rarely seen
Rarely seen
Rarely seen
Rarely seen
Rarely seen
Rarely seen
Rarely seen
After a DNS failover the SIP proxy can blacklist your request to avoid
overloading the DNS client
Rarely Seen
User not present in the location table
Dialog does not exist in the destination

Look for SIP spirals, requests sent to na ITSP who sent back to you
Usually you forgot to add the internal domain to the server and it is
looping.
No comments
No comments
No comments
Received after CANCEL
Codec Mismatch or RTP/SRTP mismatch
No comments
No comments
Rarely seen

Rarely seen
Error internal to the server, usually the server log will show you the
real cause (ex. failed query)
Check the Allow header
Common causes, domain not resolvable, gateway not reachable,
firewall blocking the request.
Usually congestion
No comments
No comments
No comments
No comments
Shoudn't be failed over
Default Asterisk response after the end of the dialpan
Rarely seen
Rarely seen