SIP 503 Service Unavailable
A server in the path is temporarily unable to handle the call. On a hosted system this most often means the trunk has hit its concurrent call limit, has lost registration with the carrier, or the provider is having an incident.
What SIP 503 Service Unavailable actually means
The server is temporarily unable to process the request due to overload or maintenance, and it may include a Retry-After header suggesting when to try again. The word temporarily is meaningful: it signals a capacity or availability condition rather than a configuration error, which is why the fix is so often on the provider side.
What causes SIP 503 on a business phone system
- The concurrent call limit has been reachedTrunks are sold with a fixed number of simultaneous channels, and the call that exceeds the ceiling is refused. The tell is that it happens at busy periods and clears on its own, which is exactly what makes people dismiss it as random.
- The trunk has lost registration with the carrierWhere your platform registers upstream to a carrier, losing that registration refuses calls while your own handsets still show as registered. Everything looks healthy locally and nothing can call out.
- The provider is having an incident or doing maintenanceA platform-side problem produces a 503 across every extension at once. If it started without any change at your end and affects everyone, check the provider status page before investigating further.
- An upstream route is unavailableCalls to one particular destination or country failing with a 503 while everything else works points at a carrier route rather than your system.
How to fix SIP 503
- Establish the blast radiusOne extension, one destination, or everyone? Everyone at once points at the provider or the trunk. One destination points at a route. One extension points at that extension. This determines who needs to fix it.
- Check the concurrent call count against your allowanceLook at how many simultaneous calls you are licensed for and how many were live when it failed. Businesses that have grown since the trunk was ordered routinely outgrow it without noticing.
- Check your provider status page and trunk registrationConfirm the trunk shows as registered upstream. Where the provider has an open incident, the remaining steps are moot.
- Review your failover arrangementsA 503 is exactly the condition failover exists for. If a provider incident took your phones out entirely, that is worth designing around rather than waiting for the next one.
Fixing the underlying problem
This page explains the code. These guides walk through the fix in detail.
Questions about SIP 503
What does SIP 503 Service Unavailable mean?
Why does SIP 503 only happen at busy times?
Is SIP 503 my fault or my provider fault?
Call hangup causes that become SIP 503
If the call crossed a gateway between SIP and ISDN or SS7, this status may have started life as one of these Q.850 cause values. The mapping is defined in RFC 3398 section 7.2.4.1.
- Q.850 cause 34No circuit/channel available
- Q.850 cause 38Network out of order
- Q.850 cause 41Temporary failure
- Q.850 cause 42Switching equipment congestion
- Q.850 cause 47Resource unavailable, unspecified
- Q.850 cause 58Bearer capability not presently available
- Q.850 cause 88Incompatible destination
Related SIP response codes
Source. SIP 503 Service Unavailable is defined in RFC 3261 section 21.5.4 and registered in the IANA SIP Parameters — Response Codes. The causes and fixes above are drawn from our own experience supporting UK business phone systems.