How it Works
Siemens
Loading...
MC39i
User Manual
314 pgs2.39 Mb1
User Manual
36 pgs1.13 Mb0

Siemens MC39i User Manual

Download
MC39i Siemens Cellular Engine
Version: 01.02 DocID: MC39i_ATC_V01.02
MC39i AT Command Set
Confidential / Released
Document Name:
Version:
Date:
DocId:
Status:
General Notes
Product is deemed accepted by recipient and is provided without interface to recipient’s products. The documentation and/or product are provided for testing, evaluation, integration and information pur­poses. The documentation and/or product are provided on an “as is” basis only and may contain defi­ciencies or inadequacies. The documentation and/or product are provided without warranty of any kind, express or implied. To the maximum extent permitted by applicable law, Siemens further dis­claims all warranties, including without limitation any implied warranties of merchantability, complete­ness, fitness for a particular purpose and non-infringement of third-party rights. The entire risk arising out of the use or performance of the product and documentation remains with recipient. This product is not intended for use in life support appliances, devices or systems where a malfunction of the product can reasonably be expected to result in personal injury. Applications incorporating the described prod­uct must be designed to be in accordance with the technical specifications provided in these guide­lines. Failure to comply with any of the required procedures can result in malfunctions or serious dis­crepancies in results. Furthermore, all safety instructions regarding the use of mobile technical sys­tems, including GSM products, which also apply to cellular phones must be followed. Siemens or its suppliers shall, regardless of any legal theory upon which the claim is based, not be liable for any con­sequential, incidental, direct, indirect, punitive or other damages whatsoever (including, without limita­tion, damages for loss of business profits, business interruption, loss of business information or data, or other pecuniary loss) arising out the use of or inability to use the documentation and/or product, even if Siemens has been advised of the possibility of such damages. The foregoing limitations of li­ability shall not apply in case of mandatory liability, e.g. under the German Product Liability Act, in case of intent, gross negligence, injury of life, body or health, or breach of a condition which goes to the root of the contract. However, claims for damages arising from a breach of a condition, which goes to the root of the contract, shall be limited to the foreseeable damage, which is intrinsic to the contract, unless caused by intent or gross negligence or based on liability for injury of life, body or health. The above provision does not imply a change on the burden of proof to the detriment of the recipient. Sub­ject to change without notice at any time. The interpretation of this general note shall be governed and construed according to German law without reference to any other substantive law.
Copyright
Transmittal, reproduction, dissemination and/or editing of this document as well as utilization of its contents and communication thereof to others without express authorization are prohibited. Offenders will be held liable for payment of damages. All rights created by patent grant or registration of a utility model or design patent are reserved.
Copyright © Siemens AG 2003
MC39i AT Command Set
01.02
November 11, 2003
MC39i_ATC_V01.02
Confidential / Released
s
MC39i_ATC_V01.02 Page 2 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s

Contents

