Gsm error codes

Коды ошибок запуска программы и отправки СМС:

        0           Сообщение отправлено, и модем/телефон подтвердил 
                    успешную отправку сообщения.

        2           На компьютере нет указанного последовательного порта или
                    не найден указанный конф. файл.

        5           Не удалось открыть указанный порт COM ("нет доступа",
                    скорее всего, порт был занят другой программой).

       87           Ошибка в параметрах запуска программы или параметрах смс.

      121           Нет ответа от модема.

     1460           Нет ответа от модема (тайм-аут)

     7012           Модем не найден 

536870912           Ошибка отправки СМС.

536870929           Модем отклонил попытку отправки сообщения

536870931           Модем сообщил об ошибке отправки

536870932           Модем не сообщил результат отправки

536870933           Получен неправильный ответ модема

536870934           Ошибка ответа модема 

536870935           Одна или несколько частей длинного сообщения не были 
                    отправлены из-за ошибок (этот код ошибки только для длинных 
                    сообщений)

536870936           Все части длинного сообщения не были отправлены из-за ошибок 
                    (этот код ошибки только для длинных сообщений)

Коды ошибок CME ERROR – GSM Equipment related codes

CME ERROR: 0    Phone failure
CME ERROR: 1 	 No connection to phone
CME ERROR: 2 	 Phone adapter link reserved
CME ERROR: 3 	 Operation not allowed
CME ERROR: 4 	 Operation not supported
CME ERROR: 5 	 PH_SIM PIN required
CME ERROR: 6 	 PH_FSIM PIN required
CME ERROR: 7 	 PH_FSIM PUK required
CME ERROR: 10 	 SIM not inserted
CME ERROR: 11 	 SIM PIN required
CME ERROR: 12 	 SIM PUK required
CME ERROR: 13 	 SIM failure
CME ERROR: 14 	 SIM busy
CME ERROR: 15 	 SIM wrong
CME ERROR: 16 	 Incorrect password
CME ERROR: 17 	 SIM PIN2 required
CME ERROR: 18 	 SIM PUK2 required
CME ERROR: 20 	 Memory full
CME ERROR: 21 	 Invalid index
CME ERROR: 22 	 Not found
CME ERROR: 23 	 Memory failure
CME ERROR: 24 	 Text string too long
CME ERROR: 25 	 Invalid characters in text string
CME ERROR: 26 	 Dial string too long
CME ERROR: 27 	 Invalid characters in dial string
CME ERROR: 30 	 No network service
CME ERROR: 31 	 Network timeout
CME ERROR: 32 	 Network not allowed, emergency calls only
CME ERROR: 40 	 Network personalization PIN required
CME ERROR: 41 	 Network personalization PUK required
CME ERROR: 42 	 Network subset personalization PIN required
CME ERROR: 43 	 Network subset personalization PUK required
CME ERROR: 44 	 Service provider personalization PIN required
CME ERROR: 45 	 Service provider personalization PUK required
CME ERROR: 46 	 Corporate personalization PIN required
CME ERROR: 47 	 Corporate personalization PUK required
CME ERROR: 48 	 PH-SIM PUK required
CME ERROR: 100 	 Unknown error
CME ERROR: 103 	 Illegal MS
CME ERROR: 106 	 Illegal ME
CME ERROR: 107 	 GPRS services not allowed
CME ERROR: 111 	 PLMN not allowed
CME ERROR: 112 	 Location area not allowed
CME ERROR: 113 	 Roaming not allowed in this location area
CME ERROR: 126 	 Operation temporary not allowed
CME ERROR: 132 	 Service operation not supported
CME ERROR: 133 	 Requested service option not subscribed
CME ERROR: 134 	 Service option temporary out of order
CME ERROR: 148 	 Unspecified GPRS error
CME ERROR: 149 	 PDP authentication failure
CME ERROR: 150 	 Invalid mobile class
CME ERROR: 256 	 Operation temporarily not allowed
CME ERROR: 257 	 Call barred
CME ERROR: 258 	 Phone is busy
CME ERROR: 259 	 User abort
CME ERROR: 260 	 Invalid dial string
CME ERROR: 261 	 SS not executed
CME ERROR: 262 	 SIM Blocked
CME ERROR: 263 	 Invalid block
CME ERROR: 772 	 SIM powered down

