Understanding SIP Response Codes (SIP 4xx, 5xx, 6xx) for Troubleshooting

SIP response codes are the PBX's way of telling you why a call failed—reading them correctly turns vague "call didn't go through" complaints into fast fixes.

Definition: SIP response codes are three-digit replies to SIP requests: 1xx (provisional), 2xx (success), 3xx (redirection), 4xx (client error), 5xx (server error), 6xx (global failure).

The classes at a glance

Common codes and what to do

• 401/407 – authentication needed: check SIP username/password.
• 404 – not found: wrong extension or DID mapping.
• 486 – busy: caller/callee busy or no free channel.
• 403 – forbidden: ACL or trunk permission issue.
• 503 – service unavailable: trunk down or overload.
• 408 – timeout: NAT/firewall blocking, or device offline.
• 603 – decline: callee rejected (DND).

Troubleshooting flow

1. Capture the SIP message (PBX logs or packet capture).
2. Note the code class (4xx = config, 5xx = service).
3. Check credentials for 401, routing for 404, trunks for 503.
4. For 408/timeout, inspect NAT and firewall ALG.

Newrock perspective

Newrock OM-series logs SIP sessions clearly and an SBC at the edge normalizes inter-op issues that produce 4xx/5xx across carriers.

FAQ

Is 486 the same as no answer?

No—486 is busy; no-answer is typically a 408/timeout or forward to voicemail.

Why do I see 503 intermittently?

Usually trunk capacity or carrier blips; add redundancy and retry.

Do codes differ by vendor?

The classes are standardized by RFC 3261; exact subcodes vary slightly.

Where do I see these codes?

In the IP-PBX call logs or a SIP packet capture (e.g., Wireshark).

Conclusion

Learn the SIP code classes and the handful of common ones, and you can triage most VoIP call failures in minutes instead of hours.