GSM Error Codes
Validation error message may be a one or any combination of the ones below:
Error code – NIS (hex) | Error code – Messaging (hex) | Summary | Description | Usually caused by? | Causes retry? |
---|---|---|---|---|---|
0 | 0000 | No error | Delivery successful. | – | No |
1 | 0001 | unknownSubscriber | The MSISDN is not assigned by the operator at the moment. | Network | No |
2 | 0002 | unknownBaseStation | Network | No | |
3 | 0003 | unknownMSC | Network | No | |
5 | 0005 | unidentifiedSubscriber | Indicates that the MSC that should manage the MSISDN according to the HLR does not know the MSISDN. This is usually a sign for a technical issue inside of the destination network. | Network | Yes |
6 | 0006 | absentsubscriberSM | Network | Yes | |
7 | 0007 | unknownEquipment | Network | No | |
8 | 0008 | roamingNotAllowed | Network | Yes | |
9 | 0009 | illegalSubscriber | The MSISDN is not a subscriber of the target network or otherwise failed to authenticate correctly and is not allowed to receive SMS. This can indicate message filtering. | Network | No |
a | 000a | bearerServiceNotProvisioned | Network | Yes | |
b | 000b | teleserviceNotProvisioned | Usually occurs if the carrier disabled sending of SMS to the receiver MSISDN. | Network | No |
c | 000c | illegalEquipment | This error usually indicates that the receiver handset is not able to receive messages or special types of messages | Network | No |
d | 000d | callBarred | “Can indicate that the MSISDN was deactivated by the operator but other reasons were observed, too.” | Network | Yes |
e | 000e | forwardingViolation | Network | Yes | |
f | 000f | cug-Reject | Network | Yes | |
10 | 0010 | illegalSS-Operation | Network | Yes | |
11 | 0011 | ss-ErrorStatus | Network | Yes | |
12 | 0012 | ss-NotAvailable | Network | Yes | |
13 | 0013 | ss-SubscriptionViolation | Network | Yes | |
14 | 0014 | ss-Incompatibility | Network | Yes | |
15 | 0015 | facilityNotSupported | Can indicate that a network note does not support incoming SMS. This can indicate message filtering. | Network | Yes |
17 | 0017 | invalidTargetBaseStation | Network | Yes | |
18 | 0018 | noRadioResourceAvailable | Network | Yes | |
19 | 0019 | noHandoverNumberAvailable | Network | Yes | |
1a | 001a | subsequentHandoverFailure | Network | Yes | |
1b | 001b | Phone switched off | The phone is switched off. | Network | Yes |
1c | 001c | incompatibleTerminal | Network | Yes | |
1d | 001d | shortTermDenial | Network | Yes | |
1e | 001e | longTermDenial | Network | Yes | |
1f | 001f | SubscriberBusyForMT-SMS | The MSISDN received another message at the very same time and was therefore not able to receive the message that experienced the error. | Network | Yes |
20 | 0020 | Sm-DeliveryFailure | See 6XXX error codes. | Network | Yes |
21 | 0021 | messageWaitingListFull | Possible congestion in the target opeator’s HLR. May also be a bug in the target operator’s HLR. | Network | Yes |
22 | 0022 | systemFailure | “Generic error in destination network, can have multiple reasons.” | Network | Yes |
23 | 0023 | dataMissing | Network | No | |
24 | 0024 | unexpectedDataValue | The response of the destination operator for our signal was not as we expected it. This can indicate message filtering or a broken machine in the destination network. | Network | No |
25 | 0025 | pw-RegistrationFailure | Network | No | |
26 | 0026 | negativePW-Check | Network | Yes | |
27 | 0027 | noRoamingNumberAvailable | Network | No | |
28 | 0028 | tracingBufferFull | Network | Yes | |
2b | 002b | numberOfPW-AttemptsViolation | Network | Yes | |
2c | 002c | numberChanged | Network | Yes | |
2d | 002d | busySubscriber | Network | Yes | |
2e | 002e | noSubscriberReply | Network | Yes | |
2f | 002f | forwardingFailed | Network | Yes | |
30 | 0030 | or-NotAllowed | Network | Yes | |
31 | 0031 | ati-NotAllowed | Network | Yes | |
32 | 0032 | noGroupCallNumberAvailable | Network | Yes | |
33 | 0033 | resourceLimitation | Network | Yes | |
34 | 0034 | unauthorizedRequestingNetwork | Network | No | |
35 | 0035 | unauthorizedLCSClient | Network | No | |
36 | 0036 | positionMethodFailure | Network | Yes | |
3a | 003a | unknownOrUnreachableLCSClient | Network | Yes | |
47 | 0047 | unknownAlphabet | Network | No | |
48 | 0048 | ussd-Busy | Network | Yes | |
56 | 0056 | subscriberLocationReport | Network | Yes | |
2100 | 2100 | Unrecognized component | Network | Yes | |
2101 | 2101 | Mistyped component | Network | Yes | |
2102 | 2102 | Badly structured component | Network | Yes | |
2200 | 2200 | Duplicate invoke ID | Network | Yes | |
2201 | 2201 | Unrecognized operation | Network | Yes | |
2202 | 2202 | Mistyped parameter | Network | Yes | |
2203 | 2203 | Resource limitation | Congestion in the target network. | Network | Yes |
2204 | 2204 | Initiating release | Network | Yes | |
2205 | 2205 | Unrecognized linked ID | Network | Yes | |
2206 | 2206 | Linked response unexpected | Network | Yes | |
2207 | 2207 | Unexpected linked operation | Network | Yes | |
2300 | 2300 | Unrecognized invoke ID | Network | Yes | |
2301 | 2301 | Return Result unexpected | Network | Yes | |
2302 | 2302 | Mistyped parameter | Network | Yes | |
2400 | 2400 | Unrecognized invoke ID | Network | Yes | |
2401 | 2401 | Return Error unexpected | Network | Yes | |
2402 | 2402 | Unrecognized error | Network | Yes | |
2403 | 2403 | Unexpected error | Network | Yes | |
2404 | 2404 | Mistyped parameter | Network | No | |
6000 | 6000 | memoryCapacityExceeded | SIM card full | Network | Yes |
6xxx | 6xxx | Handset delivery failure | “6XXX error codes usually related to a handset or basestation issue but other reasons were observed, too.” | Network | Yes |
6001 | 6001 | equipmentProtocolError | Network | Yes | |
6002 | 6002 | equipmentNotSM-Equipped | Network | No | |
6003 | 6003 | unknownServiceCentre | Network | Yes | |
6004 | 6004 | sc-Congestion | Network | Yes | |
6005 | 6005 | invalidSME-Address | Network | Yes | |
6006 | 6006 | subscriberNotSC-Subscriber | Network | Yes | |
8000 | 8000 | Unrecognized message type | Network | Yes | |
8001 | 8001 | Unrecognized transaction ID | Network | Yes | |
8002 | 8002 | Badly formatted transaction portion | Network | Yes | |
8003 | 8003 | Incorrect transaction portion | Network | Yes | |
8004 | 8004 | Resource limitation | Congestion in target network. | Network | Yes |
8008 | 8008 | Node not reachable | “General error. May, among other reasons, be a congestion in target network, on SS7 layer or unknown MSISDN range.” | Network | Yes |
800b | 800b | Dialogue collision | Usually indicates congestions inside the destination network or en route. | Network | Yes |
8010 | 8010 | Node not reachable | “Routing error, can indicate, e.g., congestions or missing routing data inside the international SS7 network.” | Network | Yes |
a001 | a001 | No network response | A network node did not respond in time to tyntec. | Network | Yes |
a002 | a002 | Message too long | The message exceeds the maximum size. | tyntec | No |
cxxx | cxxx | “The Codes from c000 to c00f are compound codes, which can signal more then one state of the receiving number at once.” | ” The last digit gives the hexadecimal value for four bits that can all be set or not set. c000 means none of them are set, c00f means all are set. To find out which ones are set one has to find a sum of basic values that is equal to the compound value. E.g. c003 means c002 and c001 is true (1+2=3), c00d means c001, c004 and c008 is true (8+4+1=13=D)” | Network | Yes |
c000 | c000 | See description for error code “cxxx” | See description for error code “cxxx” | Network | Yes |
c001 | c001 | sc-AddressNotIncluded | SC address not included in message waiting list. | Network | Yes |
c002 | c002 | mnrf-Set | Mobile subscriber not reachable. | Network | Yes |
c003 | c003 | See description for error code “cxxx” | See description for error code “cxxx” | Network | Yes |
c004 | c004 | mcef-Set | SIM card full | Network | Yes |
c005 | c005 | See description for error code “cxxx” | See description for error code “cxxx” | Network | Yes |
c006 | c006 | See description for error code “cxxx” | See description for error code “cxxx” | Network | Yes |
c007 | c007 | See description for error code “cxxx” | See description for error code “cxxx” | Network | Yes |
c008 | c008 | mnrg-Set | Mobile station not reachable for GPRS. | Network | Yes |
c009 | c009 | See description for error code “cxxx” | See description for error code “cxxx” | Network | Yes |
c00a | c00a | See description for error code “cxxx” | See description for error code “cxxx” | Network | Yes |
c00b | c00b | See description for error code “cxxx” | See description for error code “cxxx” | Network | Yes |
c00d | c00d | See description for error code “cxxx” | See description for error code “cxxx” | Network | Yes |
d000 | d000 | Internal error | Routing information could not be processed. | tyntec | No |
d001 | d001 | Customer blocked | Customer is not allowed to send at all or receiver is currently roaming in a network which is not accessible to customer. | tyntec | No |
d002 | d002 | Destination blocked | The message could not be delivered because the destination operator is currently not available. | tyntec | No |
d004 | d004 | Destination temporarily not available | Operator network physically not reachable for a longer period. | Network | No |
d00a | d00a | Destination blocked and not reroutable | Target network currently not available or the destination operator is currently not accessible to customer. | Network | No |
d00c | d00c | Insufficient routing rights | The destination operator is not accessible to customer. | tyntec | No |
d010 | d010 | Destination blocked by customer | Destination network blocked by customers choice. | tyntec | No |
d020 | d020 | providerNotAvailable | “The destination network did not respond to tyntec, possibly due to congestion.” | Network | Yes |
e010 | e010 | Missing parameter | The destination operator responded to our signals with an empty signal. This can occur when a CDMA receiver is addressed. | Network | Yes |
e040 | e040 | Timeout | A network node en route or inside of the destination operator did not respond or did not respond in time. | Network | Yes |
e082 | e082 | Signalling error | Signalling error in the target network. | Network | Yes |
fc0a | fc0a | No network response | A network node did not respond in time to tyntec. | Network | Yes |
fc06 | fc06 | Subscriber has opted out from this messaging service | For the selected destinations, tyntec can indicate in the DLR if the subscriber has opted out from receiving messages for the respective service and as a consequence the message cannot be delivered. | Network | No |
fc07 | fc07 | Message rejected by Chat App | The destination Chat App rejected the message due to one or more incorrect parameters | Network | No |
fc08 | fc08 | Not a Chat App user | The recipient is not a user of the respective Chat App | Network | No |
ffdd | ffdd | Destination blocked | The message could not be delivered because the destination operator is currently not available. | tyntec | No |
ffde | ffde | Destination blocked | The message could not be delivered because the destination operator is currently not available. | tyntec | No |
ffdf | ffdf | Customer blocked | Customer is not allowed to send at all or receiver is currently roaming in a network which is not accessible to customer. | tyntec | No |
ffe0 | ffe0 | Customer blocked | Customer is not allowed to send at all or receiver is currently roaming in a network which is not accessible to customer. | tyntec | No |
ffe1 | ffe1 | Internal error | Routing information could not be processed. | tyntec | No |
ffe5 | ffe5 | Destination blocked by customer | Destination network is blocked by customers choice. | tyntec | No |
fff0 | fff0 | Destination blocked | The message could not be delivered because the destination operator is currently not available. | tyntec | No |
ffff | ffff | Internal error code | Message delivery failed. Either the message could not be delivered within the validity period (expired) or the delivery could not be carried out by the operator without further details being provided. | tyntec | No |
4xxx | 4xxx | Network specific error codes | “4XXX error codes can indicate that the route was blocked by the destination operator but other reasons were observed, too.” | Network | Yes |
81xx | 81xx | Incorrect message length | Network | Yes | |
82xx | 82xx | Missing mandatory IE | Network | Yes | |
83xx | 83xx | Incorrect IE length | Network | Yes | |
84xx | 84xx | Bad parameter value | Network | Yes | |
85xx | 85xx | No free dialogues | Network | Yes | |
86xx | 86xx | Invalid dialogue ID | Network | Yes | |
87xx | 87xx | Exceeded maximum length | Network | Yes | |
88xx | 88xx | Invalid parameter | Network | Yes | |
8axx | 8axx | Agent not registered | Network | Yes | |
89xx | 89xx | Inappropriate transport message | Network | Yes | |
8cxx | 8cxx | TC User not bound | Network | Yes | |
exxx | exxx | GSM adapter error | An error occurred in a GSM adapter with unclear reason. | Network | Yes |
e140 | e140 | Node not reachable | “Routing error, can indicate, e.g., congestions or missing routing data inside the international SS7 network.” | Network | Yes |