cdma data terminal - search read.pudn.comread.pudn.com/downloads116/doc/494283/cdma at...

CDMA DATA TERMINAL

AT Command Set Application Information

December.19, 2007

AnyDATA AnyTime AnyPlace Any Wireless Data SolutionTM

2

About this Guide CDMA (Code Division Multiple Access) Data Module operating functions are implemented as AT commands, and are available via the Data Module serial interface. This reference manual describes the AT commands supported by CDMA Data Module. The following sections define the CDMA Data Module operating modes. 1 Defines the Command Mode and Data Mode 2 Command Line Syntax – Defines AT commands prefix, body, and termination character 3 Concatenating AT Commands – Multiple AT commands 4 Working with Command Lines 5 Command Summary Summarizes the commands that CDMA Data Module supports 6 Command Descriptions Defines the AT Commands, CDMA Commands,


3

1 Operating Modes The CDMA Data Module operates in one of the following modes:

Command Mode - Enables the transmission of AT commands to the CDMA Data Module via its serial interface. Data Mode - Allows the CDMA Data Module to exchange data across the communications line with a remote

modem. The CDMA Data Module enters the Command Mode automatically when the module station (MS):

Is turned on Loses the data connection with a remote modem Detects an On-to-Off transition on the Data Terminal Ready (DTR) circuit with the &D1 command in effect.

When this occurs, the CDMA Data Module returns to Command Mode without hanging up. To hang up the CDMA Data Module, send the H command or, if the &D2 command is in effect, use the software to turn off the DTR.

Detects an On-to-Off transition on the DTR circuit with the &D2 command in effect. When this occurs, the CDMA Data Module hangs up, and returns to Command Mode.

Detects an On-to-Off transition on the DTR circuit with the &D3 command in effect. When this occurs, the CDMA Data Module:

Hangs up Resets itself Loads the active configuration from nonvolatile memory Returns to Command Mode

1.1 Entering Data Mode The CDMA Data Module automatically enters Data Mode after making a data connection with a remote modem. But we do not support the GSM-like data connection yet.


4

2 Command Line Syntax When using the CDMA Data Module, typing AT commands enables the data module to perform various activities. The AT standard is a line-oriented command language that is typed on a command line. Each command line consists of the following:

Prefix: Consists of the characters AT, which preface every command line, except those containing the A/ command.

Body: Consists of individual characters described in this chapter. Some commands have optional numeric parameters associated with them. These optional values are denoted with brackets, for example, […], in this document.

Termination: Completes the command line, and tells the CDMA Data Module to execute it. The default termination character is (= 0x0D).

The following is an example of a command line.

One command line holds up to 39 characters, excluding the AT characters at the start of the line. Each command is separated by spaces to enhance readability.

Note: Spaces are not counted as command line characters, and are ignored by the CDMA Data Module. Characters such as parentheses and dashes are used to improve readability. The CDMA Data Module ignores these characters, but applies them to the 39 maximum command line character count. When a command line is executed, the CDMA Data Module returns an OK result code. If an ERROR result code is received, verify that the command line does not contain:

An invalid command More than 39 characters


5

3 Concatenating AT Commands When executing multiple AT commands, each command must be typed on a single command line with as the line terminator. For example: AT&W0&Y0&C1 If the CDMA Data Module is to execute AT commands along with +F and +V commands, a semicolon “;” is inserted between the AT, +F, and +V commands with as the line terminator. The following example shows how to use the semicolon to concatenate a +FAA command with the M0 command. AT+FAA=0;M0


6

4 Working with Command Lines This section provides guidelines for working with command lines.

4.1 Omitting a Command Parameter Some commands require a numeric parameter such as 0, 1, or 2 to completely define the command. For example, the Qn command determines whether the CDMA Data Module sends result codes. Omitting a parameter from a command that requires one is equivalent to specifying a parameter of 0. For example, if the Qn command is entered without specifying either 0 or 1, it is equivalent to sending the command Q0, which enables result codes.

Q0 activate a result code. Q1 suppresses result codes.

4.2 Repeating a Command Line The CDMA Data Module stores the last-executed command line in memory until it executes a new command line. To re-execute the last command line sent, type A/ without typing AT before it or pressing <cr> after typing it. The A/ command is particularly useful when the CDMA Data Module is to re-execute a lengthy command line.

Caution If the CDMA Data Module is reset or loses power, the last-executed command is lost from memory. This renders the A/ command useless until the Module executes a command line.

4.3 Result Codes By default, when a command line is sent to the CDMA Data Module, the Module sends a result code such as OK. The default Q0 command is then in effect.

To disable result codes, issue the Q1 command To reactivate result codes, issue the Q0 command

4.4 Result Code Format Result codes appear as English words or numbers, depending on the Vn command in effect, see Table 6-12.

The V1 command enables word result codes. Word result codes are followed by a carriage return and line feed. The V0 command enables numeric responses. Numeric result codes are followed by a carriage return only.

Numeric result codes are useful if the CDMA Data Module is operating under an application that either cannot handle character strings, or handles them inefficiently.


7

5 Command Summary Table 5-1 lists the AT Commands that are supported by the CDMA Data Module. Table 5-2 lists the GSM commands. For additional information about the commands, refer to the table as indicated.

Table 5-1 AT Command Summary

Command Description See A/ Repeat Last Command Line Executed Table 6-1 A Answer Incoming Call Table 6-2 D Dial Command Table 6-3 En Enable Command Echo Table 6-4 Hn Hook Switch Table 6-5 Qn Suppress Result Codes Table 6-6 S0 Set Number of Rings Table 6-7 S3 Set Carriage Return Character Table 6-8 S4 Set Line Feed Character Table 6-9 S5 Set Backspace Character Table 6-10 T Tone Dial Table 6-11 Vn Result Code Format Table 6-12 &Cn DCD Control Table 6-13 &Dn DTR Control Table 6-14 +IFC Set Local Data Flow Control Table 6-15 +IFC=? Supported Flow Control Methods Table 6-16 +IFC? Current Flow Control Method Table 6-17 +IPR Set Fixed DTE Rate Table 6-18 +IPR=? Supported Fixed DTE Rates Table 6-19 +IPR? Current Fixed DTE Rate Table 6-20

Table 5-2 GSM Command Summary

Command Description See +CCFC Call Forwarding and Conditions Table 6-21 +CCFC=? Supported Call Forwarding Reasons Table 6-22 +CCWA Call Waiting Table 6-23 +CCWA=? Supported Call Waiting Values Table 6-24 +CCWA? Current Call Waiting Status Table 6-25 +CFUN Set Phone Functionality Table 6-26 +CFUN=? Supported Phone Functionality Table 6-28 +CFUN? Current Phone Functionality Table 6-27 +CHLD Call Hold Table 6-29 +CHLD=? Supported Call Hold Parameters Table 6-30 +CIMI Request International Mobile Subscriber Identity Table 6-31 +CIMI=? Supported International Mobile Subscriber Identity Table 6-32 +CKPD Keypad Control Table 6-33 +CKPD=? Supported Keypad Control Values Table 6-34


8

Command Description See +CLCC List Current Calls Table 6-35 +CLCC=? Current Calls Test Command Table 6-36 +CLCK Facility Lock Table 6-37 +CLCK=? Supported Facility Lock Modes Table 6-38 +CLIP Calling line Identification presentation Table 6-39 +CLIP=? Supported Calling line Identification presentation Values Table 6-40 +CLIP? Current Calling line Identification presentation Status Table 6-41 +CLIR Calling Line Identification Restriction Table 6-42 +CLIR=? Supported Calling Line Identification Restriction Values Table 6-43 +CLIR? Current Calling Line Identification Restriction Status Table 6-44 +CLVL Loudspeaker Volume Level Table 6-45 +CLVL=? Supported Loudspeaker Volume Levels Table 6-46 +CLVL? Current Loudspeaker Volume Level Table 6-47 +CMEE Mobile Equipment Error Code Table 6-48 +CMEE=? Supported Mobile Equipment Error Code Values Table 6-49 +CMEE? Current Mobile Equipment Error Code Status Table 6-50 +CMGD Delete Message Table 6-52 +CMGD=? Delete Message Test Command Table 6-53 +CMGF Message Format Table 6-54 +CMGF=? Supported Message Format Modes Table 6-55 +CMGF? Current Message Format Mode Table 6-56 +CMGR Read Message Table 6-57 +CMGR=? Read message Test Command Table 6-58 +CMGS Send Message Table 6-59 +CMGS=? Send Message Test Command Table 6-60 +CMGW Write Message Table 6-61 +CMGW=? Write Message Test Command Table 6-62 +CMUT Mute control Table 6-63 +CMUT=? Supported Mute Control Values Table 6-64 +CMUT= Current Mute Control Status Table 6-65 +CMUX Multiplexing Mode Table 6-66 +CMUX=? Supported Multiplexing Modes Table 6-67 +CMUX? Current Multiplexing Mode Table 6-68 +CNMI New Message Indication Table 6-69 +CNMI=? Supported New Message Indication Values Table 6-70 +CNMI? Current New Message Indication Status Table 6-71 +CNUM Subscriber Number Table 6-72 +CNUM=? Subscriber Number Test Command Table 6-73 +COLP Connected Line Identification Presentation Table 6-74 +COLP=? Supported Connected Line Identification Presentation Values Table 6-75 +COLP? Current Connected Line Identification Presentation Status Table 6-76 +COPS Network Operator Selection Table 6-77 +COPS=? Supported Network Operators Table 6-78 +COPS? Current Network Operator Table 6-79


9

