How it Works
Siemens
Loading...
AC75
Hardware Interface Description
120 pgs2.98 Mb0
User Manual
569 pgs4.86 Mb0
User Manual
123 pgs6.1 Mb0
Table of contents
Loading...

Siemens AC75 User Manual

Download
Page 1
s
AC75
Siemens Cellular Engine
Version: 01.002 DocId: AC75_ATC_V01.002
AT Command Set
Page 2
AC75 AT Command Set
s
Document Name:
Version:
Date:
DocId:
Status
General Notes
Product is deemed accepted by recipient and is provided without interface to recipient’s products. The documen­tation and/or product are provided for testing, evaluation, integration and information purposes. The documen­tation and/or product are provided on an “as is” basis only and may contain deficiencies 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 disclaims all warranties, including without limitation any im­plied warranties of merchantability, completeness, 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 product must be designed to be in accordance with the technical specifications provided in these guidelines. Fail­ure to comply with any of the required procedures can result in malfunctions or serious discrepancies in results. Furthermore, all safety instructions regarding the use of mobile technical systems, including GSM products, which also apply to cellular phones must be followed. Siemens or its suppliers shall, regardless of any legal the­ory upon which the claim is based, not be liable for any consequential, incidental, direct, indirect, punitive or other damages whatsoever (including, without limitation, 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 docu­mentation and/or product, even if Siemens has been advised of the possibility of such damages. The foregoing limitations of liability 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. Subject 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.
AC75 AT Command Set
01.002
October 30, 2006
AC75_ATC_V01.002
Confidential / Released
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 re­served.
Copyright © Siemens AG 2006
Trademark notice
Bluetooth™ is a registered trademark of Bluetooth SIG Inc.
AC75_ATC_V01.002 Page 2 of 569 10/30/06 Confidential / Released
Page 3
AC75 AT Command Set

Contents

s
Contents
1. Introduction............................................................................................................................................ 14
1.1 Scope of the document ................................................................................................................. 14
1.2 Related documents ....................................................................................................................... 15
1.3 Document conventions.................................................................................................................. 16
1.3.1 Quick reference table..................................................................................................... 16
1.3.2 Superscript notation for parameters and values ............................................................ 17
1.4 AT Command Syntax .................................................................................................................... 18
1.4.1 Using Parameters .......................................................................................................... 18
1.4.2 Combining AT commands on the same command line ................................................. 19
1.5 Supported character sets .............................................................................................................. 20
1.5.1 GSM alphabet tables and UCS2 character values ........................................................ 22
1.5.2 UCS2 and GSM data coding and conversion for SMS text mode ................................. 24
1.5.2.1 Implementing output of SIM data to Terminal (direction TA to TE) ................................ 24
1.5.2.2 Implementing input of Terminal data to SIM (direction TE to TA)................................... 25
1.6 Serial Interface Flow Control ......................................................................................................... 26
1.6.1 Software Flow Control (XON/OFF Handshake)............................................................. 26
1.6.2 Hardware Flow Control (RTS/CTS Handshake) ............................................................ 26
1.7 Communication between Customer Application and AC75........................................................... 28
1.8 Unsolicited Result Code Presentation........................................................................................... 29
1.9 Common PCN Handset Specification (CPHS) .............................................................................. 30
1.10 Errors and Messages .................................................................................................................... 31
2. Configuration Commands..................................................................................................................... 32
2.1 AT&F Set all current parameters to manufacturer defaults ......................................................... 32
2.2 AT&V Display current configuration ............................................................................................33
2.2.1 AT&V responses............................................................................................................ 34
2.3 AT&W Stores current configuration to user defined profile ......................................................... 36
2.4 ATQ Set result code presentation mode ..................................................................................... 37
2.5 ATV Set result code format mode ...............................................................................................38
2.5.1 Verbose and numeric result codes ................................................................................ 38
2.6 ATX Set CONNECT result code format and call monitoring ....................................................... 39
2.7 AT\V Set CONNECT result code format ..................................................................................... 40
2.8 ATZ Set all current parameters to user defined profile................................................................ 41
2.9 AT+CFUN Set phone functionality .............................................................................................. 42
2.9.1 Wake up the ME from SLEEP mode ............................................................................. 44
2.10 AT^SMSO Switch off mobile station............................................................................................46
2.11 AT+GCAP Request complete TA capabilities list........................................................................ 47
2.12 AT+CMEE Mobile Equipment Error Message Format ................................................................ 48
2.12.1 CME/CMS Error Code Overview ................................................................................... 49
2.13 AT+CSCS Select TE character set ............................................................................................. 54
2.14 AT^SCFG Extended Configuration Settings ............................................................................... 55
2.15 AT^SM20 Set M20 compatibility mode ....................................................................................... 79
3. Status Control Commands ................................................................................................................... 80
3.1 AT+CMER Mobile Equipment Event Reporting .......................................................................... 80
3.2 AT+CIND Indicator control .......................................................................................................... 82
AC75_ATC_V01.002 Page 3 of 569 10/30/06 Confidential / Released
Page 4
AC75 AT Command Set
Contents
3.3 AT^SIND Extended Indicator Control.......................................................................................... 85
3.4 AT+CEER Extended Error Report............................................................................................... 92
3.4.1 Cause Location ID for the extended error report ........................................................... 93
3.4.2 SIEMENS L2 cause ....................................................................................................... 94
3.4.3 GSM release cause for L3 Radio Resource (RR).......................................................... 94
3.4.4 SIEMENS release cause for L3 Radio Resource (RR).................................................. 94
3.4.5 GSM release cause for Mobility Management (MM) or Session Management (SM)..... 95
3.4.6 SIEMENS release cause for L3 Mobility Management (MM) ........................................ 96
3.4.7 GSM release cause for L3 Call Control (CC)................................................................. 96
3.4.8 SIEMENS release cause for L3 Call Control (CC)......................................................... 98
3.4.9 GSM Release cause for Supplementary Service Call ................................................... 98
3.4.10 GSM release cause for Session Management (SM) ..................................................... 99
3.4.11 GSM cause for L3 Protocol module or other local cause ........................................... 100
3.4.12 SIEMENS release cause for GPRS API ...................................................................... 100
3.4.13 SIEMENS release cause for PPP/IP-Stack ................................................................. 100
3.5 ATS18 Extended call release report.......................................................................................... 101
3.6 AT+CPAS Mobile equipment activity status.............................................................................. 103
3.7 AT+WS46 Select wireless network ........................................................................................... 104
s
4. Serial Interface Control Commands................................................................................................... 105
4.1 AT\Q Flow control...................................................................................................................... 105
4.2 AT&C Set Data Carrier Detect (DCD) Line mode ..................................................................... 106
4.3 AT&D Set circuit Data Terminal Ready (DTR) function mode................................................... 107
4.4 AT&S Set circuit Data Set Ready (DSR) function mode ........................................................... 108
4.5 ATE Enable command echo...................................................................................................... 109
4.6 AT+ICF Serial Interface Character Framing.............................................................................. 110
4.7 AT+IFC Set Flow Control separately for data directions ........................................................... 112
4.8 AT+ILRR Set TE-TA local rate reporting................................................................................... 114
4.9 AT+IPR Set fixed local rate ....................................................................................................... 116
4.9.1 Autobauding................................................................................................................. 117
4.10 AT+CMUX Enter multiplex mode .............................................................................................. 119
4.10.1 Restrictions on Multiplex mode .................................................................................... 120
4.10.2 Second serial interface ASC1...................................................................................... 122
4.11 AT^STPB Transmit Parity Bit (for 7E1 and 7O1 only) ............................................................... 123
5. Security Commands ............................................................................................................................ 124
5.1 AT+CPIN PIN Authentication ....................................................................................................124
5.1.1 What to do if PIN or password authentication fails? .................................................... 126
5.2 AT+CPIN2 PIN2 Authentication ................................................................................................ 128
5.3 AT^SPIC Display PIN counter...................................................................................................130
5.4 AT+CLCK Facility lock .............................................................................................................. 134
5.5 AT^SLCK Facility lock ............................................................................................................... 139
5.6 AT+CPWD Change Password .................................................................................................. 140
5.7 AT^SPWD Change Password................................................................................................... 144
5.8 AT^SCSL Customer SIM Lock .................................................................................................. 146
6. Identification Commands.................................................................................................................... 150
6.1 ATI Display product identification information ........................................................................... 150
6.2 AT+CGMI Request manufacturer identification......................................................................... 151
6.3 AT+GMI Request manufacturer identification ........................................................................... 151
AC75_ATC_V01.002 Page 4 of 569 10/30/06 Confidential / Released
Page 5
AC75 AT Command Set
Contents
6.4 AT+CGMM Request model identification .................................................................................. 152
6.5 AT+GMM Request model identification..................................................................................... 152
6.6 AT+CGMR Request revision identification of software status................................................... 153
6.7 AT+GMR Request revision identification of software status ..................................................... 153
6.8 AT+CGSN Request International Mobile Equipment Identity (IMEI) ......................................... 154
6.9 AT+GSN Request International Mobile Equipment Identity (IMEI) ........................................... 154
6.10 AT+CIMI Request International Mobile Subscriber Identity (IMSI)............................................ 155
7. Call related Commands....................................................................................................................... 156
7.1 Call Status Information ................................................................................................................ 156
7.2 ATA Answer a call ..................................................................................................................... 157
7.3 ATD Mobile originated call to specified number........................................................................ 158
7.4 ATD><mem><n> Mobile originated call using specific memory and index number ................. 160
7.5 ATD><n> Mobile originated call from active memory using index number ............................... 162
7.6 ATD><str> Mobile originated call from active memory using corresponding field .................... 163
7.7 ATDI Mobile originated call to ISDN number............................................................................. 164
7.8 ATDL Redial last number used ................................................................................................. 165
7.9 ATH Disconnect existing connection......................................................................................... 166
7.10 AT+CHUP Hang up call ............................................................................................................ 167
7.11 AT^SHUP Hang up call(s) indicating a specific GSM04.08 release cause ............................... 168
7.12 ATS0 Set number of rings before automatically answering a call ............................................. 170
7.13 ATS6 Set pause before blind dialing ......................................................................................... 171
7.14 ATS7 Set number of seconds to wait for connection completion .............................................. 172
7.15 ATS8 Set number of seconds to wait for comma dialing modifier............................................. 173
7.16 ATS10 Set disconnect delay after indicating the absence of data carrier ................................. 174
7.17 ATO Switch from command mode to data mode / PPP online mode........................................ 175
7.18 +++ Switch from data mode to command mode ....................................................................... 176
7.19 AT+CBST Select bearer service type ....................................................................................... 177
7.20 AT+CRLP Select radio link protocol parameters for originated non-transparent data calls ...... 179
7.21 AT+CLCC List current calls of ME ............................................................................................ 180
7.22 AT^SLCC Siemens defined command to list current calls of ME.............................................. 182
7.23 AT+CR Service reporting control ..............................................................................................187
7.24 AT+CRC Set Cellular Result Codes for incoming call indication .............................................. 188
7.25 AT+CSNS Single Numbering Scheme...................................................................................... 189
7.26 AT^SCNI List Call Number Information..................................................................................... 190
7.27 AT^SLCD Display Last Call Duration ........................................................................................ 191
7.28 AT^STCD Display Total Call Duration....................................................................................... 192
7.29 ATP Select pulse dialing ........................................................................................................... 193
7.30 ATT Select tone dialing ............................................................................................................. 193
s
8. Network Service Commands .............................................................................................................. 194
8.1 AT+COPN Read operator names ............................................................................................. 194
8.2 AT+COPS Operator Selection .................................................................................................. 195
8.3 AT^SOPS Extended Operator Selection................................................................................... 198
8.4 AT+CREG Network registration ................................................................................................ 200
8.5 AT+CSQ Signal quality ............................................................................................................. 203
8.6 AT^SMONC Cell Monitoring......................................................................................................204
8.7 AT^SMOND Cell Monitoring......................................................................................................206
8.8 AT^SFNUR Select the fixed network user rate ......................................................................... 209
8.9 AT^MONI Monitor idle mode and dedicated mode ................................................................... 210
AC75_ATC_V01.002 Page 5 of 569 10/30/06 Confidential / Released
Page 6
AC75 AT Command Set
Contents
8.9.1 AT^MONI responses.................................................................................................... 211
8.9.2 Service states .............................................................................................................. 212
8.10 AT^MONP Monitor neighbour cells ........................................................................................... 213
8.10.1 AT^MONP responses .................................................................................................. 214
8.11 AT^SMONG GPRS Monitor ...................................................................................................... 215
8.11.1 AT^SMONG Cell Info Table......................................................................................... 216
8.12 AT^SALS Alternate Line Service...............................................................................................217
8.13 AT^SHOM Display Homezone .................................................................................................. 219
8.14 AT^SPLM Read the PLMN list .................................................................................................. 220
8.15 AT+CPOL Preferred Operator List ............................................................................................ 222
8.16 AT^SPLR Read entry from the preferred operators list............................................................. 223
8.17 AT^SPLW Write an entry to the preferred operators list ........................................................... 224
9. Supplementary Service Commands .................................................................................................. 225
9.1 AT+CACM Accumulated call meter (ACM) reset or query ........................................................ 225
9.2 AT^SACM Advice of charge and query of ACM and ACMmax ................................................. 226
9.3 AT+CAMM Accumulated call meter maximum (ACMmax) set or query.................................... 228
9.4 AT+CAOC Advice of Charge information.................................................................................. 229
9.5 AT+CCUG Closed User Group ................................................................................................. 230
9.6 AT+CCFC Call forwarding number and conditions control ....................................................... 232
9.7 AT+CCWA Call Waiting ............................................................................................................ 236
9.8 AT+CHLD Call Hold and Multiparty........................................................................................... 240
9.9 AT+CLIP Calling Line Identification Presentation ..................................................................... 242
9.10 AT+CLIR Calling Line Identification Restriction ........................................................................ 244
9.11 AT+COLP Connected Line Identification Presentation ............................................................. 245
9.12 AT+CPUC Price per unit and currency table............................................................................. 247
9.13 AT+CSSN Supplementary service notifications ........................................................................ 249
9.14 AT+CUSD Unstructured supplementary service data ............................................................... 251
s
10. Internet Service Commands ............................................................................................................... 253
10.1 AT^SICS Internet Connection Setup Profile.............................................................................. 256
10.1.1 Example: Default values of a CSD connection profile ................................................. 259
10.1.2 Example: GPRS connection profile ............................................................................. 260
10.2 AT^SICI Internet Connection Information.................................................................................. 261
10.2.1 Checking Connection Profile Status ............................................................................ 262
10.3 AT^SISS Internet Service Setup Profile .................................................................................... 263
10.4 AT^SISI Internet Service Information ........................................................................................ 272
10.5 AT^SISO Internet Service Open ............................................................................................... 274
10.5.1 Example: Accepting / Rejecting Socket Connection Request from Remote Client ..... 277
10.6 AT^SISC Internet Service Close ...............................................................................................279
10.7 AT^SISR Internet Service Read Data ....................................................................................... 280
10.7.1 Example: Socket Host Reads Small Amounts of UDP Data Packets (URC Mode)..... 282
10.8 AT^SISW Internet Service Write Data....................................................................................... 283
10.8.1 Usage of parameter <eodFlag> ................................................................................... 285
10.9 AT^SICO Internet Connection Open ......................................................................................... 287
10.10 AT^SICC Internet Connection Close......................................................................................... 289
10.11 AT^SISX Internet Service Execution......................................................................................... 290
10.11.1 Example: Ping.............................................................................................................. 292
10.12 AT^SISE Internet Service Error Report..................................................................................... 293
10.13 Internet Service URC "^SIS" ....................................................................................................... 294
AC75_ATC_V01.002 Page 6 of 569 10/30/06 Confidential / Released
Page 7
AC75 AT Command Set
Contents
10.13.1 Information Elements Related to the Service Application............................................ 295
10.13.2 Information Elements Related to FTP Service............................................................. 296
10.13.3 Information Elements Related to HTTP Service .......................................................... 297
10.13.4 Information Elements Related to POP3 Service .......................................................... 297
10.13.5 Information Elements Related to SMTP Service ......................................................... 297
10.14 Examples of how to Configure and Use Internet Service Profiles............................................... 298
10.14.1 Selecting URC Mode or Polling Mode ......................................................................... 298
10.14.2 Configuring Socket Listener......................................................................................... 298
10.14.3 Configuring Socket Client for Calling a Socket Listener on Another Host ................... 299
10.14.4 Socket Client Sends Data via TCP Connection (Polling Mode)................................... 299
10.14.5 Socket client sends data via TCP connection with URCs............................................ 300
10.14.6 Configuring and Using FTP Download (URC Mode) ................................................... 300
10.14.7 Configuring and Using FTP Upload (URC Mode) ........................................................ 301
10.14.8 Configuring SMPT Service Profile ............................................................................... 301
10.14.9 Sending Email (URC Mode) ........................................................................................ 302
10.14.10 Sending Email (Polling Mode) ..................................................................................... 303
10.14.11 Configuring POP3 Service Profile................................................................................ 304
10.14.12 Retrieving Email (URC Mode) ..................................................................................... 305
10.14.13 Retrieving Email (Polling Mode) .................................................................................. 305
10.14.14 HTTP POST (Polling Mode) ........................................................................................ 306
10.14.15 HTTP GET (Polling Mode) ........................................................................................... 307
s
11. GPRS Commands ................................................................................................................................ 308
11.1 AT+CGACT PDP context activate or deactivate ....................................................................... 308
11.2 AT+CGANS Manual response to a network request for PDP context activation ...................... 310
11.3 AT+CGATT GPRS attach or detach ......................................................................................... 312
11.4 AT+CGAUTO Automatic response to a network request for PDP context activation ............... 313
11.5 AT+CGDATA Enter data state .................................................................................................. 315
11.5.1 Automatic deactivation of PDP context during dial-up PPP......................................... 316
11.6 AT+CGDCONT Define PDP Context ........................................................................................ 317
11.7 AT+CGEQMIN 3G Quality of Service Profile (Minimum acceptable) ........................................ 319
11.8 AT+CGEQREQ 3G Quality of Service Profile (Requested) ...................................................... 323
11.9 AT+CGPADDR Show PDP address ......................................................................................... 327
11.10 AT+CGQMIN Quality of Service Profile (Minimum acceptable) ................................................ 328
11.11 AT+CGQREQ Quality of Service Profile (Requested) .............................................................. 332
11.12 AT+CGREG GPRS Network Registration Status...................................................................... 336
11.13 AT+CGSMS Select service for MO SMS messages ................................................................. 338
11.14 AT^SGACT Query all PDP context activations ......................................................................... 339
11.15 AT^SGAUTH Set type of authentication for PPP connection.................................................... 341
11.16 AT^SGCONF Configuration of GPRS related Parameters ...................................................... 342
11.17 ATA Manual response to a network request for PDP context activation................................... 344
11.18 ATD*99# Request GPRS service.............................................................................................. 345
11.19 ATD*98# Request GPRS IP service ......................................................................................... 346
11.20 ATH Manual rejection of a network request for PDP context activation.................................... 347
11.21 ATS0 Automatic response to a network request for PDP context activation............................. 348
11.22 Using GPRS AT commands (Examples)..................................................................................... 349
11.23 Using the GPRS dial command ATD .......................................................................................... 351
12. FAX Commands ................................................................................................................................... 352
12.1 FAX parameters .......................................................................................................................... 352
AC75_ATC_V01.002 Page 7 of 569 10/30/06 Confidential / Released
Page 8
AC75 AT Command Set
Contents
12.1.1 Fax Result Codes ........................................................................................................ 352
12.2 AT+FCLASS Fax: Select, read or test service class................................................................. 353
12.3 AT+FRH Receive Data Using HDLC Framing .......................................................................... 354
12.4 AT+FRM Receive Data ............................................................................................................. 355
12.5 AT+FRS Receive Silence.......................................................................................................... 356
12.6 AT+FTH Transmit Data Using HDLC Framing.......................................................................... 357
12.7 AT+FTM Transmit Data............................................................................................................. 358
12.8 AT+FTS Stop Transmission and Wait....................................................................................... 359
13. Short Message Service (SMS) Commands........................................................................................ 360
13.1 SMS parameters ......................................................................................................................... 360
13.2 AT+CMGC Send an SMS command......................................................................................... 365
13.3 AT+CMGD Delete short message............................................................................................. 366
13.4 AT+CMGF Select SMS message format .................................................................................. 367
13.5 AT+CMGL List SMS messages from preferred store................................................................ 368
13.6 AT+CMGR Read SMS messages............................................................................................. 370
13.7 AT+CMGS Send Short Message .............................................................................................. 372
13.8 AT+CMGW Write Short Messages to Memory ......................................................................... 374
13.9 AT+CMSS Send short messages from storage ........................................................................ 376
13.10 AT+CNMA New Message Acknowledgement to ME/TE, only phase 2+ .................................. 377
13.11 AT+CNMI New short Message Indication ................................................................................. 378
13.12 AT+CPMS Preferred SMS message storage............................................................................ 381
13.13 AT+CSCA SMS Service Center Address .................................................................................. 383
13.14 AT+CSCB Select Cell Broadcast Message Indication .............................................................. 384
13.15 AT+CSDH Show SMS text mode parameters........................................................................... 385
13.16 AT+CSMP Set SMS text Mode Parameters.............................................................................. 386
13.17 AT+CSMS Select Message Service.......................................................................................... 388
13.18 AT^SCML List Concatenated Short Messages from preferred store ........................................ 390
13.19 AT^SCMR Read Concatenated Short Messages ..................................................................... 391
13.20 AT^SCMS Send Concatenated Short Messages...................................................................... 392
13.21 AT^SCMW Write Concatenated Short Messages to Memory................................................... 393
13.22 AT^SLMS List SMS Memory Storage ....................................................................................... 394
13.23 AT^SMGL List Short Messages from preferred store without setting status to REC READ ..... 395
13.24 AT^SMGO Set or query SMS overflow presentation mode or query SMS overflow ................. 396
13.25 AT^SMGR Read short message without setting status to REC READ..................................... 398
13.26 AT^SSCONF SMS Command Configuration ........................................................................... 399
13.27 AT^SSDA Set SMS Display Availability .................................................................................... 400
13.28 AT^SSMSS Set Short Message Storage Sequence ................................................................. 401
s
14. SIM related Commands ....................................................................................................................... 402
14.1 AT+CRSM Restricted SIM Access ............................................................................................ 402
14.2 AT+CSIM Generic SIM Access ................................................................................................. 405
14.3 AT^SATR Query SIM's Answer to Reset Data.......................................................................... 407
14.4 AT^SXSM Extended SIM Access.............................................................................................. 408
14.5 AT^SCKS Query SIM and Chip Card Holder Status ................................................................. 410
14.6 AT^SSET Indicate SIM data ready............................................................................................ 412
14.7 AT^SCID Display SIM card identification number ..................................................................... 413
14.8 AT+CXXCID Display card ID..................................................................................................... 414
AC75_ATC_V01.002 Page 8 of 569 10/30/06 Confidential / Released
Page 9
AC75 AT Command Set
Contents
15. Remote SIM Access (RSA) Commands .............................................................................................415
15.1 AT^SRSA Remote SIM Access Activation ................................................................................ 418
15.2 AT^SRSM Remote SIM Access Message ................................................................................ 422
15.2.1 SAP Request Message Parameters ............................................................................ 425
15.2.2 SAP Response Message Parameters ......................................................................... 425
15.3 Related AT Commands............................................................................................................... 426
15.3.1 Establishing an RSA Connection in a PC Environment............................................... 426
15.3.2 Bluetooth scenario (SAP) ............................................................................................ 426
15.3.3 Serial Interface Scenario (XSAP) ................................................................................ 427
16. SIM Application Toolkit (SAT) Commands........................................................................................ 428
16.1 AT^SSTA SAT Interface Activation ........................................................................................... 428
16.2 ^SSTN SAT Notification ............................................................................................................ 430
16.3 AT^SSTGI SAT Get Information ............................................................................................... 431
16.4 AT^SSTR SAT Response .........................................................................................................432
17. Phonebook Commands....................................................................................................................... 433
17.1 Sort Order for Phonebooks ......................................................................................................... 433
17.2 AT+CNUM Read own numbers................................................................................................. 434
17.3 AT+CPBR Read from Phonebook............................................................................................. 435
17.4 AT+CPBS Select phonebook memory storage ......................................................................... 438
17.5 AT+CPBW Write into Phonebook ............................................................................................. 440
17.6 AT^SPBW Write into Phonebook with location report............................................................... 443
17.7 AT^SDLD Delete the 'last number redial' memory .................................................................... 446
17.8 AT^SPBC Find first matching entry in sorted phonebook .........................................................447
17.9 AT^SPBD Purge phonebook memory storage.......................................................................... 448
17.10 AT^SPBG Display phonebook entries in alphabetical order ..................................................... 449
17.11 AT^SPBS Step through the selected phonebook alphabetically............................................... 452
s
18. Audio Commands ................................................................................................................................ 456
18.1 Audio programming model .......................................................................................................... 456
18.2 ATL Set monitor speaker loudness ........................................................................................... 457
18.3 ATM Set monitor speaker mode................................................................................................ 457
18.4 AT+CLVL Loudspeaker volume level........................................................................................ 458
18.5 AT+CMUT Mute control ........................................................................................................
18.6 AT+VTD Tone duration ............................................................................................................. 460
18.7 AT+VTS DTMF and tone generation......................................................................................... 461
18.8 AT^SAIC Audio Interface Configuration .................................................................................... 462
18.9 AT^SNFA Set or query of microphone attenuation .................................................................. 464
18.10 AT^SNFD Set audio parameters to manufacturer default values ............................................. 466
18.11 AT^SNFI Set microphone path parameters .............................................................................. 467
18.12 AT^SNFM Set microphone audio path and power supply......................................................... 468
18.13 AT^SNFO Set audio output (= loudspeaker path) parameter ................................................... 470
18.14 AT^SNFPT Set progress tones .................................................................................................472
18.15 AT^SNFS Select audio hardware set........................................................................................ 473
18.16 AT^SNFTTY Signal TTY/CTM audio mode capability............................................................... 476
18.17 AT^SNFV Set loudspeaker volume........................................................................................... 477
18.18 AT^SNFW Write audio setting in non-volatile store .................................................................. 478
18.19 AT^SRTC Ring tone configuration ............................................................................................ 479
.... 459
AC75_ATC_V01.002 Page 9 of 569 10/30/06 Confidential / Released
Page 10
AC75 AT Command Set
Contents
19. Hardware Related Commands............................................................................................................ 481
19.1 AT+CCLK Real Time Clock....................................................................................................... 481
19.2 AT+CALA Set alarm time ......................................................................................................... 482
19.3 AT^SAD Antenna Diagnosis .....................................................................................................485
19.4 AT^SBC Battery Charge Control............................................................................................... 486
19.4.1 Responses returned by read command....................................................................... 488
19.5 AT^SBV Battery/Supply Voltage ............................................................................................... 489
19.6 AT^SCTM Set critical operating temperature presentation mode or query temperature........... 490
19.6.1 Deferred shutdown ...................................................................................................... 492
19.7 AT^SSYNC Configure SYNC Pin.............................................................................................. 493
19.7.1 ME status indicated by status LED patterns ................................................................ 494
19.8 AT^SSPI Serial Protocol Interface ............................................................................................496
19.8.1 Specifying Delay Time for I²C ...................................................................................... 498
19.8.2 Selecting SPI Mode ..................................................................................................... 499
19.8.3 Transmitting Data over AT Interface............................................................................ 500
19.8.3.1 Structure of Messages on the I²C Bus......................................................................... 501
19.8.3.2 Structure of Messages on the SPI ............................................................................... 502
19.8.4 Error Handling on the I²C Bus...................................................................................... 502
19.8.5 Example: Using I²C Bus............................................................................................... 504
19.8.6 Example: Transfer and Response Messages on SPI .................................................. 505
19.9 AT^SWDAC Configure and Read PWM Signal for DAC........................................................... 506
s
20. GPIO Commands ................................................................................................................................. 508
20.1 AT^SPIO General Purpose IO Driver Open/Close.................................................................... 508
20.2 AT^SCPIN Pin Configuration .................................................................................................... 509
20.3 AT^SCPOL Polling Configuration.............................................................................................. 511
20.4 AT^SCPORT Port Configuration ............................................................................................... 513
20.5 AT^SDPORT Delete a Port Configuration................................................................................. 514
20.6 AT^SGIO Get IO state of a specified pin or port ....................................................................... 515
20.7 AT^SSIO Set IO state of a specified pin or port ........................................................................ 516
20.8 AT^SCCNT Configure Pulse Counter ....................................................................................... 517
20.8.1 Using the Pulse Counter in Limit Counter Mode.......................................................... 518
20.9 AT^SSCNT Start and Stop Pulse Counter ................................................................................ 519
20.9.1 Using the Pulse Counter in Start-Stop Counter Mode ................................................. 520
21. Java related Commands ..................................................................................................................... 521
21.1 AT^SJRA Run Java Application ................................................................................................ 521
21.2 AT^SJNET Set Dialup Network Access Parameters................................................................. 522
21.3 AT^SJOTAP Over The Air Application Provisioning ................................................................. 525
21.4 AT^SJSEC Write Binary Java Security Data............................................................................. 527
22. Miscellaneous Commands.................................................................................................................. 529
22.1 A/ Repeat previous command line ............................................................................................ 529
22.2 ATS3 Set command line termination character......................................................................... 530
22.3 ATS4 Set response formatting character .................................................................................. 531
22.4 ATS5 Write command line editing character ............................................................................. 532
22.5 AT^SFDL Enter Firmware Download Mode .............................................................................. 533
23. Appendix .............................................................................................................................................. 535
23.1 Restricted access to SIM data after SIM PIN authentication....................................................... 535
23.2 Star-Hash (*#) Network Commands............................................................................................ 536
AC75_ATC_V01.002 Page 10 of 569 10/30/06 Confidential / Released
Page 11
AC75 AT Command Set
Contents
23.3 Available AT Commands and Dependency on SIM PIN ............................................................. 539
23.4 Availability of AT Commands Depending on Operating Mode of ME.......................................... 546
23.5 AT Command Settings storable with AT&W................................................................................ 554
23.6 Factory Default Settings Restorable with AT&F.......................................................................... 557
23.7 Summary of Unsolicited Result Codes (URC)............................................................................. 560
23.8 Alphabetical List of AT Commands ............................................................................................. 563
s
AC75_ATC_V01.002 Page 11 of 569 10/30/06 Confidential / Released
Page 12
AC75 AT Command Set

List of Tables

s
List of Tables
Table 1.1: Symbols used to mark the type of parameters ...........................................................................17
Table 1.2: Symbols used to indicate the correlations with other commands ............................................... 17
Table 1.3: Symbols used to mark different types of default values of parameters ..................................... 17
Table 1.4: Types of AT commands and responses .................................................................................... 18
Table 1.5: Examples for character definitions depending on alphabet ........................................................ 21
Table 2.1: Current configuration on ASC0 / MUX channel 1 / USB (example)............................................ 34
Table 2.2: Current configuration on ASC1 and MUX channels 2 and 3 (example) .................................... 35
Table 2.3: Wake-up events in NON-CYCLIC and CYCLIC SLEEP modes ................................................. 45
Table 2.4: General "CME ERROR" Codes (GSM 07.07) .......................................................................... 49
Table 2.5: General "CME ERROR" Codes (SIEMENS) ............................................................................ 50
Table 2.6: GPRS related "CME ERROR" Codes (GSM 07.07) ................................................................. 50
Table 2.7: GPRS related "CME ERROR" Codes (SIEMENS) ................................................................... 50
Table 2.8: SMS related "CMS ERROR" Codes (GSM 07.05) ................................................................... 51
Table 4.1: Availability of AT Commands on Virtual Channels .................................................................. 120
Table 4.2: Summary of AT commands with Different Behavior in Multiplex Mode ................................... 121
Table 10.1: Applicability of AT^SICS <conParmTag> values ................................................................... 256
Table 10.2: Applicability of AT^SISS <srvParmTag> values ................................................................... 263
Table 12.1: Fax Result Codes ..................................................................................................................... 352
Table 19.1: Modes of the LED and indicated ME functions......................................................................... 494
Table 19.2: Values for calculating the delay................................................................................................ 498
Table 19.3: Special characters for ASCII coding ......................................................................................... 500
Table 19.4: Structure of Transfer and Response Messages on the I²C bus................................................ 501
Table 19.5: Structure of Transfer and Response Messages for SPI ........................................................... 502
Table 23.1: Star-Hash (*#) Command Overview ........................................................................................ 536
Table 23.2: Abbreviations of Codes and Parameters used in Table 23.1 .................................................. 537
Table 23.3: Star-Hash Command Response Parameters .......................................................................... 538
Table 23.4: Star-Hash Commands for Supplementary Services ................................................................ 538
Table 23.5: Available AT Commands and Dependency on SIM PIN........................................................... 539
Table 23.6: Availability of AT Commands Depending on Operating Mode of ME ....................................... 546
Table 23.7: Settings Stored to User Profile on ASC0 / MUX Channel 1...................................................... 554
Table 23.8: Settings Stored to User Profile on ASC1 / MUX Channels 2 and 3.......................................... 555
Table 23.9: Factory Default Settings Restorable with AT&F ....................................................................... 557
Table 23.10: Summary of Unsolicited Result Codes (URC) .......................................................................... 560
Table 23.11: Alphabetical List of AT Commands........................................................................................... 563
AC75_ATC_V01.002 Page 12 of 569 10/30/06 Confidential / Released
Page 13
AC75 AT Command Set

List of Figures

s
List of Figures
Figure 1.1: Main character table of GSM 03.38 alphabet ............................................................................. 22
Figure 1.2: Extension character table of GSM 03.38 alphabet ..................................................................... 23
Figure 15.1: Basic Remote SIM Access Usage Scenario via Bluetooth ....................................................... 415
Figure 15.2: Basic Remote SIM Access usage scenario via RS232 ............................................................ 415
Figure 15.3: SIM usage states of SAP server............................................................................................... 416
Figure 15.4: SIM usage states of SAP client ................................................................................................ 417
Figure 18.1: Audio programming model for AC75 Module............................................................................ 456
Figure 19.1: Formula for calculating the delay.............................................................................................. 498
Figure 19.2: Delay time on I²C after Write .................................................................................................... 498
Figure 19.4: SPI modes selectable on SPI ................................................................................................... 499
Figure 19.3: Delay time on I²C after Read .................................................................................................... 499
AC75_ATC_V01.002 Page 13 of 569 10/30/06 Confidential / Released
Page 14
AC75 AT Command Set

1. Introduction

s
1. Introduction

1.1 Scope of the document

This document presents the AT Command Set for the Siemens Cellular Engine AC75 Release 01.002.
Before using the Cellular Engine or upgrading to a new firmware version please read the latest product informa­tion provided in the Release Notes [1].
More information is available at the Siemens Website: http://www.siemens.com/wm
.
AC75_ATC_V01.002 Page 14 of 569 10/30/06 Confidential / Released
Page 15
AC75 AT Command Set

1.2 Related documents

s
1.2 Related documents
[1] AC75 Release Notes, Version 01.002 [2] AC75 Hardware Interface Description, Version 01.002 [3] AC75 Java User's Guide [4] Remote-SAT User's Guide [5] GPRS Startup User's Guide [6] Multiplexer User's Guide [7] Multiplex Driver Developer's Guide for Windows 2000 and Windows XP [8] Multiplex Driver Installation Guide for Windows 2000 and Windows XP
[9] Application Note 02: Audio Interface Design [10] Application Note 16: Updating AC75 Firmware [11] Application Note 17: Over-The-Air Firmware Update [12] Application Note 24: Application Developer's Guide [13] Application Note 22: Using TTY / CTM equipment with AC75 [14] SIM Access Profile Interoperability Specification (Revision 1.0), issued by the Bluetooth Special Interest
Group
[15] ISO/IEC10646: "Universal Multiple-Octet Coded Character Set (UCS)"; UCS2, 16 bit coding [16] ITU-T Recommendation V.24: List of definitions for interchange circuits between data terminal equipment
(DTE) and data circuit-terminating equipment (DCE)
[17] ITU-T Recommendation V.250: Serial asynchronous automatic dialling and control [18] 3GPP TS 100 918/EN 300 918 (GSM 02.04): General on supplementary services [19] 3GPP TS 100 907 (GSM 02.30): Man-Machine Interface (MMI) of the Mobile Station (MS) [20] 3GPP TS 23.038 (GSM 03.38): Alphabets and language specific information [21] 3GPP TS 27.005 (GSM 07.05): Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE
- DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)
[22] 3GPP TS 27.007 (GSM 07.07): AT command set for User Equipment (UE) [23] 3GPP TS 27.060 (GSM 07.60): Mobile Station (MS) supporting Packet Switched Services [24] 3GPP TS 51.011 (GSM 11.11): Specification of the Subscriber Identity Module - Mobile Equipment (SIM -
ME) interface
[25] 3GPP TS 11.14 (GSM 11.14): Specification of the SIM Application Toolkit for the Subscriber Identity Module
- Mobile Equipment (SIM - ME) interface
[26] 3GPP TS 22.101 (GSM 22.101): Service principles [27] Common PCN Handset Specification (CPHS) v4.2 [28] USB.ORG: www.usb.org/developers/docs/USB_LANGIDs.pdf
AC75_ATC_V01.002 Page 15 of 569 10/30/06 Confidential / Released
Page 16
AC75 AT Command Set

1.3 Document conventions

s
1.3 Document conventions
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 modem, FAX board). To control your GSM engine you can simply send AT Commands via its serial interface. The controlling 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 defi­nitions please refer to TR 100 350 V7.0.0 (1999-08), (GSM 01.04, version 7.0.0 release 1998).

1.3.1 Quick reference table

Each AT command description includes a table similar to the example shown below. The table is intended as a quick reference to indicate the following functions: PIN: Is the AT command PIN protected? + Yes
- No ± Usage is dependent on conditions specified for the command, or not all command types are PIN
protected (for example write command PIN protected, read command not).
Note: The table provided in Section 23.3, Available AT Commands and Dependency on SIM
PIN uses the same symbols.
ASC0: Is the AT command supported on the first physical serial interface ASC0? + Yes
- No ASC1: Is the AT command supported on the second physical serial interface ASC1? + Yes
- No USB: Is the AT command supported on the USB interface? + Yes
- No MUXn: Is the AT command usable on the Multiplexer channels MUX1, MUX2, MUX3? + Yes
- No
± AT command is usable, but under the restrictions specified in the section related to the command. Note: The columns MUX1, MUX2 and MUX3 are relevant only when the GSM engine operates in Mul-
tiplexer mode, that is, when the first physical serial interface is partitioned into 3 virtual channels by using the Multiplexer protocol. Usage is the same on ASC0 and MUX1.
4
+ Yes
- No ± In AIRPLANE mode, not all described functions are available. For example, the test or read com-
Charge: Is the AT command supported in CHARGE ONLY mode? + Yes
- No ± AT command is usable, but under the restrictions specified in the section related to the command. Last: If commands are concatenated, this AT command must be the last one. + Yes
- No Note: See also Section 1.4, AT Command Syntax for details on concatenated AT commands.
Is the AT command supported in AIRPLANE mode?
mand is usable, the write or execute command is not. Furthermore, only some of the listed parameters can be changed in AIRPLANE mode. A typical example is AT^SCFG that controls dif­ferent features.
Example:
PIN ASC0 ASC1 USB MUX1 MUX2 MUX3 Charge 4 Last
- + + + ± ± ± + - -
AC75_ATC_V01.002 Page 16 of 569 10/30/06 Confidential / Released
Page 17
AC75 AT Command Set
1.3 Document conventions

1.3.2 Superscript notation for parameters and values

Table 1.1: Symbols used to mark the type of parameters
Parameter type Meaning
<param>
<param>
Table 1.2: Symbols used to indicate the correlations with other commands
Parameter option Meaning
<param>
<param>
<param>
<param>
Table 1.3: Symbols used to mark different types of default values of parameters
(num)
(str)
(&W)
(&V)
(ˆSNFW)
(+CSCS)
Parameter value must be numeric type Parameter value must be string type
Parameter value will be stored with AT&W Parameter value will be displayed with AT&V Parameter value will be stored with AT^SNFW Parameter value has to be (is) coded according to current setting of <chset> (see
AT+CSCS for details)
s
Value option Meaning
[x] Default value: if the parameter is omitted, the value 'x' will be assumed
(&F)
x
(P)
x
(D)
x
Factory default value, will be restored to 'x' with AT&F Powerup default value of a parameter which is not stored at power down Delivery default value of a parameter which cannot be restored automatically
AC75_ATC_V01.002 Page 17 of 569 10/30/06 Confidential / Released
Page 18
AC75 AT Command Set

1.4 AT Command Syntax

s
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>". Through-
out this document, only the responses are presented,
Table 1.4: Types of AT commands and responses
AT command type Syntax Function
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. Exec(ution) command AT+CXXX The execution command reads non-variable parameters deter-
mined by internal processes in the GSM engine.
<CR><LF> are omitted intentionally.

1.4.1 Using Parameters

• Optional parameters are enclosed in square brackets. If optional parameters are omitted, the current settings are used until you change them.
• Optional parameters or subparameters can be omitted unless they are followed by other parameters. If you want to omit a parameter in the middle of a string it must be replaced by a comma. See also example 1.
• A parameter value enclosed in square brackets represents the value that will be used if an optional parameter is omitted. See also example 2.
• 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 in 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.
• If an optional parameter of a V.250 command is omitted, its value is assumed to be 0.
Example 1: Omitting parameters in the middle of a string
AT+CCUG? +CCUG: 1,10,1 OK AT+CCUG=,9 OK AT+CCUG? +CCUG: 1,9,1 OK
Example 2: Using default parameter values for optional parameters
Query current setting
Set only the middle parameter
Query new setting
AT+CFUN=7,0 OK AT+CFUN? +CFUN: 7 OK AT+CFUN= OK +CFUN: 1 OK
AC75_ATC_V01.002 Page 18 of 569 10/30/06 Confidential / Released
Activate CYCLIC SLEEP mode, don't reset ME
Query ME mode
Set ME back to normal (default parameters: 1,0)
Page 19
AC75 AT Command Set
1.4 AT Command Syntax
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 table below lists the AT commands you cannot enter together with other commands on the same line. Oth­erwise, the responses may not be in the expected order.
AT command type Comment V.250 commands with FAX commands (Prefix AT+F) GSM 7.07 commands with Siemens commands, Prefix AT^S) 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 and the associated responses is your concern, avoid concatenating commands on the same line.
AC75_ATC_V01.002 Page 19 of 569 10/30/06 Confidential / Released
Page 20
AC75 AT Command Set

