The SIP Response Codes Reference is a searchable lookup for the response
codes carried by the Session Initiation Protocol, the signalling layer behind
VoIP calls, video conferencing and messaging. From 100 Trying to
486 Busy Here to 604 Does Not Exist Anywhere, this tool decodes every code
with its reason phrase, class and the call-flow context you need when reading a
SIP trace.
How it works
SIP, defined in RFC 3261, deliberately mirrors HTTP’s status-code model with six classes keyed off the first digit:
1xx Provisional — request received, still processing (180 Ringing)
2xx Success — request succeeded (200 OK answers the call)
3xx Redirection — try a new location (302 Moved Temporarily)
4xx Client error — request failed at THIS server (486 Busy Here)
5xx Server error — this server failed (503 Service Unavailable)
6xx Global — failure for the WHOLE call (600 Busy Everywhere)
The crucial SIP-specific distinction is between 4xx and 6xx. When a proxy
forks an INVITE to several registered devices, a 4xx rejects only that one
branch, so other devices may still answer. A 6xx is authoritative for the
entire call — it tells the proxy to abandon every branch. This tool keeps the
full table in your browser and filters it by number, reason or keyword.
Example and tips
A successful call signals 100 Trying → 180 Ringing → 200 OK → ACK. A
declined call might go 100 Trying → 180 Ringing → 603 Decline. When you
see 487 Request Terminated, look for a matching CANCEL — it usually means the
caller gave up while ringing, not a fault. Treat 488 Not Acceptable Here and
415 Unsupported Media Type as codec/SDP negotiation problems, and 407 Proxy Authentication Required as the normal challenge step before a registrar or proxy
accepts your request.