Command Description See +CPAS Phone Activity Status Table 6-80 +CPAS=? Phone Activity Status Test Command Table 6-81 +CPBD Delete Phonebook Entry Table 6-82 +CPBF Find Phonebook Entry Table 6-83 +CPBF=? Find Phonebook Entry Test Command Table 6-84 +CPBR Read Phonebook Table 6-85 +CPBR=? Read Phonebook Test Command Table 6-86 +CPBS Phonebook Memory Storage Table 6-87 +CPBS=? Supported Phonebook Memory Storages Table 6-88 +CPBS? Current Phonebook Memory Storage Table 6-89 +CPBW Write Phonebook Entry Table 6-90 +CPBW=? Write Phonebook Test Command Table 6-91 +CPIN Enter PIN Table 6-92 +CPIN=? Enter PIN Test Command Table 6-93 +CPIN? Current PIN Status Table 6-94 +CPMS Set Preferred Message Storage Table 6-95 +CPMS=? Supported Message Storages Table 6-96 +CPMS? Current Message Storage Table 6-97 +CPWD Change Password Table 6-98 +CPWD=? Supported Password Table 6-99 +CREG Network Registration Table 6-100 +CREG=? Supported Network Registration Values Table 6-101 +CREG? Current Network Registration Status Table 6-102 +CSCA Set Service Center Address Table 6-103 +CSCA=? Service Center Address Test Command Table 6-104 +CSCA? Current Set Service Center Address Table 6-105 +CSCS Select TE Character Set Table 6-106 +CSCS=? Supported TE Character Sets Table 6-107 +CSCS? Current TE Character Set Table 6-108 +CSMS Select Message Service Table 6-109 +CSMS=? Supported Message Service Table 6-110 +CSMS? Current Message Service Table 6-111 +CSQ Signal Quality Table 6-112 +CSQ=? Supported Signal Quality Values Table 6-113 +VTS DTMF and Tone Generation Table 6-114 +VTS=? Supported DTMF Tones Table 6-115 $SMOD Sleep Mode Table 6-116 $SMOD=? Supported Sleep Mode Values Table 6-117 $SMOD? Current Sleep Mode Status Table 6-118 $LCT Auto Power Off Table 6-119 $LCV Check SW Version Table 6-120 $LCHFREE Audio Path Table 6-121 $LCHFREE=? Supported Audio Path Values Table 6-122 $LCHFREE? Current Audio Path Setting Table 6-123


10

Command Description See $LTST Audio Loopback Test Table 6-124 $LTST=? Supported Audio Loopback Test Values Table 6-125 $LTST? Current Audio Loopback Test Value Table 6-126 $LCST Customer Select Table 6-127 $LCST=? Supported Customer Select Values Table 6-128 $LCST? Current Customer Select Value Table 6-129 $LLOC? Check Min Lock and MCC Lock Status Table 6-130 +CCPS=? Check Remain Count for Pin Number Input Table 6-131 +CCTI System Time Information Table 6-132 +CCTI=? Check Current System Time Information Table 6-133


11

6 Command Descriptions This section provides detailed descriptions about the following commands that the CDMA Data Module supports.

AT Commands, Section 6.1 GSM Commands, Section 6.2

6.1 AT Commands The AT commands that the CDMA Data Module supports are shown in Table 6-1 through Table 6-20.

6.1.1 Repeat Last Command Line Executed The A/ command instructs the CDMA Data Module to re-execute the last command line executed. This command executes as soon as the / character is typed. This command is useful when the CDMA Data Module is required to re-execute a lengthy command line. See Table 6-1.

Note: Do not precede this command with the AT prefix, or end it with a termination character.

Table 6-1 Repeat Last Command Line Executed

Parameters Definition Syntax Definition Parameters A/ Example None Possible Response OK Note: The last-executed command line stays in the CDMA Data Module until it is turned off or reset with the Z

command see. Either action invalidates the A/ command, since there is no command in memory to re-execute.

6.1.2 Answer Incoming Call The A command instructs the CDMA Data Module to answer an incoming call.

Table 6-2 Answer Incoming Call

Parameters Definition Syntax ATA Parameters None Example ATA Possible Response CONNECT if the call is accepted.

OK when the CDMA Data Module returns to Command Mode. NO CARRIER if there is no connection.

Note: 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 such as, during handshaking, the command cannot be aborted.


12

6.1.3 Dial Command The D command allows the user to originate a voice call to a dialed number, or to dial a number stored in memory. This command also controls supplementary services.

Table 6-3 Dial Command

Parameters Definition Syntax ATD<n>[;] Parameters V.250 dialing digits

1 2 3 4 5 6 7 8 9 0 * # (mandatory for GSM/UMTS) + A B C (mandatory for GSM/UMTS, but it may be ignored) D (optional for GSM/UMTS, and it is ignored)

V.250 modifier characters , (mandatory for GSM/UMTS, but it may be ignored) T P (mandatory for GSM/UMTS, but they are ignored) ! W @ (optional for GSM/UMTS, and they are ignored)

V.250 semicolon character In GSM/UMTS, when semicolon character is given after dialing digits (or modifiers), a voice call originated to the given address. TA returns to command state immediately (or after possible +COLP result code.

Example ATD9495551212; // Make a voice call ATD#777 // Make a data call

Possible Response OK-Voice call connects successfully NO CARRIER-The connection cannot be set up. +CME ERROR: <err>-An error is related to Data Module functionality.

Note: Up to 20 dialing digits and GSM modifiers follow the ATD command.

6.1.4 Enable Command Echo The En command determines whether the CDMA Data Module echoes the command characters received during Command Mode.

Table 6-4 Enable Command Echo

Parameters Definition Syntax ATE<n> Parameters <n> = 0 or 1

0 = do not echo command characters. 1 = echo command characters.

Example ATE1 ATE0

Possible Response OK-Acknowledges the change of state.

6.1.5 Hook Switch - Disconnect Existing Connection The Hn command terminates the current call.

Table 6-5 Hook Switch – Disconnect Existing Connection

Parameters Definition Syntax ATH<n>


13

Parameters <n> = 0 0 = Terminates the call and disconnect from line.

Example ATH0 Possible Response OK-Acknowledges the change of state. Note: OK is issued after circuit 109 (DCD) turns OFF (if it was ON).

6.1.6 Suppress Result Codes The Qn command determines whether the CDMA Data Module transmits result codes.

Table 6-6 Suppress Result Codes

Parameters Definition Syntax ATQ<n> Parameters <n> = 0 or 1

0 = transmit result codes. 1 = do not transmit result codes.

Example ATQ0 ATQ1

Possible Response If <n>=0: OK If <n>=1: no response

6.1.7 Set Number of Rings The S0 command determines the number of rings that must occur before the CDMA Data Module automatically answers an incoming call.

Table 6-7 Set Number of Rings

Parameters Definition Syntax ATS0=<n> Parameters <n> = 0 to 255 rings. Example ATS0=1 Possible Response OK

6.1.8 Set 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, and can be changed to another ASCII value between 0 and 127.

Table 6-8 Set Carriage Return Character

Parameters Definition Syntax ATS3=<n> Parameters <n> = 0 to 127 ASCII. (Default = 13 [CTRL-M]) Example ATS3=4 Possible Response OK


14

6.1.9 Set Line Feed Character The S4 command sets the ASCII value of the line feed character. The default value is 10, and can be changed to another ASCII value between 0 and 127. The CDMA 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 the user does not want to receive a line feed character, the value in this register can be changed to a null character. Do not disable line feed characters.

Table 6-9 Set Line Feed Character

Parameters Definition Syntax ATS4=<n> Parameters <n> = 0 to 127 ASCII (Default = 10 [CTRL-J]) Example ATS4=6 Possible Response OK

6.1.10 Set Backspace Character The S5 command sets the ASCII value of the backspace character. This character is created by pressing the backspace key, and the character echoed moves the cursor to the left. The default value is 8. If the user changes this value, the value must not be between 33 and 126, these values are equivalent to a printable ASCII character and the modem does not recognize it as a backspace character.

Table 6-10 Set Backspace Character

Parameters Definition Syntax ATS5=<n> Parameters <n> = 0 to 32 ASCII Example ATS5=28 Possible Response OK

6.1.11 Instruct the CDMA Data Module to Use the Tone (DTMF) Dialing Method The T modifier instructs the CDMA Data Module to use the tone (DTMF) dialing method to dial calls that follow the T modifier in the Dial command line.

Table 6-11 CDMA Data Module to Use the Tone (DTMF) Dialing Method

Parameters Definition Syntax ATDT<dialing digits> Parameters <dialing digits> = 1 2 3 4 5 6 7 8 9 0 * #

Refer to subclause 6.1.3 for more information. Example ATDT9495551212 Possible Response OK if voice call connects successfully.

NO CARRIER if a connection cannot be set up. +CME ERROR: <err> if error is related to Data Module functionality.


15

6.1.12 Result Code Format This result code format setting determines the contents of the header and trailer transmitted with result codes and information responses.

Table 6-12 Result Code Format

Parameters Definition Syntax ATV<n> Parameters <n> = 0 or 1

0 = use numeric result codes followed by <lf>. 1 = use word result codes preceded and followed by <lf>.

Example ATV0 ATV1

Possible Response OK

6.1.13 DCD Control The &Cn command controls the Data Carrier Detect (DCD) signal.

Table 6-13 DCD Control

Parameters Definition Syntax AT&C<n> Parameters <n> = 0 or 1

0 = DCD is always ON. 1 = DCD is ON only when the remote modem’s data carrier is present.

Example AT&C0 AT&C1


6.1.14 DTR Control The &Dn command determines how the CDMA Data Module reacts when an ON-to-OFF Data Terminal Ready (DTR) transition occurs.

Table 6-14 DTR Control

Parameters Definition Syntax AT&D<n> Parameters <n> = 0, 1, or 2

0 = CDMA Data Module ignores DTR transitions. 1 = ON-to-OFF DTR transition causes the CDMA Data Module to change to Command

Mode while retaining the connected call. 2 = ON-to-OFF DTR transition causes the CDMA Data Module to disconnect call and

change to Command Mode. Example AT&D0

AT&D2 Possible Response OK


16

6.1.15 Set Local Data Flow Control The IFC command determines if flow control is used on the CDMA Data Module’s 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.

Table 6-15 Set Local Data Flow Control

Parameters Definition Syntax AT+IFC=[<dce_by_dte>[,<dte_by_dce>]] Parameters <dce_by_dte> = one of the following flow control methods from the DTE point of view:

0 = none. 1 = XON/XOFF, don’t pass characters to data stack. 2 = line 133: ready for receiving. (Default) <dte_by_dce> = one of the following flow control methods from the CDMA Data Module’s point of view: 0 = none. 1 = XON/XOFF. 2 = line 106, Clear to Send. (Default)

Example AT+IFC=0,0 AT+IFC=1,1


6.1.16 Supported Flow Control Methods The +IFC=? command lists the flow control methods that the CDMA Data Module supports.

Table 6-16 Supported Flow Control Methods

Parameters Definition Syntax AT+IFC=? Parameters None Example AT+IFC=? Possible Response +IFC: (0-2),(0-2)

OK

6.1.17 Current Flow Control Method The +IFC? command reports the current flow control method in effect.

Table 6-17 Current Flow Control Method

Parameters Definition Syntax AT+IFC? Parameters None Example AT+IFC? Possible Response IFC: 2,2

OK


17

6.1.18 Set Fixed DTE Rate The IPR sets the data rate on the CDMA Data Module’s serial interface. The Module accepts rates from 300 to 115,200 bps. The rate takes effect following the result code issued after this command executes.

Table 6-18 Set Fixed DTE Rate

Parameters Definition Syntax AT+IPR=<rate> Parameters <rate> = one of the following baud rates:

300 1200 2400 4800 9600 (Default) 19200 28800 38400 57600 115200

Example AT+IPR=9600 AT+IPR=57600

Possible Response OK Note: 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 becomes corrupted. However, there are no restrictions on using this command in a command string, for example, AT&Fs0=1+ipr=9600&W+cbst=7,0,1. The CDMA Data Module does not support autobaud

6.1.19 Supported Fixed DTE Rates The +IPR=? lists the fixed-only rates that are supported on the CDMA Data Module’s serial interface.

Table 6-19 Supported Fixed DTE Rates

Parameters Definition Syntax AT+IPR=? Parameters None Example AT+IPR=? Possible Response +IPR: (list of supported autodetectable <rate> values)[,list of fixed-only <rate>values)]