1.5 Supported character sets

s
1.5 Supported character sets
The ME supports two character sets: GSM 03.38 (7 bit, also referred to as GSM alphabet or SMS alphabet) and UCS2 (16 bit, refer to ISO/IEC 10646). See AT+CSCS for information about selecting the character set. Character tables can be found below.
Explanation of terms
• International Reference Alphabet (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 characters). IRA is used here for input 8-bit or 16-bit data via terminal devices using text mode. This means only characters 'A'..F','a'..'f' and '0'..'9' are valid.
• Escape sequences The escape sequence used within a text coded in the GSM default alphabet (0x1B) must be correctly inter­preted by the TE, both for character input and output. To the module, an escape sequence appears like any other byte received or sent.
• Terminal Adapter (TA) TA is an equivalent to Mobile Equipment (ME) which stands for the GSM module described here. It uses GSM default alphabet as its character set.
• Terminal Equipment (TE) TE is the device connected to the TA via serial interface. In most cases TE is an ANSI/ASCII terminal that does not fully support the GSM default alphabet, for example MS Hyperterminal.
• TE Character Set The character set currently used by Terminal Equipment is selected with AT+CSCS.
• Data Coding Scheme (dcs) 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 and determines the coded character set.
The behavior when encountering characters that are not valid characters of the supported alphabets is unde­fined. Due to the constraints described below it is recommended to prefer the USC2 alphabet in any external applica­tion. If the GSM alphabet is selected all characters sent over the serial line (between TE and TA) are in the range from 0 to 127 (7 Bit range). CAUTION: ASCII alphabet (TE) is not GSM alphabet (TA/ME) !
Several problems resulting from the use of GSM alphabet with ASCII terminal equipment:
• "@" character with GSM alphabet value 0 is not printable by an ASCII terminal program (e.g. Microsoft© Hyperterminal®).
• "@" character with GSM alphabet value 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 the table below. By the way, this may be the reason why even network providers often replace "@"with "@=*" in their SIM application.
• Other characters of the GSM alphabet are misinterpreted by an ASCII terminal program. For example, GSM "ö" (as in "Börse") is assumed to be "|" in ASCII, thus resulting in "B|rse". This is because both alphabets mean different characters with values hex. 7C or 00 and so on.
• 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 escape 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.
AC75_ATC_V01.002 Page 20 of 569 10/30/06 Confidential / Released
Page 21
AC75 AT Command Set
1.5 Supported character sets
Table 1.5: Examples for character definitions depending on alphabet
s
GSM 03.38 character
Ö 5C \ \5C 5C 35 43 " 22 " \22 5C 32 32 @ 00 NULL \00 5C 30 30
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 mes­sages which may contain differently coded characters.
GSM character hex. value
Corresponding ASCII character
ASCII Esc sequence
Hex Esc sequence
AC75_ATC_V01.002 Page 21 of 569 10/30/06 Confidential / Released
Page 22
AC75 AT Command Set
1.5 Supported character sets
s

1.5.1 GSM alphabet tables and UCS2 character values

This section provides tables for the GSM 03.38 alphabet supported by the ME. Below any GSM character find the corresponding two byte character value of the UCS2 alphabet. (For related mapping definition see: http://www.unicode.org/Public/MAPPINGS/ETSI/GSM0338.TXT)
Figure 1.1: Main character table of GSM 03.38 alphabet
1) This code is an escape to the following extension of the 7 bit default alphabet table.
2) This code is not a printable character and therefore not defined for the UCS2 alphabet. It shall be treated as the accom­panying control character.
3) As the standard GSM alphabet does not provide a backspace functionality the AC75 is designed to use the GSM charac­ter 08 (hex 0x08) as backspace. This allows the user to easily erase the last character when using an ASCII terminal. On the other hand, this solution requires entering the escape sequence \08 for writing the "ò" character in GSM alphabet.
AC75_ATC_V01.002 Page 22 of 569 10/30/06 Confidential / Released
Page 23
AC75 AT Command Set
1.5 Supported character sets
s
Figure 1.2: Extension character table of GSM 03.38 alphabet
1) This code value is reserved for the extension to another extension table. On receipt of this code, a receiving entity shall display a space until another extension table is defined.
2) This code represents the EURO currency symbol. The code value is the one used for the character 'e'. Therefore a receiv­ing entity which is incapable of displaying the EURO currency symbol will display the character 'e' instead.
3) This code is defined as a Page Break character and may be used for example in compressed CBS messages. Any mobile which does not understand the 7 bit default alphabet table extension mechanism will treat this character as Line Feed.
AC75_ATC_V01.002 Page 23 of 569 10/30/06 Confidential / Released
Page 24
AC75 AT Command Set
1.5 Supported character sets
In the event that an MS receives a code where a symbol is not represented in Figure 1.2, Extension character
table of GSM 03.38 alphabet the MS shall display the character shown in the main default 7 bit alphabet table
(see Figure 1.1, Main character table of GSM 03.38 alphabet).
s

1.5.2 UCS2 and GSM data coding and conversion for SMS text mode

