WCOM/GSM/WMO2/WMO2ATDOC
6.6 Unsolicited result codes
Verbose result code
RING
+CMTI: <mem>,<index>
+CMT: <oa>...
or +CMT: [<alpha>,]... (PDU)
+CDS: <fo>, <mr>... (text mode)
or +CDS: <length>,... (PDU)
+CCCM: <ccm>
+CKEV: <keynb>
+CCWA: <nb>,<type>,<class>
+CLIP: <number>,<type>
+CREG: <stat>
+CRING: <type>
+WIND: <IndicationNb>
+CSQ: <RxLev>,99
6.7 Final result codes
Verbose result code
+CME ERROR: <err>
+CMS ERROR: <err>
BUSY
ERROR
NO ANSWER
NO CARRIER
OK
RING
Cause no 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 undistinguishable).
Cause no 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.
Cause no 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.
Cause no 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.
Cause no 111: "Protocol error, unspecified"
This cause is used to report a protocol error event only when no other
cause applies.
Cause no 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.
All values other than specified should be treated as error Cause No 41
Numeric (V0 set)
2
as verbose
(text mode)
as verbose
as verbose
as verbose
as verbose
as verbose
as verbose
as verbose
as verbose
as verbose
(specific)
as verbose
(specific)
Numeric (V0 set)
Description
as verbose
Error from 07.05 commands
as verbose
Error from SMS commands (07.07)
7
Busy signal detected
4
Command not accepted
8
Connection completion timeout
3
Connection terminated
0
Acknowledges correct execution of a command line
2
Incoming call signal from network
WAVECOM confidential ©
WMO2 G900 / G1800 / G1900
Description
Incoming call signal from network
Incoming message stored in <mem>
("SM") at location <index>
Incoming message directly displayed
SMS status report after sending a SMS
Current Call Meter value
Key press or release
Call Waiting number
Incoming Call Presentation
Network registration indication
Incoming call type (VOICE, FAX ...)
Specific unsolicited indication (SIM
Insert/Remove, End of init, Reset, Alerting)
Automatic RxLev indication with
AT+CCED=1,8 command
Friday 21 May 1999
85
Need help?
Do you have a question about the WMO2 and is the answer not in the manual?
Questions and answers