OK

6.1.20 Current Fixed DTE Rate The +IPR? reports the current rate on the CDMA Data Module’s serial interface.

Table 6-20 Current Fixed DTE Rate

Parameters Definition Syntax AT+IPR? Parameters None Example AT+IPR? Possible Response +IPR: <rate>

OK


18

6.2 GSM Commands The GSM commands that are supported by the CDMA Data Module are shown in Table 6-21 through Table 6-118.

6.2.1 Call Forwarding and Conditions The +CCFC allows control of the call forwarding supplementary service according to Third Generation Partnership Project (3GPP) Technical Standard (TS) 22.082 [4]. Registration, erasure, activation, deactivation, and status query are supported. When querying the status of a network service (<mode>=2) the response line for 'not active' case (<status>=0) must be returned only if service is not active for any <class>.

Table 6-21 Call Forwarding and Conditions

Parameters Definition Syntax AT+CCFC=<reas>,<mode>[,<number> [,<type>[,<class>

[,<subaddr>[,<satype>[,<time>]]]]]] Parameters <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 1 = voice. 2 = data. 4 = fax. 7 = all classes. (Default)

<time> time to wait before call is forwarded, rounded to a multiple of 5 seconds. DEFAULT is 20 seconds. 1...20...30 (only for <reas> = no reply)

Example AT+CCFC=1,1,5551212 Possible Response OK

<status> = 0 or 1 0 = not active 1 = active


19

6.2.2 Supported Call Forwarding Reasons The +CCFC=? lists the call forwarding that the CDMA Data Module supports.

Table 6-22 Supported Call Forwarding Reasons

Parameters Definition Syntax AT+CCFC=? Parameters None Example AT+CCFC=? Possible Response +CCFC: (list of supported <reas>s)

OK

6.2.3 Call Waiting The +CCWA controls the call waiting supplementary service. Activation, deactivation, and status query are supported. When the network is interrogated the command is aborted.

Table 6-23 Call Waiting

Parameters Definition Syntax AT+CCWA=[<n>][,<mode>[,<class>]]] Parameters <n> = 0 or 1

0 = disable presentation of unsolicited result code. (Default) 1 = enable presentation of unsolicited result code

<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 refers only to some

bearer services) 4 = fax 7 = all classes. (Default)

Example AT+CCWA=1,1,1 AT+CCWA=1,2

Possible Response OK <status> = 0 or 1

0 = not active 1 = enable

6.2.4 Supported Call Waiting Values The +CCWA=? returns a list of the call waiting values that the CDMA Data Module supports.

Table 6-24 Supported Call Waiting Values

Parameters Definition Syntax AT+CCWA=?


20

Parameters None Example AT+CCWA=? Possible Response +CCWA: <n>

OK

6.2.5 Current Call Waiting Status The +CCWA? indicates the current call waiting, if it is enabled or disabled.

Table 6-25 Current Call Waiting Status

Parameters Definition Syntax AT+CCWA? Parameters None Example AT+CCWA? Possible Response +CCWA: <n>

OK

6.2.6 Set Phone Functionality The +CFUN selects the level of functionality in the MS.

Table 6-26 Set Phone Functionality

Parameters Definition Syntax AT+CFUN=<L> Parameters <L>

the ID is set, as described in the examples. Example When the application stops the module such as power off, or if the application forces the

module to execute an International Mobile Subscriber Identity (IMSI) DETACH procedure, it sends: AT+CFUN=0 This command executes an IMSI DETACH and makes a backup of some internal parameters in the SIM and the Electronically-Erasable Programmable Read-Only Memory (EEPROM.) then no access to the SIM card is possible. If the mobile is not powered off after this command, it receives another command to re-start the GSM process. If the mobile is turned off after this command, the power-on automatically executes the start of the GSM process. When the application re-starts the module, after having done an AT+CFUN=0 command, and without cutting the power supply, it must send: AT+CFUN=1 This command starts the GSM stack and GSM functionality, and a complete software reset is done. All parameters are reset to their previous E2P values 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 are not written. That is, the SIM task did not have enough time to write the entries in SIM card. The OK response is sent at the last defined baud rate defined by +IPR command. With autobauding, the response is at a different baud rate, it is recommended to save the defined baud rate with AT&W before directly sending the AT+CFUN=1 command.

Possible Response OK Note: This command has no effect on the CDMA Data Module.


21

6.2.7 Supported Phone Functionalities The +CFUN=? returns a list of the phone functionalities that the CDMA Data Module supports.

Table 6-27 Supported Phone Functionalities

Parameters Definition Syntax AT+CFUN=? Parameters None Example AT+CFUN=? Possible Response +CFUN: (0-1)

OK

6.2.8 Current Phone Functionality The +CFUN? reports the CDMA Data Module’s current phone functionality.

Table 6-28 Current Phone Functionality

Parameters Definition Syntax AT+CFUN? Parameters None Example AT+CFUN? Possible Response +CFUN: 1

OK

6.2.9 Call Hold The +CHLD allows the control for the following call-related services:

A call is temporarily disconnected from the ME, but the network retains the connection. Multiparty conversation, such as conference calls. The served subscriber has two calls, such as, one held, and the other either active or alerting, connects to the other. Parties and release of the served subscriber’s own connection.

Calls are put on hold, recovered, released, added to conversation, and transferred similarly as defined in 3GPP TS 22.030 [19]. This is based on the GSM/Universal Mobile Telecommunications System™ (UMTS™) supplementary services HOLD (Call Hold; refer 3GPP TS 22.083 [5] clause 2). MultiParty (MPTY) ; refer 3GPP TS 22.084 [22]) and Explicit Call Transfer (ECT) ; 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 Transfer are only applicable to teleservice 11. It is recommended, although optional, that the test command return a list of operations, which are supported. The call number required by some operations is denoted by “x”, as an example, +CHLD: (0,1,1x,2,2x,3).

Table 6-29 Call Hold

Parameters Definition Syntax AT+CHLD=<n> Parameters <n> = 0, 1, 1x, 2, 2x, or 3

0 = terminate all held calls or User Determined User Busy (UDUB) for a waiting call


22

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 = 1-7) on hold. 3 = add the held call to the active calls.

Example AT+CHLD=1 Possible Response OK Note: The parameter <n> has no effect on the CDMA Data Module.

6.2.10 Supported Call Hold Parameters The +CHLD=? lists the supported call hold parameters

Table 6-30 Supported Call Hold Parameters

Parameters Definition Syntax AT+CHLD=? Parameters None Example AT+CHLD=? Possible Response +CHLD: (0,1,1x,2,2x,3)

OK