This section provides basic information on how to handle input and output character conversion for SMS text mode and Remote-SAT if internal (TA) and external (TE) character representation differ, i.e. if the Data Coding Scheme and the TE character use different coding.
1.5.2.1 Implementing output of SIM data to Terminal (direction TA to
TE)
Used character set DCS = 7 bit
GSM
GSM Case 1
GSM (1:1)
UCS2 Case 4
GSM to IRA (1:4)
Note: The ratio of SIM bytes to output bytes is given in parentheses.
Case 1 Every GSM character is sent to the TE as it is (8-bit value with highest bit set to zero). Example: 47'H, 53'H, 4D'H → 47'H, 53'H, 4D'H, displayed as "GSM"
Case 2 Every data byte is sent to the TE as 2 IRA characters each representing a halfbyte. Example: B8'H (184 decimal) → 42'H, 38'H, displayed as "B8"
Case 3 Every 16-bit UCS2 value is sent to the TE as 4 IRA characters. Example: C4xA7'H (50343 decimal) → 43'H, 34'H, 41'H, 37'H, displayed as "C4A7" Problem: An odd number of bytes leads to an error because there are always two bytes needed for each USC2 character
Case 4 Every GSM character is sent to the TE as 4 IRA characters to show UCS2 in text mode. Example: 41'H ("A") → 30'H, 30'H, 34'H, 31'H, displayed as "0041"
DCS = 8 bit Data
Case 2 8 bit to IRA (1:2)
Case 5 8 bit to IRA (1:4)
DCS = 16 bit UCS2
Case 3 UCS2 to IRA (2:4)
Case 6 UCS2 to IRA (2:4)
Case 5 Every data byte is sent to the TE as IRA representation of UCS2 (similar to case 4). Example: B2'H → 30'H, 30'H, 42'H, 32'H, displayed as "00B2"
Case 6 Every 16-bit value is sent to the TE as IRA representation of it. It is assumed that number of bytes is even. Example: C3x46'H → 43'H, 33'H, 34'H, 36'H, displayed as "C346"
AC75_ATC_V01.002 Page 24 of 569 10/30/06 Confidential / Released
Page 25
AC75 AT Command Set
1.5 Supported character sets
s
1.5.2.2 Implementing input of Terminal data to SIM (direction TE to TA)
Used character set DCS = 7 bit
GSM
GSM Case 1
GSM (1:1)
UCS2 Case 4
UCS2 to GSM (4:1)
Note: The ratio between the number of input characters and bytes stored on the SIM is given in parentheses.
Case 1 Every character is sent from TE to TA as GSM character (or ASCII with standard terminal emulation, e.g. Hyper­terminal). Character value must be in range from 0 to 127 because of 7-bit GSM alphabet. To reach maximum SMS text length of 160 characters in 140 bytes space characters will be compressed on SIM. This must be set using the parameter <dcs> of AT+CSMP (add 64). Example: "ABCDEFGH" typed is sent and stored uncompressed as → 4142434445464748'H (stored com­pressed as 41E19058341E91'H)
Case 2 Every data byte is sent as 2 IRA characters. Maximum text length is 280 IRA characters which will be converted into 140 bytes SMS binary user data Example: "C8" typed is sent as 43'H, 38'H → stored as C8'H
Case 3 Every 16-bit value is sent as 4 IRA characters. Maximum text length is 280 IRA characters which will be converted into 70 UCS2 characters (16-bit each) Number of IRA characters must be a multiple of four because always 4 half bytes are needed for a 16-bit value Example: "D2C8" typed is sent as 44'H, 32'H, 43'H, 38'H → stored as D2C8'H
DCS = 8 bit Data
Case 2 IRA to 8 bit (2:1)
Case 5 UCS2 to 8 bit (4:1)
DCS = 16 bit UCS2
Case 3 IRA to 16 bit (4:2)
Case 6 UCS2 to 16 bit (4:2)
Case 4 Every GSM character is sent as 4 IRA characters representing one UCS2 character. Example: To store text "ABC" using UCS2 character set you have to type "004100420043". This is sent as 30'H,30'H,34'H,31'H, 30'H,30'H,34'H,32'H, 30'H,30'H,34'H,33'H → detected as IRA representa­tion of 3 UCS2 characters, converted to GSM character set and stored as 41'H, 42'H, 43'H. Maximum input is 640 IRA characters repesenting 160 UCS2 characters when compression is active. These are converted to 160 GSM 7-bit characters. Without compression only 140 GSM characters can be stored which are put in as 560 IRA characters. Values of UCS2 characters must be smaller than 80'H (128 decimal) to be valid GSM characters. Number of IRA characters must be a multiple of four. Problems:
• "41" → Error, there are four IRA characters (two bytes) needed
• "0000" → Error, not an UCS2 character
• "4142" → Error, value of UCS2 character > 7F'H
• "008B" → Error, value of UCS2 character > 7F'H
This affects the maximum input length of a string)
Case 5 Every UCS2 character is sent as 4 IRA characters and is converted into two 8-bit values. This means that the first two characters have to be '00'. Example: UCS2 character 009F'H typed as "009F" is sent as 30'H,30'H,39'H,46'H → converted into 8-bit value 9F'H. Maximum number of UCS2 characters is 140 which are represented by 560 IRA characters. Number of IRA char­acters must be a multiple of four.
Case 6 Every UCS2 character is sent as 4 IRA characters each and is converted into a 16-bit value again. Example: UCS2 character 9F3A'H typed as "9F3A" is sent as 39'H,46'H,33'H,41'H → converted into 9F3A'H. Maximum number of UCS2 characters is 70 which are represented by 280 IRA characters. Number of IRA char­acters must be a multiple of four. Invalid UCS2 values must be prevented.
AC75_ATC_V01.002 Page 25 of 569 10/30/06 Confidential / Released
Page 26
AC75 AT Command Set

1.6 Serial Interface Flow Control

s
1.6 Serial Interface 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 until it catches up. There are basically two approaches to regulate data flow: Software flow control and hardware flow control. The High Watermark (HWM) of the input/output buffer should be set to approximately 60% of the total buffer size, the Low Watermark (LWM) is recommended to be about 30%. The data flow should be stopped when the buffer 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.

1.6.1 Software Flow Control (XON/OFF Handshake)

Software flow control sends different characters to stop (XOFF, decimal 19) and resume (XON, decimal 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 Handshake)

Hardware flow control sets or resets the RTS/CTS wires. This approach is faster and more reliable, and there­fore, the better choice. When the HWM is reached, CTS is set inactive. When the LWM is passed, CTS goes active again. To achieve smooth data flow,ensure that the RTS/CTS lines are present on your application plat­form.
Configuring hardware flow control
• Hardware flow control must be set on both sides: with AT\Q3 or AT+IFC in the ME and an equivalent RTS/ CTS handshake option in the host application.
• The default setting of the ME is AT\Q0 (no flow control) which must be altered to AT\Q3 (RTS/CTS hardware handshake on). The setting is stored volatile and must be restored each time after rebooting the ME.
• AT\Q has no read command. To verify the current setting of AT\Q, simply check the settings of the active profile with AT&V.
• Often, fax programs run an intialization procedure when started up. The intialization commonly includes enabling RTS/CTS hardware handshake, eliminating the need to set AT\Q3 once again. However, before set­ting up a CSD call, you are advised to check that RTS/CTS handshake is set.
Buffer design considerations
• Each serial interface (ASC0 and ASC1) of the AC75 uses two buffers, one for the uplink and one for the down­link. Each buffer has a capacity of minimum 1024 bytes.
• Uplink direction (where ME is receiving data from host application): CTS control is based on the filling level of the ME's receive buffer. When the application detects that CTS is being deactivated it must instantly stop sending data to the ME's receive buffer. But still, after deactivation of CTS, the receive buffer of the ME can accept another 512 bytes.
• Downlink direction (where ME is sending data to host application): The transmit buffer of the ME can hold at least 1024 bytes. After deactivation of RTS the ME sends max. 2 more bytes and then stops transferring data to the application. The maximum time RTS can be kept inactive without losing data is determined by the buffer size and the max­imum possible over-the-air data rate. In any case, the local data rate between DCE and DTE (AT+IPR) should be set to a value higher than the maximum possible over-the-air data rate.
• Buffer size recommended for the host application: Just like the ME, the host application should include send and receive buffers for each serial interface. To handle large amounts of data at high speed a buffer capacity of 1024 bytes is recommended. If the host appli­cation is designed mainly for one direction (uplink or downlink) a lower buffer size will do for the direction where less data is transferred. In fact, the optimal size of the host application buffers is a matter of finding the balance between the amount
AC75_ATC_V01.002 Page 26 of 569 10/30/06 Confidential / Released
Page 27
AC75 AT Command Set
1.6 Serial Interface Flow Control
of data, data throughput, reaction time of the application when handling the buffer, processor performance and available memory. To give an example, a small buffer size (such as 256 bytes) increases the frequency of deactivating RTS/CTS and the frequency of flushing the buffer, thus diminishing the efficiency of the appli­cation. Also, please consider that RTS/CTS flow control cannot stop the data stream coming from the network, e.g. in a GPRS or fax connection. So the lack of appropriate hardware flow control increases the risk of losing data packets if, like in the case of UDP, the connection protocol has no or only minimum error handling functions. Other network protocols are using high level flow control mechanisms. For example, to prevent loss of data the TCP protocol uses retransmission algorithms, fax applications usually repeat the transfer of faulty pages.
s
AC75_ATC_V01.002 Page 27 of 569 10/30/06 Confidential / Released
Page 28
AC75 AT Command Set

1.7 Communication between Customer Application and AC75

s
1.7 Communication between Customer Application and AC75
Leaving hardware flow control unconsidered the Customer Application (TE) is coupled with the AC75 (ME) via a receive and a transmit line. Since both lines are driven by independent devices collisions may (and will) happen. For example, if the TE issues an AT command the AC75 starts sending a URC. This will probably cause the TE to misinterpret of the URC being part of the AT command's response.
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 milliseconds before sending the next one. This gives the AC75 the opportunity to transmit pending URCs and get necessary service. Note that some AT commands may require more delay after "OK" or "ERROR" response, refer to the following command specifications for details.
• The TE shall communicate with the AC75 using activated echo (ATE1), i.e. the AC75 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 itself it has control both over the receive and the transmit paths.
AC75_ATC_V01.002 Page 28 of 569 10/30/06 Confidential / Released
Page 29
AC75 AT Command Set

1.8 Unsolicited Result Code Presentation

s
1.8 Unsolicited Result Code Presentation
URC stands for Unsolicited Result Code and is a report message issued by the ME without being requested by the TE, i.e. a URC is issued automatically when a certain event occurs. Hence, a URC is not issued as part of the response related to an executed AT command. Typical events leading to URCs are incoming calls ("RING"), waiting calls, received short messages, changes in temperature, network registration etc. A list of all URCs can be found in Section 23.7, Summary of Unsolicited Result Codes (URC).
To announce a pending URC transmission the ME will do the following:
• The ME activates its RING line (logic "1") for 1 second, i.e. the RING line changes to the physical "Low" level. This allows the TE to stay in power saving mode until an ME related event requests service. If several URCs occur coincidently or in quick succession each URC triggers the RING line independently, although the line will not be deactivated between each URC. As a result, the RING line may stay low for more than 1 second. If an incoming call is answered within less than 1 second (with ATA or if autoanswering is set to ATS0=1) than the RING line will be deactivated earlier. The "^SHUTDOWN" URC will not activate the RING line.
• 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 in the following cases:
- During the processing of an AT command (i.e. the time after the TE echoes back the first character "A" of
an AT command just sent by itself until the ME responds with "OK" or "ERROR").
- During a data call. Please note that AT command settings may be necessary to enable in-band signaling, e.g. 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 the AC75, for details refer to [6] and 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 a URC. Depending on the AT command, the URC presentation mode can be saved to the user defined profile (see AT&W), or needs to be activated every time you reboot the ME. Several URCs are not user definable, such as "^SYSSTART", "^SYSSTART <text>", "^SHUTDOWN" If autobauding is enabled (AT+IPR=0), URCs generated after restart will be output with 115200 bps until the ME has detected the current bit rate. The URCs "^SYSSTART", "^SYSSTART <text>", however, are not presented at all. For details please refer to Section 4.9.1, Autobauding. To avoid problems we recommend to configure a fixed bit rate rather than using autobauding.
AC75_ATC_V01.002 Page 29 of 569 10/30/06 Confidential / Released
Page 30
AC75 AT Command Set

1.9 Common PCN Handset Specification (CPHS)

s
1.9 Common PCN Handset Specification (CPHS)
The ME provides features to implement a device following the prerequisites of the Common PCN Handset Spec­ification (CPHS) Phase 2.
CPHS Feature Description/Remarks AT command Alternate Line Service Using two phone numbers with one SIM card. AT^SALS Voice Message Waiting
Indication
Operator (Service pro­vider) name from SIM
Network and Service Pro­vider Lock
Call Forwarding Get and set diverted call status. Access specific Elementary
Customer Service Profile (CSP)
Information numbers Hierarchically structured service numbers phonebook on
Indicate the receipt of a short message coded as Voice Mes­sage Waiting Indicator as defined by the CPHS Phase 2 standard.
Read specific Elementary Files (6F14h, 6F18h) from SIM. AT+CRSM
Lock/Unlock an ME to specific HPLMN and service provider. AT+CLCK,
File (6F13h) from SIM. Setting services and their menu entries depending on cus-
tomer profiles.
SIM according to CPHS 4.2 (mandatory).
AT^SIND, AT+CMER, indicators
"vmwait1" and "vmwait2"
(AT+CPIN)
AT+CCFC, AT+CRSM
AT+CRSM
AT+CRSM
AC75_ATC_V01.002 Page 30 of 569 10/30/06 Confidential / Released
Page 31
AC75 AT Command Set

1.10 Errors and Messages

s
1.10 Errors and Messages
The command result codes "+CME ERROR: <err>" and "+CMS ERROR: <err>" indicate errors related to mobile equipment or network functionality.
The format of <err> can be either numeric or verbose and is selectable via AT+CMEE.
A result error code terminates the execution of the command and prevents the execution of all remaining com­mands that may follow on the same command line. If so, neither "ERROR" nor "OK" result codes are returned for these commands. A 30 seconds timeout will deliver "ERROR" when the input of a command is not complete.
Using the wrong command syntax may result in errors: For example, using the execute command syntax although the command has no execute format, causes "ERROR" to be returned. Likewise, using the write com­mand syntax although the command has no write format causes "+CME ERROR: <err>" to be returned.
See also:
• Section 2.12.1, CME/CMS Error Code Overview
• Section 2.5.1, Verbose and numeric result codes
• Section 3.4, AT+CEER
AC75_ATC_V01.002 Page 31 of 569 10/30/06 Confidential / Released
Page 32
AC75 AT Command Set

2. Configuration Commands

s
2. Configuration Commands
The AT Commands described in this chapter allow the external application to determine the AC75's behaviour under various conditions.

2.1 AT&F Set all current parameters to manufacturer defaults

AT&F sets all current parameters to the manufacturer defined profile. All defined GPRS contexts which are not
activated or not online will be undefined if the non volatile storage of CGDCONT settings is not activated by the
AT^SCFG parameter "GPRS/PersistentContexts" (see AT+CGDCONT).
Syntax
Exec Command
AT&F[<value>]
Response(s)
OK
Reference(s) PIN ASC0 ASC1 USB MUX1 MUX2 MUX3 Charge 4 Last
V.250 - + + + + + + - + -
Parameter Description
<value>
[0] Set all TA parameters to manufacturer defaults
(num)
Notes
• List of parameters reset to manufacturer default can be found in Section 23.6, Factory Default Set-
tings Restorable with AT&F.
• In addition to the default profile, you can store an individual one with AT&W. To alternate between the two pro­files enter either ATZ (loads user profile) or AT&F (restores factory profile).
• Every ongoing or incoming call will be terminated.
AC75_ATC_V01.002 Page 32 of 569 10/30/06 Confidential / Released
Page 33
AC75 AT Command Set
2.2 AT&V
s

2.2 AT&V Display current configuration

AT&V returns the current parameter setting. The configuration varies depending on whether or not PIN authen-
tication has been done and whether or not Multiplex mode is enabled (see AT+CMUX).
Syntax
Exec Command
AT&V[<value>]
Response(s)
ACTIVEPROFILE:
... (see Section 2.2.1, AT&V responses)
OK
Reference(s) PIN ASC0 ASC1 USB MUX1 MUX2 MUX3 Charge 4 Last
V.250 - + ± + + ± ± - + -
Parameter Description
<value>
[0] Profile number
(num)
Notes
• The value of \Q (flow control) is also determined by the AT+IFC command. In case the value set by AT+IFC cannot be represented by a \Q equivalent, \Q255 will be displayed.
• The parameters of AT^SMGO can only be displayed after the SMS data from the SIM have been read success­fully 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 PDU mode, see AT+CMGF.
AC75_ATC_V01.002 Page 33 of 569 10/30/06 Confidential / Released
Page 34
AC75 AT Command Set
2.2 AT&V
s

2.2.1 AT&V responses

The following tables show four different kinds of responses depending on whether or not the PIN is entered and whether or not the Multiplex mode is enabled (see AT+CMUX).
Table 2.1: Current configuration on ASC0 / MUX channel 1 / USB (example)
PIN authentication done No PIN authentication ACTIVE PROFILE:
E1 Q0 V1 X4 &C1 &D2 &S0 \Q0 \V1 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 +ICF: 3 +IFC: 0,0 +ILRR: 0 +IPR: 115200 +CMEE: 2 ^SMGO: 0,0 +CSMS: 0,1,1,1 ^SACM: 0,"000000","000000" ^SLCC: 0 ^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 \V1 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 +ICF: 3 +IFC: 0,0 +ILRR: 0 +IPR: 115200 +CMEE: 2 ^SCKS: 0,1 ^SSET: 0 OK
AC75_ATC_V01.002 Page 34 of 569 10/30/06 Confidential / Released
Page 35
AC75 AT Command Set
2.2 AT&V
Table 2.2: Current configuration on ASC1 and MUX channels 2 and 3 (example)
PIN authentication done No PIN authentication ACTIVE PROFILE:
E1 Q0 V1 X4 &C1 &D0 &S0 \Q0 \V1 S0:000 S3:013 S4:010 S5:008 +CR: 0 +CRC: 0 +CMGF: 1 +CSDH: 0 +CNMI: 0,0,0,0,1 +ICF: 3 +IFC: 0,0 +ILRR: 0 +IPR: 115200 +CMEE: 2 ^SMGO: 0,0 +CSMS: 0,1,1,1 ^SACM: 0,"000000","000000" ^SLCC: 0 ^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 \V1 S0:000 S3:013 S4:010 S5:008 +CR: 0 +ICF: 3 +IFC: 0,0 +ILRR: 0 +IPR: 115200 +CMEE: 2 ^SCKS: 0,1 ^SSET: 0 +CGSMS: 3 OK
s
AC75_ATC_V01.002 Page 35 of 569 10/30/06 Confidential / Released
Page 36
AC75 AT Command Set
2.3 AT&W
s

2.3 AT&W Stores current configuration to user defined profile

AT&W stores the currently set parameters to a user defined profile in the non-volatile memory.
Syntax
Exec Command
AT&W[<value>]
Response(s)
OK ERROR/+CME ERROR <err>
Reference(s) PIN ASC0 ASC1 USB MUX1 MUX2 MUX3 Charge 4 Last
V.250 - + + + + + + - + -
Parameter Description
<value>
[0] Number of profile
(num)
Notes
• The user defined profile will be restored automatically after power-up. 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.
• AT&W stores all global settings and the current local settings of the interface, on which the command is exe­cuted.
• A list of parameters stored to the user profile can be found in Section 23.5, AT Command Settings stor-
able with AT&W.
AC75_ATC_V01.002 Page 36 of 569 10/30/06 Confidential / Released
Page 37
AC75 AT Command Set
2.4 ATQ
s

2.4 ATQ Set result code presentation mode

This parameter setting determines whether or not the TA transmits any result code to the TE. Information text transmitted in response is not affected by this setting.
Syntax
Exec Command
ATQ[<n>]
Response(s)
If <n>=0:
OK
If <n>=1: (none)
Reference(s) PIN ASC0 ASC1 USB MUX1 MUX2 MUX3 Charge 4 Last
V.250 - + + + + + + - + -
Parameter Description
(num)(&W)(&V)
<n>
(&F)
[0] 1 Result codes are suppressed and not transmitted
DCE transmits result code
Note
• If Java is running, the firmware will ignore the command. Responses will be invalid or result in "ERROR". See also "AC75 Java User's Guide" [3], Section "Configuring serial interface".
AC75_ATC_V01.002 Page 37 of 569 10/30/06 Confidential / Released
Page 38
AC75 AT Command Set
2.5 ATV
s

2.5 ATV Set result code format mode

This command determines the contents of header and trailer transmitted with AT command result codes and information responses. Possible responses are described in Section 2.5.1, Verbose and numeric result codes.
Syntax
Exec Command
ATV[<value>]
Response(s)
OK ERROR
Reference(s) PIN ASC0 ASC1 USB MUX1 MUX2 MUX3 Charge 4 Last
V.250 - + + + + + + - + -
Parameter Description
<value>
[0] Information response: <text><CR><LF>
(&F)
1
(num)(&W)(&V)
Short result code format: <numeric code><CR> Information response: <CR><LF><text><CR><LF>
Long result code format: <CR><LF><verbose code><CR>

2.5.1 Verbose and numeric result codes

Verbose format Numeric format Meaning OK 0 Command executed, no errors CONNECT 1 Link established RING 2 Ring detected NO CARRIER 3 Link not established or disconnected ERROR 4 Invalid command or command line too long NO DIALTONE 6 No dial tone, dialling impossible, wrong mode BUSY 7 Remote station busy CONNECT 2400/RLP 47 Link with 2400 bps and Radio Link Protocol CONNECT 4800/RLP 48 Link with 4800 bps and Radio Link Protocol CONNECT 9600/RLP 49 Link with 9600 bps and Radio Link Protocol CONNECT 14400/RLP 50 Link with 14400 bps and Radio Link Protocol ALERTING Alerting at called phone DIALING Mobile phone is dialing
AC75_ATC_V01.002 Page 38 of 569 10/30/06 Confidential / Released
Page 39
AC75 AT Command Set
2.6 ATX
s

2.6 ATX Set CONNECT result code format and call monitoring

ATX determines whether or not the TA detects the presence of dial tone and busy signal and whether or not TA
transmits particular result codes.
Syntax
Exec Command
ATX[<value>]
Response(s)
OK ERROR
Reference(s) PIN ASC0 ASC1 USB MUX1 MUX2 MUX3 Charge 4 Last
V.250 - + + + + + + - + -
Parameter Description
<value>
[0] CONNECT result code only returned, dial tone and busy detection are both dis-
1 CONNECT <text> result code only returned, dial tone and busy detection are
2 CONNECT <text> result code returned, dial tone detection is enabled, busy
3 CONNECT <text> result code returned, dial tone detection is disabled, busy
(&F)
4
(num)(&W)(&V)
abled.
both disabled.
detection is disabled.
detection is enabled. CONNECT <text> result code returned, dial tone and busy detection are both
enabled.
AC75_ATC_V01.002 Page 39 of 569 10/30/06 Confidential / Released
Page 40
AC75 AT Command Set
2.7 AT\V
s

2.7 AT\V Set CONNECT result code format

Syntax
Exec Command
AT\V[<value>]
Response(s)
OK ERROR
Reference(s) PIN ASC0 ASC1 USB MUX1 MUX2 MUX3 Charge 4 Last
V.250 - + - + + - - - + -
Parameter Description
<value>
[0] CONNECT <text> result code returned without RLP trailer
(&F)
1
(num)(&W)(&V)
CONNECT <text> result code returned with RLP trailer
Notes
• For circuit switched data calls only.
• Output only if ATX parameter is set with value > 0.
AC75_ATC_V01.002 Page 40 of 569 10/30/06 Confidential / Released
Page 41
AC75 AT Command Set
2.8 ATZ
s

2.8 ATZ Set all current parameters to user defined profile

ATZ sets all current parameters to the user profile stored with AT&W. If a connection is in progress, it will be ter-
minated. All defined GPRS contexts which are not activated or not online will be undefined if the non volatile storage of CGDCONT settings is not activated by the AT^SCFG parameter "GPRS/PersistentContexts" (see AT+CGDCONT). The user defined profile is stored to the non-volatile memory.
Syntax
Exec Command
ATZ[<value>]
Response(s)
OK
Reference(s) PIN ASC0 ASC1 USB MUX1 MUX2 MUX3 Charge 4 Last
V.250 - + + + + + + - + -
Parameter Description
<value>
[0] Reset to user profile
(num)
Notes
• First the profile will be set to factory default (see AT&F). If there is a valid user profile (stored with AT&W), this profile will be loaded afterwards.
• Any additional commands on the same command line may be ignored. A delay of 300 ms is required before next command is sent, otherwise "OK" response may be corrupted.
AC75_ATC_V01.002 Page 41 of 569 10/30/06 Confidential / Released
Page 42
AC75 AT Command Set
2.9 AT+CFUN
s

2.9 AT+CFUN Set phone functionality

