Skip to main content
Welcome to EDAboard.com
Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals… and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
-
Digital Design and Embedded Programming
-
Digital communication
You should upgrade or use an alternative browser.
How can I resolve +CMS ERROR:PS busy in simcom GSM modem?
-
Thread starterHHM
-
Start dateApr 14, 2010
- Status
- Not open for further replies.
-
#1
-
#2
HHM
Junior Member level 1
- Joined
- Feb 6, 2010
- Messages
- 16
- Helped
- 0
- Reputation
-
0
- Reaction score
- 0
- Trophy points
- 1,281
- Activity points
-
1,412
this is AT&v results in my module
AT&V
ACTIVE PROFILE
E: 1
L: 0
M: 0
Q: 0
V: 1
X: 4
S0: 0
S2: 43
S3: 13
S4: 10
S5: 8
S6: 2
S7: 60
S8: 2
S10: 15
+CRC: 0
+CR: 0
+FCLASS: 0
+IMODE: 0
+DR: 0
+CMGF: 1
+CSDH: 0
+ILRR: 0
+CRLP: 61,61,128,6,0,3
+CMEE: 1
+CBST: 7,0,1
+IFC: 2,2
+ICF: 3,3
+CNMI: 2,1,0,0,0
+CSTA: 129
+CSCS: «IRA»
+IPR: 0
+DS: 3,0,512,20
&C: 1
&D: 2
+CCWE: 0
+CDTX: 0
+CTZU: 0
+CTZR: 0
+CV120: 1,1,1,0,0,0
+CEXTHS: 0
+CEXTBUT: 0
+CSMINS: 0
+CMUX: 0
+CCUG: 0,0,0
+CLIP: 0
+COLP: 0
+CCWA: 0
+CAOC: 1
+CLIR: 0
+CUSD: 0
+CSSU: 0
+CSSI: 0
+CDIP: 0
+CSCLK: 0
+CIURC: 1
+SCLASS0: 0
+CSDT: 0
+CMIC: 2,2
+ECHO(NORMAL_AUDIO): 0,0,0
+ECHO(AUX_AUDIO): 0,0,0
+SIDET(NORMAL_AUDIO): 4096
+SIDET(AUX_AUDIO): 4096
+CLCAL: 1
+CCPD: 1
+CMTE: 0
+CSCA: «+98350001400»,145
+CSMP: 17,255,0,0
-
#3
-
#4
HHM
Junior Member level 1
- Joined
- Feb 6, 2010
- Messages
- 16
- Helped
- 0
- Reputation
-
0
- Reaction score
- 0
- Trophy points
- 1,281
- Activity points
-
1,412
Need to see a listing of the commands you are sending to the module and the responses
thanks for your attention.
I use from AT Commands in 2 diffrent Time for diffrent usages but i dont need both of them together…
1-for GPRS connection and like what u say in below topic…
I used from this commands …
AT+CGATT=1
OK
AT+CGDCONT=1,»IP»,»mtnirancell»
OK
AT+CDNSCFG=»10.131.26.138″,»10.131.26.138″
OK
AT+CSTT
OK
AT+CIICR
OK
AT+CIFSR
10.6.154.192
AT+CIPSTATUS
OK
STATE: IP STATUS
AT+CIPHEAD=1
OK
AT+CDNSORIP=1
OK
AT+CIPSTART=»TCP»,»www.google.com»,»80″
OK
CONNECT OK
AT+CIPSEND
>
these command works but I have problem in connection with proxy and…so I create a dialup connection via windowse connection wizard and my problem solved
2.send and recive SMS in text mode
AT+CGATT=0
OK
AT+CSMS=0
+CSMS: 1,1,1
OK
AT+CMGF=1
OK
AT+CSCA=»+98350001400″,145
OK
AT+CNMI=2,2,0,0,0
OK
at+cmgs=»+989126356112″
> h
+CMS ERROR: 515
these are all of codes,also I try to used from AT&F,AT+CFUN=0,AT+CFUN=4 and then AT+CFUN=1 but my problem still yet.
Regards
- Status
- Not open for further replies.
Similar threads
-
Digital Design and Embedded Programming
-
Digital communication
-
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Содержание
- Cms Error 515 Ps Busy
- PS BUSY ERROR IN SIMCOM GSM MoDULE — Proton BASIC
- Arduino Uno R3 w/ SIM 900 SMS: +CMS Error 515 / PS busy .
- MAS 5: TC65 AT+CMGS failing with ERROR: 535 / PS Busy .
- GSM Equipment error codes explained — SmsSolutions.net
- SMS Tutorial: +CMS ERROR — Final Result Code Specific to .
- How to send bulk or group sms using AT command with GSM .
- GSM Modem CMS Error Code List NowSMS
- SMS Gateway — GSM Modem connectivity, CMS Error codes
- files/wvdial.conf at master · morfikov/files · GitHub
- CMS ERROR: 314 — NowSMS
- Cms Error 515 Ps Busy Fixes & Solutions
- How can I resolve +CMS ERROR:PS busy in simcom GSM modem?
- GSM Modem CMS Error Code List
- Related posts:
Cms Error 515 Ps Busy
We have collected for you the most relevant information on Cms Error 515 Ps Busy, as well as possible solutions to this problem. Take a look at the links provided and find the solution that works. Other people have encountered Cms Error 515 Ps Busy before you, so use the ready-made solutions.
PS BUSY ERROR IN SIMCOM GSM MoDULE — Proton BASIC
- http://www.protonbasic.co.uk/showthread.php/57319-PS-BUSY-ERROR-IN-SIMCOM-GSM-MoDULE
- Mar 30, 2014 · When I try with AT+CEER it just gives No specified ERROR In SIMCOM300 it just gives this +CMS ERROR 515 Here when i try with AT+CEER, it gives +CEER: No cause was given Plz help me out solving this Also note it gives out correct responce to at+csca so I suppose it has no gateway prb.
Arduino Uno R3 w/ SIM 900 SMS: +CMS Error 515 / PS busy .
- https://forum.arduino.cc/index.php?topic=203612.0
- Jan 30, 2017 · +CMS ERROR: PS busy The «PS busy» text code corresponds to «Error 515» as well. This sequence *always* returns this error, no matter what I seem to try. Any help, experience, or suggestions would be much appreciated. This is my first post here, so if I have left something important out, let me know and I’ll provide it. Thank you.
MAS 5: TC65 AT+CMGS failing with ERROR: 535 / PS Busy .
- https://support.industry.siemens.com/tf/WW/en/posts/mas-5-tc65-at-cmgs-failing-with-error-535-ps-busy/34678?page=0
- Sep 08, 2009 · do you know what «PS busy» stand for? I learned it can be caused by some reasons: ‘CMS ERROR 515’ is received in the following cases: 1. Sending a SMS when the SIM initialization is going on (after rebooting the module). 2. Reading a SMS immediately after booting the module when SIM initialization is not yet over. 3.
GSM Equipment error codes explained — SmsSolutions.net
- https://www.smssolutions.net/tutorials/gsm/gsmerrorcodes/
- 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 .
SMS Tutorial: +CMS ERROR — Final Result Code Specific to .
- https://www.developershome.com/sms/resultCodes2.asp
- The final result codes OK and ERROR are available to all AT commands. Unlike OK and ERROR, the +CMS ERROR final result code is only available to SMS AT commands. It notifies you about the occurrence of a message service failure. 16.2.1. The +CMS ERROR Final Result Code — Notifies the Occurrences and Causes of Message Service Failures
How to send bulk or group sms using AT command with GSM .
- https://vinodkotiya.blogspot.com/2010/08/how-to-send-bulk-or-group-sms-using-at.html
- Aug 12, 2010 · ‘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 .
GSM Modem CMS Error Code List NowSMS
- https://www.nowsms.com/gsm-modem-cms-error-code-list
- Jul 01, 2008 · +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.
SMS Gateway — GSM Modem connectivity, CMS Error codes
- http://www.ozekisms.com/index.php?owpn=380
- 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 .
files/wvdial.conf at master · morfikov/files · GitHub
- https://github.com/morfikov/files/blob/master/configs/etc/wvdial.conf
- # 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: 314 — NowSMS
- https://support.nowsms.com/discus/messages/1/71303.html
- May 20, 2013 · CMS ERROR: 314 — NowSMS. I tried on three different machines with windows 7 installed and have the same problem with lots of 314 errors on the smsdebug log.
Cms Error 515 Ps Busy Fixes & Solutions
We are confident that the above descriptions of Cms Error 515 Ps Busy and how to fix it will be useful to you. If you have another solution to Cms Error 515 Ps Busy or some notes on the existing ways to solve it, then please drop us an email.
Источник
How can I resolve +CMS ERROR:PS busy in simcom GSM modem?
Junior Member level 1
Junior Member level 1
Re: How can I resolve +CMS ERROR S busy in simcom GSM modem
this is AT&v results in my module
AT&V
ACTIVE PROFILE
E: 1
L: 0
M: 0
Q: 0
V: 1
X: 4
S0: 0
S2: 43
S3: 13
S4: 10
S5: 8
S6: 2
S7: 60
S8: 2
S10: 15
+CRC: 0
+CR: 0
+FCLASS: 0
+IMODE: 0
+DR: 0
+CMGF: 1
+CSDH: 0
+ILRR: 0
+CRLP: 61,61,128,6,0,3
+CMEE: 1
+CBST: 7,0,1
+IFC: 2,2
+ICF: 3,3
+CNMI: 2,1,0,0,0
+CSTA: 129
+CSCS: «IRA»
+IPR: 0
+DS: 3,0,512,20
&C: 1
&D: 2
+CCWE: 0
+CDTX: 0
+CTZU: 0
+CTZR: 0
+CV120: 1,1,1,0,0,0
+CEXTHS: 0
+CEXTBUT: 0
+CSMINS: 0
+CMUX: 0
+CCUG: 0,0,0
+CLIP: 0
+COLP: 0
+CCWA: 0
+CAOC: 1
+CLIR: 0
+CUSD: 0
+CSSU: 0
+CSSI: 0
+CDIP: 0
+CSCLK: 0
+CIURC: 1
+SCLASS0: 0
+CSDT: 0
+CMIC: 2,2
+ECHO(NORMAL_AUDIO): 0,0,0
+ECHO(AUX_AUDIO): 0,0,0
+SIDET(NORMAL_AUDIO): 4096
+SIDET(AUX_AUDIO): 4096
+CLCAL: 1
+CCPD: 1
+CMTE: 0
+CSCA: «+98350001400»,145
+CSMP: 17,255,0,0
Источник
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).
Источник
Коды ошибок запуска программы и отправки СМС:
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