6.2.11 Request International Mobile Subscriber Identity The +CIMI reads and identifies the IMSI of the attached SIM card.

Table 6-31 Request International Mobile Subscriber Identity

Parameters Definition Syntax AT+CIMI Parameters <IMSI> = International Mobile Subscriber Identity (string without double quotes) Example AT+CIMI Possible Response +CIMI: 00123456789

OK If error is related to ME functionality: +CME ERROR: <err>

6.2.12 Supported International Mobile Subscriber Identity The +CIMI=? reports the IMSI.

Table 6-32 Supported International Mobile Subscriber Identity

Parameters Definition Syntax AT+CIMI=? Parameters None Example AT+CIMI=?


23


6.2.13 Keypad Control The +CKPD provides keypad control. When you send this command the following occurs:

If a call is in progress, it decreases or increases the audio volume. If no call is in progress, it decreases or increases the ringer volume.

Table 6-33 Keypad Control

Parameters Definition Syntax AT+CKPD=[<n>][<E/e>][<H/h>][<S/s>][<Y/y>] Parameters <n> = string of dialing digits (0-9,#,*)

<E/e> = hang up current call (AT+CHUP) <H/h> = <H>: headset mode, <h>: handset mode <S/s> = send either the last-number dialed or the number stored in the CKPD buffer <Y/y> = clear the CKPD buffer

Example AT+CKPD="1234s" OR ATD1234; When call is connected AT+CKPD="5678" <any number string> sends the DTMF digits 5, 6, 7, 8; the tone is heard for 5; pause then the tone for 6; pause and the tone for 7; pause and the tone for 8. The command is returned with OK.

Possible Response OK If error is related to ME functionality: +CME ERROR: <err>

6.2.14 Supported Keypad Control Values +CKPD=? reports the set of characters that are supported .

Table 6-34 Supported Keypad Control Values

Parameters Definition Syntax AT+CKPD=? Parameters None Example AT+CKPD=? Possible Response +CKPD: "#,*,0-9,E/e,H/h,S/s,Y/y"

OK

6.2.15 List Current Calls The +CLCC 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.

Table 6-35 List Current Calls

Parameters Definition Syntax AT+CLCC


24

Parameters None Example AT+CLCC Possible Response [+CLCC:<id1>,<dir>,<stat>,<mode>,<mpty>[,<number>,<type>[,<alpha>]][<lf>

+CLCC:<id2>,<dir>,<stat>,<mode>,<mpty>[,<number>,<type>[,<alpha>]][...]]] OK <idx> is the integer type; call identification number as described in GSM 02.30[19]

Subclause 4.5.5.1; this number is 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. 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>

Note: This command is not fully supported on the CDMA Data Module.

6.2.16 Current Calls Test Command The +CLCC=? is a test command for the current calls.

Table 6-36 Current Calls Test Command

Parameters Definition Syntax AT+CLCC=? Parameters None Example AT+CLCC=? Possible Response OK

6.2.17 Facility Lock The +CLCK locks, unlocks, or interrogates an ME or network facility <fac>. A password is normally required. When


25

querying the status of a network service (<mode>=2) the response line for “not-active” case (<status>=0) is returned only if service is not active for any <class>. It is possible to abort the command when network facilities are set or interrogated.

Table 6-37 Facility Lock

Parameters Definition Syntax AT+CLCK=<fac>, <mode> [,<passwd>[,<class>]] Parameters <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 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, for example, AT+CLCK="AO",1,"xxxx"

Example AT+CLCK=AO1,1234 Possible Response If <mode>=0 or 1, and command is successful:

OK If <mode>=2, and command is successful: +CLCK: <status>[,<class1>[<lf> +CLCK: <status>, class2....]] OK If error is related to ME functionality: +CME ERROR: <err> <status> = 0, 1, or 2

0 = off. 1 = on. 2 = query status.



26

6.2.18 Supported Facility Lock Modes The +CLCK=? lists the supported network facilities.

Table 6-38 Supported Facility Lock Modes

Parameters Definition Syntax AT+CLCK=? Parameters None Example AT+CLCK=? Possible Response +CLCK: ("AO","OI","OX","AI","IR","AB","AG","AC","SC","FD","PN")

OK

6.2.19 Calling Line Identification Presentation The +CLIP 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.

Table 6-39 Calling Line Identification Presentation

Parameters Definition Syntax AT+CLIP=<n>,<m> Parameters <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 AT+CLIP 1,1 Possible Response 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 at a mobile terminating call. +CLIP: <number>, <type> There are four different cases for +CLIP: +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.

6.2.20 Supported Calling Line Identification Presentation Values The +CLIP =? lists the supported unsolicited result codes.


27

Table 6-40 Supported Calling Line Identification Presentation Values

Parameters Definition Syntax AT+CLIP=? Parameters None Example AT+CLIP=? Possible Response +CLIP: (list of supported <n>s)

OK

6.2.21 Current Calling Line Identification Presentation Status The +CLIP? reports the CDMA Data Module’s unsolicited result codes.

Table 6-41 Current Calling Line Identification Presentation Status

Parameters Definition Syntax AT+CLIP? Parameters None Example AT+CLIP? Possible Response +CLIP: <n>, <m>


6.2.22 Calling Line Identification Restriction The +CLIR 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 is revoked by using the opposite command.

Table 6-42 Calling Line Identification Restriction

Parameters Definition Syntax AT+CLIR=[<n>] Parameters <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, for example, no network. 3 = CLIR temporary mode presentation restricted. 4 = CLIR temporary mode presentation allowed.

Example AT+CLIR=[<n>] Possible Response OK Note: This command has no effect on the CDMA Data Module.


28

6.2.23 Supported Calling Line Identification Restriction Values The +CLIR=? lists the supported calling line identification restriction.

Table 6-43 Supported Calling Line Identification Restriction Values

Parameters Definition Syntax AT+CLIR=? Parameters None Example AT+CLIR=? Possible Response +CLIR: (list of supported <n>s)

OK

6.2.24 Current Calling Line Identification Restriction Status The +CLIR? reports the current calling line identification restriction for the CDMA Data Module.

Table 6-44 Current Calling Line Identification Restriction Status

Parameters Definition Syntax AT+CLIR? Parameters None Example AT+CLIR? Possible Response +CLIR: <n>, <m>


6.2.25 Loudspeaker Volume Level The +CLVL selects the volume of the internal loudspeaker of the ME.

Table 6-45 Loudspeaker Volume Level

Parameters Definition Syntax AT+CLVL=<level> Parameters <level>

integer-type value with manufacturer-specific range (smallest value represents the lowest sound level).

Example AT+CLVL=8 Possible Response OK

+CME ERROR: <err>

6.2.26 Supported Loudspeaker Volume Levels The +CLVL=? lists, as compound values, the loudspeaker volume level that the CDMA Data Module supports.

Table 6-46 Supported Loudspeaker Volume Levels

Parameters Definition


29

Syntax AT+CLVL=? Parameters None Example AT+CLVL=? Possible Response +CLVL: (0-8)

OK +CME ERROR: <err>

6.2.27 Current Loudspeaker Volume Level The +CLVL? reports the current loudspeaker volume level.

Table 6-47 Current Loudspeaker Volume Level

Parameters Definition Syntax AT+CLVL? Parameters None Example AT+CLVL? Possible Response +CLVL: <level>


6.2.28 Mobile Equipment Error Code The +CMEE disables or enables the use of result code +CME ERROR: <err> as an indication of an error relating to ME functionality.

Table 6-48 Mobile Equipment Error Code

Parameters Definition Syntax AT+CMEE=<n> Parameters <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 6-

51. 2 = enable +CME ERROR: <err> result code and use verbose <err> values, see Table 6-

51. Example AT+CMEE=2 Possible Response 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.

6.2.29 Supported Mobile Equipment Error Code Values +CMEE=? reports the supported values for Mobile Equipment Error Code.


30

Table 6-49 Supported Mobile Equipment Error Code Values

Parameters Definition Syntax AT+CMEE=? Parameters None Example AT+CMEE=? Possible Response +CMEE: (list of supported <n>s)

OK

6.2.30 Current Mobile Equipment Error Code Status The +CMEE? returns values supported by the TA as a compound value.

Table 6-50 Current Mobile Equipment Error Code Status

Parameters Definition Syntax AT+CMEE? Parameters None Example AT+CMEE? Possible Response +CMEE: (<n>)

OK

6.2.31 General Errors General errors are listed in Table 6-51.

Table 6-51 General Errors

Numeric Text 0 Phone failure 1 No connection to phone 2 Phone-adapter link reserved 3 Operation not allowed 4 Operation not supported 5 PH-SIM P IN required 6 PH-FSIM P IN required 7 PH-FSIM PUK required 10 SIM not inserted 11 SIM PIN required 12 SIM PUK required 13 SIM failure 14 SIM busy 15 SIM wrong 16 Incorrect password 17 SIM PIN2 required 18 SIM PUK2 required 20 Memory full 21 Invalid index


31

22 Not found 23 Memory failure 24 Text string too long 25 Invalid characters in text string 26 Dial string too long 27 Invalid characters in dial string 30 No network service 31 Network timeout 32 Network not allowed - emergency calls only 40 Network personalization PIN required 41 Network personalization PUK required 42 Network subset personalization PIN required 43 Network subset personalization PUK required 44 Service provider personalization PIN required 45 Service provider personalization PUK required 46 Corporate personalization PIN required 47 Corporate personalization PUK required 100 Unknown

6.2.32 Delete Message The +CMGD deletes a message from preferred message storage <mem1> location <index>.

Table 6-52 Delete Message

Parameters Definition Syntax AT+CMGD=<index>[,<delflag>] Parameters <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 message storage, including unread messages. Example AT+CMGD=3 Possible Response OK


6.2.33 Delete Message Test Command The +CMGD=? shows the valid memory locations.


32

Table 6-53 Delete Message Test Command

Parameters Definition Syntax AT+CMGD=? Parameters None Example AT+CMGD=? Possible Response +CMGD: (list of supported <index>s)[,(list of supported <delflag>s)]

OK

6.2.34 Message Format The +CMGF sets a parameter that specifies the input and output format of messages that are used.

Table 6-54 Message Format

Parameters Definition Syntax AT+CMGF =[<mode>] Parameters <mode> = 0 or 1

0 = PDU mode. 1 = text mode. (Default)

Example AT+CMGF=1 Possible Response OK

6.2.35 Supported Message Format Modes The +CMGF=? lists supported report message format modes.

Table 6-55 Supported Message Format Modes

Parameters Definition Syntax AT+CMGF=? Parameters None Example AT+CMGF=? Possible Response +CMGF: (list of supported <mode>s)

OK

6.2.36 Current Message Format Mode The +CMGF? command reports the current message format mode.

Table 6-56 Current Message Format Mode

Parameters Definition Syntax AT+CMGF? Parameters None Example AT+CMGF? Possible Response +CMGF: <mode>

OK


33

6.2.37 Read Message The +CMGR 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.”

Table 6-57 Read Message

Parameters Definition Syntax AT+CMGR=<index> Parameters <index>

integer type; value in the range of location numbers supported by the associated memory <stat> = 0, 1, 2, or 3

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, that is, 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 applicable to SMs).