1 Introduction...................................................................................................9
1.1 Scope of the document .............................................................................................................9
1.2 Related documents ...................................................................................................................9
1.3 Conventions and abbreviations...............................................................................................10
1.4 AT command syntax ...............................................................................................................10
1.4.1 Using parameters....................................................................................................................10
1.4.2 Combining AT commands on the same command line ..........................................................11
1.4.3 Entering successive AT commands on separate lines ...........................................................11
1.4.4 Communication between customer application and MC39i....................................................11
1.4.5 Unsolicited Result Codes (URCs)...........................................................................................12
1.5 Supported character sets ........................................................................................................13
1.5.1 UCS2 and GSM data coding and conversion in SMS text mode and Remote-SAT...............14
1.6 Flow control.............................................................................................................................17
1.6.1 Software flow control (XON/OFF flow control)........................................................................17
1.6.2 Hardware flow control (RTS/CTS flow control) .......................................................................17
2 Standard V.25ter AT Commands ...............................................................18
2.1 A/ Repeat previous command line .........................................................................................18
2.2 +++ Switch from data mode or PPP online mode to command mode...................................18
2.3 AT\Qn Flow control ................................................................................................................19
2.4 ATA Answer a call..................................................................................................................20
2.5 ATD Mobile originated call to dial a number ..........................................................................21
2.6 ATD><mem><n> Originate call to phone number <n> in memory <mem> ..........................24
2.7 ATD><n> Originate call to phone number selected from active memory ..............................26
2.8 ATD><str> Originate call to phone number in memory with corresponding field ..................27
2.9 ATDI Mobile originated call to dialable ISDN number <n> ....................................................28
2.10 ATDL Redial last telephone number used .............................................................................29
2.11 ATE Enable command echo ..................................................................................................30
2.12 ATH Disconnect existing connection .....................................................................................30
2.13 ATI Display product identification information........................................................................31
2.14 ATI[value] Display additional identification information..........................................................31
2.15 ATL Set monitor speaker loudness........................................................................................32
2.16 ATM Set monitor speaker mode ............................................................................................32
2.17 ATO Switch from command mode to data mode / PPP online mode....................................32
2.18 ATQ Set result code presentation mode................................................................................33
2.19 ATP Select pulse dialing ........................................................................................................33
2.20 ATS0 Set number of rings before automatically answering the call ......................................33
2.21 ATS3 Write command line termination character ..................................................................34
2.22 ATS4 Set response formatting character...............................................................................34
2.23 ATS5 Write command line editing character..........................................................................34
2.24 ATS6 Set pause before blind dialing......................................................................................35
2.25 ATS7 Set number of seconds to wait for connection completion ..........................................35
2.26 ATS8 Set number of seconds to wait for comma dial modifier ..............................................35
2.27 ATS10 Set disconnect delay after indicating the absence of data carrier .............................36
2.28 ATS18 Extended error report.................................................................................................37
2.29 ATT Select tone dialing ..........................................................................................................38
2.30 ATV Set result code format mode..........................................................................................39
2.31 ATX Set CONNECT result code format and call monitoring..................................................39
2.32 ATZ Set all current parameters to user defined profile ..........................................................40
2.33 AT&C Set circuit Data Carrier Detect (DCD) function mode..................................................40
2.34 AT&D Set circuit Data Terminal Ready (DTR) function mode...............................................41
2.35 AT&F Set all current parameters to manufacturer defaults ...................................................42
2.36 AT&S Set circuit Data Set Ready (DSR) function mode........................................................44
2.37 AT&V Display current configuration .......................................................................................45
MC39i_ATC_V01.02 Page 3 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
2.38 AT&W Store current configuration to user defined profile .....................................................47
2.39 AT+GCAP Request complete TA capabilities list ..................................................................49
2.40 AT+GMI Request manufacturer identification........................................................................49
2.41 AT+GMM Request TA model identification............................................................................49
2.42 AT+GMR Request TA revision identification of software status ............................................50
2.43 AT+GSN Request TA serial number identification (IMEI)......................................................50
2.44 AT+ILRR Set TE-TA local rate reporting ................................................................................51
2.45 AT+IPR Set fixed local rate.....................................................................................................52
2.45.1 Autobauding ............................................................................................................................53
s
3 AT Commands for FAX...............................................................................54
3.1 AT+FBADLIN Bad Line Threshold .........................................................................................55
3.2 AT+FBADMUL Error Threshold Multiplier..............................................................................55
3.3 AT+FBOR Query data bit order .............................................................................................56
3.4 AT+FCIG Query or set the Local polling id ............................................................................57
3.5 AT+FCLASS Fax: Select, read or test service class .............................................................58
3.6 AT+FCQ Copy Quality Checking ...........................................................................................59
3.7 AT+FCR Capability to receive................................................................................................59
3.8 AT+FDCC Query or set capabilities.......................................................................................60
3.9 AT+FDFFC Data Compression Format Conversion ..............................................................61
3.10 AT+FDIS Query or set session parameters...........................................................................62
3.11 AT+FDR Begin or continue phase C data reception..............................................................63
3.12 AT+FDT Data Transmission ..................................................................................................63
3.13 AT+FET End a page or document .........................................................................................64
3.14 AT+FK Kill operation, orderly FAX abort................................................................................64
3.15 AT+FLID Query or set the Local Id setting capabilities .........................................................64
3.16 AT+FMDL Identify Product Model..........................................................................................65
3.17 AT+FMFR Request Manufacturer Identification ....................................................................65
3.18 AT+FOPT Set bit order independently...................................................................................65
3.19 AT+FPHCTO DTE Phase C Response Timeout ...................................................................66
3.20 AT+FREV Identify Product Revision ......................................................................................66
3.21 AT+FRH Receive Data Using HDLC Framing .......................................................................66
3.22 AT+FRM Receive Data ..........................................................................................................67
3.23 AT+FRS Receive Silence ......................................................................................................67
3.24 AT+FTH Transmit Data Using HDLC Framing ......................................................................67
3.25 AT+FTM Transmit Data .........................................................................................................68
3.26 AT+FTS Stop Transmission and Wait ...................................................................................68
3.27 AT+FVRFC Vertical resolution format conversion .................................................................69
4 AT Commands originating from GSM 07.07.............................................70
4.1 AT+CACM Accumulated call meter (ACM) reset or query ....................................................70
4.2 AT+CALA Set alarm time.......................................................................................................71
4.3 AT+CAMM Accumulated call meter maximum (ACMmax) set or query................................74
4.4 AT+CAOC Advice of Charge information ..............................................................................75
4.5 AT+CBST Select bearer service type ....................................................................................76
4.6 AT+CCFC Call forwarding number and conditions control ....................................................77
4.6.1 Examples: Call forwarding ......................................................................................................79
4.7 AT+CCLK Real Time Clock ...................................................................................................81
4.8 AT+CCUG: Closed User Group ..............................................................................................82
4.9 AT+CCWA Call waiting ..........................................................................................................83
4.10 AT+CEER Extended error report ...........................................................................................86
4.11 AT+CFUN Set phone functionality .........................................................................................88
4.11.1 Wake up the ME from SLEEP mode.......................................................................................91
4.12 AT+CGMI Request manufacturer identification ......................................................................92
4.13 AT+CGMM Request model identification...............................................................................92
4.14 AT+CGMR Request revision identification of software status ...............................................92
4.15 AT+CGSN Request product serial number identification (IMEI) identical to GSN ................93
4.16 AT+CHLD Call hold and multiparty .........................................................................................94
MC39i_ATC_V01.02 Page 4 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
4.17 AT+CHUP Hang up call .........................................................................................................97
4.18 AT+CIMI Request international mobile subscriber identity ....................................................97
4.19 AT+CIND Indicator control ......................................................................................................98
4.20 AT+CLCC List current calls of ME .......................................................................................101
4.21 AT+CLCK Facility lock .........................................................................................................103
4.21.1 Examples: Enabling / disabling PIN 1 authentication ...........................................................106
4.21.2 Examples: Phone lock...........................................................................................................107
4.21.3 Examples: Call barring ..........................................................................................................109
4.22 AT+CLIP Calling line identification presentation..................................................................110
4.23 AT+CLIR Calling line identification restriction......................................................................111
4.24 AT+CLVL Loudspeaker volume level ..................................................................................112
4.25 AT+CMEE Report mobile equipment error ..........................................................................113
4.26 AT+CMER Mobile equipment event reporting .....................................................................114
4.27 AT+CMUT Mute control .......................................................................................................116
4.28 AT+CMUX Enter multiplex mode .........................................................................................117
4.28.1 Restricted use of AT commands in Multiplex mode..............................................................118
4.29 AT+COPN Read operator names ........................................................................................120
4.30 AT+COPS Operator selection ..............................................................................................121
4.31 AT+CPAS Mobile equipment activity status ........................................................................124
4.32 AT+CPBR Read current phonebook entries ........................................................................125
4.33 AT+CPBS Select phonebook memory storage....................................................................127
4.34 AT+CPBW Write phonebook entry ......................................................................................129
4.35 AT+CPIN Enter PIN .............................................................................................................132
4.35.1 What to do if PIN or password authentication fails? .............................................................135
4.36 AT+CPIN2 Enter PIN2 .........................................................................................................137
4.37 AT+CPUC Price per unit and currency table .......................................................................138
4.38 AT+CPWD Change password .............................................................................................140
4.39 AT+CR Service reporting control .........................................................................................143
4.40 AT+CRC Set Cellular Result Codes for incoming call indication.........................................144
4.41 AT+CREG Network registration...........................................................................................145
4.42 AT+CRLP Select radio link protocol param. for orig. non-transparent data call ..................148
4.43 AT+CRSM Restricted SIM access.......................................................................................149
4.44 AT+CSCS Set TE character set...........................................................................................151
4.45 AT+CSNS Single Numbering Scheme ................................................................................152
4.46 AT+CSQ Signal quality ........................................................................................................153
4.47 AT+CSSN Supplementary service notifications...................................................................154
4.48 AT+CUSD Unstructured supplementary service data .........................................................155
4.49 AT+VTD=<n> Tone duration................................................................................................156
4.50 AT+VTS DTMF and tone generation (<Tone> in {0-9, *, #, A, B, C, D}) .............................157
4.51 AT+WS46 Select wireless network .......................................................................................158
s
5 AT commands originating from GSM 07.05 for SMS .............................159
5.1 AT+CMGC Send an SMS command ...................................................................................159
5.2 AT+CMGD Delete SMS message........................................................................................160
5.3 AT+CMGF Select SMS message format .............................................................................160
5.4 AT+CMGL List SMS messages from preferred store ..........................................................161
5.5 AT+CMGR Read SMS message .........................................................................................164
5.6 AT+CMGS Send SMS message..........................................................................................167
5.7 AT+CMGW Write SMS message to memory.......................................................................169
5.8 AT+CMSS Send SMS message from storage.....................................................................171
5.9 AT+CNMA New SMS message acknowledge to ME/TE, only phase 2+ ............................172
5.10 AT+CNMI New SMS message indications ..........................................................................173
5.11 AT+CPMS Preferred SMS message storage ......................................................................176
5.12 AT+CSCA SMS service centre address ..............................................................................178
5.13 AT+CSCB Select cell broadcast messages.........................................................................179
5.14 AT+CSDH Show SMS text mode parameters .....................................................................180
5.15 AT+CSMP Set SMS text mode parameters.........................................................................181
5.16 AT+CSMS Select Message Service ....................................................................................182
MC39i_ATC_V01.02 Page 5 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
6 GPRS AT commands................................................................................183
6.1 GPRS AT commands in accordance with GSM 07.07 .........................................................183
6.1.1 AT+CGACT PDP context activate or deactivate..................................................................183
6.1.2 AT+CGATT GPRS attach and detach .................................................................................185
6.1.3 AT+CGDATA Enter data state.............................................................................................186
6.1.4 AT+CGDCONT Define PDP Context...................................................................................188
6.1.5 AT+CGPADDR Show PDP address .....................................................................................190
6.1.6 AT+CGQMIN Quality of Service Profile (Minimum acceptable) ..........................................191
6.1.7 AT+CGQREQ Quality of Service Profile (Requested) .........................................................195
6.1.8 AT+CGREG GPRS network registration status....................................................................199
6.1.9 AT+CGSMS Select service for MO SMS messages ...........................................................200
6.2 Siemens defined GPRS AT commands................................................................................201
6.2.1 AT^SGACT Query all PDP context activations.....................................................................201
6.2.2 AT^SGAUTH Set type of authentication for PPP connection .............................................202
6.2.3 AT^SGCONF Configuration of GPRS related Parameters...................................................203
6.3 Modem compatibility commands for MTs supporting GPRS ................................................204
6.3.1 ATD *99# Request GPRS service .......................................................................................204
6.3.2 ATD *98# Request GPRS IP service ..................................................................................205
6.3.3 ATH Manual rejection of a network request for PDP context activation ..............................206
6.4 Using GPRS AT commands (examples)...............................................................................207
6.5 Using the GPRS dial command ATD ....................................................................................209
7 AT Commands for SIM Application Toolkit (GSM 11.14).......................210
7.1 AT^SSTA Remote-SAT Interface Activation .........................................................................211
7.2 ^SSTN Remote-SAT Notification ..........................................................................................212
7.3 AT^SSTGI Remote-SAT Get Information .............................................................................213
7.4 AT^SSTR Remote-SAT Response .......................................................................................214
8 Siemens defined AT commands for enhanced functions .....................215
8.1 AT+CXXCID Display card ID (identical to AT^SCID)...........................................................215
8.2 AT^MONI Monitor idle mode and dedicated mode ..............................................................216
8.3 AT^MONP Monitor neighbour cells......................................................................................219
8.4 AT^SACM Advice of charge and query of ACM and ACMmax ...........................................220
8.5 AT^SAIC Audio Interface Configuration..............................................................................221
8.6 AT^SBC Battery charge and charger control .......................................................................222
8.7 AT^SCID Display SIM card identification number................................................................223
8.8 AT^SCKS Query SIM and chip card holder status ..............................................................224
8.9 AT^SCNI List Call Number Information ...............................................................................226
8.10 AT^SCTM Set critical operating temperature presentation mode or query temperature.....227
8.10.1 Deferred shutdown................................................................................................................229
8.11 AT^SDLD Delete the “last number redial“ memory..............................................................230
8.12 AT^SHOM Display Homezone.............................................................................................230
8.13 AT^SIND Extended Indicator Control ...................................................................................231
8.14 AT^SLCD Display Last Call Duration...................................................................................233
8.15 AT^SLCK Facility lock ..........................................................................................................234
8.16 AT^SLMS List Memory Storage...........................................................................................238
8.17 AT^SM20 Set M20 Compatibility .........................................................................................239
8.18 AT^SMGL List SMS messages from preferred storage.......................................................240
8.19 AT^SMGR Read SMS message without set to REC READ................................................241
8.20 AT^SMGO Set or query SMS overflow presentation mode or query SMS overflow ...........242
8.21 AT^SMONC Cell Monitoring ................................................................................................243
8.22 AT^SMONG GPRS Monitor.................................................................................................244
8.23 AT^SMSO Switch off mobile station ....................................................................................245
8.24 AT^SNFA Set or query microphone attenuation..................................................................246
8.25 Audio programming model ....................................................................................................247
8.26 AT^SNFD Set audio parameters to manufacturer default values........................................248
8.27 AT^SNFI Set microphone path parameters .........................................................................249
MC39i_ATC_V01.02 Page 6 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
8.28 AT^SNFM Mute microphone................................................................................................250
8.29 AT^SNFO Set audio output (= loudspeaker path) parameter..............................................251
8.30 AT^SNFPT Call progress tones ..........................................................................................253
8.31 AT^SNFS Select audio hardware set...................................................................................254
8.32 AT^SNFV Set loudspeaker volume......................................................................................256
8.33 AT^SNFW Write audio setting in non-volatile store .............................................................257
8.34 AT^SPBC Search the first entry in the sorted telephonebook .............................................258
8.35 AT^SPBD Purge phonebook memory storage ....................................................................259
8.36 AT^SPBG Read entry from active telephonebook via sorted index ....................................260
8.37 AT^SPBS Step through the selected phonebook alphabetically .........................................264
8.38 AT^SPIC Display PIN counter..............................................................................................267
8.39 AT^SPLM Read the PLMN list.............................................................................................271
8.40 AT^SPLR Read entry from the preferred operators list .......................................................272
8.41 AT^SPLW Write an entry to the preferred operators list......................................................273
8.42 AT^SPWD Change password for a lock ..............................................................................274
8.43 AT^SRTC Select, query, test ring tone parameters.............................................................277
8.44 AT^SSCONF SMS Configuration........................................................................................279
8.45 AT^SSDA Set Display Availability.......................................................................................280
8.46 AT^SSET Settings for Unsolicited Result Code "SIM READY" ...........................................281
8.47 AT^SSMSS Set Short Message Storage Sequence...........................................................282
8.48 AT^SSYNC Configure SYNC Pin.........................................................................................283
8.49 AT^STCD Display Total Call Duration .................................................................................284
s
9 APPENDIX .................................................................................................285
9.1 Summary of ERRORS and Messages..................................................................................285
9.1.1 Summary of CME ERRORS related to GSM 07.07 ..............................................................285
9.1.2 Summary of GPRS-related CME ERRORS..........................................................................286
9.1.3 Summary of CMS ERRORS related to GSM 07.05 ..............................................................287
9.1.4 Summary of Unsolicited Result Codes (URC) ......................................................................290
9.1.5 Result codes .........................................................................................................................293
9.1.6 Cause Location ID for the extended error report (AT+CEER) ..............................................294
9.1.7 GSM release cause for L3 Radio Resource (RR) (AT+CEER) ...........................................295
9.1.8 Siemens release cause for L3 Radio Resource (RR) (AT+CEER)......................................295
9.1.9 GSM release cause for Mobility Management (MM) (AT+CEER) ........................................296
9.1.10 Siemens release cause for L3 Mobility Management (MM) (AT+CEER) .............................297
9.1.11 GSM release cause for L3 Call Control (CC) (AT+CEER) ...................................................297
9.1.12 Siemens release cause for L3 Call Control (CC) (AT+CEER)..............................................298
9.1.13 Siemens release cause for L3 Advice of Charge (AOC) (AT+CEER) .................................299
9.1.14 GSM release cause for Supplementary Service call (AT+CEER) ........................................299
9.1.15 Siemens release cause for Call related Supplementary Services (CRSS) (AT+CEER) ....300
9.1.16 Siemens cause for Supplementary Services Entity..............................................................300
9.1.17 Siemens cause for Supplementary Services Manager.........................................................301
9.1.18 GSM release cause for Session Management (SM) (AT+CEER) ........................................302
9.1.19 SIEMENS release cause for Session Management (SM) (AT+CEER) ................................302
9.1.20 SIEMENS release cause for GPRS API (AT+CEER) ..........................................................303
9.1.21 SIEMENS release cause for Embedded Netcore (AT+CEER) ...........................................303
9.1.22 GSM cause for L3 Protocol module or other local cause (AT+CEER) .................................303
9.2 Summary of PIN requiring AT Commands............................................................................304
9.3 AT commands available before entering the SIM PIN..........................................................306
9.4 Standard GSM service codes ...............................................................................................309
9.4.1 Additional notes on ^SCCFC, +CCWA, ^SCLCK .................................................................311
9.5 GSM alphabet tables and UCS2 character values ...............................................................312
9.6 Sort order for phonebooks ....................................................................................................314

Figures

Figure 1: AT audio programming model...............................................................................................247
MC39i_ATC_V01.02 Page 7 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s

Tables

Table 1: Types of AT commands and responses...................................................................................10
Table 2: Illegal combinations of AT commands......................................................................................11
Table 3: Explanation of terms.................................................................................................................13
Table 4: Character definitions depending on alphabet (examples)........................................................13
Table 5: Direction ME to TE (output of SIM data to the TE)...................................................................14
Table 6: Direction TE to ME (input of Terminal data to SIM) .................................................................15
Table 7: Factory settings ........................................................................................................................42
Table 8: AT&V responses on ASC0 or multiplex channel 1...................................................................45
Table 9: AT&V responses on multiplex channels 2 / 3...........................................................................46
Table 10: List of settings stored to user profile on ASC0 or multiplex channel 1...................................47
Table 11: List of settings stored to user profile on multiplex channel 2 and 3 .......................................48
Table 12: Service Classes supported by ME .........................................................................................54
Table 13: Summary of AT commands available in Alarm mode ............................................................73
Table 14: Wake-up events in NON-CYCLIC and CYCLIC SLEEP modes ............................................91
Table 15: Availability of AT commands on virtual channels .................................................................118
Table 16: Summary of AT commands with different behavior in Multiplex mode ...............................118
Table 17: Timing algorithm of incorrect password input.......................................................................135
Table 18: Operating modes of the ME indicated by status LED (if <mode> = 1):................................283
Table 19: Summary of URCs................................................................................................................290
Table 20: Summary of Fax Class 2 URCs defined by EIA PN-2388 ...................................................292
Table 21: GSM service codes ..............................................................................................................309
MC39i_ATC_V01.02 Page 8 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
1 Introduction
1.1 Scope of the document
This document presents the AT Command Set for the Siemens cellular engine MC39i
MC39i features basic SIM Application Toolkit (SAT) functionality which enables SIM cards to run addi­tional network based applications, such as value added services, online banking, information services etc. To give you an idea, Chapter 7 provides a brief overview. In greater detail, the SAT functions and the required AT commands are described in [4].
1.2 Related documents
[1] MC39i Hardware Interface Description, Version 01.02 [2] MC39i Release Notes, Release 01.02 [3] GPRS Startup User's Guide [4] Remote-SAT User's Guide [5] Multiplexer User's Guide [6] Multiplex Driver Developer’s Guide for Windows 2000 and Windows XP [7] Multiplex Driver Installation Guide for Windows 2000 and Windows XP [8] DSB35 Support Box – Evaluation Kit for Siemens Cellular Engines [9] Application Note 02: Audio Interface Design [10] Application Note 14: Audio and Battery Parameter Download [11] Application Note 16: Upgrading MC39i Firmware [12] Application Note 24: Application Developer’s Guide
Prior to using MC39i or upgrading to a new firmware release, be sure to carefully read the latest prod­uct information provided in the Release Notes.
To visit the Siemens Website you can use the following link:
http://www.siemens.com/wm
MC39i_ATC_V01.02 Page 9 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
1.3 Conventions and abbreviations
Throughout the document, the GSM engines are referred to as ME (Mobile Equipment), MS (Mobile Station), TA (Terminal Adapter), DCE (Data Communication Equipment) or facsimile DCE (FAX mo­dem, FAX board).
To control your GSM engine you can simply send AT Commands via its serial interface. The control­ling device at the other end of the serial line is referred to as TE (Terminal Equipment), DTE (Data Terminal Equipment) or plainly “the application” (probably running on an embedded system).
All abbreviations and acronyms used throughout this document are based on the GSM specifications. For definitions please refer to TR 100 350 V7.0.0 (1999-08), (GSM 01.04, version 7.0.0 release 1998).
1.4 AT command syntax
The "AT" or "at" prefix must be set at the beginning of each command line. To terminate a command line enter <CR>.
Commands are usually followed by a response that includes “<CR><LF><response><CR><LF>”. Throughout this document, only the responses are presented, <CR><LF> are omitted intentionally.
Table 1: Types of AT commands and responses
Test command AT+CXXX=? The mobile equipment returns the list of parameters and
value ranges set with the corresponding Write command or by internal processes.
Read command AT+CXXX? This command returns the currently set value of the
parameter or parameters Write command AT+CXXX=<...> This command sets user-definable parameter values. Execution command AT+CXXX The execution command reads non-variable parameters
affected by internal processes in the GSM engine.
1.4.1 Using parameters
· Factory defaults are underlined or, if necessary, explicitly stated in the parameter description. A factory value will be loaded on power-up if the parameter is not storable (for example if not stored when AT^SMSO is executed, or not stored to the user profile specified with AT&W, or not stored to the audio profile defined with AT^SNFW). To restore factory defaults use AT&F. A variety of audio parameters can be reset to their factory defaults using AT^SNFD.
· Optional parameters are enclosed in square brackets, for example [0]. If optional parameters are omitted, the bracketed value will be used by default. If a parameter is not enclosed in brackets and no other behavior is stated, the current setting remains unchanged when the parameter is omitted.
· To ensure the correct sequence of optional and mandatory parameters, a comma must be kept for each omitted parameter that is followed by further parameters. Example: AT+CPBW=,<number>,<type>,<text> writes a phonebook entry to the first free memory location. AT+CPBW=<location>,<number>,<type>,<text> writes a phonebook entry to the memory location specified by <location>.
· When the parameter is a character string, e.g. <text> or <number>, the string must be enclosed in quotation marks, e.g. "Charlie Brown" or "+49030xxxx". Symbols within quotation marks will be recognized as strings.
· All spaces will be ignored when using strings without quotaton marks.
· It is possible to omit the leading zeros of strings which represent numbers.
MC39i_ATC_V01.02 Page 10 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
1.4.2 Combining AT commands on the same command line
You may enter several AT commands on the same line. This eliminates the need to type the "AT" or "at" prefix before each command. Instead, it is only needed once at the beginning of the command line. Use a semicolon as command delimiter.
The command line buffer accepts a maximum of 391 characters. If this number is exceeded none of the commands will be executed and TA returns ERROR.
The table below lists the AT commands you cannot enter together with other commands on the same line. Otherwise, the responses may not be in the expected order.
Table 2: Illegal combinations of AT commands
V.25ter commands With GSM 7.07 commands With GSM 7.05 commands (SMS) --- To be used standalone Commands starting with AT& --- To be used standalone AT+IPR --- To be used standalone
Note: When concatenating AT commands please keep in mind that the sequence of processing may
be different from the sequential order of command input. Therefore, if the consecutive order of the issued commands is your concern, avoid concatenating commands on the same line.
FAX commands, Prefix AT+F Siemens commands, Prefix AT^S
1.4.3 Entering successive AT commands on separate lines
When you enter a series of AT commands on separate lines, leave a pause between the preceding and the following command until the final response (for example OK, CME error, CMS error) appears. This avoids sending too many AT commands at a time without waiting for a response for each.
1.4.4 Communication between customer application and MC39i
Leaving hardware flow control unconsidered, the customer application (TE) is coupled with the MC39i (ME) via a receive and a transmit line.
Since both lines are driven by independent devices collisions may (and will) occur, for example, if the TE issues an AT command at the same time when MC39i starts sending a URC. This will probably cause the TE to misinterpret the URC as part of the response returned to the AT command.
To avoid this conflict the following measures must be taken:
· If an AT command is finished (with "OK" or "ERROR") the TE shall always wait at least 100 milli­seconds before sending the next one. This gives MC39i the opportunity to transmit pending URCs and get necessary service. Some AT commands may require more delay after an "OK" or "ERROR" response, refer to the fol­lowing command specifications for details.
· The TE shall communicate with MC39i using activated echo (ATE1), i.e. MC39i echoes characters received from the TE. Hence, when the TE receives the echo of the first character "A" of the AT command just sent by it­self it has control both over the receive and the transmit paths. This way, no URC can be issued by MC39i in between.
MC39i_ATC_V01.02 Page 11 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
1.4.5 Unsolicited Result Codes (URCs)
An Unsolicited Result Code (URC) is a report message issued by the ME without being requested by the TE, i.e. a URC is delivered automatically when a certain event occurs. Hence, a URC is not issued as part of the response to an executed AT command.
Typical events leading to URCs are incoming calls (“RING”), received short messages, changing tem­perature, status of the battery etc. A summary of URCs is listed in Table 19 and Table 20.
To announce a pending URC transmission the ME will do the following:
· The ME activates its Ring line (logic "1") for one second, i.e. the line changes to physical "Low" level. This allows the TE to enter power saving mode until ME related events request service.
· If the AT command interface is busy a "BREAK" will be sent immediately but the URC will not be issued until the line is free. This may happen if the URC is pending
- while an AT command is being processed, i.e. during the time from sending the first character
"A" of an AT command by the TE until the ME has responded with "OK" or "ERROR", or
- during a data call.
Please note that AT command settings may be necessary to enable in-band signaling. For exam-
ple, refer to AT+CMER or AT+CNMI.
It is strongly recommended to use the multiplex mode to map logical communication channels onto the serial line of MC39i. For details refer to [5] and the AT command AT+CMUX. Doing so it is possible to use one channel to still process URCs while having a data call active on another.
For most of these messages, the ME needs to be configured whether or not to send an unsolicited re­sult code. Depending on the AT command, the URC presentation mode can be saved to the user de­fined profile (see AT&W in Chapter 2.38), or needs to be activated every time you reboot the ME. Several URCs are not user definable, such as “^SYSSTART”, “^SYSSTART ALARM MODE”, “^SYSSTART, “^SHUTDOWN” and the Fax Class 2 URCs listed in Table 20.
If autobauding is enabled (as factory default mode or set with AT+IPR=0) URCs generated after re­start will be output at 57600 bps until the ME has detected the current bit rate. The URCs “^SYSSTART” and “^SYSSTART ALARM MODE”, however, are not presented at all. For details please refer to Chapter 2.45.1. To avoid problems we recommend to configure a fixed bit rate rather than using autobauding.
MC39i_ATC_V01.02 Page 12 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
1.5 Supported character sets
The ME supports two character sets: GSM 03.38 (7 bit, also referred to as SMS alphabet) and UCS2 (16 bit, refer to ISO/IEC 10646). See Chapter 4.44 for information about selecting the character set. Character tables are provided in Chapter 9.5.
Table 3: Explanation of terms
Term GSM character hex. value
Data Coding Scheme The Data Coding Scheme (dcs) is part of a short message and is saved on
the SIM. When writing a short message to the SIM in text mode, the dcs stored with AT+CSMP is used.
Escape sequences The escape sequence used within a text coded in GSM default alphabet
(0x1B) must be correctly interpreted by the TE, both for character input and output. To the module, an escape sequence appears like any other byte received or sent.
IRA IRA means that one byte is displayed as two characters in hexadecimal
format. For example,. the byte 0x36 (decimal 54) is displayed as "36" (two chars).
TE
TE character set The currently used TE character set is selected with AT+CSCS.
Due to the constraints described below it is recommended to prefer the USC2 alphabet in any external application.
If the GSM alphabet is selected all characters sent over the serial line are in the range from 0 ... 127. CAUTION: GSM alphabet is not ASCII alphabet! Several problems resulting from the use of the GSM alphabet:
1. "@" character with GSM alphabet value 0 is not printable by an ASCII terminal program (e.g. Mi-
crosoft
2. "@" character with GSM alphabet value of binary 0 will terminate any C string!
This is because the \0 is defined as C string end tag. Therefore, the GSM Null character may cause problems on application level when using a ´C´-function as „strlen()“. This can be avoided if it is represented by an escape sequence as shown in Table 4. By the way, this may be the reason why even network providers often replace "@"with “@=*” in their SIM application.
3. Other characters of the GSM alphabet are misinterpreted by an ASCII terminal program. For ex-
ample, GSM "ö" (as in "Börse") is assumed to be "|" in ASCII, thus resulting in "B|rse". This is be­cause both alphabets mean different characters with values hex. 7C or 00 and so on.
4. In addition, decimal 17 and 19 which are used as XON/XOFF control characters when software
flow control is activated, are interpreted as normal characters in the GSM alphabet.
When you write characters differently coded in ASCII and GSM (e.g. Ä, Ö, Ü), you need to enter es­cape sequences. Such a character is translated into the corresponding GSM character value and, when output later, the GSM character value can be presented. Any ASCII terminal then will show wrong responses.
©
Hyperterminal®).
TE is the terminal equipment that uses the GSM default alphabet as its character set. MS Hyperterminal (often used with the module) is an ANSI / ASCII terminal that does not support the GSM default alphabet.
Table 4: Character definitions depending on alphabet (examples)
GSM 03.38 character
Ö 5C \ \5C 5C 35 43 " 22 “ \22 5C 32 32 ò 08 BSP \08 5C 30 38 @ 00 NULL \00 5C 30 30
MC39i_ATC_V01.02 Page 13 of 314 11.11.2003
GSM character hex. value
Corresponding ASCII character
ASCII Esc sequence
Hex Esc sequence
MC39i AT Command Set
Confidential / Released
CAUTION: Often, the editors of terminal programs do not recognize escape sequences. In this case, an escape sequence will be handled as normal characters. The most common workaround to this problem is to write a script which includes a decimal code instead of an escape sequence. This way you can write, for example, short messages which may contain differently coded characters.
s
1.5.1 UCS2 and GSM data coding and conversion in SMS text mode and Re-
mote-SAT
This chapter provides basic information on how to handle input and output character conversion for SMS text mode and Remote-SAT if internal (ME) and external (TE) character representation differ, i.e. if the Data Coding Scheme and the TE character set use different coding.
1.5.1.1 Implementing output of SIM data to the TE
Table 5: Direction ME to TE (output of SIM data to the TE)
dcs
CSCS GSM Case 1
UCS2 Case 4
Case 1 Every byte will be sent as GSM-character (or ASCII if Hyperterminal is used). Example: 0x41,0x21 → ”AB” (because of conversion from 7-bit to 8-bit)
Case 2 Every byte will be sent as IRA. No conversion. Example: 0x41,0x42 → ”4142”
Case 3 Every byte will be sent as IRA. No conversion to GSM to avoid data loss. Example: 0x00,0x41 → ”0041” Problems:
· 0x41,0x42 → ”4142” (invalid GSM character, but ignored with respect to GSM 07.05)
· 0x41 → Error (there are two bytes needed)
Case 4 Every byte will be converted from GSM to UCS2. Example: 0x41,0x42 → ”00410042”
Case 5 Every Byte will be converted from GSM to UCS2. Example: 0x41,0x42 → ”00410042”
Case 6 Example: 0x41,0x42 → ”4142” Problems: 0x41 → Error (there are two bytes needed)
7 bit
(GSM default)
GSM (1:1)
GSM to UCS2 (1:2)
8 bit 16 bit
(UCS2) Case 2 IRA (1:1) Case 5 GSM to UCS2 (1:2)
Case 3
IRA (2:2)
Case 6
IRA (2:2)
MC39i_ATC_V01.02 Page 14 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
1.5.1.2 Implementing input of TE data to SIM
Table 6: Direction TE to ME (input of Terminal data to SIM)
CSCS
DCS 7 bit (GSM default) 8 bit Case 2
16 bit (UCS2)
Case 1 Data will be packed to 7 bit. Maximum text length: 160 characters Example: ”AB” → 0x41,0x21
Case 2 Data will be saved without any conversion. Maximum text length: 280 characters Example: ”4142” → 0x41,0x42 Problems: ”8f” → Error (invalid GSM character)
Case 3 Two bytes are needed. No conversion. Maximum text length: 280 characters Example: ”0041” → 0x00,0x41 Problems: ”41” → Error (there are two bytes needed)
Case 4 Two bytes are needed. Two bytes will be convert to 1 Bye GSM and 7-bit packed. Maximum text length: 640 characters Example: ”00410042” → 0x41,0x21 Problems:
· ”41” → Error (there are two bytes needed)
· ”4142” → Error (invalid character)
· ”0000” → Error (not an ucs2 character)
· ”007B” → 0x1B,0x28 (the saved data are two bytes long, not 1 byte like in all other cases. This ef-
fects the maximum input length of a string).
Case 5 Two bytes are needed. Two bytes will be converted to 1 Byte GSM. Maximum text length: 560 characters Example: ”00410042” → 0x41,0x42 Problems:
· ”41” → Error (there are two bytes needed)
· ”4142” → Error (invalid character)
· ”0000” → Error (not a UCS2 character)
· ”007B” → 0x1B,0x28 (the saved data are two bytes long, not 1 byte like in all other cases. This ef-
fects the maximum input length of a string)
GSM UCS2
Case 1 GSM (1:1)
GSM to UCS2 (1:2) Case 3 IRA (2:2)
Case 4 GSM to UCS2 (2:1) Case 5 GSM to UCS2 (2:1) Case 6 IRA (2:2)
MC39i_ATC_V01.02 Page 15 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
Case 6 Two bytes are needed. Maximum text length: 280 characters Example: ”00410042” → 0x00,0x41,0x00,0x21 Problems:
· ”41” → Error (there are two bytes needed)
· ”0000” → Error (not an ucs2 character)
· ”007B” → 0x00,0x7B
s
MC39i_ATC_V01.02 Page 16 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
1.6 Flow control
Flow control is essential to prevent loss of data or avoid errors when, in a data or fax call, the sending device is transferring data faster than the receiving side is ready to accept. When the receiving buffer reaches its capacity, the receiving device should be capable to cause the sending device to pause un­til it catches up.
There are basically two approaches to regulate data flow: software flow control and hardware flow control. The High Watermark of the input / output buffer should be set to approximately 60% of the to­tal buffer size. The Low Watermark is recommended to be about 30%. The data flow should be stopped when the capacity rises close to the High Watermark and resumed when it drops below the Low Watermark. The time required to cause stop and go results in a hysteresis between the High and Low Watermarks.
In Multiplex mode, it is recommended to use hardware flow control. For details please refer to [5].
1.6.1 Software flow control (XON/OFF flow control)
Software flow control sends different characters to stop (XOFF, decimal 19) and resume (XON, deci­mal 17) data flow. The only advantage of software flow control is that three wires would be sufficient on the serial interface.
1.6.2 Hardware flow control (RTS/CTS flow control)
Hardware flow control sets or resets the RTS/CTS wires. This approach is faster and more reliable, and therefore, the better choice. When the High Watermark is reached, CTS is set inactive until the transfer from the buffer has completed. When the Low Watermark is passed, CTS goes active once again.
To achieve smooth data flow, ensure that the RTS/CTS lines are present on your application platform. The application should include options to enable RTS/CTS handshake with the GSM engine. This needs to be done with the AT command AT\Q3 - it is not sufficient to set RTS/CTS handshake in the used Terminal program only. For details refer to Chapter 2.3.
The default setting of the GSM engine is AT\Q0 (no flow control) which must be altered to AT\Q3 (RTS/CTS hardware handshake on). The setting is stored volatile. For use after restart, AT\Qn should be stored to the user profile with AT&W.
AT\Q has no read command. To verify the current setting of AT\Q, simply check the settings of the ac­tive profile with AT&V.
Often, fax programs run an intialization procedure when started up. The intialization commonly in­cludes enabling RTS/CTS hardware handshake, eliminating the need to set AT\Q3 once again. How­ever, before setting up a CSD call, you are advised to check that RTS/CTS handshake is set.
Note: After deactivating the RTS line, the ME may still send up to 264 bytes (worst case). This can
be easily managed if the buffer of the host application is sufficiently sized, and if a hysteresis is implemented in its Rx buffer as mentioned in Chapter 1.6. For host applications that are re­quired to handle a large amount of data at high speed, a total buffer capacity of at least 512 bytes is recommended.
MC39i_ATC_V01.02 Page 17 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
2 Standard V.25ter AT Commands
These AT Commands are related to ITU-T (International Telecommunication Union, Telecommunica­tion sector) V.25ter document.
MC39i supports the registers S0-S29. You can change S0,S3,S4,S5,S6,S7,S8,S10,S18 by using the appropriate ATSn commands. All the other registers are read-only and for internal usage only!
2.1 A/ Repeat previous command line
Execute command
Response
A/
Reference
V.25ter
Repeats previous command line. Line does not need to end with terminating character.
Parameter
Note
· After beginning with the character “a“ or „A“, a second character “t“ ,”T“ or “/“ has to follow. In case of using a wrong second character, it is necessary to start again with character “a“ or “A“.
· If autobauding is active (see Chapter 2.45) A/ (and a/) cannot be used.
2.2 +++ Switch from data mode or PPP online mode to command mode
Execute command
+++
Reference
V.25ter
Response
This command is only available during a CSD call or a GPRS connection. The +++ character sequence causes the TA to cancel the data flow over the AT inter­face and switch to command mode. This allows you to enter AT commands while maintaining the data connection to the remote device or, accordingly, the GPRS connection.
OK
To prevent the +++ escape sequence from being misinterpreted as data, it must be preceded and followed by a pause of at least 1000 ms. The +++ characters must be entered in quick succession, all within 1000 ms.
Note:
· To return from command mode to data or PPP online mode: Enter ATO as de­scribed in Chapter 2.17.
MC39i_ATC_V01.02 Page 18 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
2.3 AT\Qn Flow control
Execute command
AT\Q<n>
Reference
Response
OK
If RTS/CTS flow control is not supported by interface and <n> is 2 or 3
ERROR
Parameter
<n> 0 AT\Q0 No flow control 1 AT\Q1 XON/XOFF software flow control 2 AT\Q2 Only CTS by DCE 3 AT\Q3 RTS/CTS hardware flow control
Note
· Factory default is 0 (no flow control).
· The setting of AT\Qn is stored volatile. For use after restart it should be stored
to the user defined profile (AT&W).
· For compatibility reasons, the AT\Qn command can be used in Multiplex mode, though the settings will not take effect. However, be aware that whenever you use the AT\Qn write command in Multiplex mode and then save the current configuration to the user profile with AT&W, the changed AT\Qn setting will be­come active after restart.
· See also Chapter 1.6 for general information on flow control.
s
Recommended for the following procedures: in­coming or outgoing data calls, fax calls, GPRS connections, MUX mode. Often, the initialization routine of Fax programs in­cludes enabling RTS/CTS handshake, eliminating the need to issue AT\Q3 once again.
MC39i_ATC_V01.02 Page 19 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
2.4 ATA Answer a call
Execute command
ATA
Reference
V.25ter
TA causes remote station to go off-hook (e.g. answer call). Any additional com­mands on the same command line are ignored.
This command may be aborted generally by receiving a character during execu­tion. It can´t be aborted in some connection setup states, such as handshaking.
Response
Response in case of data call, if successfully connected: CONNECT<text> TA switches to data mode.
Response in case of voice call, if successfully connected:
OK
When TA returns to command mode:
OK
Response if no connection:
NO CARRIER
Parameter
<text> Connection status (string)
<text> output only if +ATX parameter setting with value > 0.
Note
· See also AT+ATX in Chapter 2.31 and and result codes in Chapter 9.1.5 for <text>
· If AT+FCLASS setting is 1 or 2, all incoming calls will be answered as fax calls, when ATA is issued on multiplexer channel 1 resp. ASC0. For calls explicitly signaled as voice or data calls, this procedure will fail with result code “NO CARRIER”, but the incoming call will continue to ring. It is possible to change the AT+FCLASS setting to 0 while the call is ringing and to accept the call af­terwards with ATA. See Chapter 3.5 for AT+FCLASS.
s
MC39i_ATC_V01.02 Page 20 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
2.5 ATD Mobile originated call to dial a number
Execute command
ATD[<n>] [<mgsm][;]
Reference
V.25ter
GSM 07.07
GSM 02.07 Annex A
This command can be used to set up outgoing voice, data or fax calls. It also serves to control supplementary services.
The command may be aborted generally when receiving an ATH command during execution. Abortion is not possible during some states of connection setup such as handshaking.
Response
If no dialtone (parameter setting ATX2 or ATX4):
NO DIALTONE
If busy (parameter setting ATX3 or ATX4):
BUSY
If a connection cannot be set up:
NO CARRIER
If successfully connected and non-voice call: CONNECT<text> TA switches to data state.
Note: <text> output only if ATX parameter setting with value > 0.
When TA returns to command mode:
OK
If successfully connected and voice call:
OK
Parameter
<n> String of dialing digits and optionally V.25ter modifiers (dialing digits): 0-
9, * , #, +, A, B, C V.25ter modifiers: these are ignored: ,(comma), T, P, !, W, @
Emergency call:
<n> = Standardized emergency number 112 (no SIM needed)
<mgsm> String of GSM modifiers: I Activates CLIR (disables presentation of own phone number to
called party)
i Deactivates CLIR (enables presentation of own phone number
to called party) G Activates Closed User Group invocation for this call only. g Deactivates Closed User Group invocation for this call only.
<;> Only required to set up voice calls. TA remains in command mode.
General remarks
· Before setting up a data call, check that RTS/CTS handshake is enabled. See
Chapters 1.6 and 2.3.
· Parameter ”l“ and ”i“ only if no *# code is within the dial string.
· <mgsm> is not supported for data calls.
· <n> is default for last number that can be dialed by ATDL.
· *# codes sent with ATD are treated as voice calls. Therefore, the command
must be terminated with a semicolon “;”.
· If ATD is used with a USSD command (e.g. ATD*100#;) an AT+CUSD=1 is
executed implicitly (see AT+CUSD, pg. 155).
s
MC39i_ATC_V01.02 Page 21 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
· Parameter ‘G’ or ‘g’ will be ignored if Closed User Group was already activated,
or accordingly, deactivated with AT+CCUG command. Call by call invocation of CUG uses the settings provisioned by the provider or, if available, the settings of the parameters <index> and <info> made with AT+CCUG. See also Chapter
4.8.
· See ATX command in Chapter 2.31 for setting result code and call monitoring
parameters. Refer to Chapter 9.1.5 for <text>.
Blacklist management:
· The ME provides a blacklist function according to GSM02.07 Annex A. After a
predefined number of failed call attempts to the same number, the dialed num­ber is entered into a read-only phonebook called “blacklist” (phonebook “BL”). Call attempts to numbers contained in the blacklist will be barred by the ME and not signaled to the network. An attempt to start a voice call to a barred phone number will be stopped with CME ERROR 257 “Call barred”. An attempt to start a data or fax call to a barred phone number will be answered immediately with the result code “NO CARRIER”.
· GSM02.07 Annex A states a variety of conditions under which a number can be
removed from the blacklist. As far as timing conditions are concerned, the ME deletes numbers from the blacklist if a timer condition specified in GSM02.07 Annex A is met. But the most important condition is that the blacklist should be cleared if a user interaction is detected (key pressed). Since the module cannot detect such user interaction, it is up to the application to clear the blacklist in this case, using the AT^SPBD command. See Chapter 8.35.
Different call release indications
· Upon termination, an outgoing fax or data call may show a different result code
than a voice call would deliver under identical conditions. In order to track down the actual reason for call release, ATS18 (see Chapter 2.28) or AT+CEER (see Chapter 4.10) should be used.
Different response modes
· For voice calls two different response modes can be determined: TA returns
“OK” either after dialing was completed or after the call has been established. The setting is made with AT^SM20 (see Chapter 8.17 for more details). Factory default is AT^SM20=1. This causes the ME to return “OK” in case of successful connection, otherwise one of the call release indications “NO CAR­RIER”, “NO DIAL TONE”, “NO CARRIER” will follow.
· Data calls: In data connections, call setup always terminates when the call has
been established (indicated by result code “CONNECT<text>”) or when it fails (indicated by “NO CARRIER”).
Using ATD during an active voice call:
· When a user originates a second voice call while there is already an active
voice call, the first call will be automatically put on hold.
· The second call attempt is acknowledged with “OK” immediately after dialing
with ATD has completed, without relation to a successful call setup. In case of failure, the additional result codes “NO CARRIER”, “NO DIAL TONE”, “NO CARRIER” will be presented afterwards (see example below). This behavior is similar to the mode set with AT^SM20=0, but occurs also if AT^SM20=1 and cannot be changed. To avoid different behavior in all proce­dures of voice call setup simply give priority to AT^SM20=0 (“OK” appears al­ways immediately after dialing).
· The current states of all calls can be easily checked at any time by using the
AT+CLCC command. For details refer to Chapter 4.20.
s
MC39i_ATC_V01.02 Page 22 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
Example
The following example shows the call setup procedure when a call is already ac­tive and a second call attempt fails because the line of the called party is busy:
atd0301234567; Dialing out the first party’s number. OK The first call is established.
atd0302222222; The number of the second party is dialed. OK The response “OK” is issued immediately though no call
BUSY Line of second called party is busy.
s
is established (same behavior as if you had chosen AT^SM20=0).
MC39i_ATC_V01.02 Page 23 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
2.6 ATD><mem><n> Originate call to phone number <n> in memory <mem>
This command allows you to dial a phone number from a specific phonebook. To initiate a call, enter a two letter abbreviation for the phonebook <mem>, followed by the memory location <n> of the de­sired entry. The location range of each phonebook can be queried with AT+CPBR (see Chapter
4.32).
Execute command
ATD><mem> <n>[<mgsm>];
Parameter
TA attempts to set up an outgoing call to the specified number. This command may be aborted generally by receiving a character during execu-
tion. Abortion is not possible during some states of connection setup such as handshaking.
Response
If error is related to ME functionality:
+CME ERROR: <err>
If no dialtone (parameter setting ATX2 or ATX4):
NO DIALTONE
If busy (parameter setting ATX3 or ATX4):
BUSY
If connection cannot be set up:
NO CARRIER
If successfully connected:
OK
<mem> phonebook:
"SM” SIM phonebook (storage depending on SIM card)
”FD” SIM fixdialing phonebook (storage depending on SIM card) ”LD” Last-dialing-phonebook (list of up to 10 most recently dialed
numbers. Depending on the SIM card, the storage is located
either on the SIM card only or shared by SIM and ME). ”MC” ME missed (unanswered received) calls list (up to 10 numbers) ”RC” Received calls list (up to 10 numbers stored in ME) ”ME” ME phonebook (up to 250 numbers) ”ON” Own numbers (MSISDNs) list. Storage depending on SIM
card. Notes:
Refer to Chapter 4.33 for more information regarding the capacity of each phonebook and types of storage (ME / SIM card).
<n> Integer type memory location in the range of locations available in
the selected memory, i.e. the index number returned by AT+CPBR.
<mgsm> I Activates CLIR (disables presentation of own phone number to
called party) i Deactivates CLIR (enables presentation of own phone number
to called party) <;> The semicolon is mandatory since dialing from a phonebook is only
supported for voice calls.
MC39i_ATC_V01.02 Page 24 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
Reference
V.25ter/GSM
07.07
Example
Note
· There is no <mem> for emergency call (“EN”).
· The command is not applicable to data calls. Any attempt to dial a data call
number from <mem> causes the result code “NO CARRIER” to appear.
· Parameter <mgsm> only if no *# code is within the dial string.
· *# codes sent with ATD are treated as voice calls. Therefore, the command
must be terminated with a semicolon “;”.
· See ATX command in Chapter 2.31 for setting result code and call monitoring
parameters.
To query the location number of the phonebook entry:
AT+CPBR=1,xx
TA returns the entries available in the active phonebook.
To dial a number from the SIM phonebook, for example the number stored to lo­cation 15:
ATD>SM15; OK
To dial a phone number stored in the last dial memory on the SIM card:
ATD>LD9; OK
s
MC39i_ATC_V01.02 Page 25 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
2.7 ATD><n> Originate call to phone number selected from active memory
This command can be used to dial a phone number selected from the active memory. The active memory is the phonebook selected with AT+CPBS (see Chapter 4.33). To set up a call simply enter the memory location of the desired entry. The memory location range of each phonebook can be queried by AT+CPBR (see Chapter 4.32).
Execute command
ATD><n>[<mgsm>];
Reference
V.25ter/GSM 07.07
TA attempts to set up an outgoing call to the stored number. The command may be aborted generally by receiving a character during
execution. Abortion is not possible during some states of connection setup such as handshaking.
Response
If error is related to ME functionality:
+CME ERROR: <err>
If no dialtone (parameter setting ATX2 or ATX4):
NO DIALTONE
If busy (parameter setting ATX3 or ATX4):
BUSY
If a connection cannot be set up:
NO CARRIER
If successfully connected:
OK
Parameter
<n> integer type memory location should be in the range of locations
available in the memory used, i.e. the index number returned by AT+CPBR.
<mgsm> I Activates CLIR (disables presentation of own phone number to
called party)
i Deactivates CLIR (enables presentation of own phone number
to called party)
<;> The semicolon is mandatory since dialing from a phonebook is
only supported for voice calls.
Note
· Parameter <mgsm> only if no *# code is within the dial string.
· The command is not applicable to data calls. Any attempt to dial a data
call number from <mem> causes the result code “NO CARRIER” to ap­pear.
· *# codes sent with ATD are treated as voice calls. Therefore, the com­mand must be terminated with a semicolon “;”.
· See ATX command in Chapter 2.31 for setting result code and call moni­toring parameters.
MC39i_ATC_V01.02 Page 26 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
2.8 ATD><str> Originate call to phone number in memory with correspond­ing field
This command searches the active phonebook for a given string <str> and dials the assigned phone number. The active phonebook is the one set with AT+CPBS.
Execute command
ATD><str>[mgsm];
Reference
V.25ter/GSM 07.07
TA attempts to set up an outgoing call to stored number. This command may be aborted generally by receiving a character during exe-
cution. Abortion is not possible during some states of connection setup such as handshaking.
Response
If error is related to ME functionality:
+CME ERROR: <err>
If no dialtone (parameter setting ATX2 or ATX4):
NO DIALTONE
If busy (parameter setting ATX3 or ATX4):
BUSY
If a connection cannot be set up:
NO CARRIER
If successfully connected:
OK
Parameter
<str> string type value (“x”), which should equal an alphanumeric field in
at least one phonebook entry in the searched memories; used char­acter set should be the one selected with AT+CSCS. <str> can con­tain escape sequences as described in Chapter 1.5. <str> must be enclosed in quotation marks (""), if escape sequences or parameter <mgsm> are used or if the alphanumeric strings con­tains a blank. If not, quotation marks are optional.
<mgsm> I Activates CLIR (disables presentation of own phone number to
called party)
i Deactivates CLIR (enables presentation of own phone number to
called party)
<;> The semicolon is mandatory since dialing from a phonebook is only
supported for voice calls.
Note
· The command is not applicable to data calls. Any attempt to dial a data call number from <mem> causes the result code “NO CARRIER” to appear.
· See ATX command in Chapter 2.31 for setting result code and call moni­toring parameters. Refer to Chapter 9.1.5 for <text>.
MC39i_ATC_V01.02 Page 27 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
2.9 ATDI Mobile originated call to dialable ISDN number <n>
Execute command
ATDI<n>[;]
Parameter
Reference
V.25ter
TA attempts to set up an outgoing call to ISDN number. This command may be aborted generally by receiving a character during execu­tion. Abortion is not possible during some states of connection setup such as handshaking.
Response
If no dialtone (parameter setting ATX2 or ATX4):
NO DIALTONE
If busy (parameter setting ATX3 or ATX4):
BUSY
If a connection cannot be set up:
NO CARRIER
If successful connected and non-voice call: CONNECT<text> TA switches to data state.
Note: <text> output only if +ATX parameter setting with value > 0.
When TA returns to command mode:
OK
If successfully connected and voice call:
OK
<n> [+]<d> phone number string with maximum length of 20 characters + international dialing format <d> ISDN number string of digits: +,0-9, A, B, C <;> voice call
Note
See ATX command in Chapter 2.31 for setting result code and call monitoring pa­rameters. Refer to Chapter 9.1.5 for <text>.
MC39i_ATC_V01.02 Page 28 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
2.10 ATDL Redial last telephone number used
Execute command
ATDL[;]
Reference
V.25ter
This command redials the last telephone number dialed.
· To redial the last data call number simply enter ATDL
· To redial the last voice call number type ATDL;
The command may be aborted generally by receiving a character during execu­tion. Abortion is not possible during some states of connection setup such as handshaking.
Response
If there is no last number or number is not valid:
+CME ERROR
If no dialtone (parameter setting ATX2 or ATX4):
NO DIALTONE
If busy (parameter setting ATX3 or ATX4):
BUSY
If a connection cannot be set up:
NO CARRIER
If successfully connected and non-voice call: CONNECT<text> TA switches to data state.
Note: <text> output only if +ATX parameter setting with value > 0.
When TA returns to command mode:
OK
If successfully connected and voice call:
OK
Parameter
<;> voice call
Note
· See ATX command in Chapter 2.31 for setting result code and call monitoring parameters. Refer to Chapter 9.1.5 for <text>.
· If terminated with semicolon, ATDL dials the last voice call number stored in the “LD”phonebook. Otherwise, the last dialed data or fax number will be used which is not stored in the “LD”phonebook. See Chapter 4.33.
s
MC39i_ATC_V01.02 Page 29 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
2.11 ATE Enable command echo
Write command
ATE[<value>]
Reference
V.25ter
This setting determines whether or not the TA echoes characters received from TE during command state.
Response
OK
Parameter
<value> 0 Echo mode off 1 Echo mode on
Note
In case of using the command without parameter, <value> is set to 0.
2.12 ATH Disconnect existing connection
Execute command
ATH[n]
Reference
V.25ter
Disconnects any call in progress, such as voice, fax or CSD calls. See notes be­low for GPRS and multiplex mode.
Response
OK
Note:
OK is issued after circuit 109 (DCD) is turned off, if it was previously on.
Parameter
<n> [0] terminate call
Note
Using ATH in Multiplex mode:
· ATH terminates every voice, fax or CSD call, no matter on which logical chan­nel ATH was executed. For more details see [2].
For example, if ATH is executed on channel 2 or 3, a voice call on channel 1
will be disconnected, too.
This behavior is in accordance with ITU-T V.25 ter; (07/97, see “6.3.6 Hook
control“: "ATH is terminating any call in progress").
Using ATH while GPRS is active during Multiplex mode:
· ATH clears an active PDP context or terminates an existing PPP connection, but only if issued on the same logical channel where GPRS is used. It does not affect PDP contexts and PPP connections on other interfaces or logical chan­nels.
· See also Chapter 6.3.3, ATH Manual rejection of a network request for PDP context activation.
s
MC39i_ATC_V01.02 Page 30 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
2.13 ATI Display product identification information
Execute command
ATI
Reference
V.25ter
Response
ME issues product information text
SIEMENS
MC39i REVISION xx.yy
OK
Explanation of “Revision“ parameter: Version xx and variant yy of software release.
Note
s
2.14 ATI[value] Display additional identification information
Execute command
ATI[value]
Reference
V.25ter
Response
<value>=9 delivers the following information. Other values are not supported and only return OK.
ATI9 SIEMENS Gipsy Soft Protocolstack V2.550
Note
MC39i_ATC_V01.02 Page 31 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
2.15 ATL Set monitor speaker loudness
Execute command
ATL[val]
Reference
V.25ter
Response
OK
Note
· The two commands ATL and ATM are implemented only for V.25ter compatibil­ity reasons and have no effect.
· In multiplex mode the command is supported on logical channel 1 only.
2.16 ATM Set monitor speaker mode
Execute command
ATM[val]
Reference
V.25ter
Response
OK
Note
· The two commands ATL and ATM are implemented only for V.25ter compatibil­ity reasons and have no effect.
· In multiplex mode the command is supported on logical channel 1 only.
s
2.17 ATO Switch from command mode to data mode / PPP online mode
Execute command
ATO[n]
Reference
V.25ter
Response
ATO is the corresponding command to the +++ escape sequence described in Chapter 2.2: When you have established a CSD call or a GPRS connection and TA is in command mode, ATO causes the TA to resume the data or GPRS con­nection and takes you back to data mode or PPP online mode.
If connection is not successfully resumed
NO CARRIER
or TA returns to data or PPP online mode from command mode
CONNECT <text>
Note: <text> output only if +ATX parameter setting with value > 0.
Parameter
<n> [0] switch from command mode to data or PPP online mode
Note
MC39i_ATC_V01.02 Page 32 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
2.18 ATQ Set result code presentation mode
Write command
ATQ[<n>]
Reference
V.25ter
Response
Specifies whether or not the TA transmits any result code to the TE. Information text transmitted in response is not affected by this setting.
If <n>=0:
OK
If <n>=1:
(none)
Parameter
<n> 0 DCE transmits result code 1 Result codes are suppressed and not transmitted
Note
s
2.19 ATP Select pulse dialing
Execute command
ATP
Reference
V.25ter
Response
OK
Note
No effect for GSM
2.20 ATS0 Set number of rings before automatically answering the call
Read command
ATS0?
Write command
ATS0=<n>
Reference
V.25ter
Response
<n> OK
Specifies whether or not the TA will accept an incoming data / fax call without user intervention. <n> determines the number of rings to wait before the TA will automatically answer.
Response
OK
Parameter
<n> 000 disables automatic answer mode 001-255 enables automatic answering after specified number of rings
(not supported on multiplex interfaces 2 and 3).
Note
· If <n> is set too high, the calling party may hang up before the call can be automatically answered.
· The correlation between ATS7 and ATS0 is important. Example: Call setup may fail if ATS0=20 and ATS7=30.
· On multiplex interfaces 2 and 3 only ATS0=0 is allowed.
MC39i_ATC_V01.02 Page 33 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
2.21 ATS3 Write command line termination character
Read command
ATS3?
Write command
ATS3=<n>
Parameter
Reference
V.25ter
Response
<n> OK
This parameter setting determines the character recognized by TA to terminate an incoming command line.
Response
OK
<n> 000-013-127 command line termination character
Note

Using other value than 13 can cause problems when entering commands.

2.22 ATS4 Set response formatting character
Read command
ATS4?
Write command
ATS4=<n>
Parameter
Reference
V.25ter
Response
<n> OK
This parameter setting determines the character generated by the TA for result code and information text.
Response
OK
<n> 000-010-127 response formatting character.
Note
s
2.23 ATS5 Write command line editing character
Read command
ATS5?
Write command
ATS5=<n>
Parameter
Reference
V.25ter
MC39i_ATC_V01.02 Page 34 of 314 11.11.2003
Response
<n> OK
This parameter setting determines the character recognized by TA as a request to delete the immediately preceding character from the command line.
Response
OK
<n> 000-008-127 command line editing character
Note
MC39i AT Command Set
s
Confidential / Released
2.24 ATS6 Set pause before blind dialing
Read command
ATS6?
Write command
ATS6=<n>
Parameter
Reference
V.25ter
Response
<n> OK
No effect for GSM
Response
OK
<n> 000-255 number of seconds to wait before blind dialing.
Note
2.25 ATS7 Set number of seconds to wait for connection completion
Read command
ATS7?
Write command
ATS7=<n>
Parameter
Response
<n> OK
Specifies the number of seconds the TA will wait for the completion of the call setup when answering or originating a data call. Also referred to as "no answer timeout". To put it plainly, this is the time to wait for the carrier signal. If no carrier signal is received within the specified time, the TA hangs up.
Response
OK
<n> 000 – 060 no. of seconds to wait for connection completion.
Reference
V.25ter
Note
· Values greater than 60 cause no error, but <n> will be restored to the maxi- mum value of 60.
· If called party has specified a high value for ATS0=<n>, call setup may fail.
· The correlation between ATS7 and ATS0 is important.
Example: Call setup may fail if ATS7=30 and ATS0=20.
· ATS7 is only applicable to data calls.
2.26 ATS8 Set number of seconds to wait for comma dial modifier
Read command
ATS8?
Write command
ATS8=<n>
Reference
V.25ter
Response
<n> OK
No effect for GSM
Response
OK
Note
MC39i_ATC_V01.02 Page 35 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
2.27 ATS10 Set disconnect delay after indicating the absence of data carrier
Read command
ATS10?
Write command
ATS10=<n>
Parameter
Reference
V.25ter
Response
<n> OK
This parameter setting determines the amount of time, that the TA remains con­nected in absence of a data carrier. If the data carrier is detected before discon­nect, the TA remains connected.
Response
OK
<n> 001-002-254 number of tenths of seconds of delay
Note
MC39i_ATC_V01.02 Page 36 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
2.28 ATS18 Extended error report
Read command
ATS18?
Write command
ATS18=<n>
Extended error report
Reference
Siemens
Example
Response
<n> OK
The write command enables or disables the presentation of more detailed error messages reported in the case of unsuccessful CSD or fax calls.
Parameter of the write command
<n> 0 – 255
Odd numbers enable the presentation of extended error reports. Even numbers disable the presentation of extended error reports.
Response
OK
If the presentation is enabled (odd number), the TA returns an extended error re­port every time it fails to establish a data or fax call. Errors are reported only for failures that occur before call setup is complete, for example if the result code NO CARRIER, NO DIALTONE or BUSY appears.
Extended error report
+CAUSE: <location ID>: <reason >
Parameters of the extended error report
<location ID> Location ID as number code
Location IDs are listed in Chapter 9.1.6. Each ID is related to an­other table that contains a list of <reason>s.
<reason> Reason for last failure, stated as number code
<reason> numbers and associated descriptions are listed in sev­eral tables, sorted by different categories (see Chapters 9.1.7 to
9.1.22). The Chapter numbers can be found proceeding from the Location ID table in Chapter 9.1.6.
Note
This command applies only to circuit switched data calls and fax calls. For voice calls, extended error reports can be retrieved using the execute command AT+CEER (Chapter 4.10).
To enable the presentation of extended error reports:
ats18=1 OK
Now, a mobile originated data call fails. Call setup is terminated with an extended error report, followed by the result code NO CARRIER:
atd0301234567 +CAUSE: 8:16 NO CARRIER
The Location ID 8 stated in Chapter 9.1.6 points to Chapter 9.1.11, where 16 = “Normal call clearing”.
s
MC39i_ATC_V01.02 Page 37 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
2.29 ATT Select tone dialing
Execute command
ATT
Reference
V.25ter
Response
OK
Note
No effect for GSM
s
MC39i_ATC_V01.02 Page 38 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
2.30 ATV Set result code format mode
Write command
ATV[<value>]
Reference
V.25ter
Response
This parameter setting determines the contents of the header and trailer transmit­ted with result codes and information responses.
When <value> =0
0 When <value> =1 OK
Parameter
<value> [0] Information response: <text><CR><LF>
Short result code format: <numeric code><CR>
1 Information response: <CR><LF><text><CR><LF> Long result code format: <CR><LF><verbose code><CR><LF>
Note
In case of using the command without parameter <value> will be set to 0. Information responses are listed in Chapter 9.1.5 (verbose code and numeric
code).
s
2.31 ATX Set CONNECT result code format and call monitoring
Write command
ATX[<value>]
Reference
V.25ter
Response
This parameter setting determines whether or not the TA detects the presence of dial tone and busy signal and whether or not TA transmits particular result codes.
OK
Parameter
<value>
[0] CONNECT result code only returned, dial tone and busy de-
tection are both disabled
1 CONNECT<text> result code only returned, dial tone and busy
detection are both disabled
2 CONNECT<text> result code returned, dial tone detection is
enabled, busy detection is disabled
3 CONNECT<text> result code returned, dial tone detection is
disabled, busy detection is enabled
4 CONNECT<text> result code returned, dial tone and busy de-
tection are both enabled
Note
See Chapter 9.1.5 for related <text>.
MC39i_ATC_V01.02 Page 39 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
2.32 ATZ Set all current parameters to user defined profile
Execute command
ATZ[<value>]
Reference
V.25ter
Response
TA sets all current parameters to the user profile stored with AT&W. If a connec­tion is in progress, it will be terminated. All defined GPRS contexts which are not activated or not online will be undefined (see +CGDCONT,+CGQREQ,+CGQMIN commands).
Note: Any additional commands on the same command line will be ignored. A de­lay of 300 ms is required before next command is sent, otherwise “OK” response may be corrupted.
OK
Parameter
<value> [0] Reset to user profile
Note
MC39i can be assigned two profiles: the factory profile (restored with AT&F) and the user profile (stored with AT&W).
Related chapters: AT&F in Chapter 2.35, AT&W in Chapter 2.38.
s
2.33 AT&C Set circuit Data Carrier Detect (DCD) function mode
Write command
AT&C[<value>]
Reference
V.25ter
Response
This parameter determines how the state of circuit 109(DCD) relates to the detec­tion of received line signal from the distant end.
OK
If DCD is not supported by the interface
ERROR
Parameter
<value> [0] DCD line is always ON. 1 DCD line is ON in the presence of data carrier only.
Note
Factory default is 1.
MC39i_ATC_V01.02 Page 40 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
2.34 AT&D Set circuit Data Terminal Ready (DTR) function mode
Write command
AT&D[<value>]
Reference
V.25ter
Response
This command is only intended for data calls. The <value> parameter determines how the TA responds when circuit 108/2 (DTR) is changed from ON to OFF dur­ing data mode.
OK
If DTR is not supported by the interface and <value> is 1 or 2
ERROR
Parameter
<value> [0] TA ignores status on DTR. 1 ON->OFF on DTR: Change to command mode while retaining
the connected call.
2 ON->OFF on DTR: Disconnect data call, change to command
mode. During state DTR = OFF is auto-answer off.
Note
Factory default is 2 if DTR is supported by the interface, otherwise 0.
MC39i_ATC_V01.02 Page 41 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
2.35 AT&F Set all current parameters to manufacturer defaults
Execute command
AT&F[value]
Reference
V.25ter
Response
TA sets all current parameters to the manufacturer defined profile.
Note: Any additional commands on the same command line will be ig­nored. A delay of 300 ms is required before next command is sent, oth­erwise “OK” response may be corrupted.
OK
Parameter
<value> 0 Set all TA parameters to manufacturer default.
See Table 7: Factory settings.
Note
In addition to the default profile, you can store an individual one with AT&W. To alternate between the two profiles enter either ATZ (loads user profile) or AT&F (restores factory profile). Refer to Chapter 2.38 for AT&W and Chapter 2.32 for ATZ.
Audio parameters set with AT^SNFA, AT^SNFO and AT^SNFI can be restored with AT^SNFD. See Chapter 8.26.
Table 7: Factory settings
AT command Restored parameters
AT\Q <n>=0 ATE <value>=1 ATQ <n>=0 ATS0 <n>=000 ATS3 <n>=013 ATS4 <n>=010 ATS5 <n>=008 ATS6 <n>=000 ATS7 <n>=060 ATS10 <n>=002 ATS18 <n>=0 ATV <value>=1 ATX <value>=4 AT&C <value>=1 AT&D <value>=2 AT&S <value>=0 AT+ILRR <value>=0 AT+FCLASS <n>=0 AT+CBST <speed>=7, <name>=0, <ce>=1 AT+CFUN <fun>=1 AT+CLIP <n>=0 AT+CMEE <n>=0 AT+CMER <mode>=0, <keyp>=0, <disp>=0, <ind>=0, <bfr>=0
MC39i_ATC_V01.02 Page 42 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
AT command Restored parameters
AT+COPS <format>=0 AT+CPBS <storage>=”SM” AT+CR <mode>=0 AT+CRC <mode>=0 AT+CREG <n>=0 AT+CRLP <iws>=61, <mws>=61, <T1>=78, <N2>=6 AT+CSCS <chset>=”GSM” AT+CSCS <chset>=”GSM” AT+CSSN <n>=0, <m>=0 AT+VTD <duration>=1 AT+CMGF <mode>=0 AT+CNMI <mode>=0, <mt>=0, <bm>=0, <ds>=0, <bfr>=1 AT+CSDH <show>=0 AT+CSMP <dcs>=0, <fo>=17, <pid>=0, <vp>=167 AT+CSMS <service>=0, <mt>=1, <mo>=1, <bm>=1 AT^SMGO <n>=0 AT^SSCONF <ra>=0 AT^SSDA <da>=0 AT^SSMSS <seq>=0 AT^SACM <n>=0 AT^SCKS <n>=0 AT^SCTM <n>=0, <p>=0 AT^SM20 <CallMode>=1, <CmgwMode>=1 AT^SPBS internal counter
s
MC39i_ATC_V01.02 Page 43 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
2.36 AT&S Set circuit Data Set Ready (DSR) function mode
Write command
AT&S<value>
Parameter
Reference V.25ter
Response
This parameter determines how the TA sets circuit 107 (DSR) depending on the communication state of the TA interfacing TE.
OK
If DSR is not supported by the interface
ERROR
<value> 0 DSR always on. 1 TA in command mode: DSR is OFF. TA in data mode: DSR is ON.
Note
Factory default is 0.
s
MC39i_ATC_V01.02 Page 44 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
2.37 AT&V Display current configuration
Execute command
AT&V[<n>]
Reference
Response
TA returns the current parameter setting. The configuration varies depending on whether or not PIN authentication has been done, or Multiplex mode has been activated.
Parameter
<n> 0 profile number
Note:
· Parameter values and order are subject to change.
· The parameters of AT^SMGO can only be displayed after the SMS data from
the SIM have been read successfully for the first time. Reading starts after successful SIM authentication has been performed, and may take up to 30 seconds depending on the SIM used. While the read process is in progress, an attempt to read the parameter will result in empty values.
· The parameter of AT+CSDH will only be displayed in SMS text mode, i.e. if AT+CMGF=1.
s
Table 8: AT&V responses on ASC0 or multiplex channel 1
PIN authentication done No PIN authentication
ACTIVE PROFILE: E1 Q0 V1 X4 &C1 &D2 &S0 \Q0 S0:000 S3:013 S4:010 S5:008 S6:000 S7:060
S8:000 S10:002 S18:000 +CBST: 7,0,1 +CRLP: 61,61,78,6 +CR: 0 +FCLASS: 0 +CRC: 0 +CMGF: 1 +CSDH: 0 +CNMI: 0,0,0,0,1 +ILRR: 0 +IPR: 57600 +CMEE: 2 ^SMGO: 0,0 +CSMS: 0,1,1,1 ^SACM: 0,”000000”,”000000” ^SCKS: 0,1 ^SSET: 0 +CREG: 0,1 +CLIP: 0,2 +CAOC: 0 +COPS: 0,0,”operator” +CGSMS: 3 OK
ACTIVE PROFILE: E1 Q0 V1 X4 &C1 &D2 &S0 \Q0 S0:000 S3:013 S4:010 S5:008 S6:000 S7:060
S8:000 S10:002 S18:000 +CBST: 7,0,1 +CRLP: 61,61,78,6 +CR: 0 +FCLASS: 0 +ILRR: 0 +IPR: 57600 +CMEE: 2 ^SCKS: 0,1 ^SSET: 0 +CGSMS: 3 OK
MC39i_ATC_V01.02 Page 45 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
Table 9: AT&V responses on multiplex channels 2 / 3
PIN authentication done No PIN authentication
s
ACTIVE PROFILE: E1 Q0 V1 X4 &C1 &D0 &S0 \Q0 S0:000 S3:013 S4:010 S5:008 +CR: 0 +CRC: 0 +CMGF: 1 +CSDH: 0 +CNMI: 0,0,0,0,1 +ILRR: 0 +IPR: 19200 +CMEE: 2 ^SMGO: 0,0 +CSMS: 0,1,1,1 ^SACM: 0,”000000”,”000000” ^SCKS: 0,1 ^SSET: 0 +CREG: 0,1 +CLIP: 0,2 +CAOC: 0 +COPS: 0,0,”operator” +CGSMS: 3 OK
ACTIVE PROFILE: E1 Q0 V1 X4 &C1 &D0 &S0 \Q0 S0:000 S3:013 S4:010 S5:008 +CR: 0 +ILRR: 0 +IPR: 19200 +CMEE: 2 ^SCKS: 0,1 ^SSET: 0 +CGSMS: 3 OK
MC39i_ATC_V01.02 Page 46 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
2.38 AT&W Store current configuration to user defined profile
Execute command
AT&W[<n>]
Reference
V.25ter
TA stores the current settings to a user defined profile in the non-volatile memory.
Response
OK or if error is related to ME functionality: ERROR / +CME ERROR: <err>
Parameter
<n> 0 number of profile
Note
· The user defined profile will be loaded automatically after PowerUp. Use ATZ to restore user profile and AT&F to restore factory settings. Until the first use of AT&W, ATZ works as AT&F. See Chapter 2.32 for details on ATZ and Chapter
2.35 for AT&F.
· On each multiplexer channel you can save an individual profile.
Table 10: List of settings stored to user profile on ASC0 or multiplex channel 1
AT command Stored parameters
AT\Q <n> ATE <value> ATQ <n> ATS0 <n> ATS3 <n> ATS4 <n> ATS5 <n> ATS6 <n> ATS7 <n> ATS8 <n> ATS10 <n> ATS18 <n> ATV <value> ATX <value> AT&C <value> AT&D <value> AT&S <value> AT+ILRR <value> AT+FCLASS <n> AT+CBST <speed>, <name>, <ce> AT+CLIP <n> AT+CMEE <n> AT+COPS <format> AT+CR <mode> AT+CRC <mode> AT+CREG <n> AT+CRLP <iws>, <mws>, <T1>, <N2> AT+CMGF <mode> AT+CNMI <mode>, <mt>, <bm>, <ds>, <bfr>
MC39i_ATC_V01.02 Page 47 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
AT command Stored parameters
AT+CSDH <show> AT+CSMS <service> AT^SMGO <n> AT^SACM <n> AT^SCKS <n> AT^SSET <n>
Table 11: List of settings stored to user profile on multiplex channel 2 and 3
AT command Stored parameters
AT\Q <n> ATE <value> ATQ <n> ATS3 <n> ATS4 <n> ATS5 <n> ATV <value> ATX <value> AT&C <value> AT&D <value> AT&S <value> AT+CLIP <n> AT+CMEE <n> AT+COPS <format> AT+CR <mode> AT+CRC <mode> AT+CREG <n> AT+CMGF <mode> AT+CNMI <mode>, <mt>, <bm>, <ds>, <bfr> AT+CSDH <show> AT+CSMS <service> AT^SMGO <n> AT^SACM <n> AT^SCKS <n> AT^SSET <n>
s
MC39i_ATC_V01.02 Page 48 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
2.39 AT+GCAP Request complete TA capabilities list
Test command
AT+GCAP=?
Execute command
AT+GCAP
Reference
V.25ter
Response
OK
Parameter
Response
TA reports a list of additional capabilities.
+GCAP: <name>
OK
Parameter
<name> e.g.: +CGSM,+FCLASS
Note
+CGSM: The response text shows which GSM commands of the ETSI standard are supported.
s
2.40 AT+GMI Request manufacturer identification
Test command
AT+GMI=?
Execute command
AT+GMI
Reference
V.25ter
Response
OK
Response
TA reports information to identify the manufacturer.
SIEMENS OK
Note
See also ”AT+CGMI Request manufacturer identification”, Chapter 4.12.
2.41 AT+GMM Request TA model identification
Test command
AT+GMM=?
Execute command
AT+GMM
Reference
V.25ter
Response
OK
TA reports one or more lines of information text which permit the user to identify the specific model of device.
MC39i
OK
Note
See also ”AT+CGMM Request model identification”, Chapter 4.13.
MC39i_ATC_V01.02 Page 49 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
2.42 AT+GMR Request TA revision identification of software status
Test command
AT+GMR=?
Execute command
AT+GMR
Reference
V.25ter
Response
OK
Response
TA returns product software version identification text.
REVISION xx.yy OK
xx.yy Version xx and variant yy of software release.
Note
See also AT+CGMR Request revision identification of software status, Chapter
4.14.
2.43 AT+GSN Request TA serial number identification (IMEI)
Test command
AT+GSN=?
Execute command
AT+GSN
Parameter
Reference
V.25ter
Response
OK
Response
TA reports one or more lines of information text which permit the user to identify the individual device.
<sn>
OK
<sn> IMEI of the telephone (International Mobile station Equipment Identity)
Note
The serial number (IMEI) varies for every individual ME device.
MC39i_ATC_V01.02 Page 50 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
2.44 AT+ILRR Set TE-TA local rate reporting
Test command
AT+ILRR=?
Read command
AT+ILRR?
Write command
AT+ILRR= <value>
Intermediate result code
Reference
V.25ter
Example
Response
+ILRR: (list of supported <value>s) OK
Parameter
See write command
Response
+ILRR: <value> OK
Parameter
See write command
The write command specifies whether or not an intermediate result code shall in­dicate the currently used local rate when an incoming or outgoing data call is es­tablished. The message is transmitted from the DCE (= TA) to the DTE (=TE) be­fore the final result code of the connection setup (e.g. CONNECT) appears.
Response
OK
Parameter
<value> 0 Disables reporting of local port rate 1 Enables reporting of local port rate
+ILRR:<rate>
Parameter
<rate> port rate setting in bit per second 0 (Autobauding, see Chapter 2.45.1) 300 600 1200 2400 4800 9600 14400 19200 28800 38400 57600 115200 230400
Note
Factory default is 0
ATD”030112233445” +ILRR: 57600 CONNECT 9600/RLP
s
MC39i_ATC_V01.02 Page 51 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
2.45 AT+IPR Set fixed local rate
Test command
AT+IPR=?
Read command
AT+IPR?
Write command
AT+IPR=<rate>
Reference
V.25ter
Response
+IPR: (list of supported auto-detectable <rate>s), (list of supported fixed-only <rate>s) OK
Parameter
See write command
Response
+IPR: <rate> OK
Parameter
See write command
This command specifies the DTE-DCE bit rate. When you set a fix rate, make sure that both DTE (TE) and DCE (= TA) are configured to the same rate. When you select autobauding the DCE will automatically recognize the bit rate currently used by the DTE.
The setting is stored in the non-volatile memory and will be used whenever the engine is powered up again. However, in case of autobaud mode (AT+IPR=0) the detected DCE bit rate will not be saved and, therefore, needs to be re­synchronized after restarting the ME (see Chapter 2.45.1).
Response
OK or if error is related to ME functionality: ERROR / +CME ERROR: <err>
Parameter
<rate> bit rate per second 0 (Autobauding, see Chapter 2.45.1)
300 600 1200 2400 4800 9600 14400 19200 28800 38400 57600 115200 230400
Note
· Factory setting is AT+IPR=0 (autobauding). It cannot be restored with AT&F. The current setting will be preserved when you download new firmware or when the ME is powered down.
· In order to account for greater amounts of data it is recommended to choose a minimum bit rate of 2400 bps. If the ME is operated in Multiplex mode we sug­gest a minimum bit rate of 4800 bps. See Chapter 4.28 for AT+CMUX.
· A selected bit rate takes effect after the write command returns OK (except for Multiplex mode).
· In Multiplex mode, the write command AT+IPR=<rate> will not change the bit rate currently used, but the new bit rate will be stored and becomes active, when the module is restarted.
s
MC39i_ATC_V01.02 Page 52 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
· Generally, AT+IPR=x should be used as a standalone command. If neverthe- less combinations with other commands on the same line cannot be avoided, there are several constraints to be considered:
- Avoid combinations with the AT commands listed in Chapter 1.4.2.
- Take into account that a delay of 100 ms is required between a response to
the last command (e.g. OK) and the next command on the same line.
- When you enter AT+IPR=0, autobauding will be activated after the re-
sponse to the last command is received.
- When local echo is active (ATE1) and you enter AT+IPR=x with other
commands you may encounter the following problem: If switching to the new bit rate takes effect while a response is being transmitted, the last bytes may be sent at the new bit rate and thus, not properly transmitted. The following commands will be correctly sent at the new bit rate.
s
2.45.1 Autobauding
Synchronization between DTE and DCE
Ensure that DTE and DCE are correctly synchronized and the bit rate used by the DTE is detected by the DCE (= ME). To allow the bit rate to be synchronized simply issue an "AT" or "at" string. This is necessary
· after you have activated autobauding
· when you start up the module while autobauding is enabled. It is recommended to wait 3 to 5 sec-
onds before sending the first AT character. Otherwise undefined characters might be returned. If you want to use autobauding and autoanswer at the same time, you can easily enable the DTE-DCE synchronization, when you activate autobauding first and then configure the autoanswer mode (ATS0=n>0).
Restrictions on autobauding operation
· The serial interface has to be operated at 8 data bits, no parity and 1 stop bit (factory setting).
· The A/ command (and a/) cannot be used.
· Only the strings “AT“ or “at“ can be detected (neither “aT“ nor “At“).
· Unsolicited Result Codes that may be issued before the ME detects the new bit rate (by receiving
the first AT command string) will be sent at the previously detected bit rate. See further note below.
· It is not recommended to switch to autobauding from a bit rate that cannot be detected by the auto-
baud mechnism (e.g. 300 baud). Responses to +IPR=0 and any commands on the same line might
be corrupted.
Autobauding and bit rate after restart
The most recently detected bit rate cannot be stored when MC39i is powered down (with AT^SMSO). Therefore, each time the module is restarted the correct bit rate must be found as described above. Unless the bit rate is determined, the following constraints apply:
· An incoming CSD call or a network initiated GPRS request cannot be accepted. This must be taken
into account when autobauding and autoanswer mode (ATS0=n>0) are enabled at the same time,
especially if SIM PIN1 authentication is done automatically and the setting ATS0=n>0 is stored to
the user profile with AT&W (if not stored to the user profile ATS0 is reset to its default 000 after re-
start and thus not relevant for autobauding).
· Until the correct bit rate is found, URCs generated after restart will be output at 57600 bps. This
applies only to user defined URCs, such as “RING”, “+CREG”, “^SCKS”, “^SSIM” etc. (see list of
URCs in Chapter 9.1.4). The URCs "^SYSSTART" and "^SYSSTART ALARM MODE" will not be
indicated. Note: To avoid any problems caused by undetermined bit rates in the direction from DCE to DTE we strongly recommend to configure a fixed bit rate rather than using autobauding.
Autobauding and multiplex mode
If autobauding is active you cannot switch to multiplex mode (see Chapter 4.28).
MC39i_ATC_V01.02 Page 53 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
3 AT Commands for FAX
The following commands can be used for FAX transmission. If the ME is acting as a Fax modem to a PC-based application (e.g. “WinFax“) it is necessary to select the proper Service Class (Fax Class) provided by the ME. The ME reports its Service Class capabilities, the current setting and the range of services available. This is provided by the AT+FCLASS command (see pg. 58).
Table 12: Service Classes supported by ME
+FCLASS parameter Service Class Reference, Standard
0 Data modem 1 Service Class 1 EIA/TIA-578-A 2 Manufacture specific This document and EIA PN-
Notes:
· When sending a FAX with a standard FAX application for Personal Computers it is recommended
to use autobauding (AT+IPR=0).
· Responses that may occur during a fax call are presented in the form of Unsolicited Result Codes
(URCs). A summary of Fax specific URCs is listed in Chapter 9.1.4, Table 20.
The following AT commands are dummy commands. Invoking these commands will not cause ER­ROR result codes, but the commands have no functionality.
AT+FAA Auto Answer mode AT+FECM Error Correction Mode control AT+FLNFC Page Length format conversion AT+FLPL Indicate document available for polling AT+FMINSP Minimum Phase C speed AT+FRBC Phase C data receive byte count AT+FREL Phase C received EOL alignment AT+FSPL Enable polling AT+FTBC Phase C data transmit byte count AT+FWDFC Page width format conversion
e.g. TIA/EIA-602 or ITU V.25ter
2388 (draft)
MC39i_ATC_V01.02 Page 54 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
3.1 AT+FBADLIN Bad Line Threshold
Read command
AT+FBADLIN?
Write command
AT+FBADLIN= <badlin>
Reference
EIA PN-2388
This command defines the “Copy-Quality-OK”-threshold. If <badline> consecu­tive lines have pixel count errors in normal resolution (98 dpi) mode, then the copy quality is unacceptable. If <badline> * 2 consecutive lines have pixel count errors in fine resolution (196 dpi) mode, then the copy quality is unacceptable. “Copy Quality Not OK” occurs if either the error percentage is too high or too many consecutive lines contain errors. A value of 0 implies that error checking is not present or disabled.
Response
<badlin> OK
Parameter
See write command
Response
OK
If error is related to ME functionality:
ERROR
Parameter
<badlin> 0 – 10 – 255 bad lines
Note
Used for Fax Class 2 only
s
3.2 AT+FBADMUL Error Threshold Multiplier
Read command
AT+FBADMUL?
Write command
AT+FBADMUL= <n>
Reference
EIA PN-2388
This command defines the “Copy-Quality-OK” multiplier. The number of lines received with a bad pixel count is multiplied by this number. If the result ex­ceeds the total number of lines on the page the error rate is considered too high. A threshold multiplier value of 20 corresponds to a 5% error rate. A value of 0 implies that error checking is not present or disabled.
Response
<badmul> OK
Parameter
See write command
Response
OK
If error is related to ME functionality:
ERROR
Parameter
<n> 0 – 20 – 255
Note
Used for Fax Class 2 only
MC39i_ATC_V01.02 Page 55 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
3.3 AT+FBOR Query data bit order
Test command
AT+FBOR=?
Read command
AT+FBOR?
Write command
AT+FBOR=<bor>
Reference
EIA PN-2388
Query the bit order for receive mode. The mode is set by the ME depending on the selected Service Class, see “AT+FCLASS Fax: Select, read or test service class”, pg. 58.
Response
(list of supported bit order modes <bor>s)
OK
Parameter
See write command
Response
<bor> OK
Parameter
See write command
Response
OK
Parameter
<bor> 0 direct bit order for both Phase C and for Phase B/D data. [1] Reversed bit order for Phase C data, direct Bit Order for
Phase B/D data.
Note
Used for Fax Class 2 only
s
MC39i_ATC_V01.02 Page 56 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
3.4 AT+FCIG Query or set the Local polling id
Test command
AT+FCIG =?
Read command
AT+FCIG?
Write command
AT+FCIG =<id>
Reference
EIA PN-2388
Response
(max. length of Local Polling ID string) (range of supported ASCII character values) OK
Parameter
See write command
Response
<id> OK
Parameter
See write command
Response
OK
Parameter
<id> Local Polling ID string, max. length and possible content as reported
by test command. Default value is empty string (“”).
Note
See also “AT+FLID Query or set the Local Id setting capabilities”, pg. 64. Used for Fax Class 2 only
s
MC39i_ATC_V01.02 Page 57 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
3.5 AT+FCLASS Fax: Select, read or test service class
Test command
AT+FCLASS=?
Read command
AT+FCLASS?
Write command
AT+FCLASS= <n>
Reference
EIA/TIA-592-A
See introduction to fax commands, pg. 54.
Response
(list of supported <n>s) OK
Parameter
See write command
Response
<n> OK
Parameter
See write command
The ME is set to a particular mode of operation (data, fax). This allows the ME to process information in a manner suitable for that type of information.
Response
OK
Parameter
<n> [0] data (e.g. EIA/TIA-602 or ITU V.25ter)
1 Fax Class 1 (EIA/TIA-578-A, Service Class 1) 2 Fax Class 2 (EIA/TIA SP-2388, an early draft version of
EIA/TIA-592-A – Service class 2.1)
Note
· Using Error Correcting Mode (ECM) when sending FAXes over GSM should be avoided.
· If AT+FCLASS setting is 1 or 2, all incoming calls will be answered as fax calls, when ATA is issued on multiplexer channel 1 resp. ASC0. For calls explicitly signaled as voice or data calls, this procedure will fail with result code “NO CARRIER”, but the incoming call will continue to ring. It is possi­ble to change the AT+FCLASS setting to 0 while the call is ringing and to accept the call afterwards with ATA.
s
MC39i_ATC_V01.02 Page 58 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
3.6 AT+FCQ Copy Quality Checking
Test command
AT+FCQ =?
Read command
AT+FCQ?
Write command
AT+FCQ =<cq>
Reference
EIA PN-2388
This command controls Copy Quality checking when receiving a fax.
Response
(list of supported copy quality checking <cq>s)
OK
Parameter
See write command
Response
<cq> OK
Parameter
See write command
Response
OK
Parameter
<cq> 0 No copy quality checking. The ME will generate Copy Qual-
ity OK (MCF) responses to complete pages.
[1] ME can check 1-D phase data. The connected application
must check copy quality for 2-D phase C data
Note
Used for Fax Class 2 only.
s
3.7 AT+FCR Capability to receive
Write command
AT+FCR=<cr>
Reference
EIA PN-2388
Response
OK
Parameter
<cr> [0] ME will not receive message data. This can be used when
the application has insufficient storage. The ME can send and can be polled for a file.
1 ME can receive message data.
Note
Used for Fax Class 2 only
MC39i_ATC_V01.02 Page 59 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
3.8 AT+FDCC Query or set capabilities
Test command
AT+FDCC =?
Read command
AT+FDCC?
Write command
AT+FDCC=<VR>, <BR>,<WD>,<LN>, <DF>,<EC>,<BF>, <ST>
Reference
EIA PN-2388
This command allows the connected application to sense and constrain the capabilities of the facsimile DCE (=ME), from the choices defined in CCITT T.30 Table 2.
Response
(list of <VR>s), (list of <BR>s), (list of <WD>s), (list of <LN>s), (list of <DF>s), (list of <EC>s), (list of <BF>s), (list of <ST>s)
OK
Parameter
VR: Vertical Resolution, BR: Bit Rate, WD: Page Width, LN: Page Length, DF: Data Compression Format, EC: Error Correction Mode, BF: Binary File Trans­fer Mode, ST: Scan Time/Line.
Note: For further information see AT+FDIS, pg. 62
Response
<VR>,<BR>,<WD>,<LN>,<DF>,<EC>,<BF>,<ST> OK
Parameter
See write command
Response
OK
Parameter
VR: Vertical Resolution, BR: Bit Rate, WD: Page Width, LN: Page Length, DF: Data Compression Format, EC: Error Correction Mode, BF: Binary File Trans­fer Mode, ST: Scan Time/Line.
Note: For further information see AT+FDIS, pg. 62
Note
Used for Fax Class 2 only
s
MC39i_ATC_V01.02 Page 60 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
3.9 AT+FDFFC Data Compression Format Conversion
Test command
AT+FDFFC=?
Read command
AT+FDFFC?
Write command
AT+FDFFC =<df>
Reference
EIA PN-2388
This parameter determines the ME response to a mismatch between the data format negotiated for the facsimile session, reported by the +FDCS:DF sub­parameter, and the Phase C data desired by the controlling application, indi­cated by the optional +FDT:DF subparameter, or the +FDIS=DF subparameter for the +FDR operation.
Response
(list of supported <df>s) OK
Parameter
See write command
Response
<df> OK
Parameter
See write command
Response
OK
Parameter
<df> [0] Mismatch checking is always disabled. The controlling ap-
plication has to check the +FDCS: DF subparameter and transfer matching data.
Note
Used for Fax Class 2 only
s
MC39i_ATC_V01.02 Page 61 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
3.10 AT+FDIS Query or set session parameters
Test command
AT+FDIS =?
Read command
AT+FDIS?
Write command
AT+FDIS = <VR>,<BR>,<WD>, <LN>,<DF>,<EC>, <BF>,<ST>
Reference
EIA PN-2388
This command allows the controlling application to sense and constrain the capabilities used for the current session. It uses +FDIS to generate DIS or DTC messages directly, and uses +FDIS and received DIS messages to gen­erate DCS messages.
Response
(list of <VR>s), (list of <BR>s), (list of <WD>s), (list of <LN>s), (list of <DF>s), (list of <EC>s), (list of <BF>s), (list of <ST>s)
Parameter
See write command
Response
<VR>,<BR>,<WD>,<LN>,<DF>,<EC>,<BF>,<ST>
OK
Parameter
See write command
Response
OK
Parameter
Vertical Resolution VR 0 normal, 98 lpi 1 fine, 196 lpi
Bit Rate BR 0 2400 bit/s, V.27ter 1 4800 bit/s, V.27ter 2 7200 bit/s, V.29 3 9600 bit/s, V.29
Page Width WD 0 *) 1728 pixels in 215mm 1 2048 pixels in 255 mm 2 2432 pixels in 303 mm 3 1216 pixels in 151 mm 4 864 pixels in 107 mm
Page Length LN 0 A4, 297mm 1 B4, 364mm 2 unlimited length
Data Compression Format DF 0 *) 1-D modified Huffman 1 2-D modified read 2 2-D uncompressed mode
Error correction EC 0 *) disable ECM (Annex A/T.30) 1 enable ECM, 64 bytes/frame 2 enable ECM, 256 bytes/frame
Binary File mode BF 0 *) disable BFT Transfer Mode 1 enable BFT
Scan Time/Line ST 0 *) 0 ms (at VR= normal) 1 5 ms 2 10 ms 3 10 ms 4 20 ms 5 20 ms 6 40 ms 7 40 ms
*) Note: Only the default value needs to be implemented. Use test command to check which parameter values are really possible.
Note
Used for Fax Class 2 only
s
MC39i_ATC_V01.02 Page 62 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
3.11 AT+FDR Begin or continue phase C data reception
Execute command
AT+FDR
Reference
EIA PN-2388
The +FDR command initiates transition to Phase C data reception.
Response
CONNECT
or
OK
If error is related to ME functionality:
ERROR
Note
Used for Fax Class 2 only
3.12 AT+FDT Data Transmission
Execute command
AT+FDT
Write command
AT+FDT= <DF>,<VR>,<BR>, <WD>,<LN>
Reference
EIA PN-2388
This command requests the ME to transmit a Phase C page. When the ME is ready to accept Phase C data, it issues the negotiation responses and the CONNECT result code to the application.
In Phase B, the +FDT command releases the ME to proceed with negotiation, and releases the DCS message to the remote station. In Phase C, the +FDT command resumes transmission after the end of a data stream transmited be­fore.
Response
CONNECT
Response
CONNECT
Parameter
<dt> DF,VR,BR,WD,LN comma separated parameter list
Data Compression Format DF 0 1-D modified Huffman 1 2-D modified read 2 2-D uncompressed mode
Vertical Resolution VR 0 normal, 98 lpi 1 fine, 196 lpi
Bit Rate BR 0 2400 bit/s, V.27ter 1 4800 bit/s, V.27ter 2 7200 bit/s, V.29 3 9600 bit/s, V.29
Page Width WD 0 1728 pixels in 215mm 1 2048 pixels in 255 mm 2 2432 pixels in 303 mm 3 1216 pixels in 151 mm 4 864 pixels in 107 mm
Page Length LN 0 A4, 297mm 1 B4, 364mm 2 unlimited length
Note
Used for Fax Class 2 only
s
MC39i_ATC_V01.02 Page 63 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
3.13 AT+FET End a page or document
Write command
AT+FET=<ppm>
Reference
EIA PN-2388
This command indicates that the current page or partial page is complete. An ERROR response code results if this command is issued while the mode is on­hook.
Response
OK
Parameter
<ppm> Post Page Message Codes
1 another document next 2 no more pages or documents 4 another page, procedure interrupt 5 another document, procedure interrupt
Note
Used for Fax Class 2 only
3.14 AT+FK Kill operation, orderly FAX abort
Execute command
AT+FK
Reference
This command causes the TA to terminate the session in an orderly manner.
Response
OK
Note
Used for Fax Class 2 only
s
3.15 AT+FLID Query or set the Local Id setting capabilities
Test command
AT+FLID =?
Read command
AT+FLID?
Write command
AT+FLID =<lid>
Reference
EIA PN-2388
Response
(max. character length of Local ID string) (range of supported ASCII character values) OK
Parameter
See write command
Response
< lid > OK
Parameter
See write command
Response
OK
Parameter
<lid> Local ID string, max. length and possible content as reported by test
command. Default value is empty string (“”).
Note
See also “AT+FCIG Query or set the Local polling id”, pg. 56. Used for Fax Class 2 only
MC39i_ATC_V01.02 Page 64 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
3.16 AT+FMDL Identify Product Model
Read command
AT+FMDL?
Reference
Siemens
Send the model identification to the TA
Response
Gipsy Soft Protocolstack OK
Note
Used for Fax Class 2 only
3.17 AT+FMFR Request Manufacturer Identification
Read command
AT+FMFR?
Reference
Siemens
Send the manufacturer identification to the TA
Response
SIEMENS OK
Note
Used for Fax Class 2 only
s
3.18 AT+FOPT Set bit order independently
Write command
AT+FOPT=<opt>
Reference
Siemens
Model specific command to set bit order independently of the understanding which is "mirrored" and which is direct.
Response
OK
Parameter
<opt> 0 non-standard
1 standard
Note
Used for Fax Class 2 only
MC39i_ATC_V01.02 Page 65 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
3.19 AT+FPHCTO DTE Phase C Response Timeout
Read command
AT+FPHCTO?
Write command
AT+FPHCTO= <tout>
Reference
EIA PN-2388
The time-out value <tout> determines how long the DCE will wait for a command after reaching the end of data when transmitting in Phase C. When time-out is reached, the DCE assumes that there are no more pages or documents to send.
Response
<tout> OK
Parameter
See write command
Parameter
<tout> 0 – 30 – 255 time-out value in 100ms units.
Response
OK
If error is related to ME functionality:
ERROR
Note
Used for Fax Class 2 only
s
3.20 AT+FREV Identify Product Revision
Test command
AT+FREV?
Reference
Siemens
Sends the revision identification to the TA
Response
V2.550
OK
Note
Used for Fax Class 2 only
3.21 AT+FRH Receive Data Using HDLC Framing
Execute command
AT+FRH=<mod>
Reference
TIA/EIA-578
This command causes the TA to receive frames using the HDLC protocol and the modulation defined below. An ERROR response code results if this command is issued while the modem is on-hook.
Response
CONNECT
If error is related to ME functionality:
ERROR
Parameter
<mod> modulation mode 3 V21 Ch2 300 bps 24 V.27ter 2400 bps 48 V.27ter 4800 bps 72 V.29 7200 bps 96 V.29 9600 bps
Note
Used for Fax Class 1 only
MC39i_ATC_V01.02 Page 66 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
3.22 AT+FRM Receive Data
Test command
AT+FRM=?
Write command
AT+FRM=<mod >
Reference
TIA/EIA-578
Response
(List of supported modulation modes <mod>s) OK
Parameter
See write command This command causes the TA to enter the receive mode using the modulation
defined below. An ERROR response code results if this command is issued while the modem is on-hook.
Response
CONNECT
If error is related to ME functionality:
ERROR
Parameter
<mod> 96 V.29 9600 bps 72 V.29 7200 bps 48 V.27ter 4800 bps 24 V.27ter 2400 bps
Note
Used for Fax Class 1 only
s
3.23 AT+FRS Receive Silence
Write command
AT+FRS=<time>
Reference
TIA/EIA-578
+FRS=n causes the TA to report an OK result code to the TE after <time> 10 mil- lisecond intervals of silence have been detected on the line. This command is aborted if any character is received by the DTE. The modem discards the abort­ing character and issues an OK result code. An ERROR response code results if this command is issued while the mode is on-hook.
Response
OK
If error is related to ME functionality:
ERROR
Parameter
<time> 0 – 255 no. of 10 millisecond intervals
Note
Used for Fax Class 1 only
3.24 AT+FTH Transmit Data Using HDLC Framing
Write command
AT+FTH=<mod>
Reference
TIA/EIA-578
This command causes the TA to transmit data using HDLC protocol and the modulation mode defined below. An ERROR response code results if this com­mand is issued while the modem is on-hook.
Response
CONNECT
Parameter
<mod> 3 V.21 Ch2 300 bps
Note
Used for Fax Class 1 only
MC39i_ATC_V01.02 Page 67 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
3.25 AT+FTM Transmit Data
Test command
AT+FTM=?
Write command
AT+FTM=<mod>
Reference
TIA/EIA-578
Response
(List of supported modulation modes) OK
Parameter
See write command
This command causes the TA to transmit data using the modulation mode de­fined below. An ERROR response code results if this command is issued while the modem is on-hook.
Response
CONNECT
If error is related to ME functionality:
ERROR
Parameter
<mod> modulation mode 96 V.29 9600 bps 72 V.29 7200 bps 48 V.27ter 4800 bps 24 V.27ter 2400 bps
Note
Used for Fax Class 1 only
s
3.26 AT+FTS Stop Transmission and Wait
Write command
AT+FTS=<time>
Reference
TIA/EIA-578
This command causes the TA to terminate a transmission and wait for <time> 10 millisecond intervals before responding with the OK result code to the DTE.
Response
An ERROR response code results if this command is issued while the modem is on-hook.
Parameter
<time> 0 – 85 no. of 10 millisecond intervals
Note
Used for Fax Class 1 only
MC39i_ATC_V01.02 Page 68 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
3.27 AT+FVRFC Vertical resolution format conversion
Test command
AT+FVRFC =?
Read command
AT+FVRFC?
Write command
AT+FVRFC =<vrfc>
Reference
EIA PN-2388
This command determines the DCE response to a mismatch between the vertical resolution negotiated for the facsimile session and the Phase C data desired by the DTE.
Response
(List of supported mismatch checking modes) OK
Parameter
See write command
Response
<vrfc> OK
Parameter
See write command
Response
OK
Parameter
<vrfc> 0 disable mismatch checking. [2] enable mismatch checking, with resolution conversion of 1-D
data in the DCE, and an implied AT+FK command executed on 2-D mismatch detection
Note
Used for Fax Class 2 only
s
MC39i_ATC_V01.02 Page 69 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
4 AT Commands originating from GSM 07.07
These AT Commands are according to ETSI (European Telecommunications Standards Institute) GSM 07.07 document.
4.1 AT+CACM Accumulated call meter (ACM) reset or query
Test command
AT+CACM=?
Read command
AT+CACM?
Write command
AT+CACM= [<passwd>]
Reference
GSM 07.07
Response
OK
Parameter
Response
TA returns the current ACM value.
+CACM: <acm> OK
If error is related to ME functionality:
+CME ERROR: <err>
Parameter
<acm> string type; three bytes of the current ACM value in hexadecimal for-
mat (e.g. “00001E” indicates decimal value 30) 000000 – FFFFFF
Parameter
<passwd> string type: SIM PIN2
Response
TA resets the Advice of Charge related to the accumulated call meter (ACM) value in SIM file EF(ACM). ACM contains the total number of home units both for the current and preceding calls.
OK
If error is related to ME functionality:
+CME ERROR: <err>
MC39i_ATC_V01.02 Page 70 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
4.2 AT+CALA Set alarm time
Test command
AT+CALA=?
Read command
AT+CALA?
Write command
AT+CALA=<time> [,<n>[,<type> [,<text>]]]
Test command returns supported array index values <n>, alarm types <type>, and maximum length of the text <tlength> to be output.
Response
+CALA: (list of supported <n>s), (list of supported <type>s), (range of sup­ported <tlength>) OK
If error is related to ME functionality:
+CME ERROR: <err>
Parameter
See write command
Read command returns the list of current active alarm settings in the ME.
Response
+CALA: <time>[,<n>[,<type>[,<text>]]]
If error is related to ME functionality:
+CME ERROR: <err>
Parameter
See write command
The write command sets an alarm time in the ME. When the alarm is timed out and executed the ME returns an Unsolicited Result Code (URC) and the alarm time is reset to “00/01/01,00:00:00”.
The alarm can adopt two functions, depending on whether or not you switch the GSM engine off after setting the alarm:
Reminder message:
You can use the alarm function to generate reminder mes­sages. For this purpose, set the alarm as described below and do not switch off or power down the ME. When executed the message comes as an Unsolicited Result Code.
Alarm mode: You can use the alarm function to restart the ME when pow-
ered down. For this purpose, set the alarm as described below. Then power down the ME by entering the AT^SMSO command (see Chapter 8.23). When the alarm time is reached, the ME will wake up to Alarm mode. To prevent the ME from uninten­tionally logging into the GSM network, Alarm mode provides re­stricted operation. Upon wake-up, the ME indicates an Unsolic­ited Result Code which reads: ^SYSSTART ALARM MODE. A limited number of AT commands is available during Alarm mode: AT+CCLK, AT+CALA, AT^SBC, AT^SCTM, AT^SMSO. The ME remains deregistered from the GSM network. If you want the ME to return to full operation (normal operating mode) it is necessary to drive the ignition line (IGT pin of application interface) to ground. For details please refer to [1].
Response
OK
If setting fails: +CME ERROR: <err> Refer to Chapter 9.1.1, pg. 285, for <err> values.
s
MC39i_ATC_V01.02 Page 71 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
Parameter
<time> string type value; format is "yy/MM/dd,hh:mm:ss", where characters
<n> Integer type value indicating the array index of the alarm.
<type> Integer type value indicating the type of the alarm
<text> String type value indicating the text to be displayed when alarm time
<tlength> integer type value indicating the maximum length of <text>. The
Unsolicited result code
Reference
GSM 07.07
Indicates reminder message:
+CALA: <text>
Indicates ME wake-up into Alarm mode:
^SYSSTART ALARM MODE
+CALA: <text>
If autobauding is active (AT+IPR=0) the URC “^SYSSTART ALARM MODE” does not appear, but your individual text message “+CALA: <text>” will be dis­played.
Note
· After the alarm was executed the parameter <time> of AT+CALA will be re­set to "00/01/01,00:00:00", but <text> will be preserved as described above.
· If MC39i is totally disconnected from power supply the most recently saved configuration of +CALA: <time>[,<n>[,<type>[,<text>]]] will be presented when MC39i is powered up.
· Each time MC39i is restarted it takes 2s to re-initialize the RTC and to up­date the current time. Therefore, it is recommended to wait 2s before using the commands AT+CCLK and AT+CALA (for example 2s after ^SYSSTART has been output).
· Alarm settings on different Multiplexer channels (see Chapter 4.28):
- On each channel an individual <text> message can be stored, but only
s
indicate year (two last digits), month, day, hour, minutes. E.g. 6th of May 2003, 22:10:00 hours equals to “03/05/06,22:10:00" (see also AT+CCLK in Chapter 4.7). Note: if <time> equals current date and time or is to an earlier date, TA returns +CME ERROR: <21>.
The ME allows to set only one alarm at a time. Therefore, the list of supported alarm events indicated by the test command AT+CALA=? is <n>=0. If a second alarm time is set, the previous alarm will be de­leted. Therefore, the read command AT+CALA? will always return <n>=0. This is also true if individual settings are made on the various Multiplexer channels, for details see notes below.
0 Alarm indication: text message via serial interface
is reached; maximum length is <tlength>. By factory default, <text> is undefined.
Note: <text> will be stored to the non-volatile flash memory when the
device enters the Power Down mode via AT^SMSO (pg. 243). Once saved, it will be available upon next power-up, until you overwrite it by typing another text. This eliminates the need to enter the full string when setting a fresh alarm. For text coding see Chapters 1.5 and 9.5.
maximum length is 16.
one time setting applies. This means an alarm <time> set on one of the
MC39i_ATC_V01.02 Page 72 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
- When the alarm is timed out and executed the ME sends the URC only
Examples
Example 1:
You may want to configure a reminder message for May 31, 2003, at 9.30h, in­cluding the message "Good Morning".
Write command:
AT+CALA="03/05/31,09:30:00",0,0,"Good Morning" OK
Do not switch off the GSM engine. When the alarm is executed the ME returns the following URC:
+CALA: Good Morning
Example 2:
To set a fresh alarm using the same message as in Example 1, simply enter date and time. <n>, <type>, <text>, <tlength> can be omitted:
AT+CALA="03/05/31,08:50:00" OK When the alarm is executed the URC comes with the same message: +CALA: Good Morning
Example 3:
To configure the alarm mode, e.g. for May 20, 2003, at 8.30h, enter
AT+CALA="03/05/20,08:30:00" OK
Next, power down the ME:
AT^SMSO ^SMSO: MS OFF
When the alarm is executed the ME wakes up to Alarm mode and displays a URC. If available, this line is followed by the individual <text> most recently saved. If no individual message was saved only the first line appears.
^SYSSTART ALARM MODE +CALA: Good Morning
s
channels overwrites the time setting on all remaining channels. There­fore, the total number of alarm events returned by the read command AT+CALA? will always be <n>=0, no matter whether different text mes­sages are stored.
on the channel where the most recent alarm setting was made. The alarm time will be reset to “00/01/01,00:00:00” on all channels.
Table 13: Summary of AT commands available in Alarm mode
AT command Use
AT+CALA Set alarm time AT+CCLK Set date and time of RTC AT^SBC Enable / disable presentation of URC ^SBC for indication of undervoltage
Query average current consumption of MC39i AT^SCTM Query temperature of GSM engine AT^SMSO Power down GSM engine
MC39i_ATC_V01.02 Page 73 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
4.3 AT+CAMM Accumulated call meter maximum (ACMmax) set or query
Test command
AT+CAMM=?
Read command
AT+CAMM?
Write command
AT+CAMM= [<acmax>[,<passwd>]]
Reference
GSM 07.07
Response OK Parameter
Response
TA returns the current ACMmax value.
+CAMM: <acmmax> OK
If error is related to ME functionality:
+CME ERROR: <err>
Parameter
See write command
Response
TA sets the Advice of Charge related to the accumulated call meter maxi­mum value in SIM file EF (ACMmax). ACMmax contains the maximum number of home units allowed to be consumed by the subscriber.
OK
If error is related to ME functionality:
+CME ERROR: <err>
Parameter
<acmmax> string type; three bytes of the max. ACM value in hexadeci-
mal format (e.g. “00001E” indicates decimal value 30) 000000 disable ACMmax feature 000001-FFFFFF
<passwd> string type SIM PIN2
Note
MC39i_ATC_V01.02 Page 74 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
4.4 AT+CAOC Advice of Charge information
Test command
AT+CAOC=?
Read command
AT+CAOC?
Write command
AT+CAOC=<mode>
Execute command
AT+CAOC
Reference
GSM 07.07
Response
+CAOC: (list of supported <mode>s) OK
Parameter
See write command
Response
+CAOC: <mode> OK
Parameter
See write command
Response
TA sets the Advice of Charge supplementary service function mode. If error is related to ME functionality:
+CME ERROR: <err> If <mode>=0, TA returns the current call meter value
OK
Parameter
<mode> 0 query CCM value <ccm> string type; three bytes of the current CCM value in hexadecimal
format (e.g. “00001E” indicates decimal value 30); bytes are simi­larly coded as ACMmax value in the SIM 000000-FFFFFF
Response
TA returns the current call meter value If error is related to ME functionality:
+CME ERROR: <err> If <mode>=0, TA returns the current call meter value
+CAOC: <ccm> OK
Parameter
See write command
Note
s
MC39i_ATC_V01.02 Page 75 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
4.5 AT+CBST Select bearer service type
Test command
AT+CBST=?
Read command
AT+CBST?
Write command
AT+CBST= <speed>[,<name> [,<ce>]]
Reference
GSM 07.07
Response
+CBST: (list of supported <speed>s),(list of supported <name>s),(list of sup­ported <ce>s) OK
Parameter
See write command
Response
+CBST: <speed>,<name>,<ce>
OK
Parameter
See write command
Response
TA selects the bearer service <name>, the data rate <speed> and the connec­tion element <ce> to be used when data calls are originated. The settings also apply to mobile terminated data calls, especially when single numbering scheme calls or calls from analog devices are received (see also Chapter
4.45).
OK
Parameter
<speed> 0 autobauding 4 2400 bps ( V.22bis) 6 4800 bps ( V.32) 7 9600 bps (V.32) 14 14400 bps (V.34) 68 2400 bps (V.110) 70 4800 bps (V.110) 71 9600 bps (V.110) 75 14400 bps (V.110)
<name> 0 asynchronous modem <ce> 1 non-transparent
Transparent mode is not supported.
Note
· GSM 02.02[1]: List of allowed combinations of subparameters.
· The PLMN influences the second air interface (to the terminator), therefore
another mode may be established by the network.
s
MC39i_ATC_V01.02 Page 76 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
4.6 AT+CCFC Call forwarding number and conditions control
Test command
AT+CCFC=?
Write command
AT+CCFC=<reas>, <mode>[,<number> [,<type>[,<class> [,<time>]]]]
Response
+CCFC: (list/range of supported <reas>s) OK
Parameter
See execute command
Response
TA controls the call forwarding supplementary service. Registration, erasure, activation, deactivation and status query are supported.
If <mode> ¹ 2 and command successful:
OK
If <mode> = 2, <reas> ¹ 2 and command successful:
+CCFC: <status>, <class1>[, <number>, <type>]
[<CR><LF>+CCFC: ....] OK
If <mode> = 2, <reas> = 2 and command successful:
+CCFC: <status>, <class1>[, <number>, <type> [, <time>]]
[<CR><LF>+CCFC: ....] OK
If error is related to ME functionality:
+CME ERROR: <err>
Parameter
<reas> 0 unconditional 1 mobile busy 2 no reply 3 not reachable 4 all call forwarding (includes reasons 0, 1, 2 and 3) 5 all conditional call forwarding (includes reasons 1, 2 and 3)
<mode> 0 disable call forwarding 1 enable call forwarding 2 query status of call forwarding 3 register <number> and activate call forwarding 4 erase <number> and deactivate call forwarding
<number> string type phone number of forwarding address in format speci-
fied by <type>. If you select <mode> = 3, the phone <number> will be registered in the network. This allows you to disable / enable CF to the same destination without the need to enter the phone number once again. Depending on the services offered by the provider the registration may be mandatory before CF can be used. The number remains registered in the network until you register an­other number or erase it using <mode> = 4.
<type> type of address in integer format; default 145 when dialing string in-
cludes international access code character “+”, otherwise 129
MC39i_ATC_V01.02 Page 77 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
<class> integer or sum of integers each representing a <class> of informa-
1 voice 2 data 4 fax 8 short message service 16 data circuit sync 32 data circuit async 64 dedicated packet access 128 dedicated PAD access x combination of some of the above classes. For example, the default setting 7 represents the sum of
<time> time to wait before call is forwarded, rounded to a multiple of 5 sec..
1...20..30 (only for <reas>=no reply)
<status> 0 not active 1 active
Reference
GSM 07.07 GSM 02.04 GSM 02.82 GSM 03.82 GSM 04.82
Note
· You can register, disable, enable and erase <reas> 4 and 5 as described above. However, querying the status of <reas> 4 and 5 with AT+CCFC will result in an error (“CME error: Operation not supported”). As an alternative, you may use the ATD command followed by *'# codes to check the status of these two reasons. See Chapter 9.4 for a complete list of *# GSM codes. See also examples below.
· The AT+CCFC command offers a broad range of call forwarding options according to the GSM specifications. However, when you attempt to set a call forwarding option which is not provisioned or not yet subscribed to, the setting will not take effect regardless of the response returned. The re­sponses in these cases vary with the network (for example “OK”, “Opera­tion not allowed”, “Operation not supported” etc.). To make sure check the call forwarding status with <mode>=2.
· <class> 2 (data) comprises all those <class> values between 16 and 128, that are supported both by the network and the MS. This means, a setting made for <class> 2 applies to all remaining data classes (if supported). In addition, you can assign a different setting to a specific class. For exam­ple, you can activate Call Forwarding for all data classes, but deactivate it for a specific data class.
· The command has been implemented with the full set of <class> parame­ters according to GSM 07.07. For actual applicability of SS “call forward­ing” to a specific service or service group (a specific <class> value) please consult table A.1 of GSM 02.04.
· Most networks will not permit registration of new parameters for conditional call forwarding (reasons 1,2,3,5) while unconditional call forwarding is en­abled.
s
tion:
the integers 1, 2 and 4 (CF for voice, data and fax). The value 255 covers all classes. If the <class> parameter is omitted, the default value 7 is used.
MC39i_ATC_V01.02 Page 78 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
4.6.1 Examples: Call forwarding
Please note that when you configure or query call forwarding without specifying any classes, the set­tings will refer to classes 1, 2 and 4 only (=default).
Example 1
Example 2
Example 3
Example 4
Example 5
To register the destination number of unconditional call forwarding (CFU) for the default classes voice, data and fax:
at+ccfc=0,3,"+493012345678",145 OK
Remember that call forwarding will be activated when you register the desti­nation number.
To query the status of CFU without specifying <class>:
at+ccfc=0,2 +CCFC: 1,1,"+493012345678",145 +CCFC: 1,2,"+493012345678",145 +CCFC: 1,4,"+493012345678",145 OK
To deactivate CFU without specifying <class>:
at+ccfc=0,0 OK
To check whether CFU was successfully deactivated (note that the destina­tion number remains registered in the network when you disable CFU):
at+ccfc=0,2 +CCFC: 0,1,"+493012345678",145 +CCFC: 0,2,"+493012345678",145 +CCFC: 0,4,"+493012345678",145 OK
To erase the registered CFU destination number:
at+ccfc=0,4 OK
Now, when you check the status, no destination number will be indicated:
at+ccfc=0,2 +CCFC: 0,1 +CCFC: 0,2
+CCFC: 0,4
To query the status of CFU for all classes:
at+ccfc=0,2,,,255
+CCFC: 0,1 +CCFC: 0,2 +CCFC: 0,4 +CCFC: 0,8 +CCFC: 0,16 +CCFC: 0,32 +CCFC: 0,64 +CCFC: 0,128
OK
MC39i_ATC_V01.02 Page 79 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
Example 6
<reas>=4 or 5 cannot be used to query the status of all call forwarding rea­sons (see also notes above):
at+ccfc=4,2 +CME error: operation not supported
at+ccfc=5,2 +CME error: operation not supported
s
MC39i_ATC_V01.02 Page 80 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
4.7 AT+CCLK Real Time Clock
Test command
AT+CCLK=?
Read command
AT+CCLK?
Write command
AT+CCLK=<time>
Reference
GSM 07.07
Response
OK
Response
+CCLK: <time>
OK / ERROR / +CME ERROR
Parameter:
<time>: string type value; format is "yy/MM/dd,hh:mm:ss", where characters
indicate year (two last digits), month, day, hour, minutes, seconds; e.g. 6th of May 2003, 22:10:00 hours equals to “03/05/06,22:10:00"
Response
OK / ERROR / +CME ERROR
Parameter:
<time> see read command
Note
· Each time MC39i is restarted it takes 2s to re-initialize the RTC and to up­date the current time. Therefore, it is recommended to wait 2s before using the commands AT+CCLK or AT+CALA command (for example 2s after ^SYSSTART has been output).
· <time> is retained if the device enters the Power Down mode via AT^SMSO (pg. 245).
· <time> will be reset to its default value if power is totally disconnected. In this case, the clock starts with <time> = “02/01/01,00:00:00” upon next power-up.
· See AT+CALA, pg. 71.
s
MC39i_ATC_V01.02 Page 81 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
4.8 AT+CCUG: Closed User Group
Test command
AT+CCUG=?
Read command
AT+CCUG?
Write command
AT+CCUG=[[<n>[, <index>[,<info>]]
Reference
GSM 02.85, GSM 03.85, GSM 04.85, Siemens
The Test command returns the supported parameters.
Response
+CCUG: (list of supported <n>s),(list of supported <index>),(list of supported <info>) OK
The Read command returns if the permanent CUG invocation is activated, which CUG index is chosen, and if Preferential Group or Outgoing Access is suppressed.
Response
+CCUG: <n>, <index>,<info> OK
The write command serves to activate or deactivate permanent CUG invoca­tion, to set the desired CUG index, and to specify if Preferential Group or Out­going Access shall be suppressed.
Parameter
<n> (numeric) 0 Deactivate permanent CUG mode 1 Activate permanent CUG mode
<index> (numeric) 0…9 Explicit selection of CUG index 10 No index (preferred CUG taken from subscriber data)
<info> State of the call (numeric) 0 No information 1 Suppress Outgoing Access 2 Suppress preferential CUG 3 Suppress preferential CUG and Outgoing Access.
Response
OK / ERROR / +CME ERROR
Note
· The active settings of omitted parameters are retained without changes.
· Upon delivery, settings are predefined with <n>=0, <index>=10, <info>=0.
These delivery defaults cannot be recalled automatically.
· Some combinations of parameters may lead to the rejection of CUG calls by the network. For more information please consult GSM 04.85.
· ATZ or AT&F have no impact on the current settings.
· See Chapter 2.5 for instructions of how to activate or deactivate the CCUG
feature call by call.
s
MC39i_ATC_V01.02 Page 82 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
4.9 AT+CCWA Call waiting
Test command
AT+CCWA=?
Read command
AT+CCWA?
Write command
AT+CCWA= [<n>,[<mode> [,<class>]]]
Response
+CCWA: (list of supported <n>s)
OK / ERROR / +CME ERROR
Parameter
See write command
Response
+CCWA: <n> OK / ERROR / +CME ERROR
Parameter
See write command
This command controls the Call Waiting supplementary service according to GSM 02.83. Activation, deactivation and status query are supported.
Response
If command is successful:
If <mode>=2
+CCWA: <status>, <class> [<CR><LF>+CCWA: ...] <CR><LF>OK
otherwise
OK
If error is related to ME functionality:
+CME ERROR: <err>
Parameters
<n> Sets/shows the presentation mode of URC in the TA 0 disable display of the URC “+CCWA” or “^SCWA” 1 enable display of the URC “+CCWA” or “^SCWA”
<status> 0 Call Waiting service not active 1 Call Waiting service active
<mode> When <mode> is not given, network is not interrogated. 0 disable 1 enable 2 query status
<class> Sum of integers each representing a class of information (de-
1 voice 2 data 4 fax 7 voice, data and fax (1+2+4) 8 SMS 16 data circuit sync 32 data circuit async 64 dedicated packet access 128 dedicated PAD access
s
fault 7). Specifies the class of the active call.
MC39i_ATC_V01.02 Page 83 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
Notes regarding <class>:
· The AT+CCWA command offers a broad range of options according to the GSM specifications. However, when you attempt to set a <class> which is not provisioned or not supported, the setting will not take effect regardless of the response returned. The responses in these cases vary with the network (for example “OK”, “Operation not allowed”, “Operation not supported” etc.). To make sure check the current Call Waiting settings with <mode>=2.
· <class> 2 (data) comprises all those <class> values between 16 and 128, that are supported both by the network and the MS. This means, a setting made for <class> 2 applies to all remaining data classes (if supported). In addition, you can assign a different setting to a specific class. For example, you can activate Call Waiting for all data classes, but deactivate it for a spe­cific data class.
· Despite the specifications stated in GSM 02.04 Call Waiting is not handled uniformly among all networks: GSM 02.04, Annex A, provides the following specification:
“The applicability of Call Waiting refers to the telecommunication service of the active call and not of the waiting call. The incoming, waiting, call may be of any kind.”
Nevertheless, networks do differ on the actual implementation of the service. For example, the activation of “call waiting” for <class> 4, “fax”, causes some networks to send a call waiting indication if a call “of any kind” comes in during an active fax call, but others may (with the same settings active) indicate a waiting fax call during any kind of active call. Thus, the only reli­able way to receive or prevent a call waiting indication under any circum­stances and in any network, is to activate or deactivate call waiting for all tele- and bearer services (<class> 255).
Unsolicited Result Codes
If <n>=1 and the Call Waiting service is enabled the following URCs indicate a waiting call to the TE:
+CCWA: <number>,<type>,<class>,,<CLI validity>
This URC appears while the waiting call is still ringing. or
^SCWA:
This URC indicates that a waiting call rang when the ME was in online mode during a CSD call, but the calling party hang up before the ME went to com­mand mode.
Parameters of the URC +CCWA
<number> String type phone number of calling address in format speci-
<type> Type of address octet in integer format (refer to GSM 04.08
<class> Indicates the class of the waiting call. See Write command for
<CLI validity> 0 CLI valid
1 CLI has been withheld 2 CLI is not available
If the active call is a CSD call, and a waiting call is received, then ME produces a BREAK while still in online mode, and displays
· +CCWA URC (as above) when ME goes back to command mode while the waiting call is still active and can be accepted;
s
fied by <type>
subclause 10.5.4.7)
possible values.
MC39i_ATC_V01.02 Page 84 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
· or ^SCWA URC (as above) when ME goes back to command mode after the waiting call has ended.
Reference
GSM 07.07, GSM 02.04, GSM 02.83
Example
Note
· With the AT+CHLD command, it is possible to establish a multiparty call or to set the active voice call on hold and then accept a waiting voice call. See also AT+CHLD in Chapter 4.16.
· Users should be aware that if Call Waiting is activated (<mode>=1), the presentation of URCs needs to be enabled, too (<n>=1). Otherwise, on the one hand, a waiting caller would be kept waiting due to lack of BUSY sig­nals, while, on the other hand, the waiting call would not be indicated to the called party.
at+ccwa=1,1 To enable the presentation of the URC and to switch
OK
at+ccwa=,2 To query the status of CW for default classes. +CCWA: 1,1 CW is activated during voice calls. +CCWA: 1,2 CW is activated during data calls. +CCWA: 1,4 CW is activated during fax calls.
OK
at+ccwa=0,0 To deactivate CW for default classes.
OK
s
on the indication of waiting calls during active voice, data, fax calls (default classes).
MC39i_ATC_V01.02 Page 85 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
4.10 AT+CEER Extended error report
Test command
AT+CEER=?
Execute command
AT+CEER
Reference
GSM 07.07
Example 1
Response
OK
TA returns an extended error report of the reason for
· the last failure to set up a call (both mobile originated or terminated)
· the last call release
· the last unsuccessful GPRS attach or unsuccessful PDP context activation
· the last GPRS detach or PDP context deactivation
· the last failure to modify a call by using Supplementary Services
· the last failed attempt to activate, register, deactivate or deregister a Sup-
plementary Service
The error report is presented in numeric format. A description associated with each number can be found in the Appendix.
The first parameter <location ID> serves to locate the other two parameters. Depending on the failure either <reason> or <ss_release> are applicable.
Response
+CEER: <location ID>, <reason > , <ss_release>OK
Parameter
<location ID> Location ID as number code.
Location IDs are listed in Chapter 9.1.6. Each ID is related with another table that contains a list of <reason>s or
<ss_release>s.
<reason> Reason for last failure as number code.
<reason> numbers and associated descriptions are listed in several tables, sorted by different categories (see Chapters
9.1.7 to 9.1.19). The chapter numbers can be found pro­ceeding from the Location ID table in Chapter 9.1.6.
<ss_release> Reason for last failure related to a Supplementary Service.
<ss_release> numbers and associated descriptions are listed in several tables (see Chapters 9.1.14 and 9.1.15. The chapter numbers can be found proceeding from the Loca­tion ID table in Chapter 9.1.6.
Note
· AT+CEER is not available for data calls, please use ATS18=1.
· Default output in the case of a no-error-situation is +CEER: 0,0,0.
· If <reason> ¹ 0, then <ss_release> = 0. Vice versa, if <reason> = 0, then
<ss_release> may be ¹ 0.
A mobile originated call is rejected by the called party. Call setup is terminated with NO CARRIER. To check for the cause the caller enters AT+CEER:
Atd”017511223344”; Call is rejected by called party. NO CARRIER at+ceer +CEER: 8,21,0 Location ID stated in Chapter 9.1.6: 8 = GSM call OK for L3 Call Control. The reference points to Chapter
s
9.1.11 where 21 = Call rejected. 0 = No error (pa­rameter <ss_release> is not applicable).
MC39i_ATC_V01.02 Page 86 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
Example 2
Example 3
User attempts to set up a multiparty call, though there are only two parties in­volved in the present conversation:
Atd”017511223344”; OK at+chld=2 OK at+chld=3 +CME ERROR: operation temporary not allowed at+ceer
+CEER: 22,0,2 Location ID stated in Chapter 9.1.6: 22 = SIEMENS
User attempts to activate call barring. Activation is denied by the network since the password is blocked after previous failures to enter the password.
at+clck=”oi”,1,”0000”,3 +CME ERROR: incorrect password at+ceer
+CEER: 35,0,43 Location ID stated in Chapter 9.1.6: 35 = Supple-
s
cause for L3 call related SS. The reference points to Chapter 9.1.15 where 2 = Initial conditions not fulfilled (one active, one held call). 0 = No error (pa­rameter <reason> is not applicable).
mentary Services network error. The reference points to Chapter 9.1.14 where 43 = Num­berOfPWAttemptsViolation (for example if wrong password has been entered 3 times or more). 0 = No error (parameter <reason> is not applicable).
MC39i_ATC_V01.02 Page 87 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
4.11 AT+CFUN Set phone functionality
Test command
AT+CFUN=?
Read command
AT+CFUN?
Write command
AT+CFUN= [<fun>[,<rst>]]
Response
+CFUN: (list of supported <fun>s), (list of supported <rst>s) If error is related to ME functionality:
+CME ERROR: <err>
Parameter
See below
Response
+CFUN: <fun>
If error is related to ME functionality:
+CME ERROR: <err>
Parameter
See below
The write command can be used to reset the ME, to choose one of the SLEEP modes or to return to full functionality.
Intended for power saving, SLEEP mode reduces the functionality level of the ME to a minimum and, thus, minimizes the current consumption. SLEEP mode falls in two categories: NON-CYCLIC SLEEP mode <fun>=0 and CYCLIC SLEEP modes, selectable as <fun>= 5, 6, 7 and 8.
NON-CYCLIC SLEEP mode permanently blocks the serial interface. The CY­CLIC SLEEP mode, however, is a dynamic process which alternatingly enables and disables the serial interface. The major benefit of CYCLIC SLEEP mode is that the serial interface remains accessible and that packet-switched calls can be done without exiting the SLEEP mode. Also, NON-CYCLIC and CYCLIC SLEEP mode provide different ways to wake up the ME. For details see Chap­ter 4.11.1.
For CYCLIC SLEEP mode (<fun>=5, 6, 7 and 8) both the ME and the applica­tion must be configured to use hardware flow control. This is necessary since the CTS signal is set/reset every time when the ME listens to a paging mes­sage from the base station. This is the way how the module indicates to the ap­plication when the UART is active. For detailed information on the timing of the CTS signal refer to [1]. The default setting of hardware flow control is AT\Q0 which must be altered to AT\Q3 (see Chapter 2.3). For use after restart you are advised to add it to the user profile saved with AT&W.
Response
OK
If error is related to ME functionality:
+CME ERROR: <err>
Parameter
<fun> 0 NON-CYCLIC SLEEP mode:
In this mode, the AT interface is not accessible. Consequently, once you have set <fun> level 0, do not send further characters. Otherwise these characters remain in the input buffer and may delay the output of an unsolicited result code. After receiving the AT+CFUN=0 command the ME waits 2 seconds before entering the power saving mode. The first wake-up event stops power saving and takes the ME back to full functionality level <fun>=1.
s
MC39i_ATC_V01.02 Page 88 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
1 Full functionality.
5 CYCLIC SLEEP mode:
6 CYCLIC SLEEP mode:
7 CYCLIC SLEEP mode:
8 CYCLIC SLEEP mode:
<rst> [0] The <rst> parameter can only be used if the serial interface
1 ME resets and restarts to full functionality.
Reference
GSM 07.07
Note
· If the ME is in Multiplexer mode, it is not recommended to activate SLEEP mode with AT+CFUN=<n>. The best approach to properly control SLEEP mode in this case is to issue the PSC messages described in [5], Chapter “Power saving control (PSC)”.
· In Multiplex mode, the CFUN profile is shared by all multiplexer channels.
· When a circuit-switched call is in progress, <fun>=7 or 8 can be activated
without terminating the call. However, setting <fun>=0, 5 or 6 during a cir­cuit-switched call immediately disconnects this call.
· Please keep in mind that power saving works only while the ME is registered to the GSM network. If you attempt to activate one of the SLEEP modes
while the ME is deregistered, the selected <fun> level will be set, but power saving does not work to its full extent. Furthermore, in order to accept in­coming calls, SMS or network related URCs in SLEEP mode the ME must be registered when it enters the SLEEP mode.
· To check that power saving is on, you can query the status with AT+CFUN?, if you have chosen CYCLIC SLEEP mode. If available, you can take advan-
s
If the ME is in one of the CYCLIC SLEEP modes you can issue AT+CFUN=1 to stop power saving and return to full functionality. Keep in mind that, unlike the reset command described below, this action does not restart the ME but only changes the level of functionality. See parameter <rst> for details on the reset.
In this mode, the serial interface is shortly enabled during paging. If characters are recognized on the serial interface, the ME stays active for 2 seconds after the last character was sent or received.
In this mode, the serial interface is shortly enabled during paging. If characters are recognized on the serial interface, the ME stays active for 10 minutes after the last character was sent or received.
In this mode, the serial interface is shortly enabled during paging. If characters are recognized on the serial interface, the ME stays active for 2 seconds after the last character was sent or received. ME exits SLEEP mode only if AT+CFUN=1 is entered.
In this mode, the serial interface is shortly enabled during paging. If characters are recognized on the serial interface, the ME stays active for 10 minutes after the last character was sent or received. ME exits SLEEP mode only if AT+CFUN=1 is entered.
is enabled. Due to the command syntax, you need to enter <fun>, followed by <rst>, where <fun> is only a placeholder and has no effect. See examples below.
After reset and restart, PIN 1 authentication is necessary (AT+CPIN). If autobauding is enabled it is recommended to wait 3 to 5 seconds before entering the first AT command. For details on autobauding refer to Chapter 2.45.
MC39i_ATC_V01.02 Page 89 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
tage of the status LED controlled by the SYNC pin. See Chapter 8.48 and [1]. The LED stops flashing once the module starts power saving.
Example 1
Example 2
Example 3
Example 4
To check the level of functionality use the read command:
AT+CFUN? +CFUN: 1 Default mode after ME was restarted.
Remember that the AT interface is not accessible in NON-CYCLIC SLEEP mode. Consequently, the read command is only useful when the ME is set to full functionality or, when <fun> is set to 5, 6, 7 or 8.
AT+CFUN? +CFUN: 5 CYCLIC SLEEP mode.
To set the ME to NON-CYCLIC SLEEP mode enter
AT+CFUN=0 OK
When, for example, an SMS is being received and indicated by an unsolicited result code (URC), the ME wakes up to full operation.
+CMTI: "SM",5 Note that the URC used in this example will appear
After this, you may want to verify the operating status:
AT+CFUN? +CFUN: 1 Indicates that ME has entered full functionality mode.
To stop CYCLIC SLEEP mode and return to full functionality:
AT+CFUN? +CFUN: 5
OK AT+CFUN=1 OK
Remember that this approach is not applicable to the NON-CYCLIC SLEEP mode (since the serial interface is disabled). The NON-CYCLIC SLEEP mode ends with the first wake-up event.
To reset and restart the ME:
AT+CFUN=1,1 or alternatively, AT+CFUN=0,1 or 5,1 or 6,1 or 7,1 or 8,1 OK
^SYSSTART The ^SYSSTART URC confirms that the ME has been
s
only if CMTI=1,1 was configured before. See Chapters
5.10 and 9.1.4.
rebooted. Note that ^SYSSTART appears only if AT+IPR¹0. If the ME is in autobaud mode, it is recommended to wait 3 to 5 seconds before entering the first AT command. Remember to enter the SIM PIN after restart.
MC39i_ATC_V01.02 Page 90 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
4.11.1 Wake up the ME from SLEEP mode
A wake-up event is any event that switches off the SLEEP mode and causes the ME to return to full functionality. In short, it takes the ME back to AT+CFUN=1.
Definitions of the state transitions described in Table 14: Yes = ME exits SLEEP mode. No = ME does not exit SLEEP mode.
Table 14: Wake-up events in NON-CYCLIC and CYCLIC SLEEP modes
Event From SLEEP mode
AT+CFUN=0 to AT+CFUN=1
Ignition line No No No
Activation of /RTS0 Yes1) No1) No1)
Unsolicited Result Code (URC)
Incoming voice or data call Yes Yes No
Any AT command (incl. outgoing voice or data call, outgoing SMS)
Incoming SMS depending on mode selected by AT+CNMI:
AT+CNMI=0,0 (= default, no indication of received SMS)
AT+CNMI=1,1 (= displays URC upon receipt of SMS)
GPRS data transfer Not possible
Yes Yes No
Not possible (UART disabled)
No
Yes
(UART disabled)
From SLEEP mode AT+CFUN=5 or 6 to AT+CFUN=1
No No
No
Yes
No No
From SLEEP mode AT+CFUN=7 or 8 to AT+CFUN=1
No
No
RTC alarm2) Yes Yes No
AT+CFUN=1 Not possible
(UART disabled)
1)
During all CYCLIC SLEEP modes, /RTS0 is conventionally used for flow control: The assertion
of /RTS0 signal is that the application is ready to receive data - without waking up the module. Be aware that this behavior is different if CFUN=0: In this case, the assertion of /RTS0 serves as a wake-up event, giving the application the possibility to intentionally terminate power saving.
2)
Recommendation: In NON-CYCLIC SLEEP mode, you can set an RTC alarm to wake up the
ME and return to full functionality. This is a useful approach because, in this mode, the AT inter­face is not accessible.
MC39i_ATC_V01.02 Page 91 of 314 11.11.2003
Yes Yes
MC39i AT Command Set
Confidential / Released
4.12 AT+CGMI Request manufacturer identification
Test command
AT+CGMI=?
Execute command
AT+CGMI
Reference
GSM 07.07
Response
OK
Response
TA returns manufacturer identification text.
SIEMENS OK
Note
See also ”AT+GMI Request manufacturer identification”.
4.13 AT+CGMM Request model identification
Test command
AT+CGMM=?
Execute command
AT+CGMM
Reference
GSM 07.07
Response
OK
Response
TA returns product model identification text.
MC39i
OK
Note
See also ”AT+GMM Request TA model identification”.
s
4.14 AT+CGMR Request revision identification of software status
Test command
AT+CGMR=?
Execute command
AT+CGMR
Reference
GSM 07.07
Response OK
Response
TA returns product firmware version identification text.
REVISION xx.yy
OK
xx.yy Version xx and variant yy of software release
Note
See also AT+GMR Request TA revision identification of software status
MC39i_ATC_V01.02 Page 92 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
4.15 AT+CGSN Request product serial number identification (IMEI) identical to GSN
Test command
AT+CGSN=?
Execute command
AT+CGSN
Reference
GSM 07.07
Response
OK
Response
TA returns identification text for determination of the individual ME.
<sn> OK
Parameter
<sn> IMEI of the telephone (International Mobile station Equipment Identity)
Note
See also ”AT+GSN Request TA serial number identification”.
MC39i_ATC_V01.02 Page 93 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
4.16 AT+CHLD Call hold and multiparty
Test command
AT+CHLD=?
Response
+CHLD: (list of supported <n>s)
OK
s
Execute command
AT+CHLD=[<n>]
Response
TA controls the supplementary services Call Hold and MultiParty. Calls can be put on hold, recovered, released and added to a conversation.
Like for all Supplementary services, the availability and detailed functionality of ”Call hold and multiparty” services depends on the configuration of the GSM net­work. The MC39i can only request the service, but the network decides whether and how the request will be answered.
OK
If error is related to ME functionality:
+CME ERROR: <err>
Parameter
<n> 0 Release all held calls or set UDUB (User Determined User
Busy) for a waiting call:
- If a call is waiting, release the waiting call. The calling
party will receive a ”BUSY” indication (Supplementary Service User Determined User Busy ”UDUB”).
- Otherwise, terminate all held calls (if any).
1 Terminate all active calls (if any) and accept the other call as the
active call:
- If a call is waiting, the waiting call will be accepted.
- Otherwise, if a held call is present, the held call will be
accepted.
1X Terminate the active call X (X= 1-7). The call may be active,
held or waiting. The remote party of the terminated call will receive a ”NO CARRIER” indication. Parameter X is the call identification number <idx> of the targeted call in the list of current calls available with AT command AT+CLCC.
2 Place all active calls on hold (if any) and accept “the other call”
as the active call:
- If a call is waiting, the waiting call will be accepted.
- Otherwise, if a held call is present, the held call will be
accepted.
2X Place all active calls except call X (X= 1-7) on hold.
Parameter X is the call identification number <idx> of the targeted call in the list of current calls available with AT command AT+CLCC.
3 Add a held call to the active calls (set up conference
(multiparty) call).
MC39i_ATC_V01.02 Page 94 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
Reference
GSM 07.07
Note
· The AT+CHLD command offers a broad range of options according to the GSM specifications. However, many of these options are dependent on the SIM card / service provider. If you attempt to invoke an option which is not provisioned by the network, or not subscribed to, invocation of this option will fail. The responses in these cases may vary with the network (for example “Operation not allowed”, “Operation not supported” etc.).
· The supplementary service is only applicable to teleservice 11 (Speech te­lephony). AT+CHLD can be used to both accept a waiting voice call and put an active voice call on hold. A data or fax call, however, cannot be put on hold. But it is possible to place a voice call on hold in order to accept a waiting data or fax call, and afterwards to recover the voice call. In this case, the only difference over speech teleph­ony is that AT+CHLD only puts the voice call on hold, the data or fax call need to be manually accepted (via ATA). Use the AT+CCWA command to activate the Call Waiting service. The classes (bearer services) of waiting calls can be easily distinguished if the URC +CCWA: <number>,<type>,<class>,,<CLI validity> is enabled. For step-by-step instructions refer to the example below. A description of the AT+CCWA command can be found in Chapter 4.9.
· The NO CARRIER result code is not displayed when a held call has been dis­connected from either party. In order to get an indication of this disconnection, please refer to the AT+CSSN command (see Chapter 4.47).
· In conflicting situations, e.g. when a waiting call comes while there are already held calls, the above procedures apply to the waiting call only. For example, <n>=0 rejects the waiting call, but does not affect the held calls.
· The current states of all calls can be easily checked at any time by using the AT+CLCC command. For details refer to Chapter 4.20.
s
Example 1
^SYSSTART at+cpin="9999" OK
+CREG: 2
+CREG: 1,"0145","0016" You are now registered. at+ccwa=1,1,1 You activate the indication of waiting calls OK during active voice calls.
atd"0301234567"; You start a voice call. OK
+CCWA: "+4901772222",145,32,,0 You receive a URC indicating a waiting data
call.
at+chld=2 You set the voice call on hold. OK You receive now the RING of the data call. RING
RING ata You accept the data call. CONNECT 9600/RLP OK With “+++” you go in command mode.
at+clcc You interrogate the status of established calls. +CLCC: 1,0,1,0,0,"0301234567",129 +CLCC: 2,1,0,1,0,"+491772222",145 OK at+chld=1 The active data call is terminated and the held
voice call becomes active.
MC39i_ATC_V01.02 Page 95 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
OK at+clcc +CLCC: 1,0,0,0,0,"0301234567",129 OK
Example 2
The example shows how to place a voice call on hold in order to accept a waiting voice call and then return to the first call.
at+ccwa=,2,1 You query the status of CW during voice calls. +CCWA: 1,1 Indication of waiting calls during active
OK atd03038639839; You start a voice call. OK
+CCWA: "017511111",129,1,,0 You receive a URC indicating a waiting voice
at+clcc You interrogate the status of established calls. +CLCC: 1,0,0,0,0,"03038639839",129,"Test" +CLCC: 2,1,5,0,0,"01755812934",129,"D1_Voice"
OK at+chld=2 You put the first voice call on hold and accept OK the waiting voice call.
at+clcc You interrogate the status of established calls. +CLCC: 1,0,1,0,0,"03038639839",129,"Test" +CLCC: 2,1,0,0,0,"01755812934",129,"D1_Voice"
OK at+chld=1 OK at+clcc +CLCC: 1,0,0,0,0,"03038639839",129,"Test"
OK ath OK
s
voice calls is switched on.
call.
MC39i_ATC_V01.02 Page 96 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
4.17 AT+CHUP Hang up call
Test command
AT+CHUP=?
Execute command
AT+CHUP
Reference
GSM 07.07
Response
OK
Cancels all active and held calls.
Response
OK/ERROR
Note
AT+CHUP implements the same behavior as ATH (see Chapter 2.12).
4.18 AT+CIMI Request international mobile subscriber identity
Test command
AT+CIMI=?
Execute command
AT+CIMI
Reference
GSM 07.07
Response
OK
Response
TA returns < IMSI> for identifying the individual SIM which is attached to ME.
<IMSI> OK
If error is related to ME functionality:
+CME ERROR: <err>
Parameter
<IMSI> International Mobile Subscriber Identity (string without quotes)
Note
MC39i_ATC_V01.02 Page 97 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
s
4.19 AT+CIND Indicator control
MC39i supports indicator event reporting for the following items: signal quality, service availability, generation of sound in the ME, indication of unread short messages, full SMS storage, call in pro­gress and roaming activities.
There are two ways to display the status and event reports by indicators:
1. You can directly query the current status of each indicator, simply by using the Read command AT+CIND?. The Read command returns the status no matter whether the indicator has been reg­istered with the Write command AT+CIND=[<stat>[,<stat>[,...]]].
2. You can take advantage of Unsolicited Result Codes. These are the +CIEV URCs which the ME automatically sends to the application, whenever the value of the associated indicator changes. The presentation of these URCs depends on two settings:
a) The indicators must be registered with the Write command AT+CIND=[<stat>[,<stat>[,...]]].
By default, all of them are registered when the ME is switched on. Any URCs you do not need can easily be excluded if deregistered with <stat>=0.
b) The URC presentation mode must be enabled with AT+CMER (see Chapter 4.26).
Test command
AT+CIND=?
Response
+CIND: (<indDescr>,(list of supported <indValue>s)) [,(<indDescr>,(list of sup- ported <indValue>s))[,...]]
Parameters
<indDescr> indicator names and their <indValue> ranges. "battchg" Battery charge level (5). Not relevant for MC39i. "signal" Signal quality (0-7 or 99 if not measurable). The
indicated value is the bit error rate of the signal received. See also AT+CSQ in Chapter 4.46.
"service" Service availability (0-1).
0: Not registered to any network 1: Registered to home network or, if ”roam”=1 then registered to another network
"sounder" Sounder activity (0-1). The indicator provides in-
formation about tones generated in the ME. The value 1 means for example: Incoming call - ME is ringing. Note that the URC +CIEV: sounder will be output only if ringing tones are activated with AT^SRTC (see Chapter 8.43) Waiting call – ME generates waiting call tone (if call waiting is enabled). Outgoing call – ME generates Call Progress tone. Outgoing call – ME generates BUSY tone. The value changes to 0, when the tone stops.
"message" Unread short message(s) at memory location
<mem1> (0-1).
"call" Call in progress (0-1).
Applies to voice, data and fax calls. Indicator value is "1" if at least one call is in state "active" or "held". The indicator is issued each time a call status transition ends in the "active" state or when a call is removed from the list of current calls. (For the list of current calls see AT+CLCC described in Chapter 4.20.)
MC39i_ATC_V01.02 Page 98 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
"roam" Roaming indicator (0-1).
"smsfull" A short message memory storage in the MT has
“rssi” Received signal (field) strength, scaled to value
<indValue> integer type value, in the range stated above for the corresponding
Read command
AT+CIND?
Write command
AT+CIND= [<state>
[,<state>[,...]]]
Reference
GSM 07.07
Examples
Response
TA returns the status of the ME indicators.
+CIND: <indValue>[,<indValue>[,...]] OK
If error is related to ME functionality
+CME ERROR: <err>
Parameter
See Test command
Response
OK / ERROR / +CME ERROR: <err>
Parameter
The Write command simply controls the registration / deregistration of indicators. <state> 0 Indicator is deregistered. The indicator cannot be presented as
Note
at+cind? +CIND: 5,99,1,0,1,0,0,0,5 First parameter not relevant for MC39i. The bit
at+cmer=2,0,0,2 Activate Indicator Event Report with at+cmer OK +CIEV: battchg,5 +CIEV: signal,99 +CIEV: service,1
s
0: Registered to home network or not registered 1: Registered to other network
become full (1) or memory locations are available (0); i.e. the range is (0-1).
range 0…5, or 99 if not measurable. 0: Signal strength < 112 dBm 1 – 4: Signal strength in 15 dBm steps 5: Signal strength > -51 dBm See also AT+CSQ in Chapter 4.46. Value range of AT+CSQ is 0 – 31.
<indDescr>.
+CIEV URC, but can be directly queried with AT+CIND?.
1 Indicator is registered, indicator event report is allowed.
error rate of the signal quality is not available (since there is no call in progress). The ME is registered to the home network. Unread short message(s) available. Signal strength greater or equal -51 dBm.
MC39i_ATC_V01.02 Page 99 of 314 11.11.2003
MC39i AT Command Set
Confidential / Released
+CIEV: sounder,0 +CIEV: message,0 +CIEV: call,0 +CIEV: roam,0 +CIEV: smsfull,0 +CIEV: rssi,4
atd"0123456"; You make a call. OK
+CIEV: sounder,1 A set of +CIEV URCs reports is presented. +CIEV: call,1 +CIEV: sounder,0 +CIEV: call,0 The receiver hangs up. NO CARRIER
at+cind=,,,0,,0 You deregister the indicators ‘sounder’ and OK ‘call’.
atd"0123456"; You make a call. OK NO CARRIER This time, no +CIEV URCs are displayed.
s
MC39i_ATC_V01.02 Page 100 of 314 11.11.2003
Loading...
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use