Коды ошибок CMS Error – GSM Network related codes

CMS ERROR: 1     Unassigned number
CMS ERROR: 8     Operator determined barring
CMS ERROR: 10    Call bared
CMS ERROR: 21    Short message transfer rejected
CMS ERROR: 27    Destination out of service
CMS ERROR: 28    Unindentified subscriber
CMS ERROR: 29    Facility rejected
CMS ERROR: 30    Unknown subscriber
CMS ERROR: 38    Network out of order
CMS ERROR: 41    Temporary failure
CMS ERROR: 42    Congestion
CMS ERROR: 47    Recources unavailable
CMS ERROR: 50    Requested facility not subscribed
CMS ERROR: 69    Requested facility not implemented
CMS ERROR: 81    Invalid short message transfer reference value
CMS ERROR: 95    Invalid message unspecified
CMS ERROR: 96    Invalid mandatory information
CMS ERROR: 97    Message type non existent or not implemented
CMS ERROR: 98    Message not compatible with short message protocol
CMS ERROR: 99    Information element non-existent or not implemente
CMS ERROR: 111   Protocol error, unspecified
CMS ERROR: 127   Internetworking , unspecified
CMS ERROR: 128   Telematic internetworking not supported
CMS ERROR: 129   Short message type 0 not supported
CMS ERROR: 130   Cannot replace short message
CMS ERROR: 143   Unspecified TP-PID error
CMS ERROR: 144   Data code scheme not supported
CMS ERROR: 145   Message class not supported
CMS ERROR: 159   Unspecified TP-DCS error
CMS ERROR: 160   Command cannot be actioned
CMS ERROR: 161   Command unsupported
CMS ERROR: 175   Unspecified TP-Command error
CMS ERROR: 176   TPDU not supported
CMS ERROR: 192   SC busy
CMS ERROR: 193   No SC subscription
CMS ERROR: 194   SC System failure
CMS ERROR: 195   Invalid SME address
CMS ERROR: 196   Destination SME barred
CMS ERROR: 197   SM Rejected-Duplicate SM
CMS ERROR: 198   TP-VPF not supported
CMS ERROR: 199   TP-VP not supported
CMS ERROR: 208   D0 SIM SMS Storage full
CMS ERROR: 209   No SMS Storage capability in SIM
CMS ERROR: 210   Error in MS
CMS ERROR: 211   Memory capacity exceeded
CMS ERROR: 212   Sim application toolkit busy
CMS ERROR: 213   SIM data download error
CMS ERROR: 255   Unspecified error cause
CMS ERROR: 300   ME Failure
CMS ERROR: 301   SMS service of ME reserved
CMS ERROR: 302   Operation not allowed
CMS ERROR: 303   Operation not supported
CMS ERROR: 304   Invalid PDU mode parameter
CMS ERROR: 305   Invalid Text mode parameter
CMS ERROR: 310   SIM not inserted
CMS ERROR: 311   SIM PIN required
CMS ERROR: 312   PH-SIM PIN required
CMS ERROR: 313   SIM failure
CMS ERROR: 314   SIM busy
CMS ERROR: 315   SIM wrong
CMS ERROR: 316   SIM PUK required
CMS ERROR: 317   SIM PIN2 required
CMS ERROR: 318   SIM PUK2 required
CMS ERROR: 320   Memory failure
CMS ERROR: 321   Invalid memory index
CMS ERROR: 322   Memory full
CMS ERROR: 330   SMSC address unknown
CMS ERROR: 331   No network service
CMS ERROR: 332   Network timeout
CMS ERROR: 340   No +CNMA expected
CMS ERROR: 500   Unknown error
CMS ERROR: 512   User abort
CMS ERROR: 513   Unable to store
CMS ERROR: 514   Invalid Status
CMS ERROR: 515   Device busy or Invalid Character in string
CMS ERROR: 516   Invalid length
CMS ERROR: 517   Invalid character in PDU
CMS ERROR: 518   Invalid parameter
CMS ERROR: 519   Invalid length or character
CMS ERROR: 520   Invalid character in text
CMS ERROR: 521   Timer expired
CMS ERROR: 522   Operation temporary not allowed
CMS ERROR: 532   SIM not ready
CMS ERROR: 534   Cell Broadcast error unknown
CMS ERROR: 535   Protocol stack busy
CMS ERROR: 538   Invalid parameter