<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-User-Data 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-Data-Header-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-Data-Header-Indication is set: ME/TA converts each 8-bit octet into Hexadecimal numbers containing two IRA characters (for example, 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: 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, for example, 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 time-string format: yy/MM/dd,hh:mm:ss±zz 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


34

<fo> Depends on the command or result code: first octet of GSM 03.40 SMS-DELIVER, SMS-SUBMIT (Default is 17), SMS-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, that is, 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 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, for example, 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 TP-Recipient-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 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 <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> 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 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 Type-of-Address octet in integer format (Default see <toda>).

<tora> GSM 04.11 TP-Recipient-Address Type-of-Address octet in integer format (Default refer<toda>).

<tosca>


35

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 time-string format (see <dt>).

Example AT+CMGR=1 Possible Response If text mode (+CMGF=1) and command is successful:

For SMS-DELIVER: +CMGR: <stat>,<oa>,[<alpha>],<scts>[,<tooa>,<fo>,<pid>,<dcs>,<sca>,<tosca>,<length>] <lf><data> OK For SMS-SUBMIT: +CMGR: <stat>,<da>,[<alpha>][,<toda>,<fo>,<pid>,<dcs>,[<vp>],<sca>,<tosca>,<length>] <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><lf><cdata>] OK For CBM storage: +CMGR: <stat>,<sn>,<mid>,<dcs>,<page>,<pages><lf><data> OK If PDU mode (+CMGF=0) and command is successful: +CMGR: <stat>,[<alpha>],<length><lf><pdu> OK If error is related to ME functionality: +CME ERROR: <err>

6.2.38 Read Message Test Command The +CMGR=? is a test command for the read message.

Table 6-58 Read Message Test Command

Parameters Definition Syntax AT+CMGR=? Parameters None Example AT+CMGR=? Possible Response OK

6.2.39 Send Message The +CMGS transmits a SMS message from a TE to the network (SMS-SUBMIT). Message reference value <mr> is returned to the TE on successful message delivery. Value is used to identify a message upon an 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


36

input to abort message send operation. No message is sent, although display returns OK.

Note: Sending e-mails via SMS: Some providers do not recognize @ symbol. Possible alternative “!” for “@”.

Table 6-59 Send Message

Parameters Definition Syntax If text mode:

(+CMGF=1):+CMGS="<da>"[,<toda>] text is entered <ctrl-Z/ESC>

If PDU mode: (+CMGF=0):+CMGS=<length> PDU is given: <ctrl-Z/ESC> ESC aborts message

Parameters <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>.


<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, that is, 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 time-string format: yy/MM/dd,hh:mm:ss±zz, 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.

<ackpdu> 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 is 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, for example, 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 AT+CMGS="+3314629800" > Note: The > line indicate that text is entered here.

Possible Response 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:


37

+CME ERROR: <err>

6.2.40 Send Message Test Command The +CMGS=? is a test command for the send message.

Table 6-60 Send Message Test Command

Parameters Definition Syntax AT+CMGS=? Parameters None Example AT+CMGS=? Possible Response OK

6.2.41 Write Message The +CMGW transmits SMS message (either SMS-DELIVER or SMS-SUBMIT) from TE to memory storage <mem2>. Memory location <index> of the stored message is returned. Message status is set to ’stored unsent,’ unless otherwise given in <stat>.

Note: SMS-COMMANDs and SMS-STATUS-REPORTs cannot be stored in text mode.

Table 6-61 Write Message

Parameters Definition Syntax If text mode: (+CMGF=1):

+CMGW[=<oa/da>[,<tooa/toda>,stat>]]] text is entered <ctrl-Z/ESC> <ESC> quits without sending

If PDU mode: (+CMGF=0):+CMGW=<length>[,stat] PDU is given <ctrl-Z/ESC>

Parameters <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>.

<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>.

<tooa> GSM 04.11 TP-Originating-Address Type-of-Address octet in integer format (Default see <toda>).


<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, that is, the RP layer SMSC address octets are not counted in


38

the length. <stat> = 0, 1, 2, or 3

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.

<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, for example, 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. <index> Index of message in selected storage <mem2>.

Example AT+CMGW="+33146290800" > Note: The > line indicates that text is entered here.

Possible Response If writing is successful: +CMGW: <index> OK If error is related to ME functionality: +CME ERROR: <err> CTRL-Z sends/writes message, returns OK. ESC aborts input, message NOT sent/written. Returns OK

Note: Sending e-mails via SMS: Some providers do not recognize @ symbol. Possible alternative"!" for "@".

6.2.42 Write Message Test Command The +CMGW=? is a test command for the write message.

Table 6-62 Write Message Test Command

Parameters Definition Syntax AT+CMGW=? Parameters None Example AT+CMGW=? Possible Response OK

6.2.43 Mute Control The +CMUT enables or disables the uplink voice muting during a voice call.

Table 6-63 Mute Control

Parameters Definition Syntax AT+CMUT=<n> Parameters <n> = 0 or 1

0 = mute off. (Default) 1 = mute on.

Example AT+CMUT=1 Possible Response OK

+CME ERROR: <err>


39

6.2.44 Supported Mute Control Values The +CMUT=? reports the supported mute control values.

Table 6-64 Supported Mute Control Values

Parameters Definition Syntax AT+CMUT=? Parameters None Example AT+CMUT=? Possible Response +CMUT: (list of supported <n>s)

OK

6.2.45 Current Setting for Mute Control Status The +CMUT? reports the current setting for mute control.

Table 6-65 Current Settings for Mute Control Status

Parameters Definition Syntax AT+CMUT? Parameters None Example AT+CMUT? Possible Response +CMUT: <n>


6.2.46 Multiplexing Mode The +CMUX enable/disable the 3GPP TS 27.010 [45] multiplexing protocol control channel. This command sets parameters for the Control Channel. If the parameters are left out, the default value is used. It is recommended that the MT/TA/TE autobaud to the +CMUX command up to and including an interface speed of 9600 bits/s. The OK or +CME ERROR: <err> response is returned at the speed of the +CMUX command prior to entering <mode>. When the multiplexer control channel is released the MT/TA/TE should assume an interface rate of up to and including 9600 bits/s for auto bauding purposes irrespective of any previous higher speed having been selected.

Table 6-66 Multiplexing Mode

Parameters Definition Syntax AT+CMUX=<mode>[,<subset>[,<port_speed>[,<N1>[,<T1>[,<N2>[,<T2>

[,<T3>[,<k>]]]]]]]] Parameters <mode> (multiplexer Transparency Mechanism)

0 = Basic option 1 = Advanced option

<subset> This parameter defines the way in which the multiplexer control channel is set up. A virtual channel may subsequently be set up differently but in the absence of any negotiation for the settings of a virtual channel, the virtual channel shall be set up according to the control channel <subset> setting. 0 = UIH frames used only (Default) 1 = UI frames used only


40

2 = I frames used only <port_speed> (transmission rate)

19600 bit/s 219200 bit/s 338400 bit/s 457600 bit/s 5115200 bit/s 6230400 bits/s

<N1> (maximum frame size) 1- 32768, where 31 is default (64 if advanced option is used)

<T1> (acknowledgement timer in units of ten milliseconds) 1-255, where 10 is default (100 ms)

<N2> (maximum number of re-transmissions) 0-100, where 3 is default

<T2> (response timer for the multiplexer control channel in units of ten milliseconds) 2-255, where 30 is default (300 ms) Note: <T2> must be longer than < T1>

<T3> (wake up response timer in seconds) 1-255, where 10 is default

<k> (window size, for Advanced operation with Error Recovery options) 1-7, where 2 is default

Example AT+CMUX=1 Possible Response OK


Note: This command has no effect on the CDMA Data Module.

6.2.47 Supported Multiplexing Modes The +CMUX=? reads the supported multiplex mode supported values for mode, subset, port_speed, N1, T1, N2, T2, T3, and k.

Table 6-67 Supported Multiplexing Modes

