| Protocol | ims | Network | 5G and LTE |
|---|---|---|---|
| Spec | RFC 3261 / 3GPP TS 24.229 | Spec Section | SIP 604 Does Not Exist Anywhere global failure response |
| Direction | IMS network -> UE | Message Type | SIP global-failure response |
| Full message name | IMS SIP 604 Does Not Exist Anywhere |
|---|---|
| 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 / Global failure response |
| Typical trigger | The service determines that the target identity does not exist anywhere relevant to the request. |
| Main purpose | Stops any further alternate-location attempts by declaring the target globally nonexistent. |
| Main specification | RFC 3261 / 3GPP TS 24.229, SIP 604 Does Not Exist Anywhere global failure response |
| Release added | See specification history |
| Procedures where used | IMS Global Target Resolution Failure |
604 Does Not Exist Anywhere means the target does not exist globally for the request.
Stops any further alternate-location attempts by declaring the target globally nonexistent.
604 means the target does not exist anywhere relevant to the request.
Previous message(s): IMS SIP INVITE
Next message(s): Procedure stop
Security context: Uses the same protected IMS signaling path as the original request.
SIP/2.0 604 Does Not Exist Anywhere
Via:
From:
To:
Call-ID:
CSeq:
Content-Length: 0
This is SIP response syntax rather than ASN.1.
SIP/2.0 604 Does Not Exist Anywhere
Via: SIP/2.0/UDP ue.example.net;branch=z9hG4bK-inv1
From: <sip:alice@example.net>;tag=mo1
To: <sip:unknown@example.net>
Call-ID: call-001@example.net
CSeq: 1 INVITE
Content-Length: 0
| IE | Required | Description |
|---|---|---|
Status-Line | Yes | Shows the 604 global nonexistent-target code. |
Call-ID | Yes | Correlates the global failure with the request. |
Status-LineShows the 604 global nonexistent-target 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.
Call-IDCorrelates the global failure with the request.
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 target identity does not exist anywhere relevant to the request.
What to inspect: Check the dialed identity and any global directory or service logic behind the response.
Next step: Do not treat it like a simple branch-level 404.
It means the target identity is considered nonexistent globally for that request.
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.