Status of a previously submitted SMS-SUBMIT (статус отправленного сообщения SMS-SUBMIT)

Short message transaction completed

0000000          Short message received by the SME
0000001          Short message forwarded by the SC to the SME but the SC is
                 unable to confirm delivery
0000010          Short message replaced by the SC

Reserved values

0000011..0001111 Reserved
0010000..0011111 Values specific to each SC

Temporary error, SC still trying to transfer SM

0100000          Congestion
0100001          SME busy
0100010          No response from SME
0100011          Service rejected
0100100          Quality of service not available
0100101          Error in SME
0100110..0101111 Reserved
0110000..0111111 Values specific to each SC

Permanent error, SC is not making any more transfer attempts

1000000          Remote procedure error
1000001          Incompatible destination
1000010          Connection rejected by SME
1000011          Not obtainable
1000100          Quality of service not available
1000101          No interworking available
1000110          SM Validity Period Expired
1000111          SM Deleted by originating SME
1001000          SM Deleted by SC Administration
1001001          SM does not exist (The SM may have previously existed in
                 the SC but the SC no longer has knowledge of it or the SM
                 may never have previously existed in the SC)
1001010..1001111 Reserved
1010000..1011111 Values specific to each SC

Temporary error, SC is not making any more transfer attempts

1100000          Congestion
1100001          SME busy
1100010          No response from SME
1100011          Service rejected
1100100          Quality of service not available
1100101          Error in SME
1100110..1101001 Reserved
1101010..1101111 Reserved
1110000..1111111 Values specific to each SC

---

There are two types of GSM error codes: CMS Error codes and CME Error codes that your GSM may return when sending an SMS.

The CMS error codes start with ‘+CMS Error:‘ and are always network related errors. The CME error codes start with ‘+CME Error:‘ and are always device (equipment) related errors.

CME Errors (GSM equipment errors)

CME Error	Description
0	Phone failure
1	No connection to phone
2	Phone adapter link reserved
3	Operation not allowed
4	Operation not supported
5	PH_SIM PIN required
6	PH_FSIM PIN required
7	PH_FSIM PUK required
10	SIM not inserted
11	SIM PIN required
12	SIM PUK required
13	SIM failure
14	SIM busy
15	SIM wrong
16	Incorrect password
17	SIM PIN2 required
18	SIM PUK2 required
20	Memory full
21	Invalid index
22	Not found
23	Memory failure
24	Text string too long
25	Invalid characters in text string
26	Dial string too long
27	Invalid characters in dial string
30	No network service
31	Network timeout
32	Network not allowed, emergency calls only
40	Network personalization PIN required
41	Network personalization PUK required
42	Network subset personalization PIN required
43	Network subset personalization PUK required
44	Service provider personalization PIN required
45	Service provider personalization PUK required
46	Corporate personalization PIN required
47	Corporate personalization PUK required
48	PH-SIM PUK required
100	Unknown error
103	Illegal MS
106	Illegal ME
107	GPRS services not allowed
111	PLMN not allowed
112	Location area not allowed
113	Roaming not allowed in this location area
126	Operation temporary not allowed
132	Service operation not supported
133	Requested service option not subscribed
134	Service option temporary out of order
148	Unspecified GPRS error
149	PDP authentication failure
150	Invalid mobile class
256	Operation temporarily not allowed
257	Call barred
258	Phone is busy
259	User abort
260	Invalid dial string
261	SS not executed
262	SIM Blocked
263	Invalid block
772	SIM powered down

CMS Errors (GSM Network errors)

