Коды ошибок запуска программы и отправки СМС:
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
Содержание
- Support forum
- GSM Modem CMS Error Code List
- Related posts:
- Cms error short message transfer rejected
- [answered] CMS ERROR: 21 (Short message transfer rejected)
Support forum
This option was introduced in version 4.1.0.0 of Diafaan SMS Server.
Thank you for the quick response 🙂
I have checked the Advanced properties of some of the GSM Modems and I can’t see a property called ‘PermanentErrorList’. The closest I can find is ‘PermitModemCommandMessages’?
We are running version 4.0.0.0, do we need to update?
CMS Error 21 means ‘Short message transfer rejected’. It indicates that the mobile service does not accept the message but it does not give the exact reason why. It could be an invalid number, insufficient SMS credits or a number of other reasons. Diafaan SMS Server has no way of knowing if the message also will be rejected by another mobile service before trying it. The reason that the other modem may give a different error code for the same message is that the error is generated by the mobile operator and each operator has its own error handling procedures and might generate a different error code for the same underlying error.
Diafaan SMS Server is designed to route the messages through all designated gateways before giving up because it is also used for alarm applications where it is important that the message is sent even if there is a good chance that the message will be rejected by the next gateway as well. But you can change that behavior by adding a (list of) permanent error code(s) in the ‘PermanentErrorList’ property in the advanced settings of the GSM Modem Gateway. This makes sure that Diafaan SMS Server does not make further send attempts when this error is returned by the modem.
Источник
GSM Modem CMS Error Code List
Posted by bryce on Jul 1, 2008 in Support Blog Comments Off on GSM Modem CMS Error Code List —>
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.
- In the “SMSC” list, highlight the modem and press “Properties” . Try changing the “SMS Access” to “GSM”.
- 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.)
- 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
For comments and further discussion, please click here to visit the NowSMS Technical Forums (Discussion Board).
Источник
Cms error short message transfer rejected
| SMS Server Tools 3 Community | ||||
[answered] CMS ERROR: 21 (Short message transfer rejected)This topic is locked Operating system name and version: SLES10 SP3 64Bit Sometimes I get errors like following in the system; are these errors local errors or remote? If these errors are local what might be the right action? 2011-07-15 08:10:39,6, GSMLAN1: Checking if Modem is registered to the network this system sents sms like short letters (but no spam) to changing customer numbers, so I cannot say if we ever sent succsessful messages to such failed numbers. Thanks. The message data itself is correct, so the number must be unused. Restarting smsd will not help, which means that you can just store failed message files and manually check the reason, and probably update your database of numbers of customers. You can also use eventhandler and first argument «FAILED» for creating some log of failed numbers, if necessary. Источник Adblock
|
| Номер ошибки | Краткое описание | Расширенное описание |
| 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 |
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 |
April 26, 2018
10:50 am
Henk Helmantel
Admin
Forum Posts: 1396
Member Since:
May 28, 2013
Offline
This option was introduced in version 4.1.0.0 of Diafaan SMS Server.
Regards, Henk
April 26, 2018
10:17 am
Mark_L
Guest
Guests
Thank you for the quick response 🙂
I have checked the Advanced properties of some of the GSM Modems and I can’t see a property called ‘PermanentErrorList’. The closest I can find is ‘PermitModemCommandMessages’?
We are running version 4.0.0.0, do we need to update?
April 25, 2018
6:22 pm
Henk Helmantel
Admin
Forum Posts: 1396
Member Since:
May 28, 2013
Offline
Hello Mark,
CMS Error 21 means ‘Short message transfer rejected’. It indicates that the mobile service does not accept the message but it does not give the exact reason why. It could be an invalid number, insufficient SMS credits or a number of other reasons. Diafaan SMS Server has no way of knowing if the message also will be rejected by another mobile service before trying it. The reason that the other modem may give a different error code for the same message is that the error is generated by the mobile operator and each operator has its own error handling procedures and might generate a different error code for the same underlying error.
Diafaan SMS Server is designed to route the messages through all designated gateways before giving up because it is also used for alarm applications where it is important that the message is sent even if there is a good chance that the message will be rejected by the next gateway as well. But you can change that behavior by adding a (list of) permanent error code(s) in the ‘PermanentErrorList’ property in the advanced settings of the GSM Modem Gateway. This makes sure that Diafaan SMS Server does not make further send attempts when this error is returned by the modem.
Regards, Henk
April 25, 2018
5:09 pm
Mark_L
Guest
Guests
Good afternoon,
I was wondering if you could clarify something for me?
We have quite a complicated setup, so I’m going to massively simplify things to home in on the specific point.
You have two sim’s, and each simm is for a different provider. Each simm is setup as a GSM Modem.
You have a scripting gateway that calls PostDispatch like so (the first 5 values are obviously variables, the last two values are hard coded)
PostDispatchMessage(recordId, toAddress, fromAddress, strMessage, messageType, «GSM1», «GSM2»)
If when sending the message Diafaan recieves a CMS Error 21 (rejected) message from the network it fails over and tries to send the message via the backup gateway.
We have found that in a high percentage of cases the attempt on the backup gateway also fails (albeit with a slightly different error code).
Is this behaviour by design? Should Diafaan be trying to failover to the second gateway when confronted with a CMS 21 error?
Is there any way to change this behaviour?
If there isn’t then it would be great if you could define a list of codes that will always fail over, and a list of codes that will never fail over.
Look forward to your response, hope that makes sense!
Mark
Connect
- Add your SIM card to the Telit GSM modem and attach it via USB port to your server.
- To find the port where your GSM modem is attached, execute the following script after you’ve marked it as executable.
#!/bin/bash
for sysdevpath in $(find /sys/bus/usb/devices/usb*/ -name dev); do
(
syspath=”${sysdevpath%/dev}”
devname=”$(udevadm info -q name -p $syspath)”
[[ “$devname” == “bus/”* ]] && continue
eval “$(udevadm info -q property –export -p $syspath)”
[[ -z “$ID_SERIAL” ]] && continue
echo “/dev/$devname – $ID_SERIAL”
)
done
# ./listdev.sh/dev/ttyACM0 - Telit_wireless_solutions_Telit_Wireless_Module_351579057468926/dev/ttyACM1 - Telit_wireless_solutions_Telit_Wireless_Module_351579057468926/dev/ttyACM2 - Telit_wireless_solutions_Telit_Wireless_Module_351579057468926/dev/ttyACM3 - Telit_wireless_solutions_Telit_Wireless_Module_351579057468926/dev/ttyACM4 - Telit_wireless_solutions_Telit_Wireless_Module_351579057468926/dev/ttyACM5 - Telit_wireless_solutions_Telit_Wireless_Module_351579057468926/dev/ttyACM6 - Telit_wireless_solutions_Telit_Wireless_Module_351579057468926/dev/input/mouse2 - VMware_VMware_Virtual_USB_Mouse/dev/input/event4 - VMware_VMware_Virtual_USB_Mouse/dev/input/js0 - VMware_VMware_Virtual_USB_Mouse/dev/input/mouse3 - VMware_VMware_Virtual_USB_Mouse/dev/input/event5 - VMware_VMware_Virtual_USB_Mouse
Take a note of the device-path (/dev/ttyACM0)
Configuration
/etc/smsd.conf: This sample configuration file works fine in our productive environment on a SIM card without PIN code enabled – if you need to configure a PIN (if enabled) try configuring “pin=” . Make sure you use the correct device-path from above (device=/dev/ttyACM0) at “device=”.
# Example smsd.conf. Read the manual for a description
# once your configuration is OK, set log level lower (5 is good in most cases)
devices=GSM1
logfile=/var/log/smsd/smsd.log
loglevel=8
user=root
infofile=/var/run/smsd/smsd.working
pidfile=/var/run/smsd/smsd.pid
# 3.1.5 introduced smart logging
smart_logging=yes[GSM1]
init=ATE0
incoming=no
rtscts=no
cs_convert=yes
report=no
mode=new
device=/dev/ttyACM0
pin=0014
baudrate=115200
Testing
Configure your hyperterminal session by using minicom -s
# minicom -s
Select “Serial port setup”
Make sure your settings looks like this (A – Serial Device must match the path from above, E – Bps/Par/Bits must be 19200 8N1 or 115200 8N1). Press ENTER to save your setting.
Select Exit to open the connection to the GSM modem
The connection is initalized
The connection is open, the GSM modem is ready to receive commands
Send SMS by using AT commands. NOTE: In this example we have removed the PIN of the SIM card, if the PIN is still present make sure you are properly authenticated – additional details please see the chapter ‘PIN codes by using AT commands’ below)ATOKAT+CMGF=1 -----> set message format, see AT referenceOKAT+CMGS="+41796316771"> Hello World!><PRESS CTRL-Z to send the message>
+CMGS: 255OK
To exit minicom press CRTL-A and then x or q.
Services
Make sure the smsd service is enabled to start on boot# chkconfig --list smsdsmsd 0:off 1:off 2:off 3:on 4:off 5:off 6:off
Enable the service on boot for runlevel 3,4 and 5 by using the following command# chkconfig smsd on
To start/stop the service use following command# service smsd stop# service smsd start
Make sure the smsd service is running by using the command line
# service smsd statussmsd (pid 1476 1475) is running...
Or check the service status via OP5 webbased GUI
Make sure you can send a SMS message by using OP5 webbased GUI.
To send SMS notifications, make sure your contacts have filled out the ‘Pager’ information
Troubleshooting
CMS Error: 314
AT+CMGS="+41796316771"+CMS ERROR: 314
CMS Error: 314 usualy means the device is busy and you have to try later again. Sometimes you can try as long as you want, you wont become able to send messages. If this is the case try to reset your GSM modem by using following command and try again afterwards, you may have solved the problem with that.
AT&F
CMS Error: 500
CMS ERROR: 500 is unfortunately a very generic error message. Try to send an SMS directly without storing it to the SIM.
AT+CMGS ‘ Send an SMS directly without storing to the SIM
AT+CMGW ‘ Writing an SMS to the SIM card and then send the SMS
AT+CMGR ‘ By using the CMGR command you can verify if the SMS is written to SIM and it’s current status
Read your configured Service-Center number configured on your SIM card to send SMS messages (for example the number of Swisscom)AT+CSCA?
+CSCA: "+41794999000",145
If the number is not correctly configured then change it by usingAT+CSCA="+41794999000",145
OK
PIN codes by using AT commands
If you have a PIN code enabled SIM card and want to remove / disable the PIN code by using AT commands, then follow these commands. Suppose 9546 is the current PIN code, replace 9546 with your PIN code. Query the state of the SIM card by using the CPIN? command and remove the SIM code afterwards.
AT+CPIN?
+CPIN: SIM PIN ----> pin codes need to be entered
OK
AT+CPIN="9546"
OKAT+CLCK="SC",0,"9546" ----> disable pin code
OKAT+CPIN?
+CPIN: READY
Attached some examples about PIN and PUK management:
AT+CLCK="SC",1,"0000",1 ---->When you want to set pin code "0000"
OK
--Reboot module
AT+CPIN?
+CPIN: SIM PIN
OK
AT+CPIN="0000"
OK
AT+CPWD="SC","0000","1234" ---->When you want to change the pin code to "1234"
OK
--Reboot module
AT+CPIN?
+CPIN: SIM PIN
OK
AT*PSPRAS?
*PSPRAS: 3,10,255,255
OK
AT+CPIN="7777" ---->Input the wrong pin code will reduce the available try times
+CME ERROR: incorrect password
AT*PSPRAS?
*PSPRAS: 2,10,255,255
OK
AT+CPIN="1234"
OK
AT+CPIN?
+CPIN: SIM PUK
OK
AT+CPIN="44753796","1234" ---->When you want to input the PUK code after you input 3 times of the wrong pin.
OK
GSM connection state details
Check for Received Signal Strength & Quality
AT+CSQ
+CSQ: 13,1
Wait for the response in format: +CSQ: <rssi>, <ber>
<rssi>
Integer from 0 to 99 indicates the received signal strength. NOTE: Signal strength less than 6 indicates only 1 antenna bar, the quality of a connection will be poor and the connection may even drop.
| <rssi> value | Signal strength | Indication (for devices with a User Interface (MMI)) |
| 0 | -113 dBm or less | Signal is VERY low: at the extreme sensibility limit |
| 1 | -111 dBm | MMI may indicate only 1 antenna bar |
| 2 | -109 dBm | MMI may indicate only 1 antenna bar |
| 3 | -107 dBm | MMI may indicate only 1 antenna bar |
| 4 | -105 dBm | MMI may indicate only 1 antenna bar |
| 5 | -103 dBm | MMI may indicate only 1 antenna bar |
| 6 | -101 dBm | MMI may indicate 2 antenna bars |
| 7 | -99 dBm | MMI may indicate 2 antenna bars |
| 8 | -97 dBm | MMI may indicate 2 antenna bars |
| 9 | -95 dBm | MMI may indicate 2 antenna bars |
| 10 | -93 dBm | MMI may indicate 3 antenna bars |
| 11 | -91 dBm | MMI may indicate 3 antenna bars |
| 12 | -89 dBm | MMI may indicate 3 antenna bars |
| 13 | -87 dBm | MMI may indicate 3 antenna bars |
| 14 | -85 dBm | MMI may indicate 3 antenna bars |
| 15 | -83 dBm | MMI may indicate 4 antenna bars |
| 16 | -81 dBm | MMI may indicate 4 antenna bars |
| 17 | -79 dBm | MMI may indicate 4 antenna bars |
| 18 | -77 dBm | MMI may indicate 4 antenna bars |
| 19 | -75 dBm | MMI may indicate 4 antenna bars |
| 20 | -73 dBm | MMI may indicate 4 antenna bars |
| 21 | -71 dBm | MMI may indicate 4 antenna bars |
| 22 | -69 dBm | MMI may indicate 4 antenna bars |
| 23 | -67 dBm | MMI may indicate 4 antenna bars |
| 24 | -65 dBm | MMI may indicate 4 antenna bars |
| 25 | -63 dBm | MMI may indicate 4 antenna bars |
| 26 | -61 dBm | MMI may indicate 4 antenna bars |
| 27 | -59 dBm | MMI may indicate 4 antenna bars |
| 28 | -57 dBm | MMI may indicate 4 antenna bars |
| 29 | -55 dBm | MMI may indicate 4 antenna bars |
| 30 | -53 dBm | MMI may indicate 4 antenna bars |
| 31 | -51 dBm or more | MMI may indicate 4 antenna bars |
| 99 | not detected | MMI may indicate flashing antenna bars |
<bet>
Integer from 0 to 7 and 99 reports the received signal quality measured on the radio traffic channel (error bit rate in percent)
Check if device is registered to the network
AT+CREG?
+CREG: 0,1
Wait for response in the format: +CREG: <mode>, <stat>
<mode>
0 GSM
2 UTRAN
<stat>
0 – not registered, ME is not currently searching a new operator to register to
1 – registered, home network
2 – not registered, but ME is currently searching a new operator to register to
3 – registration denied
4 – unknown
5 – registered, roaming
Overall overview
“battchg” – battery charge level – battery charge level indicator range 0..5
“signal” – signal quality – signal quality indicator, range: 0 to 7, 99 – not measurable
“service” – service availability – service availability indicator, range: 0 – not registered to any network, 1 – registered
AT+CIND=?
+CIND: (("battchg",(0-5,99)),("signal",(0-7,99)),("service",(0,1)),("sounder",()
Reboot device
AT#REBOOT
Check device hardware
Manufacturer Identification
AT+GMI
Telit
Model Identification
AT+GMM
HE910-D
Revidion Identification
AT+GMR
12.00.024
Serial Identification
AT+GSN
00007406xx
GSM Equipment and Network Error Codes
When controlling GSM devices using AT commands, the device can respond with either “OK” or “ERROR”. Sometimes you will receive an error and you do not know the cause of this error. That’s why most advanced GSM devices support extended errors. Instead of just displaying the “ERROR” message, it also shows an error number. The syntax of this extended error is either “+CMS ERROR: xxx” or “+CME ERROR: xxx”. When the error starts with “+CME ERROR”, it means that the error is a device specific error code. For instance, you are trying to read a phonebook entry before entering a pincode. When there is a network error, for instance, when you try to send an SMS message when there is no network coverage, you will receive an error which starts with “+CMS ERROR”. To enable these extended commands, execute the following commands, or add them to your modems init string:
AT+CMEE=1 AT&W
Below you can find a list containing almost every error code supported by GSM devices.
CME ERROR’s (GSM Equipment related codes)
| Error | Description |
|---|---|
| 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’s (GSM Network related codes)
| Error | Description |
|---|---|
| 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 |
Reference Guide
Download offline copy: Telit 3G HE910 3G/HSDPA/GSM Modem AT Command Reference R10