| 000 | 000 | No error | No error / success |
| 001 | 001 | Unassigned (unallocated) number | This cause indicates that the destination requested by the Mobile Station cannot be reached because, although the number is in a valid format, it is not currently assigned (allocated). |
| 010 | 00A | Call barred | This cause indicates that the outgoing call barred service applies to the short message service for the called destination. |
| 017 | 011 | Network failure | This cause is sent to the Mobile Station if the MSC cannot service a Mobile Station generated request because of PLMN failures, e.g. problems in MAP. |
| 021 | 015 | Short message transfer rejected | This cause indicates that the equipment sending this cause does not wish to accept this short message, although it could have accepted the short message since the equipment sending this cause is neither busy nor incompatible. |
| 022 | 016 | Congestion | This cause is sent if the service request cannot be actioned because of congestion (e.g. no channel, facility busy/congested etc.). |
| 023 | 017 | Memory capacity exceeded | This cause indicates that the mobile station cannot store the incoming short message due to lack of storage capacity. |
| 027 | 01B | Absent subscriber | This cause indicates that the destination indicated by the Mobile Station cannot be reached because the interface to the destination is not functioning correctly. The term “not functioning correctly” indicates that a signalling message was unable to be delivered to the remote user; e.g., a physical layer or data link layer failure at the remote user, user equipment off-line, etc. |
| 028 | 01C | Unidentified subscriber | This cause indicates that the subscriber is not registered in the PLMN (i.e. IMSI not known). |
| 029 | 01D | Facility rejected | This cause indicates that the facility requested by the Mobile Station is not supported by the PLMN. |
| 030 | 01E | Unknown subscriber | This cause indicates that the subscriber is not registered in the HLR (i.e. IMSI or directory number is not allocated to a subscriber). |
| 038 | 026 | Network out of order | This cause indicates that the network is not functioning correctly and that the condition is likely to last a relatively long period of time; e.g., immediately reattempting the short message transfer is not likely to be successful. |
| 041 | 029 | Temporary failure | This cause indicates that the network is not functioning correctly and that the condition is not likely to last a long period of time; e.g., the Mobile Station may wish to try another short message transfer attempt almost immediately. |
| 042 | 02A | Congestion | This cause indicates that the short message service cannot be serviced because of high traffic. |
| 069 | 045 | Requested facility not implemented | This cause indicates that the network is unable to provide the requested short message service. |
| 255 | 0FF | Unspecified error cause | This cause indicates that there has been an unidentified or unspecified error provided from the next hop. |
| 800 | 320 | Insufficient funds | Either no prepaid credits anymore or post-pay credit limit reached. |
| 801 | 321 | Anti-Spam rejection | This cause indicates that the message was rejected due to anti-spam protection regulations. |
| 802 | 322 | Empty message | The message was blocked due to the reason that it had no content. |
| 803 | 323 | Anti-Loop rejection | This cause indicates that the message was rejected due to anti-loop protection mechanism. |
| 804 | 324 | No route available | This cause indicates that temporary no supporting route is available. |
| 805 | 325 | Multi-Sent rejection | This cause indicates that the message was rejected due to the fact that it was sent several times in a very short time frame. |
| 806 | 326 | Invalid recipient format | This cause indicates that the message was rejected due to an invalid recipient format; e.g. invalid length. |
| 807 | 327 | Invalid sender | This cause indicates that the message was rejected due an invalid sender; e.g. wrong alpha-numeric format or invalid characters. |
| 808 | 328 | Number lookup failed | This cause indicates that the message could not be routed because the number lookup (e.g. MNP or HLR/SRI) failed or returned an unknown error. |
| 809 | 329 | Privacy | This cause indicates that the message was blocked due to privacy protection of the subscriber (e.g. when trying to send a silent message without permission) |
| 810 | 32A | Destination not covered | This cause indicates that the message was rejected because the destination network is not on the coverage list for the current account. The message will not be charged. We advise to re-check the latest coverage sheet provided by either your account manager or pricing team. |
| 811 | 32B | Invalid message length | This cause indicates that the message was rejected because the content length exploits the allowed standards (e.g. concat or wap exploits). |
| 812 | 32C | Queue full | This cause indicates that the message was rejected because the queue towards the next hop seems to be full. We advise to either retry a few seconds later or to use a backup account / gateway. This error is also typical for SIM routes where the TPS is reached over a longer period. |
| 813 | 32D | Queue on device full | This cause indicates that the incoming message queue on the handset or modem is full. Usually we will retry several times to redeliver. |
| 814 | 32E | Blocked recipient | This cause indicates that the message toward the recipient was blocked. This can have several reasons, e.g. blacklisted sender, blacklisted receiver, content filter, etc. |
| 815 | 32F | Relay route used | This indicates that a relay or backup route was taken, e.g. due to the fact that primary route was queuing or had similar capacity issues. Usually a backup or relay route is of equal or better quality as the primary route. |
| 816 | 330 | Validity Expired | This indicates that the validity period of the message was expired before the message could actually be delivered. |
| 899 | 383 | Temporary platform failure | This cause indicates that the message was rejected because we have temporary platform issue where the engineers will be working on immediately. |