What does 480 Temporarily Unavailable mean in IMS?
It means the target is known, but not currently available for the requested service.
| Protocol | ims | Network | 5G and LTE |
|---|---|---|---|
| Spec | RFC 3261 / 3GPP TS 24.229 | Spec Section | SIP 480 Temporarily Unavailable failure response |
| Direction | IMS network -> UE | Message Type | SIP request-failure response |
| Full message name | IMS SIP 480 Temporarily 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 / Final request-failure response |
| Typical trigger | The target user is known, but currently unavailable for service. |
| Main purpose | Stops the current attempt while indicating the target may become reachable later. |
| Main specification | RFC 3261 / 3GPP TS 24.229, SIP 480 Temporarily Unavailable failure response |
| Release added | See specification history |
| Procedures where used | IMS Reachability Failure, VoNR Call Setup Failure, VoLTE Call Setup Failure |
480 Temporarily Unavailable means the target is currently unreachable or unavailable, but not permanently unknown.
Stops the current attempt while indicating the target may become reachable later.
480 means the target is temporarily unavailable, not permanently unknown.
Previous message(s): IMS SIP INVITE
Next message(s): Retried attempt or procedure stop
Security context: Uses the same protected IMS signaling path as the original request.
SIP/2.0 480 Temporarily 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 480 Temporarily Unavailable
Via: SIP/2.0/UDP ue.example.net;branch=z9hG4bK-inv1
From: <sip:alice@example.net>;tag=mo1
To: <sip:bob@example.net>;tag=term1
Call-ID: call-001@example.net
CSeq: 1 INVITE
Content-Length: 0
| IE | Required | Description |
|---|---|---|
Status-Line | Yes | Shows the 480 failure code. |
Retry-After | Optional | Can suggest when a retry might make sense. |
Status-LineShows the 480 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 suggest when a retry might make sense.
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: The user or service is temporarily unreachable or not available right now.
What to inspect: Check presence, registration state, paging reachability, and any Retry-After information.
Next step: Decide whether to retry later or investigate why the target is currently unavailable.
It means the target is known, but not currently available for the requested service.
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.