CMS ERROR收集

Here'sa list of all of the "+CMS ERROR" codes for the GSM modem interface ...they can be found defined in the ETSI GSM specs. I figure it is worthposting as they are split between the GSM 07.05, GSM 03.40 and GSM04.11 specs, and I frequently have to look this up for supportincidents. (So if nothing else, I'll be able to search out here to findthe list.)

CMS ERROR code list (GSM Modem error codes):

1 - "Unassigned (unallocated) number"
Thiscause indicates that the destination requested by the Mobile Stationcannot be reached because, although the number is in a valid format, itis not currently assigned (allocated).

8 - "Operator determined barring"
Thiscause indicates that the MS has tried to send a mobile originatingshort message when the MS's network operator or service provider hasforbidden such transactions.

10 - "Call barred"
This cause indicates that the outgoing call barred service applies to the short message service for the called destination.

21 - "Short message transfer rejected"
Thiscause indicates that the equipment sending this cause does not wish toaccept this short message, although it could have accepted the shortmessage since the equipment sending this cause is neither busy norincompatible.

27 - "Destination out of service"
This causeindicates that the destination indicated by the Mobile Station cannotbe reached because the interface to the destination is not functioningcorrectly. The term "not functioning correctly" indicates that asignalling message was unable to be delivered to the remote user; e.g.,a physical layer or data link layer failure at the remote user, userequipment 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"
Thiscause 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"
Thiscause indicates that the network is not functioning correctly and thatthe condition is likely to last a relatively long period of time; e.g.,immediately reattempting the short message transfer is not likely to besuccessful.

41 - "Temporary failure"
This cause indicatesthat the network is not functioning correctly and that the condition isnot likely to last a long period of time; e.g., the Mobile Station maywish 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"
Thiscause indicates that the requested short message service could not beprovided by the network because the user has not completed thenecessary 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"
Thiscause indicates that the equipment sending this cause has received amessage with a short message reference which is not currently in use onthe 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"
Thiscause indicates that the equipment sending this cause has received amessage where a mandatory information element is missing and/or has acontent error (the two cases are indistinguishable).

97 - "Message type non-existent or not implemented"
Thiscause indicates that the equipment sending this cause has received amessage with a message type it does not recognize either because thisis a message not defined or defined but not implemented by theequipment sending this cause.

98 - "Message not compatible with short message protocol state"
Thiscause indicates that the equipment sending this cause has received amessage such that the procedures do not indicate that this is apermissible message to receive while in the short message transferstate.

99 - "Information element non-existent or not implemented"
Thiscause indicates that the equipment sending this cause has received amessage which includes information elements not recognized because theinformation element identifier is not defined or it is defined but notimplemented by the equipment sending the cause. However, theinformation element is not required to be present in the message inorder 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"
Thiscause indicates that there has been interworking with a network whichdoes not provide causes for actions it takes; thus, the precise causefor 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

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.

22 - "Congestion".
Thiscause is sent if the service request cannot be actioned because ofcongestion (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.

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