What does 503 Service Unavailable mean in IMS?
It means the service cannot process the request right now, often because of temporary unavailability or overload.
| Protocol | ims | Network | 5G and LTE |
|---|---|---|---|
| Spec | RFC 3261 / 3GPP TS 24.229 | Spec Section | SIP 503 Service Unavailable failure response |
| Direction | IMS network -> UE | Message Type | SIP server-failure response |
| Full message name | IMS SIP 503 Service Unavailable |
|---|---|
| Protocol | IMS |
| Technology | 5G and LTE |
| Common deployment | VoNR and VoLTE |
| Direction | IMS network -> UE |
| Interface | Gm with onward IMS routing |
| Signaling bearer / channel | IMS SIP signaling / Server-failure response |
| Typical trigger | The service is overloaded, unavailable, or temporarily unable to process the request. |
| Main purpose | Signals temporary service unavailability rather than permanent request rejection. |
| Main specification | RFC 3261 / 3GPP TS 24.229, SIP 503 Service Unavailable failure response |
| Release added | See specification history |
| Procedures where used | IMS Service Unavailability |
503 Service Unavailable means the service cannot handle the request right now, usually for temporary server or overload reasons.
Signals temporary service unavailability rather than permanent request rejection.
503 means the service is temporarily unavailable.
Previous message(s): IMS SIP INVITE, IMS SIP REGISTER
Next message(s): Retry if allowed
Security context: Uses the same protected IMS signaling path as the original request.
SIP/2.0 503 Service Unavailable
Via:
From:
To:
Call-ID:
CSeq:
Retry-After: OPTIONAL
Content-Length: 0
This is SIP response syntax rather than ASN.1.
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/UDP ue.example.net;branch=z9hG4bK-inv1
From: <sip:alice@example.net>;tag=mo1
To: <sip:bob@example.net>
Call-ID: call-001@example.net
CSeq: 1 INVITE
Retry-After: 30
Content-Length: 0
| IE | Required | Description |
|---|---|---|
Status-Line | Yes | Shows the 503 failure code. |
Retry-After | Optional | Can indicate whether a later retry is expected. |
Status-LineShows the 503 failure code.
Presence: Required
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
Retry-AfterCan indicate whether a later retry is expected.
Presence: Optional
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
Likely cause: Temporary overload, outage, maintenance, or service impairment.
What to inspect: Check Retry-After, broader failure patterns, and whether other requests fail the same way.
Next step: Treat it as a temporary service-side issue unless it persists across independent retries.
It means the service cannot process the request right now, often because of temporary unavailability or overload.
Decode this message with the 3GPP Decoder, inspect the related message database, or open the matching call flow to see where this signaling step fits in the full procedure.