AT Command Interface Chapter

Chapter 3 AT Command Interface
Command Descriptions
The following sections provide detailed descriptions about the commands that the GSM Data Module supports.
AT Commands
+++ Description: AT Escape Command When the GSM Data Module has established a connection with a remote modem, you can use the +++ command to switch the GSM Data Module from Data Mode to Command Mode while maintaining the connection with the remote modem. Issuing this command stops the flow of data on the AT command interface. Do not precede this command with the AT prefix, nor end it with a termination character. To return to Data Mode and resume data flow, use the On command (see page 65). +++ None +++ OK When issuing the +++ command, there must be a 0.5-second pause before and after issuing the command. Repeat Last Command Line Executed The A/ command instructs the GSM Data Module to re-execute the last command line executed. Do not precede this command with the AT prefix, nor
Syntax Parameters: Example: Possible Response: Notes:
A/ Description:
GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001
55
Chapter 3 AT Command Interface end it with a termination character. The command executes as soon as the / character us typed. This command is useful when you want the GSM Data Module to re-execute a lengthy command line. Syntax: Parameters: Example: Possible Response: Notes: A/ None A/ OK The last-executed command line stays in the GSM Data Modules until it is turned off or reset with the Z command. Either action invalidates the A/ command, since there is no command in memory to re-execute. Answer Incoming Call The A command instructs the GSM Data Module to answer an incoming call. ATA <cr> None ATA <cr> CONNECT <text> if the call is accepted. <text> appears if the X1, X2, X3, X4 command is in effect. OK when the GSM Data Module returns to Command Mode. NO CARRIER if there is no connection. This command must be the only command or the final command on the command line. This command aborts if a character is received during execution. However, in some connection states
A Description: Syntax: Parameters Example: Possible Responses:
Notes:
56
Chapter 3 AT Command Interface A Answer Incoming Call (such as during handshaking), the command cannot be aborted. Bell/CCITT Compatibility The Bn command lets you choose between the Bell and CCITT protocols when the GSM Data Module is operating at 300 or 1200 bps. ATB<n> <n> = 0 or 1 B0 = use the CCITT V.22 protocol at 1200 bps. B1 = use the Bell 103J protocol at 300 bps and the Bell 212A protocol at 1200 bps. (DEFAULT) ATB0 <cr> ATB1 <cr> OK if the command is accepted. ERROR if the command is rejected because the GSM Data Module is not operating at 300 or 1200 bps. Carrier Option The Cn command is provided for compatibility purposes only; no action is taken. ATC<n> <cr> <n> = 0 or 1 C0 = not supported. C1 = guarantees backward compatibility with communications software that issue the C1 command. (DEFAULT) ATC0 <cr> ATC1 <cr>
Bn Description:
Syntax: Parameters:
Examples: Possible Responses:
Cn Description: Syntax: Parameters:
Examples:
57
Chapter 3 AT Command Interface Possible Response: D Description: OK acknowledges the change of state. Dial Command The D command lets you originate a voice, data, or fax call to a dialed number, or dial a number stored in memory. The D command also controls supplementary services. Originating a Call ATD<n>[;] string of dialing digits and optionally V.25ter and GSM modifier characters: Dialing digits: 0 through 9 *, # only for supplementary service calls + only as first character of call A, B, C ignored ; voice call, return to Command Mode > direct dial from phonebook v.25ter parameters: T Tone (DTMF) dialing P Pulse (rotary) dialing comma, ! ignored W, @ ignored GSM parameters: I, #31# CLIR invocation i, *31# CLIR suppression G,g CUG info, uses set with +CCUG Examples: Possible Responses: ATD9495551212 <cr> ATD1 <cr> OK if voice call connects successfully. OK when the GSM Data Module releases the call and returns to Command Mode. NO DIALTONE if no dial tone is detected with the X2 or X4 command in effect. <n>
Syntax: Parameters:
58
Chapter 3 AT Command Interface D Dial Command BUSY if a busy tone is detected with the X3 or X4 command in effect. NO CARRIER if a connection cannot be set up. +CME ERROR: <err> if error is related to Data Module functionality. Up to 20 dialing digits and GSM modifiers can follow the ATD command. Dialing a Stored Number from Memory Syntax: Parameters: ATD><mem> <n>[][<G>][;] <mem> phone book FD = SIM fixed-dialing memory feature. LD = SIM last-dialing-phonebook SM = SIM phonebook ME = ME phonebook <n> integer-type memory location, should be in the range of locations available in the memory used. = CLIR invocation (restrict CLI presentation). = CLIR suppression (allow CLI presentation). <G> and <g> = Control CUG. Used with the +CCUG command to control the CUG supplementary service. <;> = voice call, return to Command Mode Examples: ATD>34; <cr> Places a voice call to the number from PB entry 34. ATD>"DDC"; <cr> Places a voice call to the name in PB matching the string. ATD>SM34: <cr> Places a voice call to entry 34 in the PB storage SM
Notes:
59
Chapter 3 AT Command Interface D Possible Responses: Dial Command If semicolon (;) is omitted, places a data call. OK if voice call connects successfully. OK when Data Module releases the call and returns to Command Mode. NO DIALTONE if no dial tone is detected with the X2 or X4 command in effect. BUSY if a busy tone is detected with the X3 or X4 command in effect. NO CARRIER if a connection cannot be set up. +CME ERROR: <err> if error is related to Data Module functionality. Dialing a Supplemental Service String When <n> is a supplementary service string, the Data Module tries to call the supplementary service entered in the dialed string. The Data Module returns result of the supplementary service AT command issued. For a list of the supplementary service strings supported, refer to Appendix B. Notes: The D command for dialed or supplementary service calls can usually be aborted by receiving a character during execution. This command cannot be aborted in some connection setup states, such as handshaking. Enable Command Echo The En command determines whether the GSM Data Module echoes command characters received during Command Mode. ATE<n> <cr> <n> = 0 or 1 E0 = do not echo command characters. E1 = echo command characters. ATE1 <cr> ATE0 <cr>
En Description:
Syntax: Parameters:
Examples:
60
Chapter 3 AT Command Interface En Possible Response: Fn Description: Enable Command Echo OK acknowledges the change of state.
Line Modulation The Fn command selects the line modulation. The line modulation is fixed, unless automode (F0) is selected. ATF<n> <cr> <n> = 0, 1, 3, 4, 5, 6, 7, 8,9, or 10 F0 = enable auto-detect mode. All connect speeds are possible, based on the remote modem's preference. (DEFAULT) F1 = select V.21 or Bell 103 modulation, based on the Bn command in effect, as the only acceptable line speed that can result in a data connection. F3 = select V.23 modulation as the only acceptable line speed that can result in a data connection. Originating modem operates at 75 bps and answering modem operates at 1200 bps. F4 = select V.22 1200 or Bell 211A modulation, based on the Bn command in effect, as the only acceptable line speed that can result in a data connection. F5 = select V.22bis as the only acceptable line modulation that can result in a data connection. F6 = select V.32bis 4800 or V.32 4800 as the only acceptable line modulation that can result in a data connection. F7 = select V.32bis 7200 as the only acceptable line modulation that can result in a data connection. F8 = select V.32bis 9600 or V.32 9600 as the only acceptable line modulation that can result in a data connection.
Syntax: Parameters:
61
Chapter 3 AT Command Interface Fn Line Modulation F9 = select V.32bis 12,000 as the only acceptable line modulation that can result in a data connection. F10 = select V.32bis 14,400 as the only acceptable line modulation that can result in a data connection. ATF0 <cr> ATF8 <cr> OK acknowledges the change of state.
Examples: Possible Response:
Hn Description: Syntax: Parameters: Example: Possible Response: Notes:
Hook Switch - Disconnect Existing Connection The Hn command terminates the current call. ATH<n> <cr> <n> = 0 H0 = terminate the call and disconnect from line. ATH0 <cr> OK acknowledges the change of state. OK is issued after circuit 109 (DCD) turns OFF (if it was ON). Display Product Identification Information The In command retrieves the product information text. ATI<n> <cr> <n> = 0, 1, or 3 I0 = return manufacturer followed by model
In Description: Syntax: Parameters:
62
Chapter 3 AT Command Interface In Display Product Identification Information identification. I1 = return 3 digit ROM checksum code. I3 = return modem ROM version. ATI0 <cr> ATI2 <cr> If the ATI0 command is issued: Conexant OK If the ATI1 command is issued: Conexant GSMDM100DB OK If the ATI3 command is issued: DAC19281 OK Notes: Ln Description: Syntax: Parameters: Same response for ATI1..ATI9 and +CGMI Speaker Volume The Ln command is provided for compatibility purposes only; no action is taken. ATL<n> <cr> <n> = 0, 1, 2, or 3 L0 = low volume. L1 = low volume. (DEFAULT) L2 = medium volume. L3 = high volume. ATL0 <cr> ATL3 <cr> OK acknowledges the change of state.
Examples:
Possible Response:
63
Chapter 3 AT Command Interface Mn Description: Syntax: Parameters: Speaker ON/OFF The Mn command controls the status of the GSM Data Module speaker. ATM<n> <cr> <n> = 0, 1, 2, or 3 M0 = speaker turned off. M1 = speaker off when remote carrier received. (DEFAULT) M2 = speaker always turned on. M3 = speaker off when remote carrier is received and when the GSM Data Module is dialing. ATM0 <cr> ATM3 <cr> OK acknowledges the change of state.
Examples:
Possible Response: Nn Description: Syntax: Parameters:
Automode Enable/Disable The Nn command can be used to ensure that a data connection is made only at a specified speed. ATN<n> <cr> <n> = 0 or 1 N0 = disable automode detection. When originating or answering, handshake only at the DTE-to-modem data rate. N1 = enable automode detection. Handshake with remote modem at the highest speed supported by both modems. (DEFAULT) ATN0 <cr> ATN1 <cr> OK acknowledges the change of state.
Examples:
Possible
64
Chapter 3 AT Command Interface Nn Response: Automode Enable/Disable
On Description: Syntax: Parameters: Example: Possible Responses:
Return to Data Mode The On command returns the GSM Data Module to Data Mode from Command Mode. ATO<n> <cr> <n> = 0 O0 = switch from Command Mode to Data Mode ATO0 <cr> NO CARRIER if connection is not successfully resumed. CONNECT <text> if the module successfully returns to Data Mode from Command Mode. <text> is returned only if parameter setting is greater than 0. Pulse Dial The P modifier instructs the GSM Data Module to use the pulse (rotary) dialing method to dial calls that follow the P modifier in the Dial command line. ATDP<dialing digits> <cr> ATDP9495551212 <cr> OK if voice call connects successfully. OK when Data Module releases the call and returns to Command Mode. NO DIALTONE if no dial tone is detected with the X2 or X4 command in effect. BUSY if a busy tone is detected with the X3 or X4
Notes:
P Description:
Syntax: Example: Possible Responses:
65
Chapter 3 AT Command Interface P Pulse Dial command in effect. NO CARRIER if a connection cannot be set up. +CME ERROR: <err> if error is related to Data Module functionality. The P modifier can be used along with the T modifier if both pulse and tone dialing are required in the same Dial command line. For example: ATDP5551212,,T2468 Suppress Result Codes The Qn command determines whether the GSM Data Module transmits result codes. ATQ<n> <cr> <n> = 0 or 1 Q0 = transmit result codes. Q1 = do not transmit result codes. ATQ0 <cr> ATQ1 <cr> If <n>=0: OK If <n>=1: no response
Notes:
Qn Description: Syntax: Parameters:
S0 Description:
Set Number of Rings The S0 command determines the number of rings that must occur before the GSM Data Module automatically answers an incoming call. ATS0=<n> <cr> <n> = 1 to 255 rings. ATS0=1 <cr>
Syntax: Parameters: Example:
66
Chapter 3 AT Command Interface S0 Possible Response: S3 Description: Set Number of Rings OK
Carriage Return Character The S3 command sets the ASCII value of the carriage return character used to end the command line and the character that appears after a modem response. The default value is 13, although you can change it to another ASCII value between 0 and 127. ATS3=<n> <cr> <n> = 0 to 127 ASCII. (DEFAULT = 13 [CTRLM]) ATS3=4 <cr> OK
Syntax: Parameters: Example: Possible Response: S4 Description:
Line Feed Character The S4 command sets the ASCII value of the line feed character. The default value is 10, although you can change it to another ASCII value between 0 and 127. The GSM Data Module sends the line feed character after sending a carriage return character when the V1 command is in effect, enabling English result codes. However, it is not sent with most numeric result codes. If you do not want to receive a line feed character, you can change the value in this register to a null character, but you cannot disable line feed characters.
Syntax:
ATS4=<n> <cr>
67
Chapter 3 AT Command Interface S4 Parameters: Example: Possible Response: S5 Description: Line Feed Character <n> = 0 to 127 ASCII (DEFAULT = 10 [CTRLJ]) ATS4=6 <cr> OK
Backspace Character The S5 command sets the ASCII value of the backspace character. This character is the character created by pressing the Backspace key and the character echoed to move the cursor to the left. The default value is 8. If you want to change this value, do not enter a value between 33 and 126 because these values are equivalent to a printable ASCII character and your modem will not recognize the character as a backspace character. ATS5=<n> <cr> <n> = 0 to 32 ASCII ATS5=28 <cr> OK
Set Number of Seconds to Wait for Connection to Complete The S7 command determines the amount of time that the GSM Data Module waits for a call to complete after originating or answering the call before the Module disconnects. ATS7=<n> <cr>
Syntax:
68
Chapter 3 AT Command Interface S7 Parameters: Example: Possible Response: S8 Description: Set Number of Seconds to Wait for Connection to Complete <n> = 0 to 60, 255 seconds. ATS7=15 <cr> OK
Set Number of Seconds to Wait for Comma Modifier The S8 command determines how long the GSM Data Module waits when it encounters a comma in a Dial command before processing the rest of the command line. ATS8=<n> <cr> <n> = 1-255 seconds. (DEFAULT is 2 seconds) ATS7=15 <cr> OK
Set Disconnect Delay After Indicating the Absence of Data Carrier The S10 command determines the amount of time that the GSM Data Module remains connected in the absence of a data carrier. If the data carrier is detected before disconnect, the Data Module remains connected. ATS10=<n> <cr> <n> = 1-15-255 tenths of a second. ATS10=8 <cr>
69
Chapter 3 AT Command Interface S10 Possible Response: T Description: Set Disconnect Delay After Indicating the Absence of Data Carrier OK
Tone Dial The T modifier instructs the GSM Data Module to use the tone (DTMF) dialing method to dial calls that follow the T modifier in the Dial command line. ATDT<dialing digits> <cr> ATDT9495551212 <cr> OK if voice call connects successfully. OK when Data Module releases the call and returns to Command Mode. NO DIALTONE if no dial tone is detected with the X2 or X4 command in effect. BUSY if a busy tone is detected with the X3 or X4 command in effect. NO CARRIER if a connection cannot be set up. +CME ERROR: <err> if error is related to Data Module functionality. The T modifier can be used along with the P modifier if both tone and pulse dialing are required in the same Dial command line. For example: ATDP5551212,,T2468 Result Code Format Set result code format mode. This parameter setting determines the contents of the header and trailer transmitted with result codes and information responses. ATV<n> <cr> <n> = 0 or 1
Syntax: Example: Possible Responses:
Notes:
Vn Description:
Syntax: Parameters:
70
Chapter 3 AT Command Interface Vn Result Code Format V0 = use numeric result codes followed by <cr><lf>. V1 = use word result codes preceded and followed by <cr><lf>. ATV0 <cr> ATV1 <cr> OK
Examples:
Possible Response: Wn Description: Syntax: Parameters:
Correction Message Control The Wn command controls the format of CONNECT messages. ATW<n> <cr> <n> = 0, 1, or 2 W0 = upon connection, the GSM Data Module reports only the DTE speed (for example, CONNECT 9600). Subsequent responses are disabled. (DEFAULT) W1 = upon connection, the GSM Data Module reports the line speed, the error correction protocol, and the DTE speed, respectively. Subsequent responses are disabled. W2 = upon connection, the GSM Data Module reports the DCE speed (for example, CONNECT 2400). Subsequent responses are disabled. ATW0 <cr> ATW1 <cr> OK
Examples:
Possible Response: Xn
Extended Result Code
71
Chapter 3 AT Command Interface Xn Description: Extended Result Code The Xn command sets the CONNECT result code format and call monitoring. This parameter setting determines whether or not the GSM Data Module detects the presence of dial tone and busy signal, and whether the module transmits particular result codes. ATX<n> <cr> <n> = 0, 1, 2, 3, 4, or 5 X0 = CONNECT result code only returned, dial tone and busy detection are both disabled. X1 = CONNECT<text> result code only returned, dial tone and busy detection are both disabled. X2 = CONNECT< text > result code returned, dial tone detection is enabled, busy detection is disabled. X3 = CONNECT< text > result code returned, dial tone detection is disabled, busy detection is enabled. X4 = CONNECT< text > result code returned, dial tone and busy detection are both enabled. ATX0 <cr> ATX4 <cr> OK
Syntax: Parameters:
Examples: Possible Response: Yn Description: Syntax: Parameters:
Long Space Disconnect The Yn command is provided for compatibility purposes only; no action is taken. ATY<n> <cr> <n> = 0 or 1 Y0 = disable long-space disconnect. Y1 = enable long-space disconnect.
72
Chapter 3 AT Command Interface Yn Examples: Possible Response: Zn Description: Long Space Disconnect ATY0 <cr> ATY1 <cr> OK
Soft Reset The Zn command resets the GSM Data Module and sets all current parameters to the user-defined profile. ATZ<n> <cr> <n> = 0 or 1 0 = reset to profile number 0. 1 = reset to profile number 1. ATZ0 <cr> OK The user-defined profile is stored in non-volatile memory. If the user-profile is invalid, the GSM Data Module uses the factory-default profile. The GSM Data Module ignores any additional commands that follow this command on the command line. A delay of 300ms is required before the next command can be sent, otherwise the OK response may be corrupted. Break Control The \Kn command determines the number of bits between the data characters. AT\K<n> <cr>
Syntax: Parameters:
Example: Possible Response: Notes:
\Kn Description: Syntax:
73
Chapter 3 AT Command Interface \Kn Parameters: Example: Possible Response: \Nn Description: Syntax: Parameters: Break Control <n> = 0-7 AT\K=1 <cr> OK
Error Correction The \Nn command controls the preferred errorcorrecting mode in a data connection. AT\N<n> <cr> <n> = 0, 2, 4, or 5 \N0 = disable error-correction mode. \N2 = auto-reliable mode (LAPM connection, then MNP connection). \N4 = select LAPM error-correction mode. \N5 = select MNP error-correction mode. AT\N2 <cr> OK
Example: Possible Response:
&Cn Description: Syntax: Parameters:
DCD Control The &Cn command controls the Data Carrier Detect (DCD) signal. AT&C<n> <cr> <n> = 0 or 1 &C0 = DCD is always ON. &C1 = DCD is ON only when the remote modems data carrier is present.
74
Chapter 3 AT Command Interface &Cn Examples: Possible Response: &Dn Description: DCD Control AT&C0 <cr> AT&C1 <cr> OK
DTR Control The &Dn command determines how the GSM Data Module reacts when an ON-to-OFF Data Terminal Ready (DTR) transition occurs. AT&D<n> <cr> <n> = 0, 1, or 2 &D0 = GSM Data Module ignores DTR transitions. &D 1 = ON-to-OFF DTR transition causes the GSM Data Module to change to Command Mode while retaining the connected call. &D 2 = ON-to-OFF DTR transition causes the GSM Data Module to disconnect call and change to Command Mode. AT&D0 <cr> AT&D2 <cr> OK
Syntax: Parameters:
Examples: Possible Response: &Fn Description:
Restore Factory Defaults The &Fn command sets all current parameters to manufacturer defaults. The GSM Data Module resets all current parameters to the manufacturerdefined profile. AT&F<n> <cr>
Syntax:
75
Chapter 3 AT Command Interface &Fn Parameters: Restore Factory Defaults <n> = 0 &F0 = sets all GSM Data Module parameters to the manufacturer defaults. AT&F0 <cr> OK If the &Fn command is the only command on the command line, a delay of 300ms is needed before issuing the next AT command line. Otherwise, the OK response may be corrupted. There are no restrictions for using &Fn within a command string. (for example:AT&FS0=1&W+cbst=7,0,1) Flow Control The &Kn command sets the DTE/DCE flow control type or disables flow control. AT&K<n> <cr> <n> = 0, 1, 2, 3, 4, or 5 &K0 = disable local flow control. &K1 = enable RTS/CTS hardware local flow control. &K2 = enable XON/XOFF software local flow control. &K3 = same as &K1. &K4 = same as &K2. &K5 = enable transparent XON/XOFF flow control. AT&K0 <cr> AT&F2 <cr> OK
Example: Possible Response: Notes:
&Kn Description: Syntax: Parameters:
76
Chapter 3 AT Command Interface &Qn Description: Operational (Sync/Async) The &Qn command allows the GSM Data Module to operate asynchronously or synchronously. AT&Q<n> <cr> <n> = 0, 1, 2, or 3 &Q0 = asynchronous mode. &Q1 = asynchronous in Command Mode, synchronous in Data Mode. &Q2 = when DTR goes ON, GSM Data Module dials number stored using the &Z0 command and switches to synchronous mode. &Q3 = synchronous when DTR is ON; Command Mode when DTR is OFF. AT&Q0 <cr> AT&Q3 <cr> OK
Syntax: Parameters:
Examples: Possible Response: &Rn Description:
RTS/CTS Control The &Rn command lets you determine the relationship between the Clear To Send (CTS) and Request To Send (RTS) signals. AT&R<n> <cr> <n> = 0 or 1 &R0 = CTS mimics the state of the RTS signal. &R1 = CTS is always ON. (DEFAULT) AT&R0 <cr> AT&R1 <cr> OK
Syntax: Parameters:
Examples: Possible
77
Chapter 3 AT Command Interface &Rn Response: &Sn Description: Syntax: Parameters: RTS/CTS Control
DSR Control The &Sn command controls the Data Set Ready (DSR) signal. AT&S<n> <cr> <n> = 0 or 1 &S0 = DSR is always ON. (DEFAULT) &S1 = DSR is OFF when the GSM Data Module is in Command Mode and ON when the GSM Data Module is in Data Mode. AT&S0 <cr> AT&S1 <cr> OK
Examples: Possible Response: &Tn Description:
Loopback Test Mode The &Tn command puts the GSM Data Module into one of several diagnostic test modes or exits a test mode. AT&T<n> <cr> <n> = 0, 1, 3, 4, 5, 6, 7, or 8 &T0 = end any test in progress. &T1 = local analog loopback test. &T3 = local digital loopback test. &T4 = grant remote digital loopback from remote modem. &T5 = deny remote digital loopback from remote modem. &T6 = remote digital loopback test. &T7 = remote digital loopback test with self-test. &T8 = local digital loopback test with self-test.
Syntax: Parameters:
78
Chapter 3 AT Command Interface &Tn Examples: Possible Response: &Wn Description: Loopback Test Mode AT&T1 <cr> AT&T0 <cr> OK
Store Current Configuration The &Wn command stores the current parameter settings to one of two user-defined profiles. The profiles are maintained in the GSM Data Modules nonvolatile memory. AT&W<n> <cr> <n> = 0 or 1 0 = store settings in profile 0. (DEFAULT) 1 = store settings in profile 1. AT&W0 <cr> AT&W1 <cr> OK Use the &Yn command to specify which profile the GSM Data Module is to use when it is first turned on or reset using the Zn command (see page 81). Display Current Configuration The &V command display the GSM Data Modules current parameter settings. AT&V<n> <cr> <n> = 0 or 1 0 = profile number 0. 1 = profile number 1.
Syntax: Parameters:
Examples: Possible Response: Notes:
&V Description: Syntax: Parameters:
79
Chapter 3 AT Command Interface &V Example: Possible Responses: Display Current Configuration AT&V0 <cr> ACTIVE PROFILE: &C1 &D0 &S0 S0= 1 S1= 0 S2= 43 S3= 13 S4= 10 S5= 8 S14= 138 S21= 36 S31= 6 S32= 17 S33= 19 +CBST: 0, 0, 1 +CRLP: 61,61,48,6,7 +CRC: 0 +CR: 0 +FCLASS:0 +IFC: 2, 2 +ICF: 0, 3 +CMGF: 1 +CSDH: 0 +ILRR: 0 +IPR: 0 +DS: 0, 0, 512, 6 +DR: 0 +CFUN: 0 +CSCS: "IRA" +CMEE: 0 +CMOD: 0 +CREG: 0 $ICB: 1 $ABRT: 1 +CLIP: 0 +COLP: 0 +CMEC: 2,2,2 +CIND: 0,0 +CMER: 0,0,0,0,1 +CALM: 0 +CRSL: 4 +CVIB: 0 +CLVL: 4 +CMUT: 0 +CNMI: 0,0,0,0,0 $UIND: 0 +CLIR: 0 +CSMS: 0,1,1,1
80
Chapter 3 AT Command Interface &V Display Current Configuration NPB_ME_C1_: +1949483119491 (first four PB entries in ME) DDC_ME_C2_: 1972870219722 NPB_ME_C3_: +1949483319493 DDC_ME_C4_: 1972870419724 OK
&Yn Description:
Designate User Profile The &Yn command designates the stored profile that the GSM Data Module is to use when it is first turned on or reset with the Zn command. AT&Y<n> <cr> <n> = 0 or 1 &Y0 = use parameter settings from profile 0. &Y1 = use parameter settings from profile 1. AT&Y0 <cr> AT&Y1 <cr> OK
Syntax: Parameters:
Examples: Possible Response: +DR Description:
V.42bis Data Compression Reporting The +DR command determines whether or not the intermediate result code of the current data compression is reported by TA to TE after a connection setup. AT+DR=<value> <cr> <value> = 0 or 1 0 = enable reporting. (DEFAULT) 1 = disable reporting.
Syntax: Parameters:
81
Chapter 3 AT Command Interface +DR Examples: Possible Response: +DR? Description: Syntax: Parameters: Examples: Possible Response: +DR=? Description: Syntax: Parameters: Example: Possible Response: +DS Description: V.42bis Data Compression Reporting AT+DR=0 <cr> AT+DR=1 <cr> OK
Report Current +DR Command The +DR? command reports the current +DR command in effect. AT+DR? <cr> None AT+DR? <cr> +DR: <value> OK List Supported Data Compression Values The +DR=? command lists the supported v.42bis data compression values. AT+DR=? <cr> None AT+DR=? <cr> +DR: (list of supported <value>s) OK V.42bis Data Compression Control The +DS command enables or disablesV.42bis
82
Chapter 3 AT Command Interface +DS Syntax: Parameters: V.42bis Data Compression Control data compression. AT+DS=[<p0>[,<n>[,<p1>[,<p2>]]]] <cr> <p0> = 0, 1, 2, or 3 0 = no compression. 1 = transmit only. 2 = receive only. 3 = both directions, accept any direction. <n> = 0 or 1 0 = do not disconnect if V.42bis is not negotiated by the remote DCE as specified by <p0>. 1 = disconnect if V.42bis is not negotiated by the remote DCE as specified by <p0>. <p1> the maximum number of dictionary entries that should be negotiated, from 512 to 2048. (DEFAULT is 512.) <p2> the maximum string length to be negotiated, from 6 to 20. (DEFAULT is 6) Examples: Possible Responses: +DS? Description: Syntax: Parameters: AT+DS=0 <cr> AT+DS=1,0,512,6 <cr> OK
Report Current +DS Command The +DS? command reports the current +DS command in effect. AT+DS? <cr> None
83
Chapter 3 AT Command Interface +DS? Examples: Possible Response: +DS=? Description: Syntax: Parameters: Example: Possible Response: +ICF Description: Report Current +DS Command AT+DS=0 <cr> AT+DS=1,0,512250 <cr> +DS: 1,0,512,6 OK Test +DS Command The +DS=? command tests the V.42bis data compression mode of the GSM Data Module. AT+DS=? <cr> None AT+DS=? <cr> +DS: 1,0,5,12,6 OK DTE-to-DCE Character Framing The +ICF command determines the serial interface character framing format and parity received by the GSM Data Module from the transmitting device. AT+ICF=[<format>,[<parity>]] <cr> <format> = 0, 1, 3, 4, or 5 0 = auto-detect. 1 = 8 data bits, 0 parity bit, 2 stop bits. 3 = 8 data bits, 0 parity bit, 1 stop bit. (DEFAULT) 4 = 7 data bits, 0 parity bit, 2 stop bits. 5 = 7 data bits, 1 parity bit, 1 stop bit. <parity> = 0, 1, or 3 0 = odd. 1 = even. 3 = space (0).
Syntax: Parameters:
84
Chapter 3 AT Command Interface +ICF Examples: Possible Response: Notes: +ICF=? Description: DTE-to-DCE Character Framing AT+ICF=1 <cr> AT+ICF=2,1 <cr> OK Wait 300 ms after receiving the OK response before issuing the next AT command line. List Supported Format and Parity Settings The +ICF=? command lists the character formats and parity settings that the GSM Data Module supports. AT+ICF=? <cr> None AT+ICF=? <cr> +ICF: (0,3-5),(0,1,3) OK Report Current Format and Parity Settings The +ICF? command reports the current format and parity settings in effect. AT+ICF? <cr> None AT+ICF? <cr> +ICF:0,3 OK Set Local Data Flow Control The IFC command determines whether flow
Syntax: Parameters: Example: Possible Response: +ICF? Description: Syntax: Parameters: Example: Possible Response: +IFC Description:
85
Chapter 3 AT Command Interface +IFC Set Local Data Flow Control control is used on the GSM Data Modules serial port when the Module is in Data Mode. Flow control stops the flow of data from the DTE to avoid data loss during buffering. AT+IFC=[<dce_by_dte>[,<dte_by_dce>]] <cr> <dce_by_dte> = one of the following flow control methods from the DTEs point of view: 0 = none. 1 = XON/XOFF, dont pass characters to data stack. 2 = line 133: ready for receiving. (DEFAULT) <dte_by_dce> = one of the following flow control methods from the GSM Data Modules point of view: 0 = none. 1 = XON/XOFF. 2 = line 106, Clear to Send. (DEFAULT) Examples: Possible Response: +IFC=? Description: Syntax: Parameters: Example: Possible Response: AT+IFC=0,0 <cr> AT+IFC=1,1 <cr> OK
Syntax: Parameters:
List Supported Flow Control Methods The +IFC=? command lists the flow control methods that the GSM Data Module supports. AT+IFC=? <cr> None AT+IFC=? <cr> +IFF: (0-2),(0-2) OK
86
Chapter 3 AT Command Interface +IFC? Description: Syntax: Parameters: Example: Possible Response: +ILRR Description: Report Current +Flow Control Method The +IFC? command reports the current flow control method in effect. AT+IFC? <cr> None AT+IFC? <cr> IFC: 2,2 OK Report Local Port Rate The ILRR command determines whether an intermediate result code of local rate is reported from the DCE to the DTE during connection setup. The rate reported represents the current negotiated or renegotiated DTE-DCE rate. AT+ILRR=<value> <cr> <value> = 0 or 1 0 = disable reporting or local port rate. (DEFAULT) 1 = enable reporting or local port rate. AT+ILRR=0 <cr> AT+ILRR=1 <cr> +ILLR: <rate> OK Where <rate> is the port rate setting on call connection in bauds per second 300 1200 2400 4800 9600 19200 (DEFAULT) 28800
Syntax: Parameters:
87
Chapter 3 AT Command Interface +ILRR Report Local Port Rate 38400 57600 List Supported Local Port Rate Values The ILRR=? command lists the supported local port rate values. AT+ILRR=? <cr> None AT+ILRR=? <cr> +ILRR: (list of supported <value>s) OK Report Current Port Rate Value The +ILRR? command reports the current port rate value in effect. AT+ILRR? <cr> None AT+ILRR? <cr> ILRR: <value> OK Set Terminal Equipment Rate The IPR command sets the data rate on the GSM Data Modules serial interface. The Module accepts rates from 300 to 57,600 bps. The rate takes effect following the result code issued after this command executes. AT+IPR=<rate> <cr> <rate> = one of the following baud rates:
+ILRR=? Description: Syntax: Parameters: Example: Possible Response: +ILRR? Description: Syntax: Parameters: Example: Possible Response: +IPR Description:
Syntax: Parameters:
88
Chapter 3 AT Command Interface +IPR Set Terminal Equipment Rate 300 1200 2400 4800 9600 (DEFAULT) 19200 28800 38400 57600 115200 AT+IPR=9600 <cr> AT+IPR=57600 <cr> OK If this command is the only one on the command line, wait 300 ms before issuing the next AT command line. Otherwise the OK response may be corrupted. However, there are no restrictions on using this command in a command string. (e.g., AT&Fs0=1+ipr=9600&W+cbst=7,0,1) The GSM Data Module does not support autobauding. List Supported Fixed-Only Rates The +IPR=? command lists the fixed-only rates that are supported on the GSM Data Modules serial interface. AT+IPR=? <cr> None AT+IPR=? <cr> +IPR: (list of supported autodetectable <rate> values)[,list of fixed-only <rate>values)] OK
Examples: Possible Response: Notes:
+IPR=? Description:
Syntax: Parameters: Example: Possible Response:
89
Chapter 3 AT Command Interface +IPR? Description: Syntax: Parameters: Example: Possible Response: Report Current Serial Interface Rate The +IPR? command reports the current rate on the GSM Data Modules serial interface. AT+IPR? <cr> None AT+IPR? <cr> +IPR: (0,2400,4800,9600,19200,38400, 57600,115200),(300,600,1200,14400,76800) OK
Fax Commands
+FCLASS Description: Set Service Class to Fax or Data Mode The +FCLASS command specifies data or fax operation and prepares the GSM Data Module to process information accordingly. AT+FCLASS=<n> <cr> <n> = 0, 1, or 8 0 = data operation. (DEFAULT) 1 = fax operation. 8 = voice operation. AT+FCLASS=0 <cr> AT+FCLASS=1 <cr> OK if syntax is satisfactory; otherwise, ERROR. List Supported Service Classes The +FCLASS=? command lists the
Syntax: Parameters:
Examples: Possible Responses: +FCLASS=? Description:
90
Chapter 3 AT Command Interface +FCLASS=? Syntax: Parameters: Example: Possible Responses: List Supported Service Classes supported service classes. AT+FCLASS=? <cr> None AT+FCLASS=? <cr> +FCLASS: (0, 1, 8) OK Otherwise, ERROR +FCLASS? Description: Syntax: Parameters: Example: Possible Responses: Report Current Service Class The +FCLASS? command reports the current service class in effect. AT+FCLASS? <cr> None AT+FCLASS? <cr> +FCLASS: <n> where <n> = 0, 1, or 8 (DEFAULT is 0) OK Otherwise, ERROR +FRH Description: Receive Data with HDLC The +FRH command lets the GSM Data Module receive data using the HDLC protocol and the defined modulation. AT+FRH=<n> <cr> <n> = 3 3 = V.21 channel 2 300 bps.
Syntax: Parameters:
91
Chapter 3 AT Command Interface +FRH Example: Possible Responses: Receive Data with HDLC AT+FRH=3 <cr> +FRH: OK if GSM Data Module is off-hook. ERROR if GSM Data Module is on-hook. +FRH=? Description: Syntax: Parameters: Example: Possible Responses: Report Current +FRH Command The +FRH=? command reports the current +FRH command in effect. AT+FRH=? <cr> None AT+FRH=? <cr> +FRH: (3) OK for V.21 channel 2 300 bps. ERROR if GSM Data Module is on-hook. +FRM Description: Syntax: Parameters: Receive Data According to the Defined Modulation The +FRM command receives data according to the defined data rate. AT+FRM=<n> <cr> <n> = 24, 48, 72, 73, 74, 96, 97, 121, 122, 145, or 146 24 = V.27ter 2400 bps. 48 = V.27ter 4800 bps. 72 = V.29 7200 bps long. 73 = V.17 7200 bps short.
92
Chapter 3 AT Command Interface +FRM Receive Data According to the Defined Modulation 96 = V.29 9600 bps. 97 = V.17 9600 bps long. 121 = V.17 12000 bps long. 122 = V.17 12000 bps short. 145 = V.17 14400 bps long. 146 = V.17 14400 bps short. AT+FRM=24 <cr> AT+FRM=146 <cr> OK if GSM Data Module is off-hook. ERROR if GSM Data Module is on-hook. +FRM=? Description: Syntax: Parameters: Example: Possible Responses: Report Current +FRM Command The +FRM=? command reports the current +FRM command in effect. AT+FRM=? <cr> None AT+FRM=? <cr> +FRM: (24, 28, 72, 73, 96, 97, 121, 122, 145, 146) OK ERROR if the GSM Data Module is onhook. +FRS Description: Syntax: Receive Silence The +FRS command defines the wait for silence <time>*10ms intervals. AT+FRS=<time> <cr>
93
Chapter 3 AT Command Interface +FRS Parameters: Examples: Possible Responses: Notes: Receive Silence <time> = 0-255 AT+FRS=50 <cr> AT+FRS=1125 <cr> OK after <time>*10ms silence interval elapses. ERROR if the GSM Data Module is on-hook. The command aborts if any character is received from the DTE (the response will still be OK). Report Current +FRS Command The +FRS=? command reports the current +FRS command in effect. AT+FRS=? <cr> None AT+FRS=? <cr> OK after <time>*10ms silence interval elapses. ERROR if the GSM Data Module is on-hook. The command aborts if any character is received from the DTE (The response will still be OK). Transmit Data with HDLC The +FTH command transmits data using the HDLC protocol and the defined modulation. AT+FTH=<n> <cr>
+FRS=? Description: Syntax: Parameters: Example: Possible Responses: Notes:
+FTH Description:
Syntax:
94
Chapter 3 AT Command Interface +FTH Parameters: Example: Possible Responses: +FTH=? Description: Syntax: Parameters: Example: Possible Responses: +FTS Description: Transmit Data with HDLC <n> = 3 3 = V.21 channel 2 300 bps. AT+FTH=3 <cr> +FTH: (3) OK for V.21 channel 2 300 bps. ERROR if GSM Data Module is on-hook. Report Current FTH Command The +FTH=? command reports the current +FTH command in effect. AT+FTH=? <cr> None AT+FTH=? <cr> +FTH: (3) OK for V.21 channel 2 300 bps. ERROR if GSM Data Module is on-hook. Stop Transmission and Wait The +FTS command stops any current transmission and waits for <time>*10ms intervals. AT+FTS=<time> <cr> <time> = 0-255 AT+FTS=50 <cr> AT+FTS=1125 <cr> OK after <time>*10ms silence interval elapses. ERROR if the GSM Data Module is on-hook. The command aborts if any character is
Syntax: Parameters: Examples: Possible Responses: Notes:
95
Chapter 3 AT Command Interface +FTS Stop Transmission and Wait received from the DTE (The response will still be OK). Report Current +FTS Command The +FTS=? command reports the current +FTS command in effect. AT+FTS=? <cr> None AT+FTS=? <cr> OK after <time>*10ms silence interval elapses. ERROR if the GSM Data Module is on-hook. The command aborts if any character is received from the DTE (The response will still be OK).
+FTS=? Description: Syntax: Parameters: Example: Possible Responses: Notes:
GSM Commands
+CACM Description: Accumulated Call Meter (ACM) Reset or Query The +CACM command resets the Advice of Charge related to the accumulated call meter (ACM) value in SIM file EF(ACM). ACM contains the total number of home units for both the current and preceding calls. AT+CACM=[<passwd>] <passwd>
Syntax: Parameters:
96
Chapter 3 AT Command Interface +CACM Accumulated Call Meter (ACM) Reset or Query string type: SIM PIN2 AT+CACM=1234 <cr> OK If error is related to ME functionality: +CME ERROR: <err> See subclause 9.2 for <err> values.
Example: Possible Responses:
+CACM? Description:
Return Current ACM Value The +CACM ? command returns the GSM Data Modules current accumulated call meter value. AT+CACM? <cr> None AT+CACM? <cr> +CACM: <acm> OK Where <acm> is a string-type; accumulated call meter value similarly coded as <ccm> under +CAOC. +CME ERROR: <err> See subclause 9.2 for <err> values.
Syntax: Parameters: Example: Possible Responses:
+CALA Description:
Alarm The +CALA command sets an alarm time in the ME. There can be an array of different types of alarms. AT+CALA=<time>[,<n>[,<type>
Syntax:
97
Chapter 3 AT Command Interface +CALA Alarm [,<text>[,<recurr>[,<silent>]]]]] <cr> <time> String-type value; format is yy/MM/dd,hh:mm:sszz, where characters indicate year (two last digits), month, day, hour, minutes, seconds, and time zone (indicates the difference, expressed in quarters of an hour, between the local time and GMT; range -47...+48); e.g., 6th of May 1994, 22:10:00 GMT+2 hours equals 94/05/06,22:10:00+08. <n>, <n1>, <n2> integer-type value indicating the index of the alarm; default is manufacturer specific. <type> integer-type value indicating the type of the alarm (e.g., sound, volume, LED); values and default are manufacturer specific. <text> string-type value indicating the text to be displayed when alarm time is reached; maximum length <tlength>. <tlength> integer-type value indicating the maximum length of <text>. <recurr> string-type value indicating day of week for the alarm in one of the following formats: <1..7>[,<1..7>[]] Sets a recurrent alarm for one or more days in the week. The digits 1 to 7 corresponds to the days in the week, Monday (1), , Sunday (7). Example: The string 1,2,3,4,5 may be used to set an alarm for all weekdays. 0 = sets a recurrent alarm for all days in the week.
Parameters:
98
Chapter 3 AT Command Interface +CALA Alarm <rlength> integer-type value indicating the maximum length of <recurr> <silent> = 0 or 1 integer-type value indicating if the alarm is silent or not. 0 = the alarm will not be silent. 1 = the alarm will be silent and the only result from the alarm is the unsolicited result code +CALV. Examples: AT+CALA=<time>[,<n>[,<type> [,<text>[,<recurr>[,<silent>]]]]] <cr> Example of text alarm result code: AT+CALA="01/05/25,16:01:00-08",1,0, "Conexant Alarm Test" OK Example of LED alarm result code: AT+CALA=01/05/25,16:03:00-08,1,1 OK If invalid value is entered: +CME ERROR: <err> See subclause 9.2 for <err> values. +CALA=? Description: List Supported Alarm Settings The +CALA=? command lists supported array index values, alarm types, and maximum length of the text to be displayed. AT+CALA=? <cr> None ATCALA=? <cr>
Possible Responses:
99
Chapter 3 AT Command Interface +CALA=? Possible Responses: List Supported Alarm Settings +CALA: (list of supported <n>s),(list of supported <type>s),<tlength> OK If invalid value is entered: +CME ERROR: <err> See subclause 9.2 for <err> values. +CALA? Description: Syntax: Parameters: Example: Possible Responses: List Current Alarm Settings The +CALA? command returns the list of current active alarm settings in the ME. AT+CALA? <cr> None AT+CALA? <cr> If alarm has expired: +CALA: OK If a problem is encountered: +CME ERROR: <err> See subclause 9.2 for <err> values. +CALM Description: Syntax: Parameters: Alert Sound Mode The +CALM command selects the general alert sound mode of the ME. AT+CALM=<mode> <cr> <mode> = 0 or 1 0 = normal mode. 1 = silent mode (all sounds from ME are prevented). AT+CALM=0 <cr>
Example:
100
Chapter 3 AT Command Interface +CALM Possible Response: Alert Sound Mode OK If invalid value is entered: +CME ERROR: <err> See subclause 9.2 for <err> values. +CALM=? Description: Syntax: Parameters: Example: Possible Responses: Report Supported Alert Sound Modes The +CALM=? command returns supported values as compound value. ATCALM=? <cr> None ATCALM=? <cr> +CALM: (list of supported <mode>s) +CME ERROR: <err> See subclause 9.2 for <err> values. +CALM? Description: Syntax: Parameters: Example: Possible Responses: Report Current Alert Sound Mode The +CALM? command shows the current alert sound mode. AT+CALM? <cr> None AT+CALM? <cr> +CALM: <mode> +CME ERROR: <err> See subclause 9.2 for <err> values.
101
Chapter 3 AT Command Interface +CAMM Description: Accumulated Call Meter Maximum The +CAMM command sets the Advice of Charge related to the accumulated call meter maximum value in SIM file EF(ACMmax). ACMmax contains the maximum number of home units allowed to be consumed by the subscriber. AT+CAMM=[<acmmax>[,<passwd>]] <cr> <acmmax> string type; accumulated call meter maximum value similarly coded as <ccm> under +CAOC; 0 = disables ACMmax feature. <passwd> string type; SIM PIN2 Example: Possible Responses: AT+CAMM=0,password <cr> OK If error is related to ME functionality: +CME ERROR: <err> See subclause 9.2 for <err> values. +CAMM? Description: Syntax: Parameters: Example: Possible Responses: Report Current ACMmax Value The +CAMM? command returns the current value of ACMmax. AT+CAMM? <cr> None AT+CAMM=? <cr> +CAMM: <acmmax> OK where <acmmax> is the max. ACM value in
Syntax: Parameters:
102
Chapter 3 AT Command Interface +CAMM? Report Current ACMmax Value hexadecimal format (e.g., 00001E indicates decimal value 30). +CME ERROR: <err> See subclause 9.2 for <err> values. +CAOC Description: Advice of Charge Command The +CAOC command sets the Advice of Charge supplementary service function mode. This mode lets subscribers obtain information about a calls cost. AT+CAOC=<mode> <cr> <mode> = 0, 1, or 2 0 = query CCM value. 1 = deactivate the unsolicited reporting of CCM value. 2 = activate the unsolicited reporting of CCM value. <ccm> string type; three bytes of the current CCM value in hexadecimal format (e.g., 00001E indicates decimal value 30); bytes are similarly coded as ACMmax value in the SIM 000000-FFFFFF Example: Possible Responses: AT+CAOC=2 <cr> If error is related to ME functionality: +CME ERROR: <err> If <mode>=0, TA returns the current call meter (CCM) value +CAOC: <ccm> OK If <mode>=1, TA deactivates the unsolicited reporting of CCM value
Syntax: Parameters:
103
Chapter 3 AT Command Interface +CAOC Advice of Charge Command OK If <mode>=2, TA activates the unsolicited reporting of CCM value OK +CAOC=? Description: List Supported Advice of Charge Modes The +CAOC=? command lists the Advice of Charge modes that the GSM Data Module supports. AT+CAOC=? <cr> None AT+CAOC=? <cr> +CAOC: (list of supported <mode>s) OK Report Current Advice of Charge Mode The +CAOC? command reports the GSM Data Modules current Advice of Charge mode. AT+CAOC? <cr> None
Syntax: Parameters: Example: Possible Response: +CAOC? Description:
Syntax: Parameters: Example: Possible Response: +CBC Description:
+CAOC: <mode> OK Battery Charge The +CBC command allows the TA to return battery connection status <bcs> and battery
104
Chapter 3 AT Command Interface +CBC Syntax: Parameters: Example: Possible Responses: Battery Charge charge level <bcl> values. AT+CBC <cr> None AT+CBC <cr> +CBC: <bcs>,<bcl> OK where <bcs> = 0 or 1 0 = ME is powered by the battery. 1 = ME has a battery connected, but is not powered by it <bcl> = 0 or 100 0 = battery is exhausted. 100 = battery has full capacity remaining.
+CBC=? Description:
List Supported Battery Charge Values The +CBC=? command lists the battery charge values that the GSM Data Module supports. AT+CBC=? <cr> None AT+CBC=? <cr> +CBC: (list of supported <bes>s),(list of supported <bcl>s) OK Select Bearer Service The +CBST command selects the bearer service <name> with data rate <speed> and
+CBST Description:
105
Chapter 3 AT Command Interface +CBST Select Bearer Service the connection element <ce> to be used when data calls are originated. Values may also be used during mobile terminated data call setup, especially in case of single numbering scheme calls. AT+CBST=[<speed>] [,<name> [,<ce>]]] <cr> <speed> =0-2, 4-7, 14, 65, 66, 68, 70, 71, or 75 0 = autobauding. (DEFAULT) 1 = 300 bps (V.21). 2 = 1200 bps (V.22). 4 = 2400 bps (V.22bis). 5 = 2400 bps (V.26ter). 6 = 4800 bps (V.32). 7 = 9600 bps (V.32). 65 = 300 bps (V.110). 66 = 1200 bps (V.110). 68 = 2400 bps (V.110). 70 = 4800 bps (V.110). 71 = 9600 bps (V.110). 75 = 14400 bps (V.110). <name> = 0 or 2 0 = data circuit asynchronous modem. (DEFAULT) 2 = PAD Access (asynchronous) <ce> = 0 or 1 0 = transparent. 1 = non-transparent. (DEFAULT) Example: Possible Response: +CBST=? Description: AT+CBST=1,0,0 <cr> OK
Syntax: Parameters:
List Supported Bearer Services The +CBST=? command lists the bearer
106
Chapter 3 AT Command Interface +CBST=? Syntax: Parameters: Example: Possible Response: +CBST? Description: Syntax: Parameters: Example: Possible Responses: List Supported Bearer Services services that the GSM Data Module supports. AT+CBST=? <cr> None AT+CBST=? <cr> +CBST: (list of supported <speeds>, list of supported <names>, list of supported <ces>) OK Report Current Bearer Service The +CBST? command reports the current bearer service. AT+CBST? <cr> None AT+CBST? <cr> +CBST: <speed>,<name>,<ce> OK
+CCED Description:
Cell Environment Description The +CCED command can be used by the application to retrieve the cell parameters of the main cell and of up to six neighbor cells. Two ways may exist for the external application to know these cell parameters: on request of the application, or automatically by the module every 5 seconds. The automatic mode is not supported during communication or registration. AT+CCED=<m>[,<n>] <cr>
Syntax:
107
Chapter 3 AT Command Interface +CCED Parameters: Cell Environment Description <m> = 0, 1, or 2 0 = one shot requested. 1 = automatic shots requested. 2 = stop automatic shots. <n> = 1, 2, or 3 1 = main cell. MCC, MNC, LAC, CellId, BSIC, ARFCN, RxLev, RxLev Full, RxLevSub, RxQual, RxQual Full, RxQual Sub, Idle TS 2 = neighbor cell. MCC, MNC, LAC, CellId, BSIC, ARFCN, RxLev 3 = all cell. MCC, MNC, LAC, CellId, BSIC, ARFCN, RxLev, RxLev Full, RxLevSub, RxQual, RxQual Full, RxQual Sub, Idle TS, MCC, MNC, LAC, CellId, BSIC, ARFCN, RxLev Combination (addition of the values) of the requested dumped are supported. Notice that in idle mode, only RxLev measures (one the main cell and on the neighbor cells) are done. The value of these RxLev is set in the RxLev Full field for the main cell. Example: Possible Response: +CCFC Description: AT+CCED=0,1 <cr> +CCED:<value>, ... , <value> OK Call Forwarding and Conditions The +CCFC command allows control of the call forwarding supplementary service according to 3GPP TS 22.082 [4]. Registration, erasure, activation, deactivation, and status query are supported.
108
Chapter 3 AT Command Interface +CCFC Call Forwarding and Conditions When querying the status of a network service (<mode>=2) the response line for 'not active' case (<status>=0) should be returned only if service is not active for any <class>. AT+CCFC=<reas>, <mode>[, <number> [, <type>[,<class> [,<subaddr> [,<satype>[,<time>]]]]]] <cr> <reas> = 0, 1, 2, 3, 4, or 5 0 = unconditional. (DEFAULT) 1 = mobile busy. 2 = no reply. 3 = not reachable. 4 = all call forwarding (0-3). 5 = all conditional call forwarding (1-3). <mode> = 0, 1, 2, 3, or 4 0 = disable. (DEFAULT) 1 = enable. 2 = query status. 3 = registration. 4 = erasure. <number> string type phone number of forwarding address in format specified by <type> <type> type of address in integer format; DEFAULT is 145 when dialing string includes international access code character +; otherwise, 129. <subaddr> string type subaddress of format specified by <satype>. <satype> type of subaddress in integer; DEFAULT is 128. <class> = 1, 2, 4, or 7
Syntax:
Parameters:
109
Chapter 3 AT Command Interface +CCFC Call Forwarding and Conditions 1 = voice. 2 = data. 4 = fax. 7 = all classes. (DEFAULT) <time> time to wait before call is forwarded, rounded to a multiple of 5 sec. DEFAULT is 20. 1...20...30 (only for <reas> = no reply) <status> = 0 or 1 0 = not active. 1 = active. Example: Possible Response: +CCFC=? Description: AT+CCFC=1,1,5551212 <cr> OK
List Supported Call Forwarding Reasons The +CCFC=? command lists the call forwarding reasons that the GSM Data Module supports. AT+CCFC=? <cr> None AT+CCFC=? <cr> +CCFC: (list of supported <reas> OK Clock The +CCLK command sets the real-time clock of the ME. AT+CCLK=<time> <cr>
Syntax: Parameters: Example: Possible Responses: +CCLK Description: Syntax:
110
Chapter 3 AT Command Interface +CCLK Parameters: Clock <time> String-type value; format is yy/MM/dd,hh:mm:sszz, where characters indicate year (two last digits), month, day, hour, minutes, seconds, and time zone (indicates the difference, expressed in quarters of an hour, between the local time and GMT; range 47...+48); e.g. 6th of May 1994, 22:10:00 GMT+2 hours equals 94/05/06,22:10:00+08. AT+CCLK=01/05/25,15:00:00-08 <cr> OK If setting fails in an ME error: +CME ERROR: <err> See subclause 9.2 for <err> values. +CCLK? Description: Syntax: Parameters: Example: Possible Responses: Read Current Clock Setting The +CCLK? command reads the current clock setting. AT+CCLK=? <cr> None AT+CCLK? <cr> +CCLK:01/05/25.16:01:00-08 OK If an ME error occurs: +CME ERROR: <err> See subclause 9.2 for <err> values. If the ME does not support time zone information, the three last characters of <time> are not returned. The format of
111
Chapter 3 AT Command Interface +CCLK? Read Current Clock Setting <time> is specified by use of the +CSDF command.
+CCUG Description:
Closed User Group The +CCUG command sets the closed user group supplementary service parameters as a default adjustment for all following calls. AT+CCUG=[<n>] [,<index> [,<info>]]] <cr> <n> = 0 or 1 0 = disable CUG. (DEFAULT) 1 = enable CUG. <index> = 09, or 10 0...9 = CUG index. (DEFAULT = 0) 10 = no index (preferred CUG taken from subscriber data). <info> = 0, 1, 2, or 3 0 = no information. (DEFAULT) 1 = suppress OA (Outgoing Access). 2 = suppress preferential CUG. 3 = suppress OA and preferential CUG.
Syntax: Parameters:
Example: Possible Response: +CCUG=? Description:
AT+CCUG=1,9,2 <cr> OK
List Supported Closed User Groups The +CCUG=? command lists the closed user groups that the GSM Data Module supports. AT+CCUG=? <cr>
Syntax:
112
Chapter 3 AT Command Interface +CCUG=? Parameters: Example: Possible Responses: +CCUG? Description: List Supported Closed User Groups None AT+CCUG=? <cr> OK Report Current Closed User Group The +CCUG? command reports the current closed user group configured for the GSM Data Module. AT+CCUG? <cr> None AT+CCUG? <cr> +CCUG: <n>,<index>,<info> OK If error is related to ME functionality: +CME ERROR: <err>
+CCWA Description:
Call Waiting The +CCWA command controls the call waiting supplementary service. Activation, deactivation and status query are supported. It should be possible to abort the command when network is interrogated. AT+CCWA=[<n>][,<mode>[,<class >]]] <cr> <n> = 0 or 1 0 = disable presentation of unsolicited result code. (DEFAULT) 1 = enable presentation of unsolicited result code.
Syntax: Parameters:
113
Chapter 3 AT Command Interface +CCWA Call Waiting <mode> = 0, 1, or 2 when <mode> parameter not given, network is not interrogated 0 = disable. 1 = enable. 2 = query status. <class> = 1, 2, 4, or 7 a sum of integers each representing a class of information 1 = voice (telephony) 2 = data (usually refers to all bearer services, if <mode>=2, this may refer only to some bearer services). 4 = fax. 7 = all classes. (DEFAULT) <status> = 0 or 1 0 = not active. 1 = enable. Examples: Possible Response: +CCWA=? Description: AT+CCWA=1,1,1 <cr> AT+CCWA=1,2 <cr> OK
List Supported Call Waiting Values The +CCWA=? command returns a list of the call waiting values that the GSM Data Module supports. AT+CCWA=? <cr> None AT+CCWA=? <cr>
114
Chapter 3 AT Command Interface +CCWA=? Possible Responses: +CCWA? Description: Syntax: Parameters: Example: Possible Response: +CCWE Description: List Supported Call Waiting Values +CCWA: <n> OK Report Current Call Waiting Status The +CCWA? command shows whether current call waiting is enabled or disabled. AT+CCWA? <cr> None AT+CCWA? <cr> +CCWA: <n> OK Call Meter Maximum Event Shortly before the ACM (Accumulated Call Meter) maximum value is reached, an unsolicited result code +CCWV is sent, if enabled by this command. The warning is issued approximately when 30 seconds call time remains. It is also issued when starting a call if less than 30 s call time remains. If setting fails in an ME error, +CME ERROR: <err> is returned. Refer subclause 9.2 for <err> values. AT+CCWE=<mode> <cr> <mode> = 0 or 1 0 = disable the call meter warning event. (DEFAULT) 1 = enable the call meter warning event. AT+CCWE=1 <cr> AT+CCWE=2 <cr> OK
Syntax: Parameters:
Examples: Possible
115
Chapter 3 AT Command Interface +CCWE Response: +CCWE=? Description: Call Meter Maximum Event
List Supported Call Meter Maximum Modes The +CCWE=? command returns a list of the supported call meter maximum event modes. AT+CCWE=? <cr> None AT+CCWE=? <cr> +CCWE: <mode> OK Report Current Call Meter Maximum Event Mode The +CCWE? command shows the current call meter maximum event mode. AT+CCWE? <cr> None AT+CCWE? <cr> +CCWE: <mode> OK Display Control The +CDIS command writes the contents of ME text type display elements. An element can consist of one character or several characters. The order of element parameters <text> should be as follows: first
Syntax: Parameters: Example: Possible Responses: +CCWE? Description: Syntax: Parameters: Example: Possible Response: +CDIS Description:
116
Chapter 3 AT Command Interface +CDIS Display Control is the element in upper-left corner, second is the next element to the right, and so on. The last element is the element in lower-right corner. The number of elements is ME specific. If element parameter is empty, element will remain in the previous value. AT+CDIS=[<text>[,<text>[,...]]] <cr> <text> String type parameter using character set specified by the command +CSCS. AT+CDIS="RADIOGSM <cr> OK If the ME does not allow writing to its display or if the ME is not currently reachable: +CME ERROR: <err> See subclause 9.2 for <err> values. +CDIS=? Description: Syntax: Parameters: Example: Possible Responses: List Supported Character Sets The +CDIS=? command returns the contents of ME display elements. AT+CDIS=? <cr> None AT+CDIS=? <cr> +CDIS: <length>[,<length>[,...]] OK where <length> = integer type parameter giving the maximum length of corresponding <text> parameter. If the ME does not allow writing to its
Syntax: Parameters:
117
Chapter 3 AT Command Interface +CDIS=? List Supported Character Sets display or if the ME is not currently reachable: +CME ERROR: <err> See subclause 9.2 for <err> values. Report Current Character Set The +CDIS? command returns the maximum length of each display element. If the ME does not offer the length of elements, the <length> field should be empty. AT+CDIS? <cr> None AT+CDIS? <cr> +CDIS: <text>[,<text>[,...]] OK where <text> is a string-type parameter using character set specified by the command +CSCS. If the ME does not allow writing to its display or if the ME is not currently reachable: +CME ERROR: See subclause 9.2 for <err> values. +CEER Description: Extended Error Reporting The +CEER command returns an extended report for the reason of the failure in the last unsuccessful call setup (originating or answering). Typically, the text consists of a single line containing the failure information given by GSM network in textual format. AT+CEER <cr>
+CDIS? Description:
Syntax:
118
Chapter 3 AT Command Interface +CEER Parameter: Example: Possible Response: Extended Error Reporting None AT+CEER <cr> +CEER: <report> OK where <report> is the reason for last call release as number code. Test Extended Error Reporting The +CEER=? command is a test command. AT+CEER=? <cr> None AT+CEER=? <cr> OK Set Phone Functionality The +CFUN command selects the level of functionality in the mobile station. AT+CFUN=<L> <cr> <L> the ID to be set, as described in the examples. When the application wants to stop the module to make a power off, or if the application wants to force the module to execute an IMSI DETACH procedure, it has to send: AT+CFUN=0 <cr> This command executes an IMSI DETACH and makes a backup of some internal
+CEER =? Description: Syntax: Parameters: Example: Possible Response: +CFUN Description: Syntax: Parameters: Examples:
119
Chapter 3 AT Command Interface +CFUN Set Phone Functionality parameters in the SIM and the EEPROM. Then no access to the SIM card is possible. If the mobile is not powered off after this command, it shall receive another command to re-start the whole GSM process. If the mobile is turned off after this command, the power-on automatically executes the start of the whole GSM process. When the application wants to re-start the module (after having done a AT+CFUN=0 command, and without having cut the power supply), it must send: AT+CFUN=1 This command starts again all the GSM stack and GSM functionality and a complete software reset is done. All parameters are reset to their previous E2P value if AT&W was not used. If you write entries in phonebook (+CPBW) and then reset the module directly (AT+CFUN=1, without any AT+CFUN=0 before), some entries may not be written (SIM task did not have enough time to write the entries in SIM card) Also, the OK response will be sent at the last defined baud rate defined by +IPR command. With autobauding the response can be at a different baud rate, so it is better to save the defined baud rate with AT&W before directly send the AT+CFUN=1 command. Possible Response: +CFUN? Description: OK
Report Current Phone Functionality The +CFUN? command reports the GSM
120
Chapter 3 AT Command Interface +CFUN? Syntax: Parameters: Example: Possible Response: +CFUN=? Description: Syntax: Parameters: Example: Possible Response: Report Current Phone Functionality Data Modules current phone functionality. AT+CFUN? <cr> None AT+CFUN? <cr> +CFUN: 1 OK List Supported Phone Functionality The +CFUN=? command is a test command. AT+CFUN=? <cr> None AT+CFUN=? <cr> +CFUN: 1 OK
+CGMI Description: Syntax: Parameters: Examples: Possible Response:
Report Manufacturer Identification The +CGMI command reports the GSM Data Modules manufacturer identification. AT+CGMI <cr> None AT+CGMI <cr> CONEXANT OK
121
Chapter 3 AT Command Interface +CGMM Description: Syntax: Parameters: Example: Possible Response: +CGMR Description: Syntax: Parameters: Example: Possible Response: +CGSN Description: Request Module ID The +CGMM command reports the specific model of the GSM Data Module. AT+CGMM <cr> None AT+CGMM <cr> +GSMDM100DB OK Request Revision ID The +CGMR command reports the GSM Data Modules software version. AT+CGMR <cr> None AT+CGMR <cr> Revision x.yy OK Request Product Serial Number Identification The +CGSN command allows the user application to ascertain the GSM modules International Mobile Equipment Identify (IMEI). AT+CGSN <cr> None AT+CGSN <cr>
122
Chapter 3 AT Command Interface +CGSN Possible Response: +CHLD Description: Request Product Serial Number Identification 135790248939 OK Call Hold The +CHLD command allows the control of the following call-related services:
A call can be temporarily disconnected from the ME but the connection is retained by the network. Multiparty conversation (conference calls). the served subscriber who has two calls (one held and the other either active or alerting) can connect the other. Parties and release the served subscriber's own connection.
Calls can be put on hold, recovered, released, added to conversation, and transferred similarly as defined in 3GPP TS 22.030 [19]. Refer subclause 9.2 for possible <err> values. This is based on the GSM/UMTS supplementary services HOLD (Call Hold; refer 3GPP TS 22.083 [5] clause 2), MPTY (MultiParty; refer 3GPP TS 22.084 [22]) and ECT (Explicit Call Transfer; refer 3GPP TS 22.091 [29]). The interaction of this command with other commands based on other GSM/UMTS supplementary services is described in the GSM/UMTS standards. Call Hold, MultiParty, and Explicit Call
123
Chapter 3 AT Command Interface +CHLD Call Hold Transfer are only applicable to teleservice 11. It is recommended (although optional) that test command returns a list of operations which are supported. The call number required by some operations shall be denoted by x (e.g., +CHLD: (0,1,1x,2,2x,3)). Syntax: Parameters: AT+CHLD=<n> <cr> <n> = 0, 1, 1X, 2, 2X, or 3 0 = terminate all held calls or UDUB (User Determined User Busy) for a waiting call 1 = terminate all active calls (if any) and accept the other call (waiting call or held call). 1X = terminate the active call number X (X= 1-7). 2 = place all active calls on hold (if any) and accept the other call (waiting call or held call) as the active call. 2X = place all active calls except call X (X = 17) on hold. 3 = add the held call to the active calls. AT+CHLD=1 <cr> OK
Example: Possible Response: +CHLD=? Description: Syntax: Parameters:
List Supported Call Hold Parameters The +CHLD=? command lists the supported call hold parameters AT+CHLD=? <cr> None
124
Chapter 3 AT Command Interface +CHLD=? Example: Possible Response: +CHUP Description: Syntax: Parameters: Example: Possible Responses: List Supported Call Hold Parameters AT+CHLD=? <cr> +CHLD:<n>s OK Select Hang Up Call The +CHUP command causes the TA to hang up the current call. AT+CHUP <cr> None AT+CHUP <cr> OK/ERROR All active calls and held calls are cleared down. Report Hang Up The +CHUP=? command reports whether the current call has been hung up AT+CHUP=? <cr> None AT+CHUP=? <cr> OK
+CHUP=? Description: Syntax: Parameters: Example: Possible Response: +CIMI Description:
Request International Mobile Subscriber Identity The +CIMI command reads and identifies the International Mobile Subscriber Identity
125
Chapter 3 AT Command Interface +CIMI Request International Mobile Subscriber Identity (IMSI) of the attached SIM card. AT+CIMI <cr> <IMSI> = International Mobile Subscriber Identity (string without double quotes) AT+CIMI <cr> 001010123456789 OK If error is related to ME functionality: +CME ERROR: <err> +CIMI=? Description: Syntax: Parameters: Example: Possible Response: +CIND Description: List International Mobile Subscriber Identity The +CIMI=? command reports the International Mobile Subscriber Identity. AT+CIMI=? <cr> <IMSI> = International Mobile Subscriber Identity (string without double quotes). AT+CIMI=? <cr> OK Indicator Control The +CIND command sets the values of the ME indicators. An <ind> value of 0 means that the indicator is off (or in state which can be identified as "off"-state), 1 means that indicator is on (or in a state which is more substantial than "off"-state), 2 is more substantial than 1, and so on. If the indicator
126
Chapter 3 AT Command Interface +CIND Indicator Control is a simple on/off style element, it has values 0 and 1. The number of elements is ME specific. If a certain indicator is not writable, setting of it should be ignored. If a parameter is empty field, the indicator remains in the previous value. Syntax: Parameters: AT+CIND=[<ind>[,<ind>[,...]]] <cr> <ind> an integer type value in the range corresponding to <descr>. AT+CIND=0 <cr> OK If the ME does not allow setting of indicators or ME is not currently reachable: +CME ERROR: <err> See subclause 9.2 for <err> values. +CIND=? Description: Syntax: Parameters: Example: Possible Responses: Return Status of Indicators The +CIND=? command returns the status of the ME indicators. AT+CIND=? <cr> None AT+CIND=? <cr> +CIND: (<descr>,(list of supported <ind>s)) [,(<descr>,(list of supported <ind>s))[,...]] where <descr> = values reserved by the
127
Chapter 3 AT Command Interface +CIND=? Return Status of Indicators present document and their <ind> ranges: battchg = battery charge level (0-5). signal = signal quality (0-5). service = service availability (0-1). sounder = sounder activity (0-1). message = message received (0-1). call = call in progress (0-1). vox = transmit activated by voice activity (0-1). roam = roaming indicator (0-1). Smsfull = a short message memory storage in the MT has become full (1), or memory locations are available (0). If the ME does not allow setting of indicators or ME is not currently reachable: +CME ERROR: <err> See subclause 9.2 for <err> values. +CIND? Description: Report Current Indicator Status The +CIND? command returns a maximum 16-character description of the indicator and Compound value is the allowed values for the indicator. AT+CIND <cr> None AT+CIND <cr> +CIND: <ind>[,<ind>[,...]] OK where <ind> is an integer type value in the range of the corresponding <descr>. If the ME does not allow setting of indicators or ME is not currently reachable: +CME ERROR: <err>
128
Chapter 3 AT Command Interface +CKPD Description: Keypad Control The +CKPD command provides keypad control. When you send this command:
If any call is in progress: then this command should decrease/increase the audio volume If there is no call in progress : this command should decrease/increase the ringer volume.
You may need a phone to test this command. Syntax: Parameters: AT+CKPD=[<D>][][<E>][] [<Q>][<R>][<S>][<W>] <cr> <D> = decrease the volume. = increase the volume. <E> = hang up current call (like ATCHUP). = power-down and reset. <Q> = mute the GSM Data Module. <R> = recall the last number dialed. <S> = send either the last-number dialed or the number stored in the CKPD buffer. <V> = decrease audio volume. <W> = append a pause character to the CKPD buffer. <Y> = clear the CKPD buffer. <^> = increase audio volume. <[> = increase ringer volume. <]> = decrease ringer volume. Ending a Call AT+CKPD="E" Ends the call. This command works like the AT+CHUP command and ends the current call in progress. Power-down and Reset GSM Data Module AT+CKPD="P" Powers down the GSM Data Module, returns the OK result code, and resets the GSM Data
Functions:
129
Chapter 3 AT Command Interface +CKPD Keypad Control Module. Mute the GSM Data Module AT+CKPD="Q" Mutes the GSM Data Modules audio volume. Recall Last Number Dialed AT+CKPD="R" This command returns OK. To recall the last number dialed: 1. Type AT+CKPD="1234S" or ATD1234; followed by any number string. 2. Press <cr>. 3. Type AT+CKPD="4567" followed by a number string other than the one dialed in step 1. This command saves 4567 in the CKPD buffer. 4. Press <cr>. 5. Type AT+CKPD="R" <cr>. 6. Type AT+CKPD="S" <cr>. The dialed number should be 1234 and not 4567. 7. Type AT+CKPD="S" <cr>. This command sends either the last number dialed or the number stored in the CKPD buffer. To test this command: 1. Type AT+CKPD="1234" followed by any number string. 2. Type AT+CKPD="S" <cr>. The number specified above should be dialed. You can also test this command by: 1. Typing AT+CKPD="4567S" or ATD4567; followed by any number string. 2. Pressing <cr>. 3. Typing AT+CKPD="S" <cr>. The number 4567 should be dialed. Decrease Audio Volume AT+CKPD=V This command decreases the audio volume,
130
Chapter 3 AT Command Interface +CKPD Keypad Control regardless of whether a conversation is taking place. This command returns an OK result code. Append a Pause Character AT+CKPD="W" Appends the w pause character to the CKPD buffer. This command can be used as follows: AT+CKPD="W678" This example appends the w and the 678 to the CKPD buffer. Clearing the CKPD Buffer AT+CKPDY Clears the contents of the CKPD buffer. This command returns the OK result code. Increase Audio Volume AT+CKPD^ Increases audio volume, regardless of whether a conversation is occurring. This command returns the OK result code. Increase Ringer Volume AT+CKPD[ Increases ringer volume, regardless of whether a conversation is occurring. This command returns the OK result code. Decrease Ringer Volume AT+CKPD] Decreases ringer volume, regardless of whether a conversation is occurring. This command returns the OK result code. Placing a Call with CKPD There are six ways to place a call with CKPD: 1. Type AT+CKPD=<any number string>S. Example: AT+CKPD=1234S <cr> GSM Data Module dials 1234.
131
Chapter 3 AT Command Interface +CKPD Keypad Control 2. AT+CKPD=1234 <cr> AT+CKPD=S <cr> GSM Data Module dials 1234, which is the number stored in the CKPD buffer 3. AT+CKPD=1234 <cr> Number gets stored in the CKPD buffer AT+CKPD=S <cr> GSM Data Module dials the number stored in the buffer viz. 1234 ATH <cr> Call the buffer is cleared, If you now type: AT+CKPD=S <cr> you receive ERROR because the operation is not allowed since the CKPD buffer is empty. 4. AT+CKPD=0119122 <cr> Stores number in CKPD buffer AT+CKPD=7899089S <cr> Dials the resultant of the number stored in the buffer (0119122) and the number dialed in the command(7899089). The final number dialed should be 01191227899089. 5. AT+CKPD=1234s <cr> After the call connect, make another call AT+CKPD=5678s <cr> NO CARRIER should appear. 6. Making multiparty calls with CKPD AT+CKPD=0S AT+CHLD=0 AT+CKPD=1Xs AT+CHLD=1X AT+CKPD 0S , 1S, 1XS, 2S, 2XS, and 3S are the equivalent of the AT+CHLD 0,1,1X,2,2X and 3. Storing Strings
132
Chapter 3 AT Command Interface +CKPD Keypad Control Use AT+CKPD=1234 (a number string) to store the dial string in the CKPD buffer, when the call is not in progress. After the call is made, the CKPD buffer is cleared. Example 1: 1. AT+CKPD=12345 <cr> After the above command, if you type AT+CKPD=S <cr> the GSM Data Module dials 12345. 2. AT+ CKPD=5 <cr> Appends 5 to the CKPD buffer. AT+CKPD=6 <cr> Appends 6 to the CKPD buffer. AT+CKPD=3 <cr> Appends 3 to the CKPD buffer. AT+CKPD=4 <cr> Appends 4 to the CKPD buffer. AT+CKPD=5 <cr> Appends 5 to the CKPD buffer. If you now type AT+CKPD=S <cr>, the GSM Data Module dials 56345. Supplementary Services Strings To be tested as before DTMF You can now use +CKPD to send DTMF strings. Using +CKPD, you can send an entire DTMF string or character by character. DTMF digits can be sent only when a call is in progress. AT+CKPD=<dtmf string>,<time duration for tone>, <pause between 2 consecutive tones>
133
Chapter 3 AT Command Interface +CKPD Keypad Control

