| Protocol | ims | Network | 5G and LTE |
|---|---|---|---|
| Spec | RFC 3261 / 3GPP TS 24.229 | Spec Section | SIP 302 Moved Temporarily redirection response |
| Direction | IMS network -> UE | Message Type | SIP redirection response |
| Full message name | IMS SIP 302 Moved Temporarily |
|---|---|
| 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 / SIP redirection response |
| Typical trigger | The target wants the sender to retry the request against another temporary address. |
| Main purpose | Provides alternative routing information instead of accepting the request on the current target. |
| Main specification | RFC 3261 / 3GPP TS 24.229, SIP 302 Moved Temporarily redirection response |
| Release added | See specification history |
| Procedures where used | IMS Session Redirection |
302 Moved Temporarily redirects the sender to another temporary target or contact.
Provides alternative routing information instead of accepting the request on the current target.
302 means the sender should retry the request at another temporary destination.
Previous message(s): IMS SIP INVITE
Next message(s): Retried request toward alternate target
Security context: Uses the same protected IMS signaling path as the original request.
SIP/2.0 302 Moved Temporarily
Via:
From:
To:
Call-ID:
CSeq:
Contact:
Content-Length: 0
This is SIP response syntax rather than ASN.1.
SIP/2.0 302 Moved Temporarily
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
Contact: <sip:carol@example.net>
Content-Length: 0
| IE | Required | Description |
|---|---|---|
Status-Line | Yes | Shows the 302 redirection code. |
Contact | Yes | Provides the alternate temporary target. |
Status-LineShows the 302 redirection 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.
ContactProvides the alternate temporary target.
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.
Likely cause: The far side returned a temporary redirect.
What to inspect: Check the Contact target and whether the sender retried correctly.
Next step: Follow the retried branch toward the alternate target.
It means the request should be retried toward another temporary target instead of the original one.
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.