The GTP Cause Values presented in the table below will be seen in the Cause Information Element (IE).
Specification versions: TS 29.274, R17.4.0 (GTPv2) and TS 32.295, R17.0.0 (GTP’)
You can filter the table contents by typing a value, or any text, into the Search field. Click on an arrow in a column header to sort the visible entries by that column.
Value |
Protocol |
Use |
Cause |
Description |
| 0 | GTPv2 | Request | Reserved | Shall not be sent; if received the Cause IE shall be treated as an invalid IE. |
| 1 | GTPv2 | Request | Request IMEI | Used by GGSN to notify SGSN what to do. |
| 2 | GTPv2 | Request | Local Detach | |
| 3 | GTPv2 | Request | Complete Detach | |
| 4 | GTPv2 | Request | RAT changed from 3GPP to Non-3GPP | |
| 5 | GTPv2 | Request | ISR deactivation | |
| 6 | GTPv2 | Request | Error Indication received from RNC/eNodeB/S4-SGSN | |
| 7 | GTPv2 | Request | IMSI Detach Only | |
| 8 | GTPv2 | Request | Reactivation Required | |
| 9 | GTPv2 | Request | PDN reconnection to this APN disallowed | |
| 10 | GTPv2 | Request | Access changed from Non-3GPP to 3GPP | |
| 11 | GTPv2 | Request | PDN connection inactivity timer expires | |
| 12 | GTPv2 | Request | PGW not responding | |
| 13 | GTPv2 | Request | Network Failure | |
| 14 | GTPv2 | Request | QoS parameter mismatch | |
| 15 | GTPv2 | Request | EPS to 5GS Mobility | |
| 16 | GTPv2 | Accept Rsp | Request accepted | |
| 17 | GTPv2 | Accept Rsp | Request accepted partially | |
| 18 | GTPv2 | Accept Rsp | New PDN type due to network preference. | |
| 19 | GTPv2 | Accept Rsp | New PDN type due to single address bearer only. | |
| 20-63 | GTPv2 | Accept Rsp | Spare | This value range shall be used by Cause values in an acceptance response/triggered message. |
| 49-58 | GTP' | Request | Reserved | Cause values reserved for GPRS charging protocol use (3GPP TS 32.295) |
| 59 | GTP' | Request | System failure | |
| 60 | GTP' | Request | Transmit buffers are becoming full | |
| 61 | GTP' | Request | Receive buffers are becoming full | |
| 62 | GTP' | Request | Another node is about to go down | |
| 63 | GTP' | Request | This node is about to go down | |
| 64 | GTPv2 | Reject Rsp | Context Not Found | |
| 65 | GTPv2 | Reject Rsp | Invalid Message Format. | |
| 66 | GTPv2 | Reject Rsp | Version not supported by next peer | |
| 67 | GTPv2 | Reject Rsp | Invalid length. | |
| 68 | GTPv2 | Reject Rsp | Service not supported | |
| 69 | GTPv2 | Reject Rsp | Mandatory IE incorrect | |
| 70 | GTPv2 | Reject Rsp | Mandatory IE missing | |
| 71 | GTPv2 | Reject Rsp | Shall not be used. | This value was used in earlier versions of the specification. If received, it shall be interpreted as unspecified rejection cause. Unspecified/unrecognized rejection cause shall be treated in the same ways as the cause value 94 "Request rejected (reason not specified)". |
| 72 | GTPv2 | Reject Rsp | System failure | |
| 73 | GTPv2 | Reject Rsp | No resources available | |
| 74 | GTPv2 | Reject Rsp | Semantic error in the TFT operation | |
| 75 | GTPv2 | Reject Rsp | Syntactic error in the TFT operation | |
| 76 | GTPv2 | Reject Rsp | Semantic errors in packet filter(s) | |
| 77 | GTPv2 | Reject Rsp | Syntactic errors in packet filter(s) | |
| 78 | GTPv2 | Reject Rsp | Missing or unknown APN | |
| 79 | GTPv2 | Reject Rsp | Shall not be used. | This value was used in earlier versions of the specification. If received, it shall be interpreted as unspecified rejection cause. Unspecified/unrecognized rejection cause shall be treated in the same ways as the cause value 94 "Request rejected (reason not specified)". |
| 80 | GTPv2 | Reject Rsp | GRE key not found. | |
| 81 | GTPv2 | Reject Rsp | Relocation failure. | |
| 82 | GTPv2 | Reject Rsp | Denied in RAT. | |
| 83 | GTPv2 | Reject Rsp | Preferred PDN type not supported. | |
| 84 | GTPv2 | Reject Rsp | All dynamic addresses are occupied. | |
| 85 | GTPv2 | Reject Rsp | UE context without TFT already activated. | This Cause value is only used over the S4, S5 and S8 interface in the secondary PDP Context Activation procedure. |
| 86 | GTPv2 | Reject Rsp | Protocol type not supported. | |
| 87 | GTPv2 | Reject Rsp | UE not responding. | This cause value may also be used by a Downlink Data Notification Failure Indication, which is an initial message. |
| 88 | GTPv2 | Reject Rsp | UE refuses. | |
| 89 | GTPv2 | Reject Rsp | Service denied. | This cause value may also be used by a Downlink Data Notification Failure Indication, which is an initial message. |
| 90 | GTPv2 | Reject Rsp | Unable to page UE | |
| 91 | GTPv2 | Reject Rsp | No memory available | |
| 92 | GTPv2 | Reject Rsp | User authentication failed | |
| 93 | GTPv2 | Reject Rsp | APN access denied – no subscription | |
| 94 | GTPv2 | Reject Rsp | Request rejected (reason not specified) | |
| 95 | GTPv2 | Reject Rsp | P-TMSI Signature mismatch | |
| 96 | GTPv2 | Reject Rsp | IMSI/IMEI not known | |
| 97 | GTPv2 | Reject Rsp | Semantic error in the TAD operation | |
| 98 | GTPv2 | Reject Rsp | Syntactic error in the TAD operation | |
| 99 | GTPv2 | Reject Rsp | Shall not be used | This value was used in earlier versions of the specification. If received, it shall be interpreted as unspecified rejection cause. Unspecified/unrecognized rejection cause shall be treated in the same ways as the cause value 94 "Request rejected (reason not specified)". |
| 100 | GTPv2 | Reject Rsp | Remote peer not responding | |
| 101 | GTPv2 | Reject Rsp | Collision with network initiated request | |
| 102 | GTPv2 | Reject Rsp | Unable to page UE due to Suspension | |
| 103 | GTPv2 | Reject Rsp | Conditional IE missing | |
| 104 | GTPv2 | Reject Rsp | APN Restriction type Incompatible with currently active PDN connection | |
| 105 | GTPv2 | Reject Rsp | Invalid overall length of the triggered response message and a piggybacked initial message | |
| 106 | GTPv2 | Reject Rsp | Data forwarding not supported | |
| 107 | GTPv2 | Reject Rsp | Invalid reply from remote peer | |
| 108 | GTPv2 | Reject Rsp | Fallback to GTPv1 | |
| 109 | GTPv2 | Reject Rsp | Invalid peer | |
| 110 | GTPv2 | Reject Rsp | Temporarily rejected due to handover/TAU/RAU procedure in progress | |
| 111 | GTPv2 | Reject Rsp | Modifications not limited to S1-U bearers | |
| 112 | GTPv2 | Reject Rsp | Request rejected for a PMIPv6 reason | See 3GPP TS 29.275 |
| 113 | GTPv2 | Reject Rsp | APN Congestion | |
| 114 | GTPv2 | Reject Rsp | Bearer handling not supported | |
| 115 | GTPv2 | Reject Rsp | UE already re-attached | This cause value may also be used by a Downlink Data Notification Failure Indication, which is an initial message. |
| 116 | GTPv2 | Reject Rsp | Multiple PDN connections for a given APN not allowed | |
| 117 | GTPv2 | Reject Rsp | Target access restricted for the subscriber | |
| 118 | GTPv2 | Reject Rsp | Shall not be used | This value was used in earlier versions of the specification. If received, it shall be interpreted as unspecified rejection cause. Unspecified/unrecognized rejection cause shall be treated in the same ways as the cause value 94 "Request rejected (reason not specified)". |
| 119 | GTPv2 | Reject Rsp | MME/SGSN refuses due to VPLMN Policy | |
| 120 | GTPv2 | Reject Rsp | GTP-C Entity Congestiony | |
| 121 | GTPv2 | Reject Rsp | Late Overlapping Request | |
| 122 | GTPv2 | Reject Rsp | Timed out Request | |
| 123 | GTPv2 | Reject Rsp | UE is temporarily not reachable due to power saving | |
| 124 | GTPv2 | Reject Rsp | Relocation failure due to NAS message redirection | |
| 125 | GTPv2 | Reject Rsp | UE not authorised by OCS or external AAA Server | |
| 126 | GTPv2 | Reject Rsp | Multiple accesses to a PDN connection not allowed | |
| 127 | GTPv2 | Reject Rsp | Request rejected due to UE capability | |
| 128 | GTPv2 | Reject Rsp | S1-U Path Failure | This cause code may also be used in a Downlink Data Notification and a Delete Bearer Request message, which are initial messages. |
| 129 | GTPv2 | Reject Rsp | 5GC not allowed | |
| 130 | GTPv2 | Reject Rsp | PGW mismatch with network slice subscribed by the UE | |
| 131 | GTPv2 | Reject Rsp | Rejection due to paging restriction | This cause value may also be used by a Downlink Data Notification Failure Indication, which is an initial message. |
| 132-239 | GTPv2 | Reject Rsp | Spare | These values are or may be used in the newer versions of the spec. If the receiver cannot comprehend a value, it shall be interpreted as unspecified rejection cause. Unspecified/unrecognized rejection cause shall be treated in the same way as the cause value 94 "Request rejected (reason not specified)". |
| 177 | GTP' | Accept Rsp | CDR decoding error | |
| 178-191 | GTP' | Accept Rsp | Reserved for GPRS charging protocol use (3GPP TS 32.295) | |
| 240 - 255 | GTPv2 | Request | Spare | For future use in an initial/request message. This value is or may be used in the newer versions of the spec. If the receiver cannot comprehend the value, it shall be interpreted as an unspecified request/initial message cause. Unspecified/unrecognized cause handling in a request/initial message shall be implementation dependent (e.g. may be ignored). |
| 241 - 251 | GTP' | Reject Rsp | Reserved for GPRS charging protocol use (3GPP TS 32.295) | |
| 252 | GTP' | Reject Rsp | Request related to possibly duplicated packets already fulfilled | |
| 253 | GTP' | Reject Rsp | Request already fulfilled | |
| 254 | GTP' | Reject Rsp | Sequence numbers of released/cancelled packets IE incorrect | |
| 255 | GTP' | Reject Rsp | Request not fulfilled |