The AT+CFUN command serves to control the functionality level of the ME. It 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 of the ME to a minimum and thus minimizes the current consumption. Further information, particularly power supply ratings during the various operating modes and the timing of hardware signals in SLEEP mode can be found in the "AC75 Hardware Interface
Description, Version 01.002".
SLEEP mode falls in two categories:
• NON-CYCLIC SLEEP mode <fun>=0
• and CYCLIC SLEEP modes, selectable as <fun>= 7 or 9.
NON-CYCLIC SLEEP mode permanently blocks the serial interface. The benefit of the CYCLIC SLEEP mode is that the serial interface remains accessible and that, in intermittent wake-up periods, characters can be sent or received without terminating the selected mode. This allows the ME to wake up for the duration of an event and, afterwards, to resume power saving. Please refer to Section 2.9.1, Wake up the ME from SLEEP mode for a summary of all SLEEP modes and the different ways of waking up the module. For CYCLIC SLEEP mode both the ME and the application must be configured to use hardware flow control. This is necessary since the CTS signal is set/reset every 0.9-2.7 seconds in order to indicate to the application when the UART is active. The default setting of hardware flow control is AT\Q0 which must be altered to AT\Q3. For use after restart you are advised to add it to the user profile saved with AT&W. If both interfaces ASC0 and ASC1 are connected, hardware flow control must be set in either application. See notes below for further detail. SLEEP mode management if Java is started: The Java Virtual Machine remains active, but also enters the SLEEP mode. AT commands can be sent from the Java application to the serial interface, no matter which SLEEP mode was selected. This allows you to control the ME even if it is in NON-CYCLIC SLEEP mode.
The AT+CFUN test command returns the values of the supported parameters. The AT+CFUN read command returns the current functionality value. The AT+CFUN write command can be used to reset the ME, to choose one of the SLEEP modes or to return to full functionality.
Syntax
Test Command
AT+CFUN=?
Response(s)
+CFUN: (list of supported <fun>s) , (list of supported <rst>s) OK
Read Command
AT+CFUN?
Response(s)
+CFUN: <fun> OK
Write Command
AT+CFUN=[<fun>[, <rst>]]
Response(s)
OK ERROR +CME ERROR
Reference(s) PIN ASC0 ASC1 USB MUX1 MUX2 MUX3 Charge 4 Last
GSM 07.07 - + + + ± ± ± - + -
AC75_ATC_V01.002 Page 42 of 569 10/30/06 Confidential / Released
Page 43
AC75 AT Command Set
2.9 AT+CFUN
Unsolicited Result Codes
URC 1
^SYSSTART
Indicates that the ME has been started and is ready to operate. If autobauding is active (AT+IPR=0) the URC is not generated.
If the ME is configured to enter the Airplane mode after restart or reset the following URC is received on boot­up: "^SYSSTART AIRPLANE MODE". In this mode, only the AT commands listed in Section 23.4, Avail-
ability of AT Commands Depending on Operating Mode of ME can be used. For details please
refer to the AT^SCFG command, parameter <mapos>.
URC 2
^SYSSTART CHARGE ONLY MODE
Indicates that the ME has entered the CHARGE ONLY mode. This occurs if the charger is connected while the ME is in POWER DOWN mode. If autobauding is active (AT+IPR=0) the URC is not generated. In CHARGE ONLY mode the ME is neither registered to the GSM network nor are the serial interfaces fully accessible. Only the AT commands listed in Section 23.4, Availability of AT Commands Depending
on Operating Mode of ME can be used. For further details on charging refer to the Hardware Interface
Description [2].
s
Parameter Description
(&F)(P)
(num)
In this mode, the AT interface is not accessible. Consequently, after setting
<fun>=0, do not send further characters. Otherwise these characters remain
in the input buffer and may delay the output of an unsolicited result code. Due to the fact that the serial interface is disabled, this mode cannot be used if a Remote SIM Access (RSA) connection is ongoing (reason: during RSA connections the SIM communication is routed via a serial channel). The first wake-up event stops power saving and takes the ME back to full func­tionality level <fun>=1.
Full functionality (no power saving). 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. If the ME is NON-CYCLIC SLEEP mode, <fun>=1 can also be sent by the Java application. 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 while CTS is active. If char­acters are recognized on the serial interface, the ME stays active for 2 seconds after the last character was sent or received. The ME exits SLEEP mode only, if AT+CFUN=1 is entered.
In this mode, the serial interface is shortly enabled while CTS is active. If char­acters are recognized on the serial interface, the ME stays active after the last character was sent or received for at least the time, which can be configured by AT^SCFG="PowerSaver/Mode9/Timeout",<psm9to> (temporary wakeup). In contrast to SLEEP mode 7 assertion of RTS can also be used to temporarily wake up the ME. In this case too, activity time is at least the time set with
AT^SCFG="PowerSaver/Mode9/Timeout",<psm9to>. RTS can be activated
either from ASC0 or ASC1. The ME exits SLEEP mode only, if AT+CFUN=1 is entered.
<fun>
0 NON-CYCLIC SLEEP mode:
[1]
7 CYCLIC SLEEP mode:
9 CYCLIC SLEEP mode:
AC75_ATC_V01.002 Page 43 of 569 10/30/06 Confidential / Released
Page 44
AC75 AT Command Set
2.9 AT+CFUN
s
<rst>
The parameter can only be used if the serial interface is enabled. Due to the command syntax, you need to enter parameter <fun>, followed by <rst>, where <fun> is only a placeholder and has no effect. See examples below.
[0] Placeholder for <fun> as stated above. 1 ME resets and restarts to full functionality. After reset and restart, PIN 1
(num)
authentication is necessary (AT+CPIN). If autobauding is enabled, it is recom­mended to wait 3 to 5 seconds before entering the first AT command. For details on autobauding refer to Section 4.9.1, Autobauding.
Notes
• The settings made with AT+CFUN apply to both serial interfaces ASC0 and ASC1.
• CYCLIC SLEEP mode cannot be activated or resumed as long as data are buffered in one of the output buff­ers of the ME (ASC0 or ASC1). This should be taken into account, because RTS may be unintentionally asserted if, for example, one of the following scenarios occurs: a) Hardware flow control is set in the ME (AT\Q3), but not in the host application (RTS/CTS handshake). b) The two serial interfaces ASC0 and ASC1 are connected, but one of them is released, e.g. after closing or deactivating the application connected to this interface. In cases a) and b) data sent by the ME, such as URCs or outstanding AT command responses, will be buff­ered in the output buffer of this interface, signalized by the active RTS line until the buffer is emptied. Therefore, for CYCLIC SLEEP mode to work properly take care that the following requirements be met: Be sure that data sent by the ME are collected on both interfaces. Activate hardware flow control on ME (TA) and application side (TE). Avoid releasing one of the interfaces if any URCs are likely to occur on this interface.
• In Multiplex mode, the CFUN profile is shared by all multiplexer channels.
• If the ME is in Multiplexer mode, it is not recommended to activate SLEEP mode with AT+CFUN=<fun>. The best approach to properly control SLEEP mode in this case is to issue the PSC messages described in [6], Section "Power saving control".
• If the host application uses the USB interface, power saving must be configured both on the AC75 module and on the USB host, i.e. the USB host must be set to Suspend mode (usually Selective or Global Suspend). Otherwise, if you change only the AT+CFUN parameters, the selected <fun> level will be accepted but the active USB keeps the module alive and thus prevents power saving until the USB plug is disconnected. Vice versa, if the module is in SLEEP mode restarting the USB will cause the module to stop power saving although the selected CFUN level does not change.
• When a circuit-switched call is in progress, <fun>=7 or 9 can be activated without terminating the call. How­ever, setting <fun>=0 during a circuit-switched call immediately disconnects this call.
• To check whether power saving is on, you can query the status with the read command AT+CFUN? only if the module is in full functionality mode or in CYCLIC SLEEP mode. If available, you can also take advantage of the status LED controlled by the SYNC pin (see AT^SSYNC and [2]). With AT^SSYNC you can select differ­ent modes of LED signalization during SLEEP modes (see Section 19.7.1, ME status indicated by status LED
patterns for details). However, the module can wake up temporarily from power saving without leaving its
CYCLIC SLEEP mode (without changing +CFUN "<fun>"), e.g. for a network scan after a loss of radio cov­erage, or after receipt of serial data during CYCLIC SLEEP mode. During this "temporary wakeup state" the LED will operate as if the ME was in full functionality mode.
• 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 interface is not accessible.

2.9.1 Wake up the ME from SLEEP mode