Parameters Definition Syntax AT+CMUX=? Parameters None Example AT+CMUX=? Possible Response +CMUX: (list of supported <mode>s),(list of supported <subset>s),

(list of supported<port_speed>s),(list of supported <N1>s),(list of supported <T1>s), (list of supported <N2>s),(listof supported <T2>s),(list of supported <T3>s), (list of supported <k>s) OK

6.2.48 Current Multiplexing Mode The +CMUX? returns the current multiplex mode, subset, port_speed, N1, T1, N2, T2, T3, and k.

Table 6-68 Current Multiplexing Mode

Parameters Definition Syntax AT+CMUX? Parameters None


41

Example AT+CMUX? Possible Response +CMUX: <mode>,[<subset>],<port_speed>,<N1>,<T1>, <N2>,<T2>,<T3>[,<k>]


6.2.49 New Message Indication The +CNMI determines how the receipt of new messages from the network is indicated to the TE when TE is active, for example, DTR signal is ON. If TE is inactive, for example, DTR signal is OFF, message receiving is completed as specified in GSM 03.38.

Note: The rules <mt>=2 and <mt>=3 for storing received SM are possible only if phase 2+ compatibility is activated with +CSMS=1.

Table 6-69 New Message Indication

Parameters Definition Syntax AT+CNMI =[<mode>[,<mt> [,<bm>[,<ds>[,<bfr>]]]]] Parameters <mode> = 0, 1, 2, or 3

0 = buffer unsolicited result codes in the TA. If TA result code buffer is full, indications are buffered in some other place or the oldest indications are 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, for example, 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, for example, 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 in-band 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. Note: 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: Note: 2 SMS-DELIVERs routed directly to TE are NOT supported. 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> 2 = new CBMs are routed directly to the TE using unsolicited result code:

+CBM:<length><lf><pdu> (PDU mode enabled) or +CBM:<sn>,<mid>,<dcs>,<page>,<pages><lf><data> (text mode enabled) If ME supports data coding groups that define special routing also for messages other than class 3, for example, SIM-specific messages, ME chooses not to route messages of such data coding schemes into TE (indication of a stored CBM are given as


42

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.

<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><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 defined within this command is cleared when

<mode> 1-3 is entered. Unsolicited result code: +CMTI: <mem>,<index> Indication that a new message has been received Parameters are set to provide supported values. +CMT: <length><lf><pdu> Short message is output directly +CBM: <length><lf><pdu> Cell broadcast message is output directly

Example AT+CNMI=2,1,0,0,0 Possible Response OK


6.2.50 Supported New Message Indication Values The +CNMI=? lists supported message indication values.

Table 6-70 Supported Message Indication Values

Parameters Definition Syntax AT+CNMI=? Parameters None Example AT+CNMI=? Possible Response +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

6.2.51 Current New Message Indication Status The +CNMI? reports the current message indication status.

Table 6-71 Current Message Indication Status

Parameters Definition Syntax AT+CNMI? Parameters None Example AT+CNMI?


43

Possible Response +CNMI: <mode>,<mt>,<bm>,<ds>,<bfr> OK For an explanation of these parameters, see the +CNMI command, Table 6-68.

6.2.52 Subscriber Number The +CNUM returns the MSISDN(s) related to the subscriber. This information is stored in the SIM or in the ME. If the subscriber has different MSISDN for different services, each MSISDN is returned in a separate line.

Table 6-72 Subscriber Number

Parameters Definition Syntax AT+CNUM Parameters None Example AT+CNUM Possible Response +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> <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

6.2.53 Subscriber Number Test Command The +CNUM=? is a test command for the subscriber number.

Table 6-73 Subscriber Number Test Command

Parameters Definition Syntax AT+CNUM=? Parameters None Example AT+CNUM=? Possible Response OK


44

6.2.54 Connected Line Identification Presentation The +COLP enables or disables the presentation of the COL (connected line) at the TE at a mobile originating call. It has 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.

Table 6-74 Connected Line Identification Presentation

Parameters Definition Syntax AT+COLP=[<n>] 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, for example, no network

Example AT+COLP=1 Possible Response OK Note: This command has no effect on the CDMA Data Module.

6.2.55 Supported Line Identification Presentation Values The +COLP =? lists the supported line identification presentation values.

Table 6-75 Supported Line Identification Presentation Values

Parameters Definition Syntax AT+COLP=? Parameters None Example AT+COLP=? Possible Response +COLP: (list of supported <n>s)

OK

6.2.56 Current Line Identification Presentation Status The +COLP? shows the current line identification presentation supported by the CDMA Data Module.

Table 6-76 Current Line Identification Presentation Status

Parameters Definition Syntax AT+COLP? Parameters None Example AT+COLP? Possible Response +COLP: <n>,<m>

OK


45

6.2.57 Network Operator Selection The +COPS forces an attempt to select and register the GSM network operator. If the selected operator is not available, no other operator is selected. The selected operator name format applies to further read commands (+COPS?).

Table 6-77 Network Operator Selection

Parameters Definition Syntax AT+COPS=<mode>[,<format> [,<oper>]] Parameters <mode> = 0, 1, 3, or 4

0 = automatic (<oper> field is ignored). (Default) 1 = manual (<oper> field is 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 is present); if manual selection fails, automatic mode (<mode>=0) is entered.

<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 AT+COPS=1,2,20810 since if <mode> is set to 0, the <oper> field 20810 is ignored.



6.2.58 Supported Network Operators The +COPS=? returns a list of quadruplets, each representing an operator present in the network. The formats are unavailable and are empty fields. The list of operators must be in the following order:

home network networks referenced in SIM other networks

Table 6-78 Supported Network Operators

Parameters Definition Syntax AT+COPS=? Parameters None Example AT+COPS=? Possible Response +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>


46

6.2.59 Current Network Operator The +COPS? returns the current mode and the currently selected operator. If no operator is selected, <format> and <oper> are omitted.

Table 6-79 Current Network Operator

Parameters Definition Syntax AT+COPS? Parameters None Example AT+COPS? Possible Response +COPS: <mode>[, <format>, <oper>]

OK

6.2.60 Phone Activity Status The +CPAS returns the activity status of the ME.

Table 6-80 Phone Activity Status

Parameters Definition Syntax AT+CPAS Parameters None Example AT+CPAS Possible Response +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.

6.2.61 Supported Phone Activity Status The +CPAS=? =? lists the supported phone activity status.

Table 6-81 Supported Phone Activity Status

Parameters Definition Syntax AT+CPAS=? Parameters None Example AT+CPAS=? Possible Response +CPAS: (list of supported <pas>s)

OK

6.2.62 Delete Phonebook Entry The +CPBD deletes an entry from the phonebook.


47

Table 6-82 Delete Phonebook Entry

Parameters Definition Syntax AT+CPBD=<index1>[,<index2>] Parameters <index1>

an integer from 1 to 250 that corresponds to the phonebook entry to delete. <index2>

specifies the ending range of phonebook entries is deleted (in which case <index1> specifies the starting range).

Example AT+CPBD=12 deletes entry 12 in the phonebook. AT+CPBD=1,250 deletes all 250 entries in the phonebook.


6.2.63 Find Phonebook Entry The +CPBF returns phonebook entries (from the current phonebook memory storage selected with the command +CPBS, Table 6-87, with alphanumeric fields that contain <findtext>.

Table 6-83 Find Phonebook Entry

Parameters Definition Syntax AT+CPBF=<findtext> Parameters <findtext>

string type field of maximum length <tlength>; character set as specified by the command +CSCS.

Example AT+CPBF="E" Possible Response [+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)



6.2.64 Find Phonebook Entry Test Command The +CPBF=? returns the maximum lengths of <number> and <text> fields. In case of SIM storage, the lengths are not available.

Table 6-84 Find Phonebook Entry Test Command

Parameters Definition Syntax AT+CPBF=? Parameters None


48

Example AT+CPBF=? Possible Response +CPBF: [<nlength>], [<tlength>]

OK where: <nlength>

integer type value indicating the maximum length of field <number>. <tlength>

integer type value indicating the maximum length of field <text>. If ME is not currently reachable: +CME ERROR: <err> Note: In case of SIM storage, the lengths are not available. If storage does not offer format

information, the format list is empty parenthesis.

6.2.65 Read Phonebook The +CPBR 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.

Table 6-85 Read Phonebook

Parameters Definition Syntax AT+CPBR=<index1>[, <index2>] Parameters <index1>

read from this location number. <index2> read to this location number.

Example AT+CPBR=12,14 Possible Response +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>

6.2.66 Read Phonebook Test Command The +CPBR=? 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 are not available. If storage does not offer format information, the format list is an empty parenthesis.

Table 6-86 Read Phonebook Test Command

Parameters Definition Syntax AT+CPBR=?


49

Parameters None Example AT+CPBR=? Possible Response +CPBR: (list of supported <index>s), <nlength>, <tlength>

OK where: <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>

6.2.67 Phonebook Memory Storage The +CPBS selects the current phonebook memory storage, which is used by other phonebook commands.

Table 6-87 Phonebook Memory Storage

Parameters Definition Syntax AT+CPBS=<storage> Parameters <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 show wildcard characters ("B" or "b") and a sub-address.

LD = SIM last-dialing-phonebook. The last-dialed number cannot be written into the last memory- storage position.

MC = ME missed (unanswered received) call list. +CPBW are 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 are used for deleting). SM = SIM phonebook.

Examples: AT+CPBW=1,"1234b6",,, for "b" any number from 0 to 9 are used. AT+CPBW=2,"011707",,, any number starting with "11707" is accepted.

Example AT+CPBS="SM" Possible Response OK Note: This command is not fully supported on the CDMA Data Module.

6.2.68 Supported Phonebook Memory Storages The +CPBS=? returns supported storages as compound value.

Table 6-88 Supported Phonebook Memory Storages

Parameters Definition Syntax AT+CPBS=? Parameters None Example AT+CPBS=? Possible Response +CPBS: (list of supported <storage>s)

OK


50

6.2.69 Current Phonebook Memory Storage The +CPBS? returns the currently selected memory and when supported by manufacturer, number of used locations and total number of locations in the memory.

Table 6-89 Current Phonebook Memory Storage

Parameters Definition Syntax AT+CPBS? Parameters None Example AT+CPBS? Possible Response +CPBS: <storage>

OK

6.2.70 Write Phonebook Entry The +CPBW writes a phonebook entry in location number <index> in the current phonebook memory storage selected with +CPBS, see Table 6-87. 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> shows letters, which are stored as capitals.

Note: PIN2 is necessary for writing in FD phonebook.

Table 6-90 Write Phonebook Entry

Parameters Definition Syntax AT+CPBW=[<index>],[<number>,[<type>, [<text>]]] Parameters <nlength>

maximum length of phone number. <tlength>

maximum length of text for number. <index>

location number. <number> phone number. <type>

type of number, for example, 145, when dialing string includes international access code character +; otherwise, 129.

<text> text for phone number.

The following characters in <text> are entered via the escape sequence: GSM characterSeq. NoteSeq. (hex) \\5C5C 35 43(backslash) "\225C 32 32(string delimiter) BSP\085C 30 38(backspace) NULL\005C 30 30(GSM null) 0 (GSM null) cause problems on application level when using the function (strlen) and, therefore, are represented by an escape sequence when necessary.

Example AT+CPBW=2,"1111",145


51


6.2.71 Write Phonebook Entry Test Command The +CPBW=? 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 are not available in case of SIM storage. If storage does not offer format information, the format list is an empty parenthesis.

Table 6-91 Write Phonebook Entry Test Command

Parameters Definition Syntax AT+CPBW=? Parameters None Example AT+CPBW=? Possible Response +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>

6.2.72 Enter PIN The +CPIN stores a password that is necessary before it is operated (SIM PIN, SIM PUK, PH-SIM PIN, etc.). If the PIN is 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.

Table 6-92 Enter PIN

Parameters Definition Syntax AT+CPIN=<pin> [,<new pin>] Parameters <pin>

Password (string type) entered in double quotes, for example, AT+CPIN="9515" <new pin>

if the PIN required is SIM PUK or SIM PUK2: new password Example AT+CPIN="12345678" Possible Response OK



52

6.2.73 Enter PIN Test Command The +CPIN=? is a test command.

Table 6-93 Enter PIN Test Command

Parameters Definition Syntax AT+CPIN=? Parameters None Example AT+CPIN=? Possible Response OK

6.2.74 Current PIN Status The +CPIN? returns an alphanumeric string indicating whether a password is required.

Table 6-94 Current PIN Status

Parameters Definition Syntax AT+CPIN? Parameters None Example AT+CPIN? Possible Response +CPIN: <code>


6.2.75 Set Preferred Message Storage The +CPMS selects memory storages <mem1>, <mem2>, and <mem3> used for reading and writing.

Table 6-95 Set Preferred Message Storage

Parameters Definition Syntax AT+CPMS=<mem1>[,<mem2>[,<mem3>]] Parameters <mem1>

Messages are read and deleted from this memory storage. SM = SIM message storage. BM = broadcast message storage.

<mem2> Messages are written and sent to this memory storage. SM = SIM message storage.

<mem3> Received messages are 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 AT+CPMS="BM or SM","SM","SM"


53

Possible Response +CPMS:<used1>,<total1>,<used2>,<total2>,<used3>,<total3> OK If error is related to ME functionality: +CME ERROR:<err>

6.2.76 Supported Message Storages The +CPMS=? shows the supported message storages.

Table 6-96 Supported Message storages

Parameters Definition Syntax AT+CPMS=? Parameters None Example AT+CPMS=? Possible Response +CPMS: (list of supported <mem1>s),(list of supported <mem2>s),

(list of supported <mem3>s) OK

6.2.77 Current Message Storage The +CPMS? reports the current message storage.

Table 6-97 Current Message Storage

Parameters Definition Syntax AT+CPMS? Parameters None Example AT+CPMS? Possible Response +CPMS:<mem1>,<used1>,<total1>,<mem2>,<used2>,<total2>,

<mem3>,<used3>,<total3> OK If error is related to ME functionality: +CME ERROR: <err>

6.2.78 Change Password The +CPWD sets a new password for the facility lock function.

Table 6-98 Change Password

Parameters Definition Syntax AT+CPWD=<fac>,<oldpwd>],<newpwd> Parameters <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.