CMS Error	Description
1	Unassigned number
8	Operator determined barring
10	Call bared
21	Short message transfer rejected
27	Destination out of service
28	Unindentified subscriber
29	Facility rejected
30	Unknown subscriber
38	Network out of order
41	Temporary failure
42	Congestion
47	Recources unavailable
50	Requested facility not subscribed
69	Requested facility not implemented
81	Invalid short message transfer reference value
95	Invalid message unspecified
96	Invalid mandatory information
97	Message type non existent or not implemented
98	Message not compatible with short message protocol
99	Information element non-existent or not implemente
111	Protocol error, unspecified
127	Internetworking , unspecified
128	Telematic internetworking not supported
129	Short message type 0 not supported
130	Cannot replace short message
143	Unspecified TP-PID error
144	Data code scheme not supported
145	Message class not supported
159	Unspecified TP-DCS error
160	Command cannot be actioned
161	Command unsupported
175	Unspecified TP-Command error
176	TPDU not supported
192	SC busy
193	No SC subscription
194	SC System failure
195	Invalid SME address
196	Destination SME barred
197	SM Rejected-Duplicate SM
198	TP-VPF not supported
199	TP-VP not supported
208	D0 SIM SMS Storage full
209	No SMS Storage capability in SIM
210	Error in MS
211	Memory capacity exceeded
212	Sim application toolkit busy
213	SIM data download error
255	Unspecified error cause
300	ME Failure
301	SMS service of ME reserved
302	Operation not allowed
303	Operation not supported
304	Invalid PDU mode parameter
305	Invalid Text mode parameter
310	SIM not inserted
311	SIM PIN required
312	PH-SIM PIN required
313	SIM failure
314	SIM busy
315	SIM wrong
316	SIM PUK required
317	SIM PIN2 required
318	SIM PUK2 required
320	Memory failure
321	Invalid memory index
322	Memory full
330	SMSC address unknown
331	No network service
332	Network timeout
340	No +CNMA expected
500	Unknown error
512	User abort
513	Unable to store
514	Invalid Status
515	Device busy or Invalid Character in string
516	Invalid length
517	Invalid character in PDU
518	Invalid parameter
519	Invalid length or character
520	Invalid character in text
521	Timer expired
522	Operation temporary not allowed
532	SIM not ready
534	Cell Broadcast error unknown
535	Protocol stack busy
538	Invalid parameter

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 Usually stands for message expiration or rejected messages. The message retried in case of preventing excessive messaging being forwarded to one particular handset during a short time period. 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

  ERROR’s (GSM Device related codes)

  ERROR: 0 Phone failure

  ERROR: 1 No connection to phone

  ERROR: 2 Phone adapter link reserved

  ERROR: 3 Operation not allowed

  ERROR: 4 Operation not supported

  ERROR: 5 PH_SIM PIN required

  ERROR: 6 PH_FSIM PIN required

  ERROR: 7 PH_FSIM PUK required

  ERROR: 10 SIM not inserted

  ERROR: 11 SIM PIN required

  ERROR: 12 SIM PUK required

  ERROR: 13 SIM failure

  ERROR: 14 SIM busy

  ERROR: 15 SIM wrong

  ERROR: 16 Incorrect password

  ERROR: 17 SIM PIN2 required

  ERROR: 18 SIM PUK2 required

  ERROR: 20 Memory full

  ERROR: 21 Invalid index

  ERROR: 22 Not found

  ERROR: 23 Memory failure

  ERROR: 24 Text string too long

  ERROR: 25 Invalid characters in text string

  ERROR: 26 Dial string too long

  ERROR: 27 Invalid characters in dial string

  ERROR: 30 No network service

  ERROR: 31 Network timeout

  ERROR: 32 Network not allowed, emergency calls only

  ERROR: 40 Network personalization PIN required

  ERROR: 41 Network personalization PUK required

  ERROR: 42 Network subset personalization PIN required

  ERROR: 43 Network subset personalization PUK required

  ERROR: 44 Service provider personalization PIN required

  ERROR: 45 Service provider personalization PUK required

  ERROR: 46 Corporate personalization PIN required

  ERROR: 47 Corporate personalization PUK required

  ERROR: 48 PH-SIM PUK required

  ERROR: 100 Unknown error

  ERROR: 103 Illegal MS

  ERROR: 106 Illegal ME

  ERROR: 107 GPRS services not allowed

  ERROR: 111 PLMN not allowed

  ERROR: 112 Location area not allowed

  ERROR: 113 Roaming not allowed in this location area

  ERROR: 126 Operation temporary not allowed

  ERROR: 132 Service operation not supported

  ERROR: 133 Requested service option not subscribed

  ERROR: 134 Service option temporary out of order

  ERROR: 148 Unspecified GPRS error

  ERROR: 149 PDP authentication failure

  ERROR: 150 Invalid mobile class

  ERROR: 256 Operation temporarily not allowed

  ERROR: 257 Call barred

  ERROR: 258 Phone is busy

  ERROR: 259 User abort

  ERROR: 260 Invalid dial string

  ERROR: 261 SS not executed

  ERROR: 262 SIM Blocked

  ERROR: 263 Invalid block

  ERROR: 772 SIM powered down

 ERROR’s (GSM Network related codes)

   ERROR: 1 Unassigned number

   ERROR: 8 Operator determined barring

   ERROR: 10 Call bared

   ERROR: 21 Short message transfer rejected

   ERROR: 27 Destination out of service

   ERROR: 28 Unindentified subscriber

   ERROR: 29 Facility rejected

   ERROR: 30 Unknown subscriber

   ERROR: 38 Network out of order

   ERROR: 41 Temporary failure

   ERROR: 42 Congestion

   ERROR: 47 Recources unavailable

   ERROR: 50 Requested facility not subscribed

   ERROR: 69 Requested facility not implemented

   ERROR: 81 Invalid short message transfer reference value

   ERROR: 95 Invalid message unspecified

   ERROR: 96 Invalid mandatory information

   ERROR: 97 Message type non existent or not implemented

   ERROR: 98 Message not compatible with short message protocol

   ERROR: 99 Information element non-existent or not implemente

   ERROR: 111 Protocol error, unspecified

   ERROR: 127 Internetworking , unspecified

   ERROR: 128 Telematic internetworking not supported

   ERROR: 129 Short message type 0 not supported

   ERROR: 130 Cannot replace short message

   ERROR: 143 Unspecified TP-PID error

   ERROR: 144 Data code scheme not supported

   ERROR: 145 Message class not supported

   ERROR: 159 Unspecified TP-DCS error

   ERROR: 160 Command cannot be actioned

   ERROR: 161 Command unsupported

   ERROR: 175 Unspecified TP-Command error

   ERROR: 176 TPDU not supported

   ERROR: 192 SC busy

   ERROR: 193 No SC subscription

   ERROR: 194 SC System failure

   ERROR: 195 Invalid SME address

   ERROR: 196 Destination SME barred

   ERROR: 197 SM Rejected-Duplicate SM

   ERROR: 198 TP-VPF not supported

   ERROR: 199 TP-VP not supported

   ERROR: 208 D0 SIM SMS Storage full

   ERROR: 209 No SMS Storage capability in SIM

   ERROR: 210 Error in MS

   ERROR: 211 Memory capacity exceeded

   ERROR: 212 Sim application toolkit busy

   ERROR: 213 SIM data download error

   ERROR: 255 Unspecified error cause

   ERROR: 300 ME Failure

   ERROR: 301 SMS service of ME reserved

   ERROR: 302 Operation not allowed

   ERROR: 303 Operation not supported

   ERROR: 304 Invalid PDU mode parameter

   ERROR: 305 Invalid Text mode parameter

   ERROR: 310 SIM not inserted

   ERROR: 311 SIM PIN required

   ERROR: 312 PH-SIM PIN required

   ERROR: 313 SIM failure

   ERROR: 314 SIM busy

   ERROR: 315 SIM wrong

   ERROR: 316 SIM PUK required

   ERROR: 317 SIM PIN2 required

   ERROR: 318 SIM PUK2 required

   ERROR: 320 Memory failure

   ERROR: 321 Invalid memory index

   ERROR: 322 Memory full

   ERROR: 330 SMSC address unknown

   ERROR: 331 No network service

   ERROR: 332 Network timeout

   ERROR: 340 No +CNMA expected

   ERROR: 500 Unknown error

   ERROR: 512 User abort

   ERROR: 513 Unable to store

   ERROR: 514 Invalid Status

   ERROR: 515 Device busy or Invalid Character in string

   ERROR: 516 Invalid length

   ERROR: 517 Invalid character in PDU

   ERROR: 518 Invalid parameter

   ERROR: 519 Invalid length or character

   ERROR: 520 Invalid character in text

   ERROR: 521 Timer expired

   ERROR: 522 Operation temporary not allowed

   ERROR: 532 SIM not ready

   ERROR: 534 Cell Broadcast error unknown

   ERROR: 535 Protocol stack busy

   ERROR: 538 Invalid parameter

