Event Error Codes
This section contains a list of the error codes returned in the code attribute of Data Warehouse (DWH) event strings in JSON format. Error codes are grouped by the core network node that generates them.
HLR/HSS/SMSC/GMSC Error Codes
The error codes returned by HLR, HSS, SMSC, and GMSC nodes are listed in this table
| Result Description | Error Code |
|---|---|
| Success | 0 |
| unknownSubscriber | 1 |
| unknownMSC | 3 |
| unidentifiedSubscriber | 5 |
| absentSubscriberSM | 6 |
| unknownEquipment | 7 |
| roamingNotAllowed | 8 |
| illegalSubscriber | 9 |
| bearerServiceNotProvisioned | 10 |
| teleserviceNotProvisioned | 11 |
| illegalEquipment | 12 |
| callBarred | 13 |
| forwardingViolation | 14 |
| cug-Reject | 15 |
| illegalSS-Operation | 16 |
| ss-ErrorStatus | 17 |
| ss-NotAvailable | 18 |
| ss-SubscriptionViolation | 19 |
| ss-Incompatibility | 20 |
| facilityNotSupported | 21 |
| ongoingGroupCall | 22 |
| noHandoverNumberAvailable | 25 |
| subsequentHandoverFailure | 26 |
| absentSubscriber | 27 |
| incompatibleTerminal | 28 |
| shortTermDenial | 29 |
| longTermDenial | 30 |
| subscriberBusyForMT-SMS | 31 |
| sm-DeliveryFailure | 32 |
| messageWaitingListFull | 33 |
| systemFailure | 34 |
| dataMissing | 35 |
| unexpectedDataValue | 36 |
| pw-RegistrationFailure | 37 |
| negativePW-Check | 38 |
| noRoamingNumberAvailable | 39 |
| tracingBufferFull | 40 |
| targetCellOutsideGroupCallArea | 42 |
| numberOfPW-AttemptsViolation | 43 |
| numberChanged | 44 |
| busySubscriber | 45 |
| noSubscriberReply | 46 |
| forwardingFailed | 47 |
| or-NotAllowed | 48 |
| ati-NotAllowed | 49 |
| noGroupCallNumberAvailable | 50 |
| resourceLimitation | 51 |
| unauthorizedRequestingNetwork | 52 |
| unauthorizedLCSClient | 53 |
| positionMethodFailure | 54 |
| unknownOrUnreachableLCSClient | 58 |
| mm-EventNotSupported | 59 |
| atsi-NotAllowed | 60 |
| atm-NotAllowed | 61 |
| informationNotAvailable | 62 |
| unknownAlphabet | 71 |
| ussd-Busy | 72 |
| system error | 255 |
PGW/GGSN Error Codes
The error codes returned by PGW and GGSN nodes are listed in this table.
| Result Description | Error Code |
|---|---|
| Reserved | 1 |
| Local Detach | 2 |
| Complete Detach | 3 |
| RAT changed from 3GPP to Non-3GPP | 4 |
| ISR deactivation | 5 |
| Error Indication received from RNC/eNodeB/S4-SGSN/MME | 6 |
| IMSI Detach Only | 7 |
| Reactivation Requested | 8 |
| PDN reconnection to this APN disallowed | 9 |
| Access changed from Non-3GPP to 3GPP | 10 |
| PDN connection inactivity timer expires | 11 |
| PGW not responding | 12 |
| Network Failure | 13 |
| QoS parameter mismatch | 14 |
| Spare. This value range shall be used by Cause values in an initial/request message. | 15 |
| Request accepted | 16 |
| Request accepted partially | 17 |
| New PDN type due to network preference | 18 |
| New PDN type due to single address bearer only | 19 |
| Spare. This value range shall be used by Cause values in an acceptance response/triggered message. Rejection in a Response/triggered message. | 20 to 63 |
| Context Not Found | 64 |
| Invalid Message Format | 65 |
| Version not supported by next peer | 66 |
| Invalid length | 67 |
| Service not supported | 68 |
| Mandatory IE incorrect | 69 |
| Mandatory IE missing | 70 |
| Shall not be used. See NOTE 2 and NOTE 3. | 71 |
| System failure | 72 |
| No resources available | 73 |
| Semantic error in the TFT operation | 74 |
| Syntactic error in the TFT operation | 75 |
| Semantic errors in packet filter(s) | 76 |
| Syntactic errors in packet filter(s) | 77 |
| Missing or unknown APN | 78 |
| Shall not be used. See NOTE 2 and NOTE 3. | 79 |
| GRE key not found | 80 |
| Relocation failure | 81 |
| Denied in RAT | 82 |
| Preferred PDN type not supported | 83 |
| All dynamic addresses are occupied | 84 |
| UE context without TFT already activated. See NOTE 6. | 85 |
| Protocol type not supported | 86 |
| UE not responding. See NOTE 7. | 87 |
| UE refuses | 88 |
| Service denied. See NOTE 7. | 89 |
| Unable to page UE | 90 |
| No memory available | 91 |
| User authentication failed | 92 |
| APN access denied – no subscription | 93 |
| Request rejected (reason not specified) | 94 |
| P-TMSI Signature mismatch | 95 |
| IMSI/IMEI not known | 96 |
| Semantic error in the TAD operation | 97 |
| Syntactic error in the TAD operation | 98 |
| Shall not be used. See NOTE 2 and NOTE 3. | 99 |
| Remote peer not responding | 100 |
| Collision with network initiated request | 101 |
| Unable to page UE due to Suspension | 102 |
| Conditional IE missing | 103 |
| APN Restriction type incompatible with currently active PDN connection | 104 |
| Invalid overall length of the triggered response message and a piggybacked initial message | 105 |
| Data forwarding not supported | 106 |
| Invalid reply from remote peer | 107 |
| Fallback to GTPv1 | 108 |
| Invalid peer | 109 |
| Temporarily rejected due to handover/TAU/RAU procedure in progress | 110 |
| Modifications not limited to S1-U bearers | 111 |
| Request rejected for a PMIPv6 reason (see 3GPP TS 29.275) | 112 |
| APN Congestion | 113 |
| Bearer handling not supported | 114 |
| UE already re-attached. See NOTE 7. | 115 |
| Multiple PDN connections for a given APN not allowed | 116 |
| Target access restricted for the subscriber | 117 |
| Shall not be used. See NOTE 2 and NOTE 3. | 118 |
| MME/SGSN refuses due to VPLMN Policy | 119 |
| GTP-C Entity Congestion | 120 |
| Late Overlapping Request | 121 |
| Timed out Request | 122 |
| UE is temporarily not reachable due to power saving | 123 |
| Relocation failure due to NAS message redirection | 124 |
| UE not authorised by OCS or external AAA Server | 125 |
| Multiple accesses to a PDN connection not allowed | 126 |
| Request rejected due to UE capability | 127 |
| S1-U Path Failure | 128 |
| 5GC not allowed | 129 |
| Spare for future use | 130 to 239 |
| Spare for future use | 240 to 255 |
| DDOS on session | 250 |
Diameter Error Codes
The error codes returned for Diameter protocol events are listed in this table
| Result Description | Error Code |
|---|---|
| Diameter success | 2001 |
| Diameter limited success | 2002 |
| Unsupported command | 3001 |
| Unable to deliver | 3002 |
| Realm not served | 3003 |
| Too busy | 3004 |
| Loop detected | 3005 |
| Redirect Indication | 3006 |
| Application unsupported | 3007 |
| Invalid HDR Bits | 3008 |
| Invalid AVP Bits | 3009 |
| Unknown peer | 3010 |
| Diameter user unknown | 5001 |
| Diameter identities don't match | 5002 |
| Diameter identity not registered | 5003 |
| Diameter roaming not allowed | 5004 |
| Diameter identity already registered | 5005 |
| Diameter auth scheme not supported | 5006 |
| Diameter in assignment type | 5007 |
| Diameter too much data | 5008 |
| Diameter not supported user data | 5009 |
| Diameter feature unsupported | 5011 |
| Diameter user data not recognized | 5100 |
| Diameter operation not allowed | 5101 |
| Diameter user data cannot be read | 5102 |
| Diameter user data cannot be modified | 5103 |
| Diameter user data cannot be notified | 5104 |
| Diameter transparent data out of sync | 5105 |
| Diameter subs data absent | 5106 |
| Diameter no subscription to data | 5107 |
| Diameter dsai not available | 5108 |
| Diameter unknown eps subscription | 5420 |
| Diameter rat not allowed | 5421 |
| Diameter equipment unknown | 5422 |
| Diameter unknown serving node | 5423 |
| Diameter user no non-3GPP subscription | 5450 |
| Diameter user no APN subscription | 5451 |
| Diameter rat type not allowed | 5452 |