54

PN = network lock. <oldpwd>

Password specified for the facility from the user interface or with command, entered in double quotes. If an old password has not been set, <oldpwd> is not entered. If <fac> = SC, then PIN If <fac> = AO...AC (Barring), then network password If <fac> = P2, then PIN2 Note: A password that is already set, depending on the provider. Please check with your provider.

<newpwd> new password, entered in double quotes.

Example AT+CPWD="SC","1234","5678" Possible Response OK


Note: This command is not fully supported on the CDMA Data Mudule.

6.2.79 Supported Password The +CPWD=? returns a list of pairs that present the available facilities and the maximum length of their password.

Table 6-99 Supported Password

Parameters Definition Syntax AT+CPWD=? Parameters None Example AT+CPWD=? Possible Response +CPWD: ("AB",4),("SC",8),("FD",8), ("P2",8),("PN",8)

OK

6.2.80 Network Registration The +CREG 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.

Table 6-100 Network Registration

Parameters Definition Syntax AT+CREG:<n>,<stat>,[<lac>,<ci>] Parameters <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. 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>


55

String type; two-byte location area code in Hexadecimal format, for example, 00C3 equals 193 in decimal)

<ci> String type; two-byte cell ID in Hexadecimal format.

Example AT+CREG=<n> Where: <n> = 0, 1, or 2

Possible Response 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>]


6.2.81 Supported Network Registration Values The +CREG=? lists the supported network registrations.

Table 6-101 Supported Network Registration Values

Parameters Definition Syntax AT+CREG=? Parameters None Example AT+CREG=? Possible Response +CREG: (list of supported <n>s)

OK

6.2.82 Current Network Registration Status The +CREG=? 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.

Table 6-102 Current Network Registration Status

Parameters Definition Syntax AT+CREG? Parameters None Example AT+CREG? Possible Response +CREG: <n>,<stat>,[<lac>,<ci>]

OK

6.2.83 Set Service Center Address The +CSCA updates the SMSC address through which mobile-originated SMs are transmitted.

In text mode, send and write commands use this setting. 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.


56

Table 6-103 Set Service Center Address

Parameters Definition Syntax AT+CSCA=<sca>[,<tosca>] Parameters <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>) Note: If the parameter field <tosca> is ignored, national/international call center

numbers are recognized by the leading + in the number. Example AT+CSCA="2943873"

(current address is entered in double quotes) Possible Response The +CSCA command updates the SMSC address through which mobile-originated SMs

are transmitted. In text mode, send and write commands use this setting. 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.


6.2.84 Service Center Address Test Command The +CSCA=? is a test command to set service center address.

Table 6-104 Service Center Address Test Command

Parameters Definition Syntax AT+CSCA=? Parameters None Example AT+CSCA=? Possible Response OK

6.2.85 Current Service Center Address The +CSCA? reports the current service center address setting.

Table 6-105 Current Service Center Address

Parameters Definition Syntax AT+CSCA? Parameters None Example AT+CSCA? Possible Response +CSCA: <sca>,<tosca>

OK


57

6.2.86 Select TE Character Set The +CSCS informs the TA which character set the TE is using. The TA is able to convert character strings correctly between the TE and ME character sets.

Table 6-106 Select TE Character Set

Parameters Definition Syntax AT+CSCS=<chset> Parameters <chset>

One of the following conversion methods, entered in double quotes: HEX = character strings consist of only Hexadecimal numbers from 0x00 to 0xFF. IRA = international reference alphabet (ITU-T T.50). (Default) UCS2 = 16-bit universal multiple-octet coded character set (SIO/IEC10646)

Example AT+CSCS= "UCS2" Possible Response OK

6.2.87 Supported TE Character Sets The +CSCS=? lists the character sets that the CDMA Data Module supports.

Table 6-107 Supported TE Character Sets

Parameters Definition Syntax AT+CSCS=? Parameters None Example AT+CSCS=? Possible Response +CSCS: <list of supported character sets>

OK

6.2.88 Current TE Character Set The +FCSCS? command reports the current character set that the CDMA Data Module is using.

Table 6-108 Current TE Character Set

Parameters Definition Syntax AT+CSCS? Parameters None Example AT+CSCS? Possible Response +CSCS: <chset>

OK

6.2.89 Select Message Service The +CSMS selects the message service.


58

Table 6-109 Select Message Service

Parameters Definition Syntax AT+CSMS=<service> Parameters <service> = 0, 1

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 are supported, for example, 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)

<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 AT+CSMS=1 Possible Response OK

6.2.90 Supported Message Services The +CSMS=? lists the services that the CDMA Data Module supports.

Table 6-110 Supported Message Services

Parameters Definition Syntax AT+CSMS=? Parameters None Example AT+CSMS=? Possible Response +CSMS: (list of supported <service>s)

OK

