The GTP Cause Values presented in the table below will be seen in the Cause Information Element (IE).
Specification versions: TS 29.060, R17.1.0 (GTPv1) 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 | GTPv1 | Request | Request IMSI | Used by GGSN to notify SGSN what to do. |
1 | GTPv1 | Request | Request IMEI | Used by GGSN to notify SGSN what to do. |
2 | GTPv1 | Request | Request IMSI and IMEI | Used by GGSN to notify SGSN what to do. |
3 | GTPv1 | Request | No identity needed | Used by GGSN to notify SGSN what to do. |
4 | GTPv1 | Request | MS Refuses | May be used by SGSN to reject a Network-Requested PDP Context Activation. |
5 | GTPv1 | Request | MS is not GPRS Responding | May be used by SGSN to reject a Network-Requested PDP Context Activation. |
6 | GTPv1 | Request | Reactivation Requested | Used by the GGSN while tearing down all the PDP Context(s) associated with same PDN connection. It indicates that the GGSN is requesting UE to re-initiate the PDP Context Activation procedure for the corresponding APN. |
7 | GTPv1 | Request | PDP address inactivity timer expires | Used by the GGSN in Delete PDP Context Request(s) to indicate that all the PDP context(s) that share the same emergency PDP address are deleted upon the inactivity timer expiry as specified in 3GPP TS 23.203. |
8 | GTPv1 | Request | Network Failure | Used by the SGSN in the Delete PDP Context Request to indicate that the message is sent due to a network problem. |
9 | GTPv1 | Request | QoS parameter mismatch | Used by the SGSN in the Delete PDP Context Request to indicate that the PDP can not be established due to a QoS parameter mismatch. |
10-48 | GTPv1 | Request | For future use | |
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-127 | GTPv1 | For future use | ||
128 | GTPv1 | Accept Rsp | Request accepted | Returned when a GSN has accepted a control plane request. |
129 | GTPv1 | Accept Rsp | New PDP type due to network preference | Indicates that the MS has requested PDP type IPv4v6 and only IPv4 or IPv6 address is allowed for the PDN based on GGSN operator policy, as specified in 3GPP TS 23.060. |
130 | GTPv1 | Accept Rsp | New PDP type due to single address bearer only | Indicates that the MS has requested PDP type IPv4v6 and both IPv4 and IPv6 addressing is possible in the PDN but the Dual Address Bearer Flag of the Common Flags IE is set to 0 or the Common Flags IE is absent, or only single IP version addressing is possible in the PDN, as specified in 3GPP TS 23.060. |
131-176 | GTPv1 | Accept Rsp | For future use | |
177 | GTP' | Accept Rsp | CDR decoding error | |
178-191 | GTP' | Accept Rsp | Reserved for GPRS charging protocol use (3GPP TS 32.295) | |
192 | GTPv1 | Reject Rsp | Non-existent | Indicates a non-existent or an inactive PDP context. |
193 | GTPv1 | Reject Rsp | Invalid message format | If a GTP entity receives a Request message within an IP/UDP packet of a length that is inconsistent with the value specified in the Length field of the GTP header, then the receiving GTP entity should log the error and shall send the Response message with this cause value. |
194 | GTPv1 | Reject Rsp | IMSI/IMEI not known | Indicates a non-existent MM context. |
195 | GTPv1 | Reject Rsp | MS is GPRS Detached | Indicates an idle MM context. |
196 | GTPv1 | Reject Rsp | MS is not GPRS Responding | May be used by SGSN to reject a Network-Requested PDP Context Activation. |
197 | GTPv1 | Reject Rsp | MS Refuses | May be used by SGSN to reject a Network-Requested PDP Context Activation. |
198 | GTPv1 | Reject Rsp | Version not supported | Returned when the recipient does not recognize the version number in the request message. |
199 | GTPv1 | Reject Rsp | No resources available | Generic temporary error condition indicating that some resource is used up at the moment (excluding the conditions all dynamic PDP addresses are occupied and no memory is available). |
200 | GTPv1 | Reject Rsp | Service not supported | Generic error indicating that the GSN does not support the requested service. |
201 | GTPv1 | Reject Rsp | Mandatory IE incorrect | In a received GTP signalling message Request with a valid length, a mandatory or a conditional extendable length TLV format information element may have a Length field value, which is different from the expected Length. In this case, if the Length field value is greater than expected, the extra unknown octets shall be discarded. If the Length field value is less than the number of fixed octets defined for that IE, preceding the extended field(s), the receiver shall try to continue the procedure, if possible. Otherwise, this information element shall be discarded, the error should be logged, and a Response shall be sent with this Cause code. |
202 | GTPv1 | Reject Rsp | Mandatory IE missing | The receiver of a GTP signalling Request message with a missing mandatory information element shall discard the request, should log the error, and shall send a Response with this cause code. |
203 | GTPv1 | Reject Rsp | Optional IE incorrect | All optional information elements that are incorrect in a GTP signaling message shall be treated as not present in the message. However, if the receiving node may not handle the message correctly because of the incorrect information element, the receiving node should log the error and shall return a response with this cause code. |
204 | GTPv1 | Reject Rsp | System failure | Generic permanent error condition. |
205 | GTPv1 | Reject Rsp | Roaming restriction | Indicates that the SGSN cannot activate the requested PDP context because of the roaming restrictions. |
206 | GTPv1 | Reject Rsp | P-TMSI Signature mismatch | Returned if (1) the P-TMSI Signature stored in the old SGSN does not match the value sent by the MS via the new SGSN; or (2) the MS does not provide the P-TMSI Signature to the new SGSN while the old SGSN has stored the P-TMSI Signature for that MS. |
207 | GTPv1 | Reject Rsp | GPRS connection suspended | Indicates that the GPRS activities of the mobile station are suspended. |
208 | GTPv1 | Reject Rsp | Authentication failure | Indicates that the user authentication failed in the new SGSN. |
209 | GTPv1 | Reject Rsp | User authentication failed | Indicates that the external packet network has rejected the user's service request. |
210 | GTPv1 | Reject Rsp | Context not found | Indicates that the PDP Context referenced in an Active Secondary Context Request message was not found in the receiving GGSN. |
211 | GTPv1 | Reject Rsp | All dynamic PDP addresses are occupied | Indicates that the GSN does not have a free dynamic PDP address to allocate any longer. |
212 | GTPv1 | Reject Rsp | No memory is available | Indicates that the GSN does not have enough memory to use. |
213 | GTPv1 | Reject Rsp | Relocation failure | Indicates that the SRNS relocation failed in the new SGSN side. |
214 | GTPv1 | Reject Rsp | Unknown mandatory extension header | Indicates s in a response message that the corresponding request included an extension header for which comprehension was required but unknown to the receiving end. |
215 | GTPv1 | Reject Rsp | Semantic error in the TFT operation | Used by the network or the MS to indicate that there is a semantic error in the TFT operation included in a secondary PDP context activation request or an MS-initiated PDP context modification or a network requested secondary PDP context activation. |
216 | GTPv1 | Reject Rsp | Syntactic error in the TFT operation | Used by the network or the MS to indicate that there is a syntactical error in the TFT operation included in a secondary PDP context activation request or an MS-initiated PDP context modification or a network requested secondary PDP context activation. |
217 | GTPv1 | Reject Rsp | Semantic errors in packet filter(s) | Used by the network or the MS to indicate that there is one or more semantic errors in packet filter(s) of the TFT included in a secondary PDP context activation request or an MS-initiated PDP context modification or a network requested secondary PDP context activation. |
218 | GTPv1 | Reject Rsp | Syntactic errors in packet filter(s) | Used by the network or the MS to indicate that there is one or more syntactical errors in packet filter(s) of the TFT included in a secondary PDP context activation request or an MS-initiated PDP context modification or a network requested secondary PDP context activation. |
219 | GTPv1 | Reject Rsp | Missing or unknown APN | Indicates, for example, when the GGSN does not support the Access Point Name. |
220 | GTPv1 | Reject Rsp | Unknown PDP address or PDP type | Indicates when the GGSN does not support the PDP type or the PDP address. |
221 | GTPv1 | Reject Rsp | PDP context without TFT already activated | Indication abnormal cases involving TFTs. The abnormal TFT cases and the use of the cause codes are defined in 3GPP TS 24.008. |
222 | GTPv1 | Reject Rsp | APN access denied – no subscription | Indicates that the GGSN has denied the user access to an APN because a subscription is required, but the subscriber does not have the necessary subscription. |
223 | GTPv1 | Reject Rsp | APN Restriction type incompatibility with currently active PDP Contexts | Conveys to an SGSN that a PDP Context was not allowed to be created or moved by the GGSN because if it had been created or moved, the rules for PDP Context coexistence as described in 3GPP TS 23.060 would have been broken. |
224 | GTPv1 | Reject Rsp | MS MBMS Capabilities Insufficient | Used by the SGSN to notify the GGSN that the MS MBMS Bearer Capabilities are less than the Required MBMS Bearer Capabilities. |
225 | GTPv1 | Reject Rsp | Invalid Correlation-ID | Indicates that the Correlation-ID was already in use in the SGSN. |
226 | GTPv1 | Reject Rsp | MBMS Bearer Context Superseded | Indicates that the SGSN has already established an MBMS bearer plane with another GGSN. |
227 | GTPv1 | Reject Rsp | Bearer Control Mode violation | Indicates that a request is violating the current Bearer Control Mode. |
228 | GTPv1 | Reject Rsp | Collision with network initiated request | Indicates that the UE-initiated request was rejected since the network has requested a secondary PDP context activation for the same service using a network-initiated procedure. |
229 | GTPv1 | Reject Rsp | APN Congestion | Indicates that the GGSN has detected congestion for the requested APN and performs overload control for that APN which does not allow the PDP Context to be created. |
230 | GTPv1 | Reject Rsp | Bearer handling not supported | Indicates that the request was rejected because the respective procedure (MS initiated Secondary PDP Context Activation procedure or the PDP Context Modification procedure), which is related to an established PDP context for LIPA or for SIPTO at the local network, is not supported. |
231 | GTPv1 | Reject Rsp | Target access restricted for the subscriber | Used by the MME/SGSN in the Context Response message to indicate that the target access is prohibited for the subscriber, based on the subscription profile. |
232 | GTPv1 | Reject Rsp | UE is temporarily not reachable due to power saving | |
233 | GTPv1 | Reject Rsp | Relocation failure due to NAS message redirection | |
234-240 | GTPv1 | Reject Rsp | For future use | |
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 |