Topic Keywords: CMS Error, GPRS modem, GSM modem

When sending and/or receiving SMS messages with a GSM modem, if an error occurs, the modem will report a “+CMS ERROR” with a numeric code to indicate the reason for the problem. These error codes are defined in the ETSI GSM specifications, specifically GSM 07.05, GSM 03.40 and GSM 04.11.

I posted a list of CMS ERROR codes on the NowSMS discussion board almost 5 years ago at https://nowsms.com/discus/messages/1/829.html.

It’s a useful reference that I seem to search for a few times every month, so to make the information easier to find, I figured I would post it here.

Before I get to the list, and the sometimes cryptic definitions defined in the specifications, I want to highlight a few of the error codes that seem to occur most frequently.

+CMS ERROR 500 is probably the most commonly observed error code. The specifications define this as “unknown error”. So, of course, that is the error code that many modems return for almost any reason. Most frequently, it seems that this error occurs when the modem simply does not have a signal, or it has too weak of a signal. It’s a good idea to check the signal strength of the modem, and possibly relocate the modem so that it can acquire a stronger signal from the mobile operator.

+CMS ERROR 500 can also occur in situations where the mobile operator does not have SMS over GPRS (or SMS over 3G packet data) enabled. The default behaviour with most dedicated GSM modem devices is to try to send SMS over the packet network, and if this fails, fallback to the circuit switched network. However, in some environments, the modem doesn’t know how to interpret the failure, and the fallback does not occur properly. To determine if this is the problem, try going into “Properties” for the modem in the “SMSC” list of NowSMS, and change “SMS Access” to “GSM”.

