Cause Value
|
Cause
|
Description
|
| 64 (GTPv2) |
Context Not Found
|
|
| 65 (GTPv2) |
Invalid Message Format. |
|
| 66 (GTPv2) |
Version not supported by next peer |
|
| 67 (GTPv2) |
Invalid length. |
|
| 68 (GTPv2) |
Service not supported |
|
| 69 (GTPv2) |
Mandatory IE incorrect |
|
| 70 (GTPv2) |
Mandatory IE missing |
|
| 71 (GTPv2) |
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) |
System failure |
|
| 73 (GTPv2) |
No resources available |
|
| 74 (GTPv2) |
Semantic error in the TFT operation |
|
| 75 (GTPv2) |
Syntactic error in the TFT operation |
|
| 76 (GTPv2) |
Semantic errors in packet filter(s) |
|
| 77 (GTPv2) |
Syntactic errors in packet filter(s) |
|
| 78 (GTPv2) |
Missing or unknown APN |
|
| 79 (GTPv2) |
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) |
GRE key not found. |
|
| 81 (GTPv2) |
Relocation failure. |
|
| 82 (GTPv2) |
Denied in RAT. |
|
| 83 (GTPv2) |
Preferred PDN type not supported. |
|
| 84 (GTPv2) |
All dynamic addresses are occupied. |
|
| 85 (GTPv2) |
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) |
Protocol type not supported. |
|
| 87 (GTPv2) |
UE not responding. |
This cause value may also be used by a Downlink Data Notification Failure Indication, which is an initial message. |
| 88 (GTPv2) |
UE refuses. |
|
| 89 (GTPv2) |
Service denied. |
This cause value may also be used by a Downlink Data Notification Failure Indication, which is an initial message. |
| 90 (GTPv2) |
Unable to page UE |
|
| 91 (GTPv2) |
No memory available |
|
| 92 (GTPv2) |
User authentication failed |
|
| 93 (GTPv2) |
APN access denied – no subscription |
|
| 94 (GTPv2) |
Request rejected (reason not specified) |
|
| 95 (GTPv2) |
P-TMSI Signature mismatch |
|
| 96 (GTPv2) |
IMSI/IMEI not known |
|
| 97 (GTPv2) |
Semantic error in the TAD operation |
|
| 98 (GTPv2) |
Syntactic error in the TAD operation |
|
| 99 (GTPv2) |
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) |
Remote peer not responding |
|
| 101 (GTPv2) |
Collision with network initiated request |
|
| 102 (GTPv2) |
Unable to page UE due to Suspension |
|
| 103 (GTPv2) |
Conditional IE missing |
|
| 104 (GTPv2) |
APN Restriction type Incompatible with currently active PDN connection |
|
| 105 (GTPv2) |
Invalid overall length of the triggered response message and a piggybacked initial message |
|
| 106 (GTPv2) |
Data forwarding not supported |
|
| 107 (GTPv2) |
Invalid reply from remote peer |
|
| 108 (GTPv2) |
Fallback to GTPv1 |
|
| 109 (GTPv2) |
Invalid peer |
|
| 110 (GTPv2) |
Temporarily rejected due to handover/TAU/RAU procedure in progress |
|
| 111 (GTPv2) |
Modifications not limited to S1-U bearers |
|
| 112 (GTPv2) |
Request rejected for a PMIPv6 reason
|
See 3GPP TS 29.275 |
| 113 (GTPv2) |
APN Congestion |
|
| 114 (GTPv2) |
Bearer handling not supported |
|
| 115 (GTPv2) |
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) |
Multiple PDN connections for a given APN not allowed |
|
| 117 (GTPv2) |
Target access restricted for the subscriber |
|
| 118 (GTPv2) |
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) |
MME/SGSN refuses due to VPLMN Policy |
|
| 120 (GTPv2) |
GTP-C Entity Congestiony |
|
| 121 (GTPv2) |
Late Overlapping Request |
|
| 122 (GTPv2) |
Timed out Request |
|
| 123 (GTPv2) |
UE is temporarily not reachable due to power saving |
|
| 124 (GTPv2) |
Relocation failure due to NAS message redirection |
|
| 125 (GTPv2) |
UE not authorised by OCS or external AAA Server |
|
| 126 (GTPv2) |
Multiple accesses to a PDN connection not allowed |
|
| 127 (GTPv2) |
Request rejected due to UE capability |
|
| 128 (GTPv2) |
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) |
5GC not allowed |
|
| 130-239 (GTPv2) |
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)”. |
| 192 (GTPv1) |
Non-existent |
Indicates a non-existent or an inactive PDP context. |
| 193 (GTPv1) |
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) |
IMSI/IMEI not known |
Indicates a non-existent MM context. |
| 195 (GTPv1) |
MS is GPRS Detached |
Indicates an idle MM context. |
| 196 (GTPv1) |
MS is not GPRS Responding |
May be used by SGSN to reject a Network-Requested PDP Context Activation. |
| 197 (GTPv1) |
MS Refuses |
May be used by SGSN to reject a Network-Requested PDP Context Activation. |
| 198 (GTPv1) |
Version not supported |
Returned when the recipient does not recognize the version number in the request message. |
| 199 (GTPv1) |
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) |
Service not supported |
Generic error indicating that the GSN does not support the requested service. |
| 201 (GTPv1) |
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) |
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) |
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) |
System failure |
Generic permanent error condition. |
| 205 (GTPv1) |
Roaming restriction |
Indicates that the SGSN cannot activate the requested PDP context because of the roaming restrictions. |
| 206 (GTPv1) |
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) |
GPRS connection suspended |
Indicates that the GPRS activities of the mobile station are suspended. |
| 208 (GTPv1) |
Authentication failure |
Indicates that the user authentication failed in the new SGSN. |
| 209 (GTPv1) |
User authentication failed |
Indicates that the external packet network has rejected the user’s service request. |
| 210 (GTPv1) |
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) |
All dynamic PDP addresses are occupied |
Indicates that the GSN does not have a free dynamic PDP address to allocate any longer. |
| 212 (GTPv1) |
No memory is available |
Indicates that the GSN does not have enough memory to use. |
| 213 (GTPv1) |
Relocation failure |
Indicates that the SRNS relocation failed in the new SGSN side. |
| 214 (GTPv1) |
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)
|
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)
|
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)
|
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) |
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) |
Missing or unknown APN |
Indicates, for example, when the GGSN does not support the Access Point Name. |
220 (GTPv1)
|
Unknown PDP address or PDP type
|
Indicates when the GGSN does not support the PDP type or the PDP address. |
| 221 (GTPv1) |
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)
|
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)
|
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)
|
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) |
Invalid Correlation-ID |
Indicates that the Correlation-ID was already in use in the SGSN. |
226 (GTPv1)
|
MBMS Bearer Context Superseded
|
Indicates that the SGSN has already established an MBMS bearer plane with another GGSN. |
227 (GTPv1)
|
Bearer Control Mode violation
|
Indicates that a request is violating the current Bearer Control Mode. |
| 228 (GTPv1) |
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) |
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)
|
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)
|
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) |
UE is temporarily not reachable due to power saving |
|
| 233 (GTPv1) |
Relocation failure due to NAS message redirection |
|
234 – 240 (GTPv1)
|
For future use |
|
241 – 251 (GTP’)
|
Reserved for GPRS charging protocol use (3GPP TS 32.295) |
|
252 (GTP’)
|
Request related to possibly duplicated packets already fulfilled
|
|
| 253 (GTP’) |
Request already fulfilled |
|
| 254 (GTP’) |
Sequence numbers of released/cancelled packets IE incorrect |
|
| 255 (GTP’) |
Request not fulfilled |
|
For general information on GTP messages and IEs refer to our GTPv1 Dictionary or GTPv2 Dictionary.