Here is a list of common error codes with a small description that may be returned in failed Delivery Reports.
If you are unable to resolve a message failure and need further help, please log into your online account on our website, go to Support and create a new support request for the service you are having difficulties with. Please try to include as much information as possible such as the destination number and a message ID. Please read the
article to learn more.
| Hex Code |
Description |
| 0000 |
no error |
| 0001 |
unknownSubscriber |
| 0002 |
unknownBaseStation |
| 0003 |
unknownMSC |
| 0005 |
unidentifiedSubscriber |
| 0006 |
absentsubscriberSM |
| 0007 |
unknownEquipment |
| 0008 |
Message expired, reason unknown |
| 0009 |
illegalSubscriber |
| 000a |
bearerServiceNotProvisioned |
| 000b |
teleserviceNotProvisioned |
| 000c |
illegalEquipment |
| 000d |
callBarred |
| 000e |
forwardingViolation |
| 000f |
cug-Reject |
| 0010 |
illegalSS-Operation |
| 0011 |
ss-ErrorStatus |
| 0012 |
ss-NotAvailable |
| 0013 |
ss-SubscriptionViolation |
| 0014 |
ss-Incompatibility |
| 0015 |
facilityNotSupported |
| 0017 |
invalidTargetBaseStation |
| 0018 |
noRadioResourceAvailable |
| 0019 |
noHandoverNumberAvailable |
| 001a |
subsequentHandoverFailure |
| 001b |
absentSubscriber |
| 001c |
incompatibleTerminal |
| 001d |
shortTermDenial |
| 001e |
longTermDenial |
| 001f |
subscriberBusyForMT-SMS |
| 0020 |
Permanent operator error |
| 0021 |
messageWaitingListFull |
| 0022 |
systemFailure |
| 0023 |
Absent subscriber permanent - incorrect/invalid MSISDN usually |
| 0024 |
Absent subscriber temporary - phone switched off or out of reach |
| 0025 |
Operator network failure |
| 0026 |
Temporary handset error - Memory exceeded or busy for MT delivery |
| 0027 |
Permanent handset error - Handset unable to receive this type of message |
| 0028 |
tracingBufferFull |
| 002b |
numberOfPW-AttemptsViolation |
| 002c |
numberChanged |
| 002d |
busySubscriber |
| 002e |
noSubscriberReply |
| 002f |
forwardingFailed |
| 0030 |
or-NotAllowed |
| 0031 |
ati-NotAllowed |
| 0032 |
noGroupCallNumberAvailable |
| 0033 |
resourceLimitation |
| 0034 |
unauthorizedRequestingNetwork |
| 0035 |
unauthorizedLCSClient |
| 0036 |
positionMethodFailure |
| 003a |
unknownOrUnreachableLCSClient |
| 0047 |
unknownAlphabet |
| 0048 |
ussd-Busy |
| 0056 |
subscriberLocationReport |
| 00ff |
Unknown error |
| 0400 |
Subscriber absent |
| 0401 |
Equipment memory capacity exceeded |
| 0402 |
Equipment protocol error |
| 0403 |
Equipment not supported |
| 0404 |
Equipment not SM equipped |
| 0405 |
Unknown service center |
| 0406 |
Service center congestion |
| 0407 |
Invalid SME address |
| 0408 |
Subscriber not SC subscriber |
| 0409 |
Unknown subscriber |
| 040a |
Illegal subscriber |
| 040b |
Teleservice not provisioning |
| 040c |
Illegal equipment |
| 040d |
Call barred |
| 040e |
Facility not supported |
| 040f |
Subscriber busy for MT short message |
| 0410 |
System failure |
| 0411 |
Message waiting list full |
| 0412 |
Data missing |
| 0413 |
Unexpected data value |
| 0414 |
Resource limitation |
| 0415 |
Initiating release |
| 0416 |
Unknown alphabet |
| 0417 |
USSD busy |
| 0418 |
Duplicated invoke ID |
| 0419 |
Not supported service |
| 041a |
Mistyped parameter |
| 041b |
Unexpected response from peer |
| 041c |
Service completion failure |
| 041d |
No response from peer |
| 041e |
Invalid response received |
| 04ff |
Roaming level not supported |
| 2100 |
Unrecognized component |
| 2101 |
Mistyped component |
| 2102 |
Badly structured component |
| 2200 |
Duplicate invoke ID |
| 2201 |
Unrecognized operation |
| 2202 |
Mistyped parameter |
| 2203 |
Resource limitation |
| 2204 |
Initiating release |
| 2205 |
Unrecognized linked ID |
| 2206 |
Linked response unexpected |
| 2207 |
Unexpected linked operation |
| 2300 |
Unrecognized invoke ID |
| 2301 |
Return Result unexpected |
| 2302 |
Mistyped parameter |
| 2400 |
Unrecognized invoke ID |
| 2401 |
Return Error unexpected |
| 2402 |
Unrecognized error |
| 2403 |
Unexpected error |
| 2404 |
Mistyped parameter |
| 6000 |
memoryCapacityExceeded |
| 6001 |
equipmentProtocolError |
| 6002 |
equipmentNotSM-Equipped |
| 6003 |
unknownServiceCentre |
| 6004 |
sc-Congestion |
| 6005 |
invalidSME-Address |
| 6006 |
subscriberNotSC-Subscriber |
| 8000 |
Unrecognized message type |
| 8001 |
Unrecognized transaction ID |
| 8002 |
Badly formatted transaction portion |
| 8003 |
Incorrect transaction portion |
| 8004 |
Resource limitation |
| 800b |
Dialogue collision |
| 8010 |
Node not reachable |
| 81xx |
Incorrect message length |
| 82xx |
Missing mandatory IE |
| 83xx |
Incorrect IE length |
| 84xx |
Bad parameter value |
| 85xx |
No free dialogues |
| 86xx |
Invalid dialogue ID |
| 87xx |
Exceeded maximum length |
| 88xx |
Invalid parameter |
| 89xx |
Inappropriate transport message |
| 8axx |
Agent not registered |
| 8bxx |
Dialogue collision |
| 8cxx |
TC User not bound |
| c001 |
sc-AddressNotIncluded |
| c002 |
mnrf-Set |
| c004 |
mcef-Set |
| c008 |
mnrg-Set |
| e001 |
The dialogue has received a MAP-DELIMITER unexpectedly. |
| e002 |
The dialogue has received a MAP-SERVICE-REQUEST unexpectedly. |
| e010 |
Could not decode an ASN.1 encoded parameter. |
| e011 |
Could not ASN.1 encode a parameter. |
| e020 |
Dialogue queue size exceeded. |
| e040 |
Dialogue timed out, i.e. the far side did not respond or there is a network problem. |
| e080 |
Invalid delivery outcome (< 0 or > 2 on any MAP level, or 1 on MAP 1) |
| e081 |
Invalid destination address |
| e1xx |
Could not open MAP dialogue; the lowest 8 bits contain the code returned by TDAPI |
will still return a delivery receipt when a message has been accepted or if the message is buffered in the
, for example if the handset is switched off. This will use the UNKNOWN state and sets the buffered special parameter in the deliver_sm under
3.4.