+CMS ERROR 330 occurs frequently with 3G modems, it means that the address of the operator SMSC is not defined. It seems to be a bug in commonly used modem chipsets, where they do not read this address automatically from the SIM. To resolve this error, you need to manually define the operator SMSC address in the NowSMS configuration.

You can set the SMSC address by manually editing the SMSGW.INI file. Under the section header for the modem configuration (e.g., [Modem – …], add SMSC=+phonenumber, where “+phonenumber” is the address of the SMSC. The best way to find this SMSC address is to move the SIM card from the modem temporarily to a phone, and go through the SMS configuration menus on the phone to determine the currently configured SMSC number. When you enter the SMSC phone number, always start it with a “+” and don’t include any other non-numeric characters (no dashes or dots) in the address.

Always restart the gateway service after making a change to the SMSGW.INI file.

If you try setting the SMSC value by manually editing SMSGW.INI … if the setting doesn’t make a difference, always go back in and remove it immediately so that it doesn’t confuse things down the road.

+CMS ERROR 304 occurs frequently when using Motorola phones as a modem. Basically, these modems have a bug that prevent them from being able to send any messages that include UDH (User Data Header). This includes almost all types of binary messages, as well as long text messages. There is no resolution for this problem, other than to use a different modem that does not suffer from this bug.

+CMS ERROR 512 is defined as a manufacturer specific error. From what we’ve seen, when this error occurs, it is usually the same as error 500.

General Troubleshooting Tips

Before I get into the full CMS ERROR code list, it may be worth offering some general troubleshooting tips, as the error codes themselves are usually quite cryptic.

1. In the “SMSC” list, highlight the modem and press “Properties”. Try changing the “SMS Access” to “GSM”.
2. Remove the SIM card from the modem, and put it into a mobile phone. Verify that you can actually send SMS messages using the SMS client in the mobile phone. If you cannot, then there may be a problem with your account with the mobile operator. (Note: We have observed that with some mobile operators, if you buy a modem with a SIM card, they assume that the modem is going to be used for internet access, and SMS capabilities are not provisioned for the account.)
3. Check the signal strength of the modem. Connect to the modem using HyperTerminal, and issue the command AT+CSQ. This will return a result in the format +CSQ: xx,yy. If the xx value is 99 (no signal), or lower than 10, you may have a signal problem. It’s subjective, but I like to see this value as at least 16.

CMS ERROR Code List

1 – “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).

8 – “Operator determined barring”
This cause indicates that the MS has tried to send a mobile originating short message when the MS’s network operator or service provider has forbidden such transactions.

10 – “Call barred”
This cause indicates that the outgoing call barred service applies to the short message service for the called destination.

17 – “Network failure”.
This cause is sent to the MS if the MSC cannot service an MS generated request because of PLMN failures, e.g. problems in MAP.

21 – “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.

22 – “Congestion”.
This cause is sent if the service request cannot be actioned because of congestion (e.g. no channel, facility busy/congested etc.).

