Specifications

Chapter 3 – Status Control Commands
Multi-Tech Systems, Inc. AT Commands for EDGE Modems (S000371B) 43
3.4 AT+CEER Extended Error Report
Description: AT+CEER returns an extended error report regarding the reason of the last
• call release
• failure to set up a call (both mobile originated or terminated)
• failure to modify a call by using Supplementary Services
• failed attempt to activate, register, query, deactivate or deregister a Supplementary Service
• unsuccessful GPRS attach or unsuccessful PDP context activation
• GPRS detach or PDP context deactivation
The release cause report is presented in numeric format. Default output in case of a none-error-
situation is +CEER: 0,0,0. A description associated with each number can be found in the tables
given in the following subclauses and the relevant GSM specifications.
The first parameter <locationID> serves to locate the other two parameters. Depending on the
failure or release cause either <reason> or <ssRelease> are applicable; i.e., if <reason> ≠ 0,
then <ssRelease> = 0.
Vice versa, if <reason> = 0, then <ssRelease> may be ≠ 0.
AT+CEER is not available for data calls, please use ATS18=1 instead.
Exe. Command Syntax: AT+CEER
Exe. Response: +CEER: <locationID>, <reason>, <ssRelease>
OK
ERROR
+CME ERROR
Test Command Syntax: AT+CEER=?
Test Response: OK
ERROR
+CME ERROR
Parameter Description:
<locationID>
Location ID as number code. Location IDs are listed in Section 3.4.1, Cause Location ID for the extended error
report. Each ID is related with another table that contains a list of <reason>s or <ssRelease>s.
<reason>
Reason for last call release as number code. The number codes are listed in several tables, sorted by different
categories in the following subclauses. The tables can be found proceeding from the Location ID given in
Section 3.4.1, Cause Location ID for the extended error report.
<ssRelease>
Release cause for last Supplementary Service call (listed in Section 3.4.5, GSM Release cause for
Supplementary Service Call) or last call related use of a Supplementary Service (listed in Section 3.4.10,
Release cause for Call-related Supplementary Services (CRSS)).
Examples:
Example 1
ATD”01751223344”; A mobile originated call is rejected by the remote party.
NO CARRIER Call setup is terminated with NO CARRIER.
AT+CEER To check the cause, the caller enters AT+CEER.
+CEER: 8,21,0 The Location ID 8 in Section 3.4.1 points to Section 3.4.4, where 21 =
OK “Call rejected”. 0 = “No error” refers to parameter <ssRelease> that is not applicable.
Example 2
The user attempts to set up a multiparty call, though there are only two parties involved in the present
conversation:
ATD”01751223344”;
OK
AT+CHLD=2
OK
AT+CHLD=3
+CME ERROR: operation temporary not allowed
AT+CEER
+CEER: 22,0,2 The Location ID 22 in Section 3.4.1 points to release cause for Call-Related Supplementary
Services (CRSS), where 2 = “Initial conditions not fulfilled (one active, one held call)”. 0 =
“No error” refers to parameter <reason> that is not applicable.
Example 3
The user attempts to activate call barring. Activation is denied by the network since the password is blocked after
previous failures to enter the password.
AT+clck=oi,1,”0000”,3;
+CME ERROR: incorrect password
AT+CEER
+CEER: 35,0,43 The Location ID 35 in Section 3.4.1 points to Section 3.4.5, where 43 =
OK “NumberOfPWAttemptsViolation” may mean that a wrong password has been entered for
more than 3 times. 0 = “No error” refers to parameter <reason> that is not applicable.