Locate the response family
- 1xx ProvisionalRequest is progressing
- 2xx SuccessRequest succeeded
- 3xx RedirectionAnother destination
- 4xx Request failureInterpret this request
- 5xx Server failureServer could not fulfil503 belongs here
- 6xx Global failureFailure across destinations
Read the status with its request method and call leg. For example, 200 after REGISTER confirms a binding; it does not prove an INVITE succeeded.
What this response means
The server cannot currently handle the request, for example because of temporary overload or maintenance. The response may include Retry-After guidance.
Read it in context
A PBX, proxy or carrier can emit 503 under its own capacity and availability policy. Some implementations map other upstream conditions into it, so the number alone does not prove a platform-wide outage.
Administrator checks
Identify the sender, affected methods and scope. Check service status, capacity signals and recent changes. Inspect any Retry-After and use documented backoff. Verify whether alternate routing is supported for this failure rather than assuming every trunk sequence will advance.
Next action and common mistake
Do not create rapid retries that increase load. Test new calls after recovery and verify incoming service separately from outbound fallback. Record the incident window and call identifiers when escalating to the carrier.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.