6.2.91 Current Message Service The +CSMS? reports the current message services.

Table 6-111 Current Message Service

Parameters Definition Syntax AT+CSMS? Parameters None Example AT+CSMS? Possible Response +CSMS: <service>,<mt>,<mo>,<bm>

OK


59

6.2.92 Signal Quality The +CSQ returns the received signal strength indication <rssi> and channel bit error rate <ber> from the ME.

Table 6-112 Signal Quality

Parameters Definition Syntax AT+CSQ Parameters None Example AT+CSQ Possible Response +CSQ: <rssi>, <ber>

OK where: <rssi> is the receive level: 0, 1,2, … ,30, 31, 99

0 = -113 dBm or less 1 = -111 dBm 2 = -109 dBm … 30 = -53 dBm 31 = -51 dBm or greater 99 = not known

<ber> is the bit error rate: 0, … ,7, 99 0…7 = as RXQUAL values in the table in GSM 05.08, Section 8.2.4. 99 = not known

6.2.93 Supported Signal Quality Values The +CSQ=? lists the supported receive levels.

Table 6-113 Supported Signal Quality Values

Parameters Definition Syntax AT+CSQ=? Parameters None Example AT+CSQ=? Possible Response +CSQ: (list of supported <rssi>s), (list of supported <ber>)

OK

6.2.94 DTMF and Tone Generation The +VTS allows the transmission of DTMF tones and arbitrary tones in voice mode. These tones are used (for example) when announcing the start of a recording period.

This is interpreted as a sequence of DTMF tones with duration set by the +VTD command. This has no function at GSM. This is interpreted as a DTMF tone when duration is determined by <duration>.

Table 6-114 DTMF and Tone Generation

Parameters Definition Syntax AT+VTS=<dtmfstring>

AT+VTS=[<tone1>,<tone2>,<duration>] AT+VTS=<dtmf>,<duration>


60

Parameters <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.

Example AT+VTS=”5551212” Possible Response OK


Note: This command is not fully supported in the CDMA Data Module.

6.2.95 Supported DTMF Tones The +VTS=? lists the supported DTMF tones and durations.

Table 6-115 Supported DTMF Tones

Parameters Definition Syntax AT+VTS=? Parameters None Example AT+VTS=? Possible Response +VTS: (list of supported <dtmf>s, (list of supported <duration>s)

OK Note: In GSM, the tone duration value is preset and cannot be altered. Therefore, the <duration> list is not presented.

6.2.96 Sleep Mode The $SMOD enables sleep mode.

Table 6-116 Sleep Mode

Parameters Definition Syntax AT$SMOD=<n> Parameters <n>

0 = LP mode disabled (default) 1 = LP mode enabled with DTR wakeup 2 = LP mode enbaled with auto (keyboard) wakeup

LP mode with DTR wakeup. Entry to LP mode is allowed when DTR transition from On to Off is detected and is disallowed when DTR transition from Off to On is detected.

LP mode with auto wakeup. Entry to LP mode is allowed after $SMOD=2 is entered. Data module remains awake after "AT" is detected until AT command is processed. Re-entry to LP mode is delayed for about 10 seconds after processing an AT command.

Note: At high baud rate, 115200 bps, the user notices a single garbage character with key entries after idle for a while. This is caused by latency in wakeup. Occasionally, when running script on DTE at high baud rate, 115200, an AT command is not executed due to unrecognized character. In this case, the user sets the baud rate at 19200 bps


61

or lower to avoid unnecessary interruptions caused by latency in wakeup or insert AT <lf> before AT+xxx command.

Example AT$SMOD=1 Possible Response OK Note: This command has no effect on the CDMA Data Module.

6.2.97 Supported Sleep Mode Values $SMOD=? reports the supported values for sleep mode.

Table 6-117 Supported Sleep Mode Values

Parameters Definition Syntax AT$SMOD=? Parameters None Example AT$SMOD=? Possible Response $SMOD: (0,1)

OK

6.2.98 Current Sleep Mode Status $SMOD? reports the current setting for the sleep mode.

Table 6-118 Current Sleep Mode Status

Parameters Definition Syntax AT$SMOD? Parameters None Example AT$SMOD? Possible Response $SMOD:<n>

OK

6.2.99 Auto Power Off The $LCT makes the module power off after 15minutes

Table 6-119 Auto Power Off

Parameters Definition Syntax AT$LCT Parameters None Example AT$LCT Possible Response OK


62

6.2.100 SW Version The $LCV reports the current sw version

Table 6-120 SW Version

Parameters Definition Syntax AT$LCV Parameters None Example AT$LCV Possible Response $LCV: “M100CM04”

OK

6.2.101 Audio Path The $LCHFREE sets the audio path for the Handfree or Speaker Phone

Table 6-121 Audio Path

Parameters Definition Syntax AT$LCHFREE=<n> Parameters <n>

0 = Ear1 and Mic1 (default) 1 = Aux and Mic1

Example AT$LCHFREE=0 Possible Response OK

6.2.102 Supported Audio Path Values $LCHFREE=? reports the supported values for audio path

Table 6-122 Supported Audio Path

Parameters Definition Syntax AT$LCHFREE=? Parameters None Example AT$LCHFREE=? Possible Response $LCHFREE: (0-1)

OK

6.2.103 Current Audio Path Setting $LCHFREE? reports the current setting for the sleep mode.

Table 6-123 Current Audio Path Setting

Parameters Definition Syntax AT$LCHFREE? Parameters None


63

Example AT$LCHFREE? Possible Response $LCHFREE:<n>

OK

6.2.104 Audio Loopback Test The $LTST enables audio loopback test.

Table 6-124 Audio Loopback Test

Parameters Definition Syntax AT$LTST=<n> Parameters <n>

0 = End of audio loopback test (default) 1 = Mic1 and Ear1 audio loopback test 2 = Mic1 and Aux audio loopback test

Example AT$LTST=1 Possible Response OK

6.2.105 Supported Audio Loopback Test Values $LTST=? reports the supported values for sleep mode.

Table 6-125 Supported Audio Loopback Test Values

Parameters Definition Syntax AT$LTST=? Parameters None Example AT$LTST=? Possible Response $LTST: (0-2)

OK

6.2.106 Current Audio Loopback Test Mode $LTST? reports the current setting for the audio loopback test.

Table 6-126 Current Audio Loopback Test Value

Parameters Definition Syntax AT$LTST? Parameters None Example AT$LTST? Possible Response $LTST:<n>

OK


64

6.2.107 Customer Set The $LCST enables to change the customer setting

Table 6-1267 Customer Set

Parameters Definition Syntax AT$LCST=<n> Parameters <n>

0 = Default Customer (default) 1 = Customer 1 2 = Customer 2

Example AT$CST=1 Possible Response OK

6.2.108 Supported Customer Values $LCST? reports the current setting for the customer

Table 6-128 Supported Customer Values

Parameters Definition Syntax AT$LCST=? Parameters None Example AT$LCST=? Possible Response $LCST: (0-2)

OK

6.2.109 Current Customer Value $LCST? reports the current setting for the customer

Table 6-129 Current Customer Value

Parameters Definition Syntax AT$LCST? Parameters None Example AT$LCST? Possible Response $LCST:<n>

OK

6.2.110 Check Min Lock and MCC Lock Status $LLOC? reports the current lock status of Min and MCC

Table 6-130 Check Min Lock and MCC Lock Status

Parameters Definition Syntax AT$LLOC?


65

Parameters None Example AT$LLOC? Possible Response $LLOC: 0 0

OK Note: 1st Item : Min Lock Status 2nd Item : MCC Lock Status If the modem is locked, the value will be changed to 1 for Min Lock and 1 for MCC Lock

6.2.111 Check Remain Count for Pin Number Input +CCPS=? reports the current remain count for pin number input

Table 6-131 Check Remain Count for Pin Nunmber Input

Parameters Definition Syntax AT+CCPS=? Parameters None Example AT+CCPS=? Possible Response +CCPS: 0 3 10 3 10

OK Note: 1st Item : CHV1 Status (If locked the value will be 1) 2nd Item : CHV1 Remain Count 3rd Item : UCHV1 Remain Count 4th Item : CHV2 Remain Count 5th Item : UCHV2 Remain Count

6.2.112 Current System Time Information +CCTI enables to report current system time information

Table 6-132 Current System Time Information

Parameters Definition Syntax AT+CCTI=<n>,<m> Parameters <n>

0 = Disable Auto System Time Report (Default) 1 = Enable Auto System Time Report

<m> x = Auto Report Time Interval ( minutes )

Example AT+CCTI=1,1 Note: Every 1 minute, modem reports the current system time


66

Possible Response OK +CCTI: 1 2007 12 19 2 14 25 45 Note: 1st Item : System Time Information is valid or not, 1 is valid and 0 is invalid time 2nd Item : Year 3rd Item : Month 4th Item : Day 5th Item : The day of week (0 : Monday, 1 :Tuesday, 2:Wednesday, 3:Thursday, 4:Friday, 5:Saturday, 6:Sunday) 6th Item : Hour 7th Item : Minute 8th Item : Second

6.2.113 Check Current System Time Information +CCTI=? reports the current system time information

Table 6-133 Check Current System Time Information

Parameters Definition Syntax AT+CCTI=? Parameters None Example AT+CCTI=? Possible Response +CCTI: 1 2007 12 19 2 14 25 45

OK Note: System Time Information is Valid +CCTI: 0 OK Note: System Time Information is Invalid

cdma data terminal - search read.pudn.comread.pudn.com/downloads116/doc/494283/cdma at...

Documents