22 – “Memory capacity exceeded”.
This cause indicates that the mobile station cannot store the incoming short message due to lack of storage capacity.

Note that error “22” is defined twice. It is likely that “CMS ERROR 22” would be due to the first definition, while the second definition is likely to only be a status code for delivery reports.

27 – “Destination out of service”
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.

28 – “Unidentified subscriber”
This cause indicates that the subscriber is not registered in the PLMN (i.e. IMSI not known).

29 – “Facility rejected”
This cause indicates that the facility requested by the Mobile Station is not supported by the PLMN.

30 – “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).

38 – “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.

41 – “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.

42 – “Congestion”
This cause indicates that the short message service cannot be serviced because of high traffic.

47 – “Resources unavailable, unspecified”
This cause is used to report a resource unavailable event only when no other cause applies.

50 – “Requested facility not subscribed”
This cause indicates that the requested short message service could not be provided by the network because the user has not completed the necessary administrative arrangements with its supporting networks.

69 – “Requested facility not implemented”
This cause indicates that the network is unable to provide the requested short message service.

81 – “Invalid short message transfer reference value”
This cause indicates that the equipment sending this cause has received a message with a short message reference which is not currently in use on the MS-network interface.

95 – “Invalid message, unspecified”
This cause is used to report an invalid message event only when no other cause in the invalid message class applies.

96 – “Invalid mandatory information”
This cause indicates that the equipment sending this cause has received a message where a mandatory information element is missing and/or has a content error (the two cases are indistinguishable).

97 – “Message type non-existent or not implemented”
This cause indicates that the equipment sending this cause has received a message with a message type it does not recognize either because this is a message not defined or defined but not implemented by the equipment sending this cause.

98 – “Message not compatible with short message protocol state”
This cause indicates that the equipment sending this cause has received a message such that the procedures do not indicate that this is a permissible message to receive while in the short message transfer state.

99 – “Information element non-existent or not implemented”
This cause indicates that the equipment sending this cause has received a message which includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the cause. However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message.

111 – “Protocol error, unspecified”
This cause is used to report a protocol error event only when no other cause applies.

127 – “Interworking, unspecified”
This cause indicates that there has been interworking with a network which does not provide causes for actions it takes; thus, the precise cause for a message which is being send cannot be ascertained.

0…127 – Other values in this range are reserved, defined by GSM 04.11 Annex E-2 values

128 – Telematic interworking not supported x
129 – Short message Type 0 not supported x x
130 – Cannot replace short message x x
143 – Unspecified TP-PID error x x
144 – Data coding scheme (alphabet) not supported x
145 – Message class not supported x
159 – Unspecified TP-DCS error x x
160 – Command cannot be actioned x
161 – Command unsupported x
175 – Unspecified TP-Command error x
176 – TPDU not supported x x
192 – SC busy x
193 – No SC subscription x
194 – SC system failure x
195 – Invalid SME address x
196 – Destination SME barred x
197 – SM Rejected-Duplicate SM x
198 – TP-VPF not supported X
199 – TP-VP not supported X
208 – SIM SMS storage full x
209 – No SMS storage capability in SIM x
210 – Error in MS x
211 – Memory Capacity Exceeded X
212 – SIM Application Toolkit Busy x x
255 – Unspecified error cause

128…255 – Other values in this range are reserved, defined by GSM 03.40 subclause 9.2.3.22 values

300 – ME failure
301 – SMS service of ME reserved
302 – operation not allowed
303 – operation not supported
304 – invalid PDU mode parameter
305 – invalid text mode parameter
310 – SIM not inserted
311 – SIM PIN required
312 – PH-SIM PIN required
313 – SIM failure
314 – SIM busy
315 – SIM wrong
316 – SIM PUK required
317 – SIM PIN2 required
318 – SIM PUK2 required
320 – memory failure
321 – invalid memory index
322 – memory full
330 – SMSC address unknown
331 – no network service
332 – network timeout
340 – no +CNMA acknowledgement expected
500 – unknown error

256…511 – Other values in this range are reserved

512… – manufacturer specific

Result
codes are messages sent from the GSM/GPRS modem or mobile phone to
provide you information about the execution of an AT command and the
occurrence of an event. Two types of result codes are useful to you
when dealing with AT commands for SMS messaging:

• Final
  result codes