A wake-up event is any event that causes the ME to draw more current. Depending on the selected mode, the wake-up event either switches the SLEEP mode off and takes the ME back to full functionality AT+CFUN=1, or activates the ME temporarily without terminating the selected SLEEP mode.
Definitions of the state transitions described in Table 2.3:
AC75_ATC_V01.002 Page 44 of 569 10/30/06 Confidential / Released
Page 45
AC75 AT Command Set
2.9 AT+CFUN
• Quit: ME exits SLEEP mode.
• Temporary: ME becomes active temporarily for the duration of the event and the mode-specific follow-up time after the last character was sent or received on the serial interface.
• No effect: Event is not relevant in the selected SLEEP mode. The ME does not wake up.
Table 2.3: Wake-up events in NON-CYCLIC and CYCLIC SLEEP modes
s
Event Selected mode:
<fun>=0
Ignition line No effect No effect /RTS0 or /RTS1 activation Quit Mode 7: No effect (RTS is only
Unsolicited Result Code (URC) Quit Temporary Incoming voice or data call Quit Temporary Any AT command (incl. outgoing
SMS, voice or data call)
Incoming SMS (AT+CNMI is set to 0,0 (this is the default setting)
Incoming SMS (AT+CNMI is set to 1,1)
GPRS data transfer From Java: Yes
RTC alarm line Quit Temporary
AT+CFUN=1 From Java: Yes
Java terminates Quit Temporary
From Java: Yes Without Java: Not possible (UART disabled)
No effect No effect
Quit Temporary
Without Java: Not possible (UART disabled)
Without Java: Not possible (UART disabled)
Selected mode:
<fun>=7 or 9
used for flow control) Mode 9: Temporary
Temporary
Temporary
Quit
AC75_ATC_V01.002 Page 45 of 569 10/30/06 Confidential / Released
Page 46
AC75 AT Command Set
2.10 AT^SMSO
s

2.10 AT^SMSO Switch off mobile station

AT^SMSO initiates the power-off procedure. High level of the module's PWR_IND pin and the URC "^SHUTDOWN"
notify that the procedure has completed and the module has entered the POWER DOWN mode. Therefore, be sure not to disconnect the operating voltage until PWR_IND is high or until the URC "^SHUTDOWN" is displayed. Otherwise, you run the risk of losing data. For further details on how to turn off the module see the [2].
Syntax
Test Command
AT^SMSO=?
Response(s)
OK
Exec Command
AT^SMSO
Response(s)
^SMSO: MS OFF OK ERROR
Reference(s) PIN ASC0 ASC1 USB MUX1 MUX2 MUX3 Charge 4 Last
SIEMENS - + + + + + + - + +
Unsolicited Result Code
^SHUTDOWN
Indicates that the power-off procedure is finished and the module will be switched off in less than 1 second.
Notes
• Do not send any other AT command after AT^SMSO.
• If AT^SMSO is entered on one of the Multiplexer channels the ME closes the Multiplexer channels, terminates the Multiplexer and deactivates all other functions. Then, the URC "^SHUTDOWN" will be issued on the phys- ical serial interface (ASC0). The URC will be transmitted at the bit rate last activated on ASC0 for use with the Multiplex driver.
• If both interfaces ASC0 and ASC1 are connected the URC appears on both of them.
• If the module is in NORMAL mode and the charger is connected to the VCHARGE line, the AT^SMSO com­mand causes the module to shut down shortly and then start into the CHARGE ONLY mode. If the module is in CHARGE ONLY mode the AT^SMSO command is not supported at all. In both cases, the module can only be switched off by disconnecting the charger. See also [2].
AC75_ATC_V01.002 Page 46 of 569 10/30/06 Confidential / Released
Page 47
AC75 AT Command Set
2.11 AT+GCAP
s

2.11 AT+GCAP Request complete TA capabilities list

AT+GCAP returns a list of additional capabilities.
Syntax
Test Command
AT+GCAP=?
Response(s)
OK
Exec Command
AT+GCAP
Response(s)
+GCAP: <name> OK
Reference(s) PIN ASC0 ASC1 USB MUX1 MUX2 MUX3 Charge 4 Last
V.250 - + + + + + + - + -
Parameter Description
<name>
e.g.: +CGSM,+FCLASS
(str)
Note
• +CGSM: The response text shows which GSM commands of the ETSI standard are supported.
AC75_ATC_V01.002 Page 47 of 569 10/30/06 Confidential / Released
Page 48
AC75 AT Command Set
2.12 AT+CMEE
s

2.12 AT+CMEE Mobile Equipment Error Message Format

AT+CMEE controls the format of the error result codes that indicates errors related to AC75 functionality. Format
can be selected between plain "ERROR" output, error numbers or verbose "+CME ERROR: <err>" and "+CMS ERROR: <err>" messages. Possible error result codes are listed in Table 2.4, General "CME ERROR" Codes (GSM 07.07)Table 2.5, Gen-
eral "CME ERROR" Codes (SIEMENS)Table 2.6, GPRS related "CME ERROR" Codes (GSM 07.07) and Table
2.8, SMS related "CMS ERROR" Codes (GSM 07.05).
In multiplex mode (refer AT+CMUX) the setting applies only to the logical channel where selected. The setting on the other channels may differ.
Syntax
Test Command
AT+CMEE=?
Response(s)
+CMEE: (list of supported<errMode>s) OK
Read Command
AT+CMEE?
Response(s)
+CMEE: <errMode> OK
Write Command
AT+CMEE=<errMode>
Response(s)
OK ERROR +CME ERROR: <err>
Reference(s) PIN ASC0 ASC1 USB MUX1 MUX2 MUX3 Charge 4 Last
GSM 07.07 - + + + + + + - + -
Parameter Description
<errMode>
(&F)(D)
0 1 Enable error result code with numeric values. 2 Enable error result code with verbose (string) values.
(num)(&W)(&V)
Disable result code, i.e. only "ERROR" will be displayed.
Example
To obtain enhanced error messages it is recommended to choose <errMode>=2.
AT+CMEE=2 OK
AC75_ATC_V01.002 Page 48 of 569 10/30/06 Confidential / Released
Page 49
AC75 AT Command Set
2.12 AT+CMEE

2.12.1 CME/CMS Error Code Overview

Table 2.4: General "CME ERROR" Codes (GSM 07.07)
<err> Code Text (if AT+CMEE=2) 0 phone failure 1 no connection to phone 2 phone-adapter link reserved 3 Operation not allowed 4 Operation not supported 5 PH-SIM PIN required 6 PH-FSIM PIN required 7 PH-FSIM PUK required 10 SIM not inserted 11 SIM PIN required 12 SIM PUK required 13 SIM failure 14 SIM busy 15 SIM wrong 16 Incorrect password 17 SIM PIN2 required 18 SIM PUK2 required 20 Memory full 21 invalid index 22 not found 23 Memory failure 24 text string too long 25 invalid characters in text string 26 dial string too long 27 invalid characters in dial string 30 no network service 31 Network timeout 32 Network not allowed emergency calls only 40 Network personalization PIN required 41 Network personalization PUK required 42 Network subset personalization PIN required 43 Network subset personalization PUK required 44 service provider personalization PIN required 45 service provider personalization PUK required 46 Corporate pe sonalization PIN required 47 Corporate personalization PUK required 48 Master Phone Code required 100 unknown 132 service option not supported
s
AC75_ATC_V01.002 Page 49 of 569 10/30/06 Confidential / Released
Page 50
AC75 AT Command Set
2.12 AT+CMEE
<err> Code Text (if AT+CMEE=2) 133 requested service option not subscribed 134 service option temporarily out of order 256 Operation temporary not allowed 257 call barred 258 phone busy 259 user abort 260 invalid dial string 261 ss not executed 262 SIM blocked 263 Invalid Block
Table 2.5: General "CME ERROR" Codes (SIEMENS)
<err> Code Text (if AT+CMEE=2) 615 network failure 616 network is down 639 service type not yet available 640 operation of service temporary not allowed 764 missing input value 765 invalid input value 767 operation failed 769 unable to get control of required module 770 SIM invalid - network reject 771 call setup in progress 772 SIM powered down
s
Table 2.6: GPRS related "CME ERROR" Codes (GSM 07.07)
<err> Code Text (if AT+CMEE=2) 103 Illegal MS 106 Illegal ME 107 GPRS services not allowed 111 PLMN not allowed 112 Location area not allowed 113 Roaming not allowed in this location area 148 unspecified GPRS error 149 PDP authentication failure 150 invalid mobile class
Table 2.7: GPRS related "CME ERROR" Codes (SIEMENS)
<err> Code Text (if AT+CMEE=2) 578 GPRS - unspecified activation rejection 588 GPRS - feature not supported 594 GPRS - invalid address length 595 GPRS - invalid character in address string
AC75_ATC_V01.002 Page 50 of 569 10/30/06 Confidential / Released
Page 51
AC75 AT Command Set
2.12 AT+CMEE
<err> Code Text (if AT+CMEE=2) 596 GPRS - invalid cid value 607 GPRS - missing or unknown APN 625 GPRS - pdp type not supported 630 GPRS - profile (cid) not defined 632 GPRS - QOS not accepted 633 GPRS - QOS validation fail 643 GPRS - unknown PDP address or type 644 GPRS - unknown PDP context 646 GPRS - QOS invalid parameter
Table 2.8: SMS related "CMS ERROR" Codes (GSM 07.05)
<err> Code Text (if AT+CMEE=2) 1 Unassigned (unallocated) number 8 Operator determined barring 10 Call barred 21 Short message transfer rejected 27 Destination out of service 28 Unidentified subscriber 29 Facility rejected 30 Unknown subscriber 38 Network out of order 41 Temporary failure 42 Congestion 47 Resources unavailable, unspecified 50 Requested facility not subscribed 69 Requested facility not implemented 81 Invalid short message transfer reference value 95 Invalid message, unspecified 96 Invalid mandatory information 97 Message type non-existent or not implemented 98 Message not compatible with short message protocol state 99 Information element non-existent or not implemented 111 Protocol error, unspecified 127 Interworking, unspecified 128 Telematic interworking not supported 129 Short message Type 0 not supported 130 Cannot replace short message 143 Unspecified TP-PID error 144 Data coding scheme (alphabet) not supported 145 Message class not supported 159 Unspecified TP-DCS error 160 Command cannot be actioned
s
AC75_ATC_V01.002 Page 51 of 569 10/30/06 Confidential / Released
Page 52
AC75 AT Command Set
2.12 AT+CMEE
<err> Code Text (if AT+CMEE=2) 161 Command unsupported 175 Unspecified TP-Command error 176 TPDU not supported 192 SC busy 193 No SC subscription 194 SC system failure 195 Invalid SME address 196 Destination SME barred 197 SM Rejected-Duplicate SM 198 TP-VPF not supported 199 TP-VP not supported 208 D0 SIM SMS storage full 209 No SMS storage capability in SIM 210 Error in MS 211 Memory Capacity Exceeded 212 SIM Application Toolkit Busy 213 SIM data download error 255 Unspecified error cause 300 ME failure 301 SMS service of ME reserved 302 Operation not allowed 303 Operation not supported 304 Invalid PDU mode parameter 305 Invalid text mode parameter 310 SIM not inserted 311 SIM PIN required 312 PH-SIM PIN required 313 SIM failure 314 SIM busy 315 SIM wrong 316 SIM PUK required 317 SIM PIN2 required 318 SIM PUK2 required 320 Memory failure 321 Invalid memory index 322 Memory full 330 SMSC address unknown 331 no network service 332 Network timeout 340 NO +CNMA ACK EXPECTED 500 Unknown error 512 User abort
s
AC75_ATC_V01.002 Page 52 of 569 10/30/06 Confidential / Released
Page 53
AC75 AT Command Set
2.12 AT+CMEE
<err> Code Text (if AT+CMEE=2) 513 unable to store 514 invalid status 515 invalid character in address string 516 invalid length 517 invalid character in pdu 519 invalid length or character 520 invalid character in text 521 timer expired 522 Operation temporary not allowed 532 SIM not ready 534 Cell Broadcast error unknown 535 PS busy 538 invalid parameter 549 incorrect PDU length 550 invalid message type indication (MTI) 551 invalid (non-hex) chars in address 553 incorrect PDU length (UDL) 554 incorrect SCA length
s
AC75_ATC_V01.002 Page 53 of 569 10/30/06 Confidential / Released
Page 54
AC75 AT Command Set
2.13 AT+CSCS
s

2.13 AT+CSCS Select TE character set

The AT+CSCS write command informs the TA which character set <chset> is used by the TE. This enables the TA to convert character strings correctly between TE and ME character sets. See also Section 1.5, Supported
character sets.
Note that when the TA-TE interface is set to 8-bit operation and the used TE alphabet is 7-bit, the highest bit will be set to zero.
Syntax
Test Command
AT+CSCS=?
Response(s)
+CSCS: (list of supported<chset>s) OK
Read Command
AT+CSCS?
Response(s)
+CSCS: <chset> OK
Write Command
AT+CSCS=[<chset>]
Response(s)
OK
Reference(s) PIN ASC0 ASC1 USB MUX1 MUX2 MUX3 Charge 4 Last
GSM 07.07, GSM 11.11 - + + + + + + - + -
Parameter Description
<chset>
“GSM“
“UCS2“ 16-bit universal multiple-octet coded character set (ISO/IEC10646 [32]); UCS2
(str)
(&F)(P)
GSM default alphabet (GSM 03.38 subclause 6.2.1); Note: This setting may cause software flow control problems since the codes used to stop and resume data flow (XOFF = decimal 19, XON = decimal 17) are interpreted as normal characters.
character strings are converted to hexadecimal numbers from 0000 to FFFF; e.g. "004100620063" equals three 16-bit characters with decimal values 65, 98 and 99.
AC75_ATC_V01.002 Page 54 of 569 10/30/06 Confidential / Released
Page 55
AC75 AT Command Set
2.14 AT^SCFG
s

2.14 AT^SCFG Extended Configuration Settings

AT^SCFG can be used to query and configure various settings of the AC75.
The AT^SCFG read command returns a list of all supported parameters and their current values. The AT^SCFG write command queries a configuration parameter (if no value is entered) or sets its value(s). Input of parameter names is always coded in GSM character set, parameter values are expected to be given as specified via AT+CSCS.
The following error messages may be returned by the AT^SCFG write commands:
• "+CME ERROR: operation temporary not allowed" Change of parameter value(s) temporarily not allowed.
• "+CME ERROR: invalid index" Invalid parameter name or value(s).
• "+CME ERROR: invalid characters in text string" Character set conversion of parameter value(s) failed.
• "+CME ERROR: incorrect password" A given password was not correct.
• "+CME ERROR: memory failure" Could not allocate necessary memory or storing a parameter failed.
• "+CME ERROR: operation not allowed" Change of parameter value(s) not allowed
• "+CME ERROR: unknown" Other error
Syntax
Test Command
AT^SCFG=?
Response(s)
^SCFG: "AutoExec" , (list of supported <AutoExecCmd>), (list of supported <AutoExecType>), (list of supported <AutoExecIndex>), (list of supported <AutoExecMode>), (max. string length of
<AutoExecATC>), (time range of <AutoExecPeriod>)
^SCFG: "GPRS/ATS0/withAttach", (list of supported <gs0aa>s) ^SCFG: "GPRS/AutoAttach", (list of supported <gaa>s) ^SCFG: "GPRS/PersistentContexts", (list of supported <gpc>s) ^SCFG: "GPRS/RingOnIncomingData", (list of supported <groid>s) ^SCFG: "MEopMode/Airplane", (list of supported <map>s) ^SCFG: "MEopMode/Airplane/OnStart", (list of supported <mapos>s) ^SCFG: "MEShutdown/OnIgnition", (list of supported <msi>s) ^SCFG: "PowerSaver/Mode9/Timeout", (list of supported <psm9to>s) ^SCFG: "Radio/Band", (list of supported <rbp>s), (list of supported <rba>s) ^SCFG: "Radio/OutputPowerReduction", (list of supported <ropr>s) ^SCFG: "Serial/USB/DDD" , (list of supported <deviceDescr>s) , (list of supported <descrIndex>s) ,
(max. string length of <langId>) , (max. string length of <vendorId>) , (max. string length of
<productId>) , (max. string length of <manufacturer>) , (max. string length of <product>) , (max. string
length of <serialNo>)
^SCFG: "Tcp/BufSize", (list of supported <tcpBufSize>) ^SCFG: "Tcp/IRT", (list of supported <tcpIrt>) ^SCFG: "Tcp/MR", (list of supported <tcpMr>) ^SCFG: "Tcp/OT", (list of supported <tcpOt>) ^SCFG: "Tcp/SAck", (list of supported <tcpSack>) ^SCFG: "Tcp/TTcp", (list of supported <tcpTtcp>) ^SCFG: "Tcp/WithURCs", (list of supported <tcpWithUrc>) ^SCFG: "Trace/Syslog/OTAP", (list of supported <OtapTracer>) ^SCFG: "URC/CallStatus/CIEV", (list of supported <succ>s) ^SCFG: "URC/CallStatus/SLCC", (list of supported <sucs>s)
AC75_ATC_V01.002 Page 55 of 569 10/30/06 Confidential / Released
Page 56
AC75 AT Command Set
2.14 AT^SCFG
Test Command (Continued)
AT^SCFG=?
Response(s)
^SCFG: "URC/Datamode/Ringline", (list of supported <udri>s) ^SCFG: "URC/Ringline", (list of supported <uri>s) ^SCFG: "URC/Ringline/ActiveTime", (list of supported <urat>s) ^SCFG: "Userware/Autostart", (list of supported <ua>s) ^SCFG: "Userware/Autostart/AppName", (max. string lengths of <uaa>) ^SCFG: "Userware/Autostart/Delay", (list of supported <uad>s) ^SCFG: "Userware/Passwd", (max. string length of <upwd>) ^SCFG: "Userware/DebugInterface", (<udbgif1>), (<udbgif2>), (<udbgif3>) ^SCFG: "Userware/Mode", (list of supported <umode>), (length of <uurl>), (range of supported
<uport>values)
^SCFG: "Userware/Stdout", (list of supported <if>), (list of supported <intvalue>), (<filename>), (list of
supported <logmode>)
OK
Read Command
AT^SCFG?
Response(s)
^SCFG: "AutoExec" , <AutoExecCmd>, <AutoExecType>, <AutoExecIndex>, <AutoExecMode>,
<AutoExecATC>[, <AutoExecPeriod>, <AutoExecPeriodTimeLeft>]
^SCFG: "GPRS/ATS0/withAttach", <gs0aa> ^SCFG: "GPRS/AutoAttach", <gaa> ^SCFG: "GPRS/PersistentContexts", <gpc> ^SCFG: "GPRS/RingOnIncomingData", <groid> ^SCFG: "MEopMode/Airplane", <map> ^SCFG: "MEopMode/Airplane/OnStart", <mapos> ^SCFG: "MEShutdown/OnIgnition", <msi> ^SCFG: "PowerSaver/Mode9/Timeout", <psm9to> ^SCFG: "Radio/Band", <rbc>, <rba> ^SCFG: "Radio/OutputPowerReduction", <ropr> ^SCFG: "Serial/USB/DDD" , <deviceDescr>, <descrIndex>, <langId>, <vendorId>, <productId>,
<manufacturer>, <product>, <serialNo>
^SCFG: "Tcp/BufSize", <tcpBufSize> ^SCFG: "Tcp/IRT", <tcpIrt> ^SCFG: "Tcp/MR", <tcpMr> ^SCFG: "Tcp/OT", <tcpOt> ^SCFG: "Tcp/SAck", <tcpSack> ^SCFG: "Tcp/TTcp", <tcpTtcp> ^SCFG: "Tcp/WithURCs", <tcpWithUrc> ^SCFG: "Trace/Syslog/OTAP", <OtapTracer> ^SCFG: "URC/CallStatus/CIEV", <succ> ^SCFG: "URC/CallStatus/SLCC", <sucs> ^SCFG: "URC/Datamode/Ringline", <udri> ^SCFG: "URC/Ringline", <uri> ^SCFG: "URC/Ringline/ActiveTime", <urat> ^SCFG: "Userware/Autostart", <ua> ^SCFG: "Userware/Autostart/AppName", <uaa> ^SCFG: "Userware/Autostart/Delay", <uad> ^SCFG: "Userware/Passwd" ^SCFG: "Userware/DebugInterface", <udbgif1>, <udbgif2>, <udbgif3> ^SCFG: "Userware/Mode" ^SCFG: "Userware/Stdout", <if>[, <intvalue>[, <filename>[, <logmode>]]] OK
s
AC75_ATC_V01.002 Page 56 of 569 10/30/06 Confidential / Released
Page 57
AC75 AT Command Set
2.14 AT^SCFG
Write Command
Automatic AT command execution
AT^SCFG="AutoExec" , <AutoExecCmd>, <AutoExecType>, <AutoExecIndex>[, <AutoExecMode>,
<AutoExecATC>[, <AutoExecPeriod>]]
Response(s)
^SCFG: "AutoExec" , <AutoExecCmd>, <AutoExecType>, <AutoExecIndex>, <AutoExecMode>,
<AutoExecATC>[, <AutoExecPeriod>, <AutoExecPeriodTimeLeft>]
OK ERROR +CME ERROR
Write Command
GPRS ATS0 with automatic attach AT^SCFG="GPRS/ATS0/withAttach"[, <gs0aa>]
Response(s)
^SCFG: "GPRS/ATS0/withAttach", <gs0aa> OK ERROR +CME ERROR
Write Command
Automatic GPRS attach AT^SCFG="GPRS/AutoAttach"[, <gaa>]
Response(s)
^SCFG: "GPRS/AutoAttach", <gaa> OK ERROR +CME ERROR
Write Command
Persistent GPRS contexts AT^SCFG="GPRS/PersistentContexts"[, <gpc>]
Response(s)
^SCFG: "GPRS/PersistentContexts", <gpc> OK ERROR +CME ERROR
Write Command
Ring on incoming GPRS IP data packets AT^SCFG="GPRS/RingOnIncomingData"[, <groid>]
Response(s)
^SCFG: "GPRS/RingOnIncomingData", <groid> OK ERROR +CME ERROR
s
Write Command
Enable/disable Airplane mode during operation AT^SCFG="MEopMode/Airplane"[, <map>]
Response(s)
^SCFG: "MEopMode/Airplane", <map> OK
AC75_ATC_V01.002 Page 57 of 569 10/30/06 Confidential / Released
Page 58
AC75 AT Command Set
2.14 AT^SCFG
Write Command (Continued)
Enable/disable Airplane mode during operation AT^SCFG="MEopMode/Airplane"[, <map>]
Response(s)
ERROR +CME ERROR
Write Command
Airplane mode upon ME restart AT^SCFG="MEopMode/Airplane/OnStart"[, <mapos>]
Response(s)
^SCFG: "MEopMode/Airplane/OnStart", <mapos> OK ERROR +CME ERROR
Write Command
Enable/disable shutdown by ignition line AT^SCFG="MEShutdown/OnIgnition"[, <msi>]
Response(s)
^SCFG: "MEShutdown/OnIgnition", <msi> OK ERROR +CME ERROR
s
Write Command
Query/Set timeout value for power saving mode 9 AT^SCFG="PowerSaver/Mode9/Timeout"[, <psm9to>]
Response(s)
^SCFG: "PowerSaver/Mode9/Timeout", <psm9to> OK ERROR +CME ERROR
Write Command
Radio output power reduction AT^SCFG="Radio/OutputPowerReduction"[, <ropr>]
Response(s)
^SCFG: "Radio/OutputPowerReduction", <ropr> OK ERROR +CME ERROR
Write Command
Radio band selection AT^SCFG="Radio/Band"[, <rbp>][, <rba>]
Response(s)
^SCFG: "Radio/Band", <rbp>, <rba> OK ERROR +CME ERROR
AC75_ATC_V01.002 Page 58 of 569 10/30/06 Confidential / Released
Page 59
AC75 AT Command Set
2.14 AT^SCFG
Write Command
Configuration of TCP parameter 'BufSize': AT^SCFG="Tcp/BufSize"[, <tcpBufSize>]
Response(s)
^SCFG: "Tcp/BufSize", <tcpBufSize> OK ERROR +CME ERROR
Write Command
Configuration of TCP parameter 'InitialRetransmissionTimeout': AT^SCFG="Tcp/IRT"[, <tcpIrt>]
Response(s)
^SCFG: "Tcp/IRT", <tcpIrt> OK ERROR +CME ERROR
s
Write Command
Configuration of TCP parameter 'MaxRetransmissions': AT^SCFG="Tcp/MR"[, <tcpMr>]
Response(s)
^SCFG: "Tcp/MR", <tcpMr> OK ERROR +CME ERROR
Write Command
Configuration of TCP parameter 'OverallTimeout': AT^SCFG="Tcp/OT"[, <tcpOt>]
Response(s)
^SCFG: "Tcp/OT", <tcpOt> OK ERROR +CME ERROR
Write Command
Configuration of TCP parameter 'Selective Acknowledge': AT^SCFG="Tcp/SAck"[, <tcpSack>]
Response(s)
^SCFG: "Tcp/SAck", <tcpSack> OK ERROR +CME ERROR
Write Command
Configuration of Internet Service URCs: AT^SCFG="Tcp/WithURCs"[, <tcpWithUrc>]
Response(s)
^SCFG: "Tcp/WithURCs", <tcpWithUrc> OK ERROR +CME ERROR
AC75_ATC_V01.002 Page 59 of 569 10/30/06 Confidential / Released
Page 60
AC75 AT Command Set
2.14 AT^SCFG
Write Command
Tracing: AT^SCFG="Trace/Syslog/OTAP"[, <OtapTracer>]
Response(s)
^SCFG: "Trace/Syslog/OTAP", <OtapTracer> SYSLOG ENABLED ERROR +CME ERROR
Write Command
USB Device Descriptor:
AT^SCFG="Serial/USB/DDD" [, <deviceDescr>, [<descrIndex>], [<langId>], <vendorId>,
<productId>, [<manufacturer>], [<product>], [<serialNo>]]
Response(s)
^SCFG: "Serial/USB/DDD" , <deviceDescr>, <descrIndex>, <langId>, <vendorId>, <productId>,
<manufacturer>, <product>, <serialNo>
OK ERROR +CME ERROR
Write Command
Configuration of URC "+CIEV: call" Call Status Indication AT^SCFG="URC/CallStatus/CIEV"[, <succ>]
Response(s)
^SCFG: "URC/CallStatus/CIEV", <succ> OK ERROR +CME ERROR
Write Command
Configuration of URC "^SLCC" Call Status Indication AT^SCFG="URC/CallStatus/SLCC"[, <sucs>]
Response(s)
^SCFG: "URC/CallStatus/SLCC", <sucs> OK ERROR +CME ERROR
Write Command
URC indication in datamode via Ring line: AT^SCFG="URC/Datamode/Ringline"[, <udri>]
Response(s)
^SCFG: "URC/Datamode/Ringline", <udri> OK ERROR +CME ERROR
s
Write Command
URC indication via Ring line: AT^SCFG="URC/Ringline"[, <uri>]
Response(s)
^SCFG: "URC/Ringline", <uri> OK
AC75_ATC_V01.002 Page 60 of 569 10/30/06 Confidential / Released
Page 61
AC75 AT Command Set
2.14 AT^SCFG
Write Command (Continued)
URC indication via Ring line: AT^SCFG="URC/Ringline"[, <uri>]
Response(s)
ERROR +CME ERROR
Write Command
Duration of active RING line for URC indications: AT^SCFG="URC/Ringline/ActiveTime"[, <urat>]
Response(s)
^SCFG: "URC/Ringline/ActiveTime", <urat> OK ERROR +CME ERROR
Write Command
Userware autostart status: AT^SCFG="Userware/Autostart"[, <upwd>, <ua>]
Response(s)
^SCFG: "Userware/Autostart"[, <ua>] OK ERROR +CME ERROR
s
Write Command
Userware autostart application: AT^SCFG="Userware/Autostart/AppName"[, <upwd>, <uaa>]
Response(s)
^SCFG: "Userware/Autostart/AppName"[, <uaa>] OK ERROR +CME ERROR
Write Command
Userware autostart delay: AT^SCFG="Userware/Autostart/Delay"[, <upwd>, <uad>]
Response(s)
^SCFG: "Userware/Autostart/Delay"[, <uad>] OK ERROR +CME ERROR
Write Command
Userware configuration password: AT^SCFG="Userware/Passwd"[, <upwd>
Response(s)
, <upwd>
old
, <upwd>
new
^SCFG: "Userware/Passwd" OK ERROR +CME ERROR
new
]
AC75_ATC_V01.002 Page 61 of 569 10/30/06 Confidential / Released
Page 62
AC75 AT Command Set
2.14 AT^SCFG
Write Command
Userware debug interface: AT^SCFG="Userware/DebugInterface"[, <udbgif1>, <udbgif2>[, <udbgif3>]]
Response(s)
^SCFG: "Userware/DebugInterface", <udbgif1>, <udbgif2>, <udbgif3> OK ERROR +CME ERROR
Write Command
Userware mode: AT^SCFG="Userware/Mode"[, <umode>, <uurl>, <uport>]
Response(s)
^SCFG: "Userware/Mode", <umode>, <uurl>, <uport> OK ERROR +CME ERROR
s
Write Command
Standard output of userware AT^SCFG="Userware/Stdout"[, <if>[, <intvalue>][, <filename>][, <logmode>]]
Response(s)
^SCFG: "Stdout" , <if>[, <intvalue>[, <filename>[, <logmode>]]] OK ERROR +CME ERROR
PIN ASC0 ASC1 USB MUX1 MUX2 MUX3 Charge 4 Last
- + + + + + + ± ± -
Unsolicited Result Codes
URC 1
^SCFG: "AutoExec", <AutoExecState>, <AutoExecType>, <AutoExecIndex>,
<AutoExecMode>, <AutoExecATC>
If the event specified with <AutoExecType> occurs and the related AT command line is executed this URC is issued.
URC 2
^SYSSTART AIRPLANE MODE
This URC is issued each time the Airplane mode is activated, no matter whether Airplane mode is set with parameter <map>="on" or <mapos>="on". The URC notifies the user that only the AT commands supported in Airplane mode are accessible. After leaving the Airplane mode the URC "^SYSSTART" indicates that the ME has returned to Normal mode and the full set of AT commands is accessible again.
AC75_ATC_V01.002 Page 62 of 569 10/30/06 Confidential / Released
Page 63
AC75 AT Command Set
2.14 AT^SCFG
Parameter Description
s
<AutoExecCmd>
AutoExec Command This parameter serves to switch the Autoexec function on or off.
If it is switched off (<AutoExecCmd>=0), parameters following <AutoExecIndex> are ignored and all settings at the given index are restored to their default values. Value will be saved while switching off the AC75 via AT commands (e.g. AT+CFUN or AT^SMSO) and restored on next power up.
“0“ Disable automatic execution of the AT command(s) specified with <AutoEx-
“1“ Enable automatic execution of the AT command(s) specified with <AutoExe-
<AutoExecType>
AutoExec Event Type This parameter selects the kind of event used to automatically launch the AT command(s) specified with
<AutoExecATC>.
Value will be saved while switching off the AC75 via AT commands (e.g. AT+CFUN or AT^SMSO) and restored on next power up.
“0“ Autoexec activity is driven by ASC0 DTR line activation (OFF-ON transition). “1“ Autoexec activity is timer driven. To specify the time span use <AutoExecPe-
(str)(+CSCS)
ecATC> at a given <AutoExecIndex>.
cATC> at a given <AutoExecIndex>. Not allowed for <AutoExecType>=0
(DTR line activation) while multiplex mode is active, refer to AT+CMUX.
(str)(+CSCS)
riod>.
<AutoExecIndex>
AutoExec Command Index This parameter specifies the command storage index. The following table shows the index ranges supported for
each variant of <AutoExecType>. Value will be saved while switching off the AC75 via AT commands (e.g. AT+CFUN or AT^SMSO) and restored on next power up.
<AutoExecType> value <AutoExecType> event Valid Indices
0 Autoexec activity is driven by ASC0 DTR
1 Autoexec activity is timer driven. 0-2
<AutoExecMode>
AutoExec Command Mode
0...255 This parameter specifies details regarding the behavior of the AC75 when the AT command starts to be exe-
cuted. Value is interpreted as a bit field, unused bits are reserved for future use (RFU) and shall be set to 0. When a call is released by an Autoexec activity, no release indication may be issued on the first logical channel. Value will be saved while switching off the AC75 via AT commands (e.g. AT+CFUN or AT^SMSO) and restored on next power up.
(str)(+CSCS)
0
line activation
(str)(+CSCS)
AC75_ATC_V01.002 Page 63 of 569 10/30/06 Confidential / Released
Page 64
AC75 AT Command Set
2.14 AT^SCFG
s
Bit Mask D0
D
1
0x00 0x01 0x02 0x03
D
2
0x04 4 0: One shot action
Mask
hex
0 1 2 3
Control
dec
00: Ignore ongoing calls 01: Wait until all calls have ended 10: Dismiss any ongoing call 11: RFU
1: Periodic action (for "AutoExec/Period" only) D3 0x08 8 RFU D4 0x10 16 RFU D5 0x20 32 RFU D6 0x40 64 RFU D7 0x80 128 RFU
<AutoExecATC>
(str)(+CSCS)
AutoExec AT command String This parameter specifies the AT command(s) to be launched automatically. Each AT command is executed in
the same way as if it were entered online, this means that command concatenation is possible if supported by the given commands. If serial multiplex mode is activated (AT+CMUX) the first logical channel is used, i.e. CSD calls (data or fax) could be set up. If the AC75 is busy on the serial channel command execution will be delayed until ongoing action is finished. The first two characters of the automatically launched AT command shall be "at". Please refer to examples below. Value will be saved while switching off the AC75 via AT commands (e.g. AT+CFUN or AT^SMSO) and restored on next power up.
<AutoExecPeriod>
(str)(+CSCS)
AutoExec Command Period Parameter specifies the period after which <AutoExecATC> will be executed. Format is "hhh:mm:ss", where
characters indicate hours, minutes and seconds. This parameter applies to <AutoExecType>=1 only. Value will be saved while switching off the AC75 via AT commands (e.g. AT+CFUN or AT^SMSO) and restored on next power up. When using this feature with running java applications, please consider the minimum time for the execution of
AT+CFUN or AT^SMSO is 15 seconds.
000:00:05...240:00:00
<AutoExecPeriodTimeLeft>
(str)(+CSCS)
AutoExec Command Period Left This parameter shows the amount of time left until <AutoExecATC> will be executed. Format is "hhh:mm:ss",
where characters indicate hours, minutes and seconds. This parameter applies to <AutoExecType>=1 only. Due to the internal activity and network signaling an execution delay of several seconds may occur for the overall procedure.
000:00:00...240:00:00
<AutoExecState>
(str)(+CSCS)
AutoExec Command Status This parameter is part of the Autoexec URC which is presented when a scheduled Autoexec activity is being
performed. “1“ The value 1 indicates that the Autoexec activity specified with <AutoExec-
ATC> is currently executed.
AC75_ATC_V01.002 Page 64 of 569 10/30/06 Confidential / Released
Page 65
AC75 AT Command Set
2.14 AT^SCFG
s
<gs0aa>
(str)(+CSCS)
GPRS ATS0 with Attach This parameter can be used to control the behaviour of ATS0.
Parameter is global for all interfaces, volatile and will not be reset by AT&F.
(P)
“on“
When the ATS0=<n> (<n>>0) command is received, the MT will attempt to per­form a GPRS attach.
“off“ When the ATS0=<n> (<n>>0) command is received, the MT will not attempt to
perform a GPRS attach.
<gaa>
(str)(+CSCS)
GPRS with AutoAttach This parameter can be used to control whether the ME will perform a GPRS attach immediately after power-up
and registering to the network or not. If the setting is changed to "enabled" and the ME is not attached yet, it will not initiate an attach immediately but after the next power-up and registration to the network. Parameter is global for all interfaces, non volatile and will not be reset by AT&F.
“disabled“
(D)
GPRS auto attach is disabled
“enabled“ GPRS auto attach is enabled
<gpc>
(str)(+CSCS)
GPRS with persistent contexts This parameter can be used to control whether the ME will store the GPRS context information defined by the
AT+CGDCONT volatile or non volatile.
Parameter is global for all interfaces, non volatile and will not be reset by AT&F.
(D)
“0“
GPRS context definitions are volatile.
“1“ GPRS context definitions are non-volatile and will not be reset by AT&F.
<groid>
(str)(+CSCS)
Ring on incoming GPRS IP data packets This parameter can be used to control the behaviour of the RING line for incoming IP packets in GPRS online
mode. Parameter is local for the interface, volatile and will not be reset by AT&F.
“on“ If the ME is in power saving mode 7 or 9 (see AT+CFUN) and hardware flow
control is in use (AT\Q3) and the RTS line is inactive and there are incoming IP packets for a GPRS context which is online, then the RING line will be acti­vated once, for a time which is configured by the parameter "URC/Ringline/ ActiveTime" (<urat>). The RING line to be used can be configured with the parameter "URC/Ringline" (<uri>).
(P)
“off“
<map>
(str)(+CSCS)
RING line is not activated for incoming IP packets.
MEopMode/Airplane: Enable/disable Airplane mode during operation The two parameters <map> and <mapos> can be used to enable/disable the Airplane mode. Airplane mode
shuts down the radio part of the ME (PA and receiver), causes the ME to log off from the GSM/GPRS network and disables all AT commands whose execution requires a radio connection. A list of AT commands supported during Airplane mode can be found in Section 23.4, Availability of AT Commands Depending on
Operating Mode of ME. The benefit of Airplane mode is that, at locations where no RF emission is allowed
(typically airplanes, hospitals etc.), the subscriber can continue using network-independent features rather than powering off the entire device (e.g. a PDA or smartphone). If the subscriber tries to use an AT command not available in Airplane mode the response "+CME ERROR: Unsupported AT command" is returned.
AC75_ATC_V01.002 Page 65 of 569 10/30/06 Confidential / Released
Page 66
AC75 AT Command Set
2.14 AT^SCFG
Parameter <map> allows entering or leaving the Airplane mode any time during operation, eliminating the need to enter the SIM PIN again. It can be used no matter whether the parameter <mapos> is "on" or "off". Parameter <map> is global for all interfaces, volatile and will not be reset by AT&F.
“on“ Activates Airplane mode and shuts down the radio part of the ME. The URC
"^SYSSTART AIRPLANE MODE" appears.
(P)
“off“
Deactivates Airplane mode, wakes up the radio part of the ME and restores access to network-dependent AT commands. The URC "^SYSSTART" appears.
s
(P)
(str)(+CSCS)
(str)(+CSCS)
reset. After restart or reset, the URC "^SYSSTART AIRPLANE MODE" appears and parameter <map> is "on". The SIM PIN can be entered using the AT+CPIN command. This enables the ME to read data from the SIM and give access to SIM PIN dependent AT commands which are available in Airplane mode, such as phonebook commands or several SMS commands. To notify the user when SIM data are accessible it is recommended to activate the "^SSIM READY" URC and store its presentation mode to the user profile with AT&W. To return from Airplane mode to Normal mode set the parameter <map> to "off" as described above. If PIN authentication was already done, the ME will try now to register to the GSM network.
Airplane mode will not be activated after ME restart or reset.
<mapos>
MEopMode/Airplane: Airplane mode upon ME restart There are two ways to enter Airplane mode upon restart: One is using AT^SCFG with <mapos> as described
below. Another approach is configuring the ME to restart into Airplane mode at a scheduled time. In this case, use the
AT+CALA command, set an alarm time and then switch the ME off. When the alarm time is reached the ME
wakes up to Airplane mode, no matter whether <mapos> was set "on" or "off". Parameter <mapos> is global for all interfaces, non volatile and will not be reset by AT&F.
“on“ Causes the ME to enter the Airplane mode each time the ME is restarted or
“off“
<msi>
MEShutdown/OnIgnition: Enable/disable shutdown by IGT line The parameter specifies two different switching modes of the ignition line IGT: The line may either be used only
to switch on the ME, or to switch it on and off. By factory default the module's IGT line is configured only for switching on the ME. We recommend that great care be taken before changing the switch mode of IGT. It is of vital importance that the following conditions are met to ensure that IGT works properly as ON/OFF switch: Switch-on condition: If the ME is off the IGT line must be asserted for at least 400 ms and then released. Switch-off condition: If the ME is on the IGT line must be asserted for at least 1 s and then released. The switch­off routine is identical with the shutdown procedure initiated by the AT^SMSO command, i.e. the ME performs an orderly shutdown and issues the "^SHUTDOWN" URC. Before switching off the ME wait at least 2 seconds after startup. Furthermore, particular attention shall be given to the USB interface and the DTR signal: The USB interface and the DTR line shall either be decoupled from IGT to avoid unintentional shutdown of the ME, or require special precautions if you wish to restart the ME by plugging the USB cable or to toggle IGT from DTR. For further details please refer to [2]. Parameter <msi> is global for all interfaces, non-volatile and will not be reset by AT&F.
“on“ Ignition line (IGT) can be used to switch on and off the ME. “off“ Ignition line (IGT) can be used to switch on the ME.
AC75_ATC_V01.002 Page 66 of 569 10/30/06 Confidential / Released
Page 67
AC75 AT Command Set
2.14 AT^SCFG
s
<psm9to>
Power saving mode 9 timeout This parameter can be used to query or configure the wake up time for power saving mode 9 (see AT+CFUN with
parameter <fun>=9). Parameter is global for the ME, volatile and will not be reset by AT&F.
5...20
<rba>
Allowed radio band(s) The feature "Radio/Band" with its parameters <rba>, <rbp> and <rbc> can be used to set and query prefer-
ences for selecting frequency bands. The AC75 normally uses an automode algorithm designed to recognize automatically the radio bands of the cur­rent country, typically a combination of two bands. Commonly used dual-band combinations are, for example, 900/1800 MHz in European countries or 850/1900 MHz in North America. The standard radio band combination of a country depends on the ARFCNs (Absolute Frequency Channel Number) and the MCCs (Mobile Country Code) visible at the air interface. This enables the ME to easily find the standard band or band combination of a country every time after power-up and, thus, usually eliminates the need for the subscriber to make any changes. So, if automode is used and the allowed bands are not restricted with <rba> the response parameter
<rbc> shows the standard band(s) of the current area.
As an alternative, if any bands other than those automatically selected by the ME are needed, the automode can be influenced using the AT^SCFG command. This may be necessary, for example, when running tests of GSM applications, when access to specific radio bands shall be restricted or when the final product is not intended for operation in certain countries. Before changing the parameters <rba> or <rbp> ensure that no network activity occurs. The write command cannot be executed when making a call, or sending / receiving short messages. Execution of the write command causes the ME to deregister from and re-register to the network, no matter whether the selected <rbp> or <rba> setting really changes. Therefore, it is useful to have the URC "+CREG" enabled. The status of the SIM PIN authentication remains unchanged, eliminating the need to enter the SIM PIN again after the change.
(str)(+CSCS)
(P)
...36000 The granularity of the timeout value is 100ms (i.e. a value of 10 equal 1 sec-
ond). The minimum timeout value that can be applied is 5, but accuracy is only guaranteed for timeout values greater than 20.
(str)(+CSCS)
The parameter <rba> is intended to restrict the allowed bands to less than four bands. By default, all four bands are allowed. Each band not contained in <rba> is generally disabled. All bands of <rbp> must be contained in the range set with <rba>. The response parameter <rbc> will never show a value outside the <rba> range. <rba> has precedence over <rbp> and <rbc>. The value of <rba> may be one of the single bands listed below or all valid combinations from the values 1, 2, 4 and 8. Thus, the value range of <rba> is "1".."15". To select or deselect a band calculate the sum of the values of all desired bands and enter the resulting value. For example, for 1800 MHz (2) and 850 MHz (8) please enter the value (10). Parameter <rba> is global for the ME, non-volatile and will not be reset by AT&F.
“1“ GSM 900 MHz “2“ GSM 1800 MHz “4“ GSM 1900 MHz “8“ GSM 850 MHz “3“ GSM 900 MHz + GSM 1800 MHz “5“ GSM 900 MHz + GSM 1900 MHz “10“ GSM 850 MHz + GSM 1800 MHz “12“ GSM 850 MHz + GSM 1900 MHz “15“ all bands
AC75_ATC_V01.002 Page 67 of 569 10/30/06 Confidential / Released
Page 68
AC75 AT Command Set
2.14 AT^SCFG
s
<rbp>
Preferred radio band(s) The write command will trigger the band selection, starting with the user preference specified by <rbp>. This
means bands contained in <rbp> will be searched first, regardless of the standard band combination of the cur­rent country. The final result of the band selection can be read from <rbc>. If <rbp> was a band or band combination which differs from the standard band(s) and the requested band(s) are not visible at the air interface the ME reverts to the standard band(s) of this country. Please note that the band selection procedure is independent of the registration procedure, i.e. the ME selects a band no matter whether or not there is a PLMN (Public Land Mobile Network) the ME can register to. So, if the <rbp> was a band or band combination supported by the country, but currently no PLMN can be found, the ME will select the "preferred" band (indicated by <rbc>) without registering to the network. To avoid registration problems, for example when the settings are configured for testing the GSM application it is recommended that the tester first activates the desired band(s) on the test equipment and then executes the AT^SCFG write command. Besides remember that the network registration also depends on the settings made with AT+COPS. The <rbp> is volatile and cannot be read back with the AT^SCFG read command. This is because the value is used only for triggering one single search operation. The parameter <rbp> may be one of the single bands or one of the four dualband combinations listed below. All preferred bands must be contained in the range of allowed bands set with <rba>, invalid combinations are not accepted. To give priority to a certain single band or band combination and suppress all others simply select the same value both for <rbp> and <rba>. The value range of <rbp> is "1...12", but only the bands or band selections listed below are allowed. Trying to set an unsupported value will be denied with "ERROR". To select or deselect a band calculate the sum of the values of all desired bands and enter the resulting value. For example, for GSM 1800 MHz (2) and GSM 850 MHz (8) please enter the value (10).
“1“ GSM 900 MHz “2“ GSM 1800 MHz “4“ GSM 1900 MHz “8“ GSM 850 MHz “3“ GSM 900 MHz + GSM 1800 MHz “5“ GSM 900 MHz + GSM 1900 MHz “10“ GSM 850 MHz + GSM 1800 MHz “12“ GSM 850 MHz + GSM 1900 MHz
(str)(+CSCS)
<rbc>
Currently selected radio band(s)
<rbc> is the single band or dual band combination currently used by the ME, found either by the automode
algorithm or after the network search was triggered with <rbp>. The <rbc> value is saved on power down. When restarted next time the ME tries to select the same band(s) if these are visible. If the band(s) stored with
<rbc> are not visible the ME uses the standard band(s) of the current country and consequently updates the <rbc> value. <rbc> is only a response parameter returned either after sending the read command AT^SCFG? or writing AT^SCFG="Radio/Band".
In addition to <rbc> and to allow the subscriber to be notified whenever the selected band changes it is recom­mended to activate the "
“1“ GSM 900 MHz “2“ GSM 1800 MHz “4“ GSM 1900 MHz “8“ GSM 850 MHz “3“ GSM 900 MHz + GSM 1800 MHz “5“ GSM 900 MHz + GSM 1900 MHz
AC75_ATC_V01.002 Page 68 of 569 10/30/06 Confidential / Released
(str)(+CSCS)
+CIEV: band" (see Section 3.3, AT^SIND).
Page 69
AC75 AT Command Set
2.14 AT^SCFG
“10“ GSM 850 MHz + GSM 1800 MHz “12“ GSM 850 MHz + GSM 1900 MHz
s
<ropr>
(str)(+CSCS)
Radio Output Power Reduction According to 3GPP Rel99, output power reduction for multiple TX slots is a mandatory feature. The amount of
power reduction is configurable up to 3.0dB for 2TX, 4.8dB for 3Tx to 6dB for 4TX. To optimize heat dissipation, power consumption and SAR values it is recommended to use full power reduction (value "3"). Parameter is global for all interfaces, volatile and will not be reset by AT&F.
“1“ Medium Reduction at GMSK (0dB reduction for 1TX and 2TX, 1.8dB for 3TX
and 3dB for 4TX) and Full Power at 8PSK (1TX and 2TX 0dB reduction)
“2“ Maximal Reduction at GMSK (0dB reduction for 1TX, 3dB for 2TX, 4.8dB for
3TX and 6dB for 4TX) and Full Power at 8PSK (1TX and 2TX 0dB reduction)
(P)
“3“
Maximal Reduction at GMSK (0dB reduction for 1TX, 3dB for 2TX, 4.8dB for 3TX and 6dB for 4TX) and Maximal Reduction at 8PSK (0dB reduction for 1TX, 3dB for 2TX)
<tcpBufSize>
(str)(+CSCS)
BufferSize This value defines the default size of the TCP receive queue in bytes. Higher values allow higher throughput but
less number of parallel connections. The total troughput is limited by the GPRS/EDGE network resources and cannot exceed the theoretical maximum gross throughput of 230Kbit. Parameter is global for the ME and non-volatile. Use of default value is recommended. If changed the new value takes effect the next time you start an Internet service with AT^SISO.
3000...5200
(&F)(D)
...20000 Size of TCP receive buffer in bytes.
Possible number of parallel socket connections depending on buffer size:
- 5200 bytes (default): max. 8 connections
- 10000 bytes (medium): max. 4 connecitons
- 20000 bytes (high): max. 2 connections
<tcpIrt>
(str)(+CSCS)
Initial Retransmission Timeout (IRT)
(&F)(D)
1...3
...60 This parameter determines the time (in seconds) the TCP/IP stack will wait
before starting the first retransmission of packets during the initial connection establishment phase. The TCP protocol ensures the retransmission of packets several times at increasing intervals until some upper limit is reached. This mechanism prevents packet loss and serious congestion problems. Parameter is global for the ME and non-volatile. Use of default value is recom­mended. If changed the new value takes effect the next time you start an Inter­net service with AT^SISO.
<tcpMr>
(str)(+CSCS)
Maximum Number of Retransmissions (MR)
(&F)(D)
1...10
...30 This parameter determines the maximum number of times to retransmit TCP
packets while the service is in connected state. If the service is still connecting (connection setup) another algorithm applies. The value set with <tcpMr> will be assumed as default for the <srv-
ParmTag> "tcpMR" when a new service profile is created with AT^SISS. In
each service profile, you can set another "tcpMR" value which has precedence over the global value set with AT^SCFG. Existing service profiles are not affected when you change the global value via AT^SCFG. Parameter is global for the ME and non-volatile. Use of default value is recom­mended.
AC75_ATC_V01.002 Page 69 of 569 10/30/06 Confidential / Released
Page 70
AC75 AT Command Set
2.14 AT^SCFG
s
<tcpOt>
(str)(+CSCS)
Overall TCP Timer for outstanding connections (tcpOT)
1...6000
(&F)(D)
This parameter specifies the number of seconds to wait before closing a con­nection if TCP/IP packets are not acknowledged. Setting the maximum value is practically equivalent to deactivating the tcpOT mechanism because the maximum time would never be reached by the TCP/ IP stack. The value set with <tcpOt> will be assumed as default for the <srv-
ParmTag> "tcpOT" when a new service profile is created with AT^SISS. How-
ever, in each service profile, you can set another "tcpOT" value which has precedence over the global value set with AT^SCFG. Existing service profiles are not affected when you change the global value via AT^SCFG. Parameter is non-volatile. Use of default value is recommended.
<tcpSack>
(str)(+CSCS)
Selective Acknowledge (SAck) This parameter concerns a set of TCP extensions to improve performance and to provide reliable operation. It
defines new TCP options for scaled windows and timestamps, which are designed to provide compatible inter­working with TCPs that do not implement the extensions. The set of TCP extensions to improve performance is described in RFC 1323. The value set with <tcpSack> enables or disables the set of TCP extensions. Parameter is global for the ME. Use of powerup value is recommended.
“0“ Disable set of TCP extensions.
(P)
“1“
Enable set of TCP extensions.
<tcpTtcp>
(str)(+CSCS)
Transaction/TCP (T/TCP) This parameter concerns T/TCP, an extension of TCP to provide a transaction-oriented service.
T/TCP is described in RFC 1644. The value set with <tcpTtcp> enables or disables T/TCP. Parameter is global for the ME. Use of powerup value is recommended.
(P)
“0“
Disable T/TCP extension.
“1“ Enable T/TCP extension.
<tcpWithUrc>
(str)(+CSCS)
URC mode or polling mode for Internet service commands This parameter enables or disables the presentation of the following URCs related to Internet service com-
mands: "^SISR" URC, "^SISW" URC and "^SIS" URC for parameter <urcCause>=0 (Internet service events). "^SIS" URCs with <urcCause>=1 or 2 used to indicate incoming Socket connections are always enabled. Parameter is global for the ME and non-volatile.
(&F)(D)
“on“
Enable URCs related to Internet service commands. Throughout the Chapter "Internet Service AT Commands" the mode is also referred to as URC mode.
“off“ Disable URCs related to Internet service commands.
This requires the host application to employ polling techniques when using the Internet service AT commands: The host application is responsible to retrieve all status information needed to control an Internet session. The method is referred to as polling mode.
AC75_ATC_V01.002 Page 70 of 569 10/30/06 Confidential / Released
Page 71
AC75 AT Command Set
2.14 AT^SCFG
s
<OtapTracer>
(str)(+CSCS)
OTAP tracer This parameter enables a trace output of the Java Over The Air procedure. The tracer is useful for obtaining
additional information when setting up an OTAP scenario. The output is provided on the interface on which the command was entered. While the tracer is enabled the interface is used for trace output only, meaning that no AT commands can be entered. The tracer will be switched off only by a reset of the module, e.g. after a com­pleted OTAP procedure.
“1“ Enable OTAP tracer.
<deviceDescr>
(str)(+CSCS)
Device Descriptor This parameter determines whether to use the Siemens standard USB Device Descriptor configuration (default)
or a Device Descriptor configuration customized by the application manufacturer. Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after AC75 restart.
(D)
“0“
Siemens standard USB Device Descriptor. If <deviceDescr>=0 is set all other parameters related to "Serial/USB/DDD" cannot be changed. For use in a Windows environment, the "usbmodem.inf" file delivered with AC75 shall be present. Note that whenever the AC75 firmware is updated over the USB interface the Siemens standard configuration must be present. Therefore, before starting a AC75 firmware download be sure that <deviceDescr>=0 is activated and, under Windows, the Siemens "usbmodem.inf" file can be found. Remember to restart the ME after reverting to <deviceDescr>=0 and before starting the firmware download.
“1“ Customer specific USB Device Descriptor.
If <deviceDescr>=1 is set all other parameters related to "Serial/USB/DDD" can be changed. Customizing the USB Device Descriptor configuration requires a unique Ven­dor ID obtained from the USB Implementers Forum. For information please refer to http://www.usb.org. For use under Windows a customized INF file for the USB modem must be present. An easy way to create this file is copying the Siemens "usbmodem.inf" file and overwriting the equivalent values changed with AT^SCFG, usually at least the Vendor ID, Product ID and, optionally, the manufacturer string. This is because the strings given for the customized "Serial/USB/DDD" parameters must be identical with those contained in the INF file.
<descrIndex>
(str)(+CSCS)
Descriptor Index As the AC75 shall be capable of holding 0 - 3 customized Device Desciptor configurations, the <descrIndex>
allows to create and select different parameter sets consisting of the parameters listed below. Please note that AC75 Release 01.002 supports only one parameter set associated to value 0. Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after AC75 restart.
(D)
“0“
Index for the first descriptor definition. “1“ Future use. “2“ Future use. “3“ Future use.
AC75_ATC_V01.002 Page 71 of 569 10/30/06 Confidential / Released
Page 72
AC75 AT Command Set
2.14 AT^SCFG
s
<langId>
(str)(+CSCS)
Language ID Please refer to USB.ORG [28] to find the language IDs currently defined for USB devices. If parameter
<langId> is not specified, the default value of the Siemens standard USB Device Descriptor configuration
applies (US English). Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after AC75 restart. Parameter length: maximum 4 characters.
<vendorId>
(str)(+CSCS)
Vendor ID This parameter represents the Vendor ID obtained from the USB Implementers Forum. The Vendor ID will,
together with the Product ID, be transmitted to the host during initialization. The given Vendor ID must be included in the INF file needed for Windows. Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after AC75 restart. Parameter length: maximum 4 characters.
<productId>
(str)(+CSCS)
Product ID Product ID (PID) defined by the application manufacturer to identify the USB device.
The Product ID will, together with the Vendor ID, be transmitted to the host during initialization. The given Prod­uct ID must be included in the INF file needed for Windows. Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after AC75 restart. Parameter length: maximum 4 characters.
<manufacturer>
(str)(+CSCS)
Manufacturer name Optional manufacturer string defined by the application manufacturer. If specified with <manufacturer> the
same string shall be included in the INF file needed for Windows. Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after AC75 restart. Parameter length: maximum 63 characters.
<product>
(str)(+CSCS)
Product string Optional product name defined by the application manufacturer. If specified with <product> it is recommended
to include the same string into the INF file. Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after AC75 restart. Parameter length: maximum 63 characters.
<serialNo>
(str)(+CSCS)
Device's serial number Optional serial number. Empty string if not used, like in the case of the Siemens standard USB Device Descriptor
configuration. A serial number has several advantages. For example, it enables the host to assign the same virtual COM port to same USB device even though the device is connected to another USB port. This eliminates the need for the host to load the driver again. Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after AC75 restart. If parameter <serialNo> is not specified, the default value of Siemens standard USB Device Descriptor applies. Parameter length: maximum 63 characters.
AC75_ATC_V01.002 Page 72 of 569 10/30/06 Confidential / Released
Page 73
AC75 AT Command Set
2.14 AT^SCFG
s
<succ>
(str)(+CSCS)
CIEV Call Status Indication This parameter can be used to control the behaviour of URC "+CIEV: call". See also AT+CIND, AT+CMER and
Section 7.1, Call Status Information. Parameter is global for all interfaces and will not be reset by AT&F.
“restricted“
(P)
URC "+CIEV: call" will be issued only when a Call Status transition ends in
state "active" or "unknown" (see Section 7.1, Call Status Information) for a call
in the list of active calls. “verbose“ URC "+CIEV: call" will be issued when any state transition (including transi-
tions beginning or ending in state "unknown") occurs in the list of active calls,
or when a traffic channel is established.
<sucs>
(str)(+CSCS)
SLCC Call Status Indication This parameter can be used to control the behaviour of URC "^SLCC". See also AT^SLCC and Section 7.1, Call
Status Information.
Parameter is global for all interfaces and will not be reset by AT&F. “restricted“ URC "^SLCC" will be issued only when a Call Status transition ends in state
"active" or "unknown" (see Section 7.1, Call Status Information) for a call in the
list of active calls “verbose“
(P)
URC "^SLCC" will be issued when any state transition (including transitions
beginning or ending in state "unknown") occurs in the list of active calls, or
when a traffic channel is established.
<uri>
(str)(+CSCS)
URC RING line This parameter can be used to control the behaviour of the RING line to indicate URCs (both for idle interfaces
and, if configured by the parameter "URC/Datamode/Ringline", if link is reserved) and, if configured, the indicator for incoming IP packets (see parameter "GPRS/RingOnIncomingData" (<groid>). Parameter is local for the interface, volatile and will not be reset by AT&F.
“off“ URC is not indicated by RING.
(P)
“local“
URC will be indicated by an activated RING line of the interface on which the
URC appears “asc0“ URC is indicated by an activated RING0 line.
<udri>
(str)(+CSCS)
URC Datamode RING line This parameter specifies whether RING or BREAK is used for the signaling of URCs when the TA-TE link is
reserved (e.g. during circuit-switched data calls, fax connections, in GPRS data mode or during the execution of an AT command). Parameter is global for all interfaces, volatile and will not be reset by AT&F.
(P)
“off“
URC will be indicated by BREAK “on“ URC is indicated by an active RING line for a time which is configured by the
parameter "URC/Ringline/ActiveTime" (<urat>). The RING line which will be
used, can be configured by the parameter "URC/Ringline" (<uri>).
AC75_ATC_V01.002 Page 73 of 569 10/30/06 Confidential / Released
Page 74
AC75 AT Command Set
2.14 AT^SCFG
s
<urat>
(str)(+CSCS)
URC RING line Active Time This parameter can be used to control how long the RING line is activated to indicate URCs (both for idle inter-
faces and, if configured by the parameter "URC/Datamode/Ringline" (<udri>), if link is reserved) and, if con­figured by the parameter "GPRS/RingOnIncomingData", to indicate incoming GPRS IP data packets (<groid>). Parameter is global for all interfaces, volatile and will not be reset by AT&F.
“0“ RING line will be activated for a time between 4.6 and 9.2 ms. “1“ RING line will be activated for about 100ms.
(P)
“2“
<ua>
(str)(+CSCS)
RING line will be activated for about 1s.
Userware Autostart Specifies if the userware is started automatically on power-up.
If autostart is enabled, it is no longer possible to use the multiplexer (see AT+CMUX). If the Java application starts, all current calls will be terminated. The Userware/Autostart mechanism takes effect also in Airplane modeand CHARGE-ONLY-MODE. Parameter is global, stored non-volatile in ME and not reset by AT&F.
(D)
“0“
Userware autostart disabled “1“ Userware autostart enabled
<uaa>
(str)(+CSCS)
Userware Autostart AppName Specifies the absolute path of the userware (the jar/jad file containing the desired application) to be started auto-
matically on power-up. The local flash file system is identified by: "A:", directory separator is "/" (002Fh). The underline character "_" (005Fh) will not be supported. Parameter is global, stored non-volatile in ME and not reset by AT&F. Parameter length: maximum 100 characters.
<uad>
(str)(+CSCS)
Userware Autostart Delay
(D)
0
...10000 Specifies the delay time (in 100ms) when the userware is started automatically
after power-up.
Parameter is global, stored non-volatile in ME and not reset by AT&F.
<upwd>
(str)(+CSCS)
Userware Password Password used to change values of userware parameters.
Parameter is global, stored non-volatile in ME and not reset by AT&F. The maximum length of a given password is 8 characters. It is allowed to have an empty password (this is the value on delivery of the module). CAUTION: Be careful not to lose the password. There is no way to reset or recover a forgotten password or to obtain a new password from the manufacturer.
<udbgif1>
(str)(+CSCS)
Userware Debug Interface Local IP address Local IP address of the module used by the userware debugger.
Parameter is global, volatile and not reset by AT&F.
AC75_ATC_V01.002 Page 74 of 569 10/30/06 Confidential / Released
Page 75
AC75 AT Command Set
2.14 AT^SCFG
s
<udbgif2>
(str)(+CSCS)
Userware Debug Interface Remote IP address IP address of the host running the userware debugger.
Parameter is global, volatile and not reset by AT&F.
<udbgif3>
(str)(+CSCS)
Default interface flag for IP connections Flag to select if the userware debug interface is the default interface for IP connections. Parameter is global,
volatile and not reset by AT&F. [“0“] Debug interface is not the default. “1“ Debug interface is default for IP connections.
<umode>
(str)(+CSCS)
Userware Mode Parameter is global, volatile and not reset by AT&F. [“normal“] Userware is started by AT command or autostart option.
“debug“ Userware is started by debugger on host side. “test“ Userware is loaded from test server.
<uurl>
(str)(+CSCS)
Userware Mode: Location Use of parameter depends on selected userware mode.
Parameter is global, volatile and not reset by AT&F. If <umode>= "normal": Parameter is ignored. If <umode>= "debug": File name of application stored on module. Maximum length: 126 characters. If <umode>= "test": URL of the test server. Maximum length: 126 characters.
<uport>
(str)(+CSCS)
Userware Mode: Port Use of parameter depends on selected userware mode.
Parameter is global, volatile and not reset by AT&F.
0...65535 If <umode>= "normal": Parameter is ignored.
If <umode>= "debug": Port number used by debugger.
If <umode>= "test": Port number of the test server.
(str)(+CSCS)
<if>
Interface for Java System.out This parameter specifies the interface to be used for the Java standard output System.out. The selected inter-
face must be supported by the hardware. “ASC0“ System.out is routed to the first serial interface.
The interface is shared between Java CommConnection and System.out. The
baud rate set for CommConnection applies also to System.out.
The value is global, stored non-volatile in ME and is not reset by AT&F. “ASC1“
(D)
System.out is routed to the second serial interface.
The interface is shared between Java CommConnection and System.out. The
baud rate set for CommConnection applies also to System.out.
The value is global, stored non-volatile in ME and is not reset by AT&F. “USB“ System.out is routed to the Universal Serial Bus interface.
AC75_ATC_V01.002 Page 75 of 569 10/30/06 Confidential / Released
Page 76
AC75 AT Command Set
2.14 AT^SCFG
“NULL“ Discard data.
The value is global, stored non-volatile in ME and is not reset by AT&F. “UDP“ System.out is routed to a UDP socket. The parameter requires that the port
number be given with <intvalue>.
"UDP" is intended only for use with the Java IDE and will be set automatically
each time you start the debugging emulator of the AC75 (on-device debug-
ging). Closing the debugger causes the ME to reboot and automatically resets
the <if> value last selected. This eliminates any need for manually setting
"UDP" with AT^SCFG, and, besides, allows you to select another System.out
target to be used when not debugging. Due to this, the value "UDP" is volatile
unlike all other <if> values, and switching to "UDP" is not supported while
Java is running. “FILE“ System.out is written into a file. Requires additional parameters <intvalue>,
<filename> and <logmode>.
The value is global, stored non-volatile in ME and is not reset by AT&F.
s
<intvalue>
This parameter is required only if parameter <if> for the Java System.out is set to "UDP" or "FILE". Parameter is global, stored non-volatile in ME and not reset by AT&F.
1...65535 If <if>= "UDP": UDP port number. It is recommended to use a number greater
<filename>
This parameter is required only if parameter <if> for the Java System.out is set to "FILE". It specifies the abso- lute path and the file name of the log. The local Flash File system is identified by: "A:", directory separator is "/" (002Fh). The underline character "_" (005Fh) is not supported. The log is split into two concatenated files, each using half of the entire log size set with parameter
<intvalue>. Each file name consists of the name specified with parameter <filename> and the numeric
extension "0" or "1" automatically appended, for example "a:/java/log.txt.0" for the first part of the log and "a:/ java/log.txt.1" for the second part. When the first log file reaches half of the log size, the System.out is written to the second file. When the second file is used up, the ME starts to overwrite the first one. Parameter is global, stored non-volatile in ME and not reset by AT&F. Parameter length: maximum 125 characters.
<logmode>
This parameter is required only if parameter <if> for the Java System.out is set to "FILE". The parameter selects the mode of writing System.out data to file. Parameter is global, stored non-volatile in ME and not reset by AT&F.
“buffered“ “secure“ Writes all output data byte by byte to the file.
(str)(+CSCS)
(str)(+CSCS)
(str)(+CSCS)
(D)
than 1023.
If <if>= "FILE": Size of the log file in bytes, values less then 1024 are not sup-
ported.
Uses a buffer and a timer and acts like a write cache.
Notes
• Any changes to parameters of the Autoexec function will be saved and restored on next power-up only when the ME is switched off via AT commands (e.g. AT+CFUN or AT^SMSO).
• Please keep in mind, that each time the ME is restarted the timers of all autoexec actions configured with
<AutoExecType>=1 and <AutoExecPeriod> will be reinitialized and restarted. As a result, an autoexec
action configured at a time later then a scheduled automatic restart would never be executed.
• Be careful using <AutoExecType>=1 with small period values and shutdown or reset AT commands, since only little time remains to change these settings again after AC75 restart.
• If <AutoExecATC> uses AT commands containing secret data, this information may be retrieved with
AT^SCFG?. For instance, this applies if using AT+CPIN.
AC75_ATC_V01.002 Page 76 of 569 10/30/06 Confidential / Released
Page 77
AC75 AT Command Set
2.14 AT^SCFG
• Parameters "GPRS/ATS0/withAttach" (<gs0aa>) and "GPRS/RingOnIncomingData" (<groid>) are avail- able only for modules supporting GPRS.
Examples
EXAMPLE 1
Usage of "AutoExec": Enable sending of a short message (SMS) on next DTR activation (OFF-ON transition). Sent SMS is assumed to be stored at first location of storage selected with AT+CPMS and AT^SSMSS, i.e. SMS may be sent either from SIM or ME storage. Also refer to AT+CMSS and AT+CMGW. Since SMS transmission and ongoing calls are possible at the same time there is no need to wait until all calls have ended (<AutoExecMode>=0).
AT+CMGF=1 OK AT+CNMI=1,1
OK AT+CMGD=1 OK AT+CMGW="01522400045",145 >Test-SMS to be sent from storage! +CMGW: 1 OK AT^SCFG="AutoExec",1,0,0,0,"AT+CMSS=1" ^SCFG: "AutoExec","1","0","0","0","at+cmss=1" ^SCFG: "AutoExec","0","1","0","0","","000:00:00","000:00:00" ^SCFG: "AutoExec","0","1","1","0","","000:00:00","000:00:00" ^SCFG: "AutoExec","0","1","2","0","","000:00:00","000:00:00" OK
If a DTR activation has occured the ME issues the URC "^SCFG: " followed by the response of the executed command; the message reference in this case:
^SCFG:"AutoExec",0,0,1,0,"AT+CMSS=1" OK +CMSS: 16
Enable SMS text mode.
Enable "+CMTI:" URC to be indicated when a short message is received.
Delete first SMS location.
Start writing a short message. Enter the text of the message. Finish with CTRL-Z. Confirms that message is stored to first location.
Enable execution on next DTR activation.
Confirms that AT+CMSS=1 has been issued.
s
EXAMPLE 2
Usage of "AutoExec": Configure AC75 to perform a reset every 10 hours. The execution of the reset command shall be deferred until after any calls have ended. For details regarding software controlled power down refer to AT+CFUN and AT^SMSO.
AT^SCFG="AutoExec",1,1,2,5,"AT+CFUN=0,1","010:00:00" ... OK
After ten hours:
^SCFG:"AutoExec",1,1,2,5,"AT+CFUN=0,1" OK SYSSTART
Confirms that AT+CFUN=0,1 has been issued. AC75 has restarted. Remember that the
"^SYSSTART" URC will not appear if autobauding is enabled.
EXAMPLE 3
Usage of "AutoExec": Switch off the ME after three minutes without restarting it. For details regarding software controlled power down refer to AT+CFUN and AT^SMSO. Please keep in mind that if the GSM alphabet is enabled special characters within the executed AT command
AC75_ATC_V01.002 Page 77 of 569 10/30/06 Confidential / Released
Page 78
AC75 AT Command Set
2.14 AT^SCFG
shall be issued as escape sequences. A list of typical escape sequences can be found in Section 1.5.1, GSM
alphabet tables and UCS2 character values. For example, the caret character "^" included in all Siemens
defined AT commands shall be given as "\1B\14".
AT^SCFG="AutoExec",1,1,0,0,"AT\1B\14SMSO","000:03:00" ^SCFG: "AutoExec","0","0","0","0","" ^SCFG:
"AutoExec","1","1","0","0","ATSMSO","000: 03:00","000:02:59"
Please note that the indication of the escape sequence in the write command response depends on the used program.
^SCFG: "AutoExec","0","1","1","0","","000:00:00","000:00:00" ^SCFG: "AutoExec","0","1","2","0","","000:00:00","000:00:00" OK
After three minutes:
^SCFG:"AutoExec",0,1,1,0,"AT^SMSO" ^SMSO: MS OFF OK ^SHUTDOWN
Indicates that AT^SMSO was successfully executed. The ME enters the POWER DOWN mode.
EXAMPLE 4
Usage of "AutoExec": Deactivate a timer-driven Autoexec function configured at <AutoExecIndex> 2 (such as the periodic auto­matic reset or the automatic switch-off functions configured in the preceding examples):
AT^SCFG="AutoExec",0,1,2 ... OK
EXAMPLE 5
Usage of "URC/Ringline" and "URC/Datamode/Ringline":
AT+CSCS="GSM"
Switch to GSM character set.
OK AT^SCFG?
Query all parameters.
... ^SCFG:"URC/Datamode/Ringline","off"
While the TA-TE link is reserved URCs will be indi­cated by BREAK.
^SCFG:"URC/Ringline","local"
URCs on this interface will be indicated by Ring line associated to the interface (e.g. RING0 for ASC0).
... OK AT^SCFG="URC/Datamode/Ringline","on" ^SCFG:"URC/Datamode/Ringline","on"
While the TA-TE link is reserved URCs will be indi­cated by an activated "local" Ring line.
OK AT^SCFG="URC/Ringline","asc0" ^SCFG:"URC/Ringline","asc0"
URCs on this interface will be indicated by an acti­vated RING0 no matter whether or not the TA-TE link is reserved.
OK AT^SCFG="URC/Datamode/Ringline","off" ^SCFG:"URC/Datamode/Ringline","off"
URCs on this interface will be indicated by an acti­vated RING0 if the TA-TE link is not reserved and by BREAK if the TA-TE link is reserved.
OK AT^SCFG="URC/Ringline"
Disable any Ring line indication for URCs on this interface.
^SCFG:"URC/Ringline","off" OK
s
AC75_ATC_V01.002 Page 78 of 569 10/30/06 Confidential / Released
Page 79
AC75 AT Command Set
2.15 AT^SM20
s

2.15 AT^SM20 Set M20 compatibility mode

M20 is an earlier, widely used SIEMENS GSM engine. The AT^SM20 command selects different modes of responses returned upon execution of the commands ATD and sms commands like e.g. AT+CMGW. Please note that the AT^SM20 command has no effect on any other features and is not intended to adjust other differences between M20 and AC75.
Syntax
Test Command
AT^SM20=?
Response(s)
OK
Read Command
AT^SM20?
Response(s)
^SM20:<CallMode>, <CmgwMode> OK
Write Command
AT^SM20=<CallMode>[, <CmgwMode>]
Response(s)
OK
Reference(s) PIN ASC0 ASC1 USB MUX1 MUX2 MUX3 Charge 4 Last
SIEMENS - + + + + + + - - -
Parameter Description
<CallMode>
Call setup response mode Applies only to voice calls.
0 Set compatibility to Siemens mobile phones.
(&F)
1
<CmgwMode>
Response mode for sending and writing short messages Applies to the sms commands like e.g. AT+CMGS and AT+CMGW command.
0 Set compatibility to Siemens mobile phones.
(&F)
1
(num)
ME will return "OK" immediately after attempting a call with the ATD command. In case of failure, additional call release indications, such as "NO DIAL TONE, "NO CARRIER", "BUSY" will follow.
Default call setup mode, compatible to M20. ME will return "OK" in case of a successful connection, otherwise one of the call release indications "NO DIAL TONE, "NO CARRIER", "BUSY" are indi­cated.
(num)
ME will return +CMS ERROR: <err> when writing or sending of short mes­sages fails.
Default mode for sending and writing short messages, compatible to M20. ME will return "OK", no matter whether or not sms command was successfully executed.
AC75_ATC_V01.002 Page 79 of 569 10/30/06 Confidential / Released
Page 80
AC75 AT Command Set

3. Status Control Commands

s
3. Status Control Commands
The AT Commands described in this chapter allow the external application to obtain various status information from the AC75.

3.1 AT+CMER Mobile Equipment Event Reporting

This command controls details of the "+CIEV" URC presentation related to AT^SIND and AT+CIND. If registered via these commands the URCs are sent whenever a value of the related indicator changes. In addition, AT+CMER controls "^SLCC" URCs related to AT^SLCC. For details refer to Call Status Infor-
mation, AT^SLCC and AT^SCFG, parameter <sucs>.
The read command returns the URC presentation mode <mode> and among others, the indicator event reporting status <ind>. The write command enables and disables the presentation of "+CIEV: <indDescr>, <indValue>
Value>
is the new value of this indicator. After AT+CMER has been switched on, URCs for all registered indicators will be issued. See examples provided in Section 3.2, AT+CIND and Section 3.3, AT^SIND.
][, <indValue>[,...]]" URCs. <indDescr> refers to the name of a "+CIEV" indicator and <indValue>
2
[, <ind-
1
Syntax
Test Command
AT+CMER=?
Response(s)
+CMER: (list of supported<mode>s), (list of supported <keyp>s), (list of supported <disp>s), (list of supported <ind>s), (list of supported <bfr>s)
OK
Read Command
AT+CMER?
Response(s)
+CMER: <mode>, <keyp>, <disp>, <ind>, <bfr> OK
Write Command
AT+CMER=[<mode>[, <keyp>[, <disp>[, <ind>[, <bfr>]]]]]
Response(s)
OK ERROR +CME ERROR
Reference(s) PIN ASC0 ASC1 USB MUX1 MUX2 MUX3 Charge 4 Last
GSM 07.07 - + + + + + + - + -
Unsolicited Result Code
+CIEV: <indDescr>, <indValue>1[, <indValue>2][, <indValue>[,...]]
A value of an indicator has changed. For more details see AT^SIND.
AC75_ATC_V01.002 Page 80 of 569 10/30/06 Confidential / Released
Page 81
AC75 AT Command Set
3.1 AT+CMER
Parameter Description
s
<mode>
(&F)
0
(num)
Discard "+CIEV" and "^SLCC" URCs.
1 Discard "+CIEV" and "^SLCC" URCs when TA-TE link is reserved, e.g. in
online data mode. Otherwise they are forwarded directly to the TE.
2 Buffer "+CIEV" and "^SLCC" URCs in the TA while TA-TE link is reserved, e.g.
in online data mode, and flush them to the TE afterwards. Otherwise they are forwarded directly to the TE.
3Forward "+CIEV" and "^SLCC" URCs directly to the TE. If AC75 is in online
data mode, URCs are signaled via sending BREAK and stored in a buffer. Once it is back in command mode e.g. after +++ was entered, all URCs stored in the buffer will be output.
<keyp>
(&F)
0
<disp>
(&F)
0
<ind>
(&F)
0
(num)
Keypad event reporting is not supported by AC75.
(num)
Display event reporting is not supported by AC75.
(num)
Disable indicator event reporting.
2 Enable indicator event reporting.
(&F)
(num)
TA buffer of URCs defined within this command is cleared when <mode> 1..3
<bfr>
0
is entered.
<indDescr>
(str)
Name of indicator; for a list of all supported indicators please refer to AT+CIND and AT^SIND.
<indValue>
(num)
Value of indicator; for a list of all values for the supported indicators please refer to AT+CIND and AT^SIND.
Notes
• If the ME operates on different instances (MUX channels 1, 2, 3 or ASC0/ASC1) avoid different settings for routing and indicating SMS. For example, if messages shall be routed directly to one instance of the TE (set with AT+CNMI, AT^SSDA), it is not possible to activate the presentation of URCs with AT+CMER or AT+CNMI on another instance. Any attempt to activate settings that conflict with existing settings on another interface, will result in CME ERROR, or accordingly CMS ERROR.
• It is recommended that priority be given to AT+CMER=<mode> 2 or 3. Otherwise, if <mode> equals 1, URCs will be discarded in case of long running AT commands or an active data connectiion.
AC75_ATC_V01.002 Page 81 of 569 10/30/06 Confidential / Released
Page 82
AC75 AT Command Set
3.2 AT+CIND
s

3.2 AT+CIND Indicator control

The AT+CIND command controls the presentation of Indicator Event Reports related to various functions such as battery charge level, signal quality, service availability, sound generation, indication of unread short mes­sages, full SMS storage, call in progress or roaming activities. Use of AT+CIND has become outdated. Rather we recommend the more powerful AT^SIND command which is easier to use and provides additional indicators. All indicators provided by AT+CIND can be handled with
AT^SIND as well.
AT+CIND supports two ways to get the values related to indicators:
• One approach is to query the current status of each indicator by using the read command AT+CIND?. It returns the status no matter whether the indicator has been registered with the write command
AT+CIND=[<mode>[,<mode>[,...]]].
• The other way is an event-driven notification based on the "+CIEV" URCs. In this case, the ME will automat­ically send a message to the application, whenever the value of an indicator changes. The application should be designed to react adequately when receiving a URC. The presentation of these URCs depends on two settings:
- The indicators must be registered with the write command AT+CIND=[<mode>[,<mode>[,...]]]. When the
ME is switched on all of them are in registered mode. Any indicator can be excluded if deregistered with
<mode>=0. To register or deregister an indicator the AT+CIND write command requires to type the value <mode>=1 or 0 exactly at the position where the indicator is located in the list. This is not necessary with AT^SIND which allows to specify indicators by name. See examples below.
- The presentation of the registered indicators must be enabled with AT+CMER.
Syntax
Test Command
AT+CIND=?
Response(s)
+CIND: (<indDescr>, list of supported <indValue>s)[, (<indDescr>, list of supported <indValue>s)[, ...]]
OK
Read Command
AT+CIND?
Response(s)
+CIND: <indValue>[, <indValue>[, ...]] OK ERROR +CME ERROR: <err>
Write Command
AT+CIND=<mode>[, <mode>[, ...]]
Response(s)
OK ERROR +CME ERROR: <err>
Reference(s) PIN ASC0 ASC1 USB MUX1 MUX2 MUX3 Charge 4 Last
GSM 07.07 - + + + + + + - + -
Parameter Description
<indValue>
Integer type value, which shall be in range of corresponding <indDescr>
AC75_ATC_V01.002 Page 82 of 569 10/30/06 Confidential / Released
(num)
Page 83
AC75 AT Command Set
3.2 AT+CIND
s
<indDescr>
String values and their <indValue> ranges. More indications are available via AT^SIND. Therefore use of AT^SIND for control of all indications is recom­mended. The following indications are accessible via AT+CIND:
“battchg“ Battery charge level 0..4 or 5 if no measuring is performed, e.g because no bat-
“signal“ Signal quality (0..7)
“service“ Service availability (0-1)
“sounder“ Sounder activity (0-1)
“message“ Unread short message at memory location <mem1> (0-1); refer to AT+CPMS “call“ Call in progress (0-1). Indicator value is "1" if at least one call is in state "active"
“roam“ Roaming indicator (0-1)
“smsfull“ A short message memory storage in the MT has become full (1) or memory
“rssi“ Received signal (field) strength (0..5)
(str)
tery is connected. Also refer to AT^SBC.
The indicated value is the bit error rate of the signal received. Bit errors are esti­mated values. See also AT+CSQ.
0: Not registered to any network 1: Registered to home network or, if "roam"=1 then registered to another net­work
Reports every event that causes the ME to generate a tone. Value 1 means for example: Incoming call - ME is ringing. Note that the URC "+CIEV: sounder" will be out­put only if ringing tones are activated with AT^SRTC. 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.
or "held". Depending on the parameter <succ> selected with AT^SCFG the indicator "call" will be issued
• when a state transition ends in state "active" or state "unknown", if
<succ>="restricted",
• when any state transition (including transitions beginning or ending in state "unknown") occurs in the list of active calls or when a traffic channel is established, if <succ>="verbose".
Also refer to Section 7.1, Call Status Information.
0: Registered to home network or not registered 1: Registered to other network
locations are available (0), i.e. range is (0-1)
0: signal strength <= -112 dbm 1-4: signal strength in 15 dbm steps 5: signal strength >= -51 dbm Received signal (field) strength can also be obtained with AT+CSQ. However, the signal strength is scaled to value range 0..31 by this command.
(&F)(P)
(num)
but can be queried with AT+CIND?. Indicator is registered, indicator event report allowed.
<mode>
0 Indicator is deregistered. The indicator will not be presented as "+CIEV" URC,
[1]
AC75_ATC_V01.002 Page 83 of 569 10/30/06 Confidential / Released
Page 84
AC75 AT Command Set
3.2 AT+CIND
Notes
• Due to its restrictive value range, indicator "call" does not clearly reflect specific call states (such as alerting, active, held etc.), but rather serves to trigger the application to retrieve the new call status from the list of cur­rent calls with the AT commands AT^SLCC, AT+CLCC or AT^SCNI.
• If AT^SCFG setting <succ>="verbose", indicator "call" will be issued also when a traffic channel is estab­lished, or when a call enters states "terminating" or "dropped" (see Call Status Information). In these cases, the relevant information about the cause of the display is available only from AT command
AT^SLCC.
Examples
EXAMPLE 1
^SYSSTART AT+CPIN=9999 OK AT+CIND? +CIND: 5,0,1,0,0,0,0,0
OK AT+CMER=2,0,0,2 OK +CIEV: battchg,5 +CIEV: signal,0 +CIEV: service,1 +CIEV: sounder,0 +CIEV: message,0 +CIEV: call,0 +CIEV: roam,0 +CIEV: smsfull,0 +CIEV: rssi,5 ATD0123456; OK +CIEV: sounder,1 +CIEV: call,1 +CIEV: sounder,0 +CIEV: call,0 NO CARRIER AT+CIND=,,,0,,0 OK ATD0123456; OK NO CARRIER
EXAMPLE 2
Deactivation of indicator "sounder" via AT+CIND
AT+CIND? +CIND: 5,0,1,0,1,0,0,0,4 OK AT+CIND=,,,0 OK
EXAMPLE 3
Deactivation of indicator "sounder" via AT^SIND
AT^SIND="sounder",0 ^SIND: sounder,0,0 OK
The battery is either full or no battery is connected to the ME. The bit error rate of the signal quality is not available (since there is no call in progress). The ME is registered to its home network.
Now activate the Indicator Event Report with AT+CMER.
Full receive signal strength. Make a call.
A set of "+CIEV" URCs is received.
Called party hangs up.
Deregister the indicators "sounder" and "call".
Dial the same call. This time, no URCs are displayed. Called party hangs up.
Query the current status of indicators.
To deactivate indicator "sounder" (= fourth item in list of indicators).
To deactivate indicator "sounder".
s
AC75_ATC_V01.002 Page 84 of 569 10/30/06 Confidential / Released
Page 85
AC75 AT Command Set
3.3 AT^SIND
s

3.3 AT^SIND Extended Indicator Control

Designed for extended event indicator control AT^SIND
• offers greater flexibility than the standard command AT+CIND,
• offers several extra indicators,
• can show the current status of all indicators supported by AT+CIND and AT^SIND,
• can be used to register or deregister the indicators of both commands,
• displays all indicator event reports via "+CIEV" URCs.
Presentation mode of the generated URCs is controlled via AT+CMER.
The AT^SIND read command provides a list of all indicators supported by AT+CIND and AT^SIND. Each indica­tor is represented with its registration mode and current value. The AT^SIND write command can be used to select a single indicator in order to modify its registration and to view the current value.
Syntax
Test Command
AT^SIND=?
Response(s)
^SIND: (<indDescr>, list of supported <indValue>s)[, (<indDescr>, list of supported <indValue>s)[, ...]], (list of supported <mode>s)
OK
Read Command
AT^SIND?
Response(s)
^SIND: <indDescr>, <mode>, <indValue> ^SIND: <indDescr>, <mode>, <indValue>, <eonsOperator>, <servProvider> ^SIND: <indDescr>, <mode>, <nitzUT>, <nitzTZ>, <nitzDST>
[^SIND: <indDescr>, <mode>, <indValue>] ...
OK ERROR +CME ERROR: <err>
Write Command
AT^SIND=<indDescr>, <mode>
Response(s)
^SIND: <indDescr>, <mode>, <indValue>
In case of: <indDescr>="eons" and <mode>=2 ^SIND: <indDescr>, <mode>, <indValue>, <eonsOperator>, <servProvider>
In case of: <indDescr>="nitz" and <mode>=2
^SIND: <indDescr>, <mode>, <nitzUT>, <nitzTZ>, <nitzDST> OK ERROR +CME ERROR: <err>
Reference(s) PIN ASC0 ASC1 USB MUX1 MUX2 MUX3 Charge 4 Last
SIEMENS - + + + + + + - + -
AC75_ATC_V01.002 Page 85 of 569 10/30/06 Confidential / Released
Page 86
AC75 AT Command Set
3.3 AT^SIND
Unsolicited Result Codes
URC 1
Format of the standard indicator:
+CIEV: <indDescr>, <indValue>
Value related to an indicator has changed.
URC 2
Format of the "adnread" indicator issued when accessing the ADN phonebook records stored on the SIM:
+CIEV: <indDescr>, <adnEntry>, <adnNumber>, <adnType>, <adnText> +CIEV: <indDescr>, "READY"
One URC is issued for every used Abbreviated Dialing Number (ADN) phonebook record. After the last record of the ADN phonebook was read, a URC with "READY" tag signals end of processing.
URC 3
Format of the Voice Message indicator, if the number of waiting messages is delivered by the network:
+CIEV: <indDescr>, <indValue>, <vmCounter>
If the number of waiting messages is not delivered the standard indicator applies.
s
URC 4
Format of the "eons" indicator:
+CIEV: <indDescr>, <indValue>, <eonsOperator>, <servProvider>
One URC is issued for each new LAI (Location Area Information) broadcast by the network.
URC 5
Format of the "nitz" indicator:
+CIEV: <indDescr>, <nitzUT>, <nitzTZ>, <nitzDST>
Parameter Description
<indDescr>
String values and their <indValue> ranges. All indicators supported by AT+CIND are accessible with this command, too. A detailed description of these indi­cators can be found there. The following indicators are accessible via AT^SIND only:
“audio“ Activity of the built-in audio unit.
“vmwait1“ Voice Message Waiting Indication for line 1
(str)
0 Audio unit not active. 1 Audio unit is active, for example:
MO voice call: Indicator is output with value 1 when dialing starts. MT voice call: Indicator is output with value 1 when call is ringing.
0 The value 0 notifies that no new voice message is available, and is pro-
vided by the service center to clear the voice message indication after the subscriber has retrieved all voice messages.
1 The value 1 notifies the subscriber that the mailbox contains one or
several messages. "vmwait1" and "vmwait2" indicate the receipt of a special short message with a Voice Message Waiting Indicator. The service must be provisioned by the operator. The numbers 1 or 2 in "vmwait1" and "vmwait2" are related to the two lines of the Alternate Line Service (ALS), also defined in CPHS Phase 2 standard. For further details refer to the AT^SALS command. The presentation mode of the indicator varies with the operator: If more than one message are waiting, some operators only indicate the first one, others deliver the indicator each time a new voice message is put into the mailbox.
AC75_ATC_V01.002 Page 86 of 569 10/30/06 Confidential / Released
Page 87
AC75 AT Command Set
3.3 AT^SIND
After the subscriber has retrieved all voice messages the service center auto­matically sends another message indication which provides the value 0. Some operators may also send the number of waiting voice messages along with the indication. In this case, the number will be displayed by the AC75 as part of the URC. For example, "+CIEV: vmwait1,1,5" notifies that five new voice messages are waiting. However, it should be noted that neither the read com­mand AT^SIND? nor the write command AT^SIND=<mode>,2 display the number of waiting messages. The "vmwait" indicators do not apply if a network provider signals new voice mail(s) via standard SMS. In this case the indicator "message" will be displayed (see AT+CIND).
“vmwait2“ Voice Message Waiting Indication for line 2
0 See description of "vmwait1". 1 See description of "vmwait1".
“ciphcall“ Ciphering Status Change Indication
0 Current call or SMS is not ciphered. 1 Current call or SMS is ciphered. As stated in GSM specifications 02.07 and 02.09 the ciphering indicator feature allows the AC75 to detect that ciphering is not switched on and to indicate this to the user. The ciphering indicator feature may be disabled by the home network operator setting data in the "administrative data" field (EF GSM 11.11. If this feature is not disabled by the SIM, then whenever a connection is in place, which is, or becomes unenciphered, an indication shall be given to the user. This enables the user's decision how to proceed. Read command returns valid ciphering status only if a call is in progress or active. If EF indicates a ciphered link and no URC presentaion will take place. The following restrictions apply if the same serial channel is used for AT^SIND "ciphcall" indication and for the action triggering this URC. In general, the rec­ommended solution is to use a dedicated channel for all status signalling via URCs.
• If an unciphered mobile originated SMS is performed, AT^SIND "ciphcall"
• If an unciphered mobile originated data call is performed, AT^SIND "ciph-
setting disables the ciphering indicator feature read command always
AD
URCs on the same serial channel will be issued after the related "OK" and indicate the ciphering state at this time.
call" URCs on the same serial channel will be issued after the interface is not longer blocked by the call (call is released or temporarily stopped) and indicate the ciphering state at this time.
s
) in the SIM, as defined in
AD
“adnread“ Abbreviated Dialing Number (ADN) Phonebook Read Indication
0 Phonebook reading is not finished. 1 Phonebook reading is finished. Every time after entering the AT+CPIN the module starts reading the ADN phonebook. This can be used to enable the TE to output the phonebook records as URCs. The advantage is that the user does not need to wait until the phonebook read command AT+CPBR is accessible after entering the SIM PIN (depending on the SIM card this may take up to 30 seconds without RSA or 2 minutes with RSA). If <mode>=1 all used ADN phonebook records stored on the SIM will be output as URCs after SIM PIN authentication has been performed successfully. A URC with "READY" tag issued at the end of the list indicates that AC75 has finished reading the phonebook. Note that the settings of AT^SIND and AT+CMER will be restored to their default values when restarting the AC75. Therefore it is recommended that the set­tings be enabled before entering the SIM PIN. This can be done, for example, after rebooting the AC75.
AC75_ATC_V01.002 Page 87 of 569 10/30/06 Confidential / Released
Page 88
AC75 AT Command Set
3.3 AT^SIND
“eons“ Enhanced Operator Name String (EONS) Indication
The Enhanced Operator Name String indicator feature allows the AC75 to out­put various operator names for different PLMN identities via URC. It also allows the output of a different operator name based on a subset of the registered net­work by using a range of Location Area Codes (LACs) or a single LAC. The presentation of the "eons" indicator is determined by network activity. For example, the indicator appears every time a location update occurs or a NITZ information is sent, no matter whether or not the status of the EONS informa­tion has changed. This means that the same EONS information may be reported several times. The EONS tables are stored in the SIM card and will be read at power-up. Following are the SIM Elementary Files that are affected by the introduction of EONS feature in the SIM card: EF
(SIM Service Table) - describes which features are active.
SST
EF
(Operator PLMN List) - contains the PLMN identification and location ID
OPL
together with the index of the corresponding PNN record EF
(PLMN Network Name) - contains the full and short form version of the
PNN
network name for the registered PLMN If the Operator Name Source is CPHS Operator Name String long and short form, refer to <indValue>, the following two SIM Elementary Files will be used: EF who issued the SIM. EF the PLMN operator who issued the SIM.
(Operator Name String) - contains the name of the PLMN operator
ONString
(Operator Name Short form) - contains a short form of the name of
OPShort
s
“nitz“ Network Identity and Time Zone indication
This indicator shows the time relevant information elements of an MM Informa­tion (MMI) or GMM Information (GMMI) message received from the network (see GSM 24.008, ch. 9.2.15a and 9.4.19). The network usually sends a NITZ indicator when the mobile attaches to the network, when it enters a location area with different time zone or when a daylight change occurs. A NITZ indicator may consist of the following parameters: Universal Time (UT), local Time Zone (TZ), Daylight Saving Time (DST). All information elements of MMI/GMMI are optional and therefore, the presentation of the parameters
<nitzUT>, <nitzTZ>, <nitzDST> varies with the network. For example, the
network may send all three parameters UT, TZ, DST, or only UT and TZ or only TZ.
UT is indicated in usual date/time format and represents the current world time (GMT) at the moment when sent. TZ is given as a positive (east) or negative (west) offset from UT in units of 15 minutes. DST shows the number of hours added to the local TZ because of daylight sav­ing time (summertime) adjustment. Usually DST is 1 hour but it can be also 2 hours in certain locations.
Example for time and time zone with DST: +CIEV: nitz,"04/07/23,13:39:20",-28,1 In this example TZ is -28, showing a time offset of -7 hours (west) to Universal Time/GMT (which never changes for DST). DST is 1 which indicates that one hour was added to TZ because of Daylight Saving Time. If a network does not send the DST parameter the TZ value would be -32 (8 hours west) as would be done in winter: +CIEV: nitz,"04/11/23,13:39:20",-32
Please be aware that despite the last NITZ value can be looked up again via "AT^SIND=nitz,2" the returned values may be out of date. Especially the UT value is obsolete because there is no internal NITZ clock and therefore no con­tinuation of UT. NITZ values are lost when the module detaches from network. Also when a
AC75_ATC_V01.002 Page 88 of 569 10/30/06 Confidential / Released
Page 89
AC75 AT Command Set
3.3 AT^SIND
manual network selection fails and the module automatically falls back to the previous network the NITZ values cannot be recalled. Nevertheless an indi­cated time zone is valid until a new MMI/GMMI will trigger another NITZ indi­cation.
“simstatus“ SIM Status Indication
The SIM Status indicator allows the AC75 to output the status of the subscriber identity module (SIM) via URC. 0 SIM card removed.
Note: Another way to verify the SIM card connection is the "^SCKS"
URC enabled with AT^SCKS. For use after restart, its presentation
mode can be stored to the user profile with AT&W. 1 SIM card inserted. 2 SIM PIN1 not required - SIM card unlocked. AC75 automatically regis-
ters to the GSM network without requesting SIM PIN1. 3 SIM PIN1 required - SIM card locked. SIM PIN1 must be entered to
enable AC75 to register to the GSM network. 4 Personalization info ready - CHV (Card Holder Verification) data have
been verified (if required). 5 SIM initialization completed - ME has finished reading SIM data.
Note: Another way to notify the user when SIM data are accessible is
the "^SSIM READY" URC enabled with AT^SSET. For use after restart,
its presentation mode can be stored to the user profile with AT&W.
s
“band“ Currently selected frequency band or band combination.
1...12 Identical with <rbc> of AT^SCFG. The value indicates the band(s) cur-
rently available for network selection, depending on the network config-
uration either a single band or a dualband combination. The URC
appears whenever the status of the currently available band(s)
changes, for example after using the AT^SCFG command to change
the "Radio/Band" parameters <rba> or <rbp>. Please see AT^SCFG
for further detail about the feature "Radio/Band" selection.
“simlocal“ Availability of the SIM card, physically connected
0 SIM removed. 1 SIM inserted. If RSA is active: The AT^SIND "simlocal" URC refers to the unused local SIM. The status of the remote SIM card currently used for the RSA connection is controlled by AT^SCKS. If RSA is inactive: The AT^SIND "simlocal" URC refers to the currently used local SIM. In this case the value is identical to the AT^SCKS value, except for
AT^SCKS value 2.
<indValue>
Integer type value in the range stated above for the corresponding <indDescr>.
Notes specific to the EONS feature: If the indicator is "eons", the <indValue> is a type associated to the operator name according to GSM 22.101
[26]. This type depends on the source of the operator name.
Priority of types associated to the operator names is defined as follows (the type listed first has the highest pri­ority). If a type cannot be indicated the next one will be used. 0 Not registered. 1 EF-OPL and EF-PNN (alphanumeric format, can contain up to 24 characters.) 2 Operator Name String in long and short format according to Common PCN
3 Name information received by the NITZ service long and short form (alphanu-
4 Any operator name stored internal to the ME (alphanumeric format, can con-
(num)
Handset Specification (CPHS) [27] (alphanumeric format, can contain up to 16 characters).
meric format, can contain up to 16 characters). The short form will be displayed only if EF
tain up to 16 characters).
from CPHS is available.
OPShort
AC75_ATC_V01.002 Page 89 of 569 10/30/06 Confidential / Released
Page 90
AC75 AT Command Set
3.3 AT^SIND
5 Broadcast MCC-MNC (numeric format which consists of a 3-digit country code
plus a 2- or 3-digit network code).
The name information received by the NITZ service (type 3) is stored non-volatile. It replaces the operator name of the registered PLMN (type 4) or its numeric form (type 5) stored in the ME. But if the ME, after restart, registers to another PLMN that is not equal to the saved NITZ name information, the NITZ name information must be invalidated. If the type is 2, 4 or 5, AT+COPS with the appropriate <mode> displays the same operator name.
s
<mode>
(num)
0 Indicator is deregistered, i.e. no such indicator event report (URC) will be
issued. <mode>=0 is power-up and factory default of indicators defined by
AT^SIND only.
1 Indicator is registered.
• Indicator event reports are controlled via AT+CMER.
• All indicators can be registered or deregistered via AT^SIND, but different
default settings apply: Power-up and factory default of the indicators sup­ported by AT+CIND is <mode>=1, while, as stated above, indicators defined by AT^SIND only are set to <mode>=0.
2 Query the registration status and the current value of a single indicator type.
<adnEntry>
(num)
ADN phonebook record number on the SIM.
<adnNumber>
(str)
Phone number, for further details see AT+CPBR.
<adnType>
(num)
Address type, for further details see AT+CPBR. 145 Dialing string <adnNumber> includes international access code character '+'. 209 Dialing string <adnNumber> contains printable non-alphabetic non-digit char-
acters saved with the number string.
129 otherwise
<adnText>
(str)
Text assigned to a phone number. For further details see AT+CPBR.
<vmCounter>
If delivered by the network: Number of new voice messages sent as part of the Voice Message Waiting Indicator. Refer to <indDescr>.
<eonsOperator>
Operator in format which depends on the type associated to the operator name. Refer to <indValue>.
<servProvider>
(str)
Service Provider Name according to the status settings (SIM Service No. 17) in the SIM Service Table (SST) of the SIM.
<nitzUT>
Universal Time delivered as part of the "nitz" Indicator. Refer to <indDescr>.
AC75_ATC_V01.002 Page 90 of 569 10/30/06 Confidential / Released
Page 91
AC75 AT Command Set
3.3 AT^SIND
<nitzTZ>
Time Zone delivered as part of the "nitz" Indicator. Refer to <indDescr>.
<nitzDST>
Adjustment for Daylight Saving Time as part of the "nitz" Indicator. Refer to <indDescr>.
Example
Activation and use of indicator "audio":
AT^SIND="audio",1 ^SIND: audio,1,0 OK AT+CMER=2,,,2 OK
+CIEV: battchg,5 +CIEV: signal,0 +CIEV: service,1 +CIEV: sounder,0 +CIEV: message,1 +CIEV: call,0 +CIEV: roam,0 +CIEV: smsfull,0 +CIEV: rssi,4 +CIEV: audio,0 ATD030123456 OK +CIEV: audio,1 +CIEV: sounder,1 +CIEV: call,1 +CIEV: signal,0 +CIEV: sounder,0 ATH OK +CIEV: call,0 +CIEV: rssi,3 +CIEV: audio,0 +CIEV: signal,0 +CIEV: rssi,4
You register the indicator "audio".
You activate the Indicator Event Report with AT+CMER. A set of all registered URCs is presented. (Please note that the example
includes the indicators registered due to the power-up default settings of AT+CIND.)
You make a call.
You hang up.
s
AC75_ATC_V01.002 Page 91 of 569 10/30/06 Confidential / Released
Page 92
AC75 AT Command Set
3.4 AT+CEER
s

3.4 AT+CEER Extended Error Report

AT+CEER returns an extended error report regarding the reason of the last
• call release
• failure to set up a call (both mobile originated or terminated)
• failure to modify a call by using Supplementary Services
• failed attempt to activate, register, query, deactivate or deregister a Supplementary Service
• unsuccessful GPRS attach or unsuccessful PDP context activation
• GPRS detach or PDP context deactivation The release cause report is presented in numeric format. Default output in case of a none-error-situation is
+CEER: 0,0,0. A description associated with each number can be found in the tables given in the following sub­clauses and the relevant GSM specifications. The first parameter <locationID> serves to locate the other two parameters. Depending on the failure or release cause either <reason> or <ssRelease> are applicable, i.e. if <reason> ≠ 0, then <ssRelease> = 0. Vice versa, if <reason> = 0, then <ssRelease> may be ≠ 0. In addition to AT+CEER, the command ATS18 can be used to check especially the status of fax and data calls.
Syntax
Test Command
AT+CEER=?
Response(s)
OK ERROR +CME ERROR
Exec Command
AT+CEER
Response(s)
+CEER: <locationID>, <reason>, <ssRelease> OK ERROR +CME ERROR
Reference(s) PIN ASC0 ASC1 USB MUX1 MUX2 MUX3 Charge 4 Last
GSM 07.07 + + + + + + + - + -
Parameter Description
<locationID>
Location ID as number code. Location IDs are listed in Section 3.4.1, Cause Location ID for the extended error
report. Each ID is related with another table that contains a list of <reason>s or <ssRelease>s.
(num)
<reason>
Reason for last call release as number code. The number codes are listed in several tables, sorted by different categories in the following subclauses. The tables can be found proceeding from the Location ID given in Sec­tion 3.4.1, Cause Location ID for the extended error report.
<ssRelease>
Release cause for last Supplementary Service call (listed in Section 3.4.9, GSM Release cause for Supplemen-
tary Service Call)
AC75_ATC_V01.002 Page 92 of 569 10/30/06 Confidential / Released
(num)
(num)
Page 93
AC75 AT Command Set
3.4 AT+CEER
Examples
EXAMPLE 1
ATD"01751223344"; NO CARRIER AT+CEER +CEER: 8,21,0 OK
EXAMPLE 2
The user attempts to activate call barring, but uses a wrong password.
AT+clck=oi,1,"0000",3 +CME ERROR: incorrect password AT+CEER +CEER: 35,0,38 OK
A mobile originated call is rejected by the remote party. Call setup is terminated with NO CARRIER. To check the cause, the caller enters AT+CEER. The Location ID 8 in Section 3.4.1 points to Section 3.4.7, where 21 = "Call rejected". 0 = "No error" refers to parameter <ssRelease> that is
not applicable.
The Location ID 35 in Section 3.4.1 points to Section 3.4.9, where 38 = "NegativePWCheck" may mean that a wrong password was tried for the first time. 0 = "No error" refers to parameter <reason> that is not appli- cable.
s

3.4.1 Cause Location ID for the extended error report

ID Description 0 No error (default) 1 SIEMENS L2 cause 2 GSM cause for L3 Radio Resource Sublayer (GSM 04.08 annex F) 3 SIEMENS cause for L3 Radio Resource Sublayer 4 GSM cause for L3 Mobility Management (GSM 04.08 annex G) 5 SIEMENS cause for L3 Mobility Management 6 GSM cause for L3 Mobility Management via MMR-SAP (GSM 04.08 annex G) 8 GSM cause for L3 Call Control (GSM 04.08 10.5.4.11 and annex H) 9 SIEMENS cause for L3 Call Control 12 GSM cause for L3 SMS CP Entity 13 SIEMENS cause for L3 SMS CP Entity 14 GSM cause for L3 SMS RL Entity 16 GSM cause for L3 SMS TL Entity 17 SIEMENS cause for L3 SMS TL Entity 21 GSM cause for L3 Call-related Supplementary Services 22 SIEMENS cause for L3 Call-related Supplementary Services 33 SIEMENS cause for Supplementary Services Manager 34 Network cause for Supplementary Services (GSM 04.08 10.5.4.11 and annex H) 35 Supplementary Services network error (GSM 04.80 3.6.6) 48 GSM cause for GPRS Mobility Management (GSM 04.08 annex G.6) 49 SIEMENS cause for GPRS Mobility Management 50 GSM cause for Session Management (GSM 04.08 annex I) 127 SIEMENS cause for protocol module or other local cause 128 Supplementary Services general problem (GSM 04.80 3.6.7)
AC75_ATC_V01.002 Page 93 of 569 10/30/06 Confidential / Released
Page 94
AC75 AT Command Set
3.4 AT+CEER
ID Description 129 Supplementary Services invoke problem (GSM 04.80 3.6.7) 130 Supplementary Services result problem (GSM 04.80 3.6.7) 131 Supplementary Services error problem (GSM 04.80 3.6.7) 241 SIEMENS cause for GPRS API 243 SIEMENS cause for PPP/IP-Stack

3.4.2 SIEMENS L2 cause

Number Description 249 L2 Error

3.4.3 GSM release cause for L3 Radio Resource (RR)

s
Number Description 0 Normal event 1 Abnormal release, unspecified 2 Abnormal release, channel unacceptable 3 Abnormal release, timer expired 4 Abnormal release, no activity on the radio path 5 Pre-emptive release 8 Handover impossible, timing advance out of range 9 Channel mode unacceptable 10 Frequency not implemented 65 Call already cleared 95 Semantically incorrect message 96 Invalid mandatory information 97 Message type non-existent or not implemented 98 Message type not compatible with protocol state 100 Conditional information element error 101 No cell allocation available 111 Protocol error unspecified

3.4.4 SIEMENS release cause for L3 Radio Resource (RR)

Number Description 1 Racchs not answered 2 Racchs rejected 3 Access class of the SIM is barred by the network provider 4 SABM failure 5 Radio link counter expiry or PerformAbnormalRelease
AC75_ATC_V01.002 Page 94 of 569 10/30/06 Confidential / Released
Page 95
AC75 AT Command Set
3.4 AT+CEER
Number Description 6 Confirm ABORT of the MM 7 Respond to DEACT REQ 8 Loss of coverage 9 Reestablishment not possible 10 T3122_STILL_RUNNING 11 CELL_SELECTION_IN_PROGRESS 12 RESPONDING_TO_PAGING 13 LOCATION_AREA_CODE_HAS_CHANGED 14 CIRCUIT_SWITCHED_NOT_AVAILABLE
s

3.4.5 GSM release cause for Mobility Management (MM) or Session Management (SM)

Number Description Causes related to MS identification 2 IMSI unknown in HLR 3 Illegal MS 4 IMSI unknown in VLR 5 IMEI not accepted 6 Illegal ME Cause related to subscription options 11 PLMN not allowed 12 Location Area not allowed 13 Roaming not allowed in this location area Causes related to PLMN specific network failures and congestion 17 Network failure 22 Congestion Causes related to nature of request 25 PDP context is deactivated because of a LLC or SNDCP failure 32 Service option not supported 33 Requested service option not subscribed 34 Service option temporarily out of order 38 Call cannot be identified Causes related to invalid messages 95 Semantically incorrect message 96 Invalid mandatory information 97 Message type non-existent or not implemented 98 Message not compatible with protocol state 99 Information element non-existent or not implemented 100 Conditional information element error 101 Messages not compatible with protocol state
AC75_ATC_V01.002 Page 95 of 569 10/30/06 Confidential / Released
Page 96
AC75 AT Command Set
3.4 AT+CEER
Number Description 111 Protocol error, unspecified Causes related to GPRS 7 GPRS services not allowed 8 GPRS services not allowed in combination with non-GPRS services 9 MS identity cannot be identified by the network 10 Implicitly detached 14 GPRS services not allowed in current PLMN 16 MSC temporarily unreachable
s

3.4.6 SIEMENS release cause for L3 Mobility Management (MM)

Number Description 1 No SIM available 8 No MM connection 9 Authentification failure 11 MM performs detach 17 Registration failed and will be re-attempted in a short term 18 CM connection establishment failed 19 Registration failed and will be re-attempted in a long term 20 RR connection is released 21 MS tries to register 22 SPLMN is not available 23 An MTC is in progress 24 A PLMN scan is in progress 25 The MM is detached, the MS is in MS class C GPRS only 26 The maximum numbers of CM connections is exceeded 27 The MM is not registered 28 The MM state is incompatible

3.4.7 GSM release cause for L3 Call Control (CC)

Number Description Normal class 1 Unassigned (unallocated) number 3 No route to destination 6 Channel unacceptable 8 Operator determined barring 16 Normal call clearing 17 User busy 18 No user responding
AC75_ATC_V01.002 Page 96 of 569 10/30/06 Confidential / Released
Page 97
AC75 AT Command Set
3.4 AT+CEER
Number Description 19 User alerting, no answer 21 Call rejected 22 Number changed 25 Pre-emption 26 Non-selected user clearing 27 Destination out of order 28 Invalid number format (incomplete number) 29 Facility rejected 30 Response to STATUS ENQUIRY 31 Normal, unspecified Resource unavailable class 34 No circuit/channel available 38 Network out of order 41 Temporary failure 42 Switching equipment congestion 43 Access information discarded 44 Requested circuit/channel not available 47 Resource unavailable, unspecified Service or option not available class 49 Quality of service unavailable 50 Requested facility not subscribed 55 Incoming calls barred within the CUG 57 Bearer capability not authorized 58 Bearer capability not presently available 63 Service or option not available, unspecified Service or option not implemented 65 Bearer service not implemented 68 ACM equal or greater than ACMmax 69 Requested facility not implemented 70 Only restricted digital information bearer capability is available 79 service or option not implemented, unspecified Invalid message (e.g. parameter out of range) class 81 Invalid transaction identifier value 87 User not member of CUG 88 Incompatible destination 91 Invalid transit network selection 95 Semantically incorrect message Protocol error (e.g. unknown message) class 96 Invalid mandatory information 97 Message type non-existant or not implemented 98 Message type not comaptible with protocol state 99 Information element non-existent or not implemented
s
AC75_ATC_V01.002 Page 97 of 569 10/30/06 Confidential / Released
Page 98
AC75 AT Command Set
3.4 AT+CEER
Number Description 100 Conditional information element error 101 Message not compatible with protocol 102 Recovery on timer expiry 111 Protocol error, unspecified Interworking class 127 Interworking, unspecified
s

3.4.8 SIEMENS release cause for L3 Call Control (CC)

Number Description 2 Service not available 3 Hold procedure not available 4 Temporary no service, previous procedure not yet finished 7 Mobile received a release (complete) message during a modify procedure (modify reject) 10 Number not included in FDN list Notifications 300 Called party barred incoming call

3.4.9 GSM Release cause for Supplementary Service Call

Number Description 0 No error (default) 1 UnknownSubscriber 9 IllegalSubscriber 10 BearerServiceNotProvisioned 11 TeleserviceNotProvisioned 12 IllegalEquipment 13 CallBarred 15 CUGReject 16 IllegalSSOperation 17 SSErrorStatus 18 SSNotAvailable 19 SSSubscriptionViolation 20 SSIncompatibility 21 FacilityNotSupported 27 AbsentSubscriber 29 ShortTermDenial 30 LongTermDenial 34 SystemFailure 35 DataMissing
AC75_ATC_V01.002 Page 98 of 569 10/30/06 Confidential / Released
Page 99
AC75 AT Command Set
3.4 AT+CEER
Number Description 36 UnexpectedDataValue 37 PWRegistrationFailure 38 NegativePWCheck 43 NumberOfPWAttemptsViolation 71 UnknownAlphabet 72 USSDBusy 126 MaxNumsOfMPTYCallsExceeded 127 ResourcesNotAvailable General Problem Codes 300 Unrecognized Component 301 Mistyped Component 302 Badly Structured Component Invoke Problem Codes 303 Duplicate Invoke ID 304 Unrecognized Operation 305 Mistyped Parameter 306 Resource Limitation 307 Initiating Release 308 Unrecognized Linked ID 309 Linked Response Unexpected 310 Unexpected Linked Operation Return Result Problem Codes 311 Unrecognize Invoke ID 312 Return Result Unexpected 313 Mistyped Parameter Return Error Problem Codes 314 Unrecognized Invoke ID 315 Return Error Unexpected 316 Unrecognized Error 317 Unexpected Error 318 Mistyped Parameter
s

3.4.10 GSM release cause for Session Management (SM)

Number Description 102 Recovery on timer expiry
AC75_ATC_V01.002 Page 99 of 569 10/30/06 Confidential / Released
Page 100
AC75 AT Command Set
3.4 AT+CEER
s

3.4.11 GSM cause for L3 Protocol module or other local cause

Number Description 10 Unspecified RLP Error 14 unreliable data link or if the peer instance is not RLP 15 SREJ timed out 16 REMAP procedure timed out

3.4.12 SIEMENS release cause for GPRS API

Number Description 0 Regular deactivation of the call 1 Action temporarily not allowed 2 Wrong connection type 3 Specified data service profile invalid 4 PDP type or address is unknown 5 FDN Check was not successful; GPRS Attach and PDP Context Activation blocked 9 GPRS service not available 255 Undefined

3.4.13 SIEMENS release cause for PPP/IP-Stack

Number Description 0 Regular call deactivation 1 LCP stopped 255 Undefined
AC75_ATC_V01.002 Page 100 of 569 10/30/06 Confidential / Released
Loading...
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use