<dtmf string> can have the following characters: 0-9, *, #, A, B, C,D , w, and , (comma) <time duration for tone> can be from 0 to 255. If omitted, default is taken. <pause between 2 consecutive tones> can be from 0 to 255. If omitted, default is taken.
Sending DTMF Strings You can now use the +CKPD command to send an entire string of DTMF characters. +CKPD takes care of sending the DTMF characters. Example: Example 1 Making a call: AT+CKPD="1234s" <cr> OR ATD1234; <cr> When call is connected AT+CKPD="5678" <any number string> <cr> sends the DTMF digits 5, 6, 7, 8; you should hear the tone for 5; then a pause and the tone for 6; then a pause and the tone for 7; then a pause and the tone for 8. The command should then return with OK. Example 2 Making a call and sending the DTMF string in the same command: AT+CKPD="1234s" <cr> AT+CKPD="7898#wwABCD" <cr> This command line dials the number 1234, then the following DTMF tones should be heard:
7, then pause
134
Chapter 3 AT Command Interface +CKPD Keypad Control

8, then pause 9, then pause 8, then pause #, then pause
Then there should again be a 4-second wait (each w equals 2 seconds) followed by the DTMF tones corresponding to the next string:

A, then pause B, then pause C, then pause D, then pause
Lastly, OK should be returned Example 3 In the above examples, the DTMS string was dialed, a few digits are sent, and the called part is disconnected. There should be no resets. ERROR should be returned if the called party is disconnected while a DTMF digit is being sent/played. Possible Responses: OK If emulating fails: +CME ERROR: <err> See subclause 9.2 for <err> values. +CLCC Description: List Current Calls The +CLCC command returns a list of current calls of ME. If this command succeeds but no calls are available, no information response is sent to the TE.
135
Chapter 3 AT Command Interface +CLCC Syntax: Parameters: Example: Possible Response: List Current Calls AT+CLCC <cr> None AT+CLCC <cr> [+CLCC:<id1>,<dir>,<stat>,<mode>,<mpty> [,<number>,<type>[,<alpha>]][<cr><lf> +CLCC:<id2>,<dir>,<stat>,<mode>,<mpty>[ ,<number>,<type>[,<alpha>]][...]]] OK where: <idx> is the integer type; call identification number as described in GSM 02.30[19] subclause 4.5.5.1; this number can be used in +CHLD command operations <dir> = 0 or 1 0 = mobile originated (MO) call. 1 = mobile terminated (MT) call. <stat> is the state of the call 0, 1, 2, 3, 4, or 5: 0 = active. 1 = held. 2 = dialing (MO call). 3 = alerting (MO call). 4 = incoming (MT call). 5 = waiting (MT call). <mode> bearer/teleservice 0, 1, 2, or 9: 0 = voice. 1 = data. 2 = fax. 9 = unknown. <mpty> = 0 or 1 0 = call is not one of multiparty (conference) call parties.
136
Chapter 3 AT Command Interface +CLCC List Current Calls 1 = call is one of multiparty (conference) call parties. <number> string-type phone number in format specified by <type>. <type> type of address octet in integer format; 145 when dialing string includes international access code character +; otherwise, 129. <alpha> string-type alphanumeric representation of <number> corresponding to the entry found in phonebook. If error is related to ME functionality: +CME ERROR: <err> +CLCC=? Description: Syntax: Parameters: Example: Possible Responses: +CLCK Description: Current Calls Test Command The +CLCC=? command is a test command. AT+CLCC=? <cr> None AT+CLCC=? <cr> OK
Facility Lock The +CLCK command locks, unlocks, or interrogates an ME or network facility <fac>. Password is normally needed for such actions. When querying the status of a network service (<mode>=2) the response
137
Chapter 3 AT Command Interface +CLCK Facility Lock line for not-active case (<status>=0) should be returned only if service is not active for any <class>. It should be possible to abort the command when network facilities are set or interrogated. AT+CLCK=<fac>, <mode> [,<passwd>[,<class>]] <cr> <fac> = AO, OI, OX, AI, IR, AB, AG, AC, SC, FD, or PN AO = Bar All Outgoing Calls (BAOC). OI = Bar Outgoing International Calls (BOIC). OX = Bar Outgoing International Calls except to Home Country (BOIC-exHC). AI = Bar All Incoming Calls (BAIC). IR = Bar Incoming Calls when roaming outside the home country (BIC-Roam). AB = All Barring services (applicable only for <mode>=0). AG = All outgoing barring services (applicable only for <mode>=0). AC = All incoming barring services (applicable only for <mode>=0). SC = lock SIM cards (SIM). SIM requests password at ME power-up and when this lock command issued. FD = SIM fixed-dialing memory feature. If PIN2 authentication has not been performed during the current session, PIN2 is required as <passwd>. PN = Network Personalization (see GSM 02.22[33]). <mode> = 0, 1, or 2 0 = unlock. 1 = lock. 2 = query status. <passwd> = password
Syntax: Possible Responses:
138
Chapter 3 AT Command Interface +CLCK Facility Lock if <fac> = PS, then user password. if <fac> = SC, then PIN. if <fac> = FD, then PIN2. if <fac> = AO...AC (Barring), then Network password. if <fac> = PN...PC, then user password. <class> = 1, 2, 4, 7, 8, or 16 1 = voice. 2 = data. 4 = fax. 7 = voice, data, and fax. 8 = SMS. 16 = data (all sync services). If <class> is omitted, all possible classes (depending on the network provider) are locked or unlocked. e.g., AT+CLCK="AO",1,"xxxx" <status> = 0, 1, or 2 0 = off. 1 = on. 2 = query status. Example: Possible Responses: AT+CLCK=AO1,1234 <cr> If <mode>=2 and command is successful: OK If <mode>=2 and command is successful: +CLCK: <status>[,<class1>[<cr><lf> +CLCK: <status>, class2....]] OK If error is related to ME functionality: +CME ERROR: <err> +CLCK=? Description: List Supported Network Facilities The +CLCK=? command lists the supported network facilities.
139
Chapter 3 AT Command Interface +CLCK=? Syntax: Parameters: Example: Possible Response: List Supported Network Facilities AT+CLCK=? <cr> None AT+CLCK=? <cr> +CLCK: ("AO")("OI")("OX")("AI")("IR") ("AB")("AG")("AC")("SC")("FD") ("PN") OK Calling Line ID Presentation The +CLIP command enables or disables the presentation of the CLI at the TE. It has no effect on the execution of the supplementary service CLIP in the network. AT+CLIP=<n>, <m> <cr> <n> = 0 or 1 0 = suppress unsolicited result codes. 1 = display unsolicited result codes. <m> = 0, 1, or 2 0 = CLIP not provisioned. 1 = CLIP provisioned. 2 = unknown. Example: Possible Responses: AT+CLIP 1,1 <cr> OK Unsolicited result code: When +CLIP is enabled at the TE (and is permitted by the calling subscriber), an unsolicited result code is returned after every RING (or +CRING: <type>) at a mobile terminating call. +CLIP: <number>, <type> There are four different cases for +CLIP:
+CLIP Description:
Syntax: Parameters:
140
Chapter 3 AT Command Interface +CLIP Calling Line ID Presentation +CLIP: "number", <type> +CLIP: "number pres restricted", <type> +CLIP: "number not available", <type> (provider specific) +CLIP: "", <type> (provider specific) Parameter <number> = string type phone number of calling address in format specified by <type> <type> = type of address octet in integer format; 145 when dialing string includes international access code character +; otherwise, 129. +CLIP =? Description: Syntax: Parameters: Example: Possible Response: +CLIP? Description: Syntax: Parameters: Example: Possible List Supported Unsolicited Result Codes The +CLIP =? command lists the supported unsolicited result codes. AT+CLIP=? <cr> None AT+CLIP=? <cr> +CLIP: (list of supported <n>s) OK Report Current Unsolicited Result Code The +CLIP? command reports the GSM Data Modules unsolicited result codes. AT+CLIP? <cr> None AT+CLIP? <cr> +CLIP: <n>, <m>
141
Chapter 3 AT Command Interface +CLIP? Responses: Report Current Unsolicited Result Code OK If error is related to ME functionality: +CME ERROR: <err> +CLIR Description: Calling Line Identification Restriction The +CLIR command restricts or enables the presentation of the CLI to the called party when originating a call. The command overrides the CLIR subscription (default is restricted or allowed) when temporary mode is provisioned as a default adjustment for all following outgoing calls. This adjustment can be revoked by using the opposite command. AT+CLIR=[<n>] <cr> <n> sets the adjustment for outgoing calls 0, 1, or 2: 0 = presentation indicator is used according to the subscription of the CLIR service. 1 = CLIR invocation. 2 = CLIR suppression. <m> shows the subscriber CLIR service status in the network 0, 1, 2, 3, or 4: 0 = CLIR not provisioned. 1 = CLIR provisioned in permanent mode. 2 = unknown (e.g., no network). 3 = CLIR temporary mode presentation restricted. 4 = CLIR temporary mode presentation allowed. Example: Possible Response: AT+CLIR=1,3 <cr> OK
Syntax: Parameters:
142
Chapter 3 AT Command Interface +CLIR=? Description: Syntax: Parameters: Example: Possible Responses: +CLIR? Description: List Supported Calling Line Identification Restrictions The +CLIR=? command lists the supported calling line identification restrictions. AT+CLIR=? <cr> None AT+CLIR=? <cr> +CLIR: (list of supported <n>s) OK Report Current Calling Line Identification Restrictions The +CLIR? command reports the current calling line identification restrictions for the GSM Data Module. AT+CLIR? <cr> None AT+CLIR? <cr> +CLIR: <n>, <m> OK If error is related to ME functionality: +CME ERROR: <err> +CLVL Description: Syntax: Parameters: Loudspeaker Volume Level The +CLVL command selects the volume of the internal loudspeaker of the ME. AT+CLVL=<level> <cr> <level> integer-type value with manufacturer-specific
143
Chapter 3 AT Command Interface +CLVL Loudspeaker Volume Level range (smallest value represents the lowest sound level). AT+CLVL=10 <cr> OK +CME ERROR: <err> See subclause 9.2 for <err> values. +CLVL=? Description: List Supported Loudspeaker Volume Levels The +CLVL=? command lists, as compound values, the loudspeaker volume levels that the GSM Data Module supports. AT+CLVL=? <cr> None AT+CLVL=? <cr> +CLVL: (list of supported <level>s) OK +CME ERROR: <err> See subclause 9.2 for <err> values. +CLVL? Description: Syntax: Parameters: Example: Report Current Loudspeaker Volume Level The +CLVL? command reports the current loudspeaker volume level. AT+CLVL? <cr> None AT+CLVL? <cr>
144
Chapter 3 AT Command Interface +CLVL? Possible Responses: Report Current Loudspeaker Volume Level +CLVL: <level> OK +CME ERROR: <err> See subclause 9.2 for <err> values. +CMEC Description: Mobile Equipment Control Mode The +CMEC command selects the equipment that operates ME keypad, writes to the ME display, and sets the ME indicators. +CMEC=[<keyp>[,<disp>[,<ind>]]] <cr> <keyp> = 0, 1, or 2 0 = ME can be operated only through its keypad (the +CKPD cannot be used). 1 = ME can be operated only from TE (with command +CKPD). 2 = ME can be operated from both ME keypad and TE. <disp> = 0, 1, or 2 0 = only ME can write to its display (command +CDIS can only be used to read the display). 1 = only TE can write to ME display (with command +CDIS). 2 = ME display can be written by both ME and TE. <ind> = 0, 1, or 2 0 = only ME can set the status of its indicators (command +CIND can only be used to read the indicators). 1 = only TE can set the status of ME indicators (with the command +CIND). 2 = ME indicators can be set by both ME and TE.
Syntax: Parameters:
145
Chapter 3 AT Command Interface +CMEC Example: Possible Response: +CMEC=? Description: Syntax: Parameters: Example: Possible Response: +CMEC? Description: Mobile Equipment Control Mode AT+CMEC=0,0,0 <cr> OK
List Supported Mobile Equipment Control Modes The +CMEC=? command lists the supported mobile equipment control modes. AT+CMEC=? <cr> None AT+CMEC=? <cr> +CMEC: (list of supported <keyp>s),(list of supported <disp>s),(list of supported <ind>s) OK Report Current Mobile Equipment Control Mode The +CMEC? command reports the GSM Data Modules current mobile equipment control mode. AT+CMEC? <cr> None AT+CMEC? <cr> +CMEC: <keyp>,<disp>,<ind> OK Mobile Equipment Error Code The +CMEE command disables or enables
Syntax: Parameters: Example: Possible Response: +CMEE Description:
146
Chapter 3 AT Command Interface +CMEE Mobile Equipment Error Code the use of result code +CME ERROR: <err> as an indication of an error relating to ME functionality. AT+CMEE=<n> <cr> <n> = 0, 1, or 2 0 = disable +CME ERROR: <err> result code and use ERROR instead. (DEFAULT) 1 = enable +CME ERROR: <err> result code and use numeric <err> values (see Table 3-3 on page 148). 2 = enable +CME ERROR: <err> result code and use verbose <err> values (see Table 3-3 on page 148). AT+CMEE=2 <cr> OK +CME ERROR: <err> as an indication of an error relating to the functionality of the ME. When enabled, ME-related errors cause +CME ERROR: <err> final result code instead of the regular ERROR final result code. ERROR is returned normally when error is related to syntax, invalid parameters, or TA functionality. +CMEE? Description: Syntax: Parameters: Report Mobile Equipment Error Code The +CMEE? command returns values supported by the TA as a compound value. AT+CMEE? <cr> None
Syntax: Parameters:
147
Chapter 3 AT Command Interface +CMEE? Example: Possible Response: Report Mobile Equipment Error Code AT+CMEE? <cr> +CMEE: (list of supported <n>s) OK
Table 3-3. General Errors Error 0 1 2 3 4 5 6 7 10 11 12 13 14 15 16 17 18 20 21 22 23 24 25 26 27 30 31 32 40 41 42 43 Text General Errors Phone failure No connection to phone Phone-adapter link reserved Operation not allowed Operation not supported PH-SIM P IN required PH-FSIM P IN required PH-FSIM PUK required SIM not inserted SIM PIN required SIM PUK required SIM failure SIM busy SIM wrong Incorrect password SIM PIN2 required SIM PUK2 required Memory full Invalid index Not found Memory failure Text string too long Invalid characters in text string Dial string too long Invalid characters in dial string No network service Network timeout Network not allowed - emergency calls only Network personalization PIN required Network personalization PUK required Network subset personalization PIN required Network subset personalization PUK required
148
Chapter 3 AT Command Interface Error 44 45 46 47 100 Text Service provider personalization PIN required Service provider personalization PUK required Corporate personalization PIN required Corporate personalization PUK required Unknown Attach-Related Errors (values in parentheses are GSM 04.08 cause codes) 103 Illegal MS (#3) 106 Illegal ME (#6) 107 GPRS services not allowed (#7) 111 PLMN not allowed (#11) 112 Location area not allowed (#12) 113 Roaming not allowed in this location area (#13) Activate a Context-Related Errors (values in parentheses are GSM 04.08 cause codes) 132 Service option not supported (#32) 133 Requested service option not subscribed (#33) 134 Service option temporarily out of order (#34) 149 PDP authentication failure Other GPS Errors 148 Unspecified GPRS error 150 Invalid mobile class Other values in the range 101 150 are reserved for use by GPRS. Also all other values below 256 are reserved.
+CMER Description:
Mobile Equipment Event Reporting The +CMER command enables or disables sending of unsolicited result codes from the TA to the TE in the case of key pressings, display changes, and indicator state changes. <mode> controls the processing of unsolicited result codes specified within this command. <bfr> controls the effect on buffered codes when <mode> 1, 2, or 3 is entered. +CMER=[<mode>[,<keyp>[,<disp> [,<ind>[,<bfr>]]]]] <cr>
Syntax:
149
Chapter 3 AT Command Interface +CMER Possible Responses: Mobile Equipment Event Reporting <mode> = 0, 1, 2, or 3 0 = buffer unsolicited result codes in the TA; if the TA result code buffer is full, codes can be buffered in some other place or the oldest ones can be discarded. (DEFAULT) 1 = discard unsolicited result codes when the TA-TE link is reserved (e.g., in on-line Data Mode); otherwise, forward them directly to the TE. 2 = buffer unsolicited result codes in the TA when the TA-TE link is reserved (e.g., in on-line Data Mode) and flush them to the TE after reservation; otherwise forward them directly to the TE. 3 = forward unsolicited result codes directly to the TE; TA-TE link specific inband technique used to embed result codes and data when the TA is in on-line Data Mode. <keyp> = 0, 1, or 2 0 = no keypad event reporting. 1 = keypad event reporting using result code +CKEV: <key>,<press>. <key> indicates the key (see IRA values defined in table in subclause Keypad Control +CKPD) and <press> if the key is pressed or released (1 for pressing and 0 for releasing). Only those key pressings, which are not caused by +CKPD shall be indicated by the TA to the TE. When this mode is enabled, the corresponding result codes of all keys currently pressed should be flushed to the TA regardless of <bfr> setting. 2 = keypad event reporting using result code +CKEV: <key>,<press>. All key pressings are directed from TA to TE.
150
Chapter 3 AT Command Interface +CMER Mobile Equipment Event Reporting When this mode is enabled, the corresponding result codes of all keys currently pressed are flushed to the TA regardless of the <bfr> setting. <disp> = 0, 1, or 2 0 = no display event reporting. 1 = display event reporting using result code +CDEV: <elem>,<text>. <elem> indicates the element order number (as specified for +CDIS) and <text> is the new value of text element. Only those display events, which are not caused by +CDIS shall be indicated by the TA to the TE. Character set used in <text> is as specified by the command +CSCS. 2 = display event reporting using result code +CDEV: <elem>,<text>. All display events shall be directed from the TA to the TE. Character set used in <text> is as specified by the command +CSCS. <ind> = 0, 1, or 2 0 = no indicator event reporting. 1 = indicator event reporting using result code +CIEV: <ind>,<value>. <ind> indicates the indicator order number (as specified for +CIND) and <value> is the new value of indicator. Only those indicator events, which are not caused by +CIND shall be indicated by the TA to the TE. 2 = indicator event reporting using result code +CIEV: <ind>,<value>. All indicator events shall be directed from the TA to the TE. <bfr> = 0 or 1 0 = TA buffer of unsolicited result codes defined within this command is cleared when <mode> 1...3 is entered. 1 = TA buffer of unsolicited result codes
151
Chapter 3 AT Command Interface +CMER Mobile Equipment Event Reporting defined within this command is flushed to the TE when <mode> 1...3 is entered (OK response shall be given before flushing the codes). +CMER=0,1,2, 0 <cr> OK If a setting is not supported by the ME +CME ERROR: <err> See subclause 9.2 for <err> values. +CMER=? Description: Syntax: Parameters: Example: Possible Response: Return Supported Event Reporting Modes The +CMER=? command returns the modes supported by the TA as compound values. AT+CMER=? <cr> None AT+CMER=? <cr> +CMER: (list of supported <mode>s),(list of supported <keyp>s),(list of supported <disp>s),(list of supported <ind>s),(list of supported <bfr>s) Report Current Event Reporting Command The +CMER? command reports the current mobile equipment event reporting command in effect. AT+CMER? <cr> None AT+CMER? <cr>
+CMER? Description:
152
Chapter 3 AT Command Interface +CMER? Possible Response: Report Current Event Reporting Command +CMER:<mode>,<keyp>,<disp>,<ind>,<bfr> OK where <mode>,<keyp>,<disp>,<ind>,<bfr> are values shown under the +CMER=? command on page 149. Delete Message The +CMGD command deletes message from preferred message storage <mem1> location <index>. AT+CMGD=<index>[,<delflag>] <cr> <index> integer type; value in the range of location numbers supported by the associated memory. <delflag> = 0, 1, 2, 3, or 4 one of the following integers indicating multiple-message deletion requests: 0 = delete all messages specified in <index>. 1 = delete all read messages from preferred message storage, leaving unread messages and stored mobile originated messages (whether sent or not) untouched. 2 = delete all read messages from preferred message storage and sent mobile originated messages, leaving unread messages and unsent mobile originated messages untouched. 3 = delete all read messages from preferred message storage, sent and unsent mobile originated messages leaving unread messages untouched. 4 = delete all messages from preferred
+CMGD Description:
Syntax:
Parameters:
153
Chapter 3 AT Command Interface +CMGD Example: Possible Responses: Delete Message message storage, including unread messages. AT+CMGD=3 <cr> OK If error is related to ME functionality: +CMS ERROR <err> +CMGD=? Description: Syntax: Parameters: Example: Possible Response: List Valid Memory Locations The +CMGD=? command shows the valid memory locations AT+CMGD=? <cr> None AT+CMGD=? <cr> +CMGD: (list of supported <index>s)[,(list of supported <delflag>s)] OK Message Format The +CMGF command sets a parameter that specifies the input and output format of messages to be used. AT+CMGF =[<mode>] <cr> <mode> = 0 or 1 0 = PDU mode. 1 = text mode. (DEFAULT) AT+CMGF=0 <cr> AT+CMGF=1 <cr> OK
+CMGF Description:
Syntax: Parameters:
Examples: Possible
154
Chapter 3 AT Command Interface +CMGF Response: +CMGF=? Description: Syntax: Parameters: Example: Possible Response: +CMGF? Description: Syntax: Parameters: Example: Possible Response: +CMGL Description: Message Format
List Report Message Format Modes The +CMGF=? command lists supported report message format modes. AT+CMGF=? <cr> None AT+CMGF=? <cr> +CMGF: (list of supported <mode>s) OK Report Current Message Format Mode The +CMGF? command reports the current message format mode. AT+CMGF? <cr> None AT+CMGF? <cr> +CMGF: <mode> OK List SMS Messages from Preferred Store The +CMGL command returns messages with status value <stat> from message storage <mem1> to the TE. If status of the message is received unread, status in the storage changes to received read. If the selected <mem1> can contain different types of SMS (e.g., SMS-DELIVERs, SMSSUBMITs, SMS-STATUS-REPORTs and
155
Chapter 3 AT Command Interface +CMGL List SMS Messages from Preferred Store SMS-COMMANDs), the response may be a mix of the responses of different SM types. TE application can recognize the response format by examining the third response parameter. AT+CMGL[=<stat>] <cr> If text mode: <stat> REC UNREAD = received unread messages. (DEFAULT) REC READ = received read messages. STO UNSENT = stored unsent messages STO SENT = stored sent messages. ALL = all messages. If PDU mode: <stat> = 0, 1, 2, 3, or 4 0 = received unread messages. (DEFAULT) 1 = received read messages. 2 = stored unsent messages. 3 = stored sent messages. 4 = all messages. <alpha> string-type alphanumeric representation of <da> or <oa> corresponding to the entry found in MT phonebook; implementation of this feature is manufacturer-specific. <ct> GSM 03.40 TP-Command-Type in integer format (DEFAULT = 0) <da> GSM 03.40 TP-Destination-Address Address-Value field in string format; BCD numbers (or GSM default alphabet characters) are converted into characters; type of address given by <toda>.
Syntax: Parameters:
156
Chapter 3 AT Command Interface +CMGL List SMS Messages from Preferred Store <data> In the case of SMS: GSM 03.40 TP-UserData in text mode responses; format:
If <dcs> indicates that GSM 03.38 default alphabet is used and <fo> indicates that GSM 03.40 TP-User-DataHeader-Indication is not set: ME/TA converts GSM alphabet into current TE character set according to rules of Annex A. If <dcs> indicates that 8-bit or UCS2 data coding scheme is used, or <fo> indicates that GSM 03.40 TP-UserData-Header-Indication is set: ME/TA converts each 8-bit octet into hexadecimal numbers containing two IRA characters (e.g., octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65))
In the case of CBS: GSM 03.41 CBM Content of Message in text mode responses; format: <dt> GSM 03.40 TP-Discharge-Time in timestring format: yy/MM/dd,hh:mm:sszz, where characters indicate year (two last digits), month, day, hour, minutes, seconds, and time zone. For example, 6th of May 1994, 22:10:00 GMT+2 hours equals 94/05/ 06,22:10:00+08. <fo> depending on the command or result code: first octet of GSM 03.40 SMS-DELIVER, SMS-SUBMIT (DEFAULT is 17), SMSSTATUS-REPORT, or SMS-COMMAND (DEFAULT is 2) in integer format. <length>
157
Chapter 3 AT Command Interface +CMGL List SMS Messages from Preferred Store integer type value indicating in the text mode (+CMGF=1) the length of the message body <data> (or <cdata>) in characters; or in PDU mode (+CMGF=0), the length of the actual TP data unit in octets (i.e., the RP layer SMSC address octets are not counted in the length). <index> integer type; value in the range of location numbers supported by the associated memory. <mid> GSM 03.41 CBM Message Identifier in integer format <mr> GSM 03.40 TPMessage-Reference in integer format <oa> GSM 03.40 TP-Originating-Address Address-Value field in string format; BCD numbers (or GSM default alphabet characters) are converted into characters; type of address given by <tooa>. <pages> GSM 03.41 CBM Page Parameter bits 0-3 in integer format <pdu>. In the case of SMS: GSM 04.11 SC address followed by GSM 03.40 TPDU in hexadecimal format: ME/TA converts each octet of TP data unit into hexadecimal numbers containing two IRA characters (e.g., octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65)). In the case of CBS: GSM 03.41 TPDU in hexadecimal format. <page> GSM 03.41 CBM Page Parameter, bits 4-7 in integer format <ra>
158
Chapter 3 AT Command Interface +CMGL List SMS Messages from Preferred Store GSM 03.40 TP-Recipient-Address AddressValue field in string format; BCD numbers (or GSM default alphabet characters) are converted into characters; type of address given by <tora>. <scts> GSM 03.40 TP-Service-Center-Time-Stamp in time-string format (refer to <dt>) <sn> GSM 03.41 CBM Serial Number in integer format <st> GSM 03.40 TP-Status in integer format <toda> GSM 04.11 TP-DestinationAddress Type-of-Address octet in integer format (when first character of <da> is + (IRA 43) DEFAULT is 145; otherwise, DEFAULT is 129). <tooa> GSM 04.11 TP-Originating-Address Typeof-Address octet in integer format (DEFAULT refer to <toda>). <tora> GSM 04.11 TP-Recipient-Address Type-ofAddress octet in integer format (DEFAULT refer to <toda>). Examples: Possible Responses: AT+CMGL=RC READ <cr> AT+CMGL=STO SENT <cr> If text mode (+CMGF=1) and command is successful: for SMS-SUBMITs and/or SMSDELIVERs: +CMGL:<index>,<stat>, <i/da>, [],[<scts>][,<tooa/i>, length>]<cr><lf><data>[<cr> <lf> +CMGL: <index>,<stat>,<da/oa>, [<alpha>],[<scts>][,<tooa/toda>,
159
Chapter 3 AT Command Interface +CMGL List SMS Messages from Preferred Store <length>] <cr><lf><data> [...]] OK for SMS-STATUS-REPORTs: +CMGL: <index>,<stat>,<fo>,<mr>, [<ra>], [<tora>],<scts>,<dt>, <st> [<cr><lf>+CMGL:<index>,<stat>, <fo>,<mr>,[<ra>],[<tora>],<scts>,<dt>, <st>[...]] OK for SMS-COMMANDs: +CMGL: <index>,<stat>,<fo>,<ct> [<cr><lf> +CMGL: <index>,<stat>,<fo>,<ct>[...]] OK for CBM storage: +CMGL: <index>,<stat>,<sn>,<mid>,<page>, <pages><cr><lf><data>[<cr> <lf> +CMGL: <index>,<stat>,<sn>,<mid>,<page>, <pages><cr><lf><data>[...]] OK If PDU mode (+CMGF=0) and command is successful: +CMGL: <index>,<stat>,[<alpha>],<length> <cr><LF><pdu> [<cr><lf>+CMGL: <index>,<stat>, <length><cr><lf> <pdu>[...]] OK If error is related to ME functionality: +CMS ERROR: <err> +CMGL=? List Supported Messages
160
Chapter 3 AT Command Interface +CMGL=? Description: Syntax: Parameters: Example: Possible Response: List Supported Messages The +CMGL=? command lists the messages that are supported. AT+CMGL=? <cr> None AT+CMGL=? <cr> +CMGL: list of supported <stat>s OK
+CMGR Description:
Read SMS Message The +CMGR command returns SMS message with location value <index> from message storage <mem1> to the TE. If status of the message is received unread, status in the storage changes to received read. AT+CMGR=<index> <cr> <index> integer type; value in the range of location numbers supported by the associated memory <stat> = 0, 1, 2, 3, or 4 integer type in PDU mode (DEFAULT is 0), or string type in text mode (DEFAULT is REC UNREAD); indicates the status of message in memory; defined values: 0 = REC UNREAD received unread message (i.e., new message). (DEFAULT) 1 = REC READ received read message. 2 = STO UNSENT stored unsent message (only applicable to SMs). 3 = STO SENT stored sent message (only
Syntax: Parameters:
161
Chapter 3 AT Command Interface +CMGR Read SMS Message applicable to SMs). 4 = ALL all messages (only applicable to +CMGL List SMS messages from preferred store command). <alpha> string-type alphanumeric representation of <da> or <oa> corresponding to the entry found in MT phonebook; implementation of this feature is manufacturer-specific <ct> GSM 03.40 TP-Command-Type in integer format (DEFAULT is 0). <da> GSM 03.40 TP-Destination-Address Address-Value field in string format; BCD numbers (or GSM default alphabet characters) are converted into characters; type of address given by <toda>. <data> In the case of SMS: GSM 03.40 TP-UserData in text mode responses; format:
if <dcs> indicates that GSM 03.38 default alphabet is used and <fo> indicates that GSM 03.40 TP-User-DataHeader-Indication is not set: ME/TA converts GSM alphabet into current TE character set according to rules covered in Annex A. if <dcs> indicates that 8-bit or UCS2 data coding scheme is used, or <fo> indicates that GSM 03.40 TP-User-DataHeader-Indication is set: ME/TA converts each 8-bit octet into hexadecimal numbers containing two IRA characters (e.g., octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65))
162
Chapter 3 AT Command Interface +CMGR Read SMS Message In the case of CBS: GSM 03.41 CBM Content of Message in text mode responses; format:
if <dcs> indicates that GSM 03.38 default alphabet is used: ME/TA converts GSM alphabet into current TE character set according to rules covered in Annex A. if <dcs> indicates that 8-bit or UCS2 data coding scheme is used: ME/TA converts each 8-bit octet into hexadecimal numbers containing two IRA characters <dcs> depending on the command or result code: GSM 03.38 SMS Data Coding Scheme (default 0), or Cell Broadcast Data Coding Scheme in integer format.
<cdata> GSM 03.40 TP-Command-Data in text mode responses; ME/TA converts each 8-bit octet into two IRA character long hexadecimal number (e.g., octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65)) <dt> GSM 03.40 TP-Discharge-Time in timestring format: yy/MM/dd,hh:mm:sszz where characters indicate year (two last digits), month, day, hour, minutes, seconds, and time zone. For example, 6th of May 1994, 22:10:00 GMT+2 hours equals 94/05/06,22:10:00+08 <fo> depending on the command or result code: first octet of GSM 03.40 SMS-DELIVER, SMS-SUBMIT (DEFAULT is 17), SMS-
163
Chapter 3 AT Command Interface +CMGR Read SMS Message STATUS-REPORT, or SMS-COMMAND (DEFAULT is 2) in integer format. <length> integer type value indicating in text mode (+CMGF=1) the length of the message body <data> (or <cdata>) in characters; or in PDU mode (+CMGF=0), the length of the actual TP data unit in octets (i.e., the RP layer SMSC address octets are not counted in the length). <index> integer type; value in the range of location numbers supported by the associated memory. <mid> GSM 03.41 CBM Message Identifier in integer format. <mr> GSM 03.40 TP-Message-Reference in integer format. <oa> GSM 03.40 TP-Originating-Address Address-Value field in string format; BCD numbers (or GSM default alphabet characters) are converted into characters; type of address given by <tooa>. <page> GSM 03.41 CBM Page Parameter, bits 4-7 in integer format. <pages> GSM 03.41 CBM Page Parameter, bits 0-3 in integer format. <pdu> In the case of SMS: GSM 04.11 SC address
164
Chapter 3 AT Command Interface +CMGR Read SMS Message followed by GSM 03.40 TPDU in hexadecimal format: ME/TA converts each octet of TP data unit into hexadecimal numbers containing two IRA characters (e.g., octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65)). In the case of CBS: <ra> GSM 03.40 TPRecipient-Address Address-Value field in string format; BCD numbers (or GSM default alphabet characters) are converted into characters; type of address given by <tora>. <pid> GSM 03.40 TP-Protocol-Identifier in integer format (DEFAULT is 0). <ra> GSM 03.40 TP-Recipient-Address AddressValue field in string format; BCD numbers (or GSM default alphabet characters) are converted to characters of the currently selected TE character set (see the command +CSCS); type of address given by <tora>. <sca> GSM 04.11 RP SC address Address-Value field in string format; BCD numbers (or GSM default alphabet characters) are converted to characters of the currently selected TE character set (see the command +CSCS); type of address given by <tosca>. <scts> GSM 03.40 TP-Service-Center-Time-Stamp in time-string format (see <dt>). <sn>
165
Chapter 3 AT Command Interface +CMGR Read SMS Message GSM 03.41 CBM Serial Number in integer format <st> GSM 03.40 TP-Status in integer format. <toda> GSM 04.11 TP-Destination-Address Typeof-Address octet in integer format (when first character of <da> is + (IRA 43) DEFAULT is 145; otherwise, DEFAULT is 129) <tooa> GSM 04.11 TP-Originating-Address Typeof-Address octet in integer format (DEFAULT see <toda>). <tora> GSM 04.11 TP-Recipient-Address Type-ofAddress octet in integer format (DEFAULT refer<toda>). <tosca> GSM 04.11 RP SC address Type-of-Address octet in integer format (DEFAULT see <toda>). <vp> depending on SMS-SUBMIT <fo> setting: GSM 03.40 TP-Validity-Period either in integer format (DEFAULT 167) or in timestring format (see <dt>). Example: Possible Responses: AT+CMGR=1 <cr> If text mode (+CMGF=1) and command is successful: for SMS-DELIVER: +CMGR: <stat>,<oa>,[<alpha>],<scts>[,<tooa>, <fo>,<pid>,<dcs>,<sca>,<tosca>,
166
Chapter 3 AT Command Interface +CMGR Read SMS Message <length>]<cr><lf><data> OK for SMS-SUBMIT: +CMGR: <stat>,<da>,[<alpha>][,<toda>,<fo>, <pid>,<dcs>,[<vp>],<sca>,<tosca>, <length>]<cr><lf><data> OK for SMS-STATUS-REPORT: +CMGR: <stat>,<fo>,<mr>,[<ra>],[<tora>],<scts>, <dt>,<st> OK for SMS-COMMAND: +CMGR: <stat>,<fo>,<ct>,<pid>,[<mn>],[<da>], [<toda>],<length><cr><lf><cdata>] OK for CBM storage: +CMGR: <stat>,<sn>,<mid>,<dcs>,<page>, <pages><cr><lf><data> OK If PDU mode (+CMGF=0) and command is successful: +CMGR: <stat>,[<alpha>],<length><cr><lf> <pdu> OK If error is related to ME functionality: +CMS ERROR: <err> +CMGR=? Description: Read Message Test Command The +CMGR=? command is a test command.
167
Chapter 3 AT Command Interface +CMGR=? Syntax: Parameters: Example: Possible Response: +CMGS Description: Read Message Test Command AT+CMGR=? <cr> None AT+CMGR=? <cr> OK Send Message The +CMGS command transmits SMS message from a TE to the network (SMSSUBMIT). Message reference value <mr> is returned to the TE on successful message delivery. Value can be used to identify message upon unsolicited delivery status report result code. Use CTRL-Z at the end of input to send the message and return OK. Use ESC at the end of message input to abort message send operation. No message is sent although display returns OK. Sending e-mails via SMS: Some providers do not recognize @ symbol. Possible alternative ! for @. Syntax: If text mode (+CMGF=1):+CMGS=<da>[,<toda> ] <cr> text is entered <ctrl-Z/ESC> If PDU mode (+CMGF=0):+CMGS=<length> <cr> PDU is given <ctrl-Z/ESC>
168
Chapter 3 AT Command Interface +CMGS Parameters: Send Message ESC aborts message <da> GSM 03.40 TP-Destination-Address Address-Value field in string format and entered in double quotes; BCD numbers (or GSM default alphabet characters) are converted into characters; type of address given by <toda>. <toda> GSM 04.11 TP-Destination-Address Typeof-Address octet in integer format (when first character of <da> is + (IRA 43) DEFAULT is 145; otherwise, DEFAULT is 129). <length> integer type value indicating in the text mode (+CMGF=1) the length of the message body <data> (or <cdata>) in characters; or in PDU mode (+CMGF=0), the length of the actual TP data unit in octets (i.e., the RP layer SMSC address octets are not counted in the length). <mr> GSM 03.40 TP-Message-Reference in integer format. <scts> GSM 03.40 TP-Service-Center-Time-Stamp in time-string format (see <dt>). <dt> GSM 03.40 TP-Discharge-Time in timestring format: yy/MM/dd,hh:mm:sszz, where characters indicate year (two last digits), month, day, hour, minutes, seconds, and time zone. For example, 6th of May 1994, 22:10:00 GMT+2 hours equals 94/05/06,22:10:00+08.
169
Chapter 3 AT Command Interface +CMGS Send Message <ackpdu> GSM 03.40 RP-User-Data element of RPACK PDU; format is same as for <pdu> in case of SMS, but without GSM 04.11 SC address field and parameter shall be enclosed in double quote characters like a normal string type parameter. <pdu> In the case of SMS: GSM 04.11 SC address followed by GSM 03.40 TPDU in hexadecimal format: ME/TA converts each octet of TP data unit into hexadecimal numbers containing two IRA characters (e.g., octet with integer value 42 is presented TE as two characters 2A (IRA 50 and 65)). In the case of CBS: GSM 03.41 TPDU in hexadecimal format. Example: Possible Responses: AT+CMGS=+3314629800 <cr> If text mode (+CMGF=1) and sending is successful: +CMGS: <mr>[,scts>] OK If PDU mode (+CMGF=0) and sending is successful: +CMGS: <mr>[,ackpdu>] OK If error is related to ME functionality: +CMS ERROR: <err> +CMGS=? Description: Syntax: Send Message Test Command The +CMGS=? command is a test command. AT+CMGS=? <cr>
170
Chapter 3 AT Command Interface +CMGS=? Parameters: Example: Possible Responses: +CMGW Description: Send Message Test Command None AT+CMGS=? <cr> OK
Write Message The +CMGW command transmits SMS message (either SMS-DELIVER or SMSSUBMIT) from TE to memory storage <mem2>. Memory location <index> of the stored message is returned. Message status will be set to stored unsent unless otherwise given in <stat>. SMS-COMMANDs and SMS-STATUSREPORTs can not be stored in text mode.
Syntax:
If text mode: (+CMGF=1):+CMGW[=<oa/da>[,<tooa/tod a>,stat>]]] <cr> text is entered <ctrl-Z/ESC> <ESC> quits without sending If PDU mode: (+CMGF=0):+CMGW=<length>[,stat] <cr> PDU is given <ctrl-Z/ESC>
Parameters:
<oa> GSM 03.40 TP-Originating-Address AddressValue field in string format; BCD numbers (or GSM default alphabet characters) are converted into characters; type of address given by <tooa>.
171
Chapter 3 AT Command Interface +CMGW Write Message <da> GSM 03.40 TP-Destination-Address AddressValue field in string format; BCD numbers (or GSM default alphabet characters) are converted into characters; type of address given by <toda>. <tooa> GSM 04.11 TP-Originating-Address Type-ofAddress octet in integer format (DEFAULT see <toda>). <toda> GSM 04.11 TP-Destination-Address Type-ofAddress octet in integer format (when first character of <da> is + (IRA 43) DEFAULT is 145; otherwise, DEFAULT is 129). <length> integer-type value indicating in the text mode (+CMGF=1) the length of the message body <data> (or <cdata>) in characters; or in PDU mode (+CMGF=0), the length of the actual TP data unit in octets (i.e. the RP layer SMSC address octets are not counted in the length) <stat> = 0, 1, 2, 3, or 4 0 = REC UNREAD received unread messages. (DEFAULT) 1 = REC READ received read messages. 2 = STO UNSENT stored unsent messages. 3 = STO SENT stored sent messages. 4 = ALL all messages. <pdu> In the case of SMS: GSM 04.11 SC address followed by GSM 03.40 TPDU in hexadecimal format: ME/TA converts each octet of TP data unit into hexadecimal numbers containing two IRA characters (e.g., octet with integer value 42 is presented to TE as two characters 2A
172
Chapter 3 AT Command Interface +CMGW Write Message (IRA 50 and 65)). In the case of CBS: GSM 03.41 TPDU in hexadecimal format. <index> Index of message in selected storage <mem2>. Example: Possible Responses: AT+CMGW=+33146290800 <cr> If writing is successful: +CMGW: <index> OK If error is related to ME functionality: +CMS ERROR: <err> CTRL-Z sends/writes message, returns OK. ESC aborts input, message NOT sent/written. Returns OK Sending e-mails via SMS: Some providers do not recognize @ symbol. Possible alternative"!" for "@". +CMGW=? Description: Syntax: Parameters: Example: Possible Responses: +CMOD Description: Write Message Test Command The +CMGW=? command is a test command. AT+CMGW=? <cr> None AT+CMGW=? <cr> OK Select Call Mode The +CMOD command selects the call mode used with subsequent dialing commands (D). The mode can be either single or alternating.
173
Chapter 3 AT Command Interface +CMOD Select Call Mode If single mode is selected, the call origination and hang-up procedures are similar to those specified in proposed ITU-T Recommendations V.25ter, T.class1 and T.class2. Semicolon dial modifier shall be used to start a voice call when +FCLASS=0. In GSM there can be alternating voice/ data and voice/ fax calls (see GSM 02.03). AT+CMOD=<mode> <cr> <mode> = 0, 1, 2 or 3 0 = single mode. (DEFAULT) 1 = alternating voice/fax (teleservice 61). 2 = alternating voice/data (bearer service 61). 3 = voice followed by data (bearer service 81). AT+CMOD=0 AT+CMOD=1 AT+CMOD=2 AT+CMOD=3 OK <cr> <cr> <cr> <cr>
Syntax: Parameters:
Examples:
Possible Response: +CMOD=? Description:
List Supported Call Modes The +CMOD=? command lists the call modes that the GSM Data Modules supports. AT+CMOD=? <cr> None AT+CMOD=? <cr> +CMOD: <list of supported call modes> OK
174
Chapter 3 AT Command Interface +CMOD? Description: Syntax: Parameters: Example: Possible Responses: Report Current Call Mode The +CMOD? command reports the GSM Data Modules current call mode. AT+CMOD? <cr> None AT+CMOD? <cr> +CMOD: <list of supported call modes> OK
+CMS ERROR Description:
Error Response The +CMS ERROR final result code indicates an error related to mobile equipment or network. The operation is similar to ERROR result code. None of the following commands in the same command line is executed. Neither ERROR nor OK result code shall be returned. ERROR is returned normally when error is related to syntax or invalid parameters. <err> values used by common messaging commands: 0...127 GSM 04.11 Annex E-2 values 128...255 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
Defined Values:
175
Chapter 3 AT Command Interface +CMS ERROR Error Response 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 ...511 other values in range 256...511 are reserved 512... manufacturer specific
+CMSS Description:
Send Message from Storage The +CMS command sends message with location value <index> from message storage <mem2> to the network (SMS-SUBMIT or SMS-COMMAND). If new recipient address <da> is given for SMS-SUBMIT, it shall be used instead of the one stored with the message. Reference value <mr> is returned to the TE on successful message delivery. Values can be used to identify message upon unsolicited delivery status report result code. This command should be abortable. +CMSS=<index>[,<da>[,<toda>]] <cr> <index> integer type; value in the range of location numbers supported by the associated memory. <da> GSM 03.40 TP-Destination-Address AddressValue field in string format; BCD numbers (or
Syntax: Parameters:
176
Chapter 3 AT Command Interface +CMSS Send Message from Storage GSM default alphabet characters) are converted into characters; type of address given by <toda>. <toda> GSM 04.11 TP-Destination-Address Type-ofAddress octet in integer format (when first character of <da> is + (IRA 43) DEFAULT is 145; otherwise, DEFAULT is 129). Example: Possible Response: AT+CMSS=5, 0680654321 <cr> If text mode (+CMGF=1) and send is successful: +CMSS: <mr>[,scts>] OK where: <mr> is GSM 03.40 TP-Message-Reference in integer format. <scts> is GSM 03.40 TP-Service-Center-Time Stamp in time-string format. If PDU mode (+CMGF=0) and send is successful: +CMSS: <mr>[,ackpdu>] OK where <ackpdu> is GSM 03.40 RP-User-Data element of RP-ACK PDU; format is same as for <pdu> in case of SMS, but without GSM 04.11 SC address field and parameter shall be bounded by double-quote characters like a normal string-type parameter. If error is related to ME functionality: +CMS ERROR: <err> +CMSS=? Description: Send SMS Message from Storage Test Command The +CMSS=? command is a test command.
177
Chapter 3 AT Command Interface +CMSS=? Syntax: Parameters: Example: Possible Responses: Send SMS Message from Storage Test Command AT+CMSS=? <cr> None AT+CMSS=? <cr> OK
+CMTI: Description:
Query New Message Received The +CMTI: command indicates when a new message has been received from the network and stored successfully to storage <mem>. AT+CMTI:<mem>,<index> <mem> = ME or SM ME = ME message storage. SM = SIM message storage. <index> integer with a value in the range of location numbers supported by the associated memory.
Syntax: Parameters:
Unsolicited Result: Possible Response:
AT+CNMI:SM,3 AT+CMTI:<mem>,<index> OK
+CMUT Description: Syntax:
Mute Control The +CMUT command enables or disables the uplink voice muting during a voice call. AT+CMUT=<n> <cr>
178
Chapter 3 AT Command Interface +CMUT Parameters: Mute Control <n> = 0 or 1 0 = mute off. (DEFAULT) 1 = mute on. AT+CMUT=0 <cr> AT+CMUT=1 <cr> OK +CME ERROR: <err> See subclause 9.2 for <err> values. +CMUT=? Description: List Supported Mute Controls Setting The +CMUT=? command lists, as compound values, the mute control settings that the GSM Data Module supports. AT+CMUT=? <cr> None AT+CMUT=? <cr> +CMUT: (list of supported <n>s) +CME ERROR: <err> See subclause 9.2 for <err> values. +CMUT? Description: Syntax: Parameters: Example: Report Current Mute Control Setting The +CMUT? command reports the current mute control setting. AT+CMUT? <cr> None AT+CMUT? <cr>
179
Chapter 3 AT Command Interface +CMUT? Possible Responses: Report Current Mute Control Setting +CMUT: <n> OK +CME ERROR: <err> See subclause 9.2 for <err> values. +CNMI Description: New SMS Message Indication The +CNMI command determines how the receipt of new SMS messages from the network is indicated to the TE when TE is active (e.g., DTR signal is ON). If TE is inactive (e.g., DTR signal is OFF), message receiving should be done as specified in GSM 03.38. The rules <mt>=2 and <mt>=3 for storing received SM are possible only if phase 2+ compatibility is activated with +CSMS=1. Syntax: Parameters: AT+CNMI =[<mode>[,<mt> [,<bm>[,<ds>[,<bfr>]]]]] <cr> <mode> = 0, 1, 2, or 3 0 = buffer unsolicited result codes in the TA. If TA result code buffer is full, indications can be buffered in some other place or the oldest indications may be discarded and replaced with the new received indications. (DEFAULT) 1 = discard indication and reject new received message unsolicited result codes when TA-TE link is reserved (e.g., in on-line Data Mode). Otherwise, forward them directly to the TE. 2 = buffer unsolicited result codes in the TA when TA-TE link is reserved (e.g., in on-line Data Mode) and flush them to the TE after reservation. Otherwise, forward them directly to the TE. 3 = forward unsolicited result codes directly
180
Chapter 3 AT Command Interface +CNMI New SMS Message Indication to the TE. TA-TE link specific inband technique used to embed result codes and data when TA is in on-line Data Mode. <mt> = 0, 1, or 2 the rules for storing received SMs depend on the relevant data coding method (refer to GSM 03.38 [2]), preferred memory storage (+CPMS) setting and this value. If the AT command interface is acting as the only display device, the ME must support storage of class 0 messages and messages in the message waiting indication group (discard message) 0 = no SMS-DELIVER indications are routed to the TE. (DEFAULT) 1 = if SMS-DELIVER is stored in ME/TA, indication of the memory location is routed to the TE using unsolicited result code: +CMTI: <mem>,<index>. 2 = SMS-DELIVERs (except class 2 messages and messages in the message waiting indication group (store message) are routed directly to the TE using unsolicited result code: +CMT: [<alpha>],<length><cd><lf> <pdu> (PDU mode enabled) <bm> = 0, 1, 2, or 3 the rules for storing received CBMs depend on the relevant data coding method (refer to GSM 03.38 [2]), the setting of Select CBM Types (+CSCB) and this value: 0 = no CBM indications are routed to the TE. (DEFAULT) 1 = if CBM is stored in ME/TA, indication of the memory location is routed to the TE using unsolicited result code: +CBMI: <mem>,<index>
181
Chapter 3 AT Command Interface +CNMI New SMS Message Indication 2 = new CBMs are routed directly to the TE using unsolicited result code: +CBM:<length><cr><lf><pdu> (PDU mode enabled) or +CBM:<sn>,<mid>, <dcs>,<page>,<pages><cr> <lf><data> (text mode enabled) If ME supports data coding groups that define special routing also for messages other than class 3 (e.g., SIMspecific messages), ME may choose not to route messages of such data coding schemes into TE (indication of a stored CBM may be given as defined in <bm>=1). 3 = Class 3 CBMs are routed directly to TE using unsolicited result codes defined in <bm>=2. If CBM storage is supported, messages of other classes result in indication as defined by <bm>=1. 2 SMS-DELIVERs routed directly to TE are NOT supported. <ds> = 0 or 1 0 = no SMS-STATUS-REPORTs are routed to the TE. 1 = SMS=STATUS REPORTs are routed to the TE using unsolicited result code +CDS: <length><cr><lf><pdu> (PDU mode enabled). OR +CDS: <fo>,<mr>,[<ra>,[tora],<scts>, <dt>,<st>(text mode enabled). <bfr> = 0 or 1 0 = TA buffer of unsolicited result codes defined within this command is flushed to the TE when <mode> 1...3 is entered (OK response is given before flushing the codes). 1 = TA buffer of unsolicited result codes
182
Chapter 3 AT Command Interface +CNMI New SMS Message Indication defined within this command is cleared when <mode> 1...3 is entered. Unsolicited result code: +CMTI: <mem>,<index> Indication that new message has been received +CMT: <length><cr><lf><pdu> Short message is output directly +CBM: <length><cr><lf><pdu> Cell broadcast message is output directly Parameters can only be set to provider supported values. Example: Possible Response: AT+CNMI=2,1,0,0,0 <cr> OK If error is related to ME functionality: +CMS ERROR: <err> List Supported Message Indications The +CNMI=? command lists supported message indications. AT+CNMI=? <cr> None AT+CNMI=? <cr> +CNMI: (list of supported <mode>s), (list of supported <mt>s), (list of supported <bm>s), (list of supported <ds>s), (list of supported <bfr>s) OK Report Current Message Indication
+CNMI=? Description: Syntax: Parameters: Example: Possible Response:
+CNMI?
183
Chapter 3 AT Command Interface +CNMI? Description: Syntax: Parameters: Example: Possible Response: Report Current Message Indication The +CNMI? command reports the current message indication. AT+CNMI? <cr> None AT+CNMI? <cr> +CNMI: <mode>,<mt>,<bm>,<ds>,<bfr> OK For an explanation of these parameters, see the +CNMI command on page 180.
+CNUM Description:
Subscriber Number The +CNUM command returns the MSISDN(s) related to the subscriber. This information can be stored in the SIM or in the ME. If subscriber has different MSISDN for different services, each MSISDN is returned in a separate line. AT+CNUM <cr> None AT+CNUM <cr> +CNUM: <alpha1>,<number1>,<type1>, <speed>,<service>,<itc> <cr><lf> +CNUM: <alpha2>,<number2>,<type2>, <speed>,<service>,<itc> <cr><lf> OK where <alphax> = optional alphanumeric string associated with <numberx>.
184
Chapter 3 AT Command Interface +CNUM Subscriber Number <numberx> = string-type phone number of format specified by <typex>. <speed> = as defined in subclause 6.7 (GSM7.07 version 7.5.0). <typex> = type of address octet, in integer format. <service> = service related to the phone number 0, 1, 4, or 5 0= asynchronous modem. 1 = synchronous modem. 4 = voice. 5 = fax. <itc> = information transfer capability 0 or 1 0 = 3.1 kHz. 1 = UDI. +CNUM=? Description: Syntax: Parameters: Example: Possible Response: List Supported Subscriber Numbers The +CNUM=? command lists the supported subscriber numbers. AT+CNUM=? <cr> None AT+CNUM=? <cr> +CNUM: (list of supported subscriber numbers) OK Connected Line ID Presentation The +COLP command enables or disables the presentation of the COL (connected line) at the TE at a mobile originating call. It has
+COLP Description:
185
Chapter 3 AT Command Interface +COLP Connected Line ID Presentation no effect on the execution of the supplementary service COLR in the network. Intermediate result code is returned from TA to TE before any +CR or V.25ter [5] responses. It is manufacturer-specific if this response is used when normal voice call is set up. AT+COLP=[<n>] <cr>
Syntax: Parameters:
<n> sets/shows the result code presentation status in the TA) 0 or 1: 0 = disable. 1 = enable. <m> (parameter shows the subscriber COLP service status in the network) 0, 1, or 2: 0 = COLP not provisioned. 1 = COLP provisioned. 2 = unknown (e.g., no network).
Example: Possible Response: +COLP=? Description: Syntax: Parameters: Example: Possible Responses:
AT+COLP=1 <cr> OK
List Supported Line ID Presentations The +COLP =? command lists the supported line ID presentations. AT+COLP=? <cr> None AT+COLP=? <cr> +COLP: (list of supported <n>s) OK
186
Chapter 3 AT Command Interface +COLP? Description: Report Current Line ID Presentation The +COLP? command shows the current line ID presentation supported by the GSM Data Module. AT+COLP? <cr> None AT+COLP? <cr> +COLP: <n>,<m> OK
+COPN Description: Syntax: Parameters: Example: Possible Responses:
Read Operator Names The +COPN command reads operator names. AT+COPN <cr> None AT+COPN <cr> +COPN:<numoper>,<alphaoper><cr><lf> +COPN:..... OK where <numoper> is the network operator in numeric notation and <alphaoper> is the network operator in alphanumeric notation. Otherwise, +CME: ERROR
+COPN=? Description:
Read Operator Names Test Command The +COPN=? command is a test command for read operator names.
187
Chapter 3 AT Command Interface +COPN=? Syntax: Parameters: Example: Possible Response: +COPS Description: Read Operator Names Test Command AT+COPN=? <cr> None AT+COPN=? <cr> OK
Network Operator Selection The +COPS command forces an attempt to select and register the GSM network operator. If the selected operator is not available, no other operator is selected (except <mode>=4). The selected operator name format applies to further read commands (+COPS?). Parameters used with the set command are stored in the non-volatile memory (e.g., using AT+COPS=2 to book out of the net, causes the system to not automatically book in after the next power-on). AT+COPS=0/1 is needed to register into the network.
Syntax: Parameters:
AT+COPS=<mode>[,<format> [,<oper>]] <cr> <mode> = 0, 1, 3, or 4 0 = automatic (<oper> field is ignored). (DEFAULT) 1 = manual (<oper> field shall be present). 3 = set only <format> for read command +COPS?. Do not attempt registration/ deregistration (<oper> field is ignored); this value is not applicable in read command response. 4 = manual/automatic (<oper> field shall be present); if manual selection fails, automatic mode (<mode>=0) is entered.
188
Chapter 3 AT Command Interface +COPS Network Operator Selection <format> = 0, 1, or 2 0 = long format alphanumeric <oper>. (DEFAULT) 1 = short format alphanumeric <oper>. 2 = numeric <oper>. <oper> operator in format as per <format>. Example: Possible Responses: AT+COPS==1,2,20810 <cr> OK If error is related to ME functionality: +CME ERROR: <err> +COPS=? Description: List Network Operators The +COPS=? command returns a list of quadruplets, each representing an operator present in the network. Any of the formats may be unavailable and should then be an empty field. The list of operators must be in the following order: home network, networks referenced in SIM, and other networks. AT+COPS=? <cr> None AT+COPS=? <cr> +COPS: [<stat>, long alphanumeric <oper>, numeric <oper>)s] [,(list of supported <mode>s), (list of supported <format>s)] OK If error is related to ME functionality: +CME ERROR: <err>
189
Chapter 3 AT Command Interface +COPS? Description: Report Current Network Operator The +COPS? command returns the current mode and the currently selected operator. If no operator is selected, <format> and <oper> are omitted. AT+COPS? <cr> None AT+COPS? <cr> +COPS: <mode>[, <format>, <oper>] OK Mobile Activity Equipment Status The +CPAS command returns the activity status of the ME. AT+CPAS <cr> None AT+CPAS <cr> +CPAS: <pas> OK where <pas> is: 0 = ready. 2 = unknown (ME is not guaranteed to respond to instructions). 3 = incoming call (ringing). 4 = call in progress or call hold. Phone Activity Test Command The +CPAS=? command is a test command.
Syntax: Parameters: Example: Possible Responses: +CPAS Description: Syntax: Parameters: Example: Possible Response:
+CPAS=? Description:
190
Chapter 3 AT Command Interface +CPAS=? Syntax: Parameters: Example: Possible Responses: +CPBD Description: Syntax: Parameters: Phone Activity Test Command AT+CPAS=? None AT+CPAS=? +CPAS: (list of supported <pas>s) OK Delete Phonebook Entry The +CPBD command deletes an entry from the phonebook. AT+CPBD=<index1>[,<index2>] <cr> <index1> = an integer from 1 to 250 that corresponds to the phonebook entry to be deleted. <index2> = specifies the ending range of phonebook entries to be deleted (in which case <index1> specifies the starting range). Examples: AT+CPBD=12 <cr> deletes entry 12 in the phonebook. AT+CPBD 1,250 <cr> deletes all 251 entries in the phonebook. Possible Response: +CPBF Description: OK
Find Phonebook Entry The +CPBF command returns phonebook entries (from the current phonebook memory storage selected with the command +CPBS (see page 195)) whose alphanumeric fields contain <findtext>.
191
Chapter 3 AT Command Interface +CPBF Syntax: Parameters: Find Phonebook Entry AT+CPBF=<findtext> <cr> <findtext> = string type field of maximum length <tlength>; character set as specified by the command +CSCS. AT+CPBF=E <cr> [+CPBF:<index1>,<number>,<type>,<text>[[...] <cr><lf>+CBPF:<index2>,<number>,<type>, <text>] OK where <index1>, <index2> = integer type values in the range of location numbers of phonebook memory <number> = string type phone number of format <type> = type of address octet in integer format (see GSM 04.08 [8], subclause 10.5.4.7) If error is related to ME functionality: +CME ERROR: <err> +CPBF=? Description: Find Phonebook Entry Test Command The +CPBF=? command returns the maximum lengths of <number> and <text> fields. In case of SIM storage, the lengths may not be available. AT+CPBF=? <cr> None AT+CPBF=? <cr> +CPBF: [<nlength>], [<tlength>] OK where: <nlength> = integer type value indicating the maximum length of field <number>.
192
Chapter 3 AT Command Interface +CPBF=? Find Phonebook Entry Test Command <tlength> = integer type value indicating the maximum length of field <text>. If ME is not currently reachable: +CME ERROR: <err> See subclause 9.2 for <err> values. In case of SIM storage, the lengths may not be available. If storage does not offer format information, the format list should be empty parenthesis. +CPBF="" Description: List All Phonebook Entries in Phonebook The +CPBF="" command lists all phonebook entries in currently active phonebook (+CPBS). AT+CPBF="" <cr> None AT+CPBF="" <cr> Lists all phonebook entries in currently active phonebook (+CPBS).
+CPBR Description:
Read Phonebook The +CPBR command returns phonebook entries in location number range <index1>... <index2> from the current phonebook memory storage selected with +CPBS. If <index2> is left out, only location <index1> is returned. AT+CPBR=<index1>[, <index2>] <cr> <index> = location number.
Syntax: Parameters:
193
Chapter 3 AT Command Interface +CPBR Read Phonebook <index1> = read from this location number. <index2> = read to this location number. Example: Possible Responses: AT+CPBR=12,14 <cr> +CPBR: <index1>, <number>, <type>, <text>[<cr><lf>+CPBR:...+CPBR: <index2>, <number>, <type>, <text>] OK where <index2> = location where number is read. <number> = phone number. <type> = type of number. <text> = text for phone number If error is related to ME functionality: +CME ERROR: <err> +CPBR=? Description: Return Location Ranges The +CPBR=? command returns location range supported by the current storage as a compound value and the maximum lengths of <number> and <text> fields. In case of SIM storage, the lengths may not be available. If storage does not offer format information, the format list should be empty parenthesis. AT+CPBR=? <cr> None AT+CPBR=? <cr> +CPBR: (list of supported <index>s), <nlength>, <tlength> OK where
194
Chapter 3 AT Command Interface +CPBR=? Return Location Ranges <index> = location number. <nlength> maximum length of phone number. <tlength> = maximum length of text for number. If error is related to ME functionality: +CME ERROR: <err>
+CPBS Description:
Phonebook Memory Storage The +CPBS command selects the current phonebook memory storage which is used by other phonebook commands. AT+CPBS=<storage> <cr> <storage> = FD, LD, MC, ME, MT, ON, RC, or SM, entered in double quotes FD = SIM fix-dialing-phonebook. Fixed dialing numbers stored in the SIM may contain wildcard characters (B or b) and a sub-address. Examples: AT+CPBW=1,1234b6,,, for b any number from 0 to 9 can be used. AT+CPBW=2,011707,,, any number starting with 011707 is accepted. LD = SIM last-dialing-phonebook. (The lastdialed number cannot be written into the last memory-storage position.) MC = ME missed (unanswered received) call list (+CPBW can only be used for deleting) ME = ME Phonebook storage, positions 1-5. MT = combined ME and SIM Phonebook ON = SIM (or ME) own numbers (MSISDNs) list. RC = ME received calls list (+CPBW can only be used for deleting).
Syntax: Parameters:
195
Chapter 3 AT Command Interface +CPBS Phonebook Memory Storage SM = SIM phonebook. LD - Last dialing phonebook: Number will automatically be written onto the last position. (+CPBW can be used for deleting only). Example: Possible Response: +CPBS=? Description: Syntax: Parameters: Example: Possible Responses: +CPBS? Description: AT+CPBS=SM <cr> OK
List Supported Storages The +CPBS=? command returns supported storages as compound value. AT+CPBS=? <cr> None AT+CPBS=? <cr> +CPBS: (list of supported <storage>s) OK Report Current Storage The +CPBS? command returns the currently selected memory and when supported by manufacturer, number of used locations and total number of locations in the memory. AT+CPBS? <cr> None AT+CPBS? <cr> +CPBS: <storage> OK
196
Chapter 3 AT Command Interface +CPBW Description: Write Phonebook Entry The +CPBW command writes a phonebook entry in location number <index> in the current phonebook memory storage selected with +CPBS (see page 195). Entry fields written are phone number <number> (in the format <type>) and text <text> associated with the number. If these fields are omitted, phonebook entry is deleted. If <index> is omitted, but <number> is given, the entry is written to the first free location in the phonebook (see note for MT phonebook). The string <number> may also contain letters, these are stored as capitals. PIN2 is necessary for writing in FD phonebook. Syntax: Parameters: AT+CPBW=[<index>],[<number>, [<type>, [<text>]]] <cr> <nlength> maximum length of phone number. <tlength> maximum length of text for number. <index> location number. <number> phone number. <type> type of number; e.g., 145 when dialing string includes international access code character +; otherwise, 129. <text> text for phone number.
197
Chapter 3 AT Command Interface +CPBW Write Phonebook Entry The following characters in <text> must be entered via the escape sequence: GSM char. Seq. Seq.(hex) Note \ \5C 5C 35 43 (backslash) " \22 5C 32 32 (string delimiter) BSP \08 5C 30 38 (backspace) NULL \00 5C 30 30 (GSM null) 0 (GSM null) may cause problems on application level when using the function (strlen) and, therefore, should be represented by an escape sequence when necessary. Example: Possible Responses: AT+CPBW=2,1111,145 <cr> OK If error is related to ME functionality: +CME ERROR: <err> +CPBW=? Description: Return Location Ranges The +CPBW=? command returns location range supported by the current storage, the maximum length of <number> field, supported number formats of the storage, and the maximum length of <text> field. The lengths may not be available in case of SIM storage. If storage does not offer format information, the format list should be empty parenthesis. Syntax: AT+CPBW=? <cr>
198
Chapter 3 AT Command Interface +CPBW=? Parameters: Example: Possible Responses: Return Location Ranges None AT+CPBW=? <cr> +CPBW: (list of supported <index>s), <nlength>, (list of supported <typ>s), <tlength> OK where <index> = integer type values in the range of location numbers of phonebook memory. <typ> = type of address octet. <nlength> = integer type value indicating the maximum length of field number. <tlength> = integer type value indicating the maximum length of field <text> If error is related to ME functionality: +CME ERROR: <err> +CPIN Description: Enter PIN The +CPIN command stores a password that is necessary before it can be operated (SIM PIN, SIM PUK, PH-SIM PIN, etc.). If the PIN is to be entered twice, the TA automatically repeats the PIN. If no PIN request is pending, no action is taken and the error message +CME ERROR is returned to TE. If the PIN required is SIM PUK or SIM PUK2, the second pin is required. This second pin, <newpin>, is used to replace the old pin in the SIM. AT+CPIN=<pin> [,<new pin>] <cr> <pin> password (string type) should be entered in double quotes (e.g., AT+CPIN=9515) <new pin>
Syntax: Parameters:
199
Chapter 3 AT Command Interface +CPIN Enter PIN if the PIN required is SIM PUK or SIM PUK2: new password AT+CPIN=12345678 <cr> OK If error is related to ME functionality: +CME ERROR: <err> +CPIN=? Description: Syntax: Parameters: Example: Possible Response: +CPIN? Description: Enter PIN Test Command The +CPIN=? command is a test command. AT+CPIN=? <cr> None AT+CPIN=? <cr> OK Report Whether Password is Required The +CPIN? command returns an alphanumeric string indicating whether a password is required. AT+CPIN? <cr> None AT+CPIN? <cr> +CPIN: <code> OK If error is related to ME functionality: +CME ERROR: <err>
200
Chapter 3 AT Command Interface +CPMS Description: Set Preferred Message Store The +CPMS command selects memory storages <mem1>, <mem2>, and <mem3> to be used for reading and writing. AT+CPMS=<mem1>[,<mem2>[,<mem3>]] <cr> <mem1> Messages to be read and deleted from this memory storage. SM = SIM message storage. BM = broadcast message storage. <mem2> Messages will be written and sent to this memory storage. SM = SIM message storage. <mem3> received messages will be placed in this memory storage if routing to PC is not set (+CNMI). SM = SIM message storage. <usedx> number of messages currently in <memx>. <totalx> number of messages storable in <memx>. Example: Possible Responses: AT+CPMS=BM or SM,SM,SM <cr> +CPMS:<used1>,<total1>,<used2>,<total2>, <used3>,<total3> OK If error is related to ME functionality: +CMS ERROR:<err>
Syntax: Parameters:
201
Chapter 3 AT Command Interface +CPMS=? Description: Syntax: Parameters: Example: Possible Responses: List Supported Message Stores The +CPMS=? command shows the supported message stores. AT+CPMS=? <cr> None AT+CPMS=? <cr> +CPMS: (list of supported <mem1>s),(list of supported <mem2>s),(list of supported <mem3>s) OK Report Current Message Store The +CPMS? command reports the current message store. AT+CPMS? <cr> None AT+CPMS? <cr> +CPMS:<mem1>,<used1>,<total1>, <mem2>,<used2>,<total2>, <mem3>,<used3>,<total3> OK If error is related to ME functionality: +CMS ERROR +CPOL Description: Syntax: Preferred Operator List The +CPOL command is used to edit the SIM preferred list of networks. AT+CPOL=[<index>],[,<format> [,<oper>]] <cr>
+CPMS? Description: Syntax: Parameters: Example: Possible Responses:
202
Chapter 3 AT Command Interface +CPOL Parameters: Preferred Operator List <indexn> integer type; (0-19). <format> 2 =- numeric <oper>. <opern> string type, entered in double quotes. AT+CPOL=<index> deletes an entry. AT+CPOL= ,<format> sets the format used by the read command (AT+CPOL?). AT+CPOL=, <format>, <oper> puts <oper> in the next free location. AT+CPOL=<index>, <format>, <oper> writes <oper> in the <format> at the <index>. The supported format are the numeric (value 2) and the long format alphanumeric (value 0). The default format for the read command is the numeric one (value 2). The length of this list is limited to 8 entries . Examples: AT+CPOL=6,2,20810 <cr> (preferred list of networks in numeric format; numeric <opern> should be entered in double quotes) OK
Possible Response: +CPOL? Description:
Current Report Preferred List of Networks The +CPOL? command reports the preferred list of networks.
203
Chapter 3 AT Command Interface +CPOL? Syntax: Parameters: Example: Possible Responses: Current Report Preferred List of Networks AT+CPOL? <cr> None AT+CPOL? <cr> +CPCL: 0,2,73010 +CPCL: 1,2,22802 +CPCL: 2,2,25001 OK List of Supported Preferred Operators The +CPOL=? command shows the list of supported preferred operators. AT+CPOL=? <cr> None AT+CPOL=? <cr> +CPOL: (list of supported <oper>s),(list of supported <oper2>s),(list of supported <oper>s) OK Set Price Per Unit and Currency Control The +CPUC command sets the parameters of Advice of Charge related price per unit and currency table in SIM file EFPUCT. PUCT information can be used to convert the home units (as used in +CAOC, +CACM, and +CAMM) into currency units. SIM PIN2 is usually required to set the parameters. If setting fails in an ME error, +CME ERROR: <err> is returned. Refer subclause 9.2 for <err> values.
+CPOL=? Description: Syntax: Parameters: Example: Possible Response:
+CPUC Description:
204
Chapter 3 AT Command Interface +CPUC Syntax: Parameters: Set Price Per Unit and Currency Control AT+CPUC=<currency>,<ppu>[,<pass wd>] <cr> <currency> string type; three-character currency code (e.g., GBP, DEM); character set as specified by the command +CSCS (see page 223). <ppu> string type; price per unit; dot is used as a decimal separator (e.g. "2.66"). <passwd> string type; SIM PIN2. Examples: Possible Response: +CPUC? Description: Syntax: Parameters: Example: Possible Response: +CPUC=? Description: AT+CPUC=DEM,260,PIN2 <cr> OK
Report Current Price Per Unit and Currency Control The +CPUC? command returns the current parameters of PUCT. AT+CPUC? <cr> None AT+CPUC? <cr> +CPUC: DEM,260,PIN2 OK List Supported Prices Per Unit and Currency Controls The +CPUC=? command shows the list of
205
Chapter 3 AT Command Interface +CPUC=? List Supported Prices Per Unit and Currency Controls supported prices per unit and currency controls. AT+CPUC=? <cr> None AT+CPUC=? <cr> +CPUC: (list of supported <currency>s),(list of supported <ppu>s) OK Change Password The +CPWD command sets a new password for the facility lock function. AT+CPWD=<fac>,<oldpwd>], <newpwd> <fac> = AB, SC, FD, P2, or PN, entered in double quotes. AB = All Barring services (applicable only for <mode>=0). SC = SIM (lock SIM card). SIM asks password in ME power-up and when this lock command issued. FD = SIM fixed-dialing memory feature. If PIN2 authentication has not been performed during the current session, PIN2 is required as <passwd>. P2 = SIM PIN2. PN = network lock. <oldpwd> password specified for the facility from the user interface or with command, entered in double quotes.
+CPWD Description: Syntax: Parameters:
206
Chapter 3 AT Command Interface +CPWD Change Password If an old password has not yet been set, <oldpwd> is not to be entered. If <fac> = SC, then PIN. If <fac> = AO...AC (Barring), then network password. If <fac> = P2, then PIN2. A password may already be set, depending on the provider. Please check with your provider. <newpwd> = new password, entered in double quotes. Example: Possible Responses: AT+CPWD=SC,1234,5678 <cr> OK If error is related to ME functionality: +CME ERROR: <err> +CPWD=? Description: Return Available Facilities and Password The +CPWD=? command returns a list of pairs that present the available facilities and the maximum length of their password. AT+CPWD=? <cr> None AT+CPWD <cr> +CPWD: ("AB",4),("SC",8),("FD",8), ("P2",8),("PN",8) OK Service Reporting Control
+CR
207
Chapter 3 AT Command Interface +CR Description: Service Reporting Control The +CR command controls whether or not intermediate result code +CR: <serv> is returned from the TA to the TE at call setup. AT+CR=<mode> <cr> <mode> = 0 or 1 0 = disable. (DEFAULT) 1 = enable. AT+CR=0 <cr> AT+CR=1 <cr> OK
Syntax: Parameters:
Examples: Possible Response: +CR=? Description: Syntax: Parameters: Example: Possible Responses: +CR? Description: Syntax: Parameters:
List Supported Service Reporting Control Modes The +CR=? command lists supported service reporting control modes. AT+CR=? <cr> None AT+CR=? <cr> +CR: (list of supported <mode>s) OK Report Current Service Reporting Control Mode The +CR? command reports the current service reporting control mode. AT+CR? <cr> None
208
Chapter 3 AT Command Interface +CR? Example: Possible Responses: +CRC Description: Report Current Service Reporting Control Mode AT+CR? <cr> +CR: (<mode>) OK Cellular Result Codes The +CRC command controls whether the extended format of incoming call indication is used. AT+CRC=[<mode>] <cr> <mode> = 0, 1 0 = disable extended format. (DEFAULT) 1 = enable extended format. AT+CRC=0 <cr> AT+CRC=1 <cr> OK
Syntax: Parameter:
Examples: Possible Response: +CRC=? Description: Syntax: Parameters: Example: Possible Responses:
List Supported Cellular Result Codes The +CRC=? command lists the supported cellular result code modes. AT+CRC=? <cr> None AT+CRC=? <cr> +CRC: (list of supported <mode>s) OK
209
Chapter 3 AT Command Interface +CRC? Description: Report Current Cellular Result Code Mode The +CRC? command lists the current cellular result code mode used by the GSM Data Module. AT+CRC? <cr> None AT+CRC? <cr> +CRC: <mode> OK
+CREG Description:
Network Registration The +CREG command returns an integer <stat>, which shows whether the network has indicated the registration of the ME. Location information elements <lac> and <ci> are returned only when <n>=2 and ME is registered in the network. AT+CREG:<n>,<stat>,[<lac>,<ci>] <cr> <n> = 0, 1, or 2 0 = disable network registration unsolicited result code. (DEFAULT) 1 = enable network registration unsolicited result code +CREG: <stat> 2 = enable network registration and location information unsolicited result code +CREG:<stat>[,<lac>,<ci>] <stat> = 0, 1, 2, 3, 4, or 5 0 = not registered, ME is not currently searching for a new operator at which to register. 1 = registered, home network.
Syntax: Parameters:
210
Chapter 3 AT Command Interface +CREG Network Registration 2 = not registered, but ME is currently searching for a new operator at which to register. 3 = registration denied. 4 = unknown. 5 = registered, roaming. <lac> string type; two-byte location area code in hexadecimal format (e.g., 00C3 equals 193 in decimal) <ci> string type; two-byte cell ID in hexadecimal format. Example: Possible Response: AT+CREG=<n> <cr> where <n> = 0, 1, or 2 OK Unsolicited result code: When <n>=1 and there is a change in the ME network registration status: +CREG: <stat> When <n>=2 and there is a change of the network cell: +CREG: <stat>[,<lac>,<ci>] +CREG=? Description: Syntax: Parameters: Example: Possible Responses: List Supported Network Registrations The +CREG=? command lists the supported network registrations. AT+CREG=? <cr> None AT+CREG=? <cr> +CREG: (list of supported <n>s) OK
211
Chapter 3 AT Command Interface +CREG? Description: Report Current Network Registration The +CREG=? command reports the status of result code presentation and an integer <stat>, which shows whether the network has currently indicated the registration of the ME. Location information elements <lac> and <ci> are returned only when <n>=2 and ME is registered in the network. AT+CREG? <cr> None AT+CREG <cr> +CREG: <n>,<stat>,[<lac>,<ci>] OK Restore SMS Settings The +CRES command restores SMS settings for +CSCA, +CSMP from the SIM card. AT+CRES=<profile> <cr> <profile> = a number from 0 to 255 that corresponds to the user profile where the settings are to be stored. Five user profiles are supported. Example: Possible Response: AT+CRES=2 <cr> OK If error is related to ME functionality: +CMS ERROR:<err> +CRES=? Show Supported SMS Profiles
Syntax: Parameters: Example: Possible Responses: +CRES Description: Syntax: Parameters:
212
Chapter 3 AT Command Interface +CRES=? Description: Syntax: Parameters: Example: Possible Responses: +CRLP Description: Show Supported SMS Profiles The +CRES=? command shows the supported SMS profiles. AT+CRES=? None AT+CRES=? <cr> <cr>
+CRES: (list of supported <profile>s) OK Radio Link Protocol The +CRLP command sets radio link protocol (RLP) parameters used when nontransparent data calls are originated. Available command subparameters depend on the RLP versions implemented by the device (e.g., <ver> may not be available if device supports only versions 0 and 1). AT+CRLP=[<iws>[,<mws.>[,<T1>[ ,<N2>[,<ver>[,<T4>]]]]]] <cr> <iws> = 161 interworking window size (IWF to MS). (DEFAULT = 61) <mws> = 161 mobile window size (MS to IWF). (DEFAULT = 61) <T1> = 48-100 acknowledgment timer T1, in 10 ms units. (DEFAULT = 48) <N2> = 6-50 re-transmission attempts N2. (DEFAULT = 6) <ver> = 0-2
Syntax: Parameters:
213
Chapter 3 AT Command Interface +CRLP Radio Link Protocol RLP version number, in integer format. If version indication is not present, it equals 0. Versions 0 and 1 share the same parameter set. (DEFAULT is 2) <T4> = 0-100 Resequencing period in integer format, in units of 10 ms. Default values and value ranges depend on RLP version; see GSM 04.22[18]. (DEFAULT is 7) Example: Possible Response: +CRLP=? Description: AT+CRLP=50,45,42,2,5 <cr> OK
List Supported Radio Link Protocols The +CRLP=? command lists values supported by the TA as a compound value. If ME/TA supports several RLP versions (<verx>), the RLP parameter value ranges for each <verx> are returned in a separate line. Versions 0 and 1 share the same parameter set. TA returns only one line for this set (where <verx> is not present). AT+CRLP=? None AT+CRLP=? +CRLP: (list of supported <iws>s), (list of supported <mws>s), (list of supported <T1>s), (list of supported <N2>s), (list of supported <ver1>s), (list of supported <T4>s) +CRLP: (list of supported <iws>s), (list of supported <mws>s), (list of supported
214
Chapter 3 AT Command Interface +CRLP=? List Supported Radio Link Protocols <T1>s), (list of supported <N2>s), (list of supported <ver2>s), (list of supported <T4>s) OK Report Current Radio Link Protocol The +CRLP? command reports the current settings for each supported RLP version verx>. Only RLP parameters applicable to the corresponding <verx> are returned. Versions 0 and 1 share the same parameter set. TA returns only one line for this set (where <verx> is not present). AT+CRLP? <cr> None AT+CRLP? <cr> +CRLP: <iws>,<mws>,<T1>,<N2>[,<ver1>[,<T4>]] +CRLP: <iws>,<mws>,<T1>,<N2>[,<ver2>[,<T4>]] ... OK Ringer Sound Level The +CRSL command selects the incoming call ringer sound level of the ME. AT+CRSL=<level> <cr> <level> integer-type value from 1 to 5 (smallest value represents the lowest sound level). AT+CRSL=4 <cr> OK
+CRLP? Description:
+CRSL Description: Syntax: Parameters:
Example: Possible
215
Chapter 3 AT Command Interface +CRSL Responses: Ringer Sound Level +CME ERROR: <err> See subclause 9.2 for <err> values. +CRSL=? Description: Syntax: Parameters: Example: Possible Responses: List Supported Ringer Sound Levels The +CRSL=? command lists the supported ringer sound levels as compound values. AT+CRSL=? <cr> None AT+CRSL=? <cr> +CRSL: (list of supported <level>s) +CME ERROR: <err> See subclause 9.2 for <err> values. +CRSL? Description: Syntax: Parameters: Example: Possible Responses: Report Current Ringer Sound Level The +CRSL? command shows the GSM Data Modules current ringer sound level. AT+CRSL? <cr> None AT+CRSL? <cr> +CRSL: <level> +CME ERROR: <err> See subclause 9.2 for <err> values. +CSAS Save Settings
216
Chapter 3 AT Command Interface +CSAS Description: Save Settings The +CSAS command saves current message service settings for +CSCA, +CSMP to SIM card. AT+CSAS[=<profile>] <cr> <profile> = a number from 0 to 255 that corresponds to the user profile where the current message service settings are to be stored. Five user profiles are supported.
Syntax: Parameters:
If any SMS values are changed and saved on the SIM using the +CSAS command, the original values are lost and cannot be reset. Example: Possible Response: AT+CSAS=1 <cr> OK If error is related to ME functionality: +CMS ERROR:<err> +CSAS=? Description: Syntax: Parameters: Example: Possible Responses: List Supported Profiles The +CSAS=? command lists the supported profiles. AT+CSAS=? <cr> None AT+CSAS=? <cr> +CSAS: (list of supported <profile>s) OK
217
Chapter 3 AT Command Interface +CSCA Description: Set SMS Service Center Address The +CSCA command updates the SMSC address through which mobile originated SMs are transmitted. In text mode, setting is used by send and write commands. In PDU mode, setting is used by the same commands, but only when the length of the SMSC address coded into <pdu> parameter equals zero. AT+CSCA=<sca>[,<tosca>] <cr> <sca> GSM 04.11 RP SC address Address-Value field in string format; BCD numbers (or GSM default alphabet characters) are converted into characters; type of address given by <tosca>. <tosca> service center address format GSM 04.11 RP SC address Type-of-Address octet in integer format (default refer <toda>) If the parameter field <tosca> is ignored, national/international call center numbers are recognized by the leading + in the number. Example: Possible Response: +CSCA=? Description: Syntax: Parameters: AT+CSCA=2943873 <cr> (current address is entered in double quotes) OK
Syntax: Parameters:
Set Service Center Address Test Command The +CSCA=? command is a test command. AT+CSCA=? None <cr>
218
Chapter 3 AT Command Interface +CSCA=? Example: Possible Responses: +CSCA? Description: Syntax: Parameters: Example: Possible Responses: +CSCB Description: Syntax: Parameters: Set Service Center Address Test Command AT+CSCA=? OK Report Current Service Center Address The +CSCA? command reports the current service center address setting. AT+CSCA? None AT+CSCA? <cr> <cr> <cr>
+CSCA: <sca>,<tosca> OK Select Cell Broadcast Message Type The +CSCB command selects which types of CBMs are to be received by the ME. AT+CSCB=[<mode>[,mids>[,<dcss> ]]] <cr> <mode> = 0 or 1 0 = message types specified in <mids> and <dcss> are accepted. 1 = message types specified in <mids> and <dcss> are not accepted. <mids> string type entered in double quotes; different combinations of CBM message identifiers (refer to <mids>) (DEFAULT is empty string); e.g., 0,1,5,320-478,922. The <mids> under 1000 are stored on the SIM
219
Chapter 3 AT Command Interface +CSCB Select Cell Broadcast Message Type card and are not lost by power off/on. Maximum number of Message Identifiers below 1000 is 8. The <mids> from 1000 to 65535 are stored only in RAM, they are lost after power off/on. Maximum number of Message Identifiers over 999 is 12. <dcss> string type entered in double quotes; different combinations of CBM data coding schemes (refer to <dcs>) (DEFAULT is empty string); e.g., 0-3,5. The maximum <dcss> value is 15. A maximum of 15 DCS values can be set. In +CSCB commands with <mode>=0, the <dc-ss>s must be written in order of priority (highest priority language first). The new <dcss> will have higher priority than any existing <dcss>. In +CSCB? commands with <mode>=0, the <dcss>s are written in order of priority. The indices and DCS selected are stored on the SIM card. This may restrict the number of indices and DCS allowed. <sn> serial number. CB SMS receive with Message Identifiers (MI) less than 1000: Only CB SMS for which the MI matches a registered <mids> are received. If a CB SMS is received, this is only stored if at least one of the following criteria are met: The serial number has a value which is different to that of the stored message. The <dcss> of the message received has higher priority than the <dcss> of the message stored. Only the complete message is output (when all pages are received).
220
Chapter 3 AT Command Interface +CSCB Select Cell Broadcast Message Type Output on the AT interface is controlled by the AT+CNMI command: <bm> = 0, 1, 2, or 3 0 = CB SMS are not output on the AT interface. 1 = +CBMI: <mem>,<index> is sent to AT interface. 2,3 = one of the following CB SMS indications is sent to the TE: +CBM: <length><cr><lf><pdu> (in PDU mode) or +CBM:<sn>,<mid>,<dcs>,<page>, <pages><cr><lf><data> (in text mode) CB SMS receive with Message Identifiers (MI) greater than 999: The CB SMS received can be read with +CMGR, +CMGL, ^SMGR, and ^SMGL. The <mem1> must be set to BM with the command +CPMS. Only the CB SMS for which the MI matches a registered <mids> are received. The individual pages are output. Output on the AT interface is controlled with the +CNMI command: <bm> = 0, 1, 2, or 3 0 = CB SMS are not output on the AT interface. 1,2,3 = one of the following CB SMS indications is sent to the TE: +CBM: <length><cr><lf><pdu> (in PDU mode) or +CBM: <sn>,<mid>,,<page>,
221
Chapter 3 AT Command Interface +CSCB Select Cell Broadcast Message Type <pages><cr><lf><data> (in text mode) AT+CSCB=0,15-17,50,86, <cr> OK
Example: Possible Response: +CSCB=? Description:
List Supported Cell Broadcast Message Types The +CSCB=? command lists supported cell broadcast message types as a compound value. AT+CSCB=? <cr> None AT+CSCB=? <cr> +CSCB: (list of supported <mode>s) OK Report Current Cell Broadcast Message Type The +CSCB? command reports the current cell broadcast message type. AT+CSCB? None AT+CSCB? <cr> <cr>
Syntax: Parameters: Example: Possible Responses: +CSCB? Description: Syntax: Parameters: Example: Possible Responses:
+CSCB: <mode>,<mids>,<dcss> OK For a description of these values, see the +CSCB command on page 219.
222
Chapter 3 AT Command Interface +CSCS Description: Select TE Character Set The +CSCS command informs the TA which character set the TE is using. The TA can then able to convert character strings correctly between the TE and ME character sets. AT+CSCS=<chset> <cr> <chset> = one of the following conversion methods, entered in double quotes: IRA = international reference alphabet (ITU-T T.50). (DEFAULT) GSM = GSM default alphabet. HEX = character strings consist of only hexadecimal numbers from 00 to FF. PCCP437 = PC character set Code Page xxx. AT+CSCS= PCCP437 <cr> OK
Syntax: Parameters:
Example: Possible Response: +CSCS=? Description: Syntax: Parameters: Example: Possible Responses: +CSCS?
List Supported Character Sets The +CSCS=? command lists the character sets that the GSM Data Module supports. AT+CSCS=? <cr> None AT+CSCS <cr> +CSCS: <list of supported character sets> OK Report Current Character Set
223
Chapter 3 AT Command Interface +CSCS? Description: Report Current Character Set The +FCSCS? command reports the current character set that the GSM Data Module is using. AT+CSCS? <cr> None AT+CSCS? <cr> +CSCS: <chset> OK Show SMS Text Mode Parameters The +CSDH command sets whether or not detailed header information is shown in text mode result codes. AT+CSDH=<show> <cr> <show> = 0 or 1 0 = do not show header values defined in the commands +CSCA and +CSMP (<sca>, <tosca>, <fo>, <vp>, <pid>, and <dcs>) nor <length>, <toda>, or <tooa> in +CMT, +CMGL, +CMGR result codes for SMS-DELIVERs and SMSSUBMITs in text mode; for SMSCOMMANDs in +CMGR result code, do not show <pid>, <mn>, <da>, <toda>, <length>, or <cdata>. 1 = show the values in result codes. AT+CSDH=0 <cr> AT+CSDH=1 <cr> OK
Syntax: Parameters: Example: Possible Responses: +CSDH Description:
Syntax: Parameters:
224
Chapter 3 AT Command Interface +CSDH=? Description: Syntax: Parameters: Example: Possible Responses: +CSDH? Description: Syntax: Parameters: Example: Possible Responses: +CSMP Description: List Supported SMS Text Mode Parameters The +CSDH=? command lists the supported SMS text mode parameters AT+CSDH=? <cr> None AT+CSDH=? <cr> +CSDH: (list of supported <show>s) OK Report Current Text Mode Parameter The +CSDH? command reports the current text mode parameter. AT+CSDH? None AT+CSDH? <cr> +CSDH:<show> OK Set Text Mode Parameters The +CSMP command selects values for additional parameters needed when SM is sent to the network or placed in a storage when text format message mode is selected. It is possible to set the validity period starting from when the SM is received by the SMSC (<vp> is in range 0 - 255) or define the absolute time of the validity period termination (<vp> is a string). AT+CSMP=<fo>[<vp>[,pid>[,<dcs>] <cr>
Syntax:
225
Chapter 3 AT Command Interface +CSMP Parameters: Set Text Mode Parameters ]]] <cr> <fo> depending on the command or result code: first octet of GSM 03.40 SMS-DELIVER, SMSSUBMIT (DEFAULT 17), or SMSCOMMAND (DEFAULT is 16) in integer format. <vp> depending on SMS-SUBMIT <fo> setting: GSM 03.40 TP-Validity-Period in integer format (DEFAULT is 167). <pid> protocol-identifier in integer format (DEFAULT 0). Refer to GSM 03.40. <dcs> SMS Data Coding Scheme (DEFAULT 0) or Cell Broadcast Data Coding Scheme in integer format, depending on the command or result code: GSM 03.38. The command writes the parameters in nonvolatile memory with the command +CSAS. Example: Possible Response: +CSMP=? Description: Syntax: Parameters: Example: AT+CSMP=17,23,64,244 <cr> OK
Set Text Mode Parameters Test Command The +CSMP=? command is a test command. AT+CSMP=? None AT+CSMP=? <cr> <cr>
226
Chapter 3 AT Command Interface +CSMP=? Possible Responses: +CSMP? Description: Syntax: Parameters: Example: Possible Responses: Set Text Mode Parameters Test Command OK Report Current Text Mode Parameter Settings The +CSMP? command reports the current text mode parameter settings. AT+CSMP? None AT+CSMP? <cr> <cr>
+CSMP:<fo>,<vp>,<pid>,<dcs> OK <fo> = first octet of GSM 03.40 SMSDELIVER, SMS-SUBMIT or SMSCOMMAND in integer format. <vp> = GSM 03.40 TP-Validity-Period either in integer format. <pid> = Protocol-Identifier in integer format (DEFAULT 0), refer GSM 03.40. <dcs> = SMS Data Coding Scheme or Cell Broadcast Data Coding Scheme in integer format.
+CSMS Description: Syntax: Parameters:
Select Message Service The +CSMS command selects the message service. AT+CSMS=<service> <cr> <service> = 0, 1, or 128
227
Chapter 3 AT Command Interface +CSMS Select Message Service 0 = GSM 03.40 and 03.41 (the syntax of SMS AT commands is compatible with GSM 07.05 Phase 2 version 4.7.0; Phase 2+ features which do not require new command syntax may be supported (e.g. , correct routing of messages with new Phase 2+ data coding schemes). (DEFAULT) 1 = GSM 03.40 and 03.41 (the syntax of SMS AT commands is compatible with GSM 07.05 Phase 2+ version; the requirement of <service> setting 1 is mentioned under corresponding command descriptions) 128 = compatibility to Phase 1 and to device type M1 (manufacturer specific) <mt> = mobile-terminated messages 0 or 1 0 = type not supported. 1 = type supported. <mo> = mobile-originated messages 0 or 1 0 = type not supported. 1 = type supported. <bm> = broadcast-type messages 0 or 1 0 = type not supported. 1 = type supported. Example: Possible Response: +CSMS=? Description: Syntax: AT+CSMS=1 <cr> OK
List Current Supported Message Service The +CSMS=? command lists the services that the GSM Data Module supports. AT+CSMS=? <cr>
228
Chapter 3 AT Command Interface +CSMS=? Parameters: Example: Possible Response: +CSMS? Description: Syntax: Parameters: Example: Possible Response: +CSQ Description: List Current Supported Message Service None AT+CSMS=? <cr> +CSMS: (list of supported <service>s) OK Report Current Message Service The +CSMS? command reports the current message services. AT+CSMS? <cr> None AT+CSMS? <cr> +CSMS: <service>,<mt>,<mo>,<bm> OK Signal Quality The +CSQ command returns the received signal strength indication <rssi> and channel bit error rate <ber> from the ME. AT+CSQ <cr> None AT+CSQ=0,0 <cr> +CSQ: <rssi>, <ber> OK where: <rssi> is the receive level 0, 1, 230, 31, 99: 0 = -113 dBm or less. 1 = -111 dBm.
229
Chapter 3 AT Command Interface +CSQ Signal Quality 2...30 = -109... -53 dBm. 31 = -51 dBm or greater. 99 = not known. <ber> is the bit error rate 07, 99 0...7 = as RXQUAL values in the table in GSM 05.08, section 8.2.4. 99 = not known. +CSQ=? Description: Syntax: Parameters: Example: Possible Responses: Test Signal Quality The +CSQ=? command lists the supported receive levels. AT+CSQ=? <cr> None AT+CSQ=? <cr> +CSQ: (list of supported <rssi>s), (list of supported <ber>) OK
+CSSN Description:
Supplementary Service Notifications The +CSSN command enables or disables the presentation of notification result codes from the TA to the TE. When <n>=1 and a supplementary service notification is received after a mobileoriginated call setup, intermediate result code +CSSI: <code1>[,<index>] is sent to TE before any other MO call setup result codes presented in the present document or in V.25ter [14]. When several different <code1>s are received from the network, each of them shall have its own +CSSI result code.
230
Chapter 3 AT Command Interface +CSSN Supplementary Service Notifications When <m>=1 and a supplementary service notification is received during a mobile terminated call setup or during a call, or when a forward check supplementary service notification is received, unsolicited result code +CSSU:<code2>[,<index> [,<number>,<type>[,<subaddr>,<satype>]]] is sent to the TE. In case of MT call setup, result code is sent after every +CLIP result code (refer to the +CLIP command on page 140) and when several different <code2>s are received from the network, each of them shall have its own +CSSU result code. Syntax: Parameters: AT+CSSN=[<n>[,<m>]] <cr>
<n> parameter sets/shows the +CSSI result code presentation status in the TA 0 or 1 0 = disable. 1 = enable. <m> parameter sets/shows the +CSSU result code presentation status in the TA 0 or 1 0 = disable. 1 = enable. <code1> manufacturer specific, which of these codes are supported 0 = unconditional call forwarding is active. 1 = some of the conditional call forwardings are active. 2 = call has been forwarded. 3 = call is waiting. 4 = this is a CUG call (also <index> present). 5 = outgoing calls are barred. 6 = incoming calls are barred. 7 = CLIR suppression rejected.
231
Chapter 3 AT Command Interface +CSSN Example: Possible Response: +CSSN=? Description: Syntax: Parameters: Example: Possible Response: +CSSN? Description: Syntax: Parameters: Example: Possible Responses: Supplementary Service Notifications AT+CSSP=1,1,4 <cr> OK List Supported Supplementary Service Notifications The +CSSN=? command lists the supported supplementary service notifications. AT+CSSN=? <cr> None AT+CSSN=? <cr> +CSSN: (list of supported <n>.,<m>) OK Report Current Supplementary Service Notification The +CSSN? command reports the current supplementary service notification. AT+CSSN? <cr> None AT+CSSN? <cr> +CSSN: <m>,<n> OK
+CSTA Description:
Select Type of Address The +CSTA command selects the type of number for further dialing commands (D)
232
Chapter 3 AT Command Interface +CSTA Syntax: Parameters: Select Type of Address according to GSM/UMTS specifications. AT+CSTA=<addrtype> <cr> <addrtype> type of address octet in integer format (refer to GSM 04.08 [8] subclause 10.5.4.7); DEFAULT is 145 when the dialing string includes international access code character +; otherwise, 129. AT+CSTA=129 <cr> OK List Supported Address Types The +CSTA=? command lists the supported types of addresses. AT+CSTA=? <cr> None AT+CSTA=? <cr> +CSTA: (list of supported <addrtype>s) OK Report Current Address Type The +CSTA? command reports the current address type. AT+CSTA? <cr> None AT+CSTA? <cr> +CSTA: <addrtype>
Example: Possible Response: +CSTA=? Description: Syntax: Parameters: Example: Possible Responses: +CSTA? Description: Syntax: Parameters: Example: Possible
233
Chapter 3 AT Command Interface +CSTA? Responses: Report Current Address Type OK
+CTFR Description:
Set Call Deflection The +CTFR command refers to a service that causes an incoming alerting call to be forwarded to a specified number. Action command does this. Refer subclause 9.2 for possible <err> values. This is based on the GSM/UMTS supplementary service CD (Call Deflection; refer 3GPP TS 22.072 [30]). The interaction of this command with other commands based on other GSM/UMTS supplementary services is described in the GSM/UMTS standards. Call Deflection is only applicable to teleservice 11.
Syntax: Parameters:
+CTFR=<number>[,<type> [,<subaddr>[,<satype>]]] <number> string type phone number of format specified by <type>. <type> type of address octet in integer format (refer GSM 04.08 [8] subclause 10.5.4.7); default 145 when dialing string includes international access code character "+", otherwise 129 <subaddr> string type subaddress of format specified by <satype>. <satype> type of subaddress octet in integer format (refer GSM 04.08 [8] subclause 10.5.4.8);
234
Chapter 3 AT Command Interface +CTFR Example: Possible Response: +CTFR=? Description: Syntax: Parameters: Example: Possible Response: Set Call Deflection DEFAULT is 128. AT+CTFR=144,129 <cr> OK Call Deflection The +CTFR=? command lists the call deflection number. AT+CTFR=? <cr> None AT+CTFR=? <cr> +CTFR: (call deflection <number>) OK
+CUSD Description:
Unstructured Supplementary Service Data The +CUSD command controls the Unstructured Supplementary Service Data (USSD). Both network and mobile initiated operations are supported. Parameter <n> is used to disable/enable the presentation of an unsolicited result code. The value <n>=2 is used only to cancel an ongoing USSD session. When <str> is given, a mobile initiated USSD-string or a response USSDstring to a network initiated operation is sent to the network. The set command should be abortable when network is interrogated.
Syntax:
AT+CUSD=[<n>[,<str>[,<dcs>]]] <cr>
235
Chapter 3 AT Command Interface +CUSD Parameters: Unstructured Supplementary Service Data <n> = 0 or 1 0 = disable unsolicited result code presentation. 1 = enable unsolicited result code presentation. <str> string type USSD-string if <dcs> indicates that GSM03.38[25] default alphabet is used: ME/TA converts GSM alphabet into the current TE character set (see the +CSCS command) according to rules of GSM07.05[24] AnnexA. <dcs> GSM03.38[25] Cell Broadcast Data Coding Scheme in integer format: 0 = GSM default alphabet is used in <str> in ME. (DEFAULT) <m> = 0, 1, 2, 3, 4, or 5 0 = no further user action required. Network initiated USSD-Notify, or no further information needed after mobile-initiated operation. 1 = further user action required (network initiated USSD-Request, or further information needed after mobile-initiated operation) 2 = USSD terminated by network. 3 = other local client has responded. 4 = operation not supported. 5 = network time out. Example: Possible Responses: AT+CUSD=0,0,0 <cr> OK If error is related to ME functionality: +CME ERROR: <err> Unsolicited result code: When the presentation of an unsolicited code is enabled, TA send USSD response from the
236
Chapter 3 AT Command Interface +CUSD Unstructured Supplementary Service Data network or network initiated operation to the TE: +CUSD: <m>[,<str>,<dcs>] List Supported USSD Parameters for Unsolicited Result Codes The +CUSD=? command lists the supported parameters for unsolicited result codes and ongoing USSD session. AT+CUSD=? <cr> None AT+CUSD=? <cr> +CUSD: (list of supported <n>s) OK Report Current Unsolicited Result Code The +CUSD? command reports the current unsolicited result code parameter. AT+CUSD? <cr> None AT+CUSD? <cr> +CUSD: <n> OK Voice Hang Up Control The +CVHU command selects whether the command ATH or a drop of the DTR signal causes a voice connection to be disconnected or not. Voice connection includes alternating mode calls that are currently in voice mode. (See subclause 6.6).
+CUSD=? Description:
Syntax: Parameters: Example: Possible Responses: +CUSD? Description: Syntax: Parameters: Example: Possible Responses: +CVHU Description:
237
Chapter 3 AT Command Interface +CVHU Syntax: Parameters: Voice Hang Up Control AT+CVHU=<mode> <cr>
<mode> = 0, 1, or 2 0 = AT&D setting is ignored. Drop DTR is ignored, but OK result code is given. ATH disconnects. (DEFAULT) 1 = AT&D setting is ignored. Drop DTR and ATH are both ignored, but OK result code is given. 2 = drop DTR behavior according to the AT&Dn command in effect. ATH disconnects. AT+CVHU=1 <cr> OK
Example: Possible Response: +CVHU=? Description:
List Supported Voice Hang Up Modes The +CVHU=? command lists the voice hang up modes that the GSM Data Module supports. AT+CVHU=? <cr> None AT+CVHU=? <cr> +CVIB: (list of supported <mode>s) OK Report Current Voice Hang Up Mode The +CVHU? command reports the current voice hang up mode for the GSM Data Module. AT+CVHU <cr>
Syntax: Parameters: Example: Possible Response: +CVHU? Description:
Syntax:
238
Chapter 3 AT Command Interface +CVHU? Parameters: Example: Possible Response: +CVIB Description: Syntax: Parameters: Report Current Voice Hang Up Mode None AT+CVHU <cr> +CVIB: <mode> OK Vibrator Mode The +CVIB command enables and disables the vibrator alert feature of the ME. AT+CVIB=<mode> <mode> = 0 or 1 0 = disable. 1 = enable. AT+CVIB=1 <cr> OK +CME ERROR: <err> +CVIB=? Description: List Supported Vibrator Modes The +CVIB=? command lists, as compound values, the vibrator modes that the GSM Data Module supports. AT+CVIB=? <cr> None AT+CVIB=? <cr> +CVIB: (list of supported <mode>s) OK <cr>
239
Chapter 3 AT Command Interface +CVIB=? +CVIB? Description: Syntax: Parameters: Example: Possible Responses: List Supported Vibrator Modes +CME ERROR: <err> Report Current Vibrator Mode The +CVIB? command reports the current vibrator mode for the GSM Data Module. AT+CVIB <cr> None AT+CVIB <cr> +CVIB: <mode> OK +CME ERROR: <err> +VTD Description: Tone Duration The +VTD command defines the length of tones emitted as a result of the +VTS command. This does not affect the D command. AT+VTD=<n> <cr> <n> is the length of tones emitted as a result of the +VTS command. Valid values are: 0, 1, 2, 5, 10, 20, and 50. Values other than zero cause a tone of duration <n>/10 seconds. AT+VTD=15 <cr> OK In GSM, the value of tone duration is preset and cannot be altered.
Syntax: Parameters:
240
Chapter 3 AT Command Interface +VTD=? Description: Syntax: Parameters: Example: Possible Response: +VTD? Description: Syntax: Parameters: Example: Possible Responses: +VTS Description: List Supported Tone Durations The +VTD=? command lists the supported tone durations. AT+VTD=? <cr> None AT+VTD=? <cr> +VTID: (list of supported <n>s) OK Report Current Tone Duration The +VTD? command reports the current tone duration. AT+VTD? <cr> None AT+VTD? <cr> +VTD: (current length of tone) OK DTMF and Tone Generation The +VTS command allows the transmission of DTMF tones and arbitrary tones in voice mode. These tones may be used (for example) when announcing the start of a recording period. D is used only for dialing.
This is interpreted as a sequence of DTMF tones whose duration is set by the +VTD command.
241
Chapter 3 AT Command Interface +VTS DTMF and Tone Generation

This has no function at GSM. This is interpreted as a DTMF tone whose duration is determined by <duration>.
Syntax:
AT+VTS=<dtmfstring> <cr> AT+VTS=[<tone1>,<tone2>,<duration>] <cr> AT+VTS=<dtmf>,<duration> <cr> <dtmf> string of ASCII characters in the set 0-9,#,*,. Maximum length of the string is 29. The string must be entered between double-quote characters (). Example for 1234 string: AT+VTS="1,2,3,4" <tone1> and <tone2> dual-tone frequencies lasting for a time <duration> (in 10 ms multiples). <duration> duration of the tone from in 1/10 seconds. Valid values are 10, 20, 50, 100, 200, and 500.
Parameters:
AT+VTS=5551212 <cr> OK If error is related to ME functionality: +CME ERROR: <err> The command is write only.
+VTS=? Description: Syntax:
List Supported DTMF Tones The +VTS=? command lists the supported DTMF tones and durations. AT+VTS=? <cr>
242
Chapter 3 AT Command Interface +VTS=? Parameters: Example: Possible Responses: List Supported DTMF Tones None AT+VTS=? <cr> +VTS: (list of supported <dtmf>s, (list of supported <duration>s) OK In GSM, the value of tone duration is preset and cannot be altered; therefore, the <duration> list is not presented. +WS46 Description: Select Wireless Network The +WS46 command lets the attached computer set the type of wireless network used with the GSM Data Module. AT+WS46<n> <cr> <n> = integer corresponding to a supported wireless network. 12 = GSM digital cellular network AT+WS46=12 <cr> OK
Syntax: Parameters:
Example: Possible Response: +WS46=? Description:
List Supported Wireless Networks The +WS46=? command lists the wireless networks that the GSM Data Module supports. AT+WS46=? <cr> None
Syntax: Parameters:
243
Chapter 3 AT Command Interface +WS46=? Example: Possible Response: +WS46? Description: List Supported Wireless Networks AT+WS46=? <cr> 12 OK Report Wireless Network Used The +WS46? command queries the attached computer to ascertain the type of wireless network used with the GSM Data Module. AT+WS46? <cr> None AT+WS46 <cr> 12 OK Enable/Disable Abort Key The $ABRT command enables or disables the abort key. AT$ABRT=<n> <cr> <n> = 0 or 1 0 = disable abort key. 1 = enable abort key. (DEFAULT) AT$ABRT=0 <cr> AT$ABRT=1 <cr> 12 OK List Supported Abort Key Values The $ABRT=? command lists the abort key
Syntax: Parameters: Example: Possible Response: $ABRT Description: Syntax: Parameters:
Examples: Possible Response: $ABRT=? Description:
244
Chapter 3 AT Command Interface $ABRT=? Syntax: Parameters: Example: Possible Response: $ABRT? Description: Syntax: Parameters: Example: Possible Responses: List Supported Abort Key Values values that the GSM Data Module supports. AT$ABRT=? <cr> None AT$ABRT=? <cr> $ABRT: 0-1 OK Report Current Abort Key Command Setting The $ABRT? command shows the current abort key command setting in effect. AT$ABRT? <cr> None AT$ABRT <cr> $ABRT:0 OK $ABRT:1 OK
$ICB Description:
Incoming Call Bearer The $ICB command sets the MT call to voice, data, or fax if the bearer is not specified. AT$ICB<ICBvalue> <cr> <ICBvalue> = 1, 2, or 3 1 = voice (sets the MT call to voice if the bearer is not specified).
Syntax: Parameters:
245
Chapter 3 AT Command Interface $ICB Incoming Call Bearer 2 = data (sets the MT call to data if the bearer is not specified). 3 = fax (sets the MT call to fax if the bearer is not specified). AT$ICB=1 <cr> OK
$ICB=? Description: Syntax: Parameters: Example: Possible Response: $ICB? Description: Syntax: Parameters: Example: Possible Response: $SCRT Description:
List ICB Range The $ICB=? command lists the ICB range. AT$ICB=? <cr> None AT$ICB=? <cr> $ICB:(1-3) OK Report Current ICB Setting The $ICB? command shows the current ICB setting in effect. AT$ICB? <cr> None AT$ICB <cr> $ICB:1 OK Save CSCA and CSMP Parameters The $SCRT command stores a section of the
246
Chapter 3 AT Command Interface $SCRT Save CSCA and CSMP Parameters RAM table in the GSM Data Modules nonvolatile memory. The RAM data is associated with the AT commands +CSCA and +CSMP. AT$SCRT <cr> None AT$SCRT <cr> OK: execution successful. The current user settings with +CSCA and +CSMP are stored in nonvolatile memory and will be restored in the next power cycle. Error: failure in execution. User settings are not stored in nonvolatile memory. $SMSCA=? Description: Syntax: Parameters: Examples: Possible Response: Read SCA from SIM The $SMSCA=? command returns the OK response. AT$SMSCA=? <cr> None AT$SMSCA=? <cr> OK
Syntax: Parameters: Examples: Possible Responses:
$SMSCA? Description:
Read SCA from SIM The $SMSCA? command reads the service center address form the SIM.
247
Chapter 3 AT Command Interface $SMSCA? Syntax: Parameters: Examples: Possible Responses: Read SCA from SIM AT$SMSCA? <cr> None AT$SMSCA? <cr> $SMSCA: <index>, "name", sca, type OK where <index> = integer type; range 1 to 5. "name" = string type; Service Center Name. String length up to 20 characters. The string length is SIM-specific. The GSM Data Module displays up to 20 characters. sca = integer type; Service Center Address, length up to 24 digits. type = type of sca octet in integer format (145 for international, 129 unknown , or empty for else). Example: $SMSCA: 1,"ABCDEFGHIJKL",+393359609600214 36587,145 $SMSCA: 2,"QRSTUVWXYZ",2143658709214,129 OK If the SIM has no Service Center record, this command returns OK. ERROR (CME ERROR) SIM is locked by PIN1. $UIND Command to Switch Unsolicited Message
248
Chapter 3 AT Command Interface $UIND Description: Command to Switch Unsolicited Message The $UIND command can be used to switch the unsolicited message. When PIN1 check is enabled and the UIND for bit0 (LSB) is enabled, SIM PIN REQUIRED appears after power-up until the first pin verification is attempted or the UIND for bit0 (LSB) is disabled. When PIN1 is blocked and the UIND for bit0 is enabled, SIM PUK REQUIRED appears then after power-up until the PUK verification is attempted or the UIND for bit0 (LSB) is disabled. Syntax: Parameters: AT$UIND<UINDvalue> <cr> <UINDvalue> any decimal within the supported range (065535). (DEFAULT = 0 disables the indication.) For the PIN1 check indication: <UINDvalue> = any odd parameter enables the indication. <UINDvalue> = any even parameter disables the indication. Examples: AT$UIND=0 <cr> (all 16 indications are disabled) AT$UIND=3 <cr> (indications corresponding to the first and third bits are enabled) Possible Response: OK
$UIND=? Description:
List UIND Range The $UIND=? command lists the UIND range.
249
Chapter 3 AT Command Interface $UIND=? Syntax: Parameters: Example: Possible Response: $UIND? Description: Syntax: Parameters: Example: Possible Response: List UIND Range AT$UIND=? <cr> None AT$UIND=? <cr> $UIND:(0-65535) OK Report Current UIND Setting The $UIND? command shows the current UIND setting in effect. AT$UIND? <cr> None AT$UIND <cr> $UIND:65535 OK (all 16 locations are enabled)
250

AT Command Interface Chapter

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

AT Command Interface Chapter

Transféré par

Droits d'auteur :

Formats disponibles

Chapter 3 AT Command Interface

Syntax Parameters: Example: Possible Response: Notes:

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

A Description: Syntax: Parameters Example: Possible Responses:

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

Examples: Possible Responses:

Cn Description: Syntax: Parameters:

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

Examples: Possible Response:

Hn Description: Syntax: Parameters: Example: Possible Response: Notes:

In Description: Syntax: Parameters:

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

Examples: Possible Response:

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

Possible Response: Nn Description: Syntax: Parameters:

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

Chapter 3 AT Command Interface Nn Response: Automode Enable/Disable

On Description: Syntax: Parameters: Example: Possible Responses:

Syntax: Example: Possible Responses:

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

Qn Description: Syntax: Parameters:

Examples: Possible Responses:

Syntax: Parameters: Example:

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

Chapter 3 AT Command Interface S0 Possible Response: S3 Description: Set Number of Rings OK

Syntax: Parameters: Example: Possible Response: S4 Description:

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

Syntax: Parameters: Example: Possible Response: S7 Description:

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

Syntax: Parameters: Example: Possible Response: S10 Description:

Syntax: Parameters: Example:

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

Syntax: Example: Possible Responses:

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

Possible Response: Wn Description: Syntax: Parameters:

Extended Result Code

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

Examples: Possible Response: Yn Description: Syntax: Parameters:

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

Example: Possible Response: Notes:

\Kn Description: Syntax:

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

Example: Possible Response:

&Cn Description: Syntax: Parameters:

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

Examples: Possible Response: &Fn Description:

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

Example: Possible Response: Notes:

&Kn Description: Syntax: Parameters:

Examples: Possible Response:

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

Examples: Possible Response: &Rn Description:

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

Examples: Possible Response: &Tn Description:

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001

Examples: Possible Response: Notes:

&V Description: Syntax: Parameters:

GSMDM-100DB GSM Data Module Reference Guide PRELIMINARY DRAFT 11/15/2001