• Unsolicited
  result codes

16.1. Final Result
Codes of AT Commands

A
final result code marks the end of an AT command response. It is an
indication that the GSM/GPRS modem or mobile phone has finished the
execution of a command line. Two frequently used final result codes
are OK and ERROR. Only one final result code will be returned for
each command line. Thus, you will not see both OK and ERROR in the
response of a command line.

16.1.1. The OK
Final Result Code

The
OK final result code indicates that a command line has been executed
successfully by the GSM/GPRS modem or mobile phone. It always starts
and ends with a carriage return character and a linefeed character.

Here
is an example for illustration. Let’s say you send the command line
«AT+CMGL;+CGMI<CR>» to your GSM/GPRS modem.
The AT command «+CMGL» is used to list SMS messages stored
in the message storage area and the AT command «+CGMI» is
used to get the manufacturer name of the GSM/GPRS modem. If
everything works properly without any errors, the command line,
together with the response returned, should be something similar to
this:

AT+CMGL;+CGMI<CR>
<CR><LF>+CMGL:
1,»REC
UNREAD»,»+85291234567″,,»06/11/11,00:30:29+32″<CR><LF>
Welcome
to our SMS tutorial.<CR><LF>
<CR><LF>Nokia<CR><LF>
<CR><LF>OK<CR><LF>

As
mentioned earlier, when a terminal program such as HyperTerminal of
Microsoft Windows sees a carriage return character, it moves the
cursor to the beginning of the current line. When it sees a linefeed
character, it moves the cursor to the same position on the next line.
Hence, the command line you entered, together with the response
returned, will be displayed like this in a terminal program such as
HyperTerminal of Microsoft Windows:

AT+CMGL;+CGMI
+CMGL:
1,»REC UNREAD»,»+85291234567″,,»06/11/11,00:30:29+32″
Welcome
to our SMS tutorial.

Nokia

OK

16.1.2. The ERROR
Final Result Code

The
ERROR final result code indicates that an error occurs when the
GSM/GPRS modem or mobile phone tries to execute a command line. After
the occurrence of an error, the GSM/GPRS modem or mobile phone will
not process the remaining AT commands in the command-line string.

Below
are some common causes of error:

• The
  syntax of the command line is incorrect.

• The
  value specified to a certain parameter is invalid.

• The
  name of the AT command is spelt incorrectly.

• The
  GSM/GPRS modem or mobile phone does not support one or more of the
  AT commands, command parameters or parameter values in the
  command-line string.

Like
the OK final result code, the ERROR final result code always starts
and ends with a carriage return character and a linefeed character.

Here
is an example for illustration. Suppose you want to instruct your
GSM/GPRS modem to list SMS messages from the message storage area and
get the manufacturer name of the GSM/GPRS modem. You intend to type
the command line «AT+CMGL;+CGMI<CR>» but make
a careless mistake by typing «+CMFL» instead of «+CMGL».
The GSM/GPRS modem will return the ERROR final result code, as shown
below:

AT+CMFL;+CGMI<CR>
<CR><LF>ERROR<CR><LF>

As
an error occurs when the GSM/GPRS modem processes «+CMFL»,
the GSM/GPRS modem stops the execution of the command line and so the
second AT command «+CGMI» is not processed.

If
you type the second AT command «+CGMI» incorrectly instead
of the first AT command «+CMGL», the GSM/GPRS modem will
output the result of the execution of the AT command «+CMGL»
before outputting the ERROR final result code, like this:

AT+CMGL;+CGMU<CR>
<CR><LF>+CMGL:
1,»REC
UNREAD»,»+85291234567″,,»06/11/11,00:30:29+32″<CR><LF>
Welcome
to our SMS tutorial.<CR><LF>
<CR><LF>ERROR<CR><LF>

As
mentioned earlier, when a terminal program such as HyperTerminal of
Microsoft Windows sees a carriage return character, it moves the
cursor to the beginning of the current line. When it sees a linefeed
character, it moves the cursor to the same position on the next line.
Hence, the command line you entered, together with the response
returned, will be displayed like this in a terminal program such as
HyperTerminal of Microsoft Windows:

AT+CMGL;+CGMU
+CMGL:
1,»REC UNREAD»,»+85291234567″,,»06/11/11,00:30:29+32″
Welcome
to our SMS tutorial.

ERROR