SIP 503 Service Unavailable means the server that received the call cannot handle it right now, because it is overloaded, in maintenance or has no way to complete it. On VoIP routes a 503 usually means a capacity limit (channels or CPS), no available supplier for the destination, or a problem with the account, and the right fix depends on which hop sent it.
What does SIP 503 mean?
RFC 3261 defines 503 as a temporary condition: the server is "temporarily unable to process the request due to a temporary overloading or maintenance". The server may add a Retry-After header saying when to try again. The RFC also says a client that receives a 503 should try an alternate server, and should not send that server new requests for the Retry-After period.
In practice, many switches use 503 as a generic "cannot complete this call" answer. That is why 503 is one of the most common failure codes in wholesale CDRs, and why the code alone is not enough to diagnose it. Look at the Reason header: carriers often add the original Q.850 cause code, and RFC 3398 maps causes 34, 38, 41, 42 and 47 (no circuit, network out of order, temporary failure, congestion, resource unavailable) to 503.
What causes a SIP 503 error?
| Cause | How to recognise it |
|---|---|
| Channel limit reached | 503s appear only at peak hours, when concurrent calls hit the agreed maximum |
| CPS limit exceeded | 503s come in bursts when a dialer launches many calls at once |
| No route for the destination | Every call to one prefix fails at once, other destinations work |
| Supplier down or congested | The Reason header shows cause 34, 41 or 42, often from one downstream carrier |
| Account or balance issue | All calls fail from the first attempt, right after a payment or limit date |
| Your own PBX overloaded | The 503 comes from your side, not from the provider, often with high CPU |
| Maintenance | Short outage, sometimes with a Retry-After header |
Some providers return 403 or 402 for credit problems and 503 for capacity; others use 503 for everything. Ask your supplier for its own code table.
How do you fix a SIP 503 Service Unavailable?
- Find who sent it. In a SIP trace, check the Via and Server or User-Agent headers of the 503. If your own PBX generated it, the problem is local.
- Check the time pattern. 503s that follow your traffic peaks point to channels or CPS. Compare peak concurrent calls with your limit (see SIP trunk channels and CPS).
- Check the destination pattern. If only one country or operator fails, the supplier has lost its route there. Ask for a new route or move the prefix to a backup.
- Pace your dialer. Spread call launches so you stay under the CPS limit, or ask for a higher one.
- Configure failover. Send the call to a second route when the first returns 503, as RFC 3261 recommends. This is a core part of least cost routing.
- Respect Retry-After. Hammering a server that is in maintenance only creates more failures.
Is SIP 503 the caller's fault or the network's?
Almost always the network's or the route's. The called person never sees a 503: it is a failure between servers. That is why 503s lower both ASR and NER, while busy or no-answer codes such as 486 and 480 reflect the called user. A route with a steady share of 503s above a few percent of attempts is underdimensioned or unstable (see NER vs ASR).
SIP 503 on Cisco, Asterisk and FreeSWITCH
On Cisco gateways and CUBE, a 503 sent back toward your PBX often means no outgoing trunk or resource was available for the call. In Asterisk, a 503 received from the provider usually shows up as a CONGESTION dial status (hangup cause 34). In FreeSWITCH, NORMAL_CIRCUIT_CONGESTION and similar resource causes map to 503. In each case, read the log line before the 503 to see which limit or route triggered it. The full list of codes is on our SIP error codes page.
When the route itself is the problem
If 503s persist on one destination after you have checked your limits and pacing, the route lacks capacity. VoIPMatcher sources backup and primary VoIP termination routes from its carriers and manages them for you. Request a backup VoIP route with the destinations, channels and CPS you need.
Frequently asked questions
What is the difference between SIP 503 and 500?
500 Server Internal Error means the server hit an unexpected condition, often a software fault or an unmapped cause. 503 Service Unavailable means a temporary condition such as overload, maintenance or no capacity, and implies the call may work later or on another server. For routing, 503 is the classic signal to fail over to a backup route.
What is the Retry-After header in a 503?
Retry-After is an optional header in a 503 response that tells the client how many seconds to wait before sending new requests to that server. RFC 3261 says the client should not forward other requests to that server during this time, and should try an alternate server instead.
Can a SIP 503 be caused by my own PBX?
Yes. If your PBX or session border controller runs out of channels, licences or CPU, or has no outbound route that matches the number, it can return 503 to your own users before the call ever reaches the provider. A SIP trace shows which device generated the response.
Does a SIP 503 cost money?
No. A 503 is a failed call attempt with no answer, so it is not billed per minute on standard wholesale routes. It still costs you indirectly: failed attempts lower ASR, waste dialer capacity and agent time, and a supplier may limit accounts that send a very high share of failing calls.
Need a route?
Send the destination, route type and target rate. We reply with what we can deliver.