MTCMR-G-F4 Multi-Tech Systems, MTCMR-G-F4 Datasheet - Page 178

• Manufacturer Part Number: MTCMR-G-F4
• Description: MODEM GPRS QUAD BAND GSM GLOBAL
• Manufacturer: Multi-Tech Systems
• Series: MultiModem® iCellr

Specifications of MTCMR-G-F4

• Frequency: 850MHz, 900MHz, 1.8GHz, 1.9GHz
• Applications: General Purpose
• Interface: RS-232, USB
• Function: Transceiver, Modem
• Data Rate - Maximum: 115.2kbps
• Modulation Or Protocol: GSM, GPRS
• Voltage - Supply: 9 V ~ 32 V
• Package / Case: Module with Case
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Features: -
• Power - Output: -
• Sensitivity: -
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant, Lead free / RoHS Compliant
• Other names: 881-1151; MTCMR-G-F4

GSM 04.11 Annex E-2: Mobile Originating SM-Transfer
These error causes could appear for SMS commands (+CMGS, +CMSS, +CMGD…)
Multi-Tech Systems, Inc. GPRS AT Commands Reference Guide (Document Number S000293J)
Error #
Note: All values other than specified should be treated as error #41.
111
127
10
21
27
28
29
30
38
41
42
47
50
69
81
95
96
97
98
99
1
8
Error Label
Unassigned
(unallocated) number
Operator determined
barring
Call barred
Short message transfer
rejected
Destination out of
service
Unidentified subscriber
Facility rejected
Unknown subscriber
Network out of order
Temporary failure
Congestion
Resources unavailable,
unspecified
Requested facility not
subscribed
Requested facility not
implemented
Invalid short message
transfer reference value
Invalid message,
unspecified
Invalid mandatory
information
Message type non-
existent or not
implemented
Message not compatible
with short message
protocol state
Information element non-
existent or not
implemented
Protocol error,
unspecified
Interworking, unspecified There has been interworking with a network which does not provide causes for
Description
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).
The MS has tried to send a mobile originating short message when the MS's
network operator or service provider has forbidden such transactions.
The outgoing call barred service applies to the short message service for the
called destination.
The equipment sending this cause does not wish to accept this short message,
although it could have accepted the short message.This cause is neither busy
nor incompatible.
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 signaling 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.
The subscriber is not registered in the PLMN (e.g., IMSI not known)
The facility requested by the Mobile Station is not supported by the PLMN.
The subscriber is not registered in the HLR (e.g., IMSI or directory number is
not allocated to a subscriber).
The network is not functioning correctly and 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.
The network is not functioning correctly and 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.
The short message service cannot be serviced because of high traffic.
This cause is used to report a resource unavailable event only when no other
cause applies.
The requested short message service could
The network is unable to provide the requested short message service.
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.
This cause is used to report an invalid message event only when no other
cause in the invalid message class applies.
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
undistinguishable).
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.
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.
The equipment sending this cause has received a message which includes
unrecognized information elements 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
so that the equipment sends the cause to process the message.
This cause is used to report a protocol error event only when no other cause
applies.
actions it takes; thus, the precise cause for a message which is being sent
cannot be ascertained.
Appendix A – Result Codes, Failure Causes, Other Tables
178