| Code
| Meaning
|
| 1 |
MT number is unknown in the MT network’s HLR |
| 2 |
MT number is unknown in the MT network’s HLR |
| 5 |
MT number is unknown in the MT network’s MSC |
| 9 |
MT number is classed as an illegal subscriber in the MT network’s MSC |
| 11 |
MT HLR sends back a “Teleservice not provisioned” error in responseto the SRI |
| 12 |
MT handset is listed as an Illegal device on the MSC. |
| 13 |
Customer is barred according to the MT HLR from receiving SMS |
| 15 |
MT customer is part of a CUG that is not allowed to receive SMS |
| 21 |
SMS not supported in the MT network. |
| 22 |
SMS not supported in the MT MSC |
| 31 |
MT handset is busy. The signalling control channel is in use. (Probably receiving another SMS at the same time) |
| 32 |
GPRS – As above |
| 34 |
System failure in the MT network. |
| 35 |
Data Missing in either the MT HLR or MSC |
| 36 |
Unexpected data value received in response to a FSM or SRI |
| 40 |
Memory capacity exceeded on the MT handset |
| 41 |
MT handset protocol error |
| 42 |
MT handset is not equipped to support SMS |
| 43 |
Short message type “0” not supported by the MT handset. |
| 44 |
MT network unable to replace the SMS on the MT customers’ handset |
| 45 |
Unspecified protocol error on the MT handset |
| 46 |
Message class not supported on the MT handset |
| 47 |
Unspecified DCS (Data coding scheme) error on the MT handset |
| 48 |
Transfer layer PDU not supported by MT handset |
| 49 |
SIM card full on MT handset |
| 50 |
MT handset’s SIM is unable to store the message |
| 51 |
Error in MT handset |
| 52 |
Memory capacity exceeded on the MT handset |
| 53 |
SIM application toolkit busy on the MS handset |
| 54 |
SIM data download error on the MT customer’s handset |
| 55 |
Unspecified MS handset error |
| 60 |
Absent subscriber. No reason known |
| 61 |
Absent subscriber due to phone being switched off |
| 62 |
Absent subscriber due to phone out of coverage/flat battery |
| 63 |
Absent subscriber due to roaming restriction/restricted area |
| 64 |
Absent subscriber due to being deregistered in the HLR |
| 65 |
Absent subscriber due to being purged in the VLR (off for 24+ hours) |
| 66 |
Absent subscriber (GPRS) cannot be paged by the SGSN |
| 67 |
Absent subscriber due to GPRS detached |
| 68 |
Absent subscriber due to deregistration in the HLR (GPRS) |
| 69 |
Absent subscriber due to GPRS MS purged in VLR |
| 70 |
Absent subscriber due to unidentified subscriber on the MSC that the FSM was sent to. |
| 71 |
Absent subscriber due to unidentified subscriber on the SGSN |
| 80 |
SS7 error. “Duplicate invoke ID” |
| 81 |
SS7 error. “Service not supported” – Suspect the carrier carrying the message does not support SMS |
| 82 |
SS7 error. “Mis typed parameter” |
| 83 |
SS7 error. “No response from peer” |
| 84 |
SS7 error. Returned when the C7 stack is congested |
| 85 |
SS7 error. Returned when the C7 stack is shutting down. |
| 86 |
SS7 error. “Unrecognised error” |
| 87 |
SS7 error. “Unexpected error” |
| 88 |
SS7 error. “Unexpected response from peer” |
| 89 |
SS7 error. “Service completion failure” |
| 90 |
SS7 error. “invalid response received” |
| 91 |
SS7 error. TCAP ERROR. Five possible causes:-
- The subsystem that the TCAP message is destined for is congested
- The subsystem number that the TCAP message is destined for has no application bound in
- The subsystem number that the TCAP message is destined for has not been provisioned on the peer SS7 stack
- The network is currently unavailable to transport TCAP Messages
- The network is currently congested
|
| 92 |
SS7 error. “Global Title Translation error” |
| 93 |
SS7 error. “Alphanumeric source address with more than 11 characters or message content not GSM compliant.” |
| 94 |
Barred from sending to this network. IMSI barring implemented by partner to stop submissions to this network. |
| 95 |
Message is blocked by gateway or network. May be due to origin addresses, destination address, message content or other. |
