advertisement
▼
Scroll to page 2
of 475
1 AT Command Manual for Brodersen Products with Siemens MC55 Modem Engine V. 04.00 / April 2006 / Doc 40232 Brodersen Controls A/S ● Industrivej 3 ● DK-4000 Roskilde ● Tel: +45 46 74 00 00 ● Fax: +45 46 75 73 36 E-mail: [email protected] ● Internet: www.brodersencontrols.com Document Name: MC55 AT Command Set Version: 04.00 Date: March 17, 2006 DocId: MC55_ATC_V04.00 Status Confidential / Released General Notes Product is deemed accepted by recipient and is provided without interface to recipient’s products. The documentation and/or product are provided for testing, evaluation, integration and information purposes. The documentation 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 implied warranties of merchantability, completeness, fitness for a particular purpose and non-infringement of thirdparty 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. Failure 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 theory 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 documentation 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. Copyright Transmittal, reproduction, dissemination and/or editing of this document as well as utilization of its contents and communication thereof to others without express authorization are prohibited. Offenders will be held liable for payment of damages. All rights created by patent grant or registration of a utility model or design patent are reserved. Copyright © Siemens AG 2006 MC55_ATC_V04.00 Confidential / Released Page 2 of 475 3/17/06 Contents 1. Introduction............................................................................................................................................ 13 1.1 Scope of the document ................................................................................................................. 13 1.2 Related documents ....................................................................................................................... 14 1.3 Document conventions.................................................................................................................. 15 1.3.1 Quick reference table..................................................................................................... 15 1.3.2 Superscript notation for parameters and values ............................................................ 16 1.4 AT Command Syntax .................................................................................................................... 17 1.4.1 Using Parameters .......................................................................................................... 17 1.4.2 Combining AT commands on the same command line ................................................. 18 1.5 Supported character sets .............................................................................................................. 19 1.5.1 GSM alphabet tables and UCS2 character values ........................................................ 21 1.5.2 UCS2 and GSM data coding and conversion for SMS text mode ................................. 23 1.5.2.1 Implementing output of SIM data to Terminal (direction TA to TE) ................................ 23 1.5.2.2 Implementing input of Terminal data to SIM (direction TE to TA)................................... 24 1.6 Serial Interface Flow Control ......................................................................................................... 25 1.6.1 Software Flow Control (XON/OFF Handshake)............................................................. 25 1.6.2 Hardware Flow Control (RTS/CTS Handshake) ............................................................ 25 1.7 Unsolicited Result Code Presentation........................................................................................... 26 1.7.1 Communication between Customer Application and MC55 .......................................... 26 1.8 Common PCN Handset Specification (CPHS) .............................................................................. 27 1.9 Errors and Messages .................................................................................................................... 28 2. Configuration Commands..................................................................................................................... 29 2.1 AT&F Set all current parameters to manufacturer defaults ......................................................... 29 2.2 AT&V Display current configuration ............................................................................................ 30 2.2.1 AT&V responses............................................................................................................ 31 2.3 AT&W Stores current configuration to user defined profile ......................................................... 32 2.4 ATQ Set result code presentation mode ..................................................................................... 33 2.5 ATV Set result code format mode ............................................................................................... 34 2.5.1 Verbose and numeric result codes ................................................................................ 34 2.6 ATX Set CONNECT result code format and call monitoring ....................................................... 35 2.7 ATZ Set all current parameters to user defined profile................................................................ 36 2.8 AT+CFUN Set phone functionality .............................................................................................. 37 2.8.1 Wake up the ME from SLEEP mode ............................................................................. 40 2.9 AT^SMSO Switch off mobile station............................................................................................ 42 2.10 AT+GCAP Request complete TA capabilities list........................................................................ 43 2.11 AT+CMEE Mobile Equipment Error Message Format ................................................................ 44 2.11.1 CME/CMS Error Code Overview ................................................................................... 45 2.12 AT+CSCS Select TE character set ............................................................................................. 49 2.13 AT^SCFG Extended Configuration Settings ............................................................................... 50 2.14 AT^SM20 Set M20 compatibility mode ....................................................................................... 59 3. Status Control Commands ................................................................................................................... 60 3.1 AT+CMER Mobile Equipment Event Reporting .......................................................................... 60 3.2 AT+CIND Indicator control .......................................................................................................... 62 3.3 AT^SIND Extended Indicator Control .......................................................................................... 65 MC55_ATC_V04.00 Confidential / Released Page 3 of 475 3/17/06 3.4 3.5 3.6 3.7 AT+CEER Extended Error Report............................................................................................... 71 3.4.1 Cause Location ID for the extended error report ........................................................... 72 3.4.2 GSM release cause for L3 Radio Resource (RR).......................................................... 73 3.4.3 SIEMENS release cause for L3 Radio Resource (RR).................................................. 73 3.4.4 GSM release cause for Mobility Management (MM) or Session Management (SM)..... 74 3.4.5 SIEMENS release cause for L3 Mobility Management (MM) ........................................ 75 3.4.6 GSM release cause for L3 Call Control (CC)................................................................. 75 3.4.7 SIEMENS release cause for L3 Call Control (CC)......................................................... 77 3.4.8 SIEMENS release cause for L3 Advice of Charge (AOC) ............................................. 77 3.4.9 GSM Release cause for Supplementary Service Call ................................................... 77 3.4.10 SIEMENS release cause for Call-related Supplementary Services (CRSS) ................. 79 3.4.11 SIEMENS release cause for Session Management (SM) ............................................. 80 3.4.12 GSM cause for L3 Protocol module or other local cause ............................................. 80 3.4.13 SIEMENS release cause for GPRS API ........................................................................ 80 3.4.14 SIEMENS release cause for PPP/IP-Stack ................................................................... 80 ATS18 Extended call release report............................................................................................ 81 AT+CPAS Mobile equipment activity status ................................................................................ 83 AT+WS46 Select wireless network ............................................................................................. 84 4. Serial Interface Control Commands..................................................................................................... 85 4.1 AT\Q Flow control........................................................................................................................ 85 4.2 AT&C Set Data Carrier Detect (DCD) Line mode ....................................................................... 86 4.3 AT&D Set circuit Data Terminal Ready (DTR) function mode..................................................... 87 4.4 AT&S Set circuit Data Set Ready (DSR) function mode ............................................................. 88 4.5 ATE Enable command echo........................................................................................................ 89 4.6 AT+ILRR Set TE-TA local rate reporting ..................................................................................... 90 4.7 AT+IPR Set fixed local rate ......................................................................................................... 92 4.7.1 Autobauding................................................................................................................... 93 4.8 AT+CMUX Enter multiplex mode ................................................................................................ 95 4.8.1 Restrictions on Multiplex mode...................................................................................... 96 4.8.2 Second serial interface ASC1........................................................................................ 98 5. Security Commands .............................................................................................................................. 99 5.1 AT+CPIN PIN Authentication ...................................................................................................... 99 5.1.1 What to do if PIN or password authentication fails? .................................................... 101 5.2 AT+CPIN2 PIN2 Authentication ................................................................................................ 103 5.3 AT^SPIC Display PIN counter ................................................................................................... 105 5.4 AT+CLCK Facility lock .............................................................................................................. 109 5.5 AT^SLCK Facility lock ............................................................................................................... 114 5.6 AT+CPWD Change Password .................................................................................................. 115 5.7 AT^SPWD Change Password ................................................................................................... 119 6. Identification Commands.................................................................................................................... 120 6.1 ATI Display product identification information ........................................................................... 120 6.2 AT+CGMI Request manufacturer identification......................................................................... 121 6.3 AT+GMI Request manufacturer identification ........................................................................... 121 6.4 AT+CGMM Request model identification .................................................................................. 122 6.5 AT+GMM Request model identification..................................................................................... 122 6.6 AT+CGMR Request revision identification of software status................................................... 123 6.7 AT+GMR Request revision identification of software status ..................................................... 123 MC55_ATC_V04.00 Confidential / Released Page 4 of 475 3/17/06 6.8 AT+CGSN Request International Mobile Equipment Identity (IMEI) ......................................... 124 6.9 AT+GSN Request International Mobile Equipment Identity (IMEI) ........................................... 124 6.10 AT+CIMI Request International Mobile Subscriber Identity (IMSI)............................................ 125 7. Call related Commands....................................................................................................................... 126 7.1 Call Status Information ................................................................................................................ 126 7.2 ATA Answer a call ..................................................................................................................... 127 7.3 ATD Mobile originated call to specified number ........................................................................ 128 7.4 ATD><mem><n> Mobile originated call using specific memory and index number ................. 130 7.5 ATD><n> Mobile originated call from active memory using index number ............................... 132 7.6 ATD><str> Mobile originated call from active memory using corresponding field .................... 133 7.7 ATDI Mobile originated call to ISDN number............................................................................. 134 7.8 ATDL Redial last number used ................................................................................................. 135 7.9 ATH Disconnect existing connection......................................................................................... 136 7.10 AT+CHUP Hang up call ............................................................................................................ 137 7.11 ATS0 Set number of rings before automatically answering a call ............................................. 138 7.12 ATS6 Set pause before blind dialing ......................................................................................... 139 7.13 ATS7 Set number of seconds to wait for connection completion .............................................. 140 7.14 ATS8 Set number of seconds to wait for comma dialing modifier............................................. 141 7.15 ATS10 Set disconnect delay after indicating the absence of data carrier ................................. 142 7.16 ATO Switch from command mode to data mode / PPP online mode........................................ 143 7.17 +++ Switch from data mode to command mode ....................................................................... 144 7.18 AT+CBST Select bearer service type ....................................................................................... 145 7.19 AT+CRLP Select radio link protocol parameters for originated non-transparent data calls ...... 146 7.20 AT+CLCC List current calls of ME ............................................................................................ 147 7.21 AT^SLCC Siemens defined command to list current calls of ME.............................................. 149 7.22 AT+CR Service reporting control .............................................................................................. 155 7.23 AT+CRC Set Cellular Result Codes for incoming call indication .............................................. 156 7.24 AT+CSNS Single Numbering Scheme ...................................................................................... 157 7.25 AT^SCNI List Call Number Information ..................................................................................... 158 7.26 AT^SLCD Display Last Call Duration ........................................................................................ 159 7.27 AT^STCD Display Total Call Duration....................................................................................... 160 7.28 ATP Select pulse dialing ........................................................................................................... 161 7.29 ATT Select tone dialing ............................................................................................................. 161 8. Network Service Commands .............................................................................................................. 162 8.1 AT+COPN Read operator names ............................................................................................. 162 8.2 AT+COPS Operator Selection .................................................................................................. 163 8.3 AT^SOPS Extended Operator Selection ................................................................................... 166 8.4 AT+CREG Network registration ................................................................................................ 168 8.5 AT+CSQ Signal quality ............................................................................................................. 171 8.6 AT^SMONC Cell Monitoring...................................................................................................... 172 8.7 AT^SMOND Cell Monitoring...................................................................................................... 174 8.8 AT^MONI Monitor idle mode and dedicated mode ................................................................... 177 8.8.1 AT^MONI responses.................................................................................................... 178 8.8.2 Service states .............................................................................................................. 179 8.9 AT^MONP Monitor neighbour cells ........................................................................................... 180 8.9.1 AT^MONP responses .................................................................................................. 181 8.10 AT^SMONG GPRS Monitor ...................................................................................................... 182 8.10.1 AT^SMONG Cell Info Table......................................................................................... 183 MC55_ATC_V04.00 Confidential / Released Page 5 of 475 3/17/06 8.11 8.12 8.13 8.14 8.15 8.16 AT^SALS AT^SHOM AT^SPLM AT+CPOL AT^SPLR AT^SPLW Alternate Line Service............................................................................................... 184 Display Homezone .................................................................................................. 186 Read the PLMN list .................................................................................................. 187 Preferred Operator List ............................................................................................ 188 Read entry from the preferred operators list............................................................. 189 Write an entry to the preferred operators list ........................................................... 190 9. Supplementary Service Commands .................................................................................................. 191 9.1 AT+CACM Accumulated call meter (ACM) reset or query ........................................................ 191 9.2 AT^SACM Advice of charge and query of ACM and ACMmax ................................................. 192 9.3 AT+CAMM Accumulated call meter maximum (ACMmax) set or query.................................... 194 9.4 AT+CAOC Advice of Charge information .................................................................................. 195 9.5 AT+CCUG Closed User Group ................................................................................................. 196 9.6 AT+CCFC Call forwarding number and conditions control ....................................................... 198 9.7 AT+CCWA Call Waiting ............................................................................................................ 202 9.8 AT+CHLD Call Hold and Multiparty........................................................................................... 206 9.9 AT+CLIP Calling Line Identification Presentation ..................................................................... 208 9.10 AT+CLIR Calling line identification restriction ........................................................................... 210 9.11 AT+COLP Connected Line Identification Presentation ............................................................. 211 9.12 AT+CPUC Price per unit and currency table............................................................................. 213 9.13 AT+CSSN Supplementary service notifications ........................................................................ 215 9.14 AT+CUSD Supplementary service notifications ........................................................................ 217 10. Internet Service Commands ............................................................................................................... 219 10.1 AT^SICS Internet Connection Setup Profile.............................................................................. 222 10.1.1 Example: Default values of a CSD connection profile ................................................. 224 10.1.2 Example: GPRS connection profile ............................................................................. 225 10.2 AT^SICI Internet Connection Information.................................................................................. 226 10.2.1 Checking Connection Profile Status ............................................................................ 227 10.3 AT^SISS Internet Service Setup Profile .................................................................................... 228 10.4 AT^SISI Internet Service Information ........................................................................................ 237 10.5 AT^SISO Internet Service Open ............................................................................................... 239 10.5.1 Example: Accepting / Rejecting Socket Connection Request from Remote Client ..... 242 10.6 AT^SISC Internet Service Close ............................................................................................... 244 10.7 AT^SISR Internet Service Read Data ....................................................................................... 245 10.7.1 Example: Socket Host Reads Small Amounts of UDP Data Packets (URC Mode)..... 246 10.8 AT^SISW Internet Service Write Data....................................................................................... 248 10.8.1 Usage of parameter <eodFlag>................................................................................... 250 10.9 AT^SISE Internet Service Error Report ..................................................................................... 251 10.10 Internet Service URC "^SIS" ....................................................................................................... 252 10.10.1 Information Elements Related to the Service Application............................................ 253 10.10.2 Information Elements Related to FTP Service............................................................. 254 10.10.3 Information Elements Related to HTTP Service .......................................................... 255 10.10.4 Information Elements Related to POP3 Service.......................................................... 255 10.10.5 Information Elements Related to SMTP Service ......................................................... 255 10.11 Examples of how to Configure and Use Internet Service Profiles............................................... 256 10.11.1 Selecting URC Mode or Polling Mode ......................................................................... 256 10.11.2 Configuring Socket Listener......................................................................................... 256 10.11.3 Configuring Socket Client for Calling a Socket Listener on Another Host ................... 257 10.11.4 Socket Client Sends Data via TCP Connection (Polling Mode)................................... 257 MC55_ATC_V04.00 Confidential / Released Page 6 of 475 3/17/06 10.11.5 10.11.6 10.11.7 10.11.8 10.11.9 10.11.10 10.11.11 10.11.12 10.11.13 10.11.14 10.11.15 Socket client sends data via TCP connection with URCs............................................ 258 Configuring and Using FTP Download (URC Mode) ................................................... 258 Configuring and Using FTP Upload (URC Mode)........................................................ 259 Configuring SMPT Service Profile ............................................................................... 259 Sending Email (URC Mode) ........................................................................................ 260 Sending Email (Polling Mode) ..................................................................................... 261 Configuring POP3 Service Profile................................................................................ 262 Retrieving Email (URC Mode) ..................................................................................... 262 Retrieving Email (Polling Mode) .................................................................................. 263 HTTP POST (Polling Mode) ........................................................................................ 264 HTTP GET (Polling Mode)........................................................................................... 265 11. GPRS Commands ................................................................................................................................ 266 11.1 AT+CGACT PDP context activate or deactivate ....................................................................... 266 11.2 AT+CGANS Manual response to a network request for PDP context activation ...................... 268 11.3 AT+CGATT GPRS attach or detach ......................................................................................... 270 11.4 AT+CGAUTO Automatic response to a network request for PDP context activation ............... 271 11.5 AT+CGEREP GPRS event reporting ........................................................................................ 273 11.6 AT+CGDATA Enter data state .................................................................................................. 275 11.6.1 Automatic deactivation of PDP context during dial-up PPP......................................... 276 11.7 AT+CGDCONT Define PDP Context ........................................................................................ 277 11.8 AT+CGPADDR Show PDP address ......................................................................................... 279 11.9 AT+CGQMIN Quality of Service Profile (Minimum acceptable) ................................................ 280 11.10 AT+CGQREQ Quality of Service Profile (Requested) .............................................................. 284 11.11 AT+CGREG GPRS Network Registration Status...................................................................... 288 11.12 AT+CGSMS Select service for MO SMS messages ................................................................. 290 11.13 AT^SGAUTH Set type of authentication for PPP connection.................................................... 291 11.14 AT^SGCONF Configuration of GPRS related Parameters ...................................................... 292 11.15 ATA Manual response to a network request for PDP context activation................................... 293 11.16 ATD*99# Request GPRS service.............................................................................................. 294 11.17 ATD*98# Request GPRS IP service ......................................................................................... 295 11.18 ATH Manual rejection of a network request for PDP context activation.................................... 296 11.19 ATS0 Automatic response to a network request for PDP context activation............................. 297 11.20 Using GPRS AT commands (Examples)..................................................................................... 298 11.21 Using the GPRS dial command ATD .......................................................................................... 300 12. FAX Commands ................................................................................................................................... 301 12.1 FAX parameters .......................................................................................................................... 301 12.1.1 Summary of Fax Class 2 URCs defined by EIA PN-2388 ........................................... 303 12.2 AT+FBADLIN Bad Line Threshold ............................................................................................ 304 12.3 AT+FBADMUL Error Threshold Multiplier ................................................................................. 305 12.4 AT+FBOR Query data Bit Order ............................................................................................... 306 12.5 AT+FCIG Query or set the Local Polling ID .............................................................................. 307 12.6 AT+FCLASS Fax: Select, read or test service class ................................................................. 308 12.7 AT+FCQ Copy Quality Checking .............................................................................................. 309 12.8 AT+FCR Capability to Receive ................................................................................................. 310 12.9 AT+FDCC Query or set capabilities .......................................................................................... 311 12.10 AT+FDFFC Data Compression Format Conversion ................................................................. 312 12.11 AT+FDIS Query or set session parameters .............................................................................. 313 12.12 AT+FDR Begin or continue phase C Data Reception ............................................................... 314 MC55_ATC_V04.00 Confidential / Released Page 7 of 475 3/17/06 12.13 12.14 12.15 12.16 12.17 12.18 12.19 12.20 12.21 12.22 12.23 12.24 12.25 12.26 12.27 12.28 AT+FDT Data Transmission...................................................................................................... 315 AT+FET End a page or document ............................................................................................ 316 AT+FK Kill operation, orderly FAX abort ................................................................................... 317 AT+FLID Query or set the Local Id setting capabilities ............................................................. 318 AT+FMDL Identify Product Model ............................................................................................ 319 AT+FMFR Request Manufacturer Identification ........................................................................ 320 AT+FOPT Set bit Order independently ..................................................................................... 321 AT+FPHCTO DTE Phase C Response Timeout....................................................................... 322 AT+FREV Identify Product Revision ......................................................................................... 323 AT+FRH Receive Data Using HDLC Framing .......................................................................... 324 AT+FRM Receive Data ............................................................................................................. 325 AT+FRS Receive Silence.......................................................................................................... 326 AT+FTH Transmit Data Using HDLC Framing .......................................................................... 327 AT+FTM Transmit Data............................................................................................................. 328 AT+FTS Stop Transmission and Wait ....................................................................................... 329 AT+FVRFC Vertical Resolution Format Conversion ................................................................. 330 13. Short Message Service (SMS) Commands........................................................................................ 331 13.1 SMS parameters ......................................................................................................................... 331 13.2 AT+CMGC Send an SMS command......................................................................................... 335 13.3 AT+CMGD Delete short message............................................................................................. 336 13.4 AT+CMGF Select SMS message format .................................................................................. 337 13.5 AT+CMGL List SMS messages from preferred store................................................................ 338 13.6 AT+CMGR Read SMS messages ............................................................................................. 340 13.7 AT+CMGS Send Short Message .............................................................................................. 342 13.8 AT+CMGW Write Short Messages to Memory ......................................................................... 344 13.9 AT+CMSS Send short messages from storage ........................................................................ 346 13.10 AT+CNMA New Message Acknowledgement to ME/TE, only phase 2+ .................................. 347 13.11 AT+CNMI New short Message Indication ................................................................................. 348 13.12 AT+CPMS Preferred SMS message storage ............................................................................ 351 13.13 AT+CSCA SMS Service Center Address .................................................................................. 353 13.14 AT+CSCB Select Cell Broadcast Message Indication .............................................................. 354 13.15 AT+CSDH Show SMS text mode parameters........................................................................... 355 13.16 AT+CSMP Set SMS text Mode Parameters.............................................................................. 356 13.17 AT+CSMS Select Message Service.......................................................................................... 358 13.18 AT^SLMS List SMS Memory Storage ....................................................................................... 360 13.19 AT^SMGL List Short Messages from preferred store without setting status to REC READ ..... 361 13.20 AT^SMGO Set or query SMS overflow presentation mode or query SMS overflow ................. 362 13.21 AT^SMGR Read short message without setting status to REC READ ..................................... 364 13.22 AT^SSCONF SMS Command Configuration ........................................................................... 365 13.23 AT^SSDA Set SMS Display Availability .................................................................................... 366 13.24 AT^SSMSS Set Short Message Storage Sequence ................................................................. 367 14. SIM related Commands ....................................................................................................................... 368 14.1 AT+CRSM Restricted SIM Access ............................................................................................ 368 14.2 AT^SXSM Extended SIM Access.............................................................................................. 370 14.3 AT^SCKS Query SIM and Chip Card Holder Status ................................................................. 372 14.4 AT^SCID Display SIM card identification number ..................................................................... 374 14.5 AT+CXXCID Display card ID..................................................................................................... 375 MC55_ATC_V04.00 Confidential / Released Page 8 of 475 3/17/06 15. SIM Application Toolkit (SAT) Commands........................................................................................ 376 15.1 AT^SSTA SAT Interface Activation ........................................................................................... 376 15.2 ^SSTN SAT Notification ............................................................................................................ 378 15.3 AT^SSTGI SAT Get Information ............................................................................................... 379 15.4 AT^SSTR SAT Response ......................................................................................................... 380 16. Phonebook Commands....................................................................................................................... 381 16.1 Sort Order for Phonebooks ......................................................................................................... 381 16.2 AT+CPBR Read from Phonebook............................................................................................. 382 16.3 AT+CPBS Select phonebook memory storage ......................................................................... 385 16.4 AT+CPBW Write into Phonebook ............................................................................................. 387 16.5 AT^SPBC Find first matching entry in sorted phonebook ......................................................... 390 16.6 AT^SPBD Purge phonebook memory storage .......................................................................... 391 16.7 AT^SPBG Display phonebook entries in alphabetical order ..................................................... 392 16.8 AT^SPBS Step through the selected phonebook alphabetically ............................................... 395 16.9 AT+CNUM Read own numbers................................................................................................. 399 16.10 AT^SDLD Delete the 'last number redial' memory .................................................................... 400 17. Audio Commands ................................................................................................................................ 401 17.1 Audio programming model .......................................................................................................... 401 17.2 ATL Set monitor speaker loudness ........................................................................................... 402 17.3 ATM Set monitor speaker mode................................................................................................ 402 17.4 AT+CLVL Loudspeaker volume level........................................................................................ 403 17.5 AT+CMUT Mute control ............................................................................................................ 404 17.6 AT+VTD Tone duration ............................................................................................................. 405 17.7 AT+VTS DTMF and tone generation......................................................................................... 406 17.8 AT^SAIC Audio Interface Configuration .................................................................................... 407 17.9 AT^SNFA Set or query of microphone attenuation .................................................................. 409 17.10 AT^SNFD Set audio parameters to manufacturer default values ............................................. 411 17.11 AT^SNFI Set microphone path parameters .............................................................................. 412 17.12 AT^SNFM Set microphone audio path and power supply......................................................... 413 17.13 AT^SNFO Set audio output (= loudspeaker path) parameter ................................................... 415 17.14 AT^SNFPT Set progress tones ................................................................................................. 417 17.15 AT^SNFS Select audio hardware set ........................................................................................ 418 17.16 AT^SNFTTY Signal TTY/CTM audio mode capability............................................................... 421 17.17 AT^SNFV Set loudspeaker volume ........................................................................................... 422 17.18 AT^SNFW Write audio setting in non-volatile store .................................................................. 423 17.19 AT^SRTC Ring tone configuration ............................................................................................ 424 18. Hardware related Commands ............................................................................................................. 426 18.1 AT+CCLK Real Time Clock....................................................................................................... 426 18.2 AT+CALA Set alarm time ......................................................................................................... 427 18.3 AT^SBC Battery Charge Control ............................................................................................... 430 18.3.1 Responses returned by read command....................................................................... 432 18.4 AT^SBV Battery/Supply Voltage ............................................................................................... 433 18.5 AT^SCTM Set critical operating temperature presentation mode or query temperature........... 434 18.6 AT^SSYNC Configure SYNC Pin .............................................................................................. 437 18.6.1 ME status indicated by status LED patterns ................................................................ 438 19. Miscellaneous Commands.................................................................................................................. 439 19.1 A/ Repeat previous command line ............................................................................................ 439 MC55_ATC_V04.00 Confidential / Released Page 9 of 475 3/17/06 19.2 ATS3 Set command line termination character......................................................................... 440 19.3 ATS4 Set response formatting character .................................................................................. 441 19.4 ATS5 Write command line editing character ............................................................................. 442 20. Appendix .............................................................................................................................................. 443 20.1 Restricted access to SIM data after SIM PIN authentication....................................................... 443 20.2 Star-Hash (*#) Network Commands............................................................................................ 444 20.3 Available AT Commands and Dependency on SIM PIN ............................................................. 447 20.4 Availability of AT Commands Depending on Operating Mode of ME.......................................... 454 20.5 AT Command Settings storable with AT&W................................................................................ 461 20.6 Factory Default Settings Restorable with AT&F .......................................................................... 464 20.7 Summary of Unsolicited Result Codes (URC)............................................................................. 467 20.8 Alphabetical List of AT Commands ............................................................................................. 470 MC55_ATC_V04.00 Confidential / Released Page 10 of 475 3/17/06 List of Tables Table 1.1: Table 1.2: Table 1.3: Table 1.4: Table 1.5: Table 2.1: Table 2.2: Table 2.3: Table 2.4: Table 2.5: Table 2.6: Table 2.7: Table 4.1: Table 4.2: Table 10.1: Table 10.2: Table 12.1: Table 18.1: Table 20.1: Table 20.2: Table 20.3: Table 20.4: Table 20.5: Table 20.6: Table 20.7: Table 20.8: Table 20.9: Table 20.10: Table 20.11: Symbols used to mark the type of parameters ........................................................................... 16 Symbols used to indicate the correlations with other commands ............................................... 16 Symbols used to mark different types of default values of parameters ..................................... 16 Types of AT commands and responses .................................................................................... 17 Examples for character definitions depending on alphabet ........................................................ 20 Current configuration on ASC0 / MUX channel 1 (example) ...................................................... 31 Current configuration on ASC1 and MUX channels 2 and 3 (example) .................................... 31 Wake-up events in NON-CYCLIC and CYCLIC SLEEP modes ................................................. 40 General "CME ERROR" Codes (GSM 07.07) .......................................................................... 45 General "CME ERROR" Codes (SIEMENS) ............................................................................ 46 GPRS related "CME ERROR" Codes (GSM 07.07) ................................................................. 46 SMS related "CMS ERROR" Codes (GSM 07.05) ................................................................... 46 Availability of AT Commands on Virtual Channels .................................................................... 96 Summary of AT commands with Different Behavior in Multiplex Mode ..................................... 97 Applicability of AT^SICS <conParmTag> values ................................................................... 222 Applicability of AT^SISS <srvParmTag> values ................................................................... 228 Summary of Fax Class 2 URCs defined by EIA PN-2388 ........................................................ 303 Modes of the LED and indicated ME functions......................................................................... 438 Star-Hash (*#) Command Overview ........................................................................................ 444 Abbreviations of Codes and Parameters used in Table 20.1 .................................................. 445 Star-Hash Command Response Parameters .......................................................................... 446 Star-Hash Commands for Supplementary Services ................................................................ 446 Available AT Commands and Dependency on SIM PIN........................................................... 447 Availability of AT Commands Depending on Operating Mode of ME ....................................... 454 Settings Stored to User Profile on ASC0 / MUX Channel 1...................................................... 461 Settings Stored to User Profile on ASC1 / MUX Channels 2 and 3.......................................... 462 Factory Default Settings Restorable with AT&F ....................................................................... 464 Summary of Unsolicited Result Codes (URC) .......................................................................... 467 Alphabetical List of AT Commands........................................................................................... 470 MC55_ATC_V04.00 Confidential / Released Page 11 of 475 3/17/06 List of Figures Figure 1.1: Figure 1.2: Figure 17.1: Main character table of GSM 03.38 alphabet ............................................................................. 21 Extension character table of GSM 03.38 alphabet ..................................................................... 22 Audio programming model for MC55 Module ........................................................................... 401 MC55_ATC_V04.00 Confidential / Released Page 12 of 475 3/17/06 1. Introduction 1.1 Scope of the document This document presents the AT Command Set for the Siemens Cellular Engine MC55 Release 04.00. Before using the Cellular Engine or upgrading to a new firmware version please read the latest product information provided in the Release Notes [1]. More information is available at the Siemens Website: http://www.siemens.com/wm. MC55_ATC_V04.00 Confidential / Released Page 13 of 475 3/17/06 1.2 Related documents [1] MC55 Release Notes, Version 04.00 [2] MC55 Hardware Interface Description, Version 04.00 [3] GPRS Startup User's Guide [4] Remote-SAT User's Guide [5] Multiplexer User's Guide [6] Multiplex Driver Developer's Guide for Windows 2000 and Windows XP [7] Multiplex Driver Installation Guide for Windows 2000 and Windows XP [8] Application Note 02: Audio Interface Design [9] Application Note 16: Updating MC55 Firmware [10] Application Note 24: Application Developer's Guide [11] Application Note 22: Using TTY / CTM equipment with MC55 [12] ISO/IEC10646: "Universal Multiple-Octet Coded Character Set (UCS)"; UCS2, 16 bit coding [13] ITU-T Recommendation V.24: List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-terminating equipment (DCE) [14] ITU-T Recommendation V.250: Serial asynchronous automatic dialling and control [15] 3GPP TS 100 918/EN 300 918 (GSM 02.04): General on supplementary services [16] 3GPP TS 100 907 (GSM 02.30): Man-Machine Interface (MMI) of the Mobile Station (MS) [17] 3GPP TS 23.038 (GSM 03.38): Alphabets and language specific information [18] 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) [19] 3GPP TS 27.007 (GSM 07.07): AT command set for User Equipment (UE) [20] 3GPP TS 27.060 (GSM 07.60): Mobile Station (MS) supporting Packet Switched Services [21] 3GPP TS 51.011 (GSM 11.11): Specification of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface [22] 3GPP TS 11.14 (GSM 11.14): Specification of the SIM Application Toolkit for the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface [23] 3GPP TS 22.101 (GSM 22.101): Service principles [24] Common PCN Handset Specification (CPHS) v4.2 MC55_ATC_V04.00 Confidential / Released Page 14 of 475 3/17/06 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 definitions 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 20.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 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 Multiplexer 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. Is the AT command supported in ALARM mode? % Yes ! No 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. Example: PIN ! ASC0 ASC1 % % MUX1 MUX2 § § MC55_ATC_V04.00 Confidential / Released MUX3 Charge § % ! Last ! Page 15 of 475 3/17/06 1.3.2 Table 1.1: Superscript notation for parameters and values Symbols used to mark the type of parameters Parameter type Meaning <param> (num) Parameter value must be numeric type <param> (str) Parameter value must be string type Table 1.2: Symbols used to indicate the correlations with other commands Parameter option Meaning <param> (&W) Parameter value will be stored with AT&W <param> (&V) Parameter value will be displayed with AT&V <param> (ˆSNFW) Parameter value will be stored with AT^SNFW <param> (+CSCS) Parameter value has to be (is) coded according to current setting of <chset> (see AT+CSCS for details) Table 1.3: Symbols used to mark different types of default values of parameters Value option Meaning [x] Default value: if the parameter is omitted, the value 'x' will be assumed x (&F) Factory default value, will be restored to 'x' with AT&F x (P) Powerup default value of a parameter which is not stored at power down x (D) Delivery default value of a parameter which cannot be restored automatically MC55_ATC_V04.00 Confidential / Released Page 16 of 475 3/17/06 1.4 AT Command Syntax The "AT" or "at" prefix must be set at the beginning of each command line. To terminate a command line enter <CR>. Commands are usually followed by a response that includes "<CR><LF><response><CR><LF>". Throughout this document, only the responses are presented, <CR><LF> are omitted intentionally. Table 1.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 determined by internal processes in the GSM engine. 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 Query current setting Set only the middle parameter Query new setting Example 2: Using default parameter values for optional parameters AT+CFUN=5 OK AT+CFUN? +CFUN: 5 OK AT+CFUN= OK +CFUN: 1 OK MC55_ATC_V04.00 Confidential / Released Activate CYCLIC SLEEP mode, don't reset ME Query ME mode Set ME back to normal (default parameters: 1,0) Page 17 of 475 3/17/06 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. Otherwise, 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. MC55_ATC_V04.00 Confidential / Released Page 18 of 475 3/17/06 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 interpreted 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 used 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 undefined. Due to the constraints described below it is recommended to prefer the USC2 alphabet in any external application. If the GSM alphabet is selected all characters sent over the serial line (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. MC55_ATC_V04.00 Confidential / Released Page 19 of 475 3/17/06 Table 1.5: Examples for character definitions depending on alphabet GSM 03.38 character GSM character hex. value Corresponding ASCII character ASCII Esc sequence Hex Esc sequence Ö 5C \ \5C 5C 35 43 " 22 " \22 5C 32 32 ò 08 BSP \08 5C 30 38 @ 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 messages which may contain differently coded characters. MC55_ATC_V04.00 Confidential / Released Page 20 of 475 3/17/06 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 accompanying control character. MC55_ATC_V04.00 Confidential / Released Page 21 of 475 3/17/06 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 receiving 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. MC55_ATC_V04.00 Confidential / Released Page 22 of 475 3/17/06 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). 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 DCS = 8 bit Data DCS = 16 bit UCS2 GSM Case 1 GSM (1:1) Case 2 8 bit to IRA (1:2) Case 3 UCS2 to IRA (2:4) Case 4 Case 5 GSM to IRA (1:4) 8 bit to IRA (1:4) Note: The ratio of SIM bytes to output bytes is given in parentheses. Case 6 UCS2 to IRA (2:4) UCS2 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" 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" MC55_ATC_V04.00 Confidential / Released Page 23 of 475 3/17/06 1.5.2.2 Implementing input of Terminal data to SIM (direction TE to TA) Used character set DCS = 7 bit GSM DCS = 8 bit Data DCS = 16 bit UCS2 GSM Case 1 GSM (1:1) Case 2 IRA to 8 bit (2:1) Case 3 IRA to 16 bit (4:2) UCS2 Case 4 Case 5 Case 6 UCS2 to GSM (4:1) UCS2 to 8 bit (4:1) UCS2 to 16 bit (4:2) 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. Hyperterminal). 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 compressed 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 convertedinto 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 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 representation 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 characters 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 characters must be a multiple of four. Invalid UCS2 values must be prevented. MC55_ATC_V04.00 Confidential / Released Page 24 of 475 3/17/06 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 of the input/output buffer should be set to approximately 60% of the total buffer size. The Low Watermark is recommended to be about 30%. The data flow should be stopped when the capacity rises close to the High Watermark and resumed when it drops below the Low Watermark. The time required to cause stop and go results in a hysteresis between the High and Low Watermarks. During Multiplex mode (AT+CMUX) it is recommended to use hardware flow control. 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 therefore, the better choice. When the High Watermark is reached, CTS is set inactive until the transfer from the buffer has completed. When the Low Watermark is passed, CTS goes active again. To achieve smooth data flow, ensure that the RTS/CTS lines are present on your application platform. The application should include options to enable RTS/CTS handshake with the GSM engine. This needs to be done with the AT command AT\Q3 - it is not sufficient to set RTS/CTS handshake in the used Terminal program only. The default setting of the GSM engine is AT\Q0 (no flow control) which must be altered to AT\Q3 (RTS/CTS hardware handshake on). The setting is stored volatile and must be restored each time after the GSM engine was switched off. 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 setting up a CSD call, you are advised to check that RTS/CTS handshake is set. RTS/CTS hardware handshake must also be set if you want to take advantage of the CYCLIC SLEEP modes. For further details refer to AT+CFUN. Note: After deactivating the RTS line, the ME may still send up to 264 bytes (worst case). This can be easily handled if the buffer of the host application is sufficiently sized, and if a hysteresis is implemented regarding its Rx buffer. For host applications that are required to handle a large amount of data at high speed, a total buffer capacity of 512 bytes is recommended. MC55_ATC_V04.00 Confidential / Released Page 25 of 475 3/17/06 1.7 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 20.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 MC55, for details refer to [5] 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" and the Fax Class 2 URCs listed in Section 12.1, FAX parameters. If autobauding is enabled (as factory default mode or set with AT+IPR=0), URCs generated after restart will be output with 57600 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.7.1, Autobauding. To avoid problems we recommend to configure a fixed bit rate rather than using autobauding. 1.7.1 Communication between Customer Application and MC55 Leaving hardware flow control unconsidered the Customer Application (TE) is coupled with the MC55 (ME) via a receive and a transmit line. Since both lines are driven by independent devices collisions may (and will) happen, i.e. while the TE issues an AT command the MC55 starts sending an URC. This will probably lead to the TE's misinterpretation 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 MC55 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 MC55 using activated echo (ATE1), i.e. the MC55 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. MC55_ATC_V04.00 Confidential / Released Page 26 of 475 3/17/06 1.8 Common PCN Handset Specification (CPHS) The ME provides features to implement a device following the prerequisites of the Common PCN Handset Specification (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 Indicate the receipt of a short message coded as Voice Mes- AT^SIND, sage Waiting Indicator as defined by the CPHS Phase 2 AT+CMER, indicators standard. "vmwait1" and "vmwait2" Operator (Service provider) name from SIM Read specific Elementary Files (6F14h, 6F18h) from SIM. AT+CRSM Network and Service Pro- Lock/Unlock an ME to specific HPLMN and service provider. AT+CLCK, vider Lock (AT+CPIN) Call Forwarding Get and set diverted call status. Access specific Elementary File (6F13h) from SIM. AT+CCFC, AT+CRSM Customer Service Profile (CSP) Setting services and their menu entries depending on customer profiles. AT+CRSM Information numbers Hierarchically structured service numbers phonebook on SIM according to CPHS 4.2 (mandatory). AT+CRSM MC55_ATC_V04.00 Confidential / Released Page 27 of 475 3/17/06 1.9 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 commands 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 command syntax although the command has no write format causes "+CME ERROR: <err>" to be returned. See also: • Section 2.11.1, CME/CMS Error Code Overview • Section 2.5.1, Verbose and numeric result codes • Section 3.4, AT+CEER MC55_ATC_V04.00 Confidential / Released Page 28 of 475 3/17/06 2. Configuration Commands The AT Commands described in this chapter allow the external application to determine the MC55'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 (see AT+CGDCONT). Syntax Exec Command AT&F[<value>] Response(s) OK Reference(s) PIN V.250 ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <value>(num) [0] Set all TA parameters to manufacturer defaults Notes • List of parameters reset to manufacturer default can be found in Section 20.6, Factory Default Settings Restorable with AT&F. • In addition to the default profile, you can store an individual one with AT&W. To alternate between the two profiles enter either ATZ (loads user profile) or AT&F (restores factory profile). • Every ongoing or incoming call will be terminated. MC55_ATC_V04.00 Confidential / Released Page 29 of 475 3/17/06 2.2 AT&V Display current configuration AT&V returns the current parameter setting. The configuration varies depending on whether or not PIN authentication has been done and whether or not Multiplex mode is enabled (see AT+CMUX). Syntax Exec Command AT&V[<value>] Response(s) ACTIVE PROFILE: ... (see Section 2.2.1, AT&V responses) OK Reference(s) PIN V.250 ! ASC0 ASC1 % § MUX1 MUX2 % § MUX3 Charge § ! ! Last ! Parameter Description <value>(num) [0] Profile number Notes • The parameters of AT^SMGO can only be displayed after the SMS data from the SIM have been read successfully for the first time. Reading starts after successful SIM authentication has been performed, and may take up to 30 seconds depending on the SIM used. While the read process is in progress, an attempt to read the parameter will result in empty values. • The parameter of AT+CSDH will only be displayed in SMS PDU mode, see AT+CMGF. MC55_ATC_V04.00 Confidential / Released Page 30 of 475 3/17/06 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 (example) PIN authentication done No PIN authentication ACTIVE PROFILE: E1 Q0 V1 X4 &C1 &D2 &S0 \Q0 S0:000 S3:013 S4:010 S5:008 S6:000 S7:060 S8:000 S10:002 S18:000 +CBST: 7,0,1 +CRLP: 61,61,78,6 +CR: 0 +FCLASS: 0 +CRC: 0 +CMGF: 1 +CSDH: 0 +CNMI: 0,0,0,0,1 +ILRR: 0 +IPR: 57600 +CMEE: 2 ^SMGO: 0,0 +CSMS: 0,1,1,1 ^SACM: 0,"000000","000000" ^SLCC: 0 ^SCKS: 0,1 +CREG: 0,1 +CLIP: 0,2 +CAOC: 0 +COPS: 0,0,"operator" +CGSMS: 3 OK ACTIVE PROFILE: E1 Q0 V1 X4 &C1 &D2 &S0 \Q0 S0:000 S3:013 S4:010 S5:008 S6:000 S7:060 S8:000 S10:002 S18:000 +CBST: 7,0,1 +CRLP: 61,61,78,6 +CR: 0 +FCLASS: 0 +ILRR: 0 +IPR: 57600 +CMEE: 2 ^SCKS: 0,1 OK 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 S0:000 S3:013 S4:010 S5:008 +CR: 0 +CRC: 0 +CMGF: 1 +CSDH: 0 +CNMI: 0,0,0,0,1 +ILRR: 0 +IPR: 57600 +CMEE: 2 ^SMGO: 0,0 +CSMS: 0,1,1,1 ^SACM: 0,"000000","000000" ^SLCC: 0 ^SCKS: 0,1 +CREG: 0,1 +CLIP: 0,2 +CAOC: 0 +COPS: 0,0,"operator" +CGSMS: 3 OK ACTIVE PROFILE: E1 Q0 V1 X4 &C1 &D0 &S0 \Q0 S0:000 S3:013 S4:010 S5:008 +CR: 0 +ILRR: 0 +IPR: 57600 +CMEE: 2 ^SCKS: 0,1 +CGSMS: 3 OK MC55_ATC_V04.00 Confidential / Released Page 31 of 475 3/17/06 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 V.250 ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <value>(num) [0] Number of profile 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 executed. • A list of parameters stored to the user profile can be found in Section 20.5, AT Command Settings storable with AT&W. MC55_ATC_V04.00 Confidential / Released Page 32 of 475 3/17/06 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) V.250 PIN ASC0 ASC1 ! % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <n>(num)(&W)(&V) [0](&F) DCE transmits result code 1 Result codes are suppressed and not transmitted MC55_ATC_V04.00 Confidential / Released Page 33 of 475 3/17/06 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 V.250 ! ASC0 ASC1 % MUX1 MUX2 % % % MUX3 Charge % ! ! Last ! Parameter Description <value>(num)(&W)(&V) [0] Information response: <text><CR><LF> Short result code format: <numeric code><CR> 1(&F) 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 MC55_ATC_V04.00 Confidential / Released Page 34 of 475 3/17/06 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) V.250 PIN ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <value>(num)(&W)(&V) [0] CONNECT result code only returned, dial tone and busy detection are both disabled. 1 CONNECT <text> result code only returned, dial tone and busy detection are both disabled. 2 CONNECT <text> result code returned, dial tone detection is enabled, busy detection is disabled. 3 CONNECT <text> result code returned, dial tone detection is disabled, busy detection is enabled. 4(&F) CONNECT <text> result code returned, dial tone and busy detection are both enabled. MC55_ATC_V04.00 Confidential / Released Page 35 of 475 3/17/06 2.7 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 terminated. All defined GPRS contexts which are not activated or not online will be undefined (see AT+CGDCONT). The user defined profile is stored to the non-volatile memory. Syntax Exec Command ATZ[<value>] Response(s) OK Reference(s) V.250 PIN ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <value>(num) [0] Reset to user profile 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. MC55_ATC_V04.00 Confidential / Released Page 36 of 475 3/17/06 2.8 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. SLEEP mode falls in two categories: • NON-CYCLIC SLEEP mode <fun>=0 • and CYCLIC SLEEP modes, selectable as <fun>= 5, 6, 7, 8 or 9. NON-CYCLIC SLEEP mode permanently blocks the serial interface. The CYCLIC SLEEP mode, however, is a dynamic process which alternatingly enables and disables the serial interface. The major benefit of all CYCLIC SLEEP modes 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. The best choice is using <fun>= 7, 8 or 9, since in these modes MC55 automatically resumes power saving, after you have sent or received a short message or made a call. <fun>=5 or 6 do not offer this feature to the same extent and are only supported for compatibility with earlier releases. In all CYCLIC SLEEP modes, you can enter <fun>=1 to permanently wake up MC55 and take it back to full functionality. Please refer to Section 2.8.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 (<fun>= 5, 6, 7, 8 or 9) 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 time when the ME listens to a paging message from the base station. This is the way how the module indicates to the application when the UART is active. For detailed information on the timing of the CTS signal refer to [2]. 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. 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 GSM 07.07 ! MC55_ATC_V04.00 Confidential / Released ASC0 ASC1 % Page 37 of 475 % MUX1 MUX2 § § MUX3 Charge § ! ! Last ! 3/17/06 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. 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 20.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]. Parameter Description <fun>(num) 0 NON-CYCLIC SLEEP mode: 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. The first wake-up event stops power saving and takes the ME back to full functionality level <fun>=1. [1](&F)(P) Full functionality. If the ME is in one of the CYCLIC SLEEP modes you can issue AT+CFUN=1 to stop power saving and return to full functionality. Keep in mind that, unlike the reset command described below, this action does not restart the ME but only changes the level of functionality. See parameter <rst> for details on the reset. 5 CYCLIC SLEEP mode: In this mode, the serial interface is shortly enabled while CTS is active. If characters are recognized on the serial interface, the ME stays active for 2 seconds after the last character was sent or received. 6 CYCLIC SLEEP mode: In this mode, the serial interface is shortly enabled while CTS is active. If characters are recognized on the serial interface, the ME stays active for 10 minutes after the last character was sent or received. To ensure that power saving takes effect immediately, the ME stays active for only 2 seconds after <fun>=6 was entered. 7 CYCLIC SLEEP mode: In this mode, the serial interface is shortly enabled while CTS is active. If characters are recognized on the serial interface, the ME stays active for 2 seconds after the last character was sent or received. ME exits SLEEP mode only, if AT+CFUN=1 is entered. 8 CYCLIC SLEEP mode: In this mode, the serial interface is shortly enabled while CTS is active. If characters are recognized on the serial interface, the ME stays active for 10 minutes after the last character was sent or received. ME exits SLEEP mode only, if AT+CFUN=1 is entered. To ensure that power saving takes effect immediately, the ME stays active for only 2 seconds after <fun>=8 was entered. 9 CYCLIC SLEEP mode: In this mode, the serial interface is shortly enabled while CTS is active. If characters 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 MC55_ATC_V04.00 Confidential / Released Page 38 of 475 3/17/06 by AT^SCFG="PowerSaver/Mode9/Timeout",<psm9to> (temporary wakeup). In contrast to SLEEP modes 5,6,7 and 8 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. ME exits SLEEP mode only, if AT+CFUN=1 is entered. <rst>(num) 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 authentication is necessary (AT+CPIN). If autobauding is enabled, it is recommended to wait 3 to 5 seconds before entering the first AT command. For details on autobauding refer to Section 4.7.1, Autobauding. Notes • If both serial interfaces ASC0 and ASC1 are connected, any functionality level set with AT+CFUN takes effect on both of them. 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 [5], Section "Power saving control". • When a circuit-switched call is in progress, <fun>=7 or 8 or 9 can be activated without terminating the call. However, setting <fun>=0, 5 or 6 during a circuit-switched call immediately disconnects this call. • Please keep in mind that power saving works properly only when PIN authentication has been done. If you attempt to activate power saving while the SIM card is not inserted or the PIN is not correctly entered, the selected <fun> level will be set, though power saving does not take effect. For the same reason, power saving cannot be used if MC55 operates in Alarm mode. Furthermore, in order to accept incoming calls, SMS or network related URCs in SLEEP mode the ME must be registered when it enters the SLEEP mode. • 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]). The LED remains "off" while the module is in any of the SLEEP modes. 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 coverage, 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. Examples EXAMPLE 1 To check the level of functionality use the read command: AT+CFUN? +CFUN: 1 Default mode after ME was restarted Remember that the AT interface is not accessible in NON-CYCLIC SLEEP mode. Consequently, the read command is only useful when the ME is set to full functionality or, when <fun> is set to 5, 6, 7, 8 or 9. AT+CFUN? +CFUN: 5 CYCLIC SLEEP mode EXAMPLE 2 To set the ME to NON-CYCLIC SLEEP mode enter AT+CFUN=0 OK MC55_ATC_V04.00 Confidential / Released Page 39 of 475 3/17/06 When, for example, an SMS is being received and indicated by an unsolicited result code (URC), the ME wakes up to full operation. Note that the URC used in this example will appear only, if AT+CNMI=1,1 was configured before. +CMTI: "SM",5 After this, you may want to verify the operating status: AT+CFUN? +CFUN: 1 Indicates that ME has entered full functionality mode. EXAMPLE 3 To stop CYCLIC SLEEP mode and return to full functionality: AT+CFUN? +CFUN: 5 OK AT+CFUN=1 OK Remember that this approach is not applicable to the NON-CYCLIC SLEEP mode (since the serial interface is disabled). The NON-CYCLIC SLEEP mode ends with the first wake-up event. EXAMPLE 4 To reset and restart the ME: or alternatively, AT+CFUN=0,1 or 5,1 or 6,1 or 7,1 or 8,1 or 9,1 AT+CFUN=1,1 OK ^SYSSTART 2.8.1 The ^SYSSTART URC confirms that the ME has been rebooted. Note that ^SYSSTART appears only if AT+IPR ≠ 0. If the ME is in autobaud mode, it is recommended to wait 3 to 5 seconds before entering the first AT command. Remember to enter the SIM PIN after restart. 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: • • • 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 Event Selected mode: <fun>=0 Selected mode: <fun>=5 or 6 Selected mode: <fun>=7 or 8 or 9 Ignition line No effect No effect No effect /RTS0 or /RTS1 activation Quit No effect (RTS is only used for flow control) Mode 7 and 8: No effect (RTS is only used for flow control) Mode 9: Temporary Unsolicited Result Code (URC) Quit Quit Temporary Incoming voice or data call Quit Quit Temporary MC55_ATC_V04.00 Confidential / Released Page 40 of 475 3/17/06 Event Selected mode: <fun>=0 Selected mode: <fun>=5 or 6 Selected mode: <fun>=7 or 8 or 9 Any AT command (incl. outgoing SMS, voice or data call) Not possible (UART disabled) Temporary Temporary Incoming SMS (AT+CNMI is set to 0,0 (this is the default setting) No effect No effect No effect Incoming SMS (AT+CNMI is set to 1,1) Quit Quit Temporary GPRS data transfer Not possible (UART disabled) Temporary Temporary RTC alarm line Quit Quit Temporary AT+CFUN=1 Not possible (UART disabled) Quit Quit MC55_ATC_V04.00 Confidential / Released Page 41 of 475 3/17/06 2.9 AT^SMSO Switch off mobile station AT^SMSO initiates the power-off procedure. Low level of the module's VDD 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 VDD is low 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 Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % % % Last % 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 physical 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. MC55_ATC_V04.00 Confidential / Released Page 42 of 475 3/17/06 2.10 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) V.250 PIN ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <name>(str) e.g.: +CGSM,+FCLASS Note • +CGSM: The response text shows which GSM commands of the ETSI standard are supported. MC55_ATC_V04.00 Confidential / Released Page 43 of 475 3/17/06 2.11 AT+CMEE Mobile Equipment Error Message Format AT+CMEE controls the format of the error result codes that indicates errors related to MC55 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, General "CME ERROR" Codes (SIEMENS)Table 2.6, GPRS related "CME ERROR" Codes (GSM 07.07) and Table 2.7, 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 GSM 07.07 ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <errMode>(num)(&W)(&V) 0(&F)(D) Disable result code, i.e. only "ERROR" will be displayed. 1 Enable error result code with numeric values. 2 Enable error result code with verbose (string) values. Example To obtain enhanced error messages it is recommended to choose <errMode>=2. AT+CMEE=2 OK MC55_ATC_V04.00 Confidential / Released Page 44 of 475 3/17/06 2.11.1 Table 2.4: CME/CMS Error Code Overview 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 MC55_ATC_V04.00 Confidential / Released Page 45 of 475 3/17/06 <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 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: 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 MC55_ATC_V04.00 Confidential / Released Page 46 of 475 3/17/06 <err> Code Text (if AT+CMEE=2) 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 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 MC55_ATC_V04.00 Confidential / Released Page 47 of 475 3/17/06 <err> Code Text (if AT+CMEE=2) 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 513 unable to store 514 invalid status 515 invalid character in address string 516 invalid length 517 invalid character in pdu 518 invalid parameter 519 invalid length or character 520 invalid character in text 521 timer expired 522 Operation temporary not allowed MC55_ATC_V04.00 Confidential / Released Page 48 of 475 3/17/06 2.12 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) GSM 07.07, GSM 11.11 PIN ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <chset>(str) "GSM"(&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. "UCS2" 16-bit universal multiple-octet coded character set (ISO/IEC10646 [32]); UCS2 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. MC55_ATC_V04.00 Confidential / Released Page 49 of 475 3/17/06 2.13 AT^SCFG Extended Configuration Settings AT^SCFG can be used to query and configure various settings of the MC55. 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: 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: ^SCFG: ^SCFG: ^SCFG: ^SCFG: ^SCFG: ^SCFG: ^SCFG: ^SCFG: ^SCFG: ^SCFG: ^SCFG: ^SCFG: ^SCFG: ^SCFG: OK "Audio/AMR", (list of supported <amr>s) "Call/SpeechVersion1", (list of supported <csv1>s) "GPRS/ATS0/withAttach", (list of supported <gs0aa>s) "GPRS/RingOnIncomingData", (list of supported <groid>s) "PowerSaver/Mode9/Timeout", (list of supported <psm9to>s) "Radio/Band/HandOver", (list of supported <HandOverStatus>s) "Tcp/IRT", (list of supported <tcpIrt>) "Tcp/MR", (list of supported <tcpMr>) "Tcp/OT", (list of supported <tcpOt>) "Tcp/WithURCs", (list of supported <tcpWithUrc>) "URC/CallStatus/CIEV", (list of supported <succ>s) "URC/CallStatus/SLCC", (list of supported <sucs>s) "URC/Datamode/Ringline", (list of supported <udri>s) "URC/Ringline", (list of supported <uri>s) "URC/Ringline/ActiveTime", (list of supported <urat>s) Read Command AT^SCFG? Response(s) ^SCFG: ^SCFG: ^SCFG: ^SCFG: ^SCFG: ^SCFG: ^SCFG: ^SCFG: ^SCFG: "Audio/AMR", <amr>1[, <amr>2[, <amr>3...[<amr>10]]] "Call/SpeechVersion1", <csv1> "GPRS/ATS0/withAttach", <gs0aa> "GPRS/RingOnIncomingData", <groid> "PowerSaver/Mode9/Timeout", <psm9to> "Radio/Band/HandOver", <HandOverStatus> "Tcp/IRT", <tcpIrt> "Tcp/MR", <tcpMr> "Tcp/OT", <tcpOt> MC55_ATC_V04.00 Confidential / Released Page 50 of 475 3/17/06 Read Command (Continued) AT^SCFG? Response(s) ^SCFG: ^SCFG: ^SCFG: ^SCFG: ^SCFG: ^SCFG: OK "Tcp/WithURCs", <tcpWithUrc> "URC/CallStatus/CIEV", <succ> "URC/CallStatus/SLCC", <sucs> "URC/Datamode/Ringline", <udri> "URC/Ringline", <uri> "URC/Ringline/ActiveTime", <urat> Write Command Adaptive Multi Rate (AMR): AT^SCFG="Audio/AMR"[, <amr>] Response(s) ^SCFG: "Audio/AMR", <amr>1[, <amr>2[, <amr>3...[<amr>10]]] OK ERROR +CME ERROR Write Command Query/Configure SpeechVersion1 AT^SCFG="Call/SpeechVersion1"[, <csv1>] Response(s) ^SCFG: "Call/SpeechVersion1", <csv1> 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 Ring on incoming GPRS IP data packets AT^SCFG="GPRS/RingOnIncomingData"[, <groid>] Response(s) ^SCFG: "GPRS/RingOnIncomingData", <groid> OK ERROR +CME ERROR 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 MC55_ATC_V04.00 Confidential / Released Page 51 of 475 3/17/06 Write Command (Continued) Query/Set timeout value for power saving mode 9 AT^SCFG="PowerSaver/Mode9/Timeout"[, <psm9to>] Response(s) ERROR +CME ERROR Write Command Control Special Call Handover Setting AT^SCFG="Radio/Band/HandOver"[, <HandOverStatus>] Response(s) ^SCFG: "Radio/Band/HandOver", <HandOverStatus> 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 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 Internet Service URCs: AT^SCFG="Tcp/WithURCs"[, <tcpWithUrc>] Response(s) ^SCFG: "Tcp/WithURCs", <tcpWithUrc> OK ERROR +CME ERROR MC55_ATC_V04.00 Confidential / Released Page 52 of 475 3/17/06 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 Write Command URC indication via Ring line: AT^SCFG="URC/Ringline"[, <uri>] Response(s) ^SCFG: "URC/Ringline", <uri> OK 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 PIN ! MC55_ATC_V04.00 Confidential / Released ASC0 ASC1 % Page 53 of 475 % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! 3/17/06 Parameter Description <amr>(str)(+CSCS) Adaptive Multi Rate This parameter can be used to control the usage of the feature "Adaptive Multi Rate" (AMR). It is possible to enable or disable this feature for all network operators, or to enable it for selected operators (max. 10). If the feature is enabled for all operators, any request to enable it for a specific operator will result in a "+CME ERROR: operation temporary not allowed". Changes of this parameter become active with the next call. Parameter is global for all interfaces, volatile and will not be reset by AT&F. "enabled"(P) AMR is used for every operator. "disabled" AMR is not used for any operator. 00000...999999 Enable AMR for the specified operator (in BCD or IRA format; see AT+COPS). <csv1>(str)(+CSCS) Call Speech Version1 This parameter can be used to query or configure the speech version 1 indication in the bearer capabilities in case of voice calls (see GSM 04.08). Speech version 2 (EFR) is always enabled; speech version 3 ( AMR) is not affected by this command. If you try to change this parameter as long as a circuit switched call is active, the command returns the new value and "OK", but the changes will not take effect before next call setup. Parameter is global for the ME, volatile and will not be reset by AT&F. "0"(P) FR and HR codecs are enabled for speech calls - full rate codec is preferred. "1" FR and HR codecs are enabled for speech calls - half rate codec is preferred. "2" Half rate codec is disabled for speech calls. <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. "on"(P) When the ATS0=<n> (<n>>0) command is received, the MT will attempt to perform a GPRS attach. "off" When the ATS0=<n> (<n>>0) command is received, the MT will not attempt to perform a GPRS attach. <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 8 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 activated 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>). "off"(P) RING line is not activated for incoming IP packets. MC55_ATC_V04.00 Confidential / Released Page 54 of 475 3/17/06 <psm9to>(str)(+CSCS) 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(P)...36000 The granularity of the timeout value is 100ms (i.e. a value of 10 equal 1 second). The minimum timeout value that can be applied is 5, but accuracy is only guaranteed for timeout values greater than 20. <HandOverStatus>(str)(+CSCS) Call Handover Status This parameter offers a workaround to prevent problems during call handover into the 1900 MHz (or 1800 MHz) band, caused by non-conforming configurations of the 1900 MHz (or 1800 MHz) GSM network. "0"(P) Disable workaround. "1" Enable workaround. This value should be selected when handover into a 1900 MHz (or 1800 MHz) GSM network fails. If required for permanent use the value needs to be set each time the ME is restarted. <tcpIrt>(str)(+CSCS) Initial Retransmission Timeout (IRT) 1...3(&F)(D)...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. In addition, the parameters <tcpMr> and <tcpOt> can be set to further optimize this mechanism for special conditions depending on the mobile network. 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. <tcpMr>(str)(+CSCS) Maximum Number of Retransmissions (MR) 1...10(&F)(D)...30 This parameter determines the maximum number of times to retransmit TCP packets. The value set with <tcpMr> will be assumed as default for the <srvParmTag> "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 recommended. <tcpOt>(str)(+CSCS) Overall TCP Timer for outstanding connections (tcpOT) 1...6000(&F)(D) MC55_ATC_V04.00 Confidential / Released This parameter specifies the number of seconds to wait before closing a connection 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 <srvParmTag> "tcpOT" when a new service profile is created with AT^SISS. HowPage 55 of 475 3/17/06 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. <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 commands: "^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. "on"(&F)(D) 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. <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 transitions 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" MC55_ATC_V04.00 Confidential / Released URC is not indicated by RING. Page 56 of 475 3/17/06 "local"(P) 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. "off"(P) 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>). <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 interfaces and, if configured by the parameter "URC/Datamode/Ringline" (<udri>), if link is reserved) and, if configured 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" "2" RING line will be activated for about 100ms. (P) RING line will be activated for about 1s. Note • Parameters "GPRS/ATS0/withAttach" (<gs0aa>) and "GPRS/RingOnIncomingData" (<groid>) are available only for modules supporting GPRS. Examples EXAMPLE 1 Usage of "Audio/AMR": AT+CSCS="UCS2" Switch to UCS2 character set. OK AT^SCFG? Query all parameters. ... ^SCFG:"Audio/AMR","0065006E00610062006C00650064" ... OK AT+CSCS="GSM" OK AT^SCFG? ... ^SCFG:"Audio/AMR","enabled" AMR will be used for any operator. ... OK AT^SCFG="Audio/AMR","disabled" ^SCFG:"Audio/AMR","disabled" AMR is disabled for any operator. OK AT^SCFG="Audio/AMR","23405" MC55_ATC_V04.00 Confidential / Released Page 57 of 475 3/17/06 AMR is disabled for any operator, but enabled for operator "23405". ^SCFG:"Audio/AMR","23405" OK AT^SCFG="Audio/AMR","23203" ^SCFG:"Audio/AMR","23405","23203" AMR is disabled for any operator, but enabled for operators "23405" and "23203". OK AT^SCFG="Audio/AMR" ^SCFG:"Audio/AMR","23405","23203" OK Query parameter "Audio/AMR" EXAMPLE 2 Usage of "URC/Ringline" and "URC/Datamode/Ringline": AT+CSCS="GSM" OK AT^SCFG? ... ^SCFG:"URC/Datamode/Ringline","off" ^SCFG:"URC/Ringline","local" ... OK AT^SCFG="URC/Datamode/Ringline","on" ^SCFG:"URC/Datamode/Ringline","on" OK AT^SCFG="URC/Ringline","asc0" ^SCFG:"URC/Ringline","asc0" Query all parameters. While the TA-TE link is reserved URCs will be indicated by BREAK. URCs on this interface will be indicated by Ring line associated to the interface (e.g. RING0 for ASC0). While the TA-TE link is reserved URCs will be indicated by an activated "local" Ring line. URCs on this interface will be indicated by an activated RING0 no matter whether or not the TA-TE link is reserved. OK AT^SCFG="URC/Datamode/Ringline","off" ^SCFG:"URC/Datamode/Ringline","off" OK AT^SCFG="URC/Ringline" Switch to GSM character set. URCs on this interface will be indicated by an activated RING0 if the TA-TE link is not reserved and by BREAK if the TA-TE link is reserved. Disable any Ring line indication for URCs on this interface. ^SCFG:"URC/Ringline","off" OK MC55_ATC_V04.00 Confidential / Released Page 58 of 475 3/17/06 2.14 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 MC55. 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 SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <CallMode>(num) Call setup response mode Applies only to voice calls. 0 Set compatibility to Siemens mobile phones. 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. 1(&F) 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 indicated. <CmgwMode>(num) 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. ME will return +CMS ERROR: <err> when writing or sending of short messages fails. 1(&F) 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. MC55_ATC_V04.00 Confidential / Released Page 59 of 475 3/17/06 3. Status Control Commands The AT Commands described in this chapter allow the external application to obtain various status information from the MC55. 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 Information, 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>1[, <indValue>2]" URCs. <indDescr> refers to the name of a "+CIEV" indicator and <indValue> 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. 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 GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Unsolicited Result Code +CIEV: <indDescr>, <indValue>1[, <indValue>2] A value of an indicator has changed. MC55_ATC_V04.00 Confidential / Released Page 60 of 475 3/17/06 Parameter Description <mode>(num) 0(&F) 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" URCsin 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. 3 Forward "+CIEV" and "^SLCC" URCs directly to the TE. If MC55 is in online data mode, URCs are signaled via sending BREAK (100ms) 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>(num) 0(&F) Keypad event reporting is not supported by MC55. <disp>(num) 0(&F) Display event reporting is not supported by MC55. <ind>(num) 0(&F) Disable indicator event reporting. 2 Enable indicator event reporting. <bfr>(num) 0(&F) TA buffer of URCs defined within this command is cleared when <mode> 1..3 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. Note • 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. MC55_ATC_V04.00 Confidential / Released Page 61 of 475 3/17/06 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 messages, 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 automatically 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 GSM 07.07 ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <indValue>(num) Integer type value, which shall be in range of corresponding <indDescr> MC55_ATC_V04.00 Confidential / Released Page 62 of 475 3/17/06 <indDescr>(str) String values and their <indValue> ranges. More indications are available via AT^SIND. Therefore use of AT^SIND for control of all indications is recommended. 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 battery is connected. Also refer to AT^SBC. "signal" Signal quality (0..7) or (99) if not measurable The indicated value is the bit error rate of the signal received. Bit errors are estimated values. See also AT+CSQ. "service" Service availability (0-1) 0: Not registered to any network 1: Registered to home network or, if "roam"=1 then registered to another network "sounder" Sounder activity (0-1) 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 output 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. "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" 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. "roam" Roaming indicator (0-1) 0: Registered to home network or not registered 1: Registered to other network "smsfull" A short message memory storage in the MT has become full (1) or memory locations are available (0), i.e. range is (0-1) "rssi" Received signal (field) strength (0..5) or (99) if not measurable 0: signal strength <= -112 dbm 1-4: signal strength in 15 dbm steps 5: signal strength >= -51 dbm 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. <mode>(num) 0 Indicator is deregistered. The indicator will not be presented as "+CIEV" URC, but can be queried with AT+CIND?. [1](&F)(P) Indicator is registered, indicator event report allowed. MC55_ATC_V04.00 Confidential / Released Page 63 of 475 3/17/06 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 current 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 established, 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,99,1,0,0,0,0,0 OK AT+CMER=2,0,0,2 OK +CIEV: battchg,5 +CIEV: signal,99 +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 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. EXAMPLE 2 Deactivation of indicator "sounder" via AT+CIND AT+CIND? +CIND: 5,99,1,0,1,0,0,0,4 OK AT+CIND=,,,0 OK Query the current status of indicators. To deactivate indicator "sounder" (= fourth item in list of indicators). EXAMPLE 3 Deactivation of indicator "sounder" via AT^SIND AT^SIND="sounder",0 ^SIND: sounder,0,0 OK MC55_ATC_V04.00 Confidential / Released To deactivate indicator "sounder". Page 64 of 475 3/17/06 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 indicator 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>] ... 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 SIEMENS ! MC55_ATC_V04.00 Confidential / Released ASC0 ASC1 % Page 65 of 475 % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! 3/17/06 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 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. URC 3 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 4 Format of the "nitz" indicator: +CIEV: <indDescr>, <nitzUT>, <nitzTZ>, <nitzDST> Parameter Description <indDescr>(str) String values and their <indValue> ranges. All indicators supported by AT+CIND are accessible with this command, too. A detailed description of these indicators can be found there. The following indicators are accessible via AT^SIND only: "audio" Activity of the built-in audio unit. 0 Audio unit not active. 1 Value 1 means for example: Outgoing voice call: Indicator appears when dialing starts. Incoming voice call: Indicator appears prior to the RING result code. "vmwait1" Voice Message Waiting Indication for line 1 0 The value 0 notifies that no new voice message is available, and is provided 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. After the subscriber has retrieved all voice messages the service center automatically 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 MC55 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 command AT^SIND? nor the write command AT^SIND=<mode>,2 display the number of waiting messages. MC55_ATC_V04.00 Confidential / Released Page 66 of 475 3/17/06 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 MC55 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 (EFAD) in the SIM, as defined in 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 EFAD setting disables the ciphering indicator feature read command always 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 recommended solution is to use a dedicated channel for all status signalling via URCs. "eons" MC55_ATC_V04.00 Confidential / Released • If an unciphered mobile originated SMS is performed, AT^SIND "ciphcall" URCs on the same serial channel will be issued after the related "OK" and indicate the ciphering state at this time. Because the SMS is already sent at this time, two URCs will be issued on this channel, but both are indicating that ciphering is enabled. • If an unciphered mobile originated data call is performed, AT^SIND "ciphcall" 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. Enhanced Operator Name String (EONS) Indication The Enhanced Operator Name String indicator feature allows the MC55 to output 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 network 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 information 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: EFSST (SIM Service Table) - describes which features are active. EFOPL (Operator PLMN List) - contains the PLMN identification and location ID together with the index of the corresponding PNN record EFPNN (PLMN Network Name) - contains the full and short form version of the 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: Page 67 of 475 3/17/06 EFONString (Operator Name String) - contains the name of the PLMN operator who issued the SIM. EFOPShort (Operator Name Short form) - contains a short form of the name of the PLMN operator who issued the SIM. "nitz" Network Identity and Time Zone indication This indicator shows the time relevant information elements of an MM Information (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 saving 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 continuation of UT. NITZ values are lost when the module detaches from network. Also when a manual network selection fails and the module automatically falls back to the previous network the NITZ values cannot be recalled. Nevertheless an indicated time zone is valid until a new MMI/GMMI will trigger another NITZ indication. <indValue>(num) 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 [23]. 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 priority). 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 Handset Specification (CPHS) [24] (alphanumeric format, can contain up to 16 characters). 3 Name information received by the NITZ service long and short form (alphanumeric format, can contain up to 16 characters). The short form will be displayed only if EFOPShort from CPHS is available. MC55_ATC_V04.00 Confidential / Released Page 68 of 475 3/17/06 4 Any operator name stored internal to the ME (alphanumeric format, can contain up to 16 characters). 5 Broadcast MCC-MNC (numeric format which consists of a 3-digit country code plus a 2- or 3-digit network code). If the type is 2, 4 or 5, AT+COPS with the appropriate <mode> displays the same operator name. <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. 2 • 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 supported by AT+CIND is <mode>=1, while, as stated above, indicators defined by AT^SIND only are set to <mode>=0. Query the registration status and the current value of a single indicator type. <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>. <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 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.) +CIEV: battchg,5 +CIEV: signal,99 +CIEV: service,1 MC55_ATC_V04.00 Confidential / Released Page 69 of 475 3/17/06 +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,99 +CIEV: rssi,4 MC55_ATC_V04.00 Confidential / Released You make a call. You hang up. Page 70 of 475 3/17/06 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 subclauses and the relevant GSM specifications. The first parameter <locationID> serves to locate the other two parameters. Depending on the failure or release cause either <reason> or <ssRelease> are applicable, i.e. if <reason> ≠ 0, then <ssRelease> = 0. Vice versa, if <reason> = 0, then <ssRelease> may be ≠ 0. AT+CEER is not available for data calls, please use ATS18=1 instead. In case of loosed net coverage, MC55 will disconnect the call but no network release cause is available and the default output will still be given out. 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 GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <locationID>(num) Location ID as number code. Location IDs are listed in Section 3.4.1, Cause Location ID for the extended error report. Each ID is related with another table that contains a list of <reason>s or <ssRelease>s. <reason>(num) Reason for last call release as number code. The number codes are listed in several tables, sorted by different categories in the following subclauses. The tables can be found proceeding from the Location ID given in Section 3.4.1, Cause Location ID for the extended error report. <ssRelease>(num) Release cause for last Supplementary Service call (listed in Section 3.4.9, GSM Release cause for Supplementary Service Call) or last call related use of a Supplementary Service (listed in Section 3.4.10, SIEMENS release cause for Call-related Supplementary Services (CRSS)). MC55_ATC_V04.00 Confidential / Released Page 71 of 475 3/17/06 Examples EXAMPLE 1 ATD"01751223344"; NO CARRIER AT+CEER +CEER: 8,21,0 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.6, where 21 = "Call rejected". 0 = "No error" refers to parameter <ssRelease> that is not applicable. 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 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 OK first time. 0 = "No error" refers to parameter <reason> that is not applicable. 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) 7 SIEMENS cause for L3 Mobility Management via MMR-SAP 8 GSM cause for L3 Call Control (GSM 04.08 10.5.4.11 and annex H) 9 SIEMENS cause for L3 Call Control 11 SIEMENS cause for L3 Advice of Charge Entity 12 GSM cause for L3 SMS CP Entity 13 SIEMENS cause for L3 SMS CP Entity 14 GSM cause for L3 SMS RL Entity 15 SIEMENS cause for L3 SMS RL Entity 16 GSM cause for L3 SMS TL Entity 17 SIEMENS cause for L3 SMS TL Entity 18 SIEMENS cause for DSM Entity 21 GSM cause for L3 Call-related Supplementary Services 22 SIEMENS cause for L3 Call-related Supplementary Services 32 SIEMENS cause for Supplementary Services Entity 33 SIEMENS cause for Supplementary Services Manager 34 Network cause for Supplementary Services (GSM 04.08 10.5.4.11 and annex H) MC55_ATC_V04.00 Confidential / Released Page 72 of 475 3/17/06 ID Description 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) 51 SIEMENS cause for Session Management 127 SIEMENS cause for protocol module or other local cause 128 Supplementary Services general problem (GSM 04.80 3.6.7) 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 242 SIEMENS cause for Link Management 243 SIEMENS cause for PPP/IP-Stack 3.4.2 GSM release cause for L3 Radio Resource (RR) 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.3 SIEMENS release cause for L3 Radio Resource (RR) Number Description 1 Racchs not answered 2 Racchs rejected MC55_ATC_V04.00 Confidential / Released Page 73 of 475 3/17/06 Number Description 3 Access class of the SIM is barred by the network provider 4 SABM failure 5 Radio link counter expiry or PerformAbnormalRelease 6 Confirm ABORT of the MM 7 Respond to DEACT REQ 8 Loss of coverage 9 Reestablishment not possible 3.4.4 Number GSM release cause for Mobility Management (MM) or Session Management (SM) 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 36 Regular PDP context deactivation 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 111 Protocol error, unspecified MC55_ATC_V04.00 Confidential / Released Page 74 of 475 3/17/06 Number Description 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 3.4.5 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 3.4.6 GSM release cause for L3 Call Control (CC) Number Description 0 No error 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 19 User alerting, no answer 21 Call rejected 22 Number changed MC55_ATC_V04.00 Confidential / Released Page 75 of 475 3/17/06 Number Description 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 100 Conditional information element error 101 Message not compatible with protocol 102 Recovery on timer expiry MC55_ATC_V04.00 Confidential / Released Page 76 of 475 3/17/06 Number Description 111 Protocol error, unspecified Interworking class 127 3.4.7 Interworking, unspecified SIEMENS release cause for L3 Call Control (CC) Number Description 1 Call dropped 2 Service not available 3 Hold procedure not available 4 Temporary no service, previous procedure not yet finished 5 No speech service available 6 Call reestablishment procedure active 7 Mobile received a release (complete) message during a modify procedure (modify reject) 8 Call clearing, because loss of radio connection, if no reestablishment is allowed (call not active) 10 Number not included in FDN list Notifications 300 3.4.8 Called party barred incoming call SIEMENS release cause for L3 Advice of Charge (AOC) Number Description 1 SIM data not available 2 SIM does not support AOC 3 SIM data access error 4 ACM limit almost reached ACM range overflow 5 ACM range overflow 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 MC55_ATC_V04.00 Confidential / Released Page 77 of 475 3/17/06 Number Description 16 IllegalSSOperation 17 SSErrorStatus 18 SSNotAvailable 19 SSSubscriptionViolation 20 SSIncompatibility 21 FacilityNotSupported 27 AbsentSubscriber 29 ShortTermDenial 30 LongTermDenial 34 SystemFailure 35 DataMissing 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 MC55_ATC_V04.00 Confidential / Released Page 78 of 475 3/17/06 3.4.10 SIEMENS release cause for Call-related Supplementary Services (CRSS) Number Description 0 ECT procedure failed (timer expired) 1 Call has been cleared without receiving an answer to ECT request 2 Initial conditions not fulfilled (one active, one held call) 3 Received "return error" 4 Call has been cleared without receiving an answer to CCBS request 5 Initial conditions for CCBS not fulfilled (Idle CRSS) Causes related to nature of request 25 LLC or SNDCP failure 26 Insufficient resources 27 Unknown or missing access point name 28 Unknown PDP address or PDP type 29 User authentification failed 30 Activation rejected by GGSN 31 Activation rejected, unspecified 32 Service option not supported 33 Requested service option not subscribed 34 Service option temporarily out of order 35 NSAPI already used 36 Regular PDP context deactivation 37 QoS not accepted 38 Network failure 39 Reactivation requested 40 Feature not supported Causes related to invalid messages 81 Invalid transaction identifier value 95 Semantically incorrect message 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 100 Conditional information element error 101 Message not compatible with protocol 111 Protocol error, unspecified MC55_ATC_V04.00 Confidential / Released Page 79 of 475 3/17/06 3.4.11 SIEMENS release cause for Session Management (SM) Number Description 3 The MS has not got any answer to the ACTIVATE PDP CONTEXT request message sent five times to the network 4 A MT PDP context which is active or in the activation process is deactivated because another MT PDP context with the same TI is requested by the network to be activated 5 A MT PDP context which is active or in the activation process is deactivated because another MT PDP context with the same TI is requested by the network to be activated. The activation request is rejected by the SM sending the cause 'insufficient resources' to the network because the SM was not able to perform the necessary comparisons for a static PDP address collision detection. 6 A MT PDP context which is active or in the activation process is deactivated because another MT PDP context with the same TI is requested by the network to be activated. As a static PDP address collision with an MO activating PDP context has been detected by the SM the SM discards the activation request 7 A MT PDP context request has been indicated but could not be processed in time. The activation request is rejected by the SM sending the cause 'insufficient resources' to the network. 3.4.12 GSM cause for L3 Protocol module or other local cause Number Description 2 No detailed cause 3.4.13 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 255 Undefined 3.4.14 SIEMENS release cause for PPP/IP-Stack Number Description 0 Regular call deactivation 1 LCP stopped 255 Undefined MC55_ATC_V04.00 Confidential / Released Page 80 of 475 3/17/06 3.5 ATS18 Extended call release report ATS18 controls the presentation of extended call release reports for circuit switched fax and data calls. Extended call release reports related to voice calls are controlled via AT+CEER. The call release report is presented in numeric format and shows as follows: +CAUSE: <locationID>:<reason> If enabled the message will be reported every time a fax or data call is released or fails to be established. Syntax Read Command ATS18? Response(s) <n> OK Write Command ATS18=<n> Response(s) OK ERROR Reference(s) V.250 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Parameter Description <n>(num)(&W)(&V) An odd number enables the presentation of the extended call release report. Any even number disables this feature. 0(&F)...255 <locationID>(num) Location ID as number code, see also <locationID> of AT+CEER. Location IDs are listed in Section 3.4.1, Cause Location ID for the extended error report. Each ID is related to another table that contains a list of <reason>s. <reason>(num) Reason for last call release as number code (see also <reason> of AT+CEER). <reason> numbers and the associated descriptions are listed in several tables, sorted by different categories at AT+CEER. The tables can be found proceeding from the Location IDs listed in Section 3.4.1, Cause Location ID for the extended error report. MC55_ATC_V04.00 Confidential / Released Page 81 of 475 3/17/06 Examples EXAMPLE 1 ATS18=1 OK ATD03012345678 +CAUSE: 8:17 BUSY Enables the presentation of extended call release reports. Now, a mobile originated data call fails. An extended error report is output, followed by the result code BUSY. The Location ID 8 stated in Section 3.4.1 points to Section 3.4.6, with 17 = "User busy". EXAMPLE 2 ATS18=1 OK ATD03012345678 CONNECT 9600/RLP Hello,.... +++ +CAUSE: 8:16 NO CARRIER MC55_ATC_V04.00 Confidential / Released Enables the presentation of extended call release reports. Now, a mobile originated data call is set up. Call ends after remote party hung up. Normal call release is reported, followed by the result code NO CARRIER. The Location ID 8 stated in Section 3.4.1 points to Section 3.4.6, with 16 = "Normal call clearing". Page 82 of 475 3/17/06 3.6 AT+CPAS Mobile equipment activity status The AT+CPAS execute command indicates the activity status of the ME. Syntax Test Command AT+CPAS=? Response(s) +CPAS: (list of supported<pas>s) OK Exec Command AT+CPAS Response(s) +CPAS: <pas> OK Reference(s) PIN GSM 07.07 ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <pas>(num) 0 Ready 3 Incoming call (ringing) 4 Call in progress or call hold MC55_ATC_V04.00 Confidential / Released Page 83 of 475 3/17/06 3.7 AT+WS46 Select wireless network Syntax Test Command AT+WS46=? Response(s) +WS46: (list of supported<n>s) OK Read Command AT+WS46? Response(s) <n> OK Write Command AT+WS46=[<n>] Response(s) OK ERROR +CME ERROR Reference(s) PIN GSM 07.07 ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <n>(num) 12 MC55_ATC_V04.00 Confidential / Released GSM digital cellular Page 84 of 475 3/17/06 4. Serial Interface Control Commands The AT Commands described in this chapter allow the external application to determine various settings related to the MC55's serial interface. 4.1 AT\Q Flow control Syntax Exec Command AT\Q[<n>] Response(s) OK If RTS/CTS flow control is not supported by interface and <n> is 2 or 3: ERROR Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 § § MUX3 Charge § ! ! Last ! Parameter Description <n>(num)(&W)(&V) [0](&F) Disable flow control 1 XON/XOFF software flow control 2 Only CTS by DCE (TA) 3 RTS/CTS hardware flow control Recommended for the following procedures: incoming or outgoing data calls, fax calls, MUX mode. Often, the initialization routine of Fax programs includes enabling RTS/CTS handshake, eliminating the need to issue AT\Q3 once again. Notes • When using XON/XOFF flow control (AT\Q1) in online mode, +++ should not be used while the data transmission is paused with XOFF. Before entering the command mode with +++ the paused transmission should be resumed using the XON character. • For compatibility reasons, the AT\Q command can be used in Multiplex mode, though the settings will not take effect. However, be aware that whenever you use the AT\Q write command in Multiplex mode and then save the current configuration to the user profile with AT&W, the changed AT\Q setting will become active after restart. MC55_ATC_V04.00 Confidential / Released Page 85 of 475 3/17/06 4.2 AT&C Set Data Carrier Detect (DCD) Line mode The AT&C command determines how the state of the DCD line (circuit 109) reflects the MC55's internal activity. Syntax Exec Command AT&C[<value>] Response(s) OK Reference(s) PIN V.250 , SIEMENS ! ASC0 ASC1 % ! MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <value>(num)(&W)(&V) [0] (&F) DCD line shall always be on. 1 DCD line shall be on only when data carrier signal is present. 2 DCD line shall be on when one or more Internet services defined on the related serial channel are in state "Connecting" or "Up" as described below. For details on the various service states refer to AT^SISI, parameter <srvState> or AT^SISO, parameter <srvState>. MC55_ATC_V04.00 Confidential / Released • SOCKET, HTTP, SMTP, POP3: <srvState>="Connnecting" or "Up" • FTP: DCD shall be on when data channel is connected, i.e. <srvState>="Up" Page 86 of 475 DCD shall be on when 3/17/06 4.3 AT&D Set circuit Data Terminal Ready (DTR) function mode The AT&D determines how the TA responds when circuit 108/2 (DTR) is changed from ON to OFF during data mode. Syntax Exec Command AT&D[<value>] Response(s) OK Reference(s) V.250 PIN ASC0 ASC1 ! % § MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <value>(num)(&W)(&V) [0] TA ignores status of DTR. 1 ON->OFF on DTR: Change to command mode while retaining the connected call. 2(&F) ON->OFF on DTR: Disconnect data call, change to command mode. During state DTR = OFF auto-answer is off. MC55_ATC_V04.00 Confidential / Released Page 87 of 475 3/17/06 4.4 AT&S Set circuit Data Set Ready (DSR) function mode The AT&S command determines how the TA sets circuit 107 (DSR) depending on the communication state of the TA interfacing TE. Syntax Exec Command AT&S[<value>] Response(s) OK Reference(s) V.250 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <value>(num)(&W)(&V) [0](&F) DSR line is always ON 1 TA in command mode: DSR is OFF. TA in data mode: DSR is ON. MC55_ATC_V04.00 Confidential / Released Page 88 of 475 3/17/06 4.5 ATE Enable command echo The ATE command determines whether or not the TA echoes characters received from TE during command state. Syntax Exec Command ATE[<value>] Response(s) OK Reference(s) PIN V.250 ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <value>(num)(&W)(&V) [0] Echo mode off (&F) 1 Echo mode on Note • In case of using the command without parameter, <value> is set to 0. MC55_ATC_V04.00 Confidential / Released Page 89 of 475 3/17/06 4.6 AT+ILRR Set TE-TA local rate reporting The command AT+ILRR controls whether or not the intermediate result code "+ILRR" is transmitted from the TA to the TE while a connection is being set up. The result code indicates the local rate. It is issued before the final result code of the connection, e.g. CONNECT, is transmitted to the TE. Syntax Test Command AT+ILRR=? Response(s) +ILRR: (list of supported <value>s) OK Read Command AT+ILRR? Response(s) +ILRR: <value> OK Write Command AT+ILRR=<value> Response(s) OK ERROR +CME ERROR Reference(s) PIN V.250 % ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! Last ! ! Intermediate Result Code +ILRR: <rate> Indicates local port rate setting upon connection setup. Parameter Description <value>(num)(&W)(&V) 0(&F) Disables reporting of local port rate 1 Enables reporting of local port rate <rate>(num) Port rate setting upon connection setup (bps) 0 Autobauding (see Section 4.7.1, Autobauding). Not supported on ASC1. 300 600 1200 2400 4800 9600 14400 MC55_ATC_V04.00 Confidential / Released Page 90 of 475 3/17/06 19200 28800 38400 57600 115200 230400 MC55_ATC_V04.00 Confidential / Released Page 91 of 475 3/17/06 4.7 AT+IPR Set fixed local rate The command AT+IPR can be used to set or query the TE-TA interface bit rate. Syntax Test Command AT+IPR=? Response(s) +IPR: (list of supported auto-detectable <rate>s) , (list of supported fixed-only <rate>s) OK Read Command AT+IPR? Response(s) +IPR: <rate> OK Write Command AT+IPR=<rate> Response(s) OK ERROR +CME ERROR Reference(s) V.250 PIN ! ASC0 ASC1 % § MUX1 MUX2 § § MUX3 Charge § ! ! Last ! Command Description The test command returns the values of the supported automatically detectable bit rates and the values of the supported fixed bit rates. The read command returns the current bit rate of the interface. The write command specifies the bit rate to be used for the interface. When you set a fixed-rate, make sure that both TE (DTE) and TA (DCE) are configured to the same rate. When you select autobauding, the TA will automatically recognize the bit rate currently used by the TE. The setting is stored in the non-volatile memory and will be used whenever the engine is powered up again. However, in case of autobaud mode (AT+IPR=0) the detected TA bit rate will not be saved and, therefore, needs to be resynchronized after restarting the GSM engine (see Section 4.7.1, Autobauding). Parameter Description <rate>(num)(&V) bit rate per second (bps) 0 Activates autobauding. Not supported on ASC1. See Section 4.7.1, Autobauding for further details. 300 600 1200 2400 4800 9600 MC55_ATC_V04.00 Confidential / Released Page 92 of 475 3/17/06 14400 19200 28800 38400 57600 115200 230400 Notes • Delivery value for <rate> is autobauding enabled (AT+IPR=0) on ASC0 and 57600bps on ASC1. It will not be restored with AT&F. • The current setting of AT+IPR will be preserved when you download firmware (i.e. a firmware update does not restore the factory setting) or in the event of power failure. • Generally, AT+IPR should be used as a standalone command. If nethertheless combinations with other commands on the same command line cannot be avoided, there are several constraints to be considered: - Avoid combinations with the AT commands listed in Section 1.4.2, Combining AT commands on the same command line. - Take into account, that a pause of 100ms is required between the response to the last command (e.g. OK) and the next command. - When you enter AT+IPR=0, autobauding will be activated after the response to the last command is received. - When local echo is active (ATE1) and you enter AT+IPR=x with other commands you may encounter the following problem: if switching to the new bit rate takes effect while a response is being transmitted, the last bytes may be sent with the new bit rate and thus, not properly transmitted. The following commands will be correctly sent at the new bit rate. • In order to account for greater amounts of data it is recommended to choose a minimum bit rate of 2400 bps. If the ME shall be operated in Multiplex mode we suggest a minimum bit rate of 4800bps. • In Multiplex mode, the write command AT+IPR=<rate> will not change the bit rate currently used, but the new bit rate will be stored and becomes active, when the module is restarted. • A selected bit rate takes effect after the write commands returns OK. 4.7.1 Autobauding To take advantage of autobaud mode specific attention must be paid to the following requirements: • Synchronization between TE and TA Ensure that TE and TA are correctly synchronized and the bit rate used by the TE is detected by the TA. To allow the bit rate to be synchronized simply use an "AT" or "at" string. This is necessary - after you have activated autobauding - when you start up the GSM engine while autobauding is enabled. It is recommended to wait 3 to 5 seconds before sending the first AT character. Otherwise undefined characters might be returned. If you want to use autobauding and autoanswer at the same time, you can easily enable the TE-TA synchronization, when you activate autobauding first and then configure the autoanswer mode (ATS0 ≠ 0). • Restrictions on autobauding operation - The serial interface shall be used with 8 data bits, no parity and 1 stop bit (factory setting), e.g. 2 stop bits are not supported for autobaud mode. - The command A/ cannot be used. - Only the strings "AT" or "at" can be detected (neither "At" nor "aT"). - URCs that may be issued before the ME detects a new bit rate (by receiving the first AT character) will be sent at the previously detected bit rate or, after ME restart, at 57600 bps. MC55_ATC_V04.00 Confidential / Released Page 93 of 475 3/17/06 - • It is not recommended to switch to autobauding from a bit rate that cannot be detected by the autobaud mechanism (e.g. 300 bps). Responses to AT+IPR=0 and any commands on the same line might be corrupted. Autobauding and bit rate after restart The most recently detected bit rate is stored when the ME is powered down (with AT^SMSO). Therefore, each time the module is restarted the correct bit rate must be found as described above. Unless the bit rate is determined, the following constraints apply: - An incoming CSD call or a network initiated GPRS request cannot be accepted. This must be taken into account when autobauding and autoanswer mode (ATS0 ≠ 0) are enabled at the same time, escpecially if SIM PIN 1 authentication is done automatically and the setting ATS0 ≠ 0 is stored to the user profile with AT&W. - Until the bit rate is found, URCs generated after restart will be output at 57600 bps. This applies only to user defined URCs, such as "+CREG", "CCWA", "^SCKS" etc. The URCs "^SYSSTART", "^SYSSTART CHARGE-ONLY MODE" and "^SYSSTART ALARM MODE" will not be indicated when autobauding is enabled. Note: To avoid any problems caused by undetermined bit rates in the direction from TA to TE we strongly recommend to configure a fixed bit rate rather than autobauding. • Autobauding and multiplex mode If autobauding is active you cannot switch to multiplex mode (see AT+CMUX). MC55_ATC_V04.00 Confidential / Released Page 94 of 475 3/17/06 4.8 AT+CMUX Enter multiplex mode All information provided in this section applies to the ASC0 interface only. The second interface ASC1 has no support of Multiplex mode. Multiplex mode according to the ETSI TS 101 669 and GSM 07.10 enables one physical serial asynchronous interface to be partitioned into three virtual channels. This allows you to take advantage of up to 3 simultaneous sessions running on the serial interface. For example, you can send or receive data or make a call on the first channel, while the other two channels are free to control the module with AT commands. The MC55 module incorporates an internal multiplexer and thus integrates all the functions needed to implement full-featured multiplex solutions. For the application on top, customers have the flexibility to create their own multiplex programs conforming to the multiplexer protocol. To help system integrators save the time and expense of designing multiplexer applications, SIEMENS AG offers WinMUX2k, a ready-to-use multiplex driver for Windows 2000 and Windows XP. Another approach is to develop customized solutions based on the sources of the WinMux2k driver. Refer to [5] which provides a detailed description of the multiplex architecture and step-by-step instructions of how to install and configure the multiplex mode. The WinMUX2k driver and its source files can be supplied on request. Please contact your local distributor to obtain the latest installation software and user's guide. Syntax Test Command AT+CMUX=? Response(s) +CMUX: (list of supported<mode>s) OK Read Command AT+CMUX? Response(s) +CMUX: <mode> OK ERROR +CME ERROR: <err> Write Command AT+CMUX=<mode> Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN GSM 07.07, GSM 07.10 ! ASC0 ASC1 % MUX1 MUX2 ! ! ! MUX3 Charge ! ! ! Last % Parameter Description <mode>(num) Multiplexer transparency mechanism 0 Basic option <subset>(num) Subparameters defined in GSM07.07 are adjusted for control and logical channels as follows 0 MC55_ATC_V04.00 Confidential / Released UIH frames used only (control channel) Page 95 of 475 3/17/06 Notes • The write command is used to enter the multiplex mode. The setup of the logical channels is initiated by the TE, i.e. the TE acts as initiator. This means that the TE shall ensure that logical channels are established before any further actions on the channels can be started. • There is a timeout of five seconds, if the multiplexer protocol is enabled and no multiplexer control channel is established. The GSM engine returns to AT command mode. • The parameter maximum frame size (N1) of AT+CMUX in GSM 07.10 is fixed to 98 bytes and cannot be changed. All other parameters are not available. 4.8.1 Restrictions on Multiplex mode When the serial interface ASC0 is in multiplex mode, data and fax calls can only be set up on logical channel 1. Due to this restriction, AT commands have a different behavior on channels 2+3 compared to channel 1. Several commands are not available, others return different responses. This section summarizes the concerned commands. For general rules and restrictions to be considered in Multiplex mode please refer to [5]. Table 4.1: Availability of AT Commands on Virtual Channels Command Behavior on channel 1 Behavior on channel 2+3 2) not usable, but see note 2) +++ not usable, but see note AT+CBST as described not usable AT+CRLP as described not usable AT+CG... (GPRS commands) as described see note 3) AT+F... (Fax commands) as described not usable AT&S as described not usable ATA as described no Data Calls ATD as described no Data Calls ATDI as described not usable ATL as described not usable ATM as described not usable as described not usable 1) as described not usable 1) as described not usable 1) ATO ATS6 ATS7 ATS8 ATS10 ATS18 as described not usable 1) as described not usable 1) as described not usable 1) Siemens GSM engines support the registers S0 - S29. You can change S0,S3,S4,S5,S6,S7,S8,S10 and S18 using the related ATSn commands (see starting from ATS0). The other registers are read-only and for internal use only! 2) The applicability of the +++ escape sequence depends on the customer's external application based on the Mulitplexer Protocol. Recommendations for implementing an appropriate modem status command (MSC) are provided in [5], Section "Escape Sequence". 3) PDP contexts can be defined on any channel, but are visible and usable only on the channel on which they are defined (thus it is not possible to define a context on channel 2 and activate it on channel 3). GPRS connections can be established on two channels at a time. MC55_ATC_V04.00 Confidential / Released Page 96 of 475 3/17/06 Table 4.2: Summary of AT commands with Different Behavior in Multiplex Mode Command Description AT\Q It is recommended to use hardware flow control (AT\Q3). XON/XOFF flow control (AT\Q1) is not supported in Multiplex mode. See note regarding AT\Qn settings stored with AT&W if Multiplex mode is active. AT&V Different default configurations on channels 1, 2 and 3. AT&W Different user profiles can be stored on each channel. AT+IPR Before you start Multiplex mode, it is recommended to set the ME to 57600 bps (minimum should be 4800 bps). For GPRS we suggest to use 115200 bps or 230400 bps. In Multiplex mode, the write command AT+IPR=<rate> will not change the bit rate currently used, but the new bit rate will be stored and becomes active, when the module is restarted. AT+IPR=0 Multiplex mode cannot be activated while autobauding is enabled. AT+CALA On each channel an individual <text> message can be stored. but only one time setting applies to all channels. This means an alarm <time> set on one of the channels overwrites the time setting on all remaining channels. Therefore, the total number of alarm events returned by the read command AT+CALA? will always be <n>=0, no matter whether individual text messages are stored. When the alarm is timed out and executed the ME sends the URC only on the channel where the most recent alarm setting was made. The alarm time will be reset to "00/01/01,00:00:00" on all channels. AT+CMEE Presentation mode can be separately configured for each channel. AT+CNMA If Multiplex mode is activated the +CNMI parameter will be set to zero on all channels, if one channel fails to acknowledge an incoming message within the required time. AT+CNMI Phase 2+ parameters can only be used on one channel. The parameter for <mt> and <ds> on the other channels have to be set to zero. If either a SM or a Status Report is not acknowledged, all +CNMI parameter will be set to zero on all channels. AT+CFUN 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 [5], Section "Power saving control (PSC)". AT+CPMS Parameter <mem3> will be the same on all instances, but the settings of <mem1> and <mem2> may vary on each instance. AT^SSDA If one instance is set to <da>=1 and <mt>=1, then all other instances must be configured for <mt>=0. MC55_ATC_V04.00 Confidential / Released Page 97 of 475 3/17/06 4.8.2 Second serial interface ASC1 The second serial interface ASC1 is intended as an auxiliary interface for applications which need multiple parallel access to the module (e.g. to query status information during a data call), but cannot use the GSM 07.10 multiplexing protocol. Therefore this interface offers limited functionality only. • • • • • • No DTR, DSR, DCD, RING signals. These hardware lines do not exist. As a result, AT commands controlling the behavior of these lines (AT&D, AT&C, AT&S) are not allowed and return ERROR. No presentation of ^SYSSTART URCs on ASC1. After restart or reset of the ME, either check that the URC has been sent on ASC0 or wait approximately 3 seconds before entering the first AT command on ASC1. No Autobauding. The hardware is not capable of automatically detecting the baudrate on this interface, so the AT command which selects autobauding (AT+IPR=0) is not allowed and returns ERROR. No CSD calls, so all related AT commands cannot be used and return ERROR. No fax calls, so all AT+F commands cannot be used and return ERROR. No GSM 07.10 Multiplexer. If issued on the second interface AT+CMUX=0 returns ERROR. ASC1 is disabled when the multiplexer is enabled on the first serial interface ASC0. Yet, both ASC1 and the multiplexer channel 2 are using the same parameters, and thus, the same user defined profile (if any). As a result, a user profile stored on multiplexer channel 2 takes effect on ASC1 after closing the multiplexer and starting up ASC1. Likewise, a user profile stored on ASC1 will be loaded on multiplexer channel 2. This may be a problem when ASC1 is not connected, but flow control (for example AT\Q1 or AT\Q3) is stored to the user profile on the multiplexer channel 2. In this case, flow control takes effect on ASC1, when the multiplexer is switched off. If then for example a large amount of URCs is generated, their transmission might be stopped due to the flow control. To avoid this problem we recommend that you do not activate flow control on multiplexer channel 2 when you set up a user profile with AT&W. MC55_ATC_V04.00 Confidential / Released Page 98 of 475 3/17/06 5. Security Commands The AT Commands described in this chapter allow the external application to determine various security related settings. 5.1 AT+CPIN PIN Authentication AT+CPIN controls network authentication of the MC55. The read command returns an alphanumeric string indicating whether or not network authentication is required. The write command allows the MC55 to store the entered password. This may be for example the SIM PIN1 to register to the GSM network, or the SIM PUK1 to replace a disabled SIM PIN1 with a new one, or the PH-SIM PIN if the client has taken precautions for preventing damage in the event of loss or theft etc. If no PIN1 request is pending (for example if PIN1 authentication has been done and the same PIN1 is entered again) MC55 responds "+CME ERROR: operation not allowed"; no further action is required. Each time a password is entered with AT+CPIN the module starts reading data from the SIM. The duration of reading varies with the SIM card. This may cause a delay of several seconds before all commands which need access to SIM data are effective. See Section 20.1, Restricted access to SIM data after SIM PIN authentication for further detail. Syntax Test Command AT+CPIN=? Response(s) OK Read Command AT+CPIN? Response(s) +CPIN: <code> OK ERROR +CME ERROR: <err> Write Command AT+CPIN=<pin>[, <new pin>] Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN GSM 07.07 ! MC55_ATC_V04.00 Confidential / Released ASC0 ASC1 % Page 99 of 475 % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! 3/17/06 Parameter Description <pin>(str) Password (string type), usually SIM PIN1. If the requested password was a PUK, such as SIM PUK1 or PH-FSIM PUK or another password, then <pin> must be followed by <new pin>. <new pin>(text) If the requested code was a PUK: specify a new password or restore the former disabled password. See Section 5.1.1, What to do if PIN or password authentication fails? for more information about when you may need to enter the PUK. <code>(text) SIM PIN authentication READY PIN has already been entered. No further entry needed. SIM PIN ME is waiting for SIM PIN1. SIM PUK ME is waiting for SIM PUK1 if PIN1 was disabled after three failed attempts to enter PIN1. SIM PIN2 ME is waiting for PIN2. This is only applicable when an attempt to access a PIN2 related feature was acknowledged with +CME ERROR: 17 ("SIM PIN2 required"), for example when the client attempts to edit the FD phonebook). In this case the read command AT+CPIN? also prompts for SIM PIN2. Normally, the AT+CPIN2 command is intended for SIM PIN2. SIM PUK2 ME is waiting for PUK2 to unblock a disabled PIN2. As above, this is only necessary when the preceding command was acknowledged with +CME ERROR: 18 ("SIM PUK2 required") and only if the read command AT+CPIN? also prompts for SIM PUK2. Normally, the AT+CPIN2 command is intended for SIM PUK2. Phone security locks set by client or factory PH-SIM PIN ME is waiting for phone-to-SIM card password if "PS" lock is active and the client inserts other SIM card than the one used for the lock. ("PS" lock is also referred to as phone or antitheft lock). PH-SIM PUK ME is waiting for Master Phone Code, if the above "PS" lock password was incorrectly entered three times. PH-FSIM PIN ME is waiting for phone-to-very-first-SIM card. Necessary when "PF" lock was set. When powered up the first time, ME locks itself to the first SIM card put into the card holder. As a result, operation of the mobile is restricted to this one SIM card (unless the PH-FSIM PUK is used as described below). PH-FSIM PUK ME is waiting for phone-to-very-first-SIM card unblocking password to be given. Necessary when "PF" lock is active and other than first SIM card is inserted. PH-NET PUK ME is waiting for network personalisation unblocking password PH-NS PIN ME is waiting for network subset personalisation password PH-NS PUK ME is waiting for network subset unblocking password PH-SP PIN ME is waiting for service provider personalisation password PH-SP PUK ME is waiting for service provider personalisation unblocking password PH-C PIN ME is waiting for corporate personalisation password PH-C PUK ME is waiting for corprorate personalisation un-blocking password MC55_ATC_V04.00 Confidential / Released Page 100 of 475 3/17/06 Notes • Successful PIN authentication only confirms that the entered PIN was recognized and correct. The output of the result code OK does not necessarily imply that the mobile is registered to the desired network. Typical example: PIN was entered and accepted with OK, but the ME fails to register to the network. This may be due to missing network coverage, denied network access with currently used SIM card, no valid roaming agreement between home network and currently available operators etc. MC55 offers various options to verify the present status of network registration: For example, the AT+COPS command indicates the currently used network. With AT+CREG you can also check the current status and activate an unsolicited result code which appears whenever the status of the network registration changes (e.g. when the ME is powered up, or when the network cell changes). • <pin> and <new pin> can also be entered in quotation marks (e.g. "1234"). • To check the number of remaining attempts to enter the passwords use the AT^SPIC command. • See AT+CPWD and AT^SPWD for information on passwords. • See AT+CLCK and AT^SLCK for information on lock types. 5.1.1 What to do if PIN or password authentication fails? PIN1 / PUK1: After three failures to enter PIN 1, the SIM card is blocked (except for emergency calls). +CME ERROR: 12 will prompt the client to unblock the SIM card by entering the associated PUK (= PIN Unblocking Key / Personal Unblocking Key). After ten failed attempts to enter the PUK, the SIM card will be invalidated and no longer operable. In such a case, the card needs to be replaced. PIN1 consists of 4 to 8 digits, PUK1 is an 8-digit code only. To unblock a disabled PIN1 you have two options: • • You can enter AT+CPIN=PUK1,new PIN1. You can use the ATD command followed by the GSM code **05*PUK*newPIN*newPIN#;. PIN2 / PUK2: PIN2 prevents unauthorized access to the features listed in AT+CPIN2. The handling of PIN2 varies with the provider. PIN2 may either be a specific code supplied along with an associated PUK2, or a default code such as 0000. In either case, the client is advised to replace it with an individual code. Incorrect input of PUK2 will permanently block the additional features subject to PIN2 authentification, but usually has no effect on PIN1. PIN2 consists of 4 digits, PUK2 is an 8-digit code only. To unblock a disabled PIN2 you have two options: • • You can enter AT+CPIN2=PUK2,new PIN2. You can use the ATD command followed by the GSM code **052*PUK2*newPIN2*newPIN2#;. Phone lock: If the mobile was locked to a specific SIM card (= "PS" lock or phone lock), the PUK that came with the SIM card cannot be used to remove the lock. After three failed attempts to enter the correct password, ME returns +CPIN: PH-SIM PUK (= response to read command AT+CPIN?), i.e. it is now waiting for the Master Phone Code. This is an 8-digit device code associated to the IMEI number of the mobile which can only by obtained from the manufacturer or provider. When needed, contact Siemens AG and request the Master Phone Code of the specific module. There are two ways to enter the Master Phone code: • • You can enter AT+CPIN=Master Phone Code You can use the ATD command followed by the GSM code *#0003*Master Phone Code#;. Usually, the Master Phone Code will be supplied by mail or e-mail. If the received number is enclosed in the *# codes typically used for the ATD option, it is important to crop the preceding *#0003* characters and the appended #. Example: You may be given the string *#0003*12345678#. When prompted for the PH-SIM PUK simply enter 12345678. If incorrectly input, the Master Phone Code is governed by a specific timing algorithm: (n-1)*256 seconds (see table below). The timing should be considered by system integrators when designing an individual MMI. MC55_ATC_V04.00 Confidential / Released Page 101 of 475 3/17/06 Number of failed attempts Time to wait before next input is allowed 1st failed attempt No time to wait 2nd failed attempt 4 seconds 3rd failed attempt 3 * 256 seconds 4th failed attempt 4 * 256 seconds 5th failed attempt 5 * 256 seconds 6th failed attempt and so forth 6 * 256 seconds and so forth SIM locks: These are factory set locks, such as "PF", "PN", "PU", "PP", "PC". An 8-digit unlocking code is required to operate the mobile with a different SIM card, or to lift the lock. The code can only be obtained from the provider. Failure to enter the password is subject to the same timing algorithm as the Master Phone Code (see Table above). Call barring: Supported modes are "AO", "OI", "OX", "AI", "IR", "AB", "AG", "AC". If the call barring password is entered incorrectly three times, the client will need to contact the service provider to obtain a new one. Related sections: "+CME ERROR: <err>" values are specified at Section 2.11.1, CME/CMS Error Code Overview. For further instructions and examples see AT+CLCK, AT^SLCK, AT+CPWD and AT^SPWD. For a complete list of Star-Hash codes please refer Section 20.2, Star-Hash (*#) Network Commands. MC55_ATC_V04.00 Confidential / Released Page 102 of 475 3/17/06 5.2 AT+CPIN2 PIN2 Authentication AT+CPIN2 controls network authentication of the MC55. The read command returns an alphanumeric string indicating whether or not network authentication is required. The write command allows the MC55 to store the entered password. This may be for example the SIM PIN2 to benefit from the features listed below, or the SIM PUK2 to replace a disabled PIN2 with a new one. Note that PIN2 can only be entered if PIN1 authentication was done. If the MC55 is requesting SIM PUK2, use <pin> to enter the PUK2, followed by <new pin> to specify the new PIN2. Syntax Test Command AT+CPIN2=? Response(s) OK Read Command AT+CPIN2? Response(s) +CPIN2: <code> OK ERROR +CME ERROR: <err> Write Command AT+CPIN2=<pin>[, <new pin>] Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <pin>(str) Password (string type), usually SIM PIN2 or, if requested, SIM PUK2. <new pin>(str) If the requested code was SIM PUK2: new password (PIN2). See Section 5.1.1, What to do if PIN or password authentication fails? for more information about when you may need to enter the PUK. <code>(text) READY ME is not pending for any password. SIM PIN2 ME is waiting for SIM PIN2. This <code> is returned only when PIN2 authentication has not yet been done or has failed ("+CME ERROR:17"). SIM PUK2 ME is waiting for SIM PUK2. This <code> is returned only when PIN2 authentication has failed and ME is pending for SIM PUK2 (i.e. "+CME ERROR:18"). MC55_ATC_V04.00 Confidential / Released Page 103 of 475 3/17/06 Note • Functions accessible only after PIN2 authentication: AT+CACM: Accumulated call meter (ACM) reset or query AT+CAMM: Accumulated call meter maximum (ACMmax) set or query AT+CLCK: Facility lock to "FD" (Fixed dialing phonebook) AT^SLCK: Facility lock to "FD" (Fixed dialing phonebook) AT+CPWD: Change "P2"password AT^SPWD: Change "P2"password AT+CPUC: Price per unit and currency table AT+CPIN2: Enter SIM PIN2 or SIM PUK2 if requested. For example, SIM PIN2 will be needed when you attempt to edit the "FD" phonebook and ME returns "+CME Error 17" or "+CPIN: SIM PIN2". Once the required <pin> has been entered correctly, PIN2 authentication code changes to READY. After 300s, a repetition of the authentication process is required (PIN2 authentication code changes from READY to SIM PIN2). Examples EXAMPLE 1 Change PIN2 (where "0000" = old PIN2 and "8888" = new PIN2) AT+CPWD="P2","0000","8888" OK EXAMPLE 2 Unblock a disabled PIN2 AT+CPIN2? +CPIN2: SIM PUK2 OK AT+CPIN2=12345678,8888 PIN2 has been disabled, PUK2 must be entered to define a new PIN2 where "12345678" is the PUK2, and "8888" the new PIN2. EXAMPLE 3 Write into "FD" phonebook AT+CPBS="FD" OK AT+CPBW=2,"+493012345678",145,"Charly" +CME ERROR 17 AT+CPIN2=8888 OK AT+CPBW=2,"+493012345678",145,"Charly" OK MC55_ATC_V04.00 Confidential / Released access denied due to missing PIN2 authentication Page 104 of 475 3/17/06 5.3 AT^SPIC Display PIN counter The AT^SPIC command can be used to find out whether the ME is waiting for a password and, if so, how many attempts are left to enter the password. The execute command returns the number of attempts still available for entering the currently required password, for example the PIN, PUK, PH-SIM PUK etc. The read command AT^SPIC? indicates which password the number of attempts stated by the execute command actually refers to. Also, the write command may be used to query the counter for a specific password: It indicates the number of attempts still available for entering the password identified by <facility>, for example the PIN, PIN2, PH-SIM PIN etc. To check whether or not you need to enter a password use the read commands AT+CPIN?, AT+CPIN2? and AT^SPIC?. If the response to AT+CPIN? is "READY" the counter of the execute command AT^SPIC relates to PIN2. See last example. If the responses to AT+CPIN? and AT+CPIN2? both read "READY", no password is currently required, and the referrer of the execute command AT^SPIC is explicitly undefined. Syntax Test Command AT^SPIC=? Response(s) OK Read Command AT^SPIC? Response(s) ^SPIC: <code> OK Exec Command AT^SPIC Response(s) ^SPIC: <counter> OK Write Command AT^SPIC=<facility> Response(s) ^SPIC: <counter> OK Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <counter>(num) Number of attempts left to enter the currently required password. This number will be counted down after each failure. MC55_ATC_V04.00 Confidential / Released Page 105 of 475 3/17/06 <facility>(str) Password for which the corresponding PIN counter is to be displayed. "SC" SIM PIN or SIM PUK. If the SIM PIN has been deactivated after three failed attempts, the counter for SIM PUK will be returned instead. "PS" "Phone code" or "device code" (cf. AT+CLCK and AT+CPWD). If incorrectly entered three times, the Master Phone Code is required to lift the lock and the number of remaining attempts for the master phonecode will be returned. "P2" SIM PIN2 or SIM PUK2. If the SIM PIN2 has been deactivated after three failed attempts, the counter for SIM PUK2 will be returned instead. "PN" Network Personalisation <code>(text) Identification of the currently required password. SIM PIN ME is waiting for SIM PIN1. SIM PUK ME is waiting for SIM PUK1 if PIN1 was disabled after three failed attempts to enter PIN1. SIM PIN2 ME is waiting for PIN2, when the attempt to access PIN2 requiring features was acknowledged with +CME ERROR:17 (e.g. if the user attempts to edit the FD phonebook). SIM PUK2 ME is waiting for PUK2 to unblock a disabled PIN2. Necessary if preceding command was acknowledged with +CME ERROR:18. PH-SIM PIN ME is waiting for phone-to-SIM card password if ''PS'' lock is active and user inserts other SIM card than the one used for the lock. (''PS'' lock is also referred to as phone or antitheft lock). PH-SIM PUK ME is waiting for Master Phone Code, if the above ''PS'' lock password was incorrectly entered three times. PH-NET PUK ME is waiting for network personalisation unblocking password Notes • Whenever the required password changes, <counter> changes to reflect that change. Please refer to the examples below. • For passwords associated to the phone lock (''PS'' lock set by user or factory) or other factory set locks, such as ''PF'', ''PN'', ''PU'', ''PP'', ''PC'' the number of attempts is subject to a timing algorithm explained in AT+CPIN. If these passwords are incorrectly entered the counter first returns 3, 2 and 1 remaining attempt(s), but then gives the total number of attempts which amounts to 63 (see example below). • See also Chapters AT+CLCK, AT+CPIN, AT+CPIN2, AT+CPWD, AT^SLCK for further information on locks and passwords. Examples EXAMPLE 1 The user fails to provide a correct SIM PIN three times. The counter decreases each time. After the counter reaches zero, the SIM PUK is required. After each failure to enter a correct SIM PUK, the counter decreases. at+cpin? +CPIN: SIM PIN OK at^spic ^SPIC: 3 OK at+cpin=9999 +CME ERROR: incorrect password MC55_ATC_V04.00 Confidential / Released Currently required password is PIN1. 3 attempts left. Page 106 of 475 3/17/06 at^spic ^SPIC: 2 OK at+cpin=9999 +CME ERROR: incorrect password OK at^spic ^SPIC: 1 OK at+cpin=9999 +CME ERROR: incorrect password at+cpin? +CPIN: SIM PUK OK at^spic ^SPIC: 10 OK at+cpin=01234567,1234 +CME ERROR: incorrect password at^spic ^SPIC: 9 OK 2 attempts left. 1 attempt left. Now required password is PUK 1. 10 attempts left for PUK 1. 9 attempts left for PUK 1. EXAMPLE 2 Though a mobile is locked to a specific SIM card (phone lock), the user attempts to operate it with another SIM card. The user correctly enters the SIM PIN of the SIM card currently inserted, but then fails to give the ''PS'' lock password (PH-SIM PUK): at+cpin=9999 OK at+cpin? +CPIN: PH-SIM PIN OK at^spic ^SPIC: 3 OK at+cpin=4711 +CME ERROR: incorrect password at^spic? ^SPIC: 2 OK at+cpin=4712 +CME ERROR: incorrect password at^spic ^SPIC: 1 OK at^spic? ^SPIC: PH-SIM PIN OK at+cpin=4713 +CME ERROR: incorrect password at^spic ^SPIC: 63 OK at^spic? ^SPIC: PH-SIM PUK OK MC55_ATC_V04.00 Confidential / Released ME is waiting for the phone lock password. 3 attempts left. 2 attempts left. 1 attempt left. Displayed counter refers to phone lock password. Displayed counter refers to master phone code. Page 107 of 475 3/17/06 at+cpin=4714 +CME ERROR: incorrect password at^spic ^SPIC: 63 OK EXAMPLE 3 This example shows that after successful SIM PIN1 authentication the counter of the AT^SPIC execute and read command refers to SIM PIN2, i.e. it does not reflect the status of SIM PIN1. This may be a problem if the user enters a wrong PIN1 and is not aware that the number of attempts left to enter SIM PIN1 is counted down. +CREG: 0 at+cpin=1234 OK +CREG: 2 +CREG: 1 at+cpin? +CPIN: READY at^spic ^SPIC: 3 OK AT^SPIC? ^SPIC: SIM PIN2 OK at+clck="SC",0,456789 CME ERROR: incorrect password at^spic ^SPIC: 3 at+clck="SC",0,456789 CME ERROR: incorrect password at^spic ^SPIC: 3 at+clck="SC",0,456789 CME ERROR: incorrect password +CREG: 0 at^spic ^SPIC: 10 The mobile ist properly registered to the network. The AT+CPIN? read command confirms that SIM PIN1 authentication was successful. As SIM PIN1 authentication was successful, the counter relates to SIM PIN2 and correctly indicates that the user has 3 attempts to enter SIM PIN2. Likewise, the read command notifies that the ME is waiting for SIM PIN2. First attempt to enter a wrong SIM PIN1. SIM PIN1 authentication is still valid, and the counter relates to SIM PIN2. Second attempt to enter a wrong SIM PIN1. SIM PIN1 authentication is still valid, and the counter relates to SIM PIN2. Third attempt to enter a wrong SIM PIN1. SIM PIN1 authentication is no longer valid. This time, after the SIM PIN1 code has been disabled, the counter indicates the status of SIM PIN1 and notifies that 10 attempts are left to enter the SIM PUK. To avoid conflicts we recommend to use the AT^SPIC read and write commands rather than the execute command only. The read command clearly states the currently required password, and the write command may be used to get the counter for a specific <facility>, in this case for example "P2". MC55_ATC_V04.00 Confidential / Released Page 108 of 475 3/17/06 5.4 AT+CLCK Facility lock AT+CLCK can be used to lock, unlock or interrogate a network or ME <facility>. The command can be aborted when network facilities are being set or interrogated. Syntax Test Command AT+CLCK=? Response(s) +CLCK:list of supported <facility>s OK Write Command AT+CLCK=<facility>, <mode>[, <password>][, <class>] Response(s) if <mode> is not equal 2 and command successful: OK if <mode>= 2 and command successful: +CLCK: <status>[, <class>] [+CLCK: <status>[, <class>]] [+CLCK: ...] OK If error is related to ME functionality +CME ERROR Reference(s) PIN GSM 07.07, GSM 02.04, GSM 02.88, GSM 03.88, GSM 04.88 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <facility>(str) Phone security locks set by client or factory Primarily intended for the client to take safety precautions, "SC", "PS" and "FD" can be configured individually. "PS" may also be factory set. Parameter <class> is not applicable to security locks. See examples below for further details. "SC" SIM (lock SIM cards). SIM requests password upon ME power-up and when this lock command is issued. <password>: SIM PIN1. "PS" Phone locked to SIM card. ME requests password when other than current SIM card is inserted. "PS" lock is frequently referred to as "phone lock", or "device lock". Accordingly, the password may be called "phone code" or "device code". The "PS" password is not associated with the PUK of the SIM card. If incorrectly entered three times, the Master Phone Code is required to lift the lock. This is an 8-digit device code associated to the IMEI number of the mobile which can only by obtained from the manufacturer of the module. Once the Master Phone Code has been acctepted, the mobile is operational, and the "PS" lock is no longer active. If needed it must be set once again. MC55_ATC_V04.00 Confidential / Released Page 109 of 475 3/17/06 <password>: User defined password. It is needed before the first use of <facility> "PS" and, therefore, must first be specified with AT+CPWD or AT^SPWD, if it has not been predefined by factory settings. If set by factory (e.g. for a prepaid mobile), the password is supplied by the provider or operator. "FD" SIM fixed dialling memory: If the mobile is locked to "FD", only the phone numbers stored to the "FD" memory can be dialled. (Capacity of FD phonebook depending on the SIM card). <password>: SIM PIN 2. If a lock on the SIM fixed dialing memory is active, the following applies: • Outgoing voice, data or fax calls can be made only to numbers stored in ''FD'' phonebook. Result code depends on the type of the call: for voice calls, indication is ''+CME Error 257: Call barred''. for data and fax calls, indication is ''NO CARRIER''. • Access to defined Supplementary Services such as Call barring, Call waiting, Call forwarding, Call hold and Multiparty is possible only if the exact corresponding public MMI *# code for the desired service is stored in the fixed dialing number phone book, and used with ATD. AT commands for supplementary service control are barred while "FD" lock is active. Indication is ''+CME Error 257: Call barred''. • Access to Unstructured Supplementary Services (''USSD'') is possible only if the exact desired USSD string is stored in the fixed dialling number phone book, and used with ATD. AT commands for USSD are barred while "FD" lock is active. Indication is ''+CME Error 257: Call barred''. • SMS can be sent only to phone numbers which are stored in the ''fixed dialling numbers'' phonebook ''FD''. Indication is ''+CMS Error 302: operation not allowed''. • GPRS commands can be used only if the ''fixed dialling numbers'' phonebook ''FD'' contains an entry with phone number ''*99#''. This single entry enables all GPRS commands, including AT commands and modem compatibility commands like ''ATD*99***1#'' or ''ATD*98***1#''. Indication is ''+CME Error 257: Call barred''. Factory defined SIM locks: Typical examples of factory set SIM locks are prepaid phones or network locks, used to restrict the operation of a mobile to a specific provider or operator. The client should be aware that each of these lock types can only be unlocked if the associated password is available. For example, a mobile can be locked to accept only SIM cards from the respective provider, or even one single SIM card. Once a different SIM card is inserted the ME will prompt the client to enter a specific code. This is not the PUK of the SIM card, but usually an 8-digit code which needs to be requested from the provider. The locks can only be set by the manufacturer and need to be agreed upon between the parties concerned, e.g. provider, operator, distributor etc. on the one side and the manufacturer on the other side. For details contact your local dealer or Siemens AG. Parameter <class> is not applicable to SIM locks. <password> and instructions for unlocking must be obtained from the network provider. "PF" lock Phone to the very First SIM card "PN" Network Personalisation "PU" Network subset Personalisation "PP" Service Provider Personalisation "PC" Corporate Personalisation MC55_ATC_V04.00 Confidential / Released Page 110 of 475 3/17/06 Supplementary Service Call Barring: Supplementary Service "Call Barring" allows to specify conditions under which calls will be disallowed by the network. The availability of the Supplementary Services varies with the network. To benefit from call barring the client will need to subscribe them, though a limited number of call barring types may be included in the basic tariff package. When you attempt to set a <facility> or <class> which is not provisioned, not yet subscribed to, or not supported by the module, the setting will not take effect regardless of the response returned. The responses in these cases vary with the network (for example "OK", "+CME ERROR: Operation not allowed", "+CME ERROR: Operation not supported" etc.). To make sure check the extended error response with AT+CEER and the lock status with <mode>=2. <password>: Network password supplied from the provider or operator. Usually there is one password which applies to all call barring options. For details contact your provider. "AO" BAOC (Bar All Outgoing Calls) "OI" BOIC (Bar Outgoing International Calls) "OX" BOIC-exHC (Bar Outgoing International Calls except to Home Country) "AI" BAIC (Bar All Incoming Calls) "IR" BIC-Roam (Bar Incoming Calls when Roaming outside the home country) "AB" All Barring services (applicable only for <mode>=0) "AG" All outGoing barring services (applicable only for <mode>=0) "AC" All inComing barring services (applicable only for <mode>=0) <mode>(num) 0 unlock 1 lock 2 query status <status>(num) 0 lock is inactive 1 lock is active <password>(str) Password string used to lock and to unlock a <facility>. Length and authority for passwords depend on the <facility> in question and are therefore listed in the section on parameter <facility>. Passwords can be modified with AT+CPWD or AT^SPWD. <class>(num) Integer or sum of integers each representing a class of information, i.e. a bearer service, telecommunication service or bearer service group as defined in "GSM 02.04". 1 voice 2 class 2 ("data") comprises all those individual data classes between 16 and 128, that are supported both by the network and the MS. This means, a setting made for class 2 applies to all individual data classes (if supported). In addition, you can assign a different setting to a specific class. For example, you can activate Call Forwarding for all data classes, but deactivate it for data class 64, "dedicated packet access". 4 fax 8 SMS 16 data circuit sync 32 data circuit async MC55_ATC_V04.00 Confidential / Released Page 111 of 475 3/17/06 64 dedicated packet access 128 dedicated PAD access 1...[7]...255 combination of some of the above classes. For example, the default setting 7 represents the sum of the integers 1, 2 and 4 (voice, data and fax). The value 255 covers all classes. If parameter "class" is omitted, the default value 7 is used. Notes • The AT+CLCK command offers the full range of <class> parameters according to the GSM specifications. However, when you attempt to use a service option which is not provisioned or not yet subscribed to, the setting will not take effect regardless of the response returned. The responses in these cases vary with the network (for example "OK", "Operation not allowed", "Operation not supported" etc.). To make sure check the extended error response with AT+CEER and the lock status with <mode>=2. • The command has been implemented with the full set of <class> parameters according to GSM 07.07. For actual applicability of a desired Call barring service to a specific service or service group (a specific <class> value) please consult table A.1 of GSM 02.04. • If an outgoing Fax or Data Call is rejected due to an active ''call barring'' supplementary service, the call will be terminated with result code NO CARRIER. Under the same conditions, an outgoing Voice call will be terminated with result code NO DIALTONE. • If an invalid <password> is entered several times in succession, a delay incremented after each failed attempt will increase the time to wait before the input of the <password> is accepted. To avoid blocking the serial interface the running AT+CLCK command is aborted after a short timeout and returns CME ERROR 100 ("unknown"). If then the AT+CLCK command is issued once again execution is denied with CME ERROR 256 ("Operation temporary not allowed"). For details regarding the delay see Section 5.1.1, What to do if PIN or password authentication fails?. • If the user tries to set a lock although it is already active or, the other way round, tries to unlock an inactive lock, the response will be OK, but the <password> will not be checked or verified. Examples EXAMPLE 1 Lock SIM card (<facility>= "SC") AT+CLCK="SC",1,"9999" OK AT+CLCK="SC",0,"9999" OK The "SC" parameter enables or disables the SIM PIN authentication (PIN 1) when you power up the GSM engine SIM card locked. As a result, SIM PIN 1 must be entered to enable ME to register to the GSM network. Unlocks SIM card. When powered up, ME registers to the GSM network without requesting SIM PIN1. Note: Depending on the services offered by the provider, this feature is not supported by all SIM card types. If so, the command returns ERROR when you attempt to unlock the card. To query the status of the SIM card lock: AT+CLCK="SC",2 +CLCK: 1 Query the status of SIM card lock. SIM card is locked. SIM PIN1 must be entered to enable ME to register to the GSM network. OK MC55_ATC_V04.00 Confidential / Released Page 112 of 475 3/17/06 EXAMPLE 2 Phone lock (<facility>="PS") AT+CPIN? OK Make sure that PIN1 authentication is valid. To lock the ME to the currently inserted SIM card, first specify a password for <facility> "PS": AT+CPWD="PS",,"1234" OK If "PS" lock has not been set before: enter new password. Optionally, if "PS" password was defined before, change existing password: AT+CPWD="PS","1234","3333" OK To replace existing "PS" password: Enter old and new password. Then, activate the Phone Lock: AT+CLCK="PS",1,"3333" OK Locks the mobile to the current SIM card. To operate the mobile with the SIM card for which "PS" lock was activated: AT+CPIN? +CPIN: SIM PIN OK AT+CPIN="9999" OK No additional password is required for operation (SIM recognized by mobile). To operate the mobile with other SIM card than the one used for the "PS" lock: Enter SIM PIN of present card, followed by "PS" lock password. AT+CPIN? +CPIN: SIM PIN OK AT+CPIN="1111" OK AT+CPIN? +CPIN: PH-SIM PIN OK AT+CPIN="3333" OK PIN authentication accepted. "PS" lock password is required. "PS" Lock password has been accepted. ME is fully operational now. To deactivate the Phone Lock: AT+CLCK="PS",0,"3333" OK MC55_ATC_V04.00 Confidential / Released Phone Lock password has to be provided again. Now the mobile can be used with any SIM card, without the need of the phone lock password. Page 113 of 475 3/17/06 5.5 AT^SLCK Facility lock AT^SLCK provides the "Facility lock" function as defined for the GSM 07.07 command AT+CLCK. The command can be used to lock, unlock or interrogate a network or ME <facility>. AT^SLCK is, in every respect, identical with AT+CLCK, except that the command syntax and response prefix is "^SLCK" instead of "+CLCK". For further details please refer to AT+CLCK. The command can be aborted when network facilities are being set or interrogated. Syntax Test Command AT^SLCK=? Response(s) ^SLCK:list of supported <facility>s OK Write Command AT^SLCK=<facility>, <mode>[, <password>][, <class>] Response(s) if <mode> is not equal 2 and command successful: OK if <mode>= 2 and command successful: ^SLCK: <status>, <class> [^SLCK: <status>, <class>] [^SLCK: ...] OK If error is related to ME functionality +CME ERROR Reference(s) SIEMENS, GSM 07.07, GSM 02.04, GSM 02.88, GSM 03.88, GSM 04.88 MC55_ATC_V04.00 Confidential / Released PIN % ASC0 ASC1 % Page 114 of 475 % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! 3/17/06 5.6 AT+CPWD Change Password AT+CPWD allows to define a new password for a password protected <facility> lock function. Each password is a string of digits, the length of which varies with the associated <facility>. The test command returns a list of pairs which represent the available facilities and the maximum length of the associated password. See AT commands AT+CLCK and AT^SLCK for more information on the various lock features. Specifically the command can be used to • change PIN1 or PIN2, • change the password supplied from your provider for the "call barring" supplementary service, • set individual phone security passwords, • enter the unblocking key (Master Phone Code) to restore a disabled "PS" password. To delete a password use the following syntax: at+cpwd=<facility>,<old password> Syntax Test Command AT+CPWD=? Response(s) +CPWD:list of supported (<facility>, <password length>) OK Write Command AT+CPWD=<facility>, <old password>[, <new password>] Response(s) New password has been registered for the facility lock function. OK If parameter <old password> was not correct: +CME ERROR 16 (+CME ERROR: incorrect password) If the password for the selected <facility> has been invalidated due to too many failed attempts: +CME ERROR ... If error is related to ME functionality: +CME ERROR Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <facility>(str) Phone security locks set by client or factory: Primarily intended for the client to take safety precautions, passwords "SC" (SIM PIN) and "P2" (SIM PIN2) are usually predefined, but can be configured individually. The password for lock facility "PS" may also be factory set. "SC" MC55_ATC_V04.00 Confidential / Released SIM PIN. SIM requests password upon ME power-up and when this lock command is issued. If incorrectly entered three times, the SIM PUK is required to perform authentication. Input of the SIM PUK password is possible only with AT command AT+CPIN or ATD. For further details please refer to Section 5.1.1, What to do if PIN or password authentication fails?. <password length>: 4 to 8 digits. Page 115 of 475 3/17/06 "PS" Phone locked to SIM card. ME requests password when other than current SIM card is inserted. "PS" lock is frequently referred to as "phone lock", or "device lock". Accordingly, the password may be called "phone code" or "device code". The "PS" password is not associated with the PUK of the SIM card. It must be defined before the first use of <facility> "PS" with AT+CLCK. <password length>: 4 digits. If incorrectly entered three times, the Master Phone Code is required to lift the lock. This Unblocking procedure is performed with AT+CPWD using the following parameters: <facility>="PS", <old password>= Master Phone Code (to be obtained from the module manufacturer), and <new password>= the new phone code ("PS" password for lock facility), if desired. Mind that successful PIN authentication is a prerequisite for use of AT command AT+CPWD. If Pin authentication has not been completed, input of the Master Phone code password is possible only with AT command AT+CPIN or ATD. For further detail please refer to Section 5.1.1, What to do if PIN or password authentication fails?. Once the Master Phone Code has been acctepted, the mobile is operational, and the "PS" lock is no longer active. If needed it must be set once again with AT+CLCK. "P2" SIM PIN 2, e.g. required for authentication with facility lock "FD" (cf. AT+CLCK). If incorrectly entered three times, the SIM PUK 2 is required to perform authentication. Input of the SIM PUK 2 password is possible only with AT command AT+CPIN2 or ATD. For further detail please refer to Section 5.1.1, What to do if PIN or password authentication fails?. <password length>: 4 to 8 digits. Factory defined SIM locks: Typical examples of factory set SIM locks are prepaid phones or network locks, used to restrict the operation of a mobile to a specific provider or operator. The client should be aware that each of these lock types can only be unlocked if the associated password is available. For example, a mobile can be locked to accept only SIM cards from the respective provider, or even one single SIM card. Once a different SIM card is inserted the ME will prompt the client to enter a specific code. This is not the PUK of the SIM card, but usually an 8-digit code which needs to be requested from the provider. The locks can only be set by the manufacturer and need to be agreed upon between the parties concerned, e.g. provider, operator, distributor etc. on the one side and the manufacturer on the other side. For details contact your local dealer or Siemens AG. "PF" Lock Phone to the very First SIM card "PN" Network Personalisation "PU" Network subset Personalisation "PP" Service Provider Personalisation "PC" Corporate Personalisation Supplementary Service Call Barring: Supplementary Service "Call Barring" allows to specify conditions under which calls will be disallowed by the network. The availability of the Supplementary Services varies with the network. To benefit from call barring the client will need to subscribe them, though a limited number of call barring types may be included in the basic tariff package. <password length>: The Network Password needs to be supplied from the network provider or network operator. Usually there is one 4 digit password which applies to all call barring options. For details contact your provider. "AO" BAOC (Bar All Outgoing Calls) "OI" BOIC (Bar Outgoing International Calls) "OX" BOIC-exHC (Bar Outgoing International Calls except to Home Country) "AI" BAIC (Bar All Incoming Calls) MC55_ATC_V04.00 Confidential / Released Page 116 of 475 3/17/06 "IR" BIC-Roam (Bar Incoming Calls when Roaming outside the home country) "AB" All Barring services "AG" All outGoing barring services "AC" All inComing barring services <password length>(num) 4...8 Length of password. The range of permitted length for a password depends on the associated <facility>. It is available from the test command response, or in the description of parameter <facility>. <old password>(str) Password specified for the facility. Parameter <old password> can be ignored if no old password was allocated to the facility. Take into account that a password may have already been set by factory, or that the service is subject to a password issued by the provider. See notes above or contact provider. <new password>(str) New password. Mandatory, if <old password> was an unblocking key (such as the Master Phone Code). Note • When changing PIN2 (<facility>="P2") it is recommended to check the new state of PIN2 by using the AT+CPIN2 command. Examples EXAMPLE 1 To change PIN2 AT+CPWD="P2","0000","8888" OK (where "0000" = old PIN2 and "8888" = new PIN2) PIN2 Password has been changed to "8888" EXAMPLE 2 To set password used to enable or disable barring of all outgoing calls: AT+CPWD="AO","0000","3333" OK Requests the network to change the password for supplementary service "call barring". Usually this request will affect all barring services, even though the request is issued for Supplementary Service BAOC ("Barring of all outgoing calls") only. Refer to the respective network provider for detail. EXAMPLE 3 Handling of the "PS" lock password AT+CMEE=2 AT+CPWD="PS","1111","2222" OK AT+CPWD="PS","1111","2222" +CME ERROR: incorrect password MC55_ATC_V04.00 Confidential / Released Enable text output of CME Error information (where "1111" = old password and "2222" = new password) Password for facility "PS" is now "2222" Repeat command to provoke error "incorrect password" ("1111" is no longer the correct password) Page 117 of 475 3/17/06 EXAMPLE 4 To specify a new "PS" lock password, after the old password was disabled (e.g. after three failed attempts to change the "PS" password): use the master phone code. CAUTION: THIS TEST SHOULD BE PERFORMED ONLY IF THE CORRECT MASTER PHONE CODE FOR THE INDIVIDUAL ME USED IS DEFINITELY AVAILABLE! Otherwise the module used will be rendered useless until the correct master phone code is entered!: where 12345678 is the Master Phone Code and 1111 is the new password. You may also use <new password> to restore the former disabled password. AT+CPWD="PS","12345678","1111" OK Alternatively, without giving a new password: AT+CPWD="PS","12345678" (where 12345678 is the Master Phone Code). Deactivates the present phone lock. OK MC55_ATC_V04.00 Confidential / Released Page 118 of 475 3/17/06 5.7 AT^SPWD Change Password The AT^SPWD command provides the same functions as AT+CPWD. The major difference between both commands is that, apart from the different prefixes "^SPWD" and "+CPWD", the AT^SPWD command includes additional functions dedicated to the Customer SIM Lock. Please note that this feature is only supported by specifically pre-configured MC55 modules and, therefore, not part of the standard "MC55 AT Command Set". Ordering information and a detailed description of the "Customer SIM Lock" feature can be requested from Siemens. All other functions and parameters of AT^SPWD are described in Section 5.6, AT+CPWD. Each password is a string of digits the length of which varies with the associated facility. The test command returns a list of pairs which represent the available facilities and the maximum length of the associated password. See also AT commands AT+CLCK and AT^SLCK for more detail on the various lock features. Syntax Test Command AT^SPWD=? Response(s) ^SPWD:list of supported ( <facility>, <password length>) OK Write Command AT^SPWD=<facility>, <old password>[, <new password>] Response(s) New password has been registered for the facility lock function. OK If parameter <old password> was not correct: +CME ERROR 16 (+CME ERROR: incorrect password) If the password for the selected <facility> has been invalidated due to too many failed attempts: +CME ERROR ... If error is related to ME functionality: +CME ERROR PIN % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Note • When changing the PIN2 (<facility>="P2") it is recommended to check the new state of PIN2 using the AT+CPIN2 command. MC55_ATC_V04.00 Confidential / Released Page 119 of 475 3/17/06 6. Identification Commands The AT Commands described in this chapter allow the external application to obtain various identification information related to the MC55 and linked entities. 6.1 ATI Display product identification information The ATI execute command delivers a product information text. The 'Revision' information consists of the following parts: Version xx and variant yy of software release. Syntax Exec Command ATI Response(s) SIEMENS MC55 REVISION xx.yy OK Exec Command ATI[<value>] Response(s) [SIEMENS Gipsy Soft Protocolstack V2.550] OK Reference(s) V.250 PIN ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <value>(num) 9 SIEMENS Gipsy Soft Protocolstack V2.550 This information is delivered if ATI is used with the optional parameter <value>9 (i.e. if ATI9 is entered). Other values are not supported and only return OK. MC55_ATC_V04.00 Confidential / Released Page 120 of 475 3/17/06 6.2 AT+CGMI Request manufacturer identification AT+CGMI returns a manufacturer identification text. See also: AT+GMI. Syntax Test Command AT+CGMI=? Response(s) OK Exec Command AT+CGMI Response(s) SIEMENS OK Reference(s) PIN GSM 07.07 ! 6.3 ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! AT+GMI Request manufacturer identification AT+GMI returns a manufacturer identification text. See also: AT+CGMI. Syntax Test Command AT+GMI=? Response(s) OK Exec Command AT+GMI Response(s) SIEMENS OK Reference(s) V.250 MC55_ATC_V04.00 Confidential / Released PIN ! ASC0 ASC1 % Page 121 of 475 % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! 3/17/06 6.4 AT+CGMM Request model identification AT+CGMM returns a product model identification text. Command is identical with AT+GMM. Syntax Test Command AT+CGMM=? Response(s) OK Exec Command AT+CGMM Response(s) MC55 OK Reference(s) PIN GSM 07.07 ! 6.5 ASC0 ASC1 % MUX1 MUX2 % % % MUX3 Charge % ! ! Last ! AT+GMM Request model identification AT+GMM returns a product model identification text. Command is identical with AT+CGMM. Syntax Test Command AT+GMM=? Response(s) OK Exec Command AT+GMM Response(s) MC55 OK Reference(s) V.250 MC55_ATC_V04.00 Confidential / Released PIN ! ASC0 ASC1 % Page 122 of 475 % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! 3/17/06 6.6 AT+CGMR Request revision identification of software status AT+CGMR delivers a product firmware version identification. Command is identical with AT+GMR. Syntax Test Command AT+CGMR=? Response(s) OK Exec Command AT+CGMR Response(s) REVISION <xx.yy> OK Reference(s) PIN GSM 07.07 ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <xx.yy>(str) Version xx and variant yy of software release. 6.7 AT+GMR Request revision identification of software status AT+GMR delivers a product firmware version identification. Command is identical with AT+CGMR. Syntax Test Command AT+GMR=? Response(s) OK Exec Command AT+GMR Response(s) REVISION <xx.yy> OK Reference(s) V.250 PIN ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <xx.yy>(text) Version xx and variant yy of software release. MC55_ATC_V04.00 Confidential / Released Page 123 of 475 3/17/06 6.8 AT+CGSN Request International Mobile Equipment Identity (IMEI) AT+CGSN delivers the International Mobile Equipment Identity (IMEI). Command is identical with: AT+GSN. Syntax Test Command AT+CGSN=? Response(s) OK Exec Command AT+CGSN Response(s) <sn> OK Reference(s) PIN GSM 07.07 ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! Last ! ! Parameter Description <sn>(str) International Mobile Equipment Identity (IMEI) used to identify a GSM mobile equipment to the GSM network 6.9 AT+GSN Request International Mobile Equipment Identity (IMEI) AT+GSN delivers the International Mobile Equipment Identity (IMEI). Command is identical with AT+CGSN Syntax Test Command AT+GSN=? Response(s) OK Exec Command AT+GSN Response(s) <sn> OK Reference(s) V.250 PIN ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <sn>(str) International Mobile Equipment Identity (IMEI) used to identify a GSM mobile equipment to the GSM network. MC55_ATC_V04.00 Confidential / Released Page 124 of 475 3/17/06 6.10 AT+CIMI Request International Mobile Subscriber Identity (IMSI) AT+CIMI delivers the International Mobile Subscriber Identity (IMSI). The IMSI permits the TE to identify the individual SIM attached to the ME. Syntax Test Command AT+CIMI=? Response(s) OK Exec Command AT+CIMI Response(s) <imsi> OK ERROR +CME ERROR: <err> Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <imsi>(str) International Mobile Subscriber Identity (string without quotes). MC55_ATC_V04.00 Confidential / Released Page 125 of 475 3/17/06 7. Call related Commands The AT Commands described in this chapter are related to Mobile Originated (MOC, i.e. outgoing) Calls and Mobile Terminated (MTC, i.e. incoming) Calls. 7.1 Call Status Information For Circuit switched calls, including voice, fax and data calls, call status information is available with URC "+CIEV: call" (configurable via AT commands AT+CIND and AT+CMER) or - in more detail - from the list of current calls. This list can be displayed on request via at commands AT+CLCC and AT^SLCC. It can also be issued by the ME in the form of an unsolicited result code "^SLCC" if configured with AT^SLCC and AT+CMER. URC "+CIEV: call" and URC "^SLCC" can be configured using AT command AT^SCFG. An overview of the possible configurations and their consequences for the availability of call status information will be given here. Generally speaking, the call status values recognized by the ME are as follows: • active • held • dialing (MOC) • alerting (MOC) • incoming (MTC) • waiting (MTC) • terminating: The call is not active anymore, but inband information is still available. • dropped: The call has been suspended by the network, but may be resumed later. The values "terminating" and "dropped" are not standardized for AT command AT+CLCC, and therefore only available for command AT^SLCC. A call in any of these two states will not appear in the list of current calls as displayed with AT+CLCC. A call that is not recognized by the ME is considered to be in "unknown" state. Some networks may schedule a traffic channel for a call that is not yet in the "active" state. This is reflected in parameter <traffic channel assigned> of AT command AT^SLCC and the corresponding URC. Depending on the value of AT^SCFG setting <succ>, Indicator "+CIEV" will be issued (if configured with AT+CIND and AT+CMER) • when a state transition ends in state "active" or in state "unknown" (if AT^SCFG setting <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 AT^SCFG setting <succ>=''verbose''). The indicator value for indicator "+CIEV: call" will be "1" if at least one call is in states "held" or "active", and "0" otherwise. Depending on the value of AT^SCFG setting <sucs>, Indicator "^SLCC" will be issued (if configured with write command AT^SLCC and AT+CMER) • when a state transition ends in state "active" or in state "unknown" (if AT^SCFG setting <sucs>="restricted") • when any state transition (including transitions beginning or ending in state "unknown") occurs in the list of active calls, or when a voice channel is established (if AT^SCFG setting <sucs>="verbose"). Due to compatibility considerations, the powerup default for AT^SCFG setting <succ> is "restricted", offering compatibility to the standard behaviour of indicator "+CIEV: call", while the default for setting <sucs> is "verbose". In order to see the URCs, event reporting for both indicators must be explicitely configured with the appropriate AT commands. MC55_ATC_V04.00 Confidential / Released Page 126 of 475 3/17/06 7.2 ATA Answer a call Syntax Exec Command ATA Response(s) In case of data call, if successfully connected (TA switches to data mode): CONNECT <text> In case of voice call, if successfully connected: OK When TA returns to command mode after call release: OK If no connection: NO CARRIER Reference(s) V.250 PIN ASC0 ASC1 % % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description TA causes remote station to go off-hook (e.g. answer call). Parameter Description <text>(str) Connection status <text> output only if ATX parameter setting with value greater 0. Notes • Any additional commands on the same command line are ignored. • The command may be aborted generally by receiving a character during execution. It can't be aborted in some connection setup states, such as handshaking. • If AT+FCLASS setting is 1 or 2, all incoming calls will be answered as fax calls, when ATA is issued on multiplexer channel 1 resp. ASC0. For calls explicitly signalled as voice or data calls, this procedure will fail with result code "NO CARRIER", but the call in question will continue to ring. It is possible to change the setting for AT+FCLASS to 0 while the call is ringing, and accept the call normally afterwards with ATA. • The ATA command may be used also to accept a network request for a PDP context activation (see ATA). • See also ATX for <text>. • If an incoming call is no longer available (already disconnected/hanged up)a "NO CARRIER" result code will be given. MC55_ATC_V04.00 Confidential / Released Page 127 of 475 3/17/06 7.3 ATD Mobile originated call to specified number Syntax Exec Command ATD<n>[<mgsm>][;] Response(s) If no dialtone (parameter setting ATX2 or ATX4): NO DIALTONE If busy (parameter setting ATX3 or ATX4): BUSY If a connection cannot be set up: NO CARRIER OK If successfully connected and non-voice call (TA switches to online data mode): CONNECT <text> When TA returns to command mode after call release: OK If successfully connected and voice call: OK Reference(s) V.250 PIN § ASC0 ASC1 % MUX1 MUX2 % § § MUX3 Charge § ! ! Last ! Command Description This command can be used to set up outgoing voice, data or fax calls. It also serves to control Supplementary Services. The termination character ";" is mandatory to set up voice calls or to send *# codes for Supplementary Services. It must not be used for data and fax calls. Additional notes on the responses returned after dialing with ATD: • For voice calls, you have the choice of two different response modes that can be selected with AT^SM20: AT^SM20=1 (factory default) causes the ME to respond once the call setup is completed either successfully ("OK") or unsuccessfully ("NO CARRIER", "NO DIAL TONE", "BUSY"). AT^SM20=0 causes the ME to return "OK" immediately after dialing was completed (i.e. before call setup terminates successfully or unsuccessfully). • For data connections, call setup always terminates when the call has been established (indicated by the result code "CONNECT <text>), or when it fails (indicated by "NO CARRIER"). The settings of AT^SM20 do not apply. Different call release indications: • Upon termination, an outgoing fax or data call may show a different result code than a voice call would show under identical conditions. In order to track down the actual reason for call termination, AT+CEER or ATS18 should be used for all applicable connections. Using ATD during an active call: • When a user originates a second voice call whil there is already an active voice call, the first call will automatically put on hold. The second call attempt is acknowledged with "OK" immediately after dialing with ATD has completed, without relation to a successful call setup. In case of failure, the additional result codes "NO CARRIER", "NO DIAL TONE", "NO CARRIER" will be presented afterwards (see example below). Parameter Description <n>(text) String of dialing digits and optional V.250 modifiers: 0-9, *, #, +, A, B, C The following V.250 modifiers are ignored: ,(comma), T, P, !, W ,@ MC55_ATC_V04.00 Confidential / Released Page 128 of 475 3/17/06 <mgsm>(str) String of GSM modifiers: I Activates CLIR (disables presentation of own phone number to called party) i Deactivates CLIR (enables presentation of own phone number to called party) G Activate Closed User Group explicit invocation for this call only. g Deactivate Closed User Group explicit invocation for this call only. Notes • The command may be aborted generally when receiving a character during execution. It cannot be aborted in some connection setup states, such as handshaking. • Parameter "I" and "i" only if no *#-code is within the dial string. • <mgsm> is not supported for data calls. • <n> is default for last number that can be dialled by ATDL. • See also ATX for <text>. • If ATD is used with a USSD command (e.g. ATD*100#;) an AT+CUSD=1 is executed implicitly (see AT+CUSD). • Parameter 'G' or 'g' will be ignored if Closed User Group was already activated, respectively deactivated with AT+CCUG command before. Call by call invocation of CUG uses the settings provisioned by the provider or, if available, the settings of the parameters <index> and <info> made with AT+CCUG. • The ME is equipped with a "Blacklist" function according to GSM02.07 Annex A: After a predefined number of failed call attempts, the dialed number is entered into a read-only phonebook called "blacklist" (phonebook "BL"). Call attempts to numbers contained in the blacklist will be barred by ME and not signalled to the network. An attempt to start a voice call to a barred phone number will be stopped with a CME ERROR 257 "Call Barred". An attempt to start a data or fax call to a barred phone number will be answered immediately with result code "NO CARRIER". The barred numbers are automatically removed from the blacklist according to the timing conditions specified in GSM02.07 Annex A. • Emergency calls: MC55 supports 112, 911 or 08 (standardized GSM emergency numbers, usable with or without SIM). Example The following example shows the call setup procedure when a call is already active and a second call attempt fails because the line of the called party is busy: atd03012345678 OK ATD03022222222 OK BUSY MC55_ATC_V04.00 Confidential / Released Dialing out the first party's number. The first call is established. The number of the second party is dialed. The response "OK" is issued immediately though no call is established (same behavior as is you had chosen AT^SM20=0.) Line of the second called party is busy. Page 129 of 475 3/17/06 7.4 ATD><mem><n> Mobile originated call using specific memory and index number Syntax Exec Command ATD><mem><n>[<mgsm>]; Response(s) ERROR +CME ERROR: <err> If no dialtone (parameter ATX2 or ATX4): NO DIALTONE If busy (parameter setting ATX3 or ATX4): BUSY If connection cannot be set up: NO CARRIER When TA returns to command mode after call release: OK If successfully connected: OK Reference(s) PIN V.250 % ASC0 ASC1 % MUX1 MUX2 % § § MUX3 Charge § ! ! Last ! Command Description TA attempts to set up an outgoing call to the specified number. The termination character ";" is mandatory since dialing from a phonebook is only supported for voice calls and for sending *# codes of Supplementary Services or other functions. Parameter Description <mem>(str) Phonebook storage: For detailed description of storages see AT+CPBS. "FD" Fixed dialing phonebook "SM" SIM phonebook "ON" MSISDN list "ME" Mobile Equipment Phonebook "LD" Last number dialed phonebook "MC" Missed (unanswered received) calls list "RC" Received calls list <n>(num) Integer type memory location in the range of locations available in the selected memory, i.e. the index number returned by AT+CPBR. <mgsm>(str) String of GSM modifiers: I Activates CLIR (disables presentation of own phone number to called party) i Deactivates CLIR (enables presentation of own phone number to called party) MC55_ATC_V04.00 Confidential / Released Page 130 of 475 3/17/06 Notes • This command may be aborted generally by receiving a character during execution. Abortion is not possible during some states of connection setup such as handshaking. • There is no <mem> for emergency call ("EN"). • The command is not applicable to data calls. Any attempt to dial a data call number from <mem> causes the result code "NO CARRIER" to appear. • Parameter <mgsm> only if no *# code is within the dialing string. • See ATX for setting result code and call monitoring parameters. Examples EXAMPLE 1 To query the location number of the phonebook entry: AT+CPBR=1,xx TA returns the entries available in the active phonebook. EXAMPLE 2 To dial a number from the SIM phonebook, for example the number stored to location 15: ATD>SM15; OK EXAMPLE 3 To dial a phone number stored in the last dial memory on the SIM card: ATD>LD9; OK MC55_ATC_V04.00 Confidential / Released Page 131 of 475 3/17/06 7.5 ATD><n> Mobile originated call from active memory using index number Syntax Exec Command ATD><n>[<mgsm>]; Response(s) ERROR +CME ERROR: <err> If no dialtone (parameter ATX2 or ATX4): NO DIALTONE If busy (parameter setting ATX3 or ATX4): BUSY If connection cannot be set up: NO CARRIER When TA returns to command mode after call release: OK If successfully connected: OK Reference(s) V.250 PIN % ASC0 ASC1 % § MUX1 MUX2 % § MUX3 Charge § ! ! Last ! Command Description TA attempts to set up an outgoing call to the stored number. The termination character ";" is mandatory since dialing from a phonebook is only supported for voice calls and for sending *# codes of Supplementary Services or other functions. Parameter Description <n>(num) Integer type memory location in the range of locations available in the selected memory, i.e. the index number returned by AT+CPBR. <mgsm>(str) String of GSM modifiers: I Activates CLIR (disables presentation of own phone number to called party) i Deactivates CLIR (enables presentation of own phone number to called party) Notes • This command may be aborted generally by receiving a character during execution. Abortion is not possible during some states of connection setup such as handshaking. • The command is not applicable to data calls. Any attempt to dial a data call number from <n> causes the result code "NO CARRIER" to appear. • Parameter <mgsm> only if no *# code is within the dialing string. MC55_ATC_V04.00 Confidential / Released Page 132 of 475 3/17/06 7.6 ATD><str> Mobile originated call from active memory using corresponding field Syntax Exec Command ATD><str>[<mgsm>]; Response(s) ERROR +CME ERROR: <err> If no dialtone (parameter ATX2 or ATX4): NO DIALTONE If busy (parameter setting ATX3 or ATX4): BUSY If connection cannot be set up: NO CARRIER When TA returns to command mode after call release: OK If successfully connected: OK Reference(s) V.250 PIN % ASC0 ASC1 % § MUX1 MUX2 % § MUX3 Charge § ! ! Last ! Command Description This command searches the active phonebook for a given string <str> and dials the assigned phone number. The termination character ";" is mandatory since dialing from a phonebook is only supported for voice calls and for sending *# codes of Supplementary Services or other functions. Parameter Description <str>(str)(+CSCS) String type value ("x"), which should equal an alphanumeric field in at least one phonebook entry in the searched memories; used character set should be the one selected with AT+CSCS. <str> can contain escape sequences as described in chapter "Supported character sets". <str> must be wrapped in quotation marks (""), if escape sequences or parameter <mgsm> are used or if the alphanumeric strings contains a blank. If not, quotation marks are optional. If AT+CSCS is set to "UCS2", with respect to the coding of UCS2-characters only phonebook entries that contain an alphanumeric string with as size less than the half of the parameter <tlength> from AT+CPBW can be dialed. <mgsm>(str) String of GSM modifiers: I Activates CLIR (disables presentation of own phone number to called party) i Deactivates CLIR (enables presentation of own phone number to called party) Notes • This command may be aborted generally by receiving a character during execution. Abortion is not possible during some states of connection setup such as handshaking. • The command is not applicable to data calls. Any attempt to dial <str> without semicolon ";" causes the result code "NO CARRIER" to appear. • Parameter <mgsm> only if no *# code is within the dialing string. MC55_ATC_V04.00 Confidential / Released Page 133 of 475 3/17/06 7.7 ATDI Mobile originated call to ISDN number Syntax Exec Command ATDI<n>[;] Response(s) If no dialtone (parameter ATX2 or ATX4): NO DIALTONE If busy (parameter setting ATX3 or ATX4): BUSY If connection cannot be set up: NO CARRIER All other error reasons: +CME ERROR If successfully connected and non-voice call (TA switches to data state): CONNECT <text> When TA returns to command mode after call release: OK If successfully connected and voice call: OK Reference(s) V.250 PIN % ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Command Description TA attempts to set up an outgoing call to ISDN number. The termination character ";" is mandatory to set up voice calls or to send *# codes for Supplementary Services. It must not be used for data and fax calls. Parameter Description <n>(str) ISDN number String with maximum length of 20 characters. Allowed characters: +, 0-9, A, B, C. Note • This command may be aborted generally by receiving a character during execution. Abortion is not possible during some states of connection setup such as handshaking. MC55_ATC_V04.00 Confidential / Released Page 134 of 475 3/17/06 7.8 ATDL Redial last number used Syntax Exec Command ATDL[;] Response(s) If there is no last number or number is not valid: +CME ERROR If no dialtone (parameter ATX2 or ATX4): NO DIALTONE If busy (parameter setting ATX3 or ATX4): BUSY If connection cannot be set up: NO CARRIER If successfully connected and non-voice call (TA switches to online data mode): CONNECT <text> When TA returns to command mode after call release: OK If successfully connected and voice call: OK Reference(s) V.250 PIN % ASC0 ASC1 % § MUX1 MUX2 % § MUX3 Charge § ! ! Last ! Command Description This command redials the last voice and data call number used in the ATD command. If terminated with semicolon ";" ATDL dials the last voice call number stored in the "LD" phonebook. Otherwise, the last dialed data or fax number will be used (not contained in the "LD" phonebook). Notes • This command may be aborted generally by receiving a character during execution. Abortion is not possible during some states of connection setup such as handshaking. • Parameter "I" and "i" only if no *#-code is within the dial string. MC55_ATC_V04.00 Confidential / Released Page 135 of 475 3/17/06 7.9 ATH Disconnect existing connection Syntax Exec Command ATH[<n>] Response(s) OK Reference(s) V.250 PIN ! ASC0 ASC1 % MUX1 MUX2 % % % MUX3 Charge % ! ! Last ! Command Description Disconnect existing call from command line by local TE and terminate call. Parameter Description <n>(num) [0] disconnect from line and terminate call Notes • OK is issued after circuit 109 (DCD) is turned off, if it was previously on. • ATH terminates every circuit switched call (voice, data or fax), even if it is issued via another interface. This behavior is in accordance with ITU-T V.250; (07/97, "Hook control": "ATH is terminating any call in progress."). • ATH clears any active PDP context or terminates any existing PPP connection, but only if issued on the same interface where GPRS is used and if there is no pending network request for PDP context activation. It does not affect PDP contexts and PPP connections on other interfaces (see also Chapter "ATH Manual rejection of a network request for PDP context activation"). MC55_ATC_V04.00 Confidential / Released Page 136 of 475 3/17/06 7.10 AT+CHUP Hang up call Syntax Test Command AT+CHUP=? Response(s) OK ERROR +CME ERROR Exec Command AT+CHUP Response(s) OK ERROR +CME ERROR Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description Cancels all active and held calls. Note • AT+CHUP implements the same function as ATH MC55_ATC_V04.00 Confidential / Released Page 137 of 475 3/17/06 7.11 ATS0 Set number of rings before automatically answering a call Syntax Read Command ATS0? Response(s) <n> OK ERROR Write Command ATS0=<n> Response(s) OK ERROR Reference(s) PIN V.250 ASC0 ASC1 § % % MUX1 MUX2 % % MUX3 Charge % ! Last ! ! Parameter Description <n>(num)(&W)(&V) 000(&F) Automatic answer mode is disabled. 001-255 Enable automatic answering after specified number of rings. Notes • This command works for MT data and fax calls. • Autoanswering of CSD data and fax calls is supported on ASC0/Mux1 only. • A CSD call will not be automatically answered when the module is in GPRS online mode, but it is possible in GPRS command mode. The application can detect a call by evaluating the RING line and determine whether to change into GPRS command mode or stay in GPRS online mode until GPRS is available again. To answer, to reject or to wait for automatically answering the incoming call the application has to switch into GPRS command mode. • If <n> is set to higher values, the calling party may hang up before the call is automatically answered. • The correlation between ATS7 and ATS0 is important. Example: Call setup may fail if ATS7=30 and ATS0=20. • Setting is local to the interface. It is allowed to have different settings on different interfaces. In such cases the interface 'wins', which is idle and uses the smallest <n> value. • The ATS0 write command is PIN protected. • According to "3GPP TS 27.007 (GSM 07.07): AT command set for User Equipment (UE)", ATS0 is also used as GPRS compatibility command to answer automatically to a network request for PDP context activation (see Section 11.19). Therefore, when the ATS0 write command is issued with <n> greater than 0, the ME will attempt to perform a GPRS attach if not yet attached and if configured to do so (due to the setting AT^SCFG="GPRS/ATS0/withAttach","on"). If the automatic GPRS attach fails the ME keeps trying to attach for approx. 5 minutes, before ATS0 ends up with "ERROR" or "+CME ERROR: unknown", though the new <n> value takes effect. To avoid the risk of long response times to ATS0 in such case take care that the parameter AT^SCFG=<gs0aa> is off, if autoanswer mode is not needed for GPRS or if the mobile works in non-GPRS networks. The GPRS attach will not be performed on recalling a stored user profile with ATZ or on powerup, even though a value <n> greater than 0 was stored in the user profile with AT&W. MC55_ATC_V04.00 Confidential / Released Page 138 of 475 3/17/06 7.12 ATS6 Set pause before blind dialing Syntax Read Command ATS6? Response(s) <n> OK Write Command ATS6=<n> Response(s) OK ERROR Reference(s) V.250 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Command Description No effect for GSM. Parameter Description <n>(num)(&W)(&V) 000(&F)...255 MC55_ATC_V04.00 Confidential / Released Page 139 of 475 3/17/06 7.13 ATS7 Set number of seconds to wait for connection completion ATS7 specifies the number of seconds the TA will wait for the completion of the call setup when answering or originating a data call. Also referred to as "no answer timeout". To put it plainly, this is the time to wait for the carrier signal. If no carrier signal is received within the specified time, the TA hangs up. Syntax Read Command ATS7? Response(s) <n> OK Write Command ATS7=<n> Response(s) OK ERROR Reference(s) PIN V.250 ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Parameter Description <n>(num)(&W)(&V) Number of seconds to wait for connection completion 000...060(&F) Notes • Command ATS7 is only applicable to data calls. • Values greater than 60 cause no error, but <n> will be restored to the maximum value of 60. • The correlation between ATS7 and ATS0 is important. If the called party has specified a high value for ATS0=<n> call setup may fail. Example: Call setup may fail if ATS7=30 and ATS0=20. MC55_ATC_V04.00 Confidential / Released Page 140 of 475 3/17/06 7.14 ATS8 Set number of seconds to wait for comma dialing modifier This command specifies the amount of time, in seconds, that the DCE shall pause, during signalling of call addressing information to the network (dialling), when a "," (comma) dial modifier is encountered in a dial string. Syntax Read Command ATS8? Response(s) <n> OK Write Command ATS8=<n> Response(s) OK ERROR Reference(s) V.250 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Command Description No effect for GSM. Parameter Description <n>(num)(&W)(&V) 0(&F) DCE does not pause when "," encountered in dial string 1...255 Number of seconds to pause MC55_ATC_V04.00 Confidential / Released Page 141 of 475 3/17/06 7.15 ATS10 Set disconnect delay after indicating the absence of data carrier Syntax Read Command ATS10? Response(s) <n> OK Write Command ATS10=<n> Response(s) OK ERROR Reference(s) V.250 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Command Description This parameter setting determines the amount of time, that the TA remains connected in absence of a data carrier. If the data carrier is detected before disconnect, the TA remains connected. Parameter Description <n>(num)(&W)(&V) number of tenths of seconds of delay 001...2(&F)...254 MC55_ATC_V04.00 Confidential / Released Page 142 of 475 3/17/06 7.16 ATO Switch from command mode to data mode / PPP online mode Syntax Exec Command ATO[<n>] Response(s) If connection is not successfully resumed: NO CARRIER or TA returns to data mode from command mode CONNECT <text> Note: <text> output only if ATX parameter setting with value > 0. Reference(s) V.250 PIN ! ASC0 ASC1 % § MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Command Description ATO is the corresponding command to the +++ escape sequence: When you have established a CSD call or a GPRS connection and TA is in command mode, ATO causes the TA to resume the data or GPRS connection and takes you back to data mode or PPP online mode. Parameter Description <n>(num) [0] MC55_ATC_V04.00 Confidential / Released Switch from command mode to data mode Page 143 of 475 3/17/06 7.17 +++ Switch from data mode to command mode Syntax Exec Command +++ Response(s) OK Reference(s) V.250 PIN ! ASC0 ASC1 % § MUX1 MUX2 ! ! MUX3 Charge ! ! ! Last ! Command Description This command is only available during a CSD call or a GPRS connection. The +++ character sequence causes the TA to cancel the data flow over the AT interface and switch to command mode. This allows you to enter AT commands while maintaining the data connection to the remote device or, accordingly, the GPRS connection. To prevent the +++ escape sequence from being misinterpreted as data, it must be preceded and followed by a pause of at least 1000 ms. The +++ characters must be entered in quick succession, all within 1000 ms. Notes • To return from command mode to data or PPP online mode: Enter ATO. • In Multiplex mode the +++ sequence does not work. Therefore, if required in Multiplex mode, the escape sequence needs to be implemented in the customer's external Multiplex application. Design solutions, for example using the DTR signal or a modem status command (MSC), can be found in [5], Section "Escape Sequence". See also Section 4.8, AT+CMUX. • On ASC1 the +++ sequence can be used in GPRS connections for switching from PPP online to command mode. MC55_ATC_V04.00 Confidential / Released Page 144 of 475 3/17/06 7.18 AT+CBST Select bearer service type The AT+CBST write command selects the bearer service <name>, the data rate <speed> and the connection element <ce> to be used when data calls are originated. The settings also apply to mobile terminated data calls, especially when single numbering scheme calls or calls from analog devices are received (see AT+CSNS). See GSM 02.02[1] for a list of allowed combinations of subparameters. Syntax Test Command AT+CBST=? Response(s) +CBST: (list of supported<speed>s), (list of supported<name>s), (list of supported<ce>s) OK Read Command AT+CBST? Response(s) +CBST: <speed>, <name>, <ce> OK Write Command AT+CBST=<speed>[, <name>[, <ce>]] Response(s) OK ERROR Reference(s) PIN GSM 07.07 ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Parameter Description <speed>(num)(&W)(&V) 0 Autobauding 4 2400 bps (V.22bis) 6 4800 bps (V.32) (&F) [7] 9600 bps (V.32) 14 14400 bps (V.34) 68 2400 bps (V.110) 70 4800 bps (V.110) 71 9600 bps (V.110) 75 14400 bps (V.110) <name>(num)(&W) 0(&F) Asynchronous modem <ce>(num)(&W) Transparent mode is not supported. 1(&F) MC55_ATC_V04.00 Confidential / Released Non-transparent Page 145 of 475 3/17/06 7.19 AT+CRLP Select radio link protocol parameters for originated non-transparent data calls The AT+CRLP write command sets radio link protocol (RLP) parameters used when non-transparent data calls are originated. The read command returns the current settings for the supported RLP version 0. Syntax Test Command AT+CRLP=? Response(s) +CRLP: (list of supported<iws>s), (list of supported<mws>s), (list of supported<T1>s), (list of supported<N2>s) OK Read Command AT+CRLP? Response(s) +CRLP: <iws>, <mws>, <T1>, <N2> OK Write Command AT+CRLP=[<iws>[, <mws>[, <T1>[, <N2>]]]] Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN GSM 07.07 ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Parameter Description <iws>(num)(&W)(&V) Interworking window size (IWF to MS) 0...61(&F) <mws>(num)(&W)(&V) Mobile window size (MS to IWF) 0...61(&F) <T1>(num)(&W)(&V) Acknowledgement timer (T1 in 10 ms units) 48...[78](&F)...255 <N2>(num)(&W)(&V) Re-transmission attempts N2 1...6(&F)...255 MC55_ATC_V04.00 Confidential / Released Page 146 of 475 3/17/06 7.20 AT+CLCC List current calls of ME The execute command returns a list of current calls of ME. If command is successful, but no calls are available, no information response is sent to TE. Syntax Test Command AT+CLCC=? Response(s) OK Exec Command AT+CLCC Response(s) [+CLCC: <idx>, <dir>, <stat>, <mode>, <mpty>[, <number>, <type>[, <alpha>]]] [+CLCC: <idx>, <dir>, <stat>, <mode>, <mpty>[, <number>, <type>[, <alpha>]]] [+CLCC: ...] OK ERROR +CME ERROR Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <idx>(num) Call identification number as described in GSM02.30 subclause 4.5.5.1; this number can be used in AT+CHLD command operations <dir>(num) 0 Mobile originated call (MOC) 1 Mobile terminated call (MTC) <stat>(num) State of the call 0 Active 1 Held 2 Dialing (MOC) 3 Alerting (MOC) 4 Incoming (MTC) 5 Waiting (MTC) <mode>(num) Bearer/teleservice 0 Voice 1 Data 2 Fax MC55_ATC_V04.00 Confidential / Released Page 147 of 475 3/17/06 3 Voice followed by data, voice mode (only in connection with single numbering scheme AT+CSNS) 4 Alternating voice/data, voice mode (only in connection with single numbering scheme AT+CSNS) 5 Alternating voice/fax, voice mode (only in connection with single numbering scheme AT+CSNS) 6 Voice followed by data, data mode (only in connection with single numbering scheme AT+CSNS) 7 Alternating voice/data, data mode (only in connection with single numbering scheme AT+CSNS) 8 Alternating voice/fax, fax mode (only in connection with single numbering scheme AT+CSNS) 9 Unknown <mpty>(num) 0 Call is not one of multiparty (conference) call parties 1 Call is one of multiparty (conference) call parties <number>(str) Phone number in format specified by <type> <type>(num) Type of address octect 145 Dialing string <number> includes international access code character '+' 129 Otherwise <alpha>(str)(+CSCS) Alphanumeric representation of <number> corresponding to the entry found in phonebook; used character set should be the one selected with command AT+CSCS (Select TE Character Set). The maximum displayed length of <alpha> is 16 characters. If <alpha> has more than 16 characters, only the first 15 characters are displayed. To indicate an overflow, a special character will be used as the 16th character. This is a space if the character set selected with AT+CSCS is 'GSM', or 'E400' if the character set is 'UCS2'. Due to time constraints on the necessary evaluation of the phonebook, this parameter may show a default value in early call phases (e.g. for <stat>= ''dialing'', ''incoming'' or ''alerting''), even if a phonebook entry is present for the number concerned. Note • Teleservices other than voice, data, fax are not fully supported by ME. They are used only in connection with the handling for AT+CSNS, and may therefore occur in parameter <mode> for mobile terminated calls. MC55_ATC_V04.00 Confidential / Released Page 148 of 475 3/17/06 7.21 AT^SLCC Siemens defined command to list current calls of ME AT^SLCC covers essentially the same information as GSM 07.07 command AT+CLCC, with the following additions: • The execute command response contains an additional parameter <traffic channel assigned> indicating whether the call has been assigned a traffic channel by the network (transmission of data or inband information is possible). • The additional write command allows to activate Event reporting for the list of current calls. If event reporting is active for an interface, a call status transition (cf. Call Status Information) and (if desired) the assignment of a traffic channel will generate an event report indication to this interface. In order to receive this event report as an URC, the URC presentation mode for this interface has to be configured with AT+CMER. The frequency of event report generation can be configured with AT command AT^SCFG. Refer to Call Status Information for further detail on the configuration options. • The additional read command allows to determine the event reporting mode <n> which indicates whether the interface receives event report indications for the list of current calls. Mind that the URC will be displayed only if the URC presentation mode for the interface concerned has been configured with AT+CMER. Syntax Test Command AT^SLCC=? Response(s) ^SLCC: (list of supported<n>s) OK Read Command AT^SLCC? Response(s) ^SLCC: <n> OK Exec Command AT^SLCC Response(s) [^SLCC:<idx>, <dir>, <stat>, <mode>, <mpty>, <traffic channel assigned>[, <number>, <type>[, <alpha>]]] [^SLCC:<idx>, <dir>, <stat>, <mode>, <mpty>, <traffic channel assigned>[, <number>, <type>[, <alpha>]]] [^SLCC:...] OK ERROR +CME ERROR Write Command AT^SLCC=[<n>] Response(s) OK ERROR +CME ERROR: <err> Reference(s) Siemens MC55_ATC_V04.00 Confidential / Released PIN % ASC0 ASC1 % Page 149 of 475 % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! 3/17/06 Unsolicited Result Code Unsolicited Call Status information if the list of current calls is empty: ^SLCC: if one or more calls are currently in the list: ^SLCC: <idx>, <dir>, <stat>, <mode>, <mpty>, <traffic channel assigned>[, <number>, <type>[, <alpha>]] [^SLCC: <idx>, <dir>, <stat>, <mode>, <mpty>, <traffic channel assigned>[, <number>, <type>[, <alpha>]]] [... ] ^SLCC: URC "^SLCC" displays the list of current calls as displayed with the execute command AT^SLCC. The list is displayed in the state it has at the time of display, not in the state it had when the signal was generated. The URC's occurrence indicates call status changes for any of the calls in the list of current calls. Please refer to Call Status Information and AT^SCFG for further information about the configuration of this URC. Event reporting can be enabled separately for each interface. Interface settings are saved with AT&W and can be displayed with AT&V. Additionally, The URC presentation mode for the interface must be configured with AT+CMER. Depending on the value of AT^SCFG setting <sucs>, Indicator "^SLCC" will be issued (if configured with write command AT^SLCC and AT+CMER) • when a state transition ends in state "active" or in state "unknown" (if AT^SCFG setting <sucs>="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 AT^SCFG setting <sucs>="verbose"). If multiple displays of identical list configurations occur, this happens because of short intermediate states of the list, that have already been overridden by new transitions and states. Thus, it is guaranteed that the configuration displayed is always the current configuration at the time of the last display. The list of active calls displayed with this URC will always be terminated with an empty line preceded by prefix ''^SLCC: '', in order to indicate the end of the list. Command Description The read command returns an indication whether event reporting is active for the current interface. The exec command returns a list of current calls of ME. If command is successful, but no calls are available, no information response is sent to TE. Use the write command to activate or deactivate event reporting for URC "^SLCC". Event reporting can be enabled separately for each interface. Interface settings are saved with AT&W and can be displayed with AT&V. Parameter Description <idx>(num) call identification number as described in GSM02.30 subclause 4.5.5.1; this number can be used in AT+CHLD command operations <n>(num)(&W)(&V) [0](&F) presentation of URC "^SLCC" disabled 1 presentation of URC "^SLCC" enabled <dir>(num) 0 mobile originated call (MOC) 1 mobile terminated call (MTC) MC55_ATC_V04.00 Confidential / Released Page 150 of 475 3/17/06 <stat>(num) state of the call 0 active 1 held 2 dialing (MOC) 3 alerting (MOC) 4 incoming (MTC) 5 waiting (MTC) 6 terminating: The call is not active anymore, but inband information is still available. 7 dropped: The call has been suspended by the network, but may be resumed later. <mode>(num) bearer/teleservice 0 voice 1 data 2 fax 3 voice followed by data, voice mode (only in connection with single numbering scheme AT+CSNS) 4 alternating voice/data, voice mode (only in connection with singlenumbering scheme AT+CSNS) 5 alternating voice/fax, voice mode (only in connection with single numbering scheme AT+CSNS) 6 voice followed by data, data mode (only in connection with single numbering scheme AT+CSNS) 7 alternating voice/data, data mode (only in connection with single numbering scheme AT+CSNS) 8 alternating voice/fax, fax mode (only in connection with single numbering scheme AT+CSNS) 9 unknown <mpty>(num) 0 call is not one of multiparty (conference) call parties 1 call is one of multiparty (conference) call parties <traffic channel assigned>(num) 0 no traffic channel is available to the call 1 mobile has been assigned a traffic channel It is now possible to send or receive inband information, e.g. to send DTMF tones (cf. AT+VTS), or to receive network announcements. <number>(str) phone number in format specified by <type> MC55_ATC_V04.00 Confidential / Released Page 151 of 475 3/17/06 <type>(num) type of address octect 145 dialing string <number> includes international access code character '+' 129 otherwise <alpha>(str) Alphanumeric representation of <number> corresponding to the entry found in phonebook; used character set should be the one selected with command AT+CSCS (Select TE Character Set). The maximum displayed length of <alpha> is 16 characters. If <alpha> has more than 16 characters, only the first 15 characters will be displayed. To indicate an overflow, a special character will be used as the 16th character. This will be a space if the character set selected with AT+CSCS is 'GSM', or 'E400' if the character set is 'UCS2'. Due to time constraints on the necessary evaluation of the phonebook, this parameter may show a default value during early call phases (e.g. for <stat>= ''dialing'', ''incoming'' or ''alerting''), even if a phonebook entry is present for the number concerned. Notes • Teleservices other than voice, data, fax are not fully supported by ME. They are used only in connection with the handling for AT+CSNS, and may therefore occur in parameter <mode> for mobile terminated calls. • If a URC "^SLCC" in verbose mode (see AT^SCFG) has been buffered while the interface was in dedicated mode (depending on the settings of AT+CMER parameter <bfr>), each buffered event indicator will be output as a separate URC after the interface returns to idle mode. However, the output will deliver the list of current calls in the "current" state (at the time when the output is generated), possibly leading to multiple displays of identical list configurations. • Some parameters of AT command AT+CHLD, as well as some situations where the call status in the network changes very quickly (e.g. the transition between <stat>= ''unknown'', ''dialing'' and ''alerting'' for a call to a reachable subscriber within the registered network) may lead to quasi-simultaneous changes to the states of one or several calls in the list, possibly leading to multiple displays of identical list configurations. • If multiple displays of identical list configurations occur, this happens because of intermediate states of the list, that have already been overridden by new transitions and states. Thus, it is guaranteed that the configuration displayed in such cases is the current configuration at the time of the last display. • It is adviseable to receive URC "^SLCC" on an interface that is not used for call initiation, if verbose output is configured. If only voice calls are expected, a setting of AT^SM20= 0 may be used alternatively in order to keep the call from blocking the interface. Examples EXAMPLE 1 ^SYSSTART at+cpin=9999 OK +CREG: 2 +CREG: 1,''0145'',''0016'' at^sm20=0 OK atd''1234567''; OK MC55_ATC_V04.00 Confidential / Released We are now registered command ''ATD'' for an outgoing voice call will terminate immediately with response ''OK'' We start a voice call. ''OK'' response is issued immediately because of setting ''^SM20=0'' Page 152 of 475 3/17/06 ^SLCC: 1,0,2,0,0,0,''1234567'',129,''Called Party'' ^SLCC: ^SLCC: 1,0,2,0,0,1,''1234567'',129,''Called Party'' ^SLCC: ^SLCC: 1,0,3,0,0,1,''1234567'',129,''Called Party'' ^SLCC: ^SLCC: 1,0,0,0,0,1,''1234567'',129,''Called Party'' ^SLCC: atd23456; OK ^SLCC: 1,0,1,0,0,0,''1234567'',129,''Called Party'' ^SLCC: 2,0,2,0,0,1,"23456",129 ^SLCC: ^SLCC: 1,0,1,0,0,0,''1234567'',129,''Called Party'' ^SLCC: 2,0,2,0,0,1,"23456",129 ^SLCC: ^SLCC: 1,0,1,0,0,0,''1234567'',129,''Called Party'' ^SLCC: 2,0,3,0,0,1,"23456",129 ^SLCC: ^SLCC: 1,0,0,0,0,1,''1234567'',129,''Called Party'' ^SLCC: NO CARRIER ^SLCC: NO CARRIER MO call starts, paging B-party End of current list Traffic channel established, network may now transmit network announcements, ME may now transmit DTMF tones. End of current list Call is now ringing at B-Party End of current list B-Party has accepted the call, connection established End of current list We start a second voice call. ''OK'' response is issued immediately because another call is already active (cf. ATD) The active call is automatically put on hold, triggering the display of the list The second call has already started before the indication for the held call could be displayed End of current list The identical list is displayed again, triggered by the start of the second voice call The status of the second list entry has already been displayed with the previous URC End of current list The held call doesn't change status right now The second call is now alerting the B-Party End of current list The held call doesn't change status right now End of current list: the B-Party of the second call has not accepted the call in time, the second call has ended. The second call has ended list is now empty: B-Party has ended the first call The first call has ended EXAMPLE 2 ^SLCC: 1,1,4,0,0,1,''1234567'',129 ^SLCC: RING ^SLCC: 1,1,4,0,0,1,''1234567'',129 MC55_ATC_V04.00 Confidential / Released Incoming call is signalled. Display is triggered by the incoming call, but the current status of the call at the time of display already comprises an active traffic channel. End of current list Incoming call is signalled. The incoming call had a traffic channel assigned from the start. This second identical display is triggered by the traffic channel assignment. Since the traffic channel was already indicated in the previous URC, both instances of the URC contain identical information. Page 153 of 475 3/17/06 ^SLCC: RING ata OK ^SLCC: 1,1,0,0,0,1,''1234567'',129 ^SLCC: ath OK ^SLCC: MC55_ATC_V04.00 Confidential / Released End of current list Incoming call is signalled. Incoming call is accepted. call is established. The call is now active. End of current list Hang up the call. hang up complete. The list of current calls is empty again Page 154 of 475 3/17/06 7.22 AT+CR Service reporting control AT+CR configures the TA whether or not to transmit an intermediate result code +CR: <serv> to the TE when a call is being set up. Setting the value of <mode> to 1 may lead to connection failure, if the application (e.g. WinFax) waits for default result code/URC. Syntax Test Command AT+CR=? Response(s) +CR: (list of supported<mode>s) OK ERROR Read Command AT+CR? Response(s) +CR: <mode> OK ERROR Write Command AT+CR=<mode> Response(s) OK ERROR Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Intermediate Result Code If enabled, an intermediate result code is transmitted during connect negotiation when the TA has determined the speed and quality of service to be used, before any error control or data compression reports are transmitted, and before any final result code (e.g. CONNECT) appears. +CR: <serv> Parameter Description <mode>(num)(&W)(&V) 0(&F) Disable 1 Enable <serv>(str) "REL ASYNC" Asynchronous non-transparent "GPRS" GPRS MC55_ATC_V04.00 Confidential / Released Page 155 of 475 3/17/06 7.23 AT+CRC Set Cellular Result Codes for incoming call indication The AT+CRC command controls whether or not to use the extended format of incoming call indication. <mode>=1 may lead to connection failure, if the application (e.g. WinFax) waits for the default URC. Syntax Test Command AT+CRC=? Response(s) +CRC: (list of supported<mode>s) OK ERROR Read Command AT+CRC? Response(s) +CRC: <mode> OK ERROR Write Command AT+CRC=[<mode>] Response(s) OK ERROR Reference(s) PIN GSM 07.07 ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Unsolicited Result Codes URC 1 RING Indicates incoming call to the TE if <mode>=0. URC 2 +CRING: <type> Indicates incoming call to the TE if <mode>=1. Parameter Description <mode>(num)(&W)(&V) [0](&F) Disable extended format 1 Enable extended format <type>(str) "REL ASYNC" Asynchronous non-transparent "FAX" Facsimile "VOICE" Voice "GPRS" <PDP_type>, <PDP_addr> [,[<L2P>][,<APN>]] GPRS network request for PDP context activation MC55_ATC_V04.00 Confidential / Released Page 156 of 475 3/17/06 7.24 AT+CSNS Single Numbering Scheme The AT+CSNS command enables the ME to accept incoming calls when no bearer capability information is provided with the call, e.g. single numbering scheme calls or calls originating from analog devices. Syntax Test Command AT+CSNS=? Response(s) +CSNS: (list of supported<mode>s) OK Read Command AT+CSNS? Response(s) +CSNS: <mode> OK Write Command AT+CSNS=[<mode>] Response(s) OK ERROR +CME ERROR Reference(s) PIN GSM 07.07 ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <mode>(num) [0](D) Voice: Each call received without bearer element is assumed to be speech 2 Fax: Each call received without bearer element is assumed to be an incoming fax. 4 Data: Each call received without bearer element is assumed to be a data call. Please take into account that the bearer service parameters set with AT+CBST apply to all data calls including those received without bearer capability. Notes • The command must be set before the call comes. By default, when you do not modify the settings, all calls received without bearer element are assumed to be voice. • The setting will be saved when you power down the ME with AT^SMSO, provided that PIN authentication has been done. The saved value will be restored when the same SIM card is inserted and PIN authentication done again. If no SIM card or a different SIM card is inserted the default value 0 takes effect. MC55_ATC_V04.00 Confidential / Released Page 157 of 475 3/17/06 7.25 AT^SCNI List Call Number Information Syntax Test Command AT^SCNI=? Response(s) OK Exec Command AT^SCNI Response(s) ^SCNI: <id>1[,<cs>[,<number>,<type>]] ^SCNI: <id>2[,<cs>[,<number>,<type>]] [...] OK ERROR +CME ERROR: <err> Reference(s) PIN SIEMENS % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description TA returns a list of current calls of ME. Parameter Description <id>(num) call identification number as described in GSM 02.30[19] subclause 4.5.5.1; this number can be used in AT+CHLD command operations 1...7 <cs>(num) Call status of respective call number (first parameter) 0 call hold 1 call in progress 2 waiting call <number>(str) string type phone number in format specified by <type> <type>(num) type of address octet in integer format; 145 when dialling string includes international access code character "+", otherwise 129 Note • See also GSM 07.07: AT+CLCC MC55_ATC_V04.00 Confidential / Released Page 158 of 475 3/17/06 7.26 AT^SLCD Display Last Call Duration Syntax Test Command AT^SLCD=? Response(s) OK ERROR +CME ERROR Exec Command AT^SLCD Response(s) ^SLCD: <time> OK ERROR +CME ERROR Reference(s) PIN SIEMENS % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description TA returns last call duration or current call duration. Parameter Description <time>(str) Format is "hh:mm:ss", where characters indicate hours, minutes, seconds; E.g. 22:10:00 "22:10:00" Max value is 9999:59:59 Note • The proper working of that command is network dependant. MC55_ATC_V04.00 Confidential / Released Page 159 of 475 3/17/06 7.27 AT^STCD Display Total Call Duration Syntax Test Command AT^STCD=? Response(s) OK ERROR +CME ERROR Exec Command AT^STCD Response(s) ^STCD: <time> OK ERROR +CME ERROR Reference(s) PIN SIEMENS % ASC0 ASC1 % MUX1 MUX2 % % % MUX3 Charge % ! ! Last ! Command Description TA returns total call duration (accumulated duration of all calls). Parameter Description <time>(str) Format is "hh:mm:ss", where characters indicate hours, minutes, seconds; E.g. 22:10:00 "22:10:00" Max value is 9999:59:59 Notes • The Total Call Duration will not be reset by power off or other means. • The proper working of that command is network dependant and only for MO calls. MC55_ATC_V04.00 Confidential / Released Page 160 of 475 3/17/06 7.28 ATP Select pulse dialing Syntax Exec Command ATP Response(s) OK Reference(s) PIN V.250 ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Note • No effect for GSM. 7.29 ATT Select tone dialing Syntax Exec Command ATT Response(s) OK Reference(s) V.250 PIN ! ASC0 ASC1 % ! MUX3 Charge ! ! ! Last ! Note • No effect for GSM. MC55_ATC_V04.00 Confidential / Released Page 161 of 475 3/17/06 8. Network Service Commands The AT Commands described in this chapter are related to various network services. More commands related to this area can be found in Chapter 9., Supplementary Service Commands. 8.1 AT+COPN Read operator names The AT+COPN command returns the list of operator names from the ME. Each operator code <numericn> that has an alphanumeric equivalent <alphan> in the ME memory is returned. See also: AT^SPLM. Syntax Test Command AT+COPN=? Response(s) OK ERROR +CME ERROR Exec Command AT+COPN Response(s) +COPN: <numericn>, <alphan> +COPN: ... OK ERROR +CME ERROR Reference(s) PIN GSM 07.07 % ASC0 ASC1 % MUX1 MUX2 % % % MUX3 Charge % ! ! Last ! Parameter Description <numericn>(str) Operator in numeric format; GSM location area identification number. <alphan>(str) Operator in long alphanumeric format; can contain up to 16 characters. MC55_ATC_V04.00 Confidential / Released Page 162 of 475 3/17/06 8.2 AT+COPS Operator Selection AT+COPS queries the present status of the MC55's network registration and allows to determine whether automatic or manual network selection shall be used. Additional service is available with AT^SOPS. Three operator selection modes are available: • Automatic MC55 searches for the home operator automatically. If successful the MC55 registers to the home network. If the home network is not found, MC55 goes on searching. If a permitted operator is found, MC55 registers to this operator. If no operator is found the MC55 remains unregistered. • Manual Desired operator can be determined using the AT+COPS write command. If the operator is found, MC55 registers to it immediately. If the selected operator is forbidden, the MC55 remains unregistered. • Manual/automatic The ME first tries to find the operator determined via AT+COPS write command. If the ME fails to register to this operator, then it starts to select another (permitted) operator automatically. The AT+COPS test command lists sets of four parameters, each representing an operator present in the network. A set consists of • an integer indicating the availability of the operator, • long alphanumeric format of the operator's name and • numeric format representation of the operator. Any of the parameters may be unavailable and will then be an empty field (,,). The list of operators comes in the following order: Home network, networks referenced in SIM and other networks. The operator list is followed by a list of the supported <mode>s and <format>s. These lists are delimited from the operator list by two commas. If the test command is used during an ongoing GPRS transfer, traffic will be interrupted for up to one minute. The AT+COPS read command returns the current <mode> and the currently selected operator. If no operator is selected, <format> and <oper> are omitted. The AT+COPS write command forces an attempt to select and register to the GSM network operator (see note below). If the selected operator is not available, no other operator will be selected (except <mode>=4). The selected operator name <format> will apply to further read commands, too. Command settings are effective over all serial interfaces of the MC55. Syntax Test Command AT+COPS=? Response(s) +COPS: [list of present operators (<opStatus>, long alphanumeric <oper>s,,numeric <oper>s ], , (list of supported <mode>s), (list of supported <format>s) OK ERROR +CME ERROR: <err> Read Command AT+COPS? Response(s) +COPS:<mode>[, <format>[, <oper>]] OK ERROR +CME ERROR: <err> MC55_ATC_V04.00 Confidential / Released Page 163 of 475 3/17/06 Write Command AT+COPS=<mode>[, <format>[, <oper>]] Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN GSM 07.07 § ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! Last ! ! Parameter Description <opStatus>(num) Status 0 Unknown 1 Operator available 2 Current operator 3 Operator forbidden <oper>(str) Operator If test command: Operator name in long alphanumeric format and numeric format. If read command: Operator name as per <format>. If write command: Operator name in numeric format. <mode>(num)(&V) Parameter values 0 and 1 are stored non-volatile in the MC55. 0(D) Automatic mode; <oper> field is ignored. 1 Manual operator selection Write command requires <oper> in numeric format, i.e. <format> shall be 2. Read command returns the current <mode> and the currently selected <oper>. If no operator is selected, <format> and <oper> are omitted. 2 Manually deregister from network and remain unregistered until <mode>=0 or 1 or 4 is selected. 3 Set only <format> (for AT+COPS read command). 4 Automatic / manual selection; if manual selection fails, automatic mode (<mode>=0) is entered (<oper> field will be present). <format>(num)(&W)(&V) 0(&F) Long alphanumeric format of <oper>. Can be up to 16 characters long. 2 Numeric format of <oper>. This is the GSM Location Area Identification (LAI) number, which consists of the 3-digit Mobile Country Code (MCC) plus the 2or 3-digit Mobile Network Code (MNC). MC55_ATC_V04.00 Confidential / Released Page 164 of 475 3/17/06 Note • It is not recommended to use the AT+COPS command before passing the CHV (card holder verification) / SIM PIN1 verification. This is because after PIN1 verification the module will automatically try to register to the network as though AT+COPS were 0, regardless of the settings done before with or without SIM, such as AT+COPS=2 which remains unchanged. Also, the test command should only be used after PIN1 authentication. MC55_ATC_V04.00 Confidential / Released Page 165 of 475 3/17/06 8.3 AT^SOPS Extended Operator Selection AT^SOPS queries the present status of the MC55's network registration. Since basic operator selection services are available with AT+COPS this command uses the methods of the Enhanced Operator Name String (EONS) specification while handling operator name strings. Additional EONS related information is available with AT^SIND. AT^SOPS test command lists sets of five parameters, each representing an operator present in the network. A set consists of 1. an integer indicating the availability of the operator, 2. specification of the source of the operator name <eonsOperator>, 3. operator name according to EONS Table, 4. Service Provider Name from the SIM Service Table and 5. numeric format representation of the operator. Any of the parameters may be unavailable and will then be an empty field (,,). The list of operators comes in the following order: Home network, networks referenced in SIM and other networks. After the operator list the MC55 returns lists of supported <mode>s and <format>s. These lists are delimited from the operator list by two commas. If the test command is used while an ongoing GPRS transfer, traffic will be interrupted for up to one minute. Command settings are effective over all serial interfaces of the MC55. Syntax Test Command AT^SOPS=? Response(s) ^SOPS:[list of present operator( <opStatus>, <eonsType>, <eonsOperator>, <servProvider>, <opName>)s ], , (list of supported <mode>)s, (list of supported <format>)s OK ERROR +CME ERROR: <err> Reference(s) PIN SIEMENS % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <opStatus>(num) Status 0 unknown 1 operator available 2 current operator 3 operator forbidden <eonsType>(num) Specification of the source of the operator name <eonsOperator>. Details of EONS-supplied operator name types are available at AT^SIND. MC55_ATC_V04.00 Confidential / Released Page 166 of 475 3/17/06 <eonsOperator> Operator name; format depends on the source of the operator name, specified by <eonsType>. <servProvider>(str) Service Provider Name according to setting of Service No. 17 in the SIM Service Table (EFSST). <opName> Operator Operator name in numerical presentation contains the GSM Location Area Identification (LAI) number, which consists of the 3-digit Mobile Country Code (MCC) plus the 2- or 3-digit Mobile Network Code (MNC). Parameter is stored non-volatile to the SIM. <mode>(num) Parameter is not applicable. <format>(num) Parameter is not applicable. Note • The AT^SOPS Test command is only accepted by the module after a valid pin has been entered. MC55_ATC_V04.00 Confidential / Released Page 167 of 475 3/17/06 8.4 AT+CREG Network registration The AT+CREG command serves to verify the network registration status of the ME. For this purpose two types of URCs are available. The AT+CREG read command returns the URC presentation mode <n> and an integer <stat> that shows the registration status of the ME. The location information elements <lac> and <ci> are returned only when <n>=2 and ME is registered to the network. Syntax Test Command AT+CREG=? Response(s) +CREG: (list of supported<n>s) OK Read Command AT+CREG? Response(s) +CREG: <n>, <stat>[, <lac>, <ci>] OK ERROR +CME ERROR: <err> Write Command AT+CREG=[<n>] Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN GSM 07.07 ! ASC0 ASC1 % MUX1 MUX2 % % % MUX3 Charge % ! Last ! ! Unsolicited Result Codes URC 1 If <n>=1 and there is a change in the ME network registration status: +CREG: <stat> URC 2 If <n>=2 and there is a change in the ME network registration status or a change of the network cell: +CREG: <stat>[, <lac>, <ci>] Parameter Description <n>(num)(&W)(&V) [0](&F) Disable +CREG URC 1 Enable URC +CREG:<stat> to report status of network registration 2 Enable URC +CREG:<stat>[,<lac>,<ci>] to report status of network registration including location information. Optional parameters <lac> and <ci> will not be displayed during calls or if these values have not changed since last AT+CREG read command or since last indication by +CREG URC. MC55_ATC_V04.00 Confidential / Released Page 168 of 475 3/17/06 <stat>(num)(&V) 0 Not registered, ME is currently not searching for new operator There is a technical problem. User intervention is required. Yet, emergency calls can be made if any network is available. Probable causes: • no SIM card available • no PIN entered • no valid Home PLMN entry found on the SIM 1 Registered to home network 2 Not registered, but ME is currently searching for a new operator The ME searches for an available network. Failure to log in until after more than a minute may be due to one of the following reasons: • No network available or insufficient Rx level. • The ME has no access rights to the networks available. • Networks from the SIM list of allowed networks are around, but login fails due to one of the following reasons: - #11 ... PLMN not allowed - #12 ... Location area not allowed - #13 ... Roaming not allowed in this location area After this, the search will be resumed (if automatic network search is enabled). • The Home PLMN or an allowed PLMN is available, but login is rejected by the cell (reasons: Access Class or LAC). If at least one network is available, emergency calls can be made. 3 Registration denied • If automatic network search is enabled: Authentication or registration fails after Location Update Reject due to one of the following reasons: - #2 ... IMSI unknown at HLR - #3 ... Illegal MS - #6 ... Illegal ME Either the SIM or the MS or the ME are unable to log into any network. User intervention is required. Emergency calls can be made, if any network is available. • Only if manual network search is enabled: Manual registration fails after Location Update Reject due to the following reasons: - #2 ... IMSI unknown at HLR - #3 ... Illegal MS - #6 ... Illegal ME - #11 ... PLMN not allowed - #12 ... Location area not allowed - #13 ... Roaming not allowed in this location area No further attempt is made to search or log into a network. Emergency calls can be made if any network is available. 4 Unknown (not used) 5 Registered, roaming The ME is registered at a foreign network (national or international network) MC55_ATC_V04.00 Confidential / Released Page 169 of 475 3/17/06 <lac>(str) Two byte location area code in hexadecimal format (e.g. "00C3" equals 193 in decimal). <ci>(str) Two byte cell ID in hexadecimal format. Example AT+CREG=2 OK AT+COPS=0 OK +CREG: 2 +CREG: 1,"0145","291A" MC55_ATC_V04.00 Confidential / Released Activates extended URC mode. Forces ME to automatically search network operator. URC reports that ME is currently searching. URC reports that operator has been found. Page 170 of 475 3/17/06 8.5 AT+CSQ Signal quality The AT+CSQ execute command indicates the received signal strength <rssi> and the channel bit error rate <ber>. Syntax Test Command AT+CSQ=? Response(s) +CSQ: (list of supported<rssi>s), (list of supported<ber>s) OK Exec Command AT+CSQ Response(s) +CSQ: <rssi>,<ber> OK Reference(s) PIN GSM 07.07 ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <rssi>(num) 0 -113 dBm or less 1 -111 dBm 2..30 -109... -53 dBm 31 -51 dBm or greater 99 not known or not detectable <ber>(num) To check the bit error rate there must be a call in progress to obtain realistic values. If no call is set up, there is no BER to be determined. In this case the indicated value may be 0 or 99, depending on the SIM card. 0..7 as RXQUAL values in the table in GSM 05.08 section 8.2.4. 99 not known or not detectable Note • After using network related commands such as AT+CCWA, AT+CCFC, AT+CLCK, users are advised to wait 3s before entering AT+CSQ. This is recommended to be sure that any network access required for the preceding command has finished. MC55_ATC_V04.00 Confidential / Released Page 171 of 475 3/17/06 8.6 AT^SMONC Cell Monitoring The AT^SMONC execute command delivers cell information containing 9 values from a maximum of 7 base stations. The first base station is the serving cell. Syntax Test Command AT^SMONC=? Response(s) OK ERROR +CME ERROR Exec Command AT^SMONC Response(s) ^SMONC: <MCC>1, <MNC>1, <LAC>1, <cell>1, <BSIC>1, <chann>1, <RSSI>1, <C1>1, <C2>1, <MCC>2, <MNC>2, <LAC>2, <cell>2, <BSIC>2, <chann>2, <RSSI>2, <C1>2, <C2>2, ... OK ERROR +CME ERROR Reference(s) PIN SIEMENS, 3GPP TS 05.08 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <MCC>(num) Mobile country code 3 digits, e.g. 232 000 Not decoded <MNC>(num) Mobile network code 2 digits or 3 digits, e.g. 07 or 003 000 Not decoded <LAC>(num) Location area code 4 hexadecimal digits, e.g. 4EED 0000 Not decoded <cell>(num) Cell identifier 4 hexadecimal digits, e.g. 4EAF 0000 MC55_ATC_V04.00 Confidential / Released Not decoded Page 172 of 475 3/17/06 <BSIC>(num) Base station identity code 2 digits, e.g. 32 00 Not decoded <chann>(num) ARFCN (Absolute Frequency Channel Number) 0 Not decoded. In this case, all remaining parameters related to the same channel are neither decoded. For example, a non-existing cell appears as follows: 000,000,0000,0000,00,0,0,-,- <RSSI>(num) Received signal level of the BCCH carrier (0..63). The indicated value is composed of the measured value in dBm plus an offset. This is in accordance with a formula specified in 3GPP TS 05.08 <C1>(num) Coefficient for base station reselection, e.g. 30. In dedicated mode, under certain conditions the parameter cannot be updated. In such cases a '-' is presented. <C2>(num) Coefficient for base station reselection, e.g. 30. In dedicated mode, under certain conditions the parameter cannot be updated. In such cases a '-' is presented. Note • To some extent, the cell monitoring commands AT^MONI, AT^MONP and AT^SMONC cover the same parameters. The receiving level, for example, can be queried with all three commands. Yet the resulting values may be slightly different, even though obtained over a time period of a few seconds. This is quite normal and nothing to worry about, as the cell information is permanently updated. MC55_ATC_V04.00 Confidential / Released Page 173 of 475 3/17/06 8.7 AT^SMOND Cell Monitoring The AT^SMOND execute command can be used to obtain status information of the service cell and up to six neighbour cells. The advantage over other cell monitoring commands is that AT^SMOND delivers more detailed information about the received signal strength. Syntax Test Command AT^SMOND=? Response(s) OK ERROR +CME ERROR Exec Command AT^SMOND Response(s) ^SMOND: [<sci>][, <nci>][, <TA>][, <rssiber>] OK ERROR +CME ERROR Reference(s) PIN SIEMENS, 3GPP TS 05.08 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <sci>(str) Serving cell information (comma-separated, no cr/lf included) <MCC>,<MNC>,<LAC>,<cell>,<BSIC>,<chann>,<RxLev>,<RxLev>Full,<RxLev>Sub,<RxQual>,<RxQual >Full,<RxQual>Sub,<Timeslot> If no serving cell is found, unavailable values are omitted:" ,,,,,,<RxLev>,,,0,,,0" <nci>(str) Neighbour cell information for neighbour cell 1 through 6 (comma-separated, no cr/lf included) <MCC>1,<MNC>1,<LAC>1,<cell>1,<BSIC>1,<chann>1,<RxLev>1, (these parameters repeated for neighbour cells 2 through 6 with no CR/LF): ... <MCC>6,<MNC>6,<LAC>6,<cell>6,<BSIC>6,<chann>6,<RxLev>6 An unavailable cell appears as follows: " ,,,,,,0" <rssiber>(str) Values for RSSI and BER (comma-separated, no cr/lf included) <RSSI>,<BER> <MCC>(num) Mobile country code 3 digits, e.g. 232 000 MC55_ATC_V04.00 Confidential / Released Not decoded Page 174 of 475 3/17/06 <MNC>(num) Mobile network code 2 digits or 3 digits, e.g. 07 or 003 000 Not decoded <LAC>(num) Location area code 4 hexadecimal digits, e.g. 4EED 0000 Not decoded <cell>(num) Cell identifier 4 hexadecimal digits, e.g. 4EAF 0000 Not decoded <BSIC>(num) Base station identity code 2 digits, e.g. 32 00 Not decoded <chann>(num) ARFCN (Absolute Frequency Channel Number) <RxLev>(num) Received signal level in dBm <RxQual>(num) Received signal quality as defined in GSM05.08 <Timeslot>(num) Assigned timeslot. If mobile is in idle mode, timeslot 0 (BCCH timeslot) will be indicated. 0...8 Assigned timeslot <TA>(num) Timing advance for the serving cell, in bits. <RSSI>(num) Receive Level, with value 99 indicateing "not known or not detectable" 0...31 Signifies the RSSI range from -113dBm or less ("0") to -51dBm or greater ("31") in steps of -2dBm (e.g. "1" = -111 dBm, "2" = -109 dBm ..., "30" = 53dBm) <BER>(num) Bit Error rate, with value 99 indicating "not known or not detectable" 0...7 MC55_ATC_V04.00 Confidential / Released as RXQUAL values RXQUAL0 to RXQUAL7 in GSM 05.08 section 8.2.4 Page 175 of 475 3/17/06 Notes • To some extent, the cell monitoring commands AT^SMOND, AT^MONI, AT^MONP and AT^SMONC cover the same parameters. The receiving level, for example, can be queried with all three commands. Yet the resulting values may be slightly different, even though obtained over a time period of a few seconds. This is quite normal and nothing to worry about, as the cell information is permanently updated. • During a connection, not all of the neighbour cell information can be decoded. The following restrictions apply: - Information is updated only for neighbour cells that have already been visible at connection setup, and continue to be included in the list of cells. - New neighbour cells added to the list, for example after handover, cannot be displayed until the connection is released. Example at^smond ^SMOND:262,01,3008,6060,32,100,66,,,0,,,0, 262,01,3008,DDD1,35,92,80, 262,01,3008,,31,96,83, 262,01,3008,BFBE,35,27,86, 262,01,3008,,32,98,88, 262,01,3008,BB44,32,90,89, 262,01,3008,8307,31,22,93, 2,23,99 MC55_ATC_V04.00 Confidential / Released Execute command Line breaks inserted for readability in print Page 176 of 475 3/17/06 8.8 AT^MONI Monitor idle mode and dedicated mode The AT^MONI command supplies information of the serving/dedicated cell. There are two ways to retrieve the information: once on request by using the execute command or automatically every <period> seconds by using the write command. To stop the periodic presentation type "AT" or "at". Syntax Test Command AT^MONI=? Response(s) ^MONI:(list of supported <period>s) OK Exec Command AT^MONI Response(s) See: Section 8.8.1, AT^MONI responses OK Write Command AT^MONI=<period> Response(s) See: Section 8.8.1, AT^MONI responses OK ERROR +CME ERROR Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <period>(num) Display period in seconds 1...254 Notes • The two header lines (see Section 8.8.1, AT^MONI responses) are output after every ten data lines. • The length of following output lines exceeds 80 characters. Therefore a terminal program may draw a carriage return on a screen. However, this is not part of the response. • The parameters LAC and cell are presented as hexadecimal digits, the remaining parameters are composed of decimal digits. • If the radio cell changes during a connection, the parameters PWR, RXLev and C1 of the 'Serving Cell' part cannot be updated under certain conditions and therefore, are displayed as "-" (for conditions see also AT+CREG). This is because the MS does not update the cell selection and reselection parameters since, in this mode, they are not relevant for operation. When the connection ends, and the mobile is back to IDLE mode, correct values will be given. If the radio cell changes during a connection, it normally takes 1 or 2 seconds to update the parameters cell, NCC and BCC. Until the information is received from the new base station, the default values will be shown instead: cell="0000", NCC="-", BCC="-". • If the BS supports frequency hopping during a connection, the dedicated channel (parameter chann) is not stable. This mode is indicated by chann = 'h'. MC55_ATC_V04.00 Confidential / Released Page 177 of 475 3/17/06 • To some extent, the cell monitoring command AT^SMONC covers the same parameters. The receiving level, for example, can be queried with both commands. Yet the resulting values may be slightly different, even though obtained over a time period of a few seconds. This is quite normal and nothing to worry about, as the cell information is permanently updated. • For compatibility with earlier products and to support legacy applications, any input character may be used to stop the output in certain cases (depending on the settings of AT+IPR and AT+CMUX). 8.8.1 AT^MONI responses ME is not connected: a) ME is camping on a cell and registered to the network: Serving Cell chann rs dBm 1013 21 -71 MCC MNC LAC cell NCC BCC PWR RXLev 001 01 1001 0103 7 7 33 -105 I Dedicated channel C1 I chann TS timAdv PWR 33 I No connection dBm Q ChMod b) ME is camping on a cell but not registered to the network (only emergency call allowed): Serving Cell chann rs dBm 1013 21 -71 MCC MNC LAC cell NCC BCC PWR RXLev 001 01 1001 0103 7 7 33 -105 I Dedicated channel C1 I chann TS timAdv PWR 33 I Limited Service dBm Q ChMod c) ME camping on a cell, but searching for a better cell (cell reselection): Serving Cell chann rs dBm 1013 21 -71 MCC MNC LAC cell NCC BCC PWR RXLev 001 01 1001 0103 7 7 33 -105 I Dedicated channel C1 I chann TS timAdv PWR 33 I Cell Reselection dBm Q ChMod d) ME is searching and could not (yet) find a suitable cell: Serving Cell chann rs dBm Searching MCC MNC LAC cell NCC BCC PWR RXLev I Dedicated channel C1 I chann TS timAdv PWR dBm Q ChMod I Dedicated channel C1 I chann TS timAdv PWR 33 I 1015 1 0 5 dBm Q ChMod -76 0 S_HR ME is connected (Call in progress): Serving Cell chann rs dBm 1013 19 -76 MCC MNC LAC cell NCC BCC PWR RXLev 001 01 1001 0103 7 7 33 -105 Columns for Serving Cell: Column Description chann ARFCN (Absolute Frequency Channel Number) of the BCCH carrier rs RSSI value 0 - 63 (RSSI = Received signal strength indication) dBm Receiving level of the BCCH carrier in dBm MCC Mobile Country Code (first part of the PLMN code) MNC Mobile Network Code (second part of the PLMN code) LAC Location area code, see note below cell Cell ID NCC PLMN colour code BCC Base station colour code PWR Maximal power level used on RACH channel in dBm MC55_ATC_V04.00 Confidential / Released Page 178 of 475 3/17/06 Column Description RXLev Minimal receiving level (in dBm) to allow registration C1 Coefficient for base station selection Columns for Dedicated channel: Column Description chann ARFCN (Absolute Frequency Channel Number) of the TCH carrier Note: <chann> = h indicates frequency hopping. TS Timeslot number timAdv Timing advance in bits PWR Current power level dBm Receiving level of the traffic channel carrier in dBm Q Receiving quality (0-7) ChMod Channel mode (S_HR: Half rate, S_FR: Full rate, S_EFR: Enhanced Full Rate, A_HR: AMR Half rate, A_FR: AMR Full rate) 8.8.2 Service states Depending on the service state, an additional textual output is generated (refer also to the response examples): • • • • 'Searching' - The MS is searching, but could not (yet) find a suitable cell. This output appears after restart of the MS or after loss of coverage. 'No connection' - The MS is camping on a cell and registered to the network. The service state is 'idle', i.e. there is no connection established or a dedicated channel in use. 'Cell Reselection' - The MS has not yet lost coverage but is searching for a better cell, since the cell reselection criterion is fulfilled. 'Limited Service' - The MS is camping on a cell but not registered to the network. Only emergency calls are allowed. The MS enters this state, for example, when - no SIM card is inserted, or PIN has not been given, - neither Home PLMN nor any other allowed PLMN are found, - registration request was not answered or denied by the network (use command AT+CREG to query the registration status), - authentication failed. MC55_ATC_V04.00 Confidential / Released Page 179 of 475 3/17/06 8.9 AT^MONP Monitor neighbour cells The AT^MONP supplies information of up to six neighbour cells. There are two ways to retrieve the information: once on request by using the execute command or automatically every <period> seconds by using the write command. To stop the periodic presentation type "AT" or "at". Syntax Test Command AT^MONP=? Response(s) ^MONP:(list of supported <period>s) OK Exec Command AT^MONP Response(s) See: Section 8.9.1, AT^MONP responses OK Write Command AT^MONP=<period> Response(s) See: Section 8.9.1, AT^MONP responses OK ERROR +CME ERROR Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <period>(num) Display period in seconds 1...254 Notes • • Due to the fact that not all necessary information of the neighbour cells can be decoded during a connection, there are several constraints to be considered: - Only neighbour cells that have already been visible in IDLE mode will be further updated, as long as they are still included in the list. - Though new neighbour cells can be added to the list (e.g. due to handover), their C1 and C2 parameters cannot be displayed until the connection is released. In this case "-" is presented for C1 and C2. - To some extent, the cell monitoring command AT^SMONC covers the same parameters. The receiving level, for example, can be queried with both commands. Yet the resulting values may be slightly different, even though obtained over a time period of a few seconds. This is quite normal and nothing to worry about, as the cell information is permanently updated. For compatibility with earlier products and to support legacy applications, any input character may be used to stop the output in certain cases (depending on the settings of AT+IPR and AT+CMUX). MC55_ATC_V04.00 Confidential / Released Page 180 of 475 3/17/06 8.9.1 AT^MONP responses Response of AT^MONP (Example): chann 653 660 687 678 671 643 rs dBm 26 -84 20 -90 19 -91 14 -96 14 -96 10 -100 MCC MNC BCC 262 07 0 262 07 3 262 07 1 262 07 3 262 07 1 262 07 7 C1 22 16 15 10 10 6 C2 22 16 15 10 10 6 Column Description Chann ARFCN (Absolute Radio Frequency Channel Number) of the BCCH carrier rs RSSI value 0 - 63 (RSSI = Received signal strength indication) dBm Receiving level in dBm MCC Mobile Country Code (first part of the PLMN code) MNC Mobile Network Code (second part of the PLMN code) BCC Base Station colour code C1 cell selection criterion C2 cell reselection criterion MC55_ATC_V04.00 Confidential / Released Page 181 of 475 3/17/06 8.10 AT^SMONG GPRS Monitor The AT^SMONG command supplies GPRS specific cell information. There are two ways to retrieve the information: once on request by using the execute command or automatically every <period> seconds by using the write command. To stop the periodic presentation type "AT" or "at". Syntax Test Command AT^SMONG=? Response(s) ^SMONG:(list of supported <table>s), (list of supported <period>s) OK ERROR +CME ERROR Exec Command AT^SMONG Response(s) GPRS Monitor Cell Info Table (see: Section 8.10.1, AT^SMONG Cell Info Table) OK ERROR +CME ERROR Write Command AT^SMONG=<table>[, <period>] Response(s) ^SMONG: GPRS Monitor Cell Info Table (see: Section 8.10.1, AT^SMONG Cell Info Table) OK ERROR +CME ERROR Reference(s) PIN SIEMENS % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <table>(num) 1 Cell Info Table <period>(num) Display period in seconds If <period> is omitted the cell data will be presented only once on a single line (as if Execute command was issued). If <period> is given, the cell data will be listed repeatedly on 10 data lines. Every 10th data line is followed by the header, simply to repeat the column titles. 1...100 MC55_ATC_V04.00 Confidential / Released Page 182 of 475 3/17/06 Note • For compatibility with earlier products and to support legacy applications, often any input character will stop the periodic output of the write command. But since this applies only in certain cases (depending on the settings of AT+IPR and AT+CMUX), it is recommended to always use "at" or "AT". 8.10.1 AT^SMONG Cell Info Table Example output for AT^SMONG: GPRS Monitor BCCH G PBCCH 0637 1 - PAT MCC 4 234 MNC 05 NOM 2 TA 00 RAC 0B # Cell # Columns of the cell info table: Column Description BCCH ARFCN of BCCH carrier G GPRS available ("1") or not available ("-") in currently used cell PBCCH If PBCCH is present, indication of ARFCN, else ''-'' or if Frequency Hopping is used ''H'' PAT Priority Access Threshold (GSM Rec. 04.08 / 10.5.2.37b) 0 Packet access is not allowed in the cell 1 Spare, shall be interpreted as "000" (packet access not allowed) 2 Spare, shall be interpreted as "000" (packet access not allowed) 3 Packet access is allowed for priority level 1 4 Packet access is allowed for priority level 1 to 2 MCC Mobile Country Code MNC Mobile Network Code NOM Network Operation Mode (1...3) TA Timing Advance Value RAC Routing Area Code (as hexadecimal value) MC55_ATC_V04.00 Confidential / Released Page 183 of 475 3/17/06 8.11 AT^SALS Alternate Line Service The AT^SALS command is designed to support Alternate Line Service. This allows the subscriber to use two voice numbers on the same SIM card (service requires a dual line SIM card). The write command enables or disables the presentation of <view> and specifies the <line> used for outgoing calls. The read command returns the presentation mode of <view> and the currently selected <line>. Syntax Test Command AT^SALS=? Response(s) ^SALS:(list of supported <view>s), (list of supported <line>s) OK Read Command AT^SALS? Response(s) ^SALS: <view>, <line> OK ERROR Write Command AT^SALS=<view>[, <line>] Response(s) OK ERROR Reference(s) PIN SIEMENS % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Unsolicited Result Code If switched on with <view>=1: ^SALS: <line> Indicates the line used by an incoming call. Parameter Description <view>(num) Controls the presentation mode of the URC "^SALS" which indicates the line number used by an incoming call: 0(&F)(P) Disables indication of the called line 1 Enables indication of the called line <line>(num) Selects the line to be used for outgoing calls. Setting is global for the ME and non volatile. 1(&F)(D) ALS Line 1 2 ALS Line 2 Note • If a non ALS SIM is inserted, the <line> will be reset to line 1. MC55_ATC_V04.00 Confidential / Released Page 184 of 475 3/17/06 Example AT^SALS=1,1 RING ^SALS: 2 MC55_ATC_V04.00 Confidential / Released Line 1 has been selected for outgoing calls. "^SALS" URC is enabled. You receive a notification that you have an incoming call on line 2. Page 185 of 475 3/17/06 8.12 AT^SHOM Display Homezone The AT^SHOM returns the homezone state. The result is valid only, if network registration state <stat> is 1 (registered) (see AT+CREG). The feature is available only for supported network operators (Viag, One2One, Orange and LCI) and requires a suitable SIM card. If the homezone feature is not supported by the network operator or SIM card, result is always 0. Syntax Test Command AT^SHOM=? Response(s) OK Exec Command AT^SHOM Response(s) ^SHOM: <homezonestate> OK ERROR +CME ERROR: <err> Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <homezonestate>(num) 0 ME is out of Homezone 1 ME is within the Homezone MC55_ATC_V04.00 Confidential / Released Page 186 of 475 3/17/06 8.13 AT^SPLM Read the PLMN list The AT^SPLM execute command returns the list of operators from the ME. Each operator code <numeric> that has an alphanumeric equivalent <alpha> in the ME memory is returned. The list is sorted by operator codes. See also GSM 07.07: AT+COPN, AT+COPS Syntax Test Command AT^SPLM=? Response(s) OK If error is related to ME functionality: ERROR +CME ERROR: <err> Exec Command AT^SPLM Response(s) ^SPLM:<numeric>, long <alpha> ^SPLM:[... ] OK If error is related to ME functionality: ERROR +CME ERROR Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <numeric>(str) Operator in numeric form; GSM location area identification number <alpha>(str) Operator in long alphanumeric format; can contain up to 16 characters MC55_ATC_V04.00 Confidential / Released Page 187 of 475 3/17/06 8.14 AT+CPOL Preferred Operator List The AT+CPOL read command returns the list of the preferred operators. The AT+CPOL write command allows to edit the list of the preferred operators. If <index> is given but <operator> is left out, the entry is deleted. An operator can be only once in the list. Syntax Test Command AT+CPOL=? Response(s) +CPOL:(list of supported <index>s), (list of supported <format>s) OK ERROR +CME ERROR Read Command AT+CPOL? Response(s) +CPOL: <index>, <format>, <operator> +CPOL: ... OK ERROR +CME ERROR Write Command AT+CPOL=<index>[, <format>, <operator>] Response(s) OK ERROR +CME ERROR: Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <index>(num) The order number of the operator in the SIM preferred operator list. <format>(num) 2 Numeric format <operator>(str) Operator in numeric format (GSM Location Area Identification number which consists of a 3-digit country code plus a 2- or 3-digit network code). MC55_ATC_V04.00 Confidential / Released Page 188 of 475 3/17/06 8.15 AT^SPLR Read entry from the preferred operators list The AT^SPLR write command returns used entries from the SIM list of preferred operators with <indexa> between <index1> and <index2>. If <index2> is not given, only entry at <index1> is returned. The test command returns the whole index range supported by the SIM. See also GSM 07.07: AT+CPOL Syntax Test Command AT^SPLR=? Response(s) ^SPLR:(list of supported) <indexa>s OK ERROR +CME ERROR: <err> Write Command AT^SPLR=<index1>[, <index2>] Response(s) ^SPLR: <index1><oper> ^SPLR: <index2><oper> OK ERROR +CME ERROR: <err> Reference(s) PIN SIEMENS % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <index1>(num) Location number to start reading from <index2>(num) Location number where to stop reading <indexa>(num) Index range supported by the SIM card (between <index1> and <index2>) <oper>(str) Operator in numeric form; GSM location area identification number MC55_ATC_V04.00 Confidential / Released Page 189 of 475 3/17/06 8.16 AT^SPLW Write an entry to the preferred operators list The AT^SPLW write command writes an entry to the SIM list of preferred operators at location number <index>. If <index> is given but <oper> is left out, the entry is deleted. An operator can be only once in the list. Test command returns the whole index range supported by the SIM. See also GSM 07.07: AT+CPOL Syntax Test Command AT^SPLW=? Response(s) ^SPLW:(list of supported) <index>s OK ERROR +CME ERROR: Write Command AT^SPLW=<index>[, <oper>] Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN SIEMENS % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <index>(num) location number <oper>(str) Operator in numeric format (GSM Location Area Identification number which consists of a 3-digit country code plus a 2- or 3-digit network code). MC55_ATC_V04.00 Confidential / Released Page 190 of 475 3/17/06 9. Supplementary Service Commands The AT Commands described in this chapter are related to the Supplementary Services offered by the GSM network. 9.1 AT+CACM Accumulated call meter (ACM) reset or query Syntax Test Command AT+CACM=? Response(s) OK Read Command AT+CACM? Response(s) +CACM: <acm> OK ERROR +CME ERROR: <err> Write Command AT+CACM=[<passwd>] Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description The read command returns the current ACM value. The write command resets the Advice of Charge related to the accumulated call meter (ACM) value in SIM file EF(ACM). ACM contains the total number of home units for both the current and preceding calls. Parameter Description <acm>(str) Three bytes of the current ACM value in hexadecimal format (e.g. "00001E" indicates decimal value 30) 000000 - FFFFFF. <passwd>(str) SIM PIN2 MC55_ATC_V04.00 Confidential / Released Page 191 of 475 3/17/06 9.2 AT^SACM Advice of charge and query of ACM and ACMmax Syntax Test Command AT^SACM=? Response(s) ^SACM:(list of supported <n>s) OK Exec Command AT^SACM Response(s) ^SACM: <n>, <acm>, <acmMax> OK ERROR +CME ERROR: <err> Write Command AT^SACM=<n> Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN SIEMENS % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Unsolicited Result Code +CCCM: <ccm> When activated, an unsolicited result code is sent when the CCM value changes, but not more often than every 10 seconds. Command Description The execute command can be used to query the current mode of the Advice of Charge supplementary service, the SIM values of the accumulated call meter (ACM) and accumulated call meter maximum (ACMmax). The write command enables or disables the presentation of unsolicited result codes to report the call charges. Parameter Description <n>(num)(&W)(&V) [0](&F) suppress unsolicited result code 1 display unsolicited result code <acm>(str)(&V) Three bytes of the current ACM value in hexadecimal format (e.g. "00001E" indicates decimal value 30) 000000FFFFFF <acmMax>(str)(&V) Three bytes of the max. ACM value in hexadecimal format (e.g. "00001E" indicates decimal value 30) 000000 disable ACMmax feature 000001-FFFFFF MC55_ATC_V04.00 Confidential / Released Page 192 of 475 3/17/06 <ccm>(str) Three bytes of the current CCM value in hexadecimal format (e.g. "00001E" indicates decimal value 30); bytes are coded in the same way as ACMmax value in the SIM 000000-FFFFFF Notes • When you power down or reset the ME with AT+CFUN=1,1 the URC presentation mode will be reset to its default. To benefit from the URC it is recommended to have the setting included in the user profile saved with AT&W, or to select <n>=1 every time you reboot the ME. • See also GSM07.07: AT+CACM, AT+CAMM, AT+CAOC. MC55_ATC_V04.00 Confidential / Released Page 193 of 475 3/17/06 9.3 AT+CAMM Accumulated call meter maximum (ACMmax) set or query Syntax Test Command AT+CAMM=? Response(s) OK Read Command AT+CAMM? Response(s) +CAMM: <acmmax> OK ERROR +CME ERROR: <err> Write Command AT+CAMM=[<acmmax>[, <passwd>]] Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description The read command returns the current ACMmax value. The write command sets the Advice of Charge related to the accumulated call meter maximum value in SIM file EF (ACMmax). ACMmax contains the maximum number of home units allowed to be consumed by the subscriber. Parameter Description <acmmax>(str) Three bytes of the max. ACM value in hexadecimal format (e.g. "00001E" indicates decimal value 30) 000000 disable ACMmax feature 000001-FFFFFF. <passwd>(str) SIM PIN2 MC55_ATC_V04.00 Confidential / Released Page 194 of 475 3/17/06 9.4 AT+CAOC Advice of Charge information Syntax Test Command AT+CAOC=? Response(s) +CAOC: (list of supported<mode>s) OK Read Command AT+CAOC? Response(s) +CAOC: <mode> OK Exec Command AT+CAOC Response(s) ERROR +CME ERROR: <err> If <mode>=0, TA returns the current call meter value: +CAOC: <ccm> OK Write Command AT+CAOC=[<mode>] Response(s) ERROR +CME ERROR: <err> If <mode>=0, TA returns the current call meter value. OK Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description Execute command returns the current call meter value. The write command sets the Advice of Charge supplementary service function mode. Parameter Description <mode>(num)(&V) 0 query CCM value <ccm>(str) Three bytes of the current CCM value in hexadecimal format (e.g. "00001E" indicates decimal value 30); bytes are similarly coded as ACMmax value in the SIM 000000-FFFFFF. MC55_ATC_V04.00 Confidential / Released Page 195 of 475 3/17/06 9.5 AT+CCUG Closed User Group Syntax Test Command AT+CCUG=? Response(s) +CCUG:list of supported <n>, range of supported <index>, range of supported <info> OK ERROR +CME ERROR Read Command AT+CCUG? Response(s) +CCUG:<n>, <index>, <info> OK ERROR +CME ERROR Write Command AT+CCUG=[[<n>][, <index>][, <info>]] Response(s) OK ERROR +CME ERROR Reference(s) PIN GSM 07.07, GSM 02.85, GSM 03.85, GSM 04.85 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description The Test command returns the supported parameters. The Read command returns if the Explicit CUG invocation is activated (in parameter <n>), which CUG <index> is chosen, and if Preferential Group or Outgoing Access is suppressed (in parameter <info>). The write command serves to activate or deactivate the explicit CUG invocation, to set the desired index, and to specify if Preferential Group or Outgoing Access shall be suppressed. Parameter Description <n>(num) explicit CUG invocation options 0(D) Deactivate explicit CUG invocation 1 Activate explicit CUG invocation <index>(num) 0-9 10 (D) MC55_ATC_V04.00 Confidential / Released explicit selection of CUG index No index (preferred CUG taken from subscriber data) Page 196 of 475 3/17/06 <info>(num) state of the call 0(D) no information 1 suppress outgoing access 2 suppress preferential CUG 3 Suppress preferential CUG and Outgoing Access. Notes • The active settings for omitted parameters are retained without changes. • Explicit CUG invocation means that at each call setup, CUG information is added to the called number. • Upon delivery, settings are predefined with <n>=0, <index>=10, <info>=0. These delivery defaults cannot be recalled automatically. • When starting a call with ATD, Parameter 'G' or 'g' of command ATD will have no effect if the option selected for this single call is identical to the option already selected with AT+CCUG. • Current settings are saved in the ME automatically. • ATZ or AT&F do not influence the current settings. • some combinations of parameters may lead to rejection of CUG calls by the network. For more information, please consult GSM 04.85 MC55_ATC_V04.00 Confidential / Released Page 197 of 475 3/17/06 9.6 AT+CCFC Call forwarding number and conditions control AT+CCFC controls the call forwarding supplementary service. Registration, erasure, activation, deactivation and status query are supported. Syntax Test Command AT+CCFC=? Response(s) +CCFC:(list/range of supported <reason>s) OK Write Command AT+CCFC=<reason>, <mode>[, <number>[, <type>[, <class>[, <time>]]]] Response(s) If <mode> is not equal 2 and command successful: OK If <mode>= 2, <reason> is not equal 2 and command successful: +CCFC: <status>, <class>[, <number>, <type>] OK If <mode>= 2, <reason>= 2 and command successful: +CCFC: <status>, <class>[, <number>, <type>, <time>] OK If error is related to ME functionality +CME ERROR Reference(s) PIN GSM 07.07, GSM 02.04, GSM 02.82, GSM 03.82, GSM 04.82 % ASC0 ASC1 % MUX1 MUX2 % % % MUX3 Charge % ! ! Last ! Parameter Description <reason>(num) Reason for call forwarding 0 unconditional 1 mobile busy 2 no reply 3 not reachable 4 all call forwarding (includes reasons 0, 1, 2 and 3) 5 all conditional call forwarding (includes reasons 1, 2 and 3) <mode>(num) Network operation to be performed for Supplementary service "call forwarding" 0 disable call forwarding (disable service) 1 enable call forwarding (enable service) 2 query status of call forwarding (query service status) 3 register <number> and activate call forwarding (register service) 4 erase <number> and deactivate call forwarding (erase service) MC55_ATC_V04.00 Confidential / Released Page 198 of 475 3/17/06 <number>(str) String type phone number of forwarding address in format specified by <type>. If you select <mode>= 3, the phone <number> will be registered in the network. This allows you to disable / enable CF to the same destination without the need to enter the phone number once again. Depending on the services offered by the provider the registration may be mandatory before CF can be used. The number remains registered in the network until you register another number or erase it using <mode> = 4. <type>(num) Type of address octect 145 dialing string <number> includes international access code character '+' 129 otherwise <class>(num) Integer or sum of integers each representing a class of information, i.e. a bearer service, telecommunication service or bearer service group as defined in "GSM 02.04" 1 voice 2 data <class> 2 (data) comprises all those <class> values between 16 and 128, that are supported both by the network and the MS. This means, a setting made for <class> 2 applies to all remaining data classes (if supported). In addition, you can assign a different setting to a specific class. For example, you can activate Call Forwarding for all data classes, but deactivate it for a specific data class. 4 fax 8 SMS 16 data circuit sync 32 data circuit async 64 dedicated packet access 128 dedicated PAD access 1...[7]...255 combination of some of the above classes. For example, the default setting 7 represents the sum of the integers 1, 2 and 4 (CF for voice, data and fax). The value 255 covers all classes. If the <class> parameter is omitted, the default value 7 is used. <time>(num) 5...[20]...30 Time to wait before call is forwarded, rounded to a multiple of 5 sec. (only for <reason>=no reply) <status>(num) 0 Call Forwarding not active 1 Call Forwarding active Notes • You can register, disable, enable and erase <reason> 4 and 5 as described above. However, querying the status of <reason> 4 and 5 with AT+CCFC will result in an error ("CME error: Operation not supported"). As an alternative, you may use the ATD command followed by *'# codes to check the status of these two reasons. See Star-Hash (*#) Network Commands for a complete list of *# GSM codes. See also examples below. • Most networks will not permit registration of new parameters for conditional call forwarding (reasons 1,2,3,5) while unconditional call forwarding is enabled. • The AT+CCFC command offers a broad range of call forwarding options according to the GSM specifications. MC55_ATC_V04.00 Confidential / Released Page 199 of 475 3/17/06 However, when you attempt to set a call forwarding option which is not provisioned or not yet subscribed to, the setting will not take effect regardless of the response returned. The responses in these cases vary with the network (for example "OK", "Operation not allowed", "Operation not supported" etc.). To make sure check the call forwarding status with <mode>=2. • Some networks may choose to have certain call forwarding condtions permanently enabled (e.g. forwarding to a mailbox if the mobile is not reachable). In this case, erasure or deactivation of call forwarding for these conditions will not be successful, even if the CCFC request is answered with response "OK". • The command has been implemented with the full set of <class> parameters according to GSM 07.07. For actual applicability of SS "call forwarding" to a specific service or service group (a specific <class> value) please consult table A.1 of GSM 02.04. • There is currently no release of GSM standard "GSM 02.04", in which the "Call Forwarding" Supplementary Service is defined as applicable to SMS services. Example Please note that when you configure or query call forwarding without specifying any classes, the settings will refer to classes 1, 2 and 4 only (=default). The handling of classes is equivalent to AT+CLCK. • To register the destination number for unconditional call forwarding (CFU): at+ccfc=0,3,"+493012345678",145 OK The destination number will be registered for voice, data and fax services (default <class> 7). In most networks, the registration will also cause call forwarding to be activated for these <class> values. • To query the status of CFU without specifying <class>: at+ccfc=0,2 +CCFC: 1,1,"+493012345678",145 +CCFC: 1,2,"+493012345678",145 +CCFC: 1,4,"+493012345678",145 OK • To deactivate CFU without specifying <class>: at+ccfc=0,0 OK To check whether CFU was successfully deactivated (note that the destination number remains registered in the network when you disable CFU): at+ccfc=0,2 +CCFC: 0,1,"+493012345678",145 +CCFC: 0,2,"+493012345678",145 +CCFC: 0,4,"+493012345678",145 OK • To erase the registered CFU destination number: at+ccfc=0,4 OK Now, when you check the status, no destination number will be indicated: at+ccfc=0,2 +CCFC: 0,1 +CCFC: 0,2 +CCFC: 0,4 OK MC55_ATC_V04.00 Confidential / Released Page 200 of 475 3/17/06 • To query the status of CFU for all classes: at+ccfc=0,2,,,255 +CCFC: 0,1 +CCFC: 0,2 +CCFC: 0,4 +CCFC: 0,8 +CCFC: 0,16 +CCFC: 0,32 +CCFC: 0,64 +CCFC: 0,128 OK • <reason> 4 or 5 cannot be used to query the status of all call forwarding reasons (see also notes above): at+ccfc=4,2 +CME error: operation not supported at+ccfc=5,2 +CME error: operation not supported MC55_ATC_V04.00 Confidential / Released Page 201 of 475 3/17/06 9.7 AT+CCWA Call Waiting The AT+CCWA write command controls the "Call Waiting" supplementary service according to GSM 02.83. Activation, deactivation and status query are supported. The read command returns the current value of <n>. Syntax Test Command AT+CCWA=? Response(s) +CCWA:(list of supported <n>s) OK Read Command AT+CCWA? Response(s) +CCWA:<n> OK Write Command AT+CCWA=[[<n>][, <mode>][, <class>]] Response(s) If <mode> is not equal 2 and command successful: OK If <mode>= 2 and command successful: +CCWA: <status>, <class> [+CCWA: <status>, <class>] [+CCWA: ...] OK If error is related to ME functionality +CME ERROR Reference(s) GSM 07.07, GSM 02.04, GSM 02.83, GSM 03.83, GSM 04.83 PIN % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Unsolicited Result Codes URC 1 Indication of a call that is currently waiting and can be accepted. +CCWA: <calling number>, <type of number>, <class>, , <CLI validity> If <n>=1 and the call waiting supplementary service is enabled in the network, URC "+CCWA" indicates a waiting call to the TE. It appears while the waiting call is still ringing. URC 2 Indication of a call that has been waiting. ^SCWA If <n>=1 and the call waiting supplementary service is enabled in the network, this URC indicates that a waiting call rang when the ME was in online mode during a CSD call, but the calling party hung up before the ME went back to command mode. MC55_ATC_V04.00 Confidential / Released Page 202 of 475 3/17/06 Parameter Description <n>(num) Switch URCs "+CCWA" and "^SCWA" for call waiting on/off 0 Disable display of URCs "+CCWA" and "^SCWA" 1 Enable display of URCs "+CCWA" and "^SCWA" <mode>(num) Network operation to be performed for Supplementary service call waiting 0 Disable call waiting (disable service) 1 Enable call waiting (enable service) 2 Query status of call waiting (query service status) <class>(num) Integer or sum of integers each representing a class of information, i.e. a bearer service, telecommunication service or bearer service group as defined in "GSM 02.04". In the write command, parameter <class> specifies the class of the active call during which an incoming call of any class is to be regarded as a waiting call. In URC "+CCWA: <calling number>, <type of number>, <class>, , <CLI validity>", parameter <class> specifies the class of the waiting call. 1 Voice 2 Data <class> 2 (data) comprises all those <class> values between 16 and 128, that are supported both by the network and the MS. This means, a setting made for <class> 2 applies to all remaining data classes (if supported). In addition, you can assign a different setting to a specific class. For example, you can activate call waiting for all data classes, but deactivate it for a specific data class. 4 Fax [7] Voice, data and fax (1+2+4) 8 SMS 16 Data circuit sync 32 Data circuit async 64 Dedicated packet access 128 Dedicated PAD access 1...[7]...255 Combination of some of the above classes. For example, the default setting 7 represents the sum of the integers 1, 2 and 4 (CF for voice, data and fax). The value 255 covers all classes. If parameter "class"is omitted, the default value 7 is used. <status>(num) 0 Call waiting service is not active 1 Call waiting service is active <calling number>(str) Phone number of waiting caller in the format specified by parameter <type of number>. <type of number>(num) Type of address octet in integer format (refer to GSM 04.08, subclause 10.5.4.7) 145 MC55_ATC_V04.00 Confidential / Released <calling number> includes international access code character '+' Page 203 of 475 3/17/06 128 number restricted 129 Otherwise <CLI validity>(num) 0 CLI valid 1 CLI has been withheld 2 CLI is not available Notes • If the active call is a CSD call, and a waiting call is received, then the ME produces a BREAK while still in online mode, and displays - the +CCWA URC (as above) when the ME goes back to command mode while the waiting call is still active and can be accepted; - or the ^SCWA URC (as above) when the ME goes back to command mode after the waiting call has ended. • With the AT+CHLD command, it is possible to establish a multiparty call or to set the active voice call on hold and then accept a waiting voice call (not possible with fax and data call). See also AT+CHLD • Users should be aware that if call waiting is activated (<mode>=1), the presentation of URCs needs to be enabled, too (<n>=1). Otherwise, on the one hand, a waiting caller would be kept waiting due to lack of BUSY signals, while, on the other hand, the waiting call would not be indicated to the called party. • The AT+CCWA command offers a broad range of options according to the GSM specifications. However, when you attempt to enable call waiting for a <class> for which the service is not provisioned or not supported , the setting will not take effect regardless of the response returned. The responses in these cases vary with the network (for example "OK", "Operation not allowed", "Operation not supported" etc.). To make sure check the current call waiting settings with <mode>=2. • The AT+CCWA command has been implemented with the full set of <class> parameters according to GSM 07.07. For actual applicability of SS call waiting to a specific service or service group (a specific <class> value) please consult table A.1 of GSM 02.04 • Despite the specifications stated in GSM 02.04 call waiting is not handled uniformly among all networks: GSM 02.04, Annex A, provides the following specification: "The applicability of call waiting refers to the telecommunication service of the active call and not of the waiting call. The incoming, waiting, call may be of any kind." Nevertheless, networks do differ on the actual implementation of the service. For example, the activation of call waiting for <class> 4, "fax", causes some networks to send a call waiting indication if a call "of any kind" comes in during an active fax call, but others may (with the same settings active) indicate a waiting fax call during any kind of active call. Thus, the only reliable way to receive or prevent a call waiting indication under any circumstances and in any network, is to activate or deactivate call waiting for all tele- and bearer services (<class> 255). MC55_ATC_V04.00 Confidential / Released Page 204 of 475 3/17/06 Examples EXAMPLE 1 Parameter <n> at+ccwa=1 OK To enable the presentation of the URC EXAMPLE 2 Parameter <mode> at+ccwa=,1 OK at+ccwa=,2 at+ccwa=1,1 at+ccwa=1,2 at+ccwa=1,4 OK To activate the supplementary service in the network for voice, data, and fax calls (default classes). Note that parameter <n> is left out. In this case, the current value of <n> will be retained. To query the network status of call waiting for default classes Call Waiting is activated during voice calls. Call Waiting is activated during data calls. Call Waiting is activated during fax calls. EXAMPLE 3 Parameter <class> AT+CCWA=,0,1 OK MC55_ATC_V04.00 Confidential / Released To deactivate call waiting for voice calls. Page 205 of 475 3/17/06 9.8 AT+CHLD Call Hold and Multiparty Syntax Test Command AT+CHLD=? Response(s) +CHLD: (list of supported <n>s) OK Write Command AT+CHLD=[<n>] Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description TA controls the Supplementary Services Call Hold and Multiparty. Calls can be put on hold, recovered, released, and added to a conversation. Like for all Supplementary Services, the availability and detailed functionality of Call Hold and Multiparty services depends on the configuration of the GSM network. The MC55 can only request the service, but the network decides whether and how the request will be answered. Parameter Description <n>(num) 0 1 Release all held calls or set User Determined User Busy (UDUB) for a waiting call: • If a call is waiting, release the waiting call. The calling party will receive a "BUSY" indication (Supplementary Service User Determined User Busy "UDUB") • Otherwise, terminate all held calls (if any). Terminate all active calls (if any) and accept "the other call" as the active call: • If a call is waiting, the waiting call will be accepted. • Otherwise, if a held call is present, the held call becomes active. 1X Terminate a specific call X (X= 1-7). The call may be active, held or waiting. The remote party of the terminated call will receive a "NO CARRIER" indication. Parameter X is the call number <idx> of the targeted call in the list of current calls available with AT command AT+CLCC. 2 Place all active calls on hold (if any) and accept "the other call" as the active call: • If a call is waiting, the waiting call will be accepted. • Otherwise, if a held call is present, the held call becomes active. 2X Place all active calls except call X (X= 1-7) on hold. Parameter X is the call number <idx> of the targeted call in the list of current calls available with AT command AT+CLCC. 3 Add a held call to the active calls in order to set up a conference (multiparty) call. MC55_ATC_V04.00 Confidential / Released Page 206 of 475 3/17/06 Notes • The AT+CHLD command offers a broad range of options according to the GSM specifications. However, if you attempt to invoke an option which is not provisioned by the network, or not subscribed to, invocation of this option will fail. The responses in these cases may vary with the network (for example "Operation not allowed", "Operation not supported" etc.). • The handling of the supplementary service Call hold and Multiparty varies with the types of calls. This is because only voice calls can be put on hold, while data or fax calls cannot. The following procedures apply: With AT+CHLD=2 the user can simultaneously place a voice call on hold and accept another waiting voice, data or fax call. If the waiting call is a data or fax call, it is also possible to put the voice call on hold. To switch back from the active data or fax call to the held voice call the active call must be terminated with AT+CHLD=1. If all active and held calls are voice calls it is possible to switch back and forth with AT+CHLD=2. • In conflict situations, e.g. when a waiting call comes while there are already held calls, the above procedures apply to the waiting call only. For example, <n>=0 rejects the waiting call, but does not affect the held calls. • See also the AT+CCWA command for details on how to display waiting calls. Example ^SYSSTART at+cpin="9999" OK +CREG: 2 +CREG: 1,"0145","0016" at+ccwa=1,1,1 OK atd"1234567"; OK +CCWA: "+491791292364",145,32,,0 at+chld=2 CONNECT 9600/RLP hello +++ OK at+clcc +CLCC: 1,0,1,0,0,"03038639268",129 +CLCC: 2,1,0,1,0,"+491791292364",145 OK at+chld=1 The mobile is now registered. You activate the indication of waiting calls during voice calls. You make a voice call. You receive a URC indicating a waiting data call. You put the voice call on hold. The data connection is set up. With ''+++'' you go in command mode. You interrogate the status of all established calls. The active data call is terminated and the held voice call becomes active. OK at+clcc +CLCC: 1,0,0,0,0,"03038639268",129 OK MC55_ATC_V04.00 Confidential / Released Page 207 of 475 3/17/06 9.9 AT+CLIP Calling Line Identification Presentation This command refers to the GSM supplementary service CLIP (Calling Line Identification Presentation) that enables a called subscriber to get the calling line identity (CLI) of the calling party when receiving a mobile terminated call. The AT+CLIP write command enables or disables the presentation of the CLI at the TE. It has no effect on the execution of the supplementary service CLIP in the network. The AT+CLIP read command gives the status of <n>, and also triggers an interrogation of the provision status of the CLIP service according to GSM 02.81 (given in <m>). If no SIM card is available or the SIM-PIN is not entered, the command response is "ERROR". Syntax Test Command AT+CLIP=? Response(s) +CLIP: (list of supported<n>s) OK Read Command AT+CLIP? Response(s) +CLIP: <n>, <m> OK ERROR +CME ERROR: <err> Write Command AT+CLIP=<n> Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN GSM 07.07, GSM 02.81 § ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Unsolicited Result Codes URC 1 Voice call response format: +CLIP: <number>, <type>, , [, <alpha>][, <CLI validity>] URC 2 Data/FAX call response format: +CLIP: <number>, <type> When CLIP is enabled at the TE (and is permitted by the calling subscriber), this URC is delivered after every "RING" or "+CRING" URC when a mobile terminated call occurs. Parameter Description <n>(num)(&W)(&V) [0](&F) Suppress unsolicited result codes 1 Display unsolicited result codes MC55_ATC_V04.00 Confidential / Released Page 208 of 475 3/17/06 <m>(num)(&V) 0 CLIP not provisioned 1 CLIP provisioned 2 Unknown <number>(str) String type phone number of calling address in format specified by <type>. <type>(num) Type of address octet in integer format; 145 when dialing string includes international access code character "+", otherwise 129. <alpha>(str) String type alphanumeric representation of <number> corresponding to the entry found in phonebook; used character set is the one selected with AT+CSCS. <CLI validity>(num) 0 CLI valid 1 CLI has been withheld by the originator. 2 CLI is not available due to interworking problems or limitations of originating network. <number> shall be an empty string ("") and <type> value will not be significant. When CLI is not available ( <CLI validity>=2), <number> shall be an empty string ("") and <type> value will not be significant. Nevertheless, TA shall return the recommended value 128 for <type> (TON/NPI unknown in accordance with GSM 04.08 subclause 10.5.4.7). When CLI has been withheld by the originator, (<CLI validity>=1) and the CLIP is provisioned with the "override category" option (refer GSM 02.81 and GSM 03.81), <number> and <type> is provided. Otherwise, TA shall return the same setting for <number> and <type> as if the CLI was not available. MC55_ATC_V04.00 Confidential / Released Page 209 of 475 3/17/06 9.10 AT+CLIR Calling line identification restriction The AT+CLIR command refers to the GSM supplementary service CLIR (Calling Line Identification Restriction). Syntax Test Command AT+CLIR=? Response(s) +CLIR: (list of supported <n>s) OK Read Command AT+CLIR? Response(s) +CLIR<n>, <m> OK ERROR +CME ERROR: <err> Write Command AT+CLIR=[<n>] Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <n>(num) Parameter shows the settings for outgoing calls: [0](P) Presentation indicator is used according to the subscription of the CLIR service 1 CLIR invocation 2 CLIR suppression <m>(num) Parameter shows the subscriber CLIR service status in the network: 0 CLIR not provisioned 1 CLIR provisioned in permanent mode 2 Unknown (e.g. no network, etc.) 3 CLIR temporary mode presentation restricted 4 CLIR temporary mode presentation allowed Note • The settings made with AT+CLIR=1 or AT+CLIR=2 are used for all outgoing calls until the ME is switched off or AT+CLIR=0 is used. MC55_ATC_V04.00 Confidential / Released Page 210 of 475 3/17/06 9.11 AT+COLP Connected Line Identification Presentation This command refers to the GSM supplementary service COLP (Connected Line Identification Presentation) that enables a calling subscriber to get the connected line identity (COL) of the called party after setting up a mobile originated call. The command enables or disables the presentation of the COL at the TE. It has no effect on the execution of the supplementary service COLR in the network. Syntax Test Command AT+COLP=? Response(s) +COLP:(list of supported <n>s) OK Read Command AT+COLP? Response(s) +COLP: <n>, <m> OK ERROR +CME ERROR: <err> Write Command AT+COLP=[<n>] Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Unsolicited Result Code Call response format: +COLP: <number>, <type> Parameter Description <n>(num) 0 Disable - suppress unsolicited result codes 1 Enable - display unsolicited result codes <m>(num) 0 COLP not provisioned (no presentation) 1 COLP provisioned 2 Unknown <number>(str) String type phone number of connected address in format specified by <type> MC55_ATC_V04.00 Confidential / Released Page 211 of 475 3/17/06 <type>(num) Type of address octet in integer format; 145 when dialling string includes international access code character "+", otherwise 129. MC55_ATC_V04.00 Confidential / Released Page 212 of 475 3/17/06 9.12 AT+CPUC Price per unit and currency table Syntax Test Command AT+CPUC=? Response(s) OK Read Command AT+CPUC? Response(s) +CPUC: <currency>, <ppu> OK ERROR +CME ERROR: <err> Write Command AT+CPUC=<currency>, <ppu>[, <passwd>] Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description Read command returns the current parameters of PUC. Write command sets the parameters of Advice of Charge related price per unit and currency table. SIM PIN2 is usually required to set the parameters. Parameter Description <currency>(str)(+CSCS) Three-character currency code (e.g. "GBP", "EUR"). If the currency name is longer than three characters, all characters will be cut off after the third position. Before they are written to the SIM Card, these characters are converted to the standard GSM alphabet. <ppu>(str) Price per unit; dot is used as a decimal separator (e.g. "2.66"). The length is limited to 20 characters. If the string length is exceeded, the command is terminated with an error. This string may only contain digits and a dot. Leading zeros are removed from the string. The minimum and maximum value are determined by the structure of the SIM-PUCT file. The maximum price per unit value is 999 999 999.00. When successfully entered, this value is rounded to maximum accuracy. Note: Due to storage in mantisse (range 0-4095) and exponent (-7 to 7) it is possible that rounding errors occur. <passwd>(str) SIM PIN2. String parameter which can contain any combination of characters. The maximum string length is limited to 8 characters. If this value is exceeded, the command terminates with an error message. If the PIN2 is incorrect, a CME error (+CME ERROR: incorrect password) is output. MC55_ATC_V04.00 Confidential / Released Page 213 of 475 3/17/06 Example To change currency and/or price per unit you have two ways: You can enter PIN2 along with the AT+CPUC command: AT+CPUC="EUR","0.10","8888" OK (where "8888" = PIN2) Alternatively, you can first use the AT+CPIN2 command to enter PIN2. When you execute the AT+CPUC command, subsequently, take into account that PIN2 authentication expires after 300ms (see notes in AT+CPIN2). AT+CPUC="EUR","0.10" OK AT+CPUC="EUR","0.10" +CME ERROR: SIM PIN2 required MC55_ATC_V04.00 Confidential / Released Successful Attempt not successful. PIN2 authentication has expired. Page 214 of 475 3/17/06 9.13 AT+CSSN Supplementary service notifications Syntax Test Command AT+CSSN=? Response(s) +CSSN: (list of supported<n>s), (list of supported<m>s) OK Read Command AT+CSSN? Response(s) +CSSN: <n>, <m> OK Write Command AT+CSSN=<n>[, <m>] Response(s) OK ERROR +CME ERROR Reference(s) PIN GSM 07.07 ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Unsolicited Result Codes URC 1 +CSSI: <code 1> When <n>=1 and a supplementary service notification is received after a mobile originated call setup, intermediate result code "+CSSI: <code 1>" is sent to TE before any other MO call setup result codes URC 2 +CSSU: <code 2> When <m>=1 and a supplementary service notification is received during a mobile terminated call setup or during a call, unsolicited result code "+CSSU: <code 2>" is sent to TE. Command Description The write command enables or disables the presentation of URCs for supplementary services. Parameter Description <n>(num) 0(&F) Suppress "+CSSI" URCs 1 Activate "+CSSI" URCs <m>(num) 0(&F) Suppress "+CSSU" URCs 1 Activate "+CSSU" URCs MC55_ATC_V04.00 Confidential / Released Page 215 of 475 3/17/06 <code 1>(num) 0 unconditional call forwarding is active 1 some of the conditional call forwardings are active 2 call has been forwarded 3 Waiting call is pending <code 2>(num) 0 The incoming call is a forwarded call. 5 Held call was terminated by other party 10 additional incoming call forwarded Note • URCs will be displayed only if the call concerned is a voice call, but some URCs will be displayed as well as for data calls (like "+CSSU"=0). MC55_ATC_V04.00 Confidential / Released Page 216 of 475 3/17/06 9.14 AT+CUSD Supplementary service notifications AT+CUSD allows control of the Unstructured Supplementary Service Data (USSD) according to GSM 02.90. Both network and mobile initiated operations are supported. The interaction of this command with other commands based on other GSM supplementary services is described in the GSM standard. Parameter <n> is used to disable/enable the presentation of an unsolicited result code (USSD response from the network, or network initiated operation) "+CUSD: <m>[<str_urc>[<dcs>]]" to the TE. When parameter <str_write> is given, a mobile initiated USSD string or a response USSD string to a network initiated operation is sent to the network. The response USSD string from the network is returned in a subsequent unsolicited result code "+CUSD" Syntax Test Command AT+CUSD=? Response(s) +CUSD: (list of supported<n>s) OK Read Command AT+CUSD? Response(s) +CUSD: <n> OK Write Command AT+CUSD=<n>[, <str_write>[, <dcs>]] Response(s) OK +CME ERROR Reference(s) PIN GSM 07.07, GSM 02.90, GSM 03.90, GSM 04.90 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Unsolicited Result Code +CUSD: <m>[<str_urc>[<dcs>]] URC "+CUSD" indicates an USSD response from the network, or network initiated operation Parameter Description <n>(num) 0(&F) Disable the result code presentation in the TA 1 Enable the result code presentation in the TA 2 Cancel session (not applicable to read command response) <str_write>(str) String type USSD-string (when <str_write> parameter is not given, network is not interrogated). For the write command, only <dcs>= 15 is supported. MC55_ATC_V04.00 Confidential / Released Page 217 of 475 3/17/06 <str_urc>(str)(+CSCS) String type USSD-string . If <dcs> indicates that GSM 03.38 default alphabet is used TA converts GSM alphabet into current TE character set according to rules of GSM 07.05 Annex A. Otherwise in case of invalid or omitted <dcs> conversion of <str_urc> is not possible. <dcs>(num) GSM 03.38 Cell Broadcast Data Coding Scheme in integer format (default 15). In case of an invalid or omitted <dcs> from the network side (MT) <dcs> will not be given out. <m>(num) 0 No further user action required (network initiated USSD-Notify, or no further information needed after mobile initiated operation) 1 Further user action required (network initiated USSD-Request, or further information needed after mobile initiated operation). If <m>=1, then the URC ends with ">" to prompt the user for input. The user action is finished with <CTRL-Z> or aborted with <ESC>. 2 USSD terminated by network. Notes • When a USSD string is sent via ATD, a "AT+CUSD=1" is executed implicitly. • It is recommended to finalize or escape a pending USSD user interaction before further actions are done to prevent blocking situations. • If a network initiated operation is left unanswered, several error codes may be output. The first error code is given when the AT command is timed out. Other network indications may follow, depending on the network. MC55_ATC_V04.00 Confidential / Released Page 218 of 475 3/17/06 10. Internet Service Commands MC55 has an embedded TCP/IP stack that is driven by AT commands and enables the host application to easily access the Internet. The advantage of this solution is that it eliminates the need for the application manufacturer to implement own TCP/IP and PPP stacks, thus minimizing cost and time to integrate Internet connectivity into a new or existing host application. This chapter is a reference guide to all the AT commands and responses defined for use with the TCP/IP stack. Access is provided to the following Internet Services: 1. Socket Client and Server for TCP, Client for UDP 2. FTP Client 3. HTTP Client 4. SMTP Client 5. POP3 Client Two design strategies for using Internet Service AT commands - URC mode or polling mode: The MC55 offers two modes of controlling an Internet session opened with AT^SISO. To select the mode that best suits the preferences of your application design use the AT^SCFG command, parameter "Tcp/WithURCs" (refer to <tcpWithUrc>). • URC mode (delivery default): The progress of an Internet session is URC driven. The URCs notify the host whether data can be sent or received, whether data transfer has completed, whether the service can be closed or whether an error has occurred. This mechanism eliminates the need to poll the service until the necessary progress information is received. To enable the URC mode select: AT^SCFG="Tcp/WithURCs",on. • Polling mode: In polling mode, the presentation of URCs related to the Internet Services is disabled. The host is responsible to retrieve all the status information needed for controlling the Internet session. This is done by polling, where the host application keeps sending the commands AT^SISR, AT^SISW, AT^SISI. To enable the polling mode select: AT^SCFG="Tcp/WithURCs",off. The disabled URCs are the following: "^SISR" URC, "^SISW" URC and "^SIS" URC for parameter <urcCause>=0 (Internet service events), but not for <urcCause>=1 or 2 (needed for Socket listener and always enabled). Step-by-step overview of how to configure and use TCP/IP communications with MC55: • Select URC mode or polling mode as described above. • First of all, create a CSD or GPRS connection profile with AT^SICS. The connection profile is a set of basic parameters which determines the type of connection to use for an Internet service. The connection type is also referred to as bearer. Up to 6 connection profiles can be defined, each identified by the <conProfileId>. • Secondly, use AT^SISS to create a service profile based on one of the connection profiles. Up to 10 service profiles can be defined, each identified by the <srvProfileId>. The service profile specifies the type of Internet service to use, i.e. Socket, FTP, HTTP, or one of the email services SMTP or POP3. To assign a connection profile to a service profile, the <conProfileId> of AT^SICS must be entered as "conId" value of the AT^SISS parameter <srvParmTag>. This offers great flexibility to combine connection profiles and service profiles. For example, you may have one connection profile (CSD or GPRS) specified with AT^SICS which can be associated with an SMTP service profile for sending emails and a POP3 service profile for retrieving emails. • Once the connection profile and the service profile are created, an Internet session can be opened by entering the AT^SISO write command and the desired <srvProfileId>. In URC mode, the "^SISR" or "^SISW" URC indicates whether the service is ready to receive or send data. This means, that the AT^SISR or AT^SISW command shall be entered after the URC was received. If an error occurs the "^SIS" URC is delivered instead. In polling mode, you can enter the AT^SISR or AT^SISW command straight after AT^SISO though you may MC55_ATC_V04.00 Confidential / Released Page 219 of 475 3/17/06 • • • • • need to do so several times until the service confirms that data can be sent or received. The first parameter of the AT^SISR or AT^SISW commands is always the <srvProfileId>, the second parameter is the number of bytes which the host either wants to send to or is able to receive from the module. The way the module handles the data transfer follows the rules of the ordinary socket interface and is aware that a host may be limited by its input buffer size. The maximum data size supported by MC55 is 1500 bytes in both directions (read or write). To send or receive more than 1500 bytes, the read or write action shall be repeated until the data transfer has completed. Each read or write action requires that the command response (of AT^SISR or AT^SISW) confirms that the service is ready to send or receive data. To end an upload data stream set the <eodFlag> in the last AT^SISW command. The AT^SISI command shall be used to monitor the progress of the session. The command reports the service state of the used service profile and indicates the number of bytes received, the number of bytes sent and, in the case of sending, the number of bytes acknowledged or unacknowledged at TCP layer. If an error occurs during a session you can enter the AT^SISE command and the <srvProfileId> to identify the reason. This is especially important in polling mode. The AT^SICI command can be used any time to query the current status of one or all connection profile(s). Finally, to end a session, enter the AT^SISC write command and the <srvProfileId>. Maximum number of profiles defined / used: • Up to 6 connection profiles can be created (with AT^SICS). • Up to 10 service profiles can be created (with AT^SISS), but the number of parallel profiles of the same service type is limited as listed below. If the maximum number of a service profile type is already defined, any attempt to set up another profile for the same type will be denied with "+CME ERROR: operation of service temporary not allowed". • - Maximum 3 HTTP profiles - Maximum 6 socket profiles: The socket service can accept an incoming connection only when at least one service profile is still free (not yet created with AT^SISS), otherwise the incoming connection will be rejected from the listener. - 1 FTP profile - 1 POP3 profile - 1 SMTP profile The TCP/IP stack of MC55 supports one service profile at a time. Trying to run more than one service profile may result in a blocking of one of these service profiles. Using Internet Service AT commands on several interfaces (ASC0, ASC1 or Multiplex mode on ASC0): • A connection profile can be created on one interface and then viewed or changed on all other interfaces. • A service profile can be used only on one interface at a time: - Service profiles can only be opened on the interface where they have been defined with AT^SISS. - Accordingly, on each interface the read commands AT^SISO? and AT^SISI? deliver full status information for the service profiles configured / opened on this interface, while service profiles related to other interfaces are only listed by <srvProfileId> and service type name (= <srvParmTag> value "srvType") without any status parameters. - Changes to a service profile are allowed only on the same interface where it was created, trying to change it on another interface is denied with "+CME ERROR: Invalid index". If queried with the read command AT^SISS? the entire profile is returned on the interface where the service profile was created, while on all other interfaces only the service type of the profile is stated. - To free a service profile for use on another interface, use the AT^SISS command and select service type = "none". This action deletes the entire profile and restores all parameters of the profile to their initial power-up state (all values are empty). For example, to remove the service profile 3, set AT^SISS=3,srvType,none. After this, a new profile 3 can be created on any other interface. MC55_ATC_V04.00 Confidential / Released Page 220 of 475 3/17/06 Address notation Server addresses must be provided as IP addresses in standard dot-format (e.g. "192.168.1.2") or as server address names resolvable by a DNS server (e.g. "smtp.myserver.de" or "pop3.myserver.de"). Timeouts Timeouts are not part of the Internet AT command functionality implemented in MC55 and, if desired, are the responsibility of the host application. It is recommended that the host application validates URCs and AT command responses and reacts adequately, for example by sending a close message or starting a timer. Socket UDP client The significant differences between the TCP and UDP protocols imply that UDP sometimes requires particular procedures or even specific parameters. Details on how to handle UDP services can be found in extra notes or are included in the general parameter descriptions. Using the DCD line to detect the connection status of Internet services With AT&C you can configure the DCD line of the used serial interface to indicate whether an Internet service is active. For Socket, HTTP, SMTP and POP3 the states "Up" or "Connecting" are indicated, for FTP only the state "Up". MC55_ATC_V04.00 Confidential / Released Page 221 of 475 3/17/06 10.1 AT^SICS Internet Connection Setup Profile AT^SICS serves to create and edit Internet connection profiles. A connection profile can be assigned to one or more service profiles defined with AT^SISS, and thus, determines which type of connection is to be established when opening a service profile with AT^SISO. The AT^SICS read command requests the current settings of all Internet connection profiles. One line is issued for every possible parameter of a given <conParmTag> "conType" value. The AT^SICS write command specifies all parameters of a connection profile identified by <conProfileId>. At first the type of Internet connection needs to be selected via <conParmTag> value "conType". This determines the applicability of all other <conParmTag> values related to this "conType" and automatically sets their defaults. An exception is the <conParmValue-alphabet> which can be set before or after selecting "conType". To change the settings the write command needs to be executed for each single <conParmTag>. All profile parameters set with AT^SICS are volatile. MC55 supports the authentication methods PAP (Password Authentication Protocol), CHAP (Handshake Authentication Protocol) or none. The method actually used for an Internet connection via CSD or GPRS is negotiated at the LCP layer, i.e. it is negotiated with the remote peer at connection setup. Table 10.1: Applicability of AT^SICS <conParmTag> values <conParmTag> value CSD GPRS0 "conType" mandatory mandatory "user" optional optional "passwd" optional optional "apn" ø mandatory "inactTO" optional optional "calledNum" mandatory ø "dataType" mandatory ø "dns1" optional optional "dns2" optional optional "alphabet" optional optional Syntax Test Command AT^SICS=? Response(s) OK Read Command AT^SICS? Response(s) ^SICS: <conProfileId>, <conParmTag>, <conParmValue> OK MC55_ATC_V04.00 Confidential / Released Page 222 of 475 3/17/06 Write Command AT^SICS=<conProfileId>, <conParmTag>, <conParmValue> Response(s) OK ERROR +CME ERROR: <err> PIN ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <conProfileId>(num) 0...5 Internet connection profile identifier. The <conProfileId> identifies all parameters of a connection profile, and, when a service profile is created with AT^SISS the <conProfileId> needs to be set as "conId" value of the AT^SISS parameter <srvParmTag>. <conParmTag>(str) Internet connection parameter. "conType" Type of Internet connection. For supported values of <conParmValue> refer to <conParmValue-conType>. "alphabet" Selects the character set for input and output of string parameters within a profile. The selected value is bound to the specific profile. This means that different profiles may use different alphabets. Unlike other parameters the alphabet can be changed no matter whether the <conParmTag> value "conType" has been set. For supported values of <conParmValue> refer to <conParmValuealphabet>. "user" User name string: maximum 32 characters (where "" is default). "passwd" Password string: maximum 32 characters (where ***** is default). "apn" Access point name string value: maximum 100 characters (where "" is default). "inactTO" Inactivity timeout value in seconds: 0 ... 216-1, default = 20 Number of seconds the bearer remains open although the service no longer needs the bearer connection. "calledNum" Called BCD number. "dataType" Data call type. For supported values of <conParmValue> refer to <conParmValuedataType>. "dns1" Primary DNS server address (IP address in dotted-four-byte format). This value determines whether to use the DNS server addresses dynamically assigned by the network or a specific DNS server address given by the user. "dns1" = "0.0.0.0" (default) means that the CSD or GPRS connection profile uses dynamic DNS assignment. Any other address means that the Primary DNS is manually set. The default value applies automatically if no other address is set. Note that the AT^SICS read command only returns a manually configured IP address, while the value "0.0.0.0" is not indicated at all, no matter whether assumed by default or explicitly specified. See also note below. MC55_ATC_V04.00 Confidential / Released Page 223 of 475 3/17/06 "dns2" Secondary DNS server address (IP address in dotted-four-byte format). If "dns1" = "0.0.0.0" this setting will be ignored. Otherwise this value can be used to manually configure an alternate server for the DNS1. If "dns1" is not equal "0.0.0.0" and no "dns2" address is given, then "dns2"="0.0.0.0" will be assumed automatically. The AT^SICS read command only returns a manually configured IP address, while the value "0.0.0.0" is not indicated at all, no matter whether assumed by default or explicitly specified. <conParmValue>(str) Parameter value; type and supported content depend on related <conParmTag>. <conParmValue-conType>(str) Supported connection type values in <conParmValue> for <conParmTag> value "conType". "CSD" Circuit-switched data call. "GPRS0" GPRS connection. Settings of GPRS related commands are not used, e.g. AT+CGDCONT. When a service based on a GPRS connection profile is started after entering AT^SISO MC55 automatically tries to attach to the GPRS. Yet, the only exception is AT+CGATT which can be used any time to detach from the GPRS and, and thus disconnect the bearer opened with AT^SISO. "none" Clears the connection profile. <conParmValue-alphabet>(str) Character set selectable with <conParmValue> for <conParmTag> value "alphabet". ["0"] Character set determined with AT+CSCS applies. "1" International Reference Alphabet (IRA, seven bit ASCII) applies. <conParmValue-dataType>(str) Supported data call type values in <conParmValue> for <conParmTag> value "dataType". "0" ISDN ["1"] Analog Notes • Before opening a service profile based on a connection profile recently used, check with AT^SICI that the previous connection was properly closed. If AT^SICI confirms that the connection profile is in <conState> 0 (Down) the connection profile may be used again. • If a GPRS network does not support or is not correctly configured for automatic DNS address assignment the TCP/IP stack cannot resolve fully qualified domain names. In this case, a warning message will be returned when trying to open an Internet service configured for automatic DNS address assignment. 10.1.1 Example: Default values of a CSD connection profile As stated earlier, the "conType" selected with AT^SICS determines all other matching profile parameters related to this "conType". Once "conType" is set in a new profile, the default values of all other related parameters are assumed. To view the default settings you can use the read command AT^SICS?. at^sics=1,conType,CSD Select connection type CSD, identified by <conProfileId>1 OK at^sics? ^SICS: 0, "conType", "" Query current profiles. Profile with <conProfileId> 0 is still empty. MC55_ATC_V04.00 Confidential / Released Page 224 of 475 3/17/06 ^SICS: 1, "conType", "CSD" ^SICS: 1, "alphabet", "0" ^SICS: ^SICS: ^SICS: ^SICS: ^SICS: ^SICS: ^SICS: ^SICS: ^SICS: OK 10.1.2 1, 1, 1, 1, 1, 2, 3, 4, 5, "user", "" "passwd", "*****" "inactTO", "20" "calledNum", "" "dataType", "1" "conType", "" "conType", "" "conType", "" "conType", "" The new CSD profile just created is indicated with all related parameters set to their default. Character set determined with AT+CSCS applies when string parameters are input with AT^SICS. No user name set. Password masked with asteriks. Inactivity timeout = 20s. No destination set. Remote device is analog, e.g. an analog modem. Profile with <conProfileId> 2 is still empty. Profile with <conProfileId> 3 is still empty. Profile with <conProfileId> 4 is still empty. Profile with <conProfileId> 5 is still empty. Example: GPRS connection profile at^sics=0,conType,GPRS0 OK AT^SICS=0,"inactTO", "20" OK AT^SICS=0,dns1,"193.254.160.1" OK AT^SICS=0,passwd,t-d1 OK AT^SICS=0,apn,"internet.t-d1.de" Select connection type GPRS0. Inactivity timeout = 20s. IP address of Primary DNS server. Password for GPRS services provided by the German operator T-D1. APN to access the GPRS services provided by the German operator T-D1. OK MC55_ATC_V04.00 Confidential / Released Page 225 of 475 3/17/06 10.2 AT^SICI Internet Connection Information The AT^SICI read command requests the current status of the Internet connection profiles currently defined with AT^SICS. The AT^SICI write command displays the status of the specified Internet connection profile. If the connection profile is not defined yet, the command returns a "+CME ERROR" response. Syntax Test Command AT^SICI=? Response(s) [^SICI:(list of defined <conProfileId>s)] OK Read Command AT^SICI? Response(s) [^SICI: <conProfileId>, <conState>, <numServices>, <conAddr>] [^SICI: ...] OK Write Command AT^SICI=<conProfileId> Response(s) ^SICI: <conProfileId>, <conState>, <numServices>, <conAddr> OK ERROR +CME ERROR: <err> PIN ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <conProfileId>(num) Internet connection profile identifier as defined by AT^SICS (<conProfileId>). 0...5 <conState>(num) State of the Internet connection profile. 0 Down - Internet connection is defined but not connected. 1 Connecting - A service has been opened and so the Internet connection is initated. 2 Up - Internet connection is established and usable by one or more services. 3 Limited Up - Internet connection is established, but temporarily no network coverage. 4 Closing - Internet connection is terminating. MC55_ATC_V04.00 Confidential / Released Page 226 of 475 3/17/06 <numServices>(num) Number of services using this Internet connection profile. 0...9 <conAddr>(str) Local IP address of the Internet connection profile (empty if no address is associated yet). Note • Before opening a service profile based on a connection profile recently used, check with AT^SICI that the previous connection was properly closed. If AT^SICI confirms that the connection profile is in <conState> 0 (Down) the connection profile may be used again. 10.2.1 Checking Connection Profile Status at^sici? ^SICI: 1,2,1,"10.10.0.161" Query the current status of the connection profile. One connection profile has been created at <conProfileId>=1, and one service is opened using this connection profile. The Internet connection is in <conState>=2 ("Up"). OK Assume the network connection is temporarily not available. (If URC presentation mode of network registration is enabled the state is shown by the URC "+CREG: 2"). at^sici? ^SICI: 1,3,1,"10.10.0.161" Query once again the current status of the connection profile. Parameter <conState> has changed to state "Limited up". OK The network connection is temporarily not available but the Internet connection is still established, so the host may decide to stop the data transfer to minimize the risk of losing data due to memory limitations. at^sici? ^SICI: 1,2,1,"10.10.0.161" Query once again the current status of the connection profile. After re-establishing the network connection, <conState> reverts to state "Up". OK After closing the service with AT^SISC: at^sici? ^SICI: 1,2,0,"10.10.0.161" OK at^sici? ^SICI: 1,0,0,"0.0.0.0" Query once again the current status of the connection profile. Parameter <numServices> has decreased. The bearer is still open because the service was closed before expiry of the inactivity timeout "inactTO" of AT^SICS. Query again the current status. The inactivity timeout "inactTO" of AT^SICS has expired, therefore the bearer is closed now. OK MC55_ATC_V04.00 Confidential / Released Page 227 of 475 3/17/06 10.3 AT^SISS Internet Service Setup Profile AT^SISS serves to set up the necessary parameters in the Internet service profiles. Any service profile can then be used to control a data link in conjunction with AT^SISI, AT^SISO, AT^SISC, AT^SISR, AT^SISW and AT^SISE. The AT^SISS read command requests the current settings of all Internet service profiles. One line is issued for every possible parameter of a given <srvParmTag> "srvType" value. The AT^SISS write command specifies the parameters for a service profile identified by <srvProfileId>. At first the type of Internet service needs to be selected via <srvParmTag> value "srvType". This determines the applicability of all other <srvParmTag> values related to this "srvType" and sets their defaults. Changing the <srvParmTag> "srvType" of an existing service profile will reset all <srvParmTag> default values to suit the new "srvType". An exception is the <srvParmValue-alphabet> which can be set before or after selecting "srvType" and is not reset when "srvType" changes. To change the settings the write command needs to be executed for each single <srvParmTag>. All profile parameters set with AT^SISS are volatile. The list below shows which <srvParmTag> parameters apply to each Internet service and which of them are mandatory or optional. Table 10.2: Applicability of AT^SISS <srvParmTag> values <srvParmTag> Mandatory or optional Socket service "srvType" mandatory "conId" mandatory "alphabet" optional "address" mandatory "tcpMR" optional "tcpOT" optional FTP service "srvType" mandatory "conId" mandatory "alphabet" optional "address" mandatory "tcpMR" optional "tcpOT" optional HTTP service "srvType" mandatory "conId" mandatory "alphabet" optional "address" mandatory "user" optional "password" optional "hcContent" optional "hcContLen" optional MC55_ATC_V04.00 Confidential / Released Page 228 of 475 3/17/06 <srvParmTag> Mandatory or optional "hcUserAgent" optional "hcMethod" mandatory "hcProp" optional "hcRedir" optional "hcAuth" optional "tcpMR" optional "tcpOT" optional SMTP service "srvType" mandatory "conId" mandatory "alphabet" optional "address" mandatory "user" optional "password" optional "tcpPort" optional "smFrom" mandatory "smRcpt" mandatory "smCC" optional "smSubj" optional "smHdr" optional "smAuth" optional "tcpMR" optional "tcpOT" optional POP3 service "srvType" mandatory "conId" mandatory "alphabet" optional "address" mandatory "user" mandatory "password" mandatory "tcpPort" optional "pCmd" mandatory "pNumber" optional "pLength" optional "pDelFlag" optional "tcpMR" optional "tcpOT" optional MC55_ATC_V04.00 Confidential / Released Page 229 of 475 3/17/06 Syntax Test Command AT^SISS=? Response(s) OK Read Command AT^SISS? Response(s) ^SISS: <srvProfileId>, <srvParmTag>, <srvParmValue> OK Write Command AT^SISS=<srvProfileId>, <srvParmTag>, <srvParmValue> Response(s) OK ERROR +CME ERROR: <err> PIN ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <srvProfileId>(num) Internet service profile identifier. The <srvProfileId> is used to reference all parameters related to the same service profile. Furthermore, when using the AT commands AT^SISO, AT^SISR, AT^SISW and AT^SISC the <srvProfileId> is needed to select a specific service profile. 0...9 <srvParmTag> Internet service profile parameter. srvType Type of Internet service to be configured with consecutive usage of AT^SISS. For supported values of <srvParmValue> refer to <srvParmValue-srvType>. alphabet Selects the character set for input and output of string parameters within a profile. The selected value is bound to the specific profile. This means that different profiles may use different alphabets. Unlike other parameters the alphabet can be changed no matter whether the <srvParmTag> value "srvType" has been set. For supported values of <srvParmValue> refer to <srvParmValuealphabet>. user User name string 1. Socket Not applicable. 2. FTP Not applicable; set within "address" parameter. 3. HTTP Length: 2 ... 31 User name for the HTTP authentication mechanism. Currently only HTTP simple authentication is supported. MC55_ATC_V04.00 Confidential / Released Page 230 of 475 3/17/06 4. SMTP User name to be used for SMTP authentication (string). Length: 4 ... 64. If SMTP authentication is disabled, i.e. "smAuth" flag not set, user name parameter will be ignored. 5. POP3 User name identifying a mailbox, i.e. mailbox name (string). Length: 1 ... 64. passwd Password string 1. Socket Not applicable. 2. FTP Not applicable; set within "address" parameter. 3. HTTP Length: 2 ... 31 Password for the HTTP authentication mechanism. Currently HTTP simple authentication is supported only. 4. SMTP Password to be used for SMTP authentication (string). Length: 4 ... 64. If SMTP authentication is disabled, i.e. "smAuth" flag not set, password parameter will be ignored. 5. POP3 Server/mailbox-specific password (string). Length: 1 ... 64. Used to perform authentication with a POP3 server. conId tcpPort Internet connection profile to be used, for details refer AT^SICS. TCP Port Number 1. Socket Not applicable; set within "address" parameter. 2. FTP Not applicable; set within "address" parameter. 3. HTTP Not applicable; set within "address" parameter. If parameter is omitted the service connects to HTTP default port 80. 4. SMTP SMTP server TCP port number (numeric) Length: 0 ... 216-1 If this parameter is not set, SMTP default port number 25 is used. 5. POP3 POP3 server TCP port number (numeric) Length: 0 ... 216-1 If this parameter is not set, POP3 default port number 110 is used. address String value, depending on the service type either a URL in the case of Socket, FTP and HTTP or an address in the case of SMTP and POP3: 1. Socket MC55_ATC_V04.00 Confidential / Released - Socket type TCP client URL "socktcp://'host':'remote tcpPort' - Socket type TCP server URL "socktcp://listener:'local tcpPort' " - Socket type UDP client URL "sockudp://'host':'remote udpPort'[;size='byte'][;port='word']" Parameter "size" (optional): 0: PDU size is variable (default). 1 ... 1460: Fixed PDU size in bytes. Page 231 of 475 3/17/06 Parameter "port" (optional): 0: Port number will be assigned from service (default). 1 ... 216-1: defines the local port number for the UDP client. 2. FTP - FTP client URL (get) "ftp://'user':'password'@'host':'tcpPort'/'url-path' [;type='a|i|d'] " Refer "IETF-RFC 1738". - FTP client URL (put) "ftpput://'user':'password'@'host':'tcpPort'/'url-path'/'element [;type='a|i'][;mode='u|a|d'] " name' Used parameters: "host" is mandatory, all other parameters are optional. If "password" is set then "user" must be set as well. If "user" is omitted the string "anonymous" is selected for "user" and "password". If "password" is omitted the password request is served by an empty string. If "tcpPort" is omitted the service connects to the FTP default port 21. If "url-path" contains only the IP address a directory listing is requested. If "url-path" contains the IP address and has a slash '/' appended a detailed directory listing is requested. "type": [a)scii | i)mage | d)irectory] "mode": [u)nique | a)ppend | d)elete] "u)nique" selects the FTP Store Unique command to create a file name unique to the current directory. If the file name is assigned by the server then the "^SIS" URC will appear, indicating <urcInfoId> 2100 and the file name. "d)elete" clears given 'element name'. If "mode" is omitted "replace mode" is default setting. 3. HTTP HTTP client URL Length: 6 ... 255 "http://'server'/'path':'tcpPort' " "server": FQDN or IP-address "path": path of file or directory "tcpPort": If parameter is omitted the service connects to HTTP default port 80. Refer to "IETF-RFC 2616". 4. SMTP SMTP server address (string). Length: 4 ... 256. 5. POP3 POP3 server address (string). Length: 4 ... 256. hcContent Optional parameter for HTTP method "Post". Length: 0 ... 127 Can be used to transfer a small amount of data. The content of this string will only be sent if "hcContLen" = 0. The maximum length of "hcContent" is 127 bytes. To transmit a larger amount of data "hcContLen" must be set to a non-zero value. In this case the "hcContent" string will be ignored, and data transmission from the client to the server is done with AT^SISW. hcContLen Mandatory parameter for HTTP method "Post". Length: 0 ... 231-1 The content length shall be set in the header of the HTTP "Post" request before the data part is transferred. If "hcContLen" = 0 then the data given in the "hcContent" string will be posted. If "hcContLen" > 0 then the AT^SISW command will be used to send data from the client to the server. In this case, "hcContLen" specifies the total amount of data to be sent. The data can be sent in one or several parts. For each part, the transmission is triggered by the URC "^SISW: x, 1", then the AT^SISW write command can be executed. After the exact number of bytes are transferred via MC55_ATC_V04.00 Confidential / Released Page 232 of 475 3/17/06 the serial interface, the HTTP client will go from service state "Up" to service state "Closing" (see parameters <srvState> and <srvState> for detail). Finally, the URC "^SISW: x, 2" indicates that all data have been transferred and the service can be closed with AT^SISC. hcUsrAgent The user agent string must be set by the application to identify the mobile. Usually operation system and software version info is set with this browser identifier. Length: 0 ... 63 hcMethod HTTP method specification: 0=GET, 1=POST, 2=HEAD. hcProp Parameter for several HTTP settings. Length: 0 ... 127 The general format is 'key': <space> 'value' "\0d\0a". Multiple settings can be given separated by "\0d\0a" sequences within the string. Possible 'key' values are defined at HTTP/1.1 Standard RFC 2616. hcRedir This flag controls the redirection mechanism of the MC55 acting as HTTP client (numeric). If "hcRedir" = 0: No redirection. If "hcRedir" = 1: The client automatically sends a new HTTP request if the server answers with a redirect code (range 30x). Default is 1. hcAuth If set ("hcAuth" = 1) this flag determines that the HTTP client will automatically answer on authentication requests from the server with the current "passwd" and "user" parameter settings. If these parameters are not specified the MC55 will terminate the HTTP connection and send an indication to the TA. Default is 1. smFrom Email sender address, i.e. "MAIL FROM" address (string). Length: 6 ... 256 A valid address parameter consists of local part and domain name delimited by a '@' character, e.g. "[email protected]". smRcpt Recipient address of the email, i.e. "RCPT TO" address (string). Length: 6 ... 256 If multiple recipient addresses are to be supplied the comma character is used as delimiter to separate individual address values, e.g. "[email protected],[email protected]". smCC CC recipient address of the email (string). Length: 6 ... 256 If multiple CC recipient addresses are to be supplied the comma character is used as delimiter to separate individual address values, e.g. "[email protected],[email protected]". smSubj Subject content of the email (string). Length: 0 ... 256 If no subject is supplied the email will be sent with an empty subject. smHdr This parameter, if set, will be appended at the end of the email header section (string). Length: 0... 256 Hence, it serves as a generic header field parameter which allows the user to provide any email header field. It is the user's responsibility to provide correct header fields! String of max. 256 characters. Example for multipart MIME messages: "Content-Type: multipart/mixed". smAuth SMTP authentication control flag (numeric). If disabled (<srvParmValue> "0" by default), MC55 performs action without SMTP authentication. If enabled (<srvParmValue> "1") authentication procedure with the SMTP server will be performed by means of supported authentication methods, using MC55_ATC_V04.00 Confidential / Released Page 233 of 475 3/17/06 values of "user" and "passwd" parameters. If MC55 and SMTP server are not able to negotiate an authentication mechanism supported by both parties, the MC55 continues action without authentication. MC55 supports SMTP authentication. pCmd POP3 user command to be executed by the POP3 service (numeric). For supported values of <srvParmValue> refer to <srvParmValue-pCmd>. pNumber Optional message number argument used by the POP3 commands List ("2"), Retrieve ("3") and Delete ("4"). For POP3 commands see <srvParmTag> value "pCmd". Length: 0 ... 232-1 If no specific value is set in the service profile, the value "0" is assumed by default, i.e. "pNumber" is disabled. pLength Maximum message length (string, optional) Length: 0 ... 232-1 "pLength" can be used to specify the length of the message(s) to be retrieved from or deleted on the POP3 server. If no specific value is set in the service profile, the default value "0" is assumed, which means that there is no limit on the message size. A warning will be issued inthe following cases: • If "pNumber" > 0 and a specific message to be retrieved from / deleted on the server is longer than "pLength". • If "pNumber" = 0 and all messages to be retrieved from / deleted on the server are longer than "pLength". No warning will be issued in the following cases: • If there are no messages at all on the server. • If the server has message(s) below and above the "pLength" specified. In this case, the message(s) within the range of "pLength" can be successfully retrieved or deleted, but the message(s) above "pLength" remain on the server without any further notification given to the user. • Therefore, after retrieving / deleting messages, it is recommended to check the message status on the server. This can be done by adding a further POP3 service profile using the POP3 user command List ("2"). pDelFlag Flag to be used with the POP3 user command Retrieve ("3"). Specifies whether or not to delete retrieved emails on the server (optional). For supported values of <srvParmValue> refer to <srvParmValuepDelFlag>. tcpMR Parameter can be used to overwrite the global AT^SCFG parameter "Tcp/ MaxRetransmissions" <tcpMr> for a specific Internet Service connection profile. If the parameter is not specified the value specified with AT^SCFG will be used. Supported values <srvParmValue> for this parameter are the same as described for <tcpMr>. Setting is not relevant for Internet Service "Socket" whit type "UDP". tcpOT Parameter can be used to overwrite the global AT^SCFG parameter "Tcp/OverallTimeout" <tcpOt> for a specific Internet Service connection profile. If the parameter is not specified the value specified with AT^SCFG will be used. Supported values <srvParmValue> for this parameter are the same as described for <tcpOt>. Setting is not relevant for Internet Service "Socket" whit type "UDP". <srvParmValue>(str) Parameter value; type and supported content depend on related <srvParmTag>. MC55_ATC_V04.00 Confidential / Released Page 234 of 475 3/17/06 <srvParmValue-srvType>(str) Supported Internet service type values in <srvParmValue> for <srvParmTag> value "srvType". Before changing the "srvType" of an existing service profile be sure that the profile is closed. To verify the connection state of the service profile enter the read command AT^SISI. Only when <srvState>=2 is returned for this specific service profile you can change its service type. "Socket" MC55 acting as client or server (listener) for TCP, or as client for UDP. If MC55 is listener at least two service profiles are required. The first socket profile must be configured as listener. The second service profile will be dynamically assigned when a socket connection request from a remote client is incoming. For this purpose, one service profile must be left free (= not configured with AT^SISS). An incoming socket connection request will be indicated by the "^SIS" URC, with the next free <srvProfileId> shown inside the URC as parameter <urcInfoId>. The connection request can be accepted or rejected by using the commands AT^SISO or AT^SISC and the ID retrieved from the "^SIS". "Ftp" MC55 acting as FTP client. "Http" MC55 acting as HTTP client. "Smtp" MC55 acting as SMTP client. "Pop3" MC55 acting as POP3 client. "none" Reset Internet service profile settings. Operation is not allowed if profile is in use, i.e. it was activated via AT^SISO. <srvParmValue-alphabet>(str) Supported string parameter character set selections in <srvParmValue> for <srvParmTag> value "alphabet". ["0"] Applicable character set is determined by current setting of AT+CSCS. "1" International Reference Alphabet (IRA, seven bit ASCII). <srvParmValue-pCmd>(num) Supported POP3 user command values in <srvParmValue> for <srvParmTag> value "pCmd". 1 Status command. This command retrieves the "drop listing" of a POP3 server. A "drop listing" consists of a single line containing the number of messages in the maildrop list followed by the total size of the maildrop list in bytes. Each drop listing will be finished by a so-called "dotline", i.e. a new line with just a single dot. 2 List command. If <srvParmTag> value "pNumber" is set to a non-zero value the "List" command returns the "scan listing", consisting of a single line which contains the message number and the message size in bytes if the specified message exists in the maildrop list on the POP3 server. If no such message exists on the server than the POP3 service issues an error response to the user. If <srvParmTag> value "pNumber" is zero the "List" command returns a multiline "scan listing". For each message on the maildrop list of the server the POP3 service returns a line containing the message number and its size in bytes. A final "dotline" will be printed at the end of the "scan listing". If there are no messages on the maildrop list of the server, the POP3 service returns a positive response, i.e. it doesn't issue an error response, but the "scan listing" will be empty. In either case, each scan listing will be finished by a so-called "dotline", i.e. a new line with just a single dot. MC55_ATC_V04.00 Confidential / Released Page 235 of 475 3/17/06 3 Retrieve command. If <srvParmTag> value "pNumber" is set to a non-zero value this command retrieves the related message from the POP3 server's maildrop list. If no such message exists on the server the POP3 service issues an error response to the user. It depends on the parameter "pDelFlag" if the message will be deleted from the POP3 server upon successful retrieval. If <srvParmTag> value "pNumber" is zero the "Retrieve" command returns all messages pending in the POP3 server's maildrop. If there are no messages on the maildrop list of the server the POP3 service returns with a positive response, i.e. it doesn't issue an error response, but the returned list will be empty. Each email will be finished by a so-called "dotline", i.e. a new line with just a single dot. 4 Delete command If <srvParmTag> value "pNumber" is set to a non-zero value the command deletes the related message from the POP3 server's maildrop list. In fact, the message is marked as deleted on the server and will be deleted permanently if the POP3 service command executes successfully. In case an error has occurred, e.g. network loss, the message will not be deleted on the server even though the POP3 service command has been finished. If <srvParmTag> value "pNumber" is zero the "Delete" command deletes all messages from the POP3 server's maildrop list. In fact, the messages are marked as deleted on the server and will be deleted permanently if the POP3 service command executes successfully. In case an error has occurred, the messages will not be deleted on the server even though the POP3 service command has been finished. <srvParmValue-pDelFlag>(num) Supported flag values in <srvParmValue> for <srvParmTag> value "pDelFlag". Only applicable if the profile contains the POP3 user command Retrieve ("3"). [0] Messages will not be deleted on the server. 1 Delete messages on the server which have been retrieved successfully. Note • String parameters are truncated if greater than the maximum length specified above. MC55_ATC_V04.00 Confidential / Released Page 236 of 475 3/17/06 10.4 AT^SISI Internet Service Information AT^SISI serves to monitor the status of Internet service profiles defined with AT^SISS. The AT^SISI read command requests the current status of all defined Internet service profiles. The AT^SISI write command requests the status of the specified Internet service profile. If the specified service profile is not defined yet, "+CME ERROR" is returned. Syntax Test Command AT^SISI=? Response(s) [^SISI:(list of defined <srvProfileId>s)] OK Read Command AT^SISI? Response(s) If response is related to service profile(s) created / opened on this interface: [^SISI: <srvProfileId>, <srvState>, <rxCount>, <txCount>, <ackData>, <unackData>] [^SISI: ...] If response is related to service profile(s) created / opened on other interface(s): [^SISI: <srvProfileId>, <srvParmTag>value "srvType"] [^SISI: ...] OK ERROR Write Command AT^SISI=<srvProfileId> Response(s) ^SISI: <srvProfileId>, <srvState>, <rxCount>, <txCount>, <ackData>, <unackData> OK ERROR +CME ERROR: <err> PIN ! MC55_ATC_V04.00 Confidential / Released ASC0 ASC1 % Page 237 of 475 % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! 3/17/06 Parameter Description <srvProfileId>(num) Internet service profile identifier as defined by AT^SISS (<srvProfileId>). 0...9 <srvState>(num) Internet service state (for details see AT^SISO parameter <srvState>). 2 Allocated 3 Connecting 4 Up 5 Closing 6 Down <rxCount>(num) Number of bytes received via AT^SISR since last successful AT^SISO write command. This is the same value as displayed by the AT^SISO read command with the parameter <rxCount>. <txCount>(num) Number of bytes sent via AT^SISW since last successful AT^SISO write command. This is the same value as displayed by the AT^SISO read command with the parameter <txCount>. <ackData>(num) Number of data bytes already sent and acknowledged at TCP layer. Value 0 indicates that no sent data is acknowledged yet. Parameter is not applicable to HTTP, POP3, SMTP and Socket UDP client. For these services the counter is always set to 0. <unackData>(num) Number of data bytes already sent but not yet acknowledged at TCP layer. A value 0 indicates that all sent data is already acknowledged. This is the same value as displayed in the response of the AT^SISW write command with the parameter <unackData>. Parameter is not applicable to HTTP, POP3, SMTP and Socket UDP client. For these services the counter is always set to 0. Note • If a service is in state "Down" the responses for <rxCount>, <txCount>, <ackData> and <unackData> are the last known values for the service in the states "Connecting", "Up" and "Closing". MC55_ATC_V04.00 Confidential / Released Page 238 of 475 3/17/06 10.5 AT^SISO Internet Service Open The AT^SISO write command starts the Internet session configured by the service profile. All further steps needed to control the session depend on whether you are using URC mode or polling mode. The AT^SISO read command returns the current status of all services. URC mode: If the service opens successfully, the URCs "^SISW" and "^SISR" will trigger the action to follow, either writing data with AT^SISW or reading data with AT^SISR. To terminate an upload data stream set the <eodFlag> within the last AT^SISW command. If the URCs notify that a data transfer has been successful ("^SISR: x, 2" or "^SISW: x, 2"), the service can be closed with AT^SISC. If a special event occurs, e.g. an error or a warning, after opening or while using a service then the URC type "^SIS" will be delivered. Polling mode: After opening the service, all progress information needed to control the session shall be explicitly requested by the host application. The particular sequence of AT commands varies depending on the service used. The following list summarizes, by way of an example, the steps normally involved in managing an upload or download job. • Upload (Socket, FTP, HTTP, SMTP): • • - Enter the AT^SISO command, e.g. AT^SISO=9. - Enter AT^SISW, specify <reqWriteLength>, e.g. AT^SISW=9,20. Check resulting response for <cnfWriteLength>. Optionally, check error with AT^SISE, e.g. AT^SISE=9. If necessary, repeat the sequence several times. - Enter last AT^SISW command and enable <eodFlag>, e.g. AT^SISW=9,0,1. 1) If Socket service: Query available data with AT^SISR, e.g. AT^SISR=9,1430. - Check service state with AT^SISI, e.g. AT^SISI=9, if necessary several times until <srvState>=6 ("Down"). - Check error with AT^SISE, e.g. AT^SISE=9. - Close service with AT^SISC, e.g. AT^SISC=9. Download (Socket, FTP, HTTP, POP3): - Enter the AT^SISO command, e.g. AT^SISO=9. - Enter AT^SISR, specify <reqReadLength>, e.g. AT^SISR=9,1000. Check resulting response for <cnfReadLength>. If necessary, repeat the sequence several times until <cnfReadLength>= -2 (end of data) or ERROR. - Check error with AT^SISE, e.g. AT^SISE=9. - Close service with AT^SISC, e.g. AT^SISC=9. Socket service (upload and download possible in one session): - Recommended: Set AT+CMEE=2 to enable extended error text. - Enter the AT^SISO command, e.g. AT^SISO=9. - Enter AT^SISR or AT^SISW, specifying <reqReadLength> or <reqWriteLength>, e.g. AT^SISR=9,20 or AT^SISW=9,20. Check resulting response for <cnfReadLength> or <cnfWriteLength>. If necessary, repeat the sequence several times. - Check error with AT^SISE, e.g. AT^SISE=9. - If write action: Enter last AT^SISW command and enable <eodFlag>, e.g. AT^SISW=9,0,1. 1) If Socket service: Query available data with AT^SISR, e.g. AT^SISR=9,1430. - Close service with AT^SISC, e.g. AT^SISC=9. 1) Please note that in MC55 04.00 the <eodFlag> does not work properly for the Socket service. Therefore, if the Socket service is configured for TCP, check with <unackData> that the transmission buffer is empty, before activating the <eodFlag>. See Release Notes related to MC55 04.00. MC55_ATC_V04.00 Confidential / Released Page 239 of 475 3/17/06 Syntax Test Command AT^SISO=? Response(s) OK Read Command AT^SISO? Response(s) ^SISO: <srvProfileId>, <srvParmTag>value "srvType" [, <srvState>, <socketState>, <rxCount>, <txCount>, <locAddr>, <remAddr>] [^SISO: ...] OK Write Command AT^SISO=<srvProfileId> Response(s) OK ERROR +CME ERROR: <err> PIN § ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <srvProfileId>(num) <srvProfileId> 0 ... 9 specified with AT^SISS. <srvState>(num) Internet service state. Please note, that the state of an Internet service may influence the state of the serial DCD line. For details see description of value 2 for parameter <value> of command AT&C. 2 Allocated Service profile resources are allocated, i.e. at least the service type has been set (parameter <srvParmTag>, value "srvType" of AT^SISS). The service is not opened, but ready for configuration. 3 Connecting State after opening a service with AT^SISO where the connection is being established. If connection setup is successful the service proceeds to the state "4" (Up) and one of the URCs "^SISW" and "^SISR" may follow. If connection setup is not successful, the "^SIS" URC may appear and the service enters <srvState> 6 (Down). In the case of FTP, <srvState>=3 means that the command channel is being established. If the service profile is configured as Socket listener, then the listener always stays at <srvState>=3 and <socketState>=3 (LISTENER), while the <srvState> and <socketState> of the dynamically assigned service profile may change. See examples in Section 10.5.1. MC55_ATC_V04.00 Confidential / Released Page 240 of 475 3/17/06 4 Up The service performs its purpose. The data transfer process is the major function at this state. FTP: Data channel is up. SMTP: The SMTP service will not enter <srvState>=4 until the host has written the first data packet with AT^SISW. 5 Closing Internet Service is closing the network connection. FTP: Command channel is released. 6 Down This state is entered if - the service has successfully finished its session (see note on Socket), - the remote peer has reset the connection or - the IP connection has been closed because of an error. If a service in this state be sure to close it with AT^SISC before reopening it. Additional note for Socket: The Socket service enters <srvState>=6 after <unackData> counter has reached 0. <socketState>(num) Socket state identifier. 1 Socket not assigned, i.e. no TCP/UDP connection active. 2 Socket assigned as CLIENT. 3 Socket assigned as LISTENER. 4 Socket assigned as SERVER. <rxCount>(num) Number of bytes received via AT^SISR since last successful AT^SISO write command. <txCount>(num) Number of bytes sent via AT^SISW since last successful AT^SISO write command. <locAddr>(str) Recently used local IP address in dotted-four-byte format and TCP port, separated by colon, e.g. "192.60.10.10:80". <remAddr>(str) Remote IP address in dotted-four-byte format and TCP port, separated by colon, e.g. "192.60.10.10:80". Note • As in polling mode no error URCs are available you are advised to integrate the commands AT^SISI and AT^SISE into the command sequences for upload and download jobs. So, the AT^SISO command may be followed by AT^SISI to check that the service has entered the <srvState>=4 before sending AT^SISR or AT^SISW. This helps you to detect errors even though the "^SIS" URCs are disabled. A typical example is that the service fails to be opened because the service profile contains a wrong destination address. In such a case, after opening with AT^SISO and OK response, the service quickly enters the states <srvState>=2, 4 and 6, with an error being returned no earlier than after sending the first AT^SISR or AT^SISW command. In URC mode, an error URC, such as "Host not found" would be received in this situation, but in polling mode the only way to detect the state is using AT^SISI or, alternatively, AT^SISO. MC55_ATC_V04.00 Confidential / Released Page 241 of 475 3/17/06 10.5.1 Example: Accepting / Rejecting Socket Connection Request from Remote Client Host 1 configured as Socket listener with IP address 10.10.0.187 at port 65534 is receiving a connection request from the remote client 10.10.0.185 (at port 1024). The example assumes that connection and service profiles have been created as stated earlier. Start the Socket service in listener mode, then query the IP address dynamically assigned to the Socket listener: at^siso=4 at^siso? ^SISO: 0, ^SISO: 1, ^SISO: 2, ^SISO: 3, ^SISO: ^SISO: ^SISO: ^SISO: ^SISO: OK 4, 6, 7, 8, 9, Host 1 opens the Socket service. Query the current status of all services. All service profiles are unused, except for service profile 4 "" which is running in listener mode, where "" <srvState>=3 (listening) and <socketState>=3 "" (LISTENER). The response also indicates the IP "" address dynamically assigned to the listener. The listener's access data (IP address and TCP port number) shall be passed on to the client. "Socket","3","3","0","0","10.10.0.187:65534","0.0.0.0:0" "" "" "" "" Indication of incoming Socket connection request: ^SIS: 4, 1, 0 The URC indicates that the listener configured on service profile 4 is receiving a Socket connection request (<urcCause>=1) from the remote client. The last URC parameter <urcInfoId> represents the ID of the dynamically assigned service profile, here 0. Query the current status of services. Indication on host 1 that the connection request from the remote client has been dynamically assigned to service profile 0 which is set to Server mode (<socketState>=4). at^siso? ^SISO: 0, "Socket","2","4","0","0", "10.10.0.187:0","10.10.0.185:1024" ^SISO: 1, "" ^SISO: 2, "" ^SISO: 3, "" ^SISO: 4, "Socket","3","3","0","0", "10.10.0.187:65534","0.0.0.0:0" ^SISO: 6, "" ^SISO: 7, "" ^SISO: 8, "" ^SISO: 9, "" OK Host 1 accepts the Socket connection request: at^siso=0 OK ^SISW: 0, 1 Host 1 accepts the connection request, where 0 is the ID of the dynamically assigned service profile. The URC indicates that data transmission to the remote client is possible. If the remote client has already sent some data the additional URC ^SISR: 0,1 is displayed. Query the current status of services. The socket connection between host 1 and remote client is successfully established. at^siso? ^SISO: 0, "Socket","4","4","0","0", "10.10.0.187:65534","10.10.0.185:1024" ^SISO: 1, "" ^SISO: 2, "" ^SISO: 3, "" ^SISO: 4, "Socket","3","3","0","0","10.10.0.187:65534","0.0.0.0:0" MC55_ATC_V04.00 Confidential / Released Page 242 of 475 3/17/06 ^SISO: ^SISO: ^SISO: ^SISO: OK 6, 7, 8, 9, "" "" "" "" Host 1 rejects the Socket connection request: at^sisc=0 OK at^siso? ^SISO: 0, ^SISO: 1, ^SISO: 2, ^SISO: 3, ^SISO: 4, ^SISO: 6, ^SISO: 7, ^SISO: 8, ^SISO: 9, OK Host 1 rejects the connection request, where 0 is the ID of the dynamically assigned service profile. Query the current status of services. The dynamically assigned service profile is free again. The Socket listener stays at <srvState>=3 (listening) and <socketState>=3 (LISTENER). "" "" "" "" "Socket","3","3","0","0","10.10.0.187:65534","0.0.0.0:0" "" "" "" "" MC55_ATC_V04.00 Confidential / Released Page 243 of 475 3/17/06 10.6 AT^SISC Internet Service Close The AT^SISC write command closes the TCP/IP connection to the remote peer which was opened with AT^SISO. All resources are released, all status information parameters, e.g. <srvState>, <unackData>, <ackData>, <rxCount> and <txCount> counters, are reset. Only the initial configuration settings are preserved. The service can be restarted any time, using the same configuration or a new one. Syntax Test Command AT^SISC=? Response(s) OK Write Command AT^SISC=<srvProfileId> Response(s) OK ERROR +CME ERROR: <err> PIN § ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <srvProfileId>(num) 0...9 MC55_ATC_V04.00 Confidential / Released <srvProfileId> specified with AT^SISS. Page 244 of 475 3/17/06 10.7 AT^SISR Internet Service Read Data The AT^SISR command either triggers a read operation (download) or queries the number of bytes in the internal buffer. The AT^SISR write command may return the following errors: • "+CME ERROR: operation failed" if there is a problem on application, socket, PPP or GPRS/GSM level. The AT^SISE command and the "^SIS" URC offer additional error information. • "+CME ERROR: operation temporary not allowed" e.g. if the service has not network resources allocated. • "+CME ERROR: operation not allowed" e.g. if the service is not configured. Syntax Test Command AT^SISR=? Response(s) OK Write Command AT^SISR=<srvProfileId>, <reqReadLength> Response(s) ^SISR: <srvProfileId>, <cnfReadLength>[, <remainUdpPacketLength>] Number of data bytes are sent as specified by <cnfReadLength>. If peek operator was used no data bytes are sent. OK ERROR +CME ERROR: <err> PIN § ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last % Unsolicited Result Code ^SISR: <srvProfileId>, <urcCauseId> Data availability status of the Internet service configured with AT^SISS has changed. The URC is issued when: • data is available after opening an Internet service or • less data was confirmed (in <cnfReadLength>) than requested (with <reqReadLength>) during the last "Read Data" operation and new data is available. The URC is disabled in polling mode. See AT^SCFG, parameter "Tcp/WithURCs", <tcpWithUrc>. Parameter Description <srvProfileId>(num) <srvProfileId> 0 ... 9 specified with AT^SISS. <reqReadLength>(num) 0 Peek Operator: Query number of received bytes within internal buffers. The behaviour of the peek operator depends on the selected Internet service, i.e. it may not be supported by all IP Services. For "Socket" service configured for UDP the size of the next available UDP packet is returned. 1...1500 Requested number of data bytes to be read via the Internet service specified in <srvProfileId>. MC55_ATC_V04.00 Confidential / Released Page 245 of 475 3/17/06 <cnfReadLength>(num) -2 Indicates end of data. Data transfer has been finished (all data have been read) and the service can be closed with AT^SISC. -1 Applies only to HTTP: Querying number of available bytes is not supported by the HTTP service. 0 Indicates that no further is are available at the moment. >1 Number of available data bytes. The range is determined by <reqReadLength>: If <reqReadLength> was greater than 0, then <cnfReadLength> may be less or equal to the value requested with <reqReadLength>. If <reqReadLength> equals 0 (peek operator) the value indicated by <cnfReadLength> may be greater than 1500. <urcCauseId>(num) Indicates whether or not data is available for reading with AT^SISR. 1 Data is available and can be read by sending the AT^SISR command. The URC appears when less data was confirmed (in <cnfReadLength>) than requested (with <reqReadLength>) during the last "Read Data" operation and new data is available. 2 End of data. Data transfer has completed (all data read). The service can be closed with AT^SISC. <remainUdpPacketLength>(num) Optional third parameter of the AT^SISR write command response displayed only if the Socket service uses UDP. The reception of each datagram must be completed before the next datagram can be received. This may be a problem if the buffer of the host application is limited and not designed to handle the maximum packet size of 1500 bytes. To compensate this, the host is advised to request, via <reqReadLength>, an amount less or equal its maxmimum buffer capacity and wait for the resulting AT^SISR write command response with parameter <remainUdpPacketLength>. The benefit of this approach is that the host may properly receive all parts of a UDP datagram, as after each received data part the number of remaining bytes is synchronized, until reading the datagram is finished. If the currently read datagram is smaller than the number of bytes requested by the host the <remainUdpPacketLength> parameter is omitted. Further write attempts with AT^SISR are denied as long as the <remainUdpPacketLength> is unequal 0 or is not omitted. In this case the service returns "+CME ERROR: operation of service temporary not allowed". 0 Indicates that all bytes of the current UDP datagram are read. 1...(max. data size)-1 Indicates that the currently read UDP datagram is not yet complete. The displayed value is the remaining number of bytes. <remainUdpPacketLength> is unequal 0 until reading all parts of the current datagram is finished. 10.7.1 Example: Socket Host Reads Small Amounts of UDP Data Packets (URC Mode) This section applies only to the Socket service using the UDP protocol. The example shows how to read UDP packets if the buffer of the host application can handle only a few bytes. There are two datagrams available for reading. Buffer size: 6 bytes Datagram A = 18 bytes (content "THIS_IS_DATAGRAM_A") Datagram B = 3 bytes (content "NEW") MC55_ATC_V04.00 Confidential / Released Page 246 of 475 3/17/06 ^SISR: 0,1 at^sisr=0,6 ^SISR: 0,6,12 THIS_I OK at^sisr=0,6 ^SISR: 0,6,6 S_DATA OK at^sisr=0,6 ^SISR: 0,6,0 GRAM_A OK at^sisr=0,6 ^SISR: 0,3 NEW OK MC55_ATC_V04.00 Confidential / Released Service profile 0 is configured for Socket service and UDP. The URC notifies host that data is available for reading. The host requests to read 6 bytes. The first 6 bytes of datagram A are confirmed and transmitted. Another 12 bytes are still available. The host requests to read the next part of 6 bytes. The next 6 bytes of datagram A are confirmed and transmitted. Another 6 bytes are still available. The host requests to read the next part of 6 bytes. Last part of datagram A was received, no remainder is left. Again, the host requests to read 6 bytes. This time, the request refers to datagram B which has only 3 bytes. As the read datagram is smaller than the size requested by the host, the response does not include the <remainUdpPacketLength>. 3 bytes are confirmed and transmitted. Datagram B was properly received. Page 247 of 475 3/17/06 10.8 AT^SISW Internet Service Write Data The AT^SISW command triggers a write operation (upload) and queries the amount of data already sent, but not acknowledged at the TCP layer. The write operation may be run in binary mode, or in interactive text mode. The AT^SISW write command may return the following errors: • "+CME ERROR: operation failed" if there is a problem on application, socket, PPP or GPRS/GSM level. The AT^SISE command and the "^SIS" URC offer additional error information. • "+CME ERROR: operation temporary not allowed" e.g. if the service has not network resources allocated. • "+CME ERROR: operation not allowed" e.g. if the service is not configured. Syntax Test Command AT^SISW=? Response(s) OK Write Command AT^SISW=<srvProfileId>, <reqWriteLength>[, <eodFlag>[, <mode>]] Response(s) ^SISW: <srvProfileId>, <cnfWriteLength>, <unackData> Number of data bytes as specified by <cnfWriteLength>. OK ERROR +CME ERROR: <err> PIN § ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last % Unsolicited Result Code ^SISW: <srvProfileId>, <urcCauseId> Data availability status of the Internet service configured with AT^SISS has changed. The URC is issued when the service is ready to accept new user data. The URC is disabled in polling mode. See AT^SCFG, parameter "Tcp/WithURCs", <tcpWithUrc>. Parameter Description <srvProfileId>(num) <srvProfileId> 0 ... 9 specified with AT^SISS. <reqWriteLength>(num) 0...1500 Specifies the number of bytes to be sent with AT^SISW or, if set to 0, requests the amount of data already sent with AT^SISW but not yet acknowledged: • Parameter <reqWriteLength> may be 1...1500 bytes to specify the amount of data to be sent with AT^SISW. • If parameter <reqWriteLength> equals 0, AT^SISW does not expect any data, but a normal query is perfomed. This allows the application to explictly request, in particular at the end of an upload job, the amount of unacknowledged data at the TCP layer indicated by <unackData>. • In interactive text mode, <reqWriteLength> must be set to any value greater than 0 (but not necessarily the precise number of bytes). If set to 0 in interactive text mode, <reqWriteLength> would be interpreted as query for unacknowledged data and, thus, prevent data transfer. MC55_ATC_V04.00 Confidential / Released Page 248 of 475 3/17/06 • If Socket service is selected with UDP protocol - <reqWriteLength>=0 can be used to send an empty UDP packet; - the maximum requestable write size specified via <reqWriteLength> is limited to 1460 bytes. Any attempt to write more bytes will be denied and causes the following URC to appear: "^SIS: <id>, 0, 9, The supplied buffer was too small / large". <eodFlag>(num) End of data indication flag. Parameter is ignored for HTTP. [0] No end of data. Other data may follow to be transmitted via the Internet service. 1 End of data is signalled to the Internet Service. Further AT^SISW write commands return an error response. However, reading data may be possible. The <eodFlag> is effective only if the <reqWriteLength> equals <cnfWriteLength>, in particular if the <reqWriteLength> equals 0. If <mode> equals 1 the <eodFlag> is effective only if the write operation has been finished with CTRL-Z. <mode>(num) Control how the application provides the data bytes to be sent. [0] Binary mode This mode allows sending a number of bytes defined with parameter <reqWriteLength>. 1 Interactive text mode This mode allows the user to type and send 8-bit ASCII characters while the service is open. Ctrl-Z terminates data input and causes the data to be transferred. Interactive text mode requires that the <reqWriteLength> is set to any value greater than 0 (though it is not necessary to specify the precise number of bytes). In this case the <cnfWriteLength> parameter indicates the maximum length of the data stream without control character CTRL-Z. The <txCount> counter is incremented only by the portion of data actually transmitted. In interactive text mode, the following characters are defined as control codes: • BACKSPACE ("\x08") deletes the last given character, • CTRL-Z ("\x1a") terminates the input, • ESC ("\x1b") aborts the command. An <eodFlag> is ignored in this case. The V.25 command ATE also controls the echo mode of the interactive text mode. If echo is enabled (ATE1) all characters are echoed until <cnfWriteLength> is reached. Any attempt to input further data ends up with the warning message 4001 indicated after the data stream has been completed with CTRL-Z, nevertheless all data within the range of <cnfWriteLength> will be sent. See also Section 10.10, Internet Service URC "^SIS". ATE0 disables the echo mode generally. <cnfWriteLength>(num) 0...1500 MC55_ATC_V04.00 Confidential / Released Confirmed number of data bytes which can be transmitted via the Internet service configured in <srvProfileId>. In binary mode (see <mode>) this number may be less or equal to the value requested with <reqWriteLength>. The application has to deliver exactly the number of bytes indicated by <cnfWriteLength>. A 0 value means that no data can be written at this time, i.e. it serves as a flow control mechanism. In interactive text mode, <cnfWriteLength> indicates the maximum number of bytes it can process. Characters above the indicated number are ignored. Page 249 of 475 3/17/06 <unackData>(num) Number of data bytes already sent but not yet acknowledged at the TCP layer. The value is constantly changing until the entire upload job has completed. If the value equals 0 all data sent so far is acknowledged. In binary mode, <unackData> includes the <cnfWriteLength> value of the pending write operation. Therefore, the very first write operation of an upload job returns identical values for <cnfWriteLength> and <unackData>. This mechanism allows the host application to easily verify whether or not the remote host has successfully received the data. Parameter is not applicable to HTTP, POP3, SMTP and Socket UDP client. For these services the counter is always set to 0. <urcCauseId>(num) 1 The service is ready to accept new user data. 2 Data transfer has been finished successfully and Internet service may be closed without loss of data. Notes • The AT^SISW write command must be terminated only with the ASCII character set with ATS3. The factory default for S3 is #13 (Carriage Return). Do not send any further characters after the S3 end-of-line identifier, until the response "^SISW" is received. This is necessary to avoid that any characters related to the AT command can be interpreted as being part of the data stream to be transferred. Also refer Section 1.4, AT Command Syntax. • If the Socket service is configured for UDP and fixed size and the interactive text mode is active, the PDU length always equals the specified fixed length. If the input characters exceed the specified fixed length, then all surplus characters will be ignored. If the input characters are less than the specified fixed length, then the remaining range will be filled with "\0" bytes. 10.8.1 Usage of parameter <eodFlag> Service type Socket After the service accepts the end-of-data flag the service state changes to "Closing". No further user data is accepted. After releasing the TCP link the service remains in state "Down". FTP Parameter only applicable for FTP upload session. After accepting the end-of-data flag the service state changes to "Closing" and starts to end the running FTP session. No further user data is accepted. After the FTP session is completed on FTP protocol level the service state switches to "Down". In case of successful completion the URC "^SISW: x,2" is generated. SMTP SMTP service sends some "closing" commands to the SMTP server which are necessary to mark the email as successfully sent on the server. The service enters "Closing" state and remains in it until the final protocol exchange with the SMTP server has been completed. The "OK" response following AT^SISW indicates that the SMTP service has accepted the last data - IT DOES NOT indicate the successful completion of the SMTP service. Successful completion will be indicated either by the appropriate URC "^SISW:x,2" or due to the fact that the SMTP service state changes to "Down" state without any error. HTTP / POP3 Parameter not applicable, i.e. value is ignored. MC55_ATC_V04.00 Confidential / Released Page 250 of 475 3/17/06 10.9 AT^SISE Internet Service Error Report The AT^SISE write command returns the current error status of the specified Internet service profile. If the service profile is not defined or the value is invalid "+CME ERROR" response is returned. The error status is identical to the content of the "^SIS" URC last issued. If a service fails the commands AT^SISR or AT^SISW will return an error response. However, if the AT^SISE command returns <infoID>=0 it is recommended to use the AT+CEER command because a general GSM/ GPRS problem might be the reason. Syntax Test Command AT^SISE=? Response(s) OK Write Command AT^SISE=<srvProfileId> Response(s) ^SISE: <srvProfileId>, <infoID>[, <info>] OK ERROR +CME ERROR: <err> PIN ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <srvProfileId>(num) Internet service profile identifier as defined by AT^SISS <srvProfileId>. 0...9 <infoID>(num) Reason for Internet service error. This is a subset of the <urcInfoId>s which can be found in Section 10.10, Internet Service URC "^SIS". The value 0 indicates there is no special Internet service error. In this case the application may use AT+CEER to check for general GSM/GPRS problems. <info>(str) Information text related to <infoID>. This is a subset of the <urcInfoText>s which can be found in Section 10.10, Internet Service URC "^SIS". Note • In particular cases, the AT^SISE command may deliver information and warnings. This applies the following services: FTP: Information 2100 POP3: Warnings SMTP: Warnings If an error occurs the information and warning messages are overwritten by error messages. MC55_ATC_V04.00 Confidential / Released Page 251 of 475 3/17/06 10.10 Internet Service URC "^SIS" This section first describes the syntax and the parameters of the "^SIS" URC. The second part consists of tables listing the information elements delivered within the "^SIS" URC and the command response of AT^SISE. The presentation of the "^SIS" URC containing the parameter <urcCause>=0 can be disabled or enabled depending on whether polling mode or URC mode is preferred. To do so, use the AT^SCFG command, parameter "Tcp/WithURCs" (refer to <tcpWithUrc>). However, if related to <urcCause>=1 or 2, the "^SIS" URC will always be delivered regardless of the setting made with AT^SCFG. Unsolicited Result Code Indicates an event, an error or an information element. The same information can be obtained via AT^SISE. ^SIS: <srvProfileId>, <urcCause>[, [<urcInfoId>][, <urcInfoText>]] The URC may appear if an event or an error occurs, for example after opening an Internet service with AT^SISO or any time during operation. The URC also indicates a request for a mobile terminated Internet service client connection, or a failure if a mobile terminated request is rejected. Furthermore, the URC may deliver an information element resulting from a specific command given in the service profile. A list of possible causes can be found in the tables below. The tables contain the <urcInfoId> and, if applicable, a specific <urcInfoText>. If marked with *) the precise text related to a <urcInfoId> varies greatly depending on the scenario and the implementation of the remote server. In these cases, only a brief explanation of the scenario can be found in the table column "Description". Parameter Description <urcCause>(num) URC cause identifier. 0 An event has occurred after opening or while using an Internet service. The event number is presented via <urcInfoId> and may be an error, a warning, an information element or a note. Optionally additional information may be supplied via <urcInfoText>. 1 Indicates that an opened Socket listener service is receiving a connection request from a remote client. The incoming socket connection is dynamically assigned to the next free Internet service profile. In this case, the parameter <urcInfoId> inside the "^SIS" URC equals the <srvProfileId> of the dynamically assigned service profile. This ID shall be used to accept the connection request with AT^SISO or to reject it with AT^SISC. The connection status may be requested by using the AT^SISI read or write command or the AT^SISO read command. Among other details, the response indicates the IP address of the remote client (parameter <remAddr>). This may be helpful to decide whether to accept or reject the request. 2 Incoming Socket service client connection has failed. The client request was rejected automatically because no free Internet service profile was available. <urcInfoId>(num) Information identifier related to <urcCause>. See tables below for further detail. The <urcInfoId> number ranges indicate the type of information element: 0: Service is working properly. 1 - 2000: Error, service is aborted and enters <srvState>=6 (Down). 2001 - 4000: Information related to progress of service. 4001 - 6000: Warning, but no service abort. 6001 - 8000: Notes Additional information for Socket service: As stated above, if a Socket connection request from a remote client is received (see <urcCause>=1) the <urcInfoId> equals the <srvProfileId> of the dynamically assigned free service profile. MC55_ATC_V04.00 Confidential / Released Page 252 of 475 3/17/06 <urcInfoText>(str) Information text related to <urcCause>. See tables below for further detail. 10.10.1 Information Elements Related to the Service Application The following table lists the informatiomation elements which may be returned by all supported services within the "^SIS" URC and the command response of AT^SISE. It should be noted that TCP/IP socket problems may occur in all Internet service connections (Socket, FTP, HTTP, POP3 or SMTP). <urcInfoId> Description <urcInfoText> Information Elements Returned by the TCP/IP socket 2 Invalid socket descriptor Socket error 3 Bad access specified Socket error 4 Invalid operation Socket error 5 No free socket descriptors Socket error 6 The operation would block Socket error 7 A previous attempt at this operation is still ongoing Socket error 8 Socket is not bound Socket error 9 The supplied buffer is too small / large Socket error 10 Flags not supported Socket error 11 Operation not supported Socket error 12 The address is already in use Socket error 13 The network is unavailable Socket error 14 An established connection was aborted (transmission time-out or protocol error) Socket error 15 Remote host has reset the connection Socket error 16 No buffer space available Socket error 17 The socket is already connected Socket error 18 For TCP/IP sockets, the socket is not connected Socket error 19 Socket has been shut down Socket error 20 Connection timed out Socket error 21 Remote host has rejected the connection Socket error 22 Remote host is unreachable Socket error 23 An unexpected error occurred Socket error 24 Host not found DNS error 25 An error occurred that may be transient; a further attempt may succeed. DNS error 26 An unrecoverable error occurred DNS error General Information Elements 46 Fatal: The service has detected an unknown error 47 *) MC55_ATC_V04.00 Confidential / Released Indicates that the remote service has closed the connection. The host shall close the service. Page 253 of 475 3/17/06 <urcInfoId> <urcInfoText> Description 48 Remote peer has closed the connection Remote peer has closed the connection unexpectedly, and no data are available. The host shall close the service. Note that the "^SIS" URC only indicates the <urcInfoId>, but the AT^SISE command indicates both the <urcInfoId> and the <urcInfoText>. 49 Fatal: No memory is available for service action 50 Fatal: Service has detected an internal error 80 Connection profile not defined. 84 PPP LCP FAILED PPP error 85 PAP Authentication failed PPP error 86 CHAP Authentication failed PPP error 87 IPCP failed PPP error Warnings 4001 Applies only to interactive text mode: Indicates that number of input characters is greater than <cnfWriteLength>. General Information Elements 6001 10.10.2 General progress information for connection setup. Information Elements Related to FTP Service Description <urcInfoId> <urcInfoText> 100 FTP Server rejects session. 101 FTP Server rejects USER command. 102 FTP Server rejects PASS command. 103 FTP Server rejects PASV command or client can't detect remote IP address. 104 FTP Server rejects requested client action. 105 The given path segment is wrong. 106 *) The FTP client requests the file size from the server before starting the download. During transmission phase the client adds the bytes which are sent via serial line. After transmission is done the client compares the amount of bytes transferred via serial line and socket. 2100 FILE: <filename> File name assigned by FTP server if mode=u is used. MC55_ATC_V04.00 Confidential / Released Page 254 of 475 3/17/06 10.10.3 <urcInfoId> Information Elements Related to HTTP Service Description <urcInfoText> Error URCs 200 HTTP-ERR: Not connected - cannot send request HTTP-ERR: failed on sending request 201 <HTTP Response Str> Client error 202 <HTTP Response Str> HTTP-ERR: Service unavailable Server error 203 HTTP-ERR: Redirect failed - too many redirects HTTP-ERR: Redirect failed - not allowed HTTP-ERR: Redirect failed - location missing Max. number of allowed redirects: 6 204 HTTP-ERR: auth failed - user name or password missing HTTP-ERR: auth failed - user name or password wrong HTTP-ERR: Authority required for this URL HTTP-ERR: No access to this URL allowed Info URCs 2200 HTTP Redirect to: <Host>:<Port> <Path> 2201 HTTP Response <Response code> Example: ^SIS: 2,3,2201, "HTTP Response: HTTP/1.1 200 OK" 10.10.4 <urcInfoId> Information Elements Related to POP3 Service <urcInfoText> Description *) Indicates that the POP3 User Command could not be executed successfully. *) POP3 specific warning Errors 300 Warnings 4300 10.10.5 <urcInfoId> Information Elements Related to SMTP Service <urcInfoText> Description *) Indicates that the SMTP service could not be executed successfully. *) SMTP specific warning Errors 400 Warnings 4400 *) Text varies depending on scenario. MC55_ATC_V04.00 Confidential / Released Page 255 of 475 3/17/06 10.11 Examples of how to Configure and Use Internet Service Profiles Below you can find selective examples of how to configure and use Internet service profiles. To visualize the difference between URC mode and polling mode the operation of services (after opening with AT^SISO) is explained in separate examples for either mode. 10.11.1 Selecting URC Mode or Polling Mode To enable or disable the presentation of URCs for the Internet services use the AT^SCFG command, type "TcpIp/ WithURCs" and select "on" or "off" for parameter <tcpWithUrc>. Query the current setting. URC mode is enabled (delivery detault). at^scfg=tcp/withurcs ^SCFG: "Tcp/WithURCs","on" OK at^scfg=tcp/withurcs,off ^SCFG: "Tcp/WithURCs","off" OK 10.11.2 Select polling mode (by switching off URC mode). Polling mode is accepted. Configuring Socket Listener The example assumes that a connection profile has been created as explained in Section 10.1.1 or Section 10.1.2. Keep in mind that if the host is configured as listener another service profile must be left free to be dynamically assigned as Server when the listener receives a connection request from a remote client. Configure the service profile 4 for use as Socket listener: at^siss=4,srvType,socket OK at^siss=4,conId,0 OK at^siss=4,address,"socktcp://listener:65534" Select service type Socket. Select connection profile 0. The host specifies its local port 65534 to be used for the Socket listener service. The local IP address will be dynamically assigned when the service is opened with AT^SISO. OK Open the Socket service and query the IP address dynamically assigned to the Socket listener: at^siso=4 OK at^siso? ^SISO: 0, "" ^SISO: 1, "" ^SISO: ^SISO: ^SISO: ^SISO: ^SISO: ^SISO: ^SISO: OK 2, 3, 4, 6, 7, 8, 9, Open the Socket service. Query the current status of services. All service profiles are unused, except for service profile 4 which is running in listener mode, where <srvState>=3 (listening) and <socketState>=3 (LISTENER). The response also indicates the IP address dynamically assigned to the listener. "" "" "Socket","3","3","0","0","10.10.0.187:65534","0.0.0.0:0" "" "" "" "" MC55_ATC_V04.00 Confidential / Released Page 256 of 475 3/17/06 10.11.3 Configuring Socket Client for Calling a Socket Listener on Another Host The example assumes that a connection profile has been created as explained in Section 10.1.1 or Section 10.1.2. Configure the client's service profile 1 for calling a Socket listener on another host: at^siss=1,srvType,socket OK at^siss=1,conId,0 OK at^siss=1,address,"socktcp:// 10.10.0.187:65534" OK 10.11.4 Select service type Socket. Select connection profile 0. The service profile of the client contains the IP address and the TCP port of the remote host. Socket Client Sends Data via TCP Connection (Polling Mode) The example uses service profile 0 configured for Socket service and TCP. AT^SISO=0 OK AT^SISI=0 ^SISI: 0,3,0,0,0,0 OK AT^SISI=0 ^SISI: 0,4,0,0,0,0 OK AT^SISW=0,10 ^SISW: 0,10,10 0123456789 OK AT^SISW=0,10,1 ^SISW: 0,0,10 OK AT^SISW=0,10,1 ^SISW: 0,10,20 0123456789 OK AT^SISW=0,0,0 ^SISW: 0,0,10 OK AT^SISI=0 ^SISI: 0,5,0,20,10,10 The host opens service profile 0. Note: URC ^SISW:0, 1 does not appear! The host must poll the service state by means of AT^SISI until the service is in <srvState> "Up". The service is still in <srvState> "Connecting". The service is now in <srvState> "Up" and is ready to accept data. The host requests to write 10 bytes. Response that 10 bytes can be sent and are unacknowledged. The host requests to write next 10 bytes and enables the end-of-data flag. But the service refuses the request, even the end-ofdata flag remains without effect. Next try (polling). Response that the service accepts 10 bytes and this data and the previously sent data are unacknowledged. Polling to request unacknowledged data. There are 10 bytes still unacknowledged. Polling for <srvState> change ("Closing" -> "Down"). 20 bytes are transfered via serial interface, 10 bytes are acknowledged by remote peer, 10 bytes are on the way. OK MC55_ATC_V04.00 Confidential / Released Page 257 of 475 3/17/06 AT^SISI=0 ^SISI: 0,6,0,20,20,0 OK AT^SISC=0 OK 10.11.5 Polling for <srvState> change ("Closing" -> "Down"). The Service is in state "Down" and all data is confirmed by the remote peer. Closing the Socket service. Socket client sends data via TCP connection with URCs The example uses service profile 0 configured for Socket service and TCP. AT^SISO=0 OK ^SISW: 0,1 AT^SISW=0,10 ^SISW: 0,10,10 0123456789 OK ^SISW: 0,1 AT^SISW=0,10,1 ^SISW: 0,10,20 0123456789 OK -----^SISW: 0,2 AT^SISC=0 OK 10.11.6 The host opens service profile 0. Socket service is ready for upload. The host requests to write 10 bytes. Response that 10 bytes can be sent and are unacknowledged. The URC indicates that the Socket service is ready to transfer more data. Data of the last AT^SISW command are transferred to the remote host. The host requests to write next 10 bytes and enables the end-of-data flag to notify that these are the last 10 bytes of the session. Response that the service accepts 10 bytes and this data and the previously sent data are unacknowledged. Waiting for URC. Data transfer has been finished. Closing the Socket service. Configuring and Using FTP Download (URC Mode) First set up a connection profile as explained in Section 10.1.1 or Section 10.1.2. Enter at least all parameters which are mandatory for the connection profile. Configure the service profile 1 for FTP: at^siss=1,srvType,ftp OK at^siss=1,conId,0 OK at^siss=1,address,"ftp:// 192.168.1.2;type=d" OK Select service type FTP. Select connection profile 0. Specify FTP address with user and password anonymous. Make an FTP connection: at^siso=1 OK ^SISR: 1, 1 at^sisr=1,1500 MC55_ATC_V04.00 Confidential / Released Open the service. Bearer is established, service is getting started. Data is available. Request to read 1500 bytes. Page 258 of 475 3/17/06 50 bytes are now available. ^SISR: 1, 50 hardware inttest software support systemtest OK ^SISR: 1, 2 Data transfer finished. No more data available. The connection to the FTP server is closed. Close the service. at^sisc=1 OK 10.11.7 Configuring and Using FTP Upload (URC Mode) First set up a connection profile as explained in Section 10.1.1 or Section 10.1.2. Enter at least all parameters which are mandatory for the connection profile. Configure the service profile 1 for FTP: at^siss=1,srvType,ftp OK at^siss=1,conId,0 OK at^siss=1,address,"ftpput:// myname:[email protected]/upload/example.bin;type=i" OK Select service type FTP. Select connection profile 0. Specify FTP address with individual user name and password. The file "example.bin" shall be created on the FTP server. Make an FTP connection: at^siso=1 OK ^SISW: 1, 1 at^sisw=1,100 ^SISW: 1,100,100 0123456789012345678901234567890123456789012 3456789012345678901234567890123456789012345 67890123456789 OK ^SISW: 1, 1 at^sisw=1,0,1 OK ^SISW: 1, 2 at^sisc=1 10.11.8 Open the service. Bearer is established, service is getting started. FTP service is ready for upload. Client requests to send 100 bytes. The write command response confirms that 100 bytes must be transferred now. User data is transferred. URC indicates that the FTP service is ready to transfer more data. Data of the last AT^SISW command is transferred to the remote host. No more data available. The file "example.bin" shall be closed on the FTP server. Data transfer finished successfully. The connection to the FTP server is closed. Close the FTP service. Configuring SMPT Service Profile First set up a connection profile as explained in Section 10.1.1 or Section 10.1.2. Enter at least all parameters which are mandatory for a CSD or GPRS profile. The example uses the connection profile ID 1 and the service profile ID 9. at^siss=9,srvType,"Smtp" OK MC55_ATC_V04.00 Confidential / Released Select service type SMTP. Page 259 of 475 3/17/06 at^siss=9,alphabet,"1" Choose ASCII alphabet. OK at^siss=9,conId,"1" Select connection profile 1. OK at^siss=9,address,"192.168.1.2" Specify SMTP server address. OK at^siss=9,user,"subscriber1" Specify sender's user name required for SMTP authentication. OK at^siss=9,passwd,"subscr1" Specify password used by the sender for SMTP authentication. OK at^siss=9,smFrom,"subscriber1@testdoSender's email address. main.com" OK at^siss=9,smRcpt,"subscriber2@testdoRecipient's email address. main.com" OK at^siss=9,smSubj,"Meeting Request Sunday Enter text for subject field. Morning" OK at^siss=9,smAuth,"1" Sender name and password can be used for SMTP authentication. OK at^siss? To check the profile enter the AT^SISS read command. The response includes the values of all 10 ^SISS: 0, "srvType", "" connection profiles. In this example, no values are ^SISS: 1, "srvType", "" set for the profiles 0 through 8. Service profile 9 con^SISS: 2, "srvType", "" tains the values specified above and the values auto^SISS: 3, "srvType", "" matically assumed by default. ^SISS: 4, "srvType", "" ^SISS: 6, "srvType", "" ^SISS: 7, "srvType", "" ^SISS: 8, "srvType", "" ^SISS: 9, "srvType", "Smtp" ^SISS: 9, "conId", "1" ^SISS: 9, "alphabet", "1" ^SISS: 9, "address", "192.168.1.2" ^SISS: 9, "user", "subscriber1" ^SISS: 9, "passwd", "*******" ^SISS: 9, "smFrom", "[email protected]" ^SISS: 9, "smRcpt", "[email protected]" ^SISS: 9, "smCC", "" ^SISS: 9, "smSubj", "Meeting Request Sunday Morning" ^SISS: 9, "smHdr", "" ^SISS: 9, "tcPort", "25" Default: TCP port number commonly used for SMTP. ^SISS: 9, "smAuth", "1" ^SISS: 9, "tcpMR", "10" Default: Number of retransmission attempts for TCP packets is 10 (= default of AT^SCFG). ^SISS: 9, "tcpOT", "6000" Default: Timeout before closing outstanding TCP connection is 6000 sec (= default of AT^SCFG). OK 10.11.9 Sending Email (URC Mode) This example uses the service profile described in Section 10.11.8. at^siso=9 OK MC55_ATC_V04.00 Confidential / Released Open the service, i.e. start to send the email. Page 260 of 475 3/17/06 ^SISW: 9, 1 at^sisw=9,87 ^SISW: 9,87,87 The "^SISW" URC indicates that email data can be transferred. The email to be sent has 87 bytes. The write command response confirms that 87 bytes are available for transmission. Write the message text. Good Morning everyone, we are delighted to announce our next meeting on Sunday morning. OK at^sisw=9,0,1 Set the <eodFlag> to mark the end of the email body. ^SISW: 9,0,0 The <eodFlag> is accepted by the service. ^SISW: 9,2 The "^SISW" URC confirms that all data is sent successfully. at^sisi=9 Check the connection state of the service profile 9. ^SISI: 9,6,0,87,0,0 The command response confirms that the SMTP service is in state "6" (Down) and that 87 bytes have been transferred. at^sisc=9 Close the service. OK 10.11.10 Sending Email (Polling Mode) This example uses the service profile described in Section 10.11.8. at^siso=9 OK at^sisw=9,10 ^SISW: 9, 10, 0 Hallo Tom! OK at^sisw=9,10 ^SISW: 9, 0, 0 OK at^sisw0=9,12 ^SISW: 9, 12, 0 Bye Bye Tom! OK at^sisw=9,0,1 ^SISW: 9,0,0 OK at^sisi=9 ^SISI: 9,5,0,22,0,0 OK at^sisi=9 ^SISI: 9,6,0,22,0,0 OK at^sise=9 ^SISE: 9,0 Open the service, i.e. start to send the email. Try to write 10 bytes. The service response indicates that 10 bytes can be written. Write 10 bytes. Try to write 10 bytes. The service response indicates that the service refuses to accept any data at the moment. Try to write 12 bytes. The service response indicates that 12 bytes can be written. Write 12 bytes. Set the <eodFlag> to mark the end of the email body. The <eodFlag> is accepted by the service. Check the connection state of service profile 9. The command response confirms that the SMTP service is in state "5" (Closing) and that 22 bytes have been written. Check the connection state of service profile 9. The command response confirms that the SMTP service is in state "6" (Down) and that 22 bytes have been written. Check error status of service profile 9. The command response confirms that no error occurred. OK MC55_ATC_V04.00 Confidential / Released Page 261 of 475 3/17/06 Close the service. at^sisc=9 OK 10.11.11 Configuring POP3 Service Profile First set up a connection profile as explained in Section 10.1.1 or Section 10.1.2. Enter at least all parameters which are mandatory for a GPRS profile. The example uses the connection profile ID 1 and the service profile ID 1. The service profile is set up to retrieve a specific email (email number 2). at^siss=1,srvType,"Pop3" OK at^siss=1,conId,"1" OK at^siss=1,address,"192.168.1.2" OK at^siss=1,user,"subscriber1" OK at^siss=1,passwd,"subscr1" OK at^siss=1,pCmd,"3" OK at^siss=1,pNumber,"2" OK at^siss? ^SISS: 0, "srvType", "" ^SISS: 1, "srvType", "Pop3" ^SISS: 1, "conId", "1" ^SISS: 1, "alphabet", "0" ^SISS: ^SISS: ^SISS: ^SISS: ^SISS: ^SISS: ^SISS: ^SISS: 1, 1, 1, 1, 1, 1, 1, 1, "address", "192.168.1.2" "user", "subscriber1" "passwd", "*******" "pCmd", "3" "tcPort", "110" "pNumber", "2" "pLength", "0" "pDelFlag", "0" ^SISS: 1, "tcpMR", "10" ^SISS: 1, "tcpOT", "6000" ^SISS: ^SISS: ^SISS: ^SISS: ^SISS: ^SISS: ^SISS: OK 2, 3, 4, 6, 7, 8, 9, 10.11.12 "srvType", "srvType", "srvType", "srvType", "srvType", "srvType", "srvType", Select service type POP3. Select connection profile 1. Specify POP3 server address. Specify recipient's mailbox name. Password used by recipient for authentication to POP3 server. Command used to retrieve emails. Email message number 2 shall be retrieved. To check the profile enter the AT^SISS read command. The response includes the values of all 10 connection profiles. Service profile 1 contains the values specified above and the values automatically assumed by default. Default: Character set enabled with AT+CSCS shall be used. Default: TCP port number commonly used for POP3. Default: Message size shall not be limited. Default: Retrieved message shall not be deleted on POP3 server. Default: Number of retransmission attempts for TCP packets is 10 (= default of AT^SCFG). Default: Timeout before closing outstanding TCP connection is 6000 sec (= default of AT^SCFG). "" "" "" "" "" "" "" Retrieving Email (URC Mode) This example uses the service profile described in Section 10.11.11. MC55_ATC_V04.00 Confidential / Released Page 262 of 475 3/17/06 Open the service that was created to retrieve email number 2 from the POP3 server. at^siso=1 OK ^SISR: 1, 1 at^sisr=1,500 ^SISR: 1, 500 The "^SISR" indicates that data is available for reading. Try to read 500 bytes. Command response indicates that 500 bytes will be transferred, i.e. there will be no other URC since the requested length equals the confirmed length. Return-Path: <[email protected]> X-Original-To: [email protected] Delivered-To: [email protected] Received: from 10.10.0.132 (unknown [10.10.0.132]) by testdomain.com (Postfix) with SMTP id 379321D004 for <[email protected]>; Tue, 20 Dec 2005 08:00:07 +0100 (CET) To: [email protected] Cc: From: [email protected] Subject: TestMail Message-Id: <[email protected] > Date: Tue, 20 Dec 2005 08:00:07 +0100 OK at^sisr=1,500 Try to read another 500 bytes. at^sisr=1,78 Command response indicates that only 78 bytes will transferred. (CET) X-UIDL: &lL"!(Z6"!^cl!!1+%"! Status: RO Hallo Tom!Bye Bye Tom! . OK ^SISR: 1, 2 at^sisc=1 OK 10.11.13 Dot indicates end of mail according to RFC 2821. Parameter <urcCauseId> of the "^SISR" URC confirms that all data is transferred successfully. Close the service. Retrieving Email (Polling Mode) This example uses the service profile described in Section 10.11.11. at^siso=1 OK at^sisr=1,1000 ^SISR: 1, 0 OK at^sisr=1,1000 ^SISR: 1, 0 OK at^sisr=1,1000 ^SISR: 1, 578 MC55_ATC_V04.00 Confidential / Released Open the service that was created to retrieve email number 2 from the POP3 server. Try to read 1000 bytes. Command response indicates that currently no data is available. Again, try to read 1000 bytes. Command response indicates that currently no data is available. Again, try to read 1000 bytes. Command response indicates that 578 bytes are available for reading. Page 263 of 475 3/17/06 Return-Path: <[email protected]> X-Original-To: [email protected] Delivered-To: [email protected] Received: from 10.10.0.132 (unknown [10.10.0.132]) by testdomain.com (Postfix) with SMTP id 379321D004 for <[email protected]>; Tue, 20 Dec 2005 08:00:07 +0100 (CET) To: [email protected] Cc: From: [email protected] Subject: TestMail Message-Id: <[email protected] > Date: Tue, 20 Dec 2005 08:00:07 +0100 (CET) X-UIDL: &lL"!(Z6"!^cl!!1+%"! Status: RO Hallo Tom!Bye Bye Tom! . OK at^sisr=1,1000 ^SISR: 1,-2 Dot indicates end of mail according to RFC 2821. Try to read 1000 bytes once again. No more data available to read, i.e. the service has finished. OK at^sisi=1 ^SISI: 1,6,578,0,0,0 OK Check the connection state of service profile 1. The command response indicates that the POP3 service is in state "6" (Down) and that 578 bytes have been retrieved. Check error status of service profile 1. The command response confirms that no error occurred. at^sise=1 ^SISE: 1,0 OK at^sisc=1 OK 10.11.14 Close the service. HTTP POST (Polling Mode) at^siss=1,srvType,"Http" Select service type HTTP. OK at^siss=1,conId,1 Select connection profile 1. OK at^siss=1,hcMethod,1 Select "Post" method. OK at^siss=1,address,"http://192.168.1.3/datafiles/dummy/dummy.txt" OK at^siss=1,hcContLen,180 Try to upload 180 bytes. OK at^siso=1 Open the service. OK at^sisw=1,100 Send the first 100 bytes. ^SISW: 1, 100, 0 OK at^sisw=1,100 Try to send again 100 bytes. ^SISW: 1, 80, 0 80 bytes are sent. OK at^sisw=1,40 Try to write data once again. ^SISW: 1, 0, 0 No further data available, i.e. the service has finished. OK MC55_ATC_V04.00 Confidential / Released Page 264 of 475 3/17/06 at^sisi? ^SISI: 1,6,0,180,0,0 OK The command response indicates that HTTP service is in state "6" (Down) and that 180 bytes have been sent. Check error status of service profile 1. The command response confirms that no error occurred. at^sise=1 ^SISE: 1,0 OK at^sisc=1 OK 10.11.15 Close the service. HTTP GET (Polling Mode) at^siss=0,srvType,"Http" OK at^siss=0,conId,1 OK at^siss=0,hcMethod,0 OK at^siss=0,address,http://192.168.1.4/ OK at^siso=0 OK at^sisr=0,1500 ^SISR: 0, 1264 ...DATA... OK at^sisr=0,1500 ^SISR: 0, 1500 ...DATA... OK at^sisr=0,1500 ^SISR: 0, 602 ...DATA... OK at^sisr=0,1500 ^SISR: 0, -2 OK at^sisi? ^SISI: 0,6,0,3366,0,0 OK at^sise=0 ^SISE: 0,0 OK at^sisc=0 OK MC55_ATC_V04.00 Confidential / Released Select service type HTTP. Select connection profile 1. Start reading data in polling mode. Again, try to read 1500 bytes. Nor more data to read, i.e. the service has finished. The command response indicates that the HTTP service is in state "6" (Down) and that 3366 bytes have been read. Check error status of service profile 0. The command response confirms that no error occurred. Close the service. Page 265 of 475 3/17/06 11. GPRS Commands This chapter describes AT Commands that a TE (Terminal Equipment, e.g. an application running on a controlling PC) may use to control the MC55 acting as GPRS Mobile Termination (MT). Please use chapter "Using GPRS AT commands (Examples)" as a first guidance. 11.1 AT+CGACT PDP context activate or deactivate Syntax Test Command AT+CGACT=? Response(s) +CGACT: (list of supported <state>s) OK Read Command AT+CGACT? Response(s) +CGACT: <cid>, <state> [+CGACT: <cid>, <state>] ... OK Write Command AT+CGACT=[<state>[, <cid>[, <cid>]]] Response(s) OK ERROR +CME ERROR Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description The test command is used for requesting information on the supported PDP context activation states. The read command returns the current activation states for all the defined PDP contexts. The write command is used to activate or deactivate the specified PDP context(s). After the command has completed, the MT remains in V.250 command state. If any PDP context is already in the requested state, the state for that context remains unchanged. If the MT is not GPRS attached when the activation form of the command is executed, the MT first performs a GPRS attach and then attempts to activate the specified contexts. If no <cid>s are specified the activation/deactivation form of the command activates/deactivates all defined contexts. If the MT is not able to activate a context because of a failed attach, the command returns "ERROR" or "+CME ERROR: unknown" after 385 seconds (timer T3310 expired). If the MT is attached but is not able to activate a context for more than 160 seconds (timer T3380 expired), command returns "ERROR" or "+CME ERROR: unspecified GPRS error. In this case AT+CEER returns "+CEER: 51,3,0". The command should not be used to deactivate a PDP context during the implicit PDP context deactivation procedure which is started automatically after LCP termination or by dropping the DTR line (if AT&D2 is configured). For details refer to Section 11.6.1, Automatic deactivation of PDP context during dial-up PPP. MC55_ATC_V04.00 Confidential / Released Page 266 of 475 3/17/06 Parameter Description <state>(num) Indicates the state of PDP context activation. 0 deactivated [1] activated <cid>(num) PDP Context Identifier is a numeric parameter which specifies a particular PDP context definition. The parameter is local to the TE-MT interface and is used in other PDP context related commands. 1...2 Notes • ATH will deactivate any PDP context. • If the MT is in dedicated mode, the write command returns "+CME ERROR: operation temporary not allowed". • A maximum of 2 contexts can be activated at the same time, no matter on which interface. Trying to activate more than 2 contexts will cause "+CME ERROR: operation temporary not allowed". Note that, depending on the provider, the number of activated contexts may be further restricted. In such cases "+CME ERROR: unspecified GPRS error" will be returned and AT+CEER returns "+CEER: 50,26,0". Remember that contexts may be activated implicitly by using the ATD*98# or ATD*99# GPRS compatibility commands without specifying a <cid>. • If an activated context will be deactivated without using the command AT+CGACT, then the result code "NO CARRIER" will be issued to indicate the context deactivation. This happens for example if the context deactivation is forced by the network or if deactivation results from a network deregistration with AT+COPS=2. MC55_ATC_V04.00 Confidential / Released Page 267 of 475 3/17/06 11.2 AT+CGANS Manual response to a network request for PDP context activation Syntax Test Command AT+CGANS=? Response(s) +CGANS: (list of supported <response>s), (list of supported <L2P>s) OK Write Command AT+CGANS=[<response>[, <L2P>[, <cid>]]] Response(s) CONNECT NO CARRIER ERROR +CME ERROR Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! Last ! % Command Description The write command requests the MT to respond to a network request for GPRS PDP context activation which has been signaled to the TE by the RING or CRING unsolicited result code. The <response> parameter allows the TE to accept or reject the request. Parameter Description <response>(num) [0] the request is rejected and the MT returns OK to the TE 1 accept and request that the PDP context be activated <L2P>(str) a string parameter which indicates the layer 2 protocol to be used (see AT+CGDATA command) <cid>(num) a numeric parameter which specifies a particular PDP context definition (see AT+CGDCONT command). Note • If <response> is 1, the following procedure is followed by the MT: If the <L2P> parameter value is unacceptable to the MT, the MT will return an ERROR or +CME ERROR response. Otherwise, the MT issues the intermediate result code CONNECT and enters V.250 online data state. A <cid> may be specified for use in the context activation request. During the PDP startup procedure the MT has the PDP type and the PDP address provided by the network in the Request PDP context activation message. If this is in conflict with the information provided by a specified <cid>, the command will fail. There will be no conflict, if the PDP type matches exactly and the PDP address given by the context definition for <cid> is empty or matches exactly with the address specified with the network PDP context activation message. The context will be activated using the values for PDP type and address provided by the network, together with all other information found in the PDP context definition. An APN may or may not be required, depending on the application. MC55_ATC_V04.00 Confidential / Released Page 268 of 475 3/17/06 If no <cid> is given or if there is no matching context definition, the MT will attempt to activate the context using the values for PDP type and address provided by the network. The other parameters will be set to their default values (see AT+CGDCONT). If activation is successful, data transfer may proceed. After data transfer is complete, and the layer 2 protocol termination procedure has completed successfully, the V.250 command state is reentered and the MT returns the final result code OK. In the event of an erroneous termination or a failure to start up, the V.250 command state is re-entered and the MT returns the final result code NO CARRIER, or if enabled, +CME ERROR. Attach, activate and other errors may be reported. It is also an error to issue the AT+CGANS command when there is no pending network request. The command may be used in both normal and modem compatibility modes. MC55_ATC_V04.00 Confidential / Released Page 269 of 475 3/17/06 11.3 AT+CGATT GPRS attach or detach Syntax Test Command AT+CGATT=? Response(s) +CGATT: (list of supported <state>s) OK Read Command AT+CGATT? Response(s) +CGATT: <state> OK Write Command AT+CGATT=[<state>] Response(s) OK ERROR +CME ERROR Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description The test command is used for requesting information on the supported GPRS service states. The read command returns the current GPRS service state. The write command is used to attach the MT to, or detach the MT from the GPRS service. After the command has completed, the MT remains in V.250 command state. If the MT is already in the requested state, the command is ignored and the OK response is returned. Any active PDP contexts will be automatically deactivated when the attachment state changes to detached. If the MT is not able to attach for more than 5 minutes, command returns "ERROR" or "+CME ERROR: unknown", but MT is still trying to attach. If the MT is not able to detach for more than 1 minute, command returns "ERROR" or "+CME ERROR: unknown", but MT is still trying to detach. If an attach is issued during a running detach, command returns "ERROR" or "+CME ERROR: unspecified GPRS error". Parameter Description <state>(num) Indicates the state of GPRS attachement. 0(P) detached [1] attached Notes • If the MT is in dedicated mode, write command returns "+CME ERROR: operation temporary not allowed". • When the module is GPRS attached and a PLMN reselection occurs to a non-GPRS network or to a network where the SIM is not subscribed to for using GPRS, the resulting GMM (GPRS mobility management) state according to GSM 24.008 is REGISTERED/NO CELL, meaning that the read command will still show <state>=1. MC55_ATC_V04.00 Confidential / Released Page 270 of 475 3/17/06 11.4 AT+CGAUTO Automatic response to a network request for PDP context activation Syntax Test Command AT+CGAUTO=? Response(s) +CGAUTO: (list of supported <n>s) OK Read Command AT+CGAUTO? Response(s) +CGAUTO: <n> OK Write Command AT+CGAUTO=[<n>] Response(s) OK ERROR +CME ERROR Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description The test command returns the values of <n> supported by the MT as a compound value. The write command disables or enables an automatic positive response (auto-answer) to the receipt of a Request PDP Context Activation message from the network. It also provides control over the use of the V.250 basic commands ATS0, ATA and ATH for handling network requests for PDP context activation. Parameter Description <n>(num) 0 Disable automatic response for network requests for GPRS PDP context activation. GPRS network requests are manually accepted or rejected by the AT+CGANS command. 1 Enable automatic response for network requests for GPRS PDP context activation. GPRS requests are automatically accepted according to the description below. 3(&F)(P) Modem compatibility mode. The automatic acceptance of both GPRS and incoming CSD calls is controlled by the ATS0 command. Manual control uses the ATA and ATH commands, respectively, to accept or reject GPRS network requests or incoming CSD calls. Notes • It is allowed to have different AT+CGAUTO settings on different interfaces. • When the AT+CGAUTO=0 command is received, the MT will not perform a GPRS detach if it is attached. Subsequently, when the MT announces a network request for PDP context activation by issuing the URC RING or CRING, the TE may manually accept or reject the request by issuing the AT+CGANS command or may simply ignore the network request. MC55_ATC_V04.00 Confidential / Released Page 271 of 475 3/17/06 • When the AT+CGAUTO=1 command is received, the MT will attempt to perform a GPRS attach if it is not yet attached. Failure will result in ERROR or, if enabled +CME ERROR being returned to the TE. Subsequently, the MT announces a network request for PDP context activation by issuing the URC RING to the TE, followed by the intermediate result code CONNECT. The MT then enters V.250 online data state and follows the same procedure as it would after having received a +CGANS=1 with no <L2P> or <cid> values specified. • If a GPRS attach will be initiated by this command and the MT is not able to attach for more than 385 seconds (timer T3310 expired), command returns with "ERROR" or "+CME ERROR: unknown", but MT is still trying to attach and the requested automatic mode <n> is in use. • If a network request for PDP context activation is answered automatically and if another AT command is issued at the same time on the same interface, then this AT command is not executed. Any response belongs to the automatic context activation procedure. If the AT command which caused the collision was a circuit switched data call, the CONNECT response does not belong to this data call but to the GPRS. This can be detected if ATX is not set to 0. CS data call will issue CONNECT <text>, GPRS will issue CONNECT only. MC55_ATC_V04.00 Confidential / Released Page 272 of 475 3/17/06 11.5 AT+CGEREP GPRS event reporting The write command enables or disables sending of unsolicited result codes, "+CGEV" from MT to TE in the case of certain events occurring in the GPRS MT or the network. <mode> controls the processing of unsolicited result codes specified within this command. <bfr> controls the effect on buffered codes when <mode> 1 or 2 is entered. If a setting is not supported by the MT, ERROR or +CME ERROR: is returned. Read command returns the current <mode> and buffer settings. Test command returns the modes and buffer settings supported by the MT as compound values. Syntax Test Command AT+CGEREP=? Response(s) +CGEREP: (list of supported <mode>s), (list of supported <bfr>s) OK Read Command AT+CGEREP? Response(s) +CGEREP: <mode>, <bfr> OK Write Command AT+CGEREP=[<mode>[, <bfr>]] Response(s) OK ERROR +CME ERROR Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Unsolicited Result Codes URC 1 +CGEV: REJECT <PDP_type>, <PDP_addr> A network request for PDP context activation occurred when the MT was unable to report it to the TE with a +CRING unsolicited result code and was automatically rejected. URC 2 +CGEV: NW REACT <PDP_type>, <PDP_addr>, [<cid>] The network has requested a context reactivation. The <cid> that was used to reactivate the context is provided if known to the MT. URC 3 +CGEV: NW DEACT <PDP_type>, <PDP_addr>, [<cid>] The network has forced a context deactivation. The <cid> that was used to activate the context is provided if known to the MT. URC 4 +CGEV: ME DEACT <PDP_type>, <PDP_addr>, [<cid>] The mobile equipment has forced a context deactivation. The <cid> that was used to activate the context is provided if known to the MT. MC55_ATC_V04.00 Confidential / Released Page 273 of 475 3/17/06 URC 5 +CGEV: NW DETACH The network has forced a GPRS detach. URC 6 +CGEV: ME DETACH The mobile equipment has forced a GPRS detach. URC 7 +CGEV: NW CLASS <class> The network has forced a change of MS class. The highest available class is reported. URC 8 +CGEV: ME CLASS <class> The mobile equipment has forced a change of MS class. The highest available class is reported. Parameter Description <mode>(num) 0(P) Buffer unsolicited result codes in the MT. Currently 3 +CGEV URCs can be buffered. If MT result code buffer is full, the oldest ones will be discarded. No codes are forwarded to the TE. 1 Discard unsolicited result codes when MT TE link is reserved (e.g. in on line data mode); otherwise forward them directly to the TE. 2 Buffer unsolicited result codes in the MT when MT TE link is reserved (e.g. in on line data mode) and flush them to the TE when MT TE link becomes available; otherwise forward them directly to the TE. Currently 3 +CGEV URCs can be buffered. If MT result code buffer is full, the oldest URCs will be discarded. <bfr>(num) 0 MT buffer of unsolicited result codes defined within this command is cleared when <mode> 1 or 2 is entered 1 MT buffer of unsolicited result codes defined within this command is flushed to the TE when <mode> 1 or 2 is entered (OK response will be given before flushing the codes). Buffer is empty afterwards. <class>(str) Parameter indicates the GPRS mobile class. "B" MC55_ATC_V04.00 Confidential / Released class B Page 274 of 475 3/17/06 11.6 AT+CGDATA Enter data state Syntax Test Command AT+CGDATA=? Response(s) +CGDATA: (list of supported <L2P>s) OK Write Command AT+CGDATA=[<L2P>[, <cid>[, <cid>]]] Response(s) CONNECT NO CARRIER ERROR +CME ERROR Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last % Command Description The test command is used for requesting information on the supported layer 2 protocols to be used between the TE and MT. The write command causes the MT to perform all actions which are necessary to establish communication between the TE and the network using one or more GPRS PDP types. This may include performing a GPRS attach and one or more PDP context activations. Commands following the AT+CGDATA command in the AT command line will not be processed by the MT. If no <cid> is given or if there is no matching context definition, the MT will attempt to activate the context with PDP type IP and all other context parameters set to their default values (see AT+CGDCONT, AT+CGQREQ, AT+CGQMIN). If the <L2P> parameter is omitted, the layer 2 protocol is unspecified and PPP will be used. If the write command is successful, the MT issues the intermediate result code CONNECT and enters V.250 online data state. After data transfer is complete, and the layer 2 protocol termination procedure has completed successfully, the command state is reentered and the MT returns the final result code OK. If the <L2P> parameter value is unacceptable to the MT, the MT returns ERROR or +CME ERROR. In the event of erroneous termination or a failure to start up, the command state is reentered and the MT returns NO CARRIER, or if enabled +CME ERROR. Parameter Description <L2P>(str) Layer 2 protocol to be used between the TE and MT. ["PPP"] layer 2 protocol PPP <cid>(num) Parameter specifies a particular PDP context definition. The parameter is local to the TE-MT interface and is used in other PDP context-related commands. 1...2 MC55_ATC_V04.00 Confidential / Released Page 275 of 475 3/17/06 Notes • If the MT is in dedicated mode, write command returns "+CME ERROR: operation temporary not allowed". • It is possible to leave the GPRS data mode and enter the command mode by using the V.250 command +++. By using the command AT+CGDATA again, the data mode is reentered. Which context is used to return to data mode, depends on the supplied parameter <cid>. If no <cid> is specified, this is equivalent to using the V.250 command ATO, which is usable for GPRS connections too. In this case the first context will be used, which is active and already in data mode since it has been activated (the internal context used for GPRS connection without explicitly specifiying a context identifier has the highest priority). It is possible to use AT+CGDATA to enter the data mode for a context, which is not yet in data mode since it has been activated. With ATO this is not possible. 11.6.1 Automatic deactivation of PDP context during dial-up PPP When using the AT+CGDATA write command or ATD*99# or ATD*98# the MT issues the intermediate result code CONNECT and enters V.250ter online data state. In V.250 online data state, first some LCP protocol exchange between MT and TE is performed to set up the PPP link. After successfully establishing the PPP link, the MT performs the PDP context activation procedure if the context is not already activated. As a result, the MT is in a "PDP context activated" state within the PLMN, the PPP link is established on the mobile side and the mobile is ready for IP data transfer. If the TE wants to close the LCP link the MT may perform an LCP termination request procedure on PPP level. After this LCP termination procedure the MT deactivates the PDP context automatically and the MT returns to V.250 command mode and issues the final result code NO CARRIER. During the implicit PDP context deactivation procedure after LCP termination the TE may change into V.250 command state (e.g. by using +++ or by toggling DTR if AT&D is set to 1) before the result NO CARRIER occurs. In this case the application should not try to deactivate the PDP context by using the commands AT+CGACT or ATH. If DTR is configured to disconnect data connections (AT&D2), then the application should not toggle DTR during the implicit PDP context deactivation and before "NO CARRIER" is received. MC55_ATC_V04.00 Confidential / Released Page 276 of 475 3/17/06 11.7 AT+CGDCONT Define PDP Context Syntax Test Command AT+CGDCONT=? Response(s) +CGDCONT: (range of supported<cid>s), <PDP_type>, , , (list of supported <d_comp>s), (list of supported <h_comp>s) OK ERROR +CME ERROR Read Command AT+CGDCONT? Response(s) [+CGDCONT: <cid>, <PDP_type>, <APN>, <PDP_addr>, <d_comp>, <h_comp>] [+CGDCONT: ...] OK ERROR +CME ERROR Write Command AT+CGDCONT=[<cid>[, <PDP_type>[, <APN>[, <PDP_addr>]]]] Response(s) OK ERROR +CME ERROR Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description The test command returns supported values as a compound value. The read command returns the current settings for each defined PDP context. The write command specifies the parameters for a PDP context identified by the context identifier <cid>. The number of contexts that may be in a defined state at the same time is given by the range returned by the test command. A special form of the write command (AT+CGDCONT=<cid>) causes the values for context <cid> to become undefined. Parameter Description <cid>(num) PDP Context Identifier Parameter specifies a particular PDP context definition. The parameter is local to the TE-MT interface and is used in other PDP context-related commands. 1...2 <PDP_type>(str) Packet Data Protocol type Specifies the type of the packet data protocol. "IP" MC55_ATC_V04.00 Confidential / Released Internet Protocol (IETF STD 5) Page 277 of 475 3/17/06 <APN>(str) Access Point Name The logical name that is used to select the GGSN or the external packet data network. If the value is null or omitted, then the subscription value will be requested. <PDP_addr>(str) Packet Data Protocol address Identifies the MT in the address space applicable to PDP (e.g. IP V4 address for PDP type IP). If the value is null or omitted, then a value may be provided by the TE during the PDP startup procedure or, failing that, a dynamic address will be requested. The read command will continue to return the null string even if an address has been allocated during the PDP startup procedure. The allocated address may be read using AT+CGPADDR. <d_comp>(num) Data Compression Controls the PDP data compression (applicable for Subnetwork Dependent Convergence Protocol (SNDCP) only) 3GPP TS 44.065 [0] off <h_comp>(num) Header Compression Controls the PDP header compression 3GPP TS 44.065, 3GPP TS 25.323 [0] off Notes • The MT supports PDP type IP only. • AT&F and ATZ will undefine every context which is not active or not online. MC55_ATC_V04.00 Confidential / Released Page 278 of 475 3/17/06 11.8 AT+CGPADDR Show PDP address Syntax Test Command AT+CGPADDR=? Response(s) [+CGPADDR: (list of defined <cid>s)] OK Write Command AT+CGPADDR=[<cid>[,<cid>]] Response(s) [+CGPADDR: <cid>, <PDP_address>] [+CGPADDR: <cid>, <PDP_address>] OK ERROR +CME ERROR Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! Last ! ! Command Description The test command returns a list of defined <cid>s. The write command returns a list of PDP addresses for the specified context identifiers. If no <cid> is specified, the addresses for all defined contexts are returned. Parameter Description <cid>(num) A numeric parameter which specifies a particular PDP context definition (see AT+CGDCONT command). <PDP_address>(str) A string that identifies the MT in the address space applicable to the PDP. The address may be static or dynamic. Note • If no <cid> is specified, the write command will return a list of all defined contexts. MC55_ATC_V04.00 Confidential / Released Page 279 of 475 3/17/06 11.9 AT+CGQMIN Quality of Service Profile (Minimum acceptable) Syntax Test Command AT+CGQMIN=? Response(s) +CGQMIN: <PDP_type>, (list of supported <precedence>s), (list of supported <delay>s), (list of supported <reliability>s), (list of supported <peak>s), (list of supported <mean>s) OK ERROR +CME ERROR Read Command AT+CGQMIN? Response(s) [+CGQMIN: <cid>, <precedence>, <delay>, <reliability>, <peak>, <mean>] [+CGQMIN: ...] OK ERROR +CME ERROR Write Command AT+CGQMIN=[<cid>[, <precedence>[, <delay>[, <reliability>[, <peak>[, <mean>]]]]]] Response(s) OK ERROR +CME ERROR Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description The test command returns values supported as a compound value. If the MT supports several PDP types, the parameter value ranges for each PDP type are returned on a separate line. The read command returns the current settings for each defined context. If no minimum profile was explicitly specified for a context, simply OK will be returned, but default values will be used for that context. This command allows the TE to specify a minimum acceptable profile which is checked by the MT against the negotiated profile returned in the Activate PDP Context Accept message. The set command specifies a profile for the context identified by the (local) context identification parameter, <cid>. A special form of the set command, AT+CGQMIN= <cid> causes the minimum acceptable profile for context number <cid> to become undefined. In this case no check is made against the negotiated profile. AT&F and ATZ will undefine the minimum QoS profiles of every context which is not active or not online. Parameter Description <cid>(num) Parameter specifies a particular PDP context definition. The parameter is local to the TE-MT interface and is used in other PDP context-related commands. 1...2 MC55_ATC_V04.00 Confidential / Released Page 280 of 475 3/17/06 <precedence>(num) Precedence class [0] network subscribed value 1 High Priority Service commitments shall be maintained ahead of precedence classes 2 and 3 2 Normal priority Service commitments shall be maintained ahead of precedence class 3 3 Low priority Service commitments shall be maintained <delay>(num) Delay class The delay parameter defines the end-to-end transfer delay incurred in the transmission of SDUs through the GPRS network(s). [0] network subscribed value 1..4 SDU size: 128 octets: Delay Class Mean Transfer Delay 95 percentile 1 (Predictive) <0.5 <1.5 2 (Predictive) <5 <25 3 (Predictive) <50 <250 4 (Best Effort) Unspecified SDU size: 1024 octets: Delay Class Mean Transfer Delay 95 percentile 1 (Predictive) <0.5 <1.5 2 (Predictive) <5 <25 3 (Predictive) <50 <250 4 (Best Effort) Unspecified <reliability>(num) Reliability class [0] network subscribed value 1 Non real-time traffic, error-sensitive application that cannot cope with data loss 2 Non real-time traffic, error-sensitive application that can cope with infrequent data loss 3 Non real-time traffic, error-sensitive application that can cope with data loss, GMM/SM, and SMS 4 Real-time traffic, error-sensitive application that can cope with data loss 5 Real-time traffic, error non-sensitive application that can cope with data loss <peak>(num) Peak throughput class (in octets per second). [0] MC55_ATC_V04.00 Confidential / Released network subscribed value Page 281 of 475 3/17/06 1 Up to 1 000 (8 kbit/s). 2 Up to 2 000 (16 kbit/s). 3 Up to 4 000 (32 kbit/s). 4 Up to 8 000 (64 kbit/s). 5 Up to 16 000 (128 kbit/s). 6 Up to 32 000 (256 kbit/s). 7 Up to 64 000 (512 kbit/s). 8 Up to 128 000 (1024 kbit/s). 9 Up to 256 000 (2048 kbit/s). <mean>(num) Mean throughput class(in octets per hour). [0] network subscribed value 1 100 (~0.22 bit/s) 2 200 (~0.44 bit/s) 3 500 (~1.11 bit/s) 4 1 000 (~2.2 bit/s) 5 2 000 (~4.4 bit/s) 6 5 000 (~11.1 bit/s) 7 10 000 (~22 bit/s) 8 20 000 (~44 bit/s) 9 50 000 (~111 bit/s) 10 100 000 (~0.22 kbit/s) 11 200 000(~0.44 kbit/s) 12 500 000(~1.11 kbit/s) 13 1 000 000 (~2.2 kbit/s) 14 2 000 000 (~4.4 kbit/s) 15 5 000 000 (~11.1 kbit/s) 16 10 000 000 (~22 kbit/s) 17 20 000 000 (~44 kbit/s) 18 50 000 000 (~111 kbit/s) 31 best effort <PDP_type>(str) Packet Data Protocol Type "IP" Notes • If parameters are not defined, the parameter default values depend on the HLR-stored subscribed default values. • Definitions of parameters in GSM 02.60 and GSM 03.60 paragraph 15.2 "Quality of Service Profile". MC55_ATC_V04.00 Confidential / Released Page 282 of 475 3/17/06 Example If some of the QoS parameters are omitted, they will keep their current value (or the default value if not specified so far), e.g.: AT+CGDCONT=1,"IP" OK AT+CGQMIN= OK AT+CGQMIN? OK AT+CGQMIN=1,0 OK AT+CGQMIN? +CGQMIN:1,0,0,0,0,0 OK AT+CGQMIN=1,0,0,0,1 OK AT+CGQMIN? +CGQMIN:1,0,0,0,1,0 OK AT+CGQMIN=1,1 OK AT+CGQMIN? +CGQMIN:1,1,0,0,1,0 OK MC55_ATC_V04.00 Confidential / Released Page 283 of 475 3/17/06 11.10 AT+CGQREQ Quality of Service Profile (Requested) Syntax Test Command AT+CGQREQ=? Response(s) +CGQREQ: <PDP_type>, (list of supported <precedence>s), (list of supported <delay>s), (list of supported <reliability>s), (list of supported <peak>s), (list of supported <mean>s) OK Read Command AT+CGQREQ? Response(s) [+CGQREQ: <cid>, <precedence>, <delay>, <reliability>, <peak>, <mean>] [+CGQREQ: ...] Write Command AT+CGQREQ=[<cid>[, <precedence>[, <delay>[, <reliability>[, <peak>[, <mean>]]]]]] Response(s) OK ERROR +CME ERROR Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description The test command returns values supported as a compound value. If the MT supports several PDP types, the parameter value ranges for each PDP type are returned on a separate line. The read command returns the current settings for each defined context. If no requested profile was explicitly specified for a context, simply OK will be returned, but default values will be used for that context. This command allows the TE to specify a Quality of Service Profile that is used when the MT sends an Activate PDP Context Request message to the network. The set command specifies a profile for the context identified by the (local) context identification parameter, <cid>. A special form of the set command, +CGQREQ=<cid> causes the requested profile for context number <cid> to become undefined. AT&F and ATZ will undefine the QoS profiles of every context which is not active or not online. Parameter Description <cid>(num) Parameter specifies a particular PDP context definition. The parameter is local to the TE-MT interface and is used in other PDP context-related commands. 1...2 <precedence>(num) Precedence class [0] network subscribed value 1 High Priority Service commitments shall be maintained ahead of precedence classes 2 and 3 MC55_ATC_V04.00 Confidential / Released Page 284 of 475 3/17/06 2 Normal priority Service commitments shall be maintained ahead of precedence class 3 3 Low priority Service commitments shall be maintained <delay>(num) Delay class This parameter defines the end-to-end transfer delay incurred in the transmission of SDUs through the GPRS network(s). [0] network subscribed value 1..4 with SDU size = 128 octets: Delay Class Mean Transfer Delay 95 percentile 1 (Predictive) <0.5 <1.5 2 (Predictive) <5 <25 3 (Predictive) <50 <250 4 (Best Effort) Unspecified - with SDU size = 1024 octets: Delay Class Mean Transfer Delay 95 percentile 1 (Predictive) <0.5 <1.5 2 (Predictive) <5 <25 3 (Predictive) <50 <250 4 (Best Effort) Unspecified - <reliability>(num) Reliability class [0] network subscribed value 1 Non real-time traffic, error-sensitive application that cannot cope with data loss 2 Non real-time traffic, error-sensitive application that can cope with infrequent data loss 3 Non real-time traffic, error-sensitive application that can cope with data loss, GMM/SM, and SMS 4 Real-time traffic, error-sensitive application that can cope with data loss 5 Real-time traffic, error non-sensitive application that can cope with data loss <peak>(num) Peak throughput class in octets per second [0] network subscribed value 1 Up to 1 000 (8 kbit/s) 2 Up to 2 000 (16 kbit/s) 3 Up to 4 000 (32 kbit/s) 4 Up to 8 000 (64 kbit/s) 5 Up to 16 000 (128 kbit/s) MC55_ATC_V04.00 Confidential / Released Page 285 of 475 3/17/06 6 Up to 32 000 (256 kbit/s) 7 Up to 64 000 (512 kbit/s) 8 Up to 128 000 (1024 kbit/s) 9 Up to 256 000 (2048 kbit/s) <mean>(num) Mean throughput class in octets per hour [0] network subscribed value 1 100 (~0.22 bit/s) 2 200 (~0.44 bit/s) 3 500 (~1.11 bit/s) 4 1 000 (~2.2 bit/s) 5 2 000 (~4.4 bit/s) 6 5 000 (~11.1 bit/s) 7 10 000 (~22 bit/s) 8 20 000 (~44 bit/s) 9 50 000 (~111 bit/s) 10 100 000 (~0.22 kbit/s) 11 200 000(~0.44 kbit/s) 12 500 000(~1.11 kbit/s) 13 1 000 000 (~2.2 kbit/s) 14 2 000 000 (~4.4 kbit/s) 15 5 000 000 (~11.1 kbit/s) 16 10 000 000 (~22 kbit/s) 17 20 000 000 (~44 kbit/s) 18 50 000 000 (~111 kbit/s) 31 best effort <PDP_type>(str) Packet Data Protocol type "IP" Notes • If parameters are not defined, the parameter default values depend on the HLR-stored subscribed default values. • Definitions of parameters in GSM 02.60 and GSM 03.60 paragraph 15.2 "Quality of Service Profile". Example If some of the QoS parameters are omitted, they will keep their current value (or the default value if not specified so far), e.g.: AT+CGDCONT=1,"IP" OK AT+CGQREQ= OK MC55_ATC_V04.00 Confidential / Released Page 286 of 475 3/17/06 AT+CGQREQ? OK AT+CGQREQ=1,0 OK AT+CGQMIN? +CGQREQ:1,0,0,0,0,0 OK AT+CGQREQ=1,0,0,0,1 OK AT+CGQREQ? +CGQREQ:1,0,0,0,1,0 OK AT+CGQREQ=1,1 OK AT+CGQREQ? +CGQREQ:1,1,0,0,1,0 OK MC55_ATC_V04.00 Confidential / Released Page 287 of 475 3/17/06 11.11 AT+CGREG GPRS Network Registration Status AT+CGREG write command enables presentation of URC "+CGREG: <stat>" when <n>=1 and ME's GPRS network registration status changes. AT+CGREG read command queries the current URC presentation status and <stat> which shows whether the network has currently indicated the registration of the ME. Syntax Test Command AT+CGREG=? Response(s) +CGREG: (list of supported <n>s) OK Read Command AT+CGREG? Response(s) +CGREG: <n>, <stat> OK Write Command AT+CGREG=[<n>] Response(s) OK ERROR +CME ERROR Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Unsolicited Result Code +CGREG: <stat> Indicates a change in the ME's GPRS network registration status. Parameter Description <n>(num) 0(&F)(P) Disable network registration unsolicited result code 1 Enable network registration URC "+CGREG: <stat>" <stat>(num) 0 Not registered, ME is not currently searching an operator to register to. The ME is in GMM state GMM-NULL or GMM-DEREGISTERED-INITIATED. GPRS service is disabled, the ME is allowed to attach to GPRS if requested by the user. 1 Registered, home network. The ME is in GMM state GMM-REGISTERED or GMM-ROUTING-AREA-UPDATING-INITIATED INITIATED on the home PLMN MC55_ATC_V04.00 Confidential / Released Page 288 of 475 3/17/06 2 Not registered, but ME is currently trying to attach or searching an operator to register to. The ME is in GMM state GMM-DEREGISTERED or GMM-REGISTERED-INITIATED. The GPRS service is enabled, but an allowable PLMN is currently not available. The ME will start a GPRS attach as soon as an allowable PLMN is available. 3 Registration denied. The ME is in GMM state GMM-NULL. The GPRS service is disabled, the ME is not allowed to attach to GPRS if requested by the user. 4 Unknown 5 Registered, roaming. The ME is in GMM state GMM-REGISTERED or GMMROUTING-AREA-UPDATING-INITIATED on a visited PLMN. Note • When the module is GPRS attached and a PLMN reselection occurs to a non-GPRS network or to a network where the SIM is not subscribed to for using GPRS, the resulting GMM (GPRS mobility management) state according to GSM 24.008 is REGISTERED/NO CELL, meaning that the read command will still show <stat>=1 or <stat>=5. MC55_ATC_V04.00 Confidential / Released Page 289 of 475 3/17/06 11.12 AT+CGSMS Select service for MO SMS messages Syntax Test Command AT+CGSMS=? Response(s) +CGSMS: (list of supported <service>s) OK Read Command AT+CGSMS? Response(s) +CGSMS: <service> OK Write Command AT+CGSMS=[<service>] Response(s) OK ERROR +CME ERROR Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! Last ! ! Command Description The test command is used for requesting information on which services and service preferences can be set by using the AT+CGSMS write command The read command returns the currently selected service or service preference. The write command is used to specify the service or service preference that the MT will use to send MO SMS messages. If parameter <service> is not given, the current value remains unchanged. Parameter Description <service>(num) A numeric parameter which indicates the service or service preference to be used. Parameter is global for all interfaces and volatile. 0 GPRS 1 Circuit switched 2 GPRS preferred (use circuit switched SMS transfer if mobile is not GPRS attached) 3(&F)(P) Circuit switched preferred (use GPRS if circuit switched is not available) Note • Sending SMS via GPRS is only possible when mobile is attached using AT+CGATT. MC55_ATC_V04.00 Confidential / Released Page 290 of 475 3/17/06 11.13 AT^SGAUTH Set type of authentication for PPP connection Syntax Test Command AT^SGAUTH=? Response(s) ^SGAUTH: (list of supported <auth>s) OK ERROR +CME ERROR Read Command AT^SGAUTH? Response(s) ^SGAUTH: <auth> OK ERROR +CME ERROR Write Command AT^SGAUTH=<auth> Response(s) OK ERROR +CME ERROR Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <auth>(num) Indicates types of supported authentication. 0 none 1 PAP 2 CHAP (&F)(P) 3 MC55_ATC_V04.00 Confidential / Released PAP and CHAP Page 291 of 475 3/17/06 11.14 AT^SGCONF Configuration of GPRS related Parameters Syntax Test Command AT^SGCONF=? Response(s) ^SGCONF: (list of supported <llc_pdu_length_U>s), (list of supported <GPRS msclass>es) OK Read Command AT^SGCONF? Response(s) ^SGCONF: <llc_pdu_length_U>, <GPRS msclass> OK Write Command AT^SGCONF=[<llc_pdu_length_U>][, [<GPRS msclass>]] Response(s) OK ERROR +CME ERROR Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <llc_pdu_length_U>(num) The maximum number of octets in an information field of Unnumbered (U) frames. 0 No negotiation with network (500 will be used). 140...1520 (P) Lower values diminish performance. <GPRS msclass>(num) GPRS Multislot Class. The value can be one of the classes indicated with the Test command. The value set is volatile and powerup value is the maximum allowed. Notes • +CME ERROR: invalid index: Parameter is out of range • +CME ERROR: operation temporary not allowed: The command is blocked as long as GPRS is already in use (as long as mobile is GPRS attached). • Writing to user profile with AT&W and restoring with AT&F are not supported. MC55_ATC_V04.00 Confidential / Released Page 292 of 475 3/17/06 11.15 ATA Manual response to a network request for PDP context activation The V.250 ATA command may be used to accept a network request for a PDP context activation announced by the unsolicited result codes "RING" or "+CRING: GPRS". The MT responds with CONNECT, enters V.250 online data state and follows the same procedure as it would after having received a AT+CGANS=1 with no <L2P> or <cid> values specified. If you try to answer a request which is no longer present or which is already answered by another instance, NO CARRIER is returned. Syntax Exec Command ATA Response(s) CONNECT NO CARRIER Reference(s) PIN GSM 07.07 % MC55_ATC_V04.00 Confidential / Released ASC0 ASC1 % Page 293 of 475 % MUX1 MUX2 % % MUX3 Charge % ! ! Last % 3/17/06 11.16 ATD*99# Request GPRS service This command causes the MT to perform whatever actions are necessary to establish a communication between the TE and the external PDN. The V.250 'D' (Dial) command causes the MT to enter the V.250 online data state and, with the TE, to start the specified layer 2 protocol. No further commands may follow on the AT command line. GPRS attachment and PDP context activation procedures may take place prior to or during the PDP startup if they have not already been performed using the AT+CGATT and AT+CGACT commands. If the context to be used is already activated, it will be deactivated first. This ensures that the right context parameters will be used (e.g. QoS changes since the last context activation or the called address specified by ATD*99#). Examples on how to use this command are provided in "Section 11.20, Using GPRS AT commands (Examples)". To confirm acceptance of the command before entering the V.250 online data state command will respond with CONNECT. When the layer 2 protocol has terminated, either as a result of an orderly shut down of the PDP or an error, the MT enters V.250 command state and returns NO CARRIER (for details refer to Section 11.6.1, Automatic deactivation of PDP context during dial-up PPP). Syntax Exec Command ATD*99[* [<called_address>][* [<L2P>][* [<cid>]]]]# Response(s) CONNECT NO CARRIER Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last % Parameter Description <called_address>(str) IP V4 address in the form w.x.y.z, which identifies the called party; if it is provided, the MT will automatically set up a virtual call to the specified address after the context has been activated. This parameter is currently not used and needs not to be specified. <L2P>(str) Layer 2 protocol to be used between the TE and MT. "PPP" layer 2 protocol PPP "1" layer 2 protocol PPP <cid>(num) Parameter specifies a particular PDP context definition (see AT+CGDCONT command). If no context is specified, an internal context with default properties is used (see AT+CGDCONT, AT+CGQREQ and AT+CGQMIN). 1...2 Notes • If MC55 is in dedicated mode, command returns "+CME ERROR: phone busy". • ATD is used as a standard V.250 AT command, too. MC55_ATC_V04.00 Confidential / Released Page 294 of 475 3/17/06 11.17 ATD*98# Request GPRS IP service This command causes the MT to perform whatever actions are necessary to establish a communication between the TE and the external PDN. The V.250 'D' (Dial) command causes the MT to enter the V.250 online data state and, with the TE, to start the layer 2 protocol. GPRS attachment and PDP context activation procedures may take place prior to or during the PDP startup if they have not already been performed using the AT+CGATT and AT+CGACT commands. If the context to be used is already activated, it will be deactivated first. This ensures that the right context parameters will be used (e.g. QoS changes since the last context activation). To confirm acceptance of the command before entering the V.250 online data state command will respond with CONNECT. When the layer 2 protocol has terminated, either as a result of an orderly shut down of the PDP or an error, the MT enters V.250 command state and returns NO CARRIER (for details refer to Section 11.6.1, Automatic deactivation of PDP context during dial-up PPP). Syntax Exec Command ATD*98[* <cid>]# Response(s) CONNECT NO CARRIER Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last % Parameter Description <cid>(num) Parameter specifies a particular PDP context definition (see AT+CGDCONT command). If no context is specified, an internal context with default properties is used (see AT+CGDCONT, AT+CGQREQ and AT+CGQMIN). 1...2 Notes • If MC55 is in dedicated mode, command returns "+CME ERROR: phone busy". • ATD is used as a standard V.250 AT command, too. MC55_ATC_V04.00 Confidential / Released Page 295 of 475 3/17/06 11.18 ATH Manual rejection of a network request for PDP context activation The V.250 ATH command may be used to deactivate all PDP contexts which are active or online on the same interface. This command should not be used to deactivate PDP contexts during the implicit PDP context deactivation procedure which is started automatically after LCP termination or by dropping the DTR line (if AT&D2 is configured). For details refer to Section 11.6.1, Automatic deactivation of PDP context during dial-up PPP. The ATH command may also be used to reject a network request for PDP context activation announced by the unsolicited result codes "RING: GPRS" or "+CRING: GPRS". Syntax Exec Command ATH Response(s) OK Reference(s) PIN GSM 07.07 % ASC0 ASC1 % § MUX1 MUX2 % § MUX3 Charge § ! ! Last ! Notes • In contrast to GSM 07.07 it is possible to cancel a connection with ATH after a break. This is done for compatibility reasons due to the "dial-up network" drivers of Microsoft Windows. • ATH is used as a standard V.250 AT command, too. • If ATH is used to reject a network request for PDP context activation, then other PDP contexts on the same interface which are active or online will not be deactivated. MC55_ATC_V04.00 Confidential / Released Page 296 of 475 3/17/06 11.19 ATS0 Automatic response to a network request for PDP context activation The V.250 ATS0=<n> (Automatic answer) command may be used to turn off (n=0) and on (n>0) the automatic response to a network request for a PDP context activation. See also "3GPP TS 27.007 (GSM 07.07): AT command set for User Equipment (UE)". When the ATS0=<n> (<n> > 0) command is received, the MT will attempt to perform a GPRS attach if not yet attached and if configured to do so (see AT^SCFG, parameter <gs0aa>). Subsequently, the MT will announce a network request for PDP context activation by issuing the URC RING or CRING to the TE, followed by the intermediate result code CONNECT. The MT then enters V.250 online data state and follows the same procedure as it would after receiving a AT+CGANS=1 command with no <L2P> or <cid> values specified. ATS0=0 does not perform an automatic GPRS detach. Syntax Read Command ATS0? Response(s) <n> OK Write Command ATS0=<n> Response(s) OK Reference(s) PIN GSM 07.07 § ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <n>(num)(&W)(&V) 000(&F) Disables automatic answer mode. 001-255 Enables automatic answering after specified number of rings. Notes • If different settings are used on each interface, and a request for PDP context activation is received, the interface 'wins' which is idle and uses the smallest ATS0 value. • When a network request for PDP context activation is answered automatically and another AT command is issued at the same time on the same interface then this AT command will not be executed. Any response relates to the automatic context activation procedure. If the AT command which caused the collision was a CS data call, the CONNECT response does not pertain to this data call but to GPRS. This can be detected if ATX is not set to 0. The CS data call will issue CONNECT <text>, GPRS will issue CONNECT only. • A network request for PDP context activation has a maximum duration of approximately 40 seconds (for details see GSM 04.08). A RING/CRING URC is issued every 5 seconds, so setting parameter <n> to values greater than 7 will not allow a successful context activation and is not recommended. • Automatic GPRS attach will not be performed on recalling a stored user profile with ATZ or on power-up, even though a value <n> greater than 0 was stored in the user profile with AT&W. • If AT^SCFG="GPRS/ATS0/withAttach","on" is selected, but the automatic GPRS attach attempt fails (e.g. the network rejects the attach request), the ATS0 write command ends up with "ERROR" or "+CME ERROR: unknown" after approx. 5 minutes, though the new <n> value takes effect. This is necessary because ATS0 is used for circuit switched calls too. • ATS0 write command is PIN protected. MC55_ATC_V04.00 Confidential / Released Page 297 of 475 3/17/06 11.20 Using GPRS AT commands (Examples) Examples EXAMPLE 1 Defining and using a Context Definition ID (CID): Every time a CID is used as a parameter for a GPRS command the CID has to be defined before by using the AT+CGDCONT command. To get the parameter of a CID use the AT+CGDCONT read option. If the response of 'AT+CGDCONT?' is OK only, there is no CID defined. AT+CGDCONT? OK There is no CID defined All parameters of the CID are initiated by NULL or not present values, and the CID itself is set to be undefined. To define a CID use the AT+CGDCONT command with at least one CID parameter. At the moment the mobile supports CID 1 and CID 2 by using the AT+CGDCONT command. Define CID 1 and set the PDP type to IP, access point name and IP address are not set: AT+CGDCONT=1,"IP" OK Define CID 2 and sets PDP type, APN and IP addr: AT+CGDCONT=2,"IP", "internet.t-d1.gprs", 111.222.123.234 OK A following read command will respond: AT+CGDCONT? +CGDCONT:1,"IP","","",0,0 +CGDCONT:2,"IP","internet.t-d1.gprs",111.222.123.234 OK Set the CID 1 to be undefined: AT+CGDCONT=1 OK A following read command will respond: AT+CGDCONT? +CGDCONT:2,"IP","internet.t-d1.gprs",111.222.123.234 OK MC55_ATC_V04.00 Confidential / Released Page 298 of 475 3/17/06 EXAMPLE 2 Quality of Service (QoS) is a special parameter of a CID which consists of several parameters itself. The QoS consists of - the precedence class - the delay class - the reliability class - the peak throughput class - the mean throughput class and is divided in "requested QoS" and "minimum acceptable QoS". All parameters of the QoS are initiated by default to the "network subscribed value (= 0)" but the QoS itself is set to be undefined. To define a QoS use the AT+CGQREQ or AT+CGQMIN command. Overwrite the precedence class of QoS of CID 1 and set the QoS of CID 1 to be present: AT+CGQREQ=1,2 OK A following read command will respond: AT+CGQREQ? +CGQREQ: 1,2,0,0,0,0 OK All QoS values of CID 1 are set to network subscribed now, except precedence class which is set to 2. Now set the QoS of CID 1 to not present: AT+CGQREQ=1 OK Once defined, the CID it can be activated. To activate CID 2 use: AT+CGACT=1,2 OK If the CID is already active, the mobile responds OK at once. If no CID and no STATE is given, all defined CIDs will be activated by: AT+CGACT= OK If no CID is defined the mobile responds +CME ERROR: invalid index Remark: If the mobile is NOT attached by AT+CGATT=1 before activating, the attach is automatically done by the AT+CGACT command. After defining and activating a CID it may be used to get online by: AT+CGDATA="PPP",1 CONNECT AT+CGDATA= CONNECT The mobile is connected using the parameters of CID 1. The mobile is connected using default parameters (<L2P>="PPP" and <cid> as described for command AT+CGDATA). The mobile supports Layer 2 Protocol (L2P) PPP only. Remark: If the mobile is NOT attached by AT+CGATT=1 and the CID is NOT activated before connecting, attaching and activating is automatically done by the AT+CGDATA command. Some providers (e.g. Vodafone or E-Plus) require to use an APN to establish a GPRS connection. So if you use the Microsoft Windows Dial-Up Network and ATD*9... to connect to GPRS you must provide the context definition as part of the modem definition (Modem properties/Connection/Advanced.../Extra settings). As an alternative, you can define and activate the context in a terminal program (e.g. Microsoft Hyperterminal) and then use the Dial-Up Network to send only the ATD command. MC55_ATC_V04.00 Confidential / Released Page 299 of 475 3/17/06 11.21 Using the GPRS dial command ATD Example In addition to the GPRS AT commands you can use the "D" command to dial into to the GPRS network. There are two GPRS Service Codes for the ATD command: Values 98 and 99. Examples: ATD*99# CONNECT ATD*99*123.124.125.126*PPP*1# CONNECT ATD*99**PPP# CONNECT ATD*99***1# CONNECT ATD*99**PPP*1# CONNECT ATD*98# CONNECT ATD*98*1# CONNECT MC55_ATC_V04.00 Confidential / Released Establish a connection by service code 99. Establish a connection by service code 99, IP address 123 and L2P = PPP and using CID 1. The CID has to be defined by AT+CGDCONT. Establish a connection by service code 99 and L2P = PPP. Establish a connection by service code 99 and using CID 1. Establish a connection by service code 99 and L2P = PPP and using CID 1. The CID has to be defined by AT+CGDCONT. Establish a connection by service code 98. Establish an IP connection by service code 98 using CID 1. The CID has to be defined by AT+CGDCONT. Page 300 of 475 3/17/06 12. FAX Commands This chapter describes the AT commands used for fax communications. If the ME is acting as a fax modem for a PC based fax application (e.g. "WinFax") it is necessary to select the proper Service Class (Fax Class) provided by the ME. The ME reports its Service Class capabilities, i.e. the current setting and the range of services available. This is provided by the AT+FCLASS command. Service Classes supported by the ME: AT+FCLASS Parameter Service class Reference, Standard 0 Data modem e.g. TIA/EIA-602 or ITU V.250 1 Service Class 1 EIA/TIA-578-A 2 Manufacturer specific This document and EIA PN-2388 (draft) The following AT commands are dummy commands: AT+FAA Auto Answer mode AT+FECM Error Correction Mode control AT+FLNFC Page Length format conversion AT+FLPL Indicate document available for polling AT+FMINSP Minimum Phase C speed AT+FRBC Phase C data receive byte count AT+FREL Phase C received EOL alignment AT+FSPL Enable polling AT+FTBC Phase C data transmit byte count AT+FWDFC Page width format conversion Invoking these commands will not cause ERROR result codes, but these commands have no functionality. 12.1 FAX parameters Below you can find a summary of parameters used by the fax-specific AT commands and responses described in this chapter. Please note that parameter <mod> is dedicated to Fax Class 1 only. All other parameters listed below are for Fax Class 2 only. Parameter Description <mod>(num) Modulation scheme To find out which value is actually supported by <mod> use the test commands while the ME is off-hook. 3 V21 Ch2 - 300 bps 24 V.27ter - 2400 bps 48 V.27ter - 7200 bps 72 V.29 - 7200 bps 96 V.29 - 9600 bps <bf>(num) Binary File Transfer Mode [0] Disable BFT 1 Enable BFT MC55_ATC_V04.00 Confidential / Released Page 301 of 475 3/17/06 <br>(num) Bit Rate 0 2400 bps, V.27ter 1 4800 bps, V.27ter 2 7200 bps, V.29 [3] 9600 bps, V.29 <df>(num) Data Compression Format [0] 1-D modified Huffman 1 2-D modified read 2 2-D uncompressed mode <ec>(num) Error Correction Mode [0] Disable ECM 1 Enable ECM, 64 bytes/frame 2 Enable ECM, 256 bytes/frame <ln>(num) Page Length 0 A4, 297mm 1 B4, 364mm [2] Unlimited length <st>(num) Scan Time/Line [0] 0 ms (at VR= normal) 1 5 ms 2 10 ms 3 10 ms 4 20 ms 5 20 ms 6 40 ms 7 40 ms <vr>(num) Vertical Resolution 0 Normal, 98 lpi [1] Fine, 196 lpi MC55_ATC_V04.00 Confidential / Released Page 302 of 475 3/17/06 <wd>(num) Page Width [0] 1728 pixels in 215mm 1 2048 pixels in 255 mm 2 2432 pixels in 303 mm 3 1216 pixels in 151 mm 4 864 pixels in 107 mm Note • The host application is not required to support all values of the parameters listed above. Depending on the application design it may be sufficient to implement only the default values. See T.31, T.32 and EIA PN-2388 specifications for further advice. 12.1.1 Summary of Fax Class 2 URCs defined by EIA PN-2388 The following URCs are messages indicated in communication only. The URCs are not user definable. Table 12.1: Summary of Fax Class 2 URCs defined by EIA PN-2388 URC Meaning +FCON Indicates connection with a fax machine. +FCSI: <id> Reports the remote ID, called station ID. +FDCS: <vr>, <br>, <wd>, <ln>, <df>, <ec>, <bf>, <st> Reports current session parameters (refer to EIA PN-2388, Table 3.10). +FDIS: <vr>, <br>, <wd>, <ln>, <df>, <ec>, Reports the remote station capabilities (refer to EIA PN-2388, <bf>, <st> Table 3.10). +FET: <stat> Post page message. Indicates whether or not further pages or documents are pending. +FHNG: <stat> Reports that call has been terminated and indicates status. +FNSF: "<param>" Reports non-standard setup frame. +FPTS: "<stat>" Reports the status of received pages. +FTSI: "<id>" Reports the remote ID, transmit station ID. MC55_ATC_V04.00 Confidential / Released Page 303 of 475 3/17/06 12.2 AT+FBADLIN Bad Line Threshold This command defines the Copy-Quality-OK-threshold. If <badlin> consecutive lines have pixel count errors in normal resolution (98 dpi) mode, then the copy quality is unacceptable. If <badlin> * 2 consecutive lines have pixel count errors in fine resolution (196 dpi) mode, then the copy quality is unacceptable. "Copy Quality Not OK" occurs if either the error percentage is too high or too many consecutive lines contain errors. A value of 0 implies that error checking is not present or disabled. Syntax Read Command AT+FBADLIN? Response(s) <badlin> OK Write Command AT+FBADLIN=<badlin> Response(s) OK If error is related to ME functionality ERROR Reference(s) EIA PN-2388 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Parameter Description <badlin>(num) Bad lines 0...10(P)...255 Note • Used for Fax Class 2 only. MC55_ATC_V04.00 Confidential / Released Page 304 of 475 3/17/06 12.3 AT+FBADMUL Error Threshold Multiplier This command defines the "Copy-Quality-OK" multiplier. The number of lines received with a bad pixel count is multiplied by this number. If the result exceeds the total number of lines on the page the error rate is considered too high. A threshold multiplier value of 20 corresponds to a 5 per cent error rate. A value of 0 implies that error checking is not present or disabled. Syntax Read Command AT+FBADMUL? Response(s) <badmul> OK Write Command AT+FBADMUL=<badmul> Response(s) OK If error is related to ME functionality: ERROR Reference(s) EIA PN-2388 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Parameter Description <badmul>(num) 0...20(P)...255 Note • Used for Fax Class 2 only. MC55_ATC_V04.00 Confidential / Released Page 305 of 475 3/17/06 12.4 AT+FBOR Query data Bit Order This command queries the bit order for the receive mode. The mode is set by the ME depending on the selected Service Class, see "AT+FCLASS Fax: Select, read or test service class". Syntax Test Command AT+FBOR=? Response(s) (list of supported <bor>s) OK Read Command AT+FBOR? Response(s) <bor> OK Write Command AT+FBOR=<bor> Response(s) OK Reference(s) EIA PN-2388 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! Last ! ! Parameter Description <bor>(num) bit order modes 0 Direct bit order for both Phase C and for Phase B/D data. [1] Reversed bit order for Phase C data, direct Bit Order for Phase B/D data. Note • Used for Fax Class 2 only. MC55_ATC_V04.00 Confidential / Released Page 306 of 475 3/17/06 12.5 AT+FCIG Query or set the Local Polling ID Syntax Test Command AT+FCIG=? Response(s) (max. length of Local Polling ID string) (range of supported ASCII character values) OK Read Command AT+FCIG? Response(s) <id> OK Write Command AT+FCIG=<id> Response(s) OK Reference(s) EIA PN-2388 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Parameter Description <id>(num) Local Polling ID string, max. length and possible content as reported by test command. Default value is empty string (""). Notes • Used for Fax Class 2 only. • See also AT+FLID Query or set the Local ID setting capabilities. MC55_ATC_V04.00 Confidential / Released Page 307 of 475 3/17/06 12.6 AT+FCLASS Fax: Select, read or test service class AT+FCLASS sets the ME to a particular mode of operation (data, fax). This allows the ME to process information in a manner suitable for that type of information. Syntax Test Command AT+FCLASS=? Response(s) (list of supported <n>s) OK Read Command AT+FCLASS? Response(s) <n> OK Write Command AT+FCLASS=<n> Response(s) OK Reference(s) EIA/TIA-592-A PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Parameter Description <n>(num)(&W)(&V) 0(&F) Data (e.g. EIA/TIA-602 or ITU V.250) 1 Fax class 1 (EIA/TIA-578-A, Service Class 1) 2 Fax class 2 (EIA/TIA SP-2388, an early draft version of EIA/TIA-592-A - Service class 2.1) Notes • Using Error Correcting Mode (ECM) when sending FAXes over GSM should be avoided. • If <n> is set to 1 or 2, all incoming calls will be answered as fax calls when ATA is issued on multiplexer channel 1 resp. ASC0. For calls explicitly signaled as voice or data calls, this procedure will fail with result code "NO CARRIER", but the incoming call will continue to ring. It is possible to change the setting of <n> to 0 while the call is ringing, and accept the call afterwards with ATA. MC55_ATC_V04.00 Confidential / Released Page 308 of 475 3/17/06 12.7 AT+FCQ Copy Quality Checking This command controls Copy Quality checking when receiving a fax. Syntax Test Command AT+FCQ=? Response(s) (list of supported copy quality checking <cq>s) OK Read Command AT+FCQ? Response(s) <cq> OK Write Command AT+FCQ=<cq> Response(s) OK Reference(s) EIA PN-2388 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Parameter Description <cq>(num) 0 No copy quality checking. The ME will generate Copy Quality OK (MCF) responses to complete pages. [1] ME can check 1-D phase data. The connected application must check copy quality for 2-D phase C data. Note • Used for Fax Class 2 only. MC55_ATC_V04.00 Confidential / Released Page 309 of 475 3/17/06 12.8 AT+FCR Capability to Receive Syntax Write Command AT+FCR=<cr> Response(s) OK Reference(s) EIA PN-2388 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Parameter Description <cr>(num) [0] ME will not receive message data. This value can be used when the application has insufficient storage. The ME can send and can be polled for a file. 1 ME can receive message data. Note • Used for Fax Class 2 only. MC55_ATC_V04.00 Confidential / Released Page 310 of 475 3/17/06 12.9 AT+FDCC Query or set capabilities This command allows the connected application to sense and constrain the capabilities of the facsimile DCE (=ME), from the choices defined in CCITT T.30 Table 2. Syntax Test Command AT+FDCC=? Response(s) (list of <vr>s), (list of <br>s), (list of <wd>s), (list of <ln>s), (list of <df>s), (list of <ec>s), (list of <bf>s), (list of <st>s) OK Read Command AT+FDCC? Response(s) <vr>, <br>, <wd>, <ln>, <df>, <ec>, <bf>, <st> OK Write Command AT+FDCC=<vr>, <br>, <wd>, <ln>, <df>, <ec>, <bf>, <st> Response(s) OK Reference(s) EIA PN-2388 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Notes • For further information see AT+FDIS. • Used for Fax Class 2 only. MC55_ATC_V04.00 Confidential / Released Page 311 of 475 3/17/06 12.10 AT+FDFFC Data Compression Format Conversion This command determines the ME response to a mismatch between the data format negotiated for the fax session, reported by the <df> subparameter, and the Phase C data desired by the controlling application, indicated by the optional AT+FDT <df> subparameter, or the AT+FDIS <df> subparameter for AT+FDR operation. Syntax Test Command AT+FDFFC=? Response(s) (list of <df>s) OK Read Command AT+FDFFC? Response(s) <df> OK Write Command AT+FDFFC=<df> Response(s) OK Reference(s) PIN EIA PN-2388 ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Parameter Description <df>(num) [0] Mismatch checking is always disabled. The controlling application has to check the <df> subparameter and transfer matching data. Notes • For further information see AT+FDIS. • Used for Fax Class 2 only. MC55_ATC_V04.00 Confidential / Released Page 312 of 475 3/17/06 12.11 AT+FDIS Query or set session parameters This command allows the controlling application to sense and constrain the capabilities used for the current session. It uses AT+FDIS to generate DIS or DTC messages directly, and uses AT+FDIS and received DIS messages to generate DCS messages. Syntax Test Command AT+FDIS=? Response(s) (list of <vr>s), (list of <br>s), (list of <wd>s), (list of <ln>s), (list of <df>s), (list of <ec>s), (list of <bf>s), (list of <st>s) OK Read Command AT+FDIS? Response(s) <vr>, <br>, <wd>, <ln>, <df>, <ec>, <bf>, <st> OK Write Command AT+FDIS=<vr>, <br>, <wd>, <ln>, <df>, <ec>, <bf>, <st> Response(s) OK Reference(s) EIA PN-2388 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Note • Used for Fax Class 2 only. MC55_ATC_V04.00 Confidential / Released Page 313 of 475 3/17/06 12.12 AT+FDR Begin or continue phase C Data Reception The command initiates transition to Phase C data reception. Syntax Exec Command AT+FDR Response(s) CONNECT or OK If error related to ME functionality ERROR Reference(s) EIA PN-2388 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Note • Used for Fax Class 2 only. MC55_ATC_V04.00 Confidential / Released Page 314 of 475 3/17/06 12.13 AT+FDT Data Transmission This command requests the ME to transmit a Phase C page. When the ME is ready to accept Phase C data, it issues the negotiation responses and the CONNECT result code to the application. In Phase B, the AT+FDT command releases the ME to proceed with negotiation, and releases the DCS message to the remote station. In Phase C, the AT+FDT command resumes transmission after the end of a data stream transmitted before. Syntax Exec Command AT+FDT Response(s) CONNECT Write Command AT+FDT=<df>, <vr>, <wd>, <ln> Response(s) CONNECT Reference(s) EIA PN-2388 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Note • Used for Fax Class 2 only. MC55_ATC_V04.00 Confidential / Released Page 315 of 475 3/17/06 12.14 AT+FET End a page or document This command indicates that the current page or partial page is complete. An ERROR response code results if this command is issued while the mode is on-hook. Syntax Write Command AT+FET=<ppm> Response(s) OK Reference(s) EIA PN-2388 PIN ! ASC0 ASC1 % MUX1 MUX2 % ! ! MUX3 Charge ! ! ! Last ! Parameter Description <ppm>(num) Post Page Message Codes 1 Another document next 2 No morepages or documents 4 Another page, procedure interrupt 5 Another document, procedure interrupt Note • Used for Fax Class 2 only. MC55_ATC_V04.00 Confidential / Released Page 316 of 475 3/17/06 12.15 AT+FK Kill operation, orderly FAX abort This command causes the TA to terminate the session in an orderly manner. Syntax Exec Command AT+FK Response(s) OK PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Note • Used for Fax Class 2 only MC55_ATC_V04.00 Confidential / Released Page 317 of 475 3/17/06 12.16 AT+FLID Query or set the Local Id setting capabilities Syntax Test Command AT+FLID=? Response(s) (max. character length of Local ID string) (range of supported ASCII character values) OK Read Command AT+FLID? Response(s) <lid> OK Write Command AT+FLID=<lid> Response(s) OK Reference(s) EIA PN-2388 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Parameter Description <lid>(num) Local ID string Max. length and possible content as reported by test command. Default value is empty string (""). Notes • Used for Fax Class 2 only. • See also AT+FCIG. MC55_ATC_V04.00 Confidential / Released Page 318 of 475 3/17/06 12.17 AT+FMDL Identify Product Model This command sends the model identification to the TA. Syntax Read Command AT+FMDL? Response(s) Gipsy Soft Protocolstack OK Reference(s) PIN SIEMENS ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Note • Used for Fax Class 2 only. MC55_ATC_V04.00 Confidential / Released Page 319 of 475 3/17/06 12.18 AT+FMFR Request Manufacturer Identification This command sends the manufacturer identification to the TA. Syntax Read Command AT+FMFR? Response(s) SIEMENS OK Reference(s) PIN SIEMENS ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Note • Used for Fax Class 2 only MC55_ATC_V04.00 Confidential / Released Page 320 of 475 3/17/06 12.19 AT+FOPT Set bit Order independently Model specific command to set bit order independently of the understanding which is "mirrored" and which is direct. Syntax Write Command AT+FOPT=<opt> Response(s) OK Reference(s) PIN SIEMENS ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Parameter Description <opt>(num) 0 Non-standard 1 Standard Note • Used for Fax Class 2 only. MC55_ATC_V04.00 Confidential / Released Page 321 of 475 3/17/06 12.20 AT+FPHCTO DTE Phase C Response Timeout The timeout value <tout> determines how long the DCE will wait for a command after reaching the end of data when transmitting in Phase C. When timeout is reached, the DCE assumes that there are no more pages or documents to send. Syntax Read Command AT+FPHCTO? Response(s) <tout> OK Write Command AT+FPHCTO=<tout> Response(s) OK If error is related to ME functionality ERROR Reference(s) EIA PN-2388 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Parameter Description <tout>(num) Timeout Value in 100ms units 0...30(P)...255 Note • Used for Fax Class 2 only. MC55_ATC_V04.00 Confidential / Released Page 322 of 475 3/17/06 12.21 AT+FREV Identify Product Revision This comand sends the revision identification to the TA. Syntax Read Command AT+FREV? Response(s) V2.550 OK Reference(s) PIN SIEMENS ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Note • Used for Fax Class 2 only. MC55_ATC_V04.00 Confidential / Released Page 323 of 475 3/17/06 12.22 AT+FRH Receive Data Using HDLC Framing The AT+FRH command enables the TA to receive frames using the HDLC protocol and the modulation schemes defined in Section 12.1, FAX parameters. An ERROR response code results if the command is issued while the modem is on-hook. The test command can be used in off-hook mode to check the modulation schemes supported by MC55. Syntax Test Command AT+FRH=? Response(s) In off-hook mode only: +FRH:(list of <mod>s) OK In on-hook mode: ERROR Write Command AT+FRH=<mod> Response(s) CONNECT If error is related to ME functionality ERROR Reference(s) TIA/EIA-578 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Note • Used for Fax Class 1 only. MC55_ATC_V04.00 Confidential / Released Page 324 of 475 3/17/06 12.23 AT+FRM Receive Data The AT+FRM command causes the TA to enter the receive mode, using one of the modulation schemes defined in Section 12.1, FAX parameters. An ERROR response code results if the write command is issued while the modem is on-hook. The test command can be used in on-hook or off-hook mode to check the modulation schemes supported by MC55. Syntax Test Command AT+FRM=? Response(s) (list of <mod>s) OK Write Command AT+FRM=<mod> Response(s) CONNECT If error is related to ME functionality: ERROR Reference(s) TIA/EIA-578 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Notes • Used for Fax Class 1 only. • <mod>= 3 is not possible. MC55_ATC_V04.00 Confidential / Released Page 325 of 475 3/17/06 12.24 AT+FRS Receive Silence <time>=n causes the TA to report an OK result code to the TE after the specified period of silence was detected on the line. The command is aborted if any character is received by the TE. The modem discards the aborting character and issues an OK result code. An ERROR response code results if this command is issued while the mode is onhook. Syntax Write Command AT+FRS=<time> Response(s) OK If error is related to ME functionality: ERROR Reference(s) TIA/EIA-578 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Parameter Description <time>(num) Number of 10 millisecond intervals 0...255 Note • Used for Fax Class 1 only MC55_ATC_V04.00 Confidential / Released Page 326 of 475 3/17/06 12.25 AT+FTH Transmit Data Using HDLC Framing The AT+FTH command causes the TA to transmit data using the HDLC protocol and the modulation schemes defined in Section 12.1, FAX parameters. An ERROR response code results if the command is issued while the modem is on-hook. The test command can be used in off-hook mode to check the modulation schemes supported by MC55. Syntax Test Command AT+FTH=? Response(s) In off-hook mode only: +FTH:(list of <mod>s) OK In on-hook mode: ERROR Write Command AT+FTH=<mod> Response(s) CONNECT Reference(s) TIA/EIA-578 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Note • Used for Fax Class 1 only MC55_ATC_V04.00 Confidential / Released Page 327 of 475 3/17/06 12.26 AT+FTM Transmit Data The AT+FTM command causes the TA to transmit data, using one of the modulation schemes defined in Section 12.1, FAX parameters. An ERROR response code results if the write command is issued while the modem is on-hook. The test command can be used in on-hook or off-hook mode to check the modulation schemes supported by MC55. Syntax Test Command AT+FTM=? Response(s) (list of <mod>s) OK Write Command AT+FTM=<mod> Response(s) CONNECT If error is related to ME functionality: ERROR Reference(s) TIA/EIA-578 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Notes • Used for Fax Class 1 only. • <mod>= 3 is not possible MC55_ATC_V04.00 Confidential / Released Page 328 of 475 3/17/06 12.27 AT+FTS Stop Transmission and Wait This command causes the TA to terminate a transmission and wait for <time> 10 millisecond intervals before sending the OK result code to the TE. Syntax Write Command AT+FTS=<time> Response(s) OK In on-hook mode: ERROR Reference(s) TIA/EIA-578 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Parameter Description <time>(num) no. of 10 millisecond intervals 0...85 Note • Used for Fax Class 1 only MC55_ATC_V04.00 Confidential / Released Page 329 of 475 3/17/06 12.28 AT+FVRFC Vertical Resolution Format Conversion This command determines the DCE response to a mismatch between the vertical resolution negotiated for the facsimile session and the Phase C data desired by the DTE. Syntax Test Command AT+FVRFC=? Response(s) (list of supported <vrfc>s) OK Read Command AT+FVRFC? Response(s) <vrfc> OK Write Command AT+FVRFC=<vrfc> Response(s) OK Reference(s) EIA PN-2388 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Parameter Description <vrfc>(num) 0 Disable mismatch checking. [2] Enable mismatch checking, with resolution conversion of 1-D data in the DCE, and an implied AT+FK command executed on 2-D mismatch detection. Note • Used for Fax Class 2 only. MC55_ATC_V04.00 Confidential / Released Page 330 of 475 3/17/06 13. Short Message Service (SMS) Commands The AT Commands described in this chapter allow an external application to use the Short Message Service with the MC55. 13.1 SMS parameters Parameter Description <ackpdu>(num) Format is same for <pdu> in case of SMS, but without GSM 24.11 SC address field and parameter shall be bounded by double quote characters like a normal string type rarameter <alpha>(str)(+CSCS) String type alphanumeric representation of <da> or <oa> corresponding to the entry found in phonebook; implementation of this feature is manufacturer specific <cdata>(num) Command Data GSM 03.40 TP-Command-Data in text mode responses; ME/TA converts each 8-bit octet into two IRA character long hexadecimal numbers (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65)) <ct>(num) Command Type GSM 03.40 TP-Command-Type in integer format [0]...255 <da>(num)(+CSCS) Destination Address GSM 03.40 TP- Destination-Address Address-Value field in string format; BCD numbers (or GSM default alphabet characters) are converted into characters; type of address given by <toda> <data>(num)(+CSCS) User Data In case of SMS: GSM 03.40 TP-User-Data in text mode responses; format: • If <dcs> indicates that GSM 03.38 default alphabet is used and <fo> indicates that GSM 03.40 TP-UserData-Header-Indication is not set: ME/TA converts GSM alphabet into current TE character set according to rules covered in Annex A. • If <dcs> indicates that 8-bit or UCS2 data coding scheme is used, or <fo> indicates that GSM 03.40 TPUser-Data-Header-Indication is set: ME/TA converts each 8-bit octet into hexadecimal numbers con-taining two IRA characters (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65). In case of CBS: GSM 03.41 CBM Content of Message in text mode responses; format: • If <dcs> indicates that GSM 03.38 default alphabet is used: ME/TA converts GSM alphabet into current TE character set according to rules covered in Annex A. • If <dcs> indicates that 8-bit or UCS2 data coding scheme is used: ME/TA converts each 8-bit octet into hexadecimal numbers containing two IRA characters. MC55_ATC_V04.00 Confidential / Released Page 331 of 475 3/17/06 <dt>(num) Discharge Time GSM 03.40 TP-Discharge-Time in time-string format: "yy/MM/dd,hh:mm:ss+zz", where characters indicate year (two last digits), month, day, hour, minutes, seconds and time zone. For example, 6th of May 1994, 22:10:00 GMT+2 hours equals "94/05/06,22:10:00+08" <index>(num) Integer type; value in the range of location numbers supported by the associated memory <length>(num) Message Length Integer type value indicating in the text mode (AT+CMGF=1) the length of the message body <data> (or <cdata>) in characters; or in PDU mode (AT+CMGF=0), the length of the actual TP data unit in octets (i.e. the RP layer SMSC address octets are not counted in the length) In text mode, the maximum length of an SMS depends on the used coding scheme: It is 160 characters if the 7 bit GSM coding scheme is used, and 140 characters according to the 8 bit GSM coding scheme. If the SMS message format is ''text mode'' (AT+CMGF=1) and the character set is set to ''UCS2'' with AT+CSCS and the SMS is also coded as "UCS2" (see <dcs> of AT+CSMP), then the length is in octets instead of characters. <mem1>(str) Memory to be used when listing, reading and deleting messages: "SM" SIM message storage "ME" Mobile Equipment message storage "MT" (D) Sum of "SM" and "ME" storages <mem2>(str) Memory to be used when writing and sending messages: "SM" SIM message storage "ME" Mobile Equipment message storage "MT" (D) Sum of "SM" and "ME" storages <mem3>(str) Received messages will be placed in this memory storage if routing to TE is not set. See command AT+CNMI with parameter <mt>=2. "SM" "MT" (D) SIM message storage Sum of "SM" and "ME" storages <mid>(num) Message Identifier GSM 03.41 CBM Message Identifier in integer format <mn>(num) Message Number GSM 03.40 TP-Message-Number in integer format MC55_ATC_V04.00 Confidential / Released Page 332 of 475 3/17/06 <mr>(num) Message Reference GSM 03.40 TP-Message-Reference in integer format <oa>(num)(+CSCS) Originating Address GSM 03.40 TP-Originating-Address Address-Value field in string format; BCD numbers (or GSM default alphabet characters) are converted into characters; type of address given by <tooa> <page>(num) Page Parameter GSM 03.41 CBM Page Parameter bits 4-7 in integer format <pages>(num) Page Parameter GSM 03.41 CBM Page Parameter bits 0-3 in integer format <pdu>(num) In the case of SMS: GSM 04.11 SC address followed by GSM 03.40 TPDU in hexadecimal format: ME/TA converts each octet of TP data unit into hexadecimal numbers containing two IRA characters (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65)). In the case of CBS: <ra> GSM 03.40 TPRecipient-Address Ad-dress-Value field in string format; BCD numbers (or GSM default alphabet characters) are converted into characters; type of address given by <tora> <ra>(num)(+CSCS) Recipient Address GSM 03.40 TP-Recipient-Address Address-Value field in string format; BCD numbers (or GSM default alphabet characters) are converted to characters of the currently selected TE character set (refer to command AT+CSCS.); type of address given by <tora> <sca>(num)(+CSCS) Service Center Address GSM 04.11 RP SC address Address-Value field in string format; BCD numbers (or GSM default alphabet characters) are converted to characters of the currently selected TE character set (refer to command AT+CSCS); type of address given by <tosca> <scts>(num) Service Centre Time Stamp GSM 03.40 TP-Service-Centre-Time-Stamp in time-string format (refer <dt>) <sn>(num) Serial Number GSM 03.41 CBM Serial Number in integer format MC55_ATC_V04.00 Confidential / Released Page 333 of 475 3/17/06 <st>(num) Status GSM 03.40 TP-Status in integer format 0...255 <stat>(str) Message status 3GPP 27.005 Interface of SMS and CB. Indicates the status of message in memory. Description text mode (<mode>=1) PDU mode (<mode>=0) Default Received unread messages "REC UNREAD" 0 for SMS reading commands Received read messages "REC READ" 1 Stored unsent messages "STO UNSENT" 2 Stored sent messages "STO SENT" 3 All messages "ALL" 4 for SMS writing commands <toda>(num) Type of Destination Address GSM 04.11 TP-Destination-Address Type-of-Address octet in integer format (when first character of <da> is + (IRA 43) default is 145, otherwise default is 129) 0...255 <tooa>(num) Type of Originating Address GSM 04.11 TP-Originating-Address Type-of-Address octet in integer format (default refer <toda>) <tora>(num) Type of Recipient Address GSM 04.11 TP-Recipient-Address Type-of-Address octet in integer format (default refer <toda>) <tosca>(num) Type of Service Center Address GSM 04.11 RP SC address Type-of-Address octet in integer format (default refer <toda>) MC55_ATC_V04.00 Confidential / Released Page 334 of 475 3/17/06 13.2 AT+CMGC Send an SMS command Syntax Test Command AT+CMGC=? Response(s) OK Write Command If text mode (see AT+CMGF=1) AT+CMGC=<fo>, <ct>[, <pid>[, <mn>[, <da>[, <toda>]]]]<CR> Text can be entered <CTRL-Z>/<ESC> Response(s) +CMGC: <mr>[, <scts>] If sending fails ERROR +CMS ERROR Write Command If PDU mode (see AT+CMGF=0) AT+CMGC=<length><CR> PDU can be entered <CTRL-Z>/<ESC> Response(s) +CMGC: <mr>[, <ackpdu>] OK If sending fails ERROR +CMS ERROR Reference(s) PIN GSM 07.05 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Notes • • After invoking the commands AT+CMGW, AT+CMGS or AT+CMGC it is necessary to wait for the prompt ">" before entering text or PDU. After the prompt a timer will be started to observe the input. At baudrates below 19200 it is recommended to use the line termination character only (refer to ATS3, default <CR>) before entering the text or PDU. Use of the line termination character followed by the response formatting character (refer to ATS4, default <LF> can cause problems MC55_ATC_V04.00 Confidential / Released Page 335 of 475 3/17/06 13.3 AT+CMGD Delete short message The write command deletes a short message from the preferred message storage <mem1> location <index>. Syntax Test Command AT+CMGD=? Response(s) OK Write Command AT+CMGD=<index> Response(s) OK ERROR +CMS ERROR Reference(s) PIN GSM 07.05 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Notes • If there is no short message stored at the selected index, the response is OK too. • Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data may not yet be accessible, resulting in a short delay before the requested AT command response is returned. See Section 20.1, Restricted access to SIM data after SIM PIN authentication for further detail. MC55_ATC_V04.00 Confidential / Released Page 336 of 475 3/17/06 13.4 AT+CMGF Select SMS message format Syntax Test Command AT+CMGF=? Response(s) +CMGF: (list of supported<mode>s) OK Read Command AT+CMGF? Response(s) +CMGF: <mode> OK Write Command AT+CMGF=<mode> Response(s) OK Reference(s) PIN GSM 07.05 ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description The write command specifies the input and output format of the short messages. Parameter Description <mode>(num)(&W)(&V) [0](&F) PDU mode 1 Text mode MC55_ATC_V04.00 Confidential / Released Page 337 of 475 3/17/06 13.5 AT+CMGL List SMS messages from preferred store The write command returns messages with status value <stat> from message storage <mem1> to the TE. If the status of the message is 'received unread', the status in the storage changes to 'received read'. The execute command is the same as the write command with the given default for <stat>. Syntax Test Command AT+CMGL=? Response(s) +CMGL: (list of supported <stat>s) OK Exec Command AT+CMGL Response(s) +CMGL: (see write command for default of <stat>) OK Write Command AT+CMGL=<stat> Response(s) Output if text mode (AT+CMGF=1) and command successful: For SMS- SUBMITs and/or SMS-DELIVERs +CMGL: <index>, <stat>, <oa>/<da>, [<alpha>], [<scts>][, <tooa>/<toda>, <length>] <data> [... ] OK For SMS-STATUS-REPORTs +CMGL: <index>, <stat>, <fo>, <mr>, [<ra>], [<tora>], <scts>, <dt>, <st> [... ] OK For SMS-Commands +CMGL: <index>, <stat>, <fo>, <ct> [... ] OK Output if PDU mode AT+CMGF=0 and command successful: For SMS-SUBMITs and/or SMS-DELIVERs +CMGL: <index>, <stat>, [<alpha>], <length> <pdu> [... ] OK If error is related to ME functionality ERROR +CMS ERROR Reference(s) PIN GSM 07.05 % MC55_ATC_V04.00 Confidential / Released ASC0 ASC1 % Page 338 of 475 % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! 3/17/06 Notes • The selected <mem1> can contain different types of SMs (e.g. SMS-DELIVERs, SMS-SUBMITs, SMS-STATUS-REPORTs and SMS-COMMANDs), the response may be a mix of the responses of different SM types. TE application can recognize the response format by examining the third response parameter. • The parameters <ra> and <tora> will only be displayed if parameter <ra> of the AT^SSCONF command is set to 1. • Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data may not yet be accessible, resulting in a short delay before the requested AT command response is returned. See Section 20.1, Restricted access to SIM data after SIM PIN authentication for further detail. MC55_ATC_V04.00 Confidential / Released Page 339 of 475 3/17/06 13.6 AT+CMGR Read SMS messages The write command returns SMS message with location value <index> from message storage <mem1> to the TE. If status of the message is 'received unread', status in the storage changes to 'received read'. Syntax Test Command AT+CMGR=? Response(s) OK Write Command AT+CMGR=<index> Response(s) Output if text mode (AT+CMGF=1) and command successful: For SMS-DELIVER +CMGR: <stat>, <oa>, [<alpha>], <scts>[, <tooa>, <fo>, <pid>, <dcs>, <sca>, <tosca>, <length>] <data> [... ] OK For SMS-SUBMIT +CMGR: <stat>, <da>, [<alpha>][, <toda>, <fo>, <pid>, <dcs>, [<vp>], <sca>, <tosca>, <length>] <data> [... ] OK For SMS-STATUS-REPORT +CMGR: <stat>, <fo>, <mr>, [<ra>], [<tora>], <scts>, <dt>, <st> <data> [... ] OK For SMS-Commands +CMGR: <stat>, <fo>, <ct>[, <pid>, [<mn>], [<da>], [<toda>], <length>] <data> [... ] OK Output if PDU mode (AT+CMGF=0) and command successful: For SMS-SUBMITs and/or SMS-DELIVERs +CMGR: <stat>, [<alpha>], <length> <pdu> [... ] OK ERROR +CMS ERROR Reference(s) PIN GSM 07.05 % MC55_ATC_V04.00 Confidential / Released ASC0 ASC1 % Page 340 of 475 % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! 3/17/06 Notes • Response if AT+CMGR is used to read an empty record index: +CMGR: 0,,0 • Response if AT+CMGR is used to read a non-existent record index: +CMS ERROR: invalid memory index • The parameters <ra> and <tora> will only be displayed if parameter <ra> of the AT^SSCONF command is set to 1. • Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data may not yet be accessible, resulting in a short delay before the requested AT command response is returned. See Section 20.1, Restricted access to SIM data after SIM PIN authentication for further detail. MC55_ATC_V04.00 Confidential / Released Page 341 of 475 3/17/06 13.7 AT+CMGS Send Short Message The write command transmits a short message from TE to network (SMS-SUBMIT). After invoking the write command wait for the prompt ">" and then start to write the message. To send the message simply enter <CTRL-Z>. After the prompt a timer will be started to observe the input. To abort sending use <ESC>. Abortion is acknowledged with "OK", though the message will not be sent. The message reference <mr> is returned to the TE on successful message delivery. The value can be used to identify the message in a delivery status report provided as an unsolicited result code. Syntax Test Command AT+CMGS=? Response(s) OK Write Command If text mode (see AT+CMGF=1) AT+CMGS=<da>[, <toda>]<CR> Text can be entered. <CTRL-Z>/<ESC> Response(s) +CMGS: <mr>[, <scts>] OK If sending fails see notes below. Write Command If PDU mode (see AT+CMGF=0) AT+CMGS=<length><CR> PDU can be entered. <CTRL-Z>/<ESC> Response(s) +CMGS: <mr>[, <ackpdu>] OK If sending fails see notes below. Reference(s) PIN GSM 07.05 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Notes • If sending fails, for example, if a message is too long, the result code depends on the current setting of the AT^SM20 command: If the AT^SM20 <CmgwMode> equals 1 (factory default) any failure to send a message is responded with "OK". Users should be aware, that despite the "OK" response, the message will not be sent to the subscriber. If the AT^SM20 <CmgwMode> equals 0 any failure to send a message is responded with "ERROR". • If sending fails due to timeout, then AT^SM20 <CmgwMode>=1 causes "+CMS ERROR: Unknown error" to be returned; AT^SM20 <CmgwMode>=0 causes "+CMS ERROR: timer expired" to be returned. • Note that some providers do not recognize an @ symbol used in a short message. A widely used alternative is typing "*" as defined in GSM 03.40 (GPP TS 23.40). • All characters entered behind the prompt ">" will be recognized as GSM characters. For example, "Backspace" (ASCII character 8) does not delete a character, but will be inserted into the short message as an additional physical character. As a result, the character you wanted to delete still appears in the text, plus the GSM code equivalent of the Backspace key. MC55_ATC_V04.00 Confidential / Released Page 342 of 475 3/17/06 • Message Length in Text Mode The maximum length of a short message depends on the used coding scheme: It is 160 characters if the 7 bit GSM coding scheme is used, and 140 characters according to the 8 bit GSM coding scheme. In case UCS2 character set selected it is highly recommended to set Data Coding Scheme (<dcs> of AT+CSMP) to 16-bit data, otherwise the length of sms user data is restricted to 88 octets. Even better for messages with UCS2 character set is the PDU Mode. • At baudrates lower than 19200 it is recommended to use the line termination character only (refer to <n> of ATS3, default <CR>) before entering text or PDU. Use of the line termination character followed by the response formatting character (see <n> of ATS4, default <LF>) can cause problems. MC55_ATC_V04.00 Confidential / Released Page 343 of 475 3/17/06 13.8 AT+CMGW Write Short Messages to Memory The execute and write commands transmit a short message (either SMS-DELIVER or SMS-SUBMIT) from TE to memory storage <mem2>. Memory location <index> of the stored message is returned. Message status will be set to 'stored unsent' unless otherwise given in parameter <stat>. After invoking the execute or write command wait for the prompt ">" and then start to write the message. To save the message simply enter <CTRL-Z>. After the prompt a timer will be started to observe the input. To abort writing use <ESC>. Abortion is acknowledged with "OK", though the message will not be saved. Syntax Test Command AT+CMGW=? Response(s) OK Exec Command If text mode (see AT+CMGF=1): AT+CMGW Response(s) <CR> Text can be entered. <CTRL-Z>/<ESC> +CMGW: <index> OK If writing fails ERROR +CMS ERROR Write Command If text mode (see AT+CMGF=1): AT+CMGW=<oa>/<da>[, [<tooa>/<toda>][, <stat>]]<CR> Text can be entered. <CTRL-Z>/<ESC> Response(s) +CMGW: <index> OK If writing fails see notes below. Write Command If PDU mode (see AT+CMGF=0): AT+CMGW=<length>[, <stat>]<CR> PDU can be entered. <CTRL-Z>/<ESC> Response(s) +CMGW: <index> OK If writing fails see notes below. Reference(s) PIN GSM 07.05 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Notes • If writing fails, for example, if a message is too long, the result code depends on the current setting of the AT^SM20 command: If the AT^SM20 <CmgwMode>=1 (factory default) any failure to send a message is responded with "OK". Users should be aware, that despite the "OK" response, the message will not be written to the selected SMS storage. If the AT^SM20 <CmgwMode> equals 0 any failure to write a message is responded with "ERROR". MC55_ATC_V04.00 Confidential / Released Page 344 of 475 3/17/06 • If writing fails due to timeout, then AT^SM20 <CmgwMode>=1 causes "+CMS ERROR: Unknown error" to be returned; AT^SM20 <CmgwMode>=0 causes "+CMS ERROR: timer expired" to be returned. • Note that some providers do not recognize an @ symbol used in a short message. A widely used alternative is typing "*" as defined in GSM 03.40 (GPP TS 23.40). • For baudrates lower than 19200 it is recommended to use the line termination character only (refer to ATS3= <n>, default <CR>) before entering the text or PDU. Use of the line termination character followed by the response formating character (see ATS4= <n>, default <LF>) may cause problems. • SMS-COMMANDs and SMS-STATUS-REPORTs cannot be stored in text mode. • All characters entered behind the ">" prompt will be recognized as GSM characters. For example, "Backspace" (ASCII character 8) does not delete a character, but will be inserted into the short message as an additional physical character. As a result, the character you wanted to delete still appears in the text, plus the GSM code equivalent of the Backspace key. • Message Length in Text Mode The maximum length of a short message depends on the used coding scheme: It is 160 characters if the 7 bit GSM coding scheme is used, and 140 characters according to the 8 bit GSM coding scheme. In case UCS2 character set selected it is highly recommended to set Data Coding Scheme (<dcs> of AT+CSMP) to 16-bit data, otherwise the length of sms user data is restricted to 88 octets. Even better for messages with UCS2 character set is the PDU Mode. • The length of 8-bit data coded short messages has to be greater than 0. MC55_ATC_V04.00 Confidential / Released Page 345 of 475 3/17/06 13.9 AT+CMSS Send short messages from storage The write command sends message with location value <index> from message storage <mem2> to the network (SMS-SUBMIT or SMS-COMMAND). If new recipient address <da> is given for SMS-SUBMIT, it shall be used instead of the one stored with the message. Reference value <mr> is returned to the TE on successful message delivery. Value can be used to identify message upon unsolicited delivery status report result code. If the optional parameter <da> is given, the old status of the short message at <index> remains unchanged (see <stat>). Syntax Test Command AT+CMSS=? Response(s) OK Write Command If text mode (AT+CMGF=1): AT+CMSS=<index>[, <da>[, <toda>]] Response(s) +CMSS: <mr>[, <scts>] OK If sending fails ERROR +CMS ERROR Write Command If PDU mode (AT+CMGF=0): AT+CMSS=<index>[, <da>[, <toda>]] Response(s) +CMSS: <mr>[, <ackpdu>] OK If sending fails ERROR +CMS ERROR Reference(s) PIN GSM 07.05 % MC55_ATC_V04.00 Confidential / Released ASC0 ASC1 % Page 346 of 475 % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! 3/17/06 13.10 AT+CNMA New Message Acknowledgement to ME/TE, only phase 2+ The write / execute command confirms successful receipt of a new message (SMS-DELIVER or SMS-STATUSREPORT) routed directly to the TE. TA shall not send another +CMT or +CDS result code to TE until previous one is acknowledged. If ME does not receive acknowledgement within required time (network time-out), ME sends RP-ERROR to the network. TA shall automatically disable routing to TE by setting both <mt> and <ds> values of AT+CNMI to zero. Syntax Test Command AT+CNMA=? Response(s) +CNMA: (list of supported <n>s) OK Exec Command AT+CNMA Response(s) OK ERROR +CMS ERROR Write Command AT+CNMA=<n> Response(s) OK ERROR +CMS ERROR Reference(s) PIN GSM 07.05 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <n>(num) Parameter required only for PDU mode. 0 Command operates similarly as in text mode. Notes • The execute / write command shall only be used when AT+CSMS parameter <service> equals 1 (= phase 2+). • The execute command can be used no matter whether text mode or PDU mode is activated. The write command is designed for the PDU mode only. • If multiplex mode is activated (AT+CMUX=0) the AT+CNMI parameter will be set to zero on all channels, if one channel fails to acknowledge an incoming message within the required time. MC55_ATC_V04.00 Confidential / Released Page 347 of 475 3/17/06 13.11 AT+CNMI New short Message Indication The write command selects the procedure how the receipt of new short messages from the network is indicated to the TE when TE is active, e.g. DTR signal is ON. If TE is inactive (e.g. DTR signal is OFF), message receiving should be done as specified in GSM 03.38. If the DTR signal is not available or the state of the signal is ignored (V.250 command AT&D0, reliable message transfer can be assured by using AT+CNMA acknowledgment procedure. The rules <mt>=2 and <mt>=3 for storing received messages are possible only if phase 2+ compatibility is activated with AT+CSMS=1. The parameter <ds>=1 is only available in phase 2+ Syntax Test Command AT+CNMI=? Response(s) +CNMI: (list of supported<mode>s), (list of supported <mt>s), (list of supported <bm>s), (list of supported <ds>s), (list of supported <bfr>s) OK Read Command AT+CNMI? Response(s) +CNMI: <mode>, <mt>, <bm>, <ds>, <bfr> OK Write Command AT+CNMI=[<mode>][, <mt>][, <bm>][, <ds>][, <bfr>] Response(s) OK ERROR +CMS ERROR Reference(s) PIN GSM 07.05 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Unsolicited Result Codes URC 1 <mt>=1: +CMTI: <mem3>, <index> Indicates that new message has been received URC 2 <mt>=2 (PDU mode enabled): +CMT: <length><CR><LF><pdu> Indicates that new message has been received URC 3 <mt>=2 (text mode enabled): +CMT: <oa>, <scts>[, <tooa>, <fo>, <pid>, <dcs>, <sca>, <tosca>, <length>]<CR><LF><data> Indicates that new messagehas been received MC55_ATC_V04.00 Confidential / Released Page 348 of 475 3/17/06 URC 4 <bm>=2 (PDU mode enabled): +CBM: <length><CR><LF><pdu> Indicates that new cell broadcast message has been received URC 5 <bm>=2 (text mode enabled): +CBM: <sn>, <mid>, <dcs>, <page>, <pages><CR><LF><data> Indicates that new cell broadcast message has been received URC 6 <ds>=1 (PDU mode enabled): +CDS: <length><CR><LF><pdu> Indicates that new SMS status report has been received URC 7 <ds>=1 (text mode enabled): +CDS: <fo>, <mr>[, <ra>][, <tora>], <scts>, <dt>, <st> Indicates that new SMS status report has been received URC 8 <ds>=2: +CDSI: <mem3>, <index> Indicates that new SMS status report has been received Parameter Description <mode>(num)(&W) [0](&F) Buffer unsolicited result codes in the TA. If TA result code buffer is full, indications can be buffered in some other place or the oldest indications may be discarded and replaced with the new received indications. 1 Discard indication and reject new received message unsolicited result codes when TA-TE link is reserved (e.g. in on-line data mode). Otherwise forward them directly to the TE. 2 Buffer unsolicited result codes in the TA when TA-TE link is reserved (e.g. in on-line data mode) and flush them to the TE after reservation. Otherwise forward them directly to the TE. 3 Forward unsolicited result codes directly to the TE. TA-TE link specific inband technique used to embed result codes and data when TA is in on-line data mode. Signaling of unsolicited result codes is configured by AT^SCFG <mt>(num)(&W)(&V) Rules for storing received short messages depend on the relevant data coding method (refer to GSM 03.38), preferred memory storage (AT+CPMS) setting and this value. Note: If AT command interface is acting as the only display device, the ME must support storage of class 0 messages and messages in the message waiting indication group (discard message) [0](&F) No SMS-DELIVER indications are routed to the TE. 1 If SMS-DELIVER is stored in ME/TA, indication of the memory location is routed to the TE using unsolicited result code: MC55_ATC_V04.00 Confidential / Released Page 349 of 475 3/17/06 2 SMS-DELIVERs, except class 2 messages and messages in the message waiting indication group (store message) are routed directly to the TE using unsolicited result code: 3 Class 3 SMS-DELIVERs are routed directly to the TE using unsolicited result codes defined in <mt>=2. Messages of other data coding schemes result in indication as defined in <mt>=1. <bm>(num)(&W)(&V) Rules for storing received CBMs depend on the relevant data coding method (refer to GSM 03.38), the setting of Select CBM Types (AT+CSCB) and this value: [0](&F) No CBM indications are routed to the TE. 2 New CBMs are routed directly to the TE using unsolicited result code: 3 Class 3 CBMs are routed directly to TE using unsolicited result codes defined in <bm>=2. <ds>(num)(&W)(&V) [0](&F) No SMS-STATUS-REPORTs are routed to the TE. 1 SMS-STATUS-REPORTs are routed to the TE using unsolicited result code: 2 If SMS-STATUS-REPORT is routed into ME/TA, indication of the memory location is routed to the TE using unsolicited result code: <bfr>(num)(&V) [1](&F) TA buffer of unsolicited result codes defined within this command is cleared when <mode> changes from 0 to 1...3. <index>(num) Integer type; value in the range of location numbers supported by the associated memory Notes • Parameters <mt>=2,3 and <ds>=1 are only available with GSM phase 2+ (see AT+CSMS=1). Incoming SMs or Status Reports have to be acknowledged with AT+CNMA=0 when using these phase 2+ parameters. • Requirements specific to Multiplex mode: In multiplex mode (AT+CMUX=0) only one channel can use a phase 2+ parameter. The parameter for <mt> and <ds> on the other channels have to be set to zero. If either a SM or a Status Report is not acknowledged, all AT+CNMI parameter in all channels will be set to zero. • If the ME operates on different instances (MUX channels 1, 2, 3 or ASC0/ASC1) avoid different settings for routing and indicating short messages. 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. • Handling of Class 0 short messages: If the host application is provided with a display and AT^SSDA=1 has been set Class 0 short messages can be displayed immediately. If the host application does not include a display, ME handles Class 0 short messages as though there was no message class, i.e. it will ignore bits 0 and 1 in the <dcs> and normal rules for exceeded memory capacity shall apply. This approach is compliant with GSM 03.38 . • The parameters <ra> and <tora> will only be displayed if <ra> of the AT^SSCONF command is set to 1. • If either a SM or a Status Report is not acknowledged, all AT+CNMI parameter in all channels will be set to zero. MC55_ATC_V04.00 Confidential / Released Page 350 of 475 3/17/06 13.12 AT+CPMS Preferred SMS message storage The write command selects memory storages <mem1>,<mem2>, <mem3> to be used for reading, writing, etc. Syntax Test Command AT+CPMS=? Response(s) +CPMS: (list of supported <mem1>s), (list of supported <mem2>s), (list of supported <mem3>s) OK Read Command AT+CPMS? Response(s) +CPMS: <mem1>, <used1>, <total1>, <mem2>, <used2>, <total2>, <mem3>, <used3>, <total3> OK ERROR +CMS ERROR Write Command AT+CPMS=<mem1>[, <mem2>[, <mem3>]] Response(s) +CPMS: <used1>, <total1>, <used2>, <total2>, <used3>, <total3> OK ERROR ERROR +CMS ERROR Reference(s) PIN GSM 07.05 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <used1>(num) Number of messages currently in <mem1> <used2>(num) Number of messages currently in <mem2> <used3>(num) Number of messages currently in <mem3> <total1>(num) Number of messages storable in <mem1> <total2>(num) Number of messages storable in <mem2> <total3>(num) Number of messages storable in <mem3> MC55_ATC_V04.00 Confidential / Released Page 351 of 475 3/17/06 Notes • The Mobile Equipment storage ''ME'' offers space for 25 short messages, see <mem1>. • ''MT'' is the sum of ''ME'' (= 25 locations) and ''SM'' (capacity varies with SIM card). The indices <index> of the ''MT'' storage are dependent on the order selected with AT^SSMSS • The <mem1>, <mem2> and <mem3> parameter will be stored in non-volatile memory. • The user should be aware that the setting ''MT'' involves ''ME'' and ''SM'', with ''ME'' being filled up first. If the ''ME'' storage is full, MC55 will proceed with the ''SM'' storage. Incoming Class 1 short messages (ME specific) will be preferably stored to ''ME'' and may be transferred to the ''SM'' storage if ''ME'' is used up. Incoming Class 2 messages (SIM specific) will be stored to the SIM card only, no matter whether or not there is free ''ME'' space. As a result, the ^SMGO: 2 indication (see AT^SMGO) may be presented without prior indication of ^SMGO: 1. For more information regarding SIM and ME specific message classes refer to <dcs> and the following specifications: GSM 03.38 and 3GPP TS23038. • When <mem3> is switched over from ''MT'' to ''SM'' all free ''ME'' locations will be filled with dummy short messages. This procedure can take up to 35 seconds, until all the 25 records are written. If switching from ''MT'' to ''SM'' was not finished due to error or user break, the value of <mem3> remains ''MT'', but some of the dummy records remain in the ''ME'' storage. These records have to be deleted manually. When <mem3> equals ''SM'', do not delete the dummy messages in the ''ME''. storage. They will be automatically deleted when you switch back from ''SM'' to ''MT''. Again, this may take up to 35 seconds. If switching from ''SM'' to ''MT'' was not finished due to an error or user break, the value of <mem3> remains ''SM'', but the ''ME'' storage will no longer be filled with dummy records. New incoming short messages may now be written to the ''ME'' storage, if ''SM'' is already full. To avoid this, repeat the AT+CPMS command as soon as possible to switch <mem3> back to ''MT''. As an alternative, you can manually delete the dummy records and issue AT+CPMS=MT,MT,MT. • Multiplexer: In Multiplex mode or when the two physical serial interfaces are connected, the parameter <mem3> will be the same on all instances, but the settings of <mem1> and <mem2> may vary on each channel / interface. As a result, changes on parameter <mem1> and/or <mem2> befor activating the multiplexer or differences values for other instanes can result in not desired behaviours like different outputs for AT+CMGL and so on. • While <mem3> equals ''SM'' and <mem1> equals ''ME'' it is possible that, after deleting short messages from ''ME'', the freed space on ''ME'' is reclaimed for new incoming short messages, when there is no space left on the ''SM'' storage. As it is often the clients concern to have received short messages stored only to the SIM card, inconsistent settings should be generally avoided. This can be achieved simply by using the same parameter for all memory indices. • Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data may not yet be accessible, resulting in a short delay before the requested AT command response is returned. See Section 20.1, Restricted access to SIM data after SIM PIN authentication for further detail. • The indices <index> of the storage are dependent on the order selected with AT^SSMSS. MC55_ATC_V04.00 Confidential / Released Page 352 of 475 3/17/06 13.13 AT+CSCA SMS Service Center Address Write command updates the SMSC address, through which mobile originated SMs are transmitted. In text mode, setting is used by send and write commands. In PDU mode, setting is used by the same commands, but only when the length of the SMSC address coded into the <pdu> parameter equals zero. Syntax Test Command AT+CSCA=? Response(s) OK Read Command AT+CSCA? Response(s) +CSCA: <sca>, <tosca> OK Write Command AT+CSCA=<sca>[, <tosca>] Response(s) OK Reference(s) PIN GSM 07.05 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Notes • In case of using no parameter after AT+CSCA= the content of <sca> will be deleted. • This command writes the service center address to non-volatile memo. • The SMS service center address should be entered as specified by the service provider. MC55_ATC_V04.00 Confidential / Released Page 353 of 475 3/17/06 13.14 AT+CSCB Select Cell Broadcast Message Indication The test command returns the supported modes as a compound value. The write command selects which types of CBMs are to be received by the ME. Syntax Test Command AT+CSCB=? Response(s) +CSCB: (list of supported <mode>s) OK Read Command AT+CSCB? Response(s) +CSCB: <mode>, <mids>, <dcss> OK Write Command AT+CSCB=[<mode>[, <mids>[, <dcss>]]] Response(s) OK Reference(s) PIN GSM 07.05 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <mode>(num) Message mode [0](&F) Accept messages that are defined in <mids> and <dcss> 1 Forbid messages that are defined in <mids> and <dcss> <mids>(str) Cell Broadcast Message ID specification • For <mode>=0: Six different possible combinations of CBM IDs (e.g. "0,1,5,320-478,922,2000-3000"), default is empty string. In certain configurations, e.g. if using SIMs that contain data in Elementary File EF-CBMID (Cell Broadcast Message Identifier for Data download) less than six combinations may be available. To access a SIM's Elementary File data refer to command AT+CRSM. • For <mode>=1: One CBM ID or range of IDs (e.g. "320-478"), default is empty string. <dcss>(str) CBM data coding scheme specification All different possible combinations of CBM data coding schemes (e.g. "0-3,5"). Using default empty string leads to get all CBMs independent of their dcss. A given <dcss> replaces any former value and is used for consecutive requests. MC55_ATC_V04.00 Confidential / Released Page 354 of 475 3/17/06 13.15 AT+CSDH Show SMS text mode parameters The write command sets whether or not detailed header information is shown in text mode result codes. Syntax Test Command AT+CSDH=? Response(s) +CSDH: ((list of supported <show>s) OK Read Command AT+CSDH? Response(s) +CSDH:<show> OK Write Command AT+CSDH=<show> Response(s) +CSDH: <show> OK Reference(s) PIN GSM 07.05 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <show>(num)(&W) [0](&F) Do not show header values defined in commands AT+CSCA and AT+CSMP (<sca>, <tosca>,<fo>,<vp>, <pid> and <dcs>) nor <length>, <toda> or <tooa> in "+CMTI", AT+CMGL, AT+CMGR result codes for SMS-DELIVERs and SMS-SUBMITs in text mode; for SMS-COMMANDs in +CMGR result code, do not show <pid>,<mn>,<da>, <toda>, <length> or <cdata> 1 Show the values in result codes MC55_ATC_V04.00 Confidential / Released Page 355 of 475 3/17/06 13.16 AT+CSMP Set SMS text Mode Parameters The write command selects values for additional parameters needed when the short message is sent to the network or placed in a storage when text format message mode is selected. It is possible to set the validity period starting from the time when the short message is received by the SMSC (<vp> is in range 0... 255) or define the absolute time of the validity period termination (<vp> is a string). The format of <vp> is given by <fo>. If TA supports the enhanced validity period format, see GSM 03.40), it shall be given as a hexadecimal coded string (e.g. <pdu>) with quotes. Syntax Test Command AT+CSMP=? Response(s) OK Read Command AT+CSMP? Response(s) +CSMP:<fo>, <vp>/ <scts>, <pid>, <dcs> OK Write Command AT+CSMP=<fo>[, <vp>/<scts>[, <pid>[, <dcs>]]] Response(s) +CSMP: <index> OK If sending fails ERROR +CMS ERROR Reference(s) PIN GSM 07.05 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <fo>(num) First Octet depending on the command or result code: first octet of GSM 03.40 SMS-DELIVER, SMS-SUBMIT (default 17), SMS-STATUS-REPORT, or SMS-COMMAND (default 2) in integer format 0...17(&F)...255 <vp>(num) Depending on SMS-SUBMIT <fo> setting: GSM 03.40 TP-Validity-Period either in integer format or in timestring format (refer <dt>) 0...167(&F)...255 <dcs>(num) Data Coding Scheme GSM 03.38 SMS Data Coding Scheme, or Cell Broadcast Data Coding Scheme in integer format 0(&F)...247 MC55_ATC_V04.00 Confidential / Released Page 356 of 475 3/17/06 <pid>(num) Protocol Identifier GSM 03.40 TP-Protocol-Identifier in integer format 0(&F)...255 Notes • When storing a SMS DELIVER from the TE to the preferred memory storage in text mode (using the AT+CMGW write command), <vp> field can be used for <scts>. • The command writes the parameters to the non-volatile memory. MC55_ATC_V04.00 Confidential / Released Page 357 of 475 3/17/06 13.17 AT+CSMS Select Message Service Syntax Test Command AT+CSMS=? Response(s) +CSMS: (list of supported<service>s) OK Read Command AT+CSMS? Response(s) +CSMS: <service>, <mt>, <mo>, <bm> OK Write Command AT+CSMS=<service> Response(s) +CSMS: <mt>, <mo>, <bm> OK ERROR +CMS ERROR Reference(s) PIN GSM 07.05 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <service>(num)(&W)(&V) 0(&F) GSM 03.40 and GSM 03.41 (the syntax of SMS AT commands is compatible with GSM 07.05 Phase 2 version 4.7.0; Phase 2+ features which do not require new command syntax may be supported, e.g. correct routing of messages with new Phase 2+ data coding schemes) 1 GSM 03.40 and GSM 03.41 (the syntax of SMS AT commands is compatible with GSM 07.05 Phase 2+ version; the requirement of <service> setting 1 is mentioned under corresponding command descriptions). <mt>(num) Mobile Terminated Messages: 0 Type not supported 1 Type supported <mo>(num) Mobile Originated Messages: 0 Type not supported 1 Type supported MC55_ATC_V04.00 Confidential / Released Page 358 of 475 3/17/06 <bm>(num) Broadcast Type Messages: 0 Type not supported 1 Type supported Notes • If CSMS mode is switched from Phase 2+ to Phase 2 and one or more AT+CNMI Parameter are Phase 2+ specific a '+CMS ERROR: unknown error' will appear. It is recommended to switch the AT+CNMI Parameters to Phase 2 specific values before entering Phase 2. • Phase 2+ (<service>=1) must be set before the following features can be used: - Configuring procedures for indicating received short messages with the AT+CNMI parameters <mt>=2 or <mt>=3 and <ds>=1. - Acknowledging incoming short messages with AT+CNMA. - Receiving Status Reports and acknowledging them with AT+CNMA. MC55_ATC_V04.00 Confidential / Released Page 359 of 475 3/17/06 13.18 AT^SLMS List SMS Memory Storage AT^SLMS indicates the max. capacity of each SMS storage type and the number of locations currently used. Syntax Test Command AT^SLMS=? Response(s) OK Exec Command AT^SLMS Response(s) ^SLMS: ''MT'',<total3>, <used3> ^SLMS: ''SM'',<total1>, <used1> ^SLMS: ''ME'',<total2>, <used2> OK ERROR +CMS ERROR Reference(s) PIN SIEMENS % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <total1>(num) Maximum number of messages storable in the SMS memory of the SIM (physical storage "SM") <total2>(num) Maximum number of messages storable in the SMS memory of the Mobile Equipment (physical storage "ME") <total3>(num) Sum of "SM" and "ME", indicated as "MT". Maximum number of all messages storable in the SIM memory and the Mobile Equipment memory. <used1>(num) Number of messages currently stored in the SMS memory of the SIM (physical storage "SM") <used2>(num) Number of messages currently stored in the SMS memory of the Mobile Equipment (physical storage "ME") <used3>(num) Concatenated logical SMS storages of SIM ("SM") and Mobile Equipment ("ME"). Sum of all messages currently stored, indicated as "MT". Note • Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data may not yet be accessible, resulting in a short delay before the requested AT command response is returned. See Section 20.1, Restricted access to SIM data after SIM PIN authentication for further detail. MC55_ATC_V04.00 Confidential / Released Page 360 of 475 3/17/06 13.19 AT^SMGL List Short Messages from preferred store without setting status to REC READ The write command allows to select a status type and lists, from the message storage <mem1>, all messages that currently have the specified <stat>. The major difference over the standard command AT+CMGL is that the status of the listed messages remains u n c h a n g e d (unread remains unread). The execute command is the same as the write command, but uses the given default of <stat>. Syntax Test Command AT^SMGL=? Response(s) same as AT+CMGL Exec Command AT^SMGL Response(s) ^SMGL: (For default values of <stat>, see "Section 13.1, SMS parameters.) OK Write Command AT^SMGL=<stat> Response(s) same as AT+CMGL Reference(s) PIN SIEMENS % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Notes • The selected <mem1> can contain different types of SMs (e.g. SMS-DELIVERs, SMS-SUBMITs, SMS-STATUS-REPORTs and SMS-COMMANDs), the response may be a mix of the responses of different SM types. TE application can recognize the response format by examining the third response parameter. • Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data may not yet be accessible, resulting in a short delay before the requested AT command response is returned. See Section 20.1, Restricted access to SIM data after SIM PIN authentication for further detail. MC55_ATC_V04.00 Confidential / Released Page 361 of 475 3/17/06 13.20 AT^SMGO Set or query SMS overflow presentation mode or query SMS overflow The write command sets the overflow presentation mode. The read command returns the overflow presentation mode and the SMS overflow status. Syntax Test Command AT^SMGO=? Response(s) ^SMGO: (list of supported<n>s) OK Read Command AT^SMGO? Response(s) ^SMGO: <n>, <mode> OK ERROR +CMS ERROR Write Command AT^SMGO=<n> Response(s) OK ERROR CME ERROR Reference(s) PIN SIEMENS % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Unsolicited Result Code SMS buffer change: ^SMGO: <mode> Status of SMS buffer has changed. Parameter Description <n>(num)(&W)(&V) SMS overflow presentation mode [0](&F) Disable 1 Enable <mode>(num)(&V) SMS overflow status 0 Space available 1 SMS buffer full (The buffer for received short messages is <mem3>. See AT+CPMS.) 2 Buffer full and new message waiting in SC for delivery to phone MC55_ATC_V04.00 Confidential / Released Page 362 of 475 3/17/06 Notes • Incoming short messages with message class 1 (ME specific short messages) or class 2 (SIM specific short messages), see <dcs> in GSM 03.38, will be stored either in ''ME'' or in ''SM'' storage. Therefore the "^SMGO: 2" indication could occur, without issuing the indication "^SMGO: 1" before. The indication "^SMGO: 1" means that both buffers (''ME'' and ''SM'') are full. • For more information regarding SIM and ME specific message classes refer to <dcs> and the following specifications: GSM 03.38 and 3GPP TS 23.038 . MC55_ATC_V04.00 Confidential / Released Page 363 of 475 3/17/06 13.21 AT^SMGR Read short message without setting status to REC READ The AT^SMGR command is a specific Siemens command which has the same syntax as AT+CMGR. The only functional difference is that the status "REC UNREAD" of a short message is not overwritten to "REC READ". Syntax Test Command AT^SMGR=? Response(s) ^SMGR: OK Write Command AT^SMGR=<index> Response(s) see AT+CMGR Reference(s) PIN SIEMENS % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Note • Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data may not yet be accessible, resulting in a short delay before the requested AT command response is returned. See Section 20.1, Restricted access to SIM data after SIM PIN authentication for further detail. MC55_ATC_V04.00 Confidential / Released Page 364 of 475 3/17/06 13.22 AT^SSCONF SMS Command Configuration AT^SSCONF controls details of some SMS releated commands. Please note that AT^SSCONF settings are stored volatile, i.e. after restart or reset the default values will be restored. Syntax Test Command AT^SSCONF=? Response(s) ^SSCONF:list of supported <ra>s OK Read Command AT^SSCONF? Response(s) ^SSCONF:<ra> OK Write Command AT^SSCONF=<ra> Response(s) OK PIN ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <ra>(num) Display recipient address [0](&F) MC55 does not display <ra> and <tora>. These parameters are used with the result codes of AT+CMGL, AT^SMGL, AT+CMGR, AT^SMGR and the URC "+CDS". 1 MC55 displays <ra> and <tora>. MC55_ATC_V04.00 Confidential / Released Page 365 of 475 3/17/06 13.23 AT^SSDA Set SMS Display Availability This command allows to notify the MC55 of its controlling application's capability to immediately display incoming SMS on a display. If the application is able to display incoming short messages, a class 0 message shall be displayed immediately. However, if it does not, class 0 messages shall be treated as if no message class is determined (GSM 03.38[17]). The effect of this command if <da>=1 is to determine the behavior of parameter <mt> of AT+CNMI: If <da>=1 and <mt>=1 incoming class 0 mesages need to be acknowledged with AT+CNMA (see also AT+CNMI and AT+CSMS) If multiplex mode is enabled (AT+CMUX) and <da>=1 with <mt>=1 is set on any logical channel, all other channels have to use <mt>=0. Syntax Test Command AT^SSDA=? Response(s) ^SSDA:list of supported <da>s OK Read Command AT^SSDA? Response(s) ^SSDA:<da> OK Write Command AT^SSDA=<da> Response(s) OK Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <da>(num) Display Availability 0(&F) Application is not able to display incoming short message 1 Application is able to display incoming short message Note • If the ME operates on different instances (MUX channels 1, 2, 3 or ASC0/ASC1) avoid different settings for routing and indicating short messages. 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. MC55_ATC_V04.00 Confidential / Released Page 366 of 475 3/17/06 13.24 AT^SSMSS Set Short Message Storage Sequence The short message storage ''MT'' (see AT+CPMS) is a logical storage. It consists of two physical storages ''ME'' and ''SM''. This command allows to select the sequence of addressing this storage. Syntax Test Command AT^SSMSS=? Response(s) ^SSMSS: (list of supported) <seq>s Read Command AT^SSMSS? Response(s) ^SSMSS: <seq> OK Write Command AT^SSMSS=<seq> Response(s) OK Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <seq>(num) MT sequence 0(&F)(P) ''MT'' storage is ''ME'' then ''SM 1 ''MT'' storage is ''SM'' then ''ME'' Note • Access to the SIM storage is faster. For compatibility with previous software re-leases, the ''MT'' sequence <seq>=0 is the factory default. MC55_ATC_V04.00 Confidential / Released Page 367 of 475 3/17/06 14. SIM related Commands The AT commands described in this chapter are related to the Subscriber Identity Module (SIM) connected to MC55. Note: If using data from the SIM please bear in mind that the content of all Elementary Files is subject to change at any moment! This is true because the network can change the SIM's data in the background via the SIM Application Toolkit (SAT) procedure "Data download to SIM". For a detailed description please refer to GSM 11.14, [22]. To get informed that changing Elementary Files has taken place the TA needs to hook to the SAT Proactive Command "REFRESH". To achieve this, the AT command interface of SAT, i.e. Remote-SAT, needs to be activated. An overview is given at Chapter 15., SIM Application Toolkit (SAT) Commands, additional information is available with the document "Remote-SAT User Guide" [4]. 14.1 AT+CRSM Restricted SIM Access AT+CRSM offers easy access of the Elementary Files on the SIM. Access to the SIM database is restricted to the commands which are listed at <command>. However, additional SIM commands are available via AT^SXSM. All parameters of AT+CRSM are used as specified by GSM 11.11 [21]. MC55 handles internally all required SIM interface locking and file selection routines. As response to the command, the MC55 sends the actual SIM information parameters and response data. Error result code "+CME ERROR" may be returned if the command cannot be passed to the SIM, e.g. if the SIM is not inserted. However, failure in the execution of the command in the SIM is reported in <sw1> and <sw2> parameters. Please beware of possible changes to Elementary Files by the network at any time, refer Chapter 14., SIM related Commands. Syntax Test Command AT+CRSM=? Response(s) OK Write Command AT+CRSM=<command>[, <fileID>[, <P1>, <P2>, <P3>[, <data>]]] Response(s) +CRSM: <sw1>,<sw2>[,<response>] OK ERROR +CME ERROR: <err> Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <command>(num) SIM command number. 176 MC55_ATC_V04.00 Confidential / Released READ BINARY Page 368 of 475 3/17/06 178 READ RECORD 192 GET RESPONSE 214 UPDATE BINARY 220 UPDATE RECORD 242 STATUS <fileID>(num) Identifier for an elementary data file on SIM, if used by <command>. <P1>(num) Parameter to be passed on by the MC55 to the SIM. 0...255 <P2>(num) Parameter to be passed on by the MC55 to the SIM. 0...255 <P3>(num) Parameter to be passed on by the MC55 to the SIM. 0...255 <data>(str) Information which shall be written to the SIM (hexadecimal character format). <sw1>(num) Status information from the SIM about the execution of the actual command. It is returned in both cases, on successful or failed execution of the command. 0...255 <sw2>(num) Status information from the SIM about the execution of the actual command. It is returned in both cases, on successful or failed execution of the command. 0...255 <response>(str) Response data in case of a successful completion of the previously issued command. "STATUS" and "GET RESPONSE" commands return data, which gives information about the currently selected elementary data field. This information includes the type of file and its size. After "READ BINARY" or "READ RECORD" commands the requested data will be returned. <response> is empty after "UPDATE BINARY" or "UPDATE RECORD" commands. MC55_ATC_V04.00 Confidential / Released Page 369 of 475 3/17/06 14.2 AT^SXSM Extended SIM Access AT^SXSM extends AT+CRSM with additional SIM commands. All parameters of AT^SXSM are used as specified by GSM 11.11 [21]. MC55 handles internally all required SIM interface locking and file selection routines. MC55 may return error result code "+CME ERROR" if the command cannot be passed to the SIM, e.g. if no SIM is inserted. However, errors related to SIM action are reported in <sw1> and <sw2> parameters as defined in GSM 11.11 [21]. Syntax Test Command AT^SXSM=? Response(s) OK Write Command AT^SXSM=<command>[, <fileID>[, <P1>, <P2>, <P3>[, <data>]]] Response(s) ^SXSM: <sw1>, <sw2>[,<response>] OK ERROR +CME ERROR: <err> PIN % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <command>(num) 136 RUN GSM ALGORITHM Start the authentication mechanism and cipher key generation on the SIM. It runs the algorithms A3 and A8 using a 16 byte random number and the subscriber authentication key Ki, which is stored in the SIM. <fileID>(num) Identifier for an elementary data file on SIM, if used by <command>. <P1>(num) Parameter to be passed on by the MC55 to the SIM. <P2>(num) Parameter to be passed on by the MC55 to the SIM. <P3>(num) Parameter to be passed on by the MC55 to the SIM. <data>(str) If <command>=136 (RUN GSM ALGORITHM): 16 byte random number. MC55_ATC_V04.00 Confidential / Released Page 370 of 475 3/17/06 <sw1>(num) Status information from the SIM about the execution of the actual command. It is returned in both cases, on successful or failed execution of the command. 0...255 <sw2>(num) Status information from the SIM about the execution of the actual command. It is returned in both cases, on successful or failed execution of the command. 0...255 <response>(str) Response in case of a successful completion of the previously issued SIM command. If <command>=136 (RUN GSM ALGORITHM): MC55 returns SRES and cipher key Kc as calculated by the SIM. Byte(s) Description Length 1-4 SRES - Signed RESponse 4 5 - 12 Kc - Cipher Key 8 Example Use <command>=136 (RUN GSM ALGORITHM) to obtain SRES and cipher key Kc values as calculated by the SIM. at^sxsm=136,,0,0,16,"0011223 3445566778899AABBCCDDEEFF" ^SXSM: 144,0,00112233445566778899AA BB OK MC55_ATC_V04.00 Confidential / Released Start SIM command "RUN GSM ALGORITHM" with 16 byte random number. SRES (bytes 1-4) and Cypher Key Kc (bytes 5-12) values as returned by the SIM. Page 371 of 475 3/17/06 14.3 AT^SCKS Query SIM and Chip Card Holder Status This command controls the SIM connection presentation mode and queries the connection status of the SIM and the card holder tray of the MC55. Syntax Test Command AT^SCKS=? Response(s) ^SCKS:(list of supported <mode>s) OK Read Command AT^SCKS? Response(s) ^SCKS: <mode>, <SimStatus> OK ERROR +CME ERROR: <err> Write Command AT^SCKS=<mode> Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Unsolicited Result Code ^SCKS: <SimStatus> During startup, and if the MC55's SIM connection status has changed an unsolicited result code (URC) is issued. Command Description The read command returns the URC presentation mode and the status of the SIM card connection. The write command enables or disables the presentation of URCs to report whether or not the SIM card is connected. If the ME is powered down or reset (AT+CFUN or AT^SMSO) the current presentation mode setting <mode> will not be retained. Therefore the setting <mode>=1 needs to be restored after power on the MC55 or may be saved in the user profile (AT&W). Parameter Description <mode>(num)(&W)(&V) 0(&F) Suppress unsolicited result codes 1 Output unsolicited result codes <SimStatus>(num)(&V) 0 Card holder tray removed or SIM connection error 1 SIM inserted(refer to note) MC55_ATC_V04.00 Confidential / Released Page 372 of 475 3/17/06 Note • <SimStatus> reflects the status of the SIM and the card holder tray. Therefore if an empty SIM card tray is inserted, two URCs will be presented, indicating the status 1 followed by 0, i.e. a SIM is inserted into the card holder tray but no SIM connection could be established. Example AT^SCKS=1 OK Activates the presentation of unsolicited result codes Now, after inserting an empty card tray the following URCs appear: ^SCKS: 1 ^SCKS: 0 MC55_ATC_V04.00 Confidential / Released Tray connected No SIM card found Page 373 of 475 3/17/06 14.4 AT^SCID Display SIM card identification number Syntax Test Command AT^SCID=? Response(s) OK Exec Command AT^SCID Response(s) ^SCID: <cid> OK ERROR +CME ERROR: <err> Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description TA returns the card identification number in SIM (SIM file EFICCID, see GSM 11.11 Chap.10.1.1) as string type. Parameter Description <cid>(str) card identification number of SIM card MC55_ATC_V04.00 Confidential / Released Page 374 of 475 3/17/06 14.5 AT+CXXCID Display card ID Syntax Test Command AT+CXXCID=? Response(s) OK Exec Command AT+CXXCID Response(s) +CXXCID: <cid> OK ERROR +CME ERROR: <err> Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description TA returns the card identification number in SIM (SIM file EF ICCID, see GSM 11.11 Chap.10.1.1) as string type. Note • See also: AT^SCID. MC55_ATC_V04.00 Confidential / Released Page 375 of 475 3/17/06 15. SIM Application Toolkit (SAT) Commands This chapter offers a brief reference of commands and responses related to the MC55's SIM Application Toolkit (SAT) implementation. Detailed information is available with the document "Remote-SAT User Guide" [4]. Please contact the Wireless Modules Application Engineering Department at Siemens AG for details. ETSI specification GSM 11.14 [22] defines SAT in detail. SAT allows for the execution of applications provided by a Subsciber Identity Module (SIM). Usually SIM cards are used for storing GSM network provider and user specific data, e.g. phonebook entries and Short Messages (SMS). However, a SIM card may also hold a SIM Application. Since the MC55 has SAT functionality it is able to execute the commands issued by applications implemented on a network provider specific SIM card. Two groups of commands are used between the ME and the SIM Application: • Proactive Commands are issued to the MC55's SAT from the SIM Application, such as "DISPLAY TEXT". • Envelope Commands are responded to the SIM Application from the MC55, such as "MENU SELECTION". 15.1 AT^SSTA SAT Interface Activation Syntax Test Command AT^SSTA=? Response(s) ^SSTA:(list of supported <state>s), (list of supported <Alphabet>s) OK Read Command AT^SSTA? Response(s) ^SSTA: <state>, <Alphabet>, <allowedInstance>, <SatProfile> OK Write Command AT^SSTA=<mode>[, <Alphabet>] Response(s) OK Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description The read command can be used to request the current operating status and the used alphabet of the RemoteSAT interface. The write command is used to activate the AT command interface of the SIM Application Toolkit in the MC55 and needs to be issued after every power on. However, removing and inserting the SIM does not affect the activation status. SAT commands which are not using the AT interface (non MMI related SAT commands , e.g. PROVIDE LOCAL INFORMATION) could be executed without activating Remote-SAT. MC55_ATC_V04.00 Confidential / Released Page 376 of 475 3/17/06 Parameter Description <state>(num) MC55 Remote-SAT interface states 0 RESET 1 OFF 2 IDLE 3 PAC 4 WAIT <Alphabet>(num) 0 GSM character set Input of a character requests one byte, e.g. "Y". 1 UCS2 To display the 16 bit value of characters represented in UCS2 alphabet a 4 byte string is required, e.g. "0059" is coding the character "Y". For details please refer to ISO/IEC 10646. <allowedInstance>(num) 0 SAT is already used on another instance (logical channel in case of the multiplex protocol). Only test and read commands can be used. 1 SAT may be started on this instance via the write version of this command. <SatProfile>(str) SAT profile according to GSM 11.14 [22]. The profile tells the SIM Application which features (e.g. proactive commands) are supported by the SIM Application Toolkit implementation of the MC55. <mode>(num) 1 Activate Remote-SAT Note • To limit the time Remote-SAT is kept in states PAC or WAIT any ongoing (but unanswered) Proactive Command is automatically aborted after 10 minutes with Terminal Response "ME currently unable to process command" or "No response from user" if applicable. An URC "Terminate Proactive Command" will be send to the external application in this case, too. MC55_ATC_V04.00 Confidential / Released Page 377 of 475 3/17/06 15.2 ^SSTN SAT Notification Unsolicited Result Codes URC 1 Proactive Command notification ^SSTN: <cmdType> Every time the SIM Application issues a Proactive Command, via the ME, the TA will receive a notification. This indicates the type of Proactive Command issued. AT^SSTGI must then be used by the TA to request the parameters of the Proactive Command from the ME. Upon receiving the ^SSTGI response from the ME, the TA must send AT^SSTR to confirm the execution of the Proactive Command and provide any required user response, e.g. a selected menu item. URC 2 Terminate Proactive Command notification ^SSTN: <cmdTerminateValue> When the SIM application has issued a Proactive Command to the ME, it is possible that this command will be terminated later. URC "^SSTN" is sent with a different Proactive Command type number (added terminate offset 100) to indicate the termination of the specified command. The state changes to idle. Therefore the TA should avoid sending any further commands related to the terminated Proactive Command, e.g. AT^SSTGI or AT^SSTR. URC 3 Notification that SIM Application has returned to main menu ^SSTN: 254 Notification to the TA when the SIM Application has finished a command cycle and again enters its main menue, which was transferred with an URC "^SSTN: 37" (SET UP MENU) at start up. This URC should be used to open this menue on the sreen. The TA does not need to respond directly, i.e. AT^SSTR is not required. URC 4 SIM reset notification ^SSTN: 255 Notification to the TA if a Proactive Command "REFRESH - SIM Reset" has been issued by the SIM Application, please refer to AT^SSTGI. This URC should be used to set the TAs application to its initial state since the SIM Application will start from the beginning, too. The TA does not need to respond directly, i.e. related AT^SSTGI and AT^SSTR are neither required nor allowed. Since the ME is still busy on SIM access the ME may respond with "+CME ERROR: SIM blocked" or "+CME ERROR: SIM busy" on following PIN required AT Commands for a while. Then TA shall retry until the ME responds with "OK". The time needed for this process depends on the SIM and may take more than 10 seconds. Parameter Description <cmdType>(num) Proactive Command number <cmdTerminateValue>(num) Defined as <cmdType> + terminate offset. The terminate offset equals 100. MC55_ATC_V04.00 Confidential / Released Page 378 of 475 3/17/06 15.3 AT^SSTGI SAT Get Information Regularly this command is used upon receipt of an URC "^SSTN" to request the parameters of the Proactive Command. Then the TA is expected to acknowledge the AT^SSTGI response with AT^SSTR to confirm that the Proactive Command has been executed. AT^SSTR will also provide any user information, e.g. a selected menu item. The Proactive Command type value specifies to which "^SSTN" the command is related. Syntax Test Command AT^SSTGI=? Response(s) ^SSTGI:(list of supported <state>s), (list of supported <cmdType>s) OK Read Command AT^SSTGI? Response(s) ^SSTGI: <state>, <cmdType> OK Write Command AT^SSTGI=<cmdType> Response(s) OK ERROR +CME ERROR Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <state>(num) MC55 Remote-SAT interface states 0 RESET 1 OFF 2 IDLE 3 PAC 4 WAIT <cmdType>(num) Related Proactive Command MC55_ATC_V04.00 Confidential / Released Page 379 of 475 3/17/06 15.4 AT^SSTR SAT Response The TA is expected to acknowledge the AT^SSTGI response with AT^SSTR to confirm that the Proactive Command has been executed. AT^SSTR will also provide any user information, e.g. a selected menu item. Syntax Test Command AT^SSTR=? Response(s) ^SSTR:(list of supported <state>s), (list of supported <cmdType>s) OK Read Command AT^SSTR? Response(s) ^SSTR: <state>, <cmdType> OK Write Command AT^SSTR=<cmdType>, <status>[, <inputNumber>][, <inputString>] Response(s) OK Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <state>(num) MC55 Remote-SAT interface states 0 RESET 1 OFF 2 IDLE 3 PAC 4 WAIT <cmdType>(num) Number related to Proactive Command or event type according to GSM 11.14 [22]. <status>(num) Command status return regarding the type of action that has taken place, e.g. action performed by the user. Values are in accordance with GSM 11.14 [22]. <inputNumber>(num) Response number entered by user <inputString>(str) Response string entered by user MC55_ATC_V04.00 Confidential / Released Page 380 of 475 3/17/06 16. Phonebook Commands The AT commands described in this chapter allow the external application to access the phonebooks located in the MC55's memory or on the attached Subscriber Identity Module (SIM). 16.1 Sort Order for Phonebooks Due to the support of UCS2 for the <text> part of phonebook entries, the sort order for phonebook records follows the algorithm published as Unicode Technical Standard #10, "Unicode Collation Algorithm". A memory-optimized version of the proposed collation tables "[AllKeys]" from Unicode Technical Standard #10 is used in order to determine collation weights for Code points between 0000 and 06FF, and composed keys are used for Code points from ranges 0700 to 33FF, A000 to D7FF and E000 to FFFD. Code Points not referenced in these tables will be assigned a default collation weight with their unicode value as level 1 weight. Decomposition is not supported. Phonebook entries whose names contain only characters from the GSM07.07 default alphabet are converted internally into their UCS2 equivalents in order to achieve consistent sorting results. For the user, this means that: • Punctuation marks and other non-alphabetical characters from the common latin-based character sets, and from the standard GSM character set, will be sorted before any alphabetical characters. The ordering in which these marks appear as compared to other non-alphabetical characters from the same group is determined by their collation weights and does not reflect their code values in the UCS2 or GSM alphabet tables above. Please refer to www.unicode.org for detail. • Alphabetical characters from the common latin-based character sets, and from the standard GSM character set, will be sorted according to their underlying base characters, plus the collation weights of their accent signs. • Only collation levels 1 and 2 are regarded, so sorting is not case-sensitive. Example: the european letters "Å" (GSM 0EH, UCS2 00C5h), "æ" (GSM 1DH, UCS2 00E6h), "ç" (GSM09h, UCS2 00E7h), "a" (GSM 61H, UCS2 0061h ) and "b" (GSM 62H, UCS2 0062h) will be sorted in order "a", "Å", "æ" "b","ç" although their numerical values in GSM and UCS2 suggest a different ordering. Reference(s) Unicode Technical Standard #10,"Unicode Collation Algorithm" MC55_ATC_V04.00 Confidential / Released Page 381 of 475 3/17/06 16.2 AT+CPBR Read from Phonebook AT+CPBR serves to read one or more entries from the phonebook selected with AT command AT+CPBS. The AT+CPBR test command returns the location range supported by the current phonebook storage, the maximum length of <number> field and the maximum length of <text> field. Note: Length information may not be available while SIM storage is selected. If storage does not offer format information, the format list contains empty parenthesizes. The AT+CPBR write command determines the phonebook entry to be displayed with <location1> or a location range from <location1> to <location2>. Hence, if no <location2> is given only the entry at <location1> will be displayed. If no entries are found at the selected location "OK" will be returned. Syntax Test Command AT+CPBR=? Response(s) +CPBR: (1-<maxloc>), <nlength>, <tlength> OK +CME ERROR Write Command AT+CPBR=<location1>[, <location2>] Response(s) [+CPBR: <location1>, <number>, <type>, <text>] [+CPBR: <location2>, <number>, <type>, <text>] OK +CME ERROR Reference(s) GSM 07.07, GSM 11.11 PIN % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <location1>(num) The first (lowest) location number within phonebook memory where to start reading. The maximum range supported by the current phonebook is given in the test command response. If <location1> exceeds the upper bound <maxloc> (as indicated by the test command), command will respond with "+CME ERROR: invalid index". <location2>(num) The last (highest) location number within phonebook memory where to stop reading. The maximum range supported by the current phonebook is given in the test command response. If both <location1> and <location2> are in the range indicated by the test command parameter <maxloc>, the list of entries will be output and terminated with "OK". If <location2> exceeds the range indicated by the test command parameter <maxloc>, the list of entries will be output but terminated with "+CME ERROR: invalid index". <number>(str) Phone number in format specified by <type>, it may be an empty string. MC55_ATC_V04.00 Confidential / Released Page 382 of 475 3/17/06 <type>(num) Type of address octet, which defines the used type of number (ton) and the numbering plan identification (npi). Please consider that for types other than 129 or 145 dialing from phonebook with ATD><mem><n> is, depending on the network, not always possible (refer to GSM 04.08 subclause 10.5.4.7 for details). See also <type> of AT+CPBW. Possible values are: 145 Dialing string <number> includes international access code character '+' 161 National number. Network support of this type is optional. 209 Dialing string <number> has been saved as ASCII string and includes nondigit characters other than "*", "#" or "+". Note that phonebook entries saved with this type cannot be dialed. 255 Dialing string <number> is a command to control a Supplementary Service, i.e. "*", "#" codes are contained. Network support of this type is optional. 129 Otherwise <text>(str)(+CSCS) Text assigned to a phone number. The maximum length for this parameter is given with test command response parameter <tlength>. If using an ASCII terminal characters which are coded differently in ASCII and GSM have to be entered via escape sequences as described in Section 1.5, Supported character sets. <maxloc>(num) Maximum location number for the currently selected storage. For phonebooks located on the SIM this value depends on the SIM card type. <nlength>(num) Maximum length of phone number for "normal" locations. Depending on the storage a limited number of locations with extended memory is available per phonebook. These locations allow storing numbers with twice the standard length, which is 2*<nlength> digits for normal numbers, but only <nlength> digits for numbers saved with <type>=209. <tlength>(num) Maximum length of <text> assigned to the telephone number. The value indicated by the test command is given in octets. If <text> is given as GSM characters each character corresponds to one octet. If the <text> string is given in UCS2, the maximum number of characters depends on the coding scheme used for the alpha field of the SIM according to GSM 11.11, Annex B [21]. In the worst case the number of UCS2 characters is at least one less than half the number of GSM characters. Note • Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data may not yet be accessible, resulting in a short delay before the requested AT command response is returned. See Section 20.1, Restricted access to SIM data after SIM PIN authentication for further detail. MC55_ATC_V04.00 Confidential / Released Page 383 of 475 3/17/06 Example AT+CPBR=? +CPBR:(1-100),20,17 AT+CPBR =1,3 +CPBR:1,"+999999",145,"Charlie" +CPBR:2,"+777777",145,"Bill" +CPBR:3,"+888888",145,"Arthur" MC55_ATC_V04.00 Confidential / Released First run the AT+CPBR test command to find out the maximum range of entries stored in the active phonebook. MC55 returns the supported values, where 100 is the supported range of location numbers, 20 is the length of the phone number and 17 is the maximum length of the associated text. Then use the AT+CPBR write command to display the phonebook entries sorted by location numbers. Page 384 of 475 3/17/06 16.3 AT+CPBS Select phonebook memory storage AT+CPBS selects the active phonebook storage, i.e. the phonebook storage that all subsequent phonebook commands will be operating on. The read command returns the currently selected <storage>, the number of <used> entries and the <total> number of entries available for this storage. The test command returns all supported <storage>s as compound value. Syntax Test Command AT+CPBS=? Response(s) +CPBS: (list of supported <storage>s) OK +CME ERROR Read Command AT+CPBS? Response(s) +CPBS: <storage>, <used>, <total> OK +CME ERROR Write Command AT+CPBS=<storage> Response(s) OK +CME ERROR: Reference(s) PIN GSM07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <storage>(str) "FD" Fixed dialing phonebook Capacity: depending on SIM card Location: SIM "SM"(&F) SIM phonebook Capacity: depending on SIM card Location: SIM "ON" MSISDN list Capacity: depending on SIM card Location: SIM "ME" Mobile Equipment Phonebook Capacity: max. 250 entries Location: ME "LD" Last number dialed phonebook. Stores all voice call numbers dialed with ATD, but no data call numbers. Capacity: max. 10 entries Location: depending on SIM this phonebook may reside partly or completely in ME AT+CPBW command is not applicable to this storage. The LD list can be deleted with AT^SDLD or with AT^SPBD. MC55_ATC_V04.00 Confidential / Released Page 385 of 475 3/17/06 "MC" Missed (unanswered received) calls list Capacity: max. 10 entries Location: ME AT+CPBW command is not applicable to this storage. The MC list can be deleted with AT^SPBD. "RC" Received calls list Capacity: max. 10 entries Location: ME AT+CPBW command is not applicable to this storage. The RC list can be deleted with AT^SPBD. <used>(num) Value indicating the number of used locations in selected memory storage. <total>(num) Value indicating the maximum number of locations allowed in the selected memory storage. Notes • Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data may not yet be accessible, resulting in a short delay before the requested AT command response is returned. See Section 20.1, Restricted access to SIM data after SIM PIN authentication for further detail. • If the SIM card is changed, all records of the "MC", "RC" and "LD" phonebooks stored on the ME will be deleted automatically. If the same SIM is removed and reinserted, no automatic deletion is performed. Calls made after last switch-on will be lost from "MC", "RC" and "LD" phonebook, if the SIM is removed and reinserted during normal operation. MC55_ATC_V04.00 Confidential / Released Page 386 of 475 3/17/06 16.4 AT+CPBW Write into Phonebook The AT+CPBW write command can be used to create, edit and delete a phonebook entry at a <location> of the active storage selected with AT+CPBS. If <storage>="FD" (SIM fixed dialing numbers) is selected, PIN2 authentication has to be performed prior to any write access. The AT+CPBW test command returns the location range supported by the current storage, the maximum length of the <number> field, the range of supported <type> values and the maximum length of the <text> field. Note: The length may not be available while SIM storage is selected. If storage does not offer format information, the format list contains empty parenthesizes. Syntax Test Command AT+CPBW=? Response(s) +CPBW: (1-<maxloc>), <nlength>, (list of supported <type>s), <tlength> OK ERROR +CME ERROR Write Command AT+CPBW=[<location>][, <number>[[, <type>][, <text>]]] Response(s) OK ERROR +CME ERROR Reference(s) GSM 07.07, GSM 04.08 PIN % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <location>(num) Location number within phonebook memory. The maximum range supported by each storage type is indicated in the test command response. If <location> is not given, the first free entry will be used. If <location> is given as the only parameter, the phonebook entry specified by <location> is deleted. <number>(str) Phone number in format specified by <type>. Parameter must be present, although it may be an empty string. Alphabetic characters are not permitted. <number> may contain dialstring modifiers "*", "#" or "+". If other printable non-alphabetic characters are used the entry needs to be saved with <type>=209. Otherwise, if <type>=209 is not used any non-digit characters other than "*", "#" or "+" will be removed from the string and only accepted modifiers from the GSM alphabet will be saved. A <number> saved with <type>=209 requires double memory. In order to fit into a standard location, the number needs to be reduced to a maximum length of <nlength>/2, including all digits and dial string modifiers. Extended locations may be used as stated below for <nlength>. MC55_ATC_V04.00 Confidential / Released Page 387 of 475 3/17/06 <type>(num) Type of address octet, which defines the used type of number (ton) and the numbering plan identification (npi). Please consider that for types other than 129 or 145 dialing from phonebook with ATD><mem><n> is, depending on the network, not always possible (refer GSM 04.08 subclause 10.5.4.7 for details). If <type> is not specified the unknown <type>=129 is used. If <number> contains a leading "+" <type>=145 (international) is used. Supported values are: 145 Dialing string <number> includes international access code character "+" 161 National number. The network support for this type is optional. 209 Dialing string <number> will be saved as ASCII string. This is the default value, if <type> is not specified explicitly and characters other than "*", "#" or "+" are included in <number>. Note that phonebook entries saved with this type cannot be dialed. 255 Dialing string <number> is a command to control a Supplementary Service, i.e. "*", "#" codes are contained. Network support of this type is optional. 129 Unknown number. If <type> is unknown and the <number> contains a leading "+", then this sign is removed. <text>(str)(+CSCS) Text assigned to the phone number. The maximum length of this parameter is given in the test command response <tlength>. When using an ASCII terminal, characters which are coded differently in ASCII and GSM have to be entered via escape sequences as described in Section 1.5, Supported character sets. <maxloc>(num) Maximum number of locations supported by the currently selected storage. For phonebooks located on SIM, this value varies depending on the SIM card. See AT+CPBS for typical values. <nlength>(num) Maximum length of phone number for "normal" locations. Depending on the storage, a limited number of locations with extended memory is available per phonebook. These locations allow storing numbers with twice the standard length, which is 2*<nlength> digits for normal numbers, but only <nlength> digits for numbers saved with parameter <type>= 209. If all extended locations of the selected phonebook are used up, then any attempt to write a number which requires extended memory will be denied with CME ERROR 260: INVALID DIAL STRING. <tlength>(num) Maximum length of <text> assigned to the telephone number. The value indicated by the test command is given in octets. If the <text> string is given in GSM characters, each character corresponds to one octet. If the <text> string is given in UCS2, the maximum number of characters depends on the coding scheme used for the alpha field of the SIM. In the worst case the number of UCS2 characters is at least one less than half the number of GSM characters. For a detailed description please refer to GSM 11.11, Annex B [21]. Note • Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data may not yet be accessible, resulting in a short delay before the requested AT command response is returned. See Section 20.1, Restricted access to SIM data after SIM PIN authentication for further detail. MC55_ATC_V04.00 Confidential / Released Page 388 of 475 3/17/06 Examples EXAMPLE 1 Make a new phonebook entry at the first free location AT+CPBW=,"+431234567",145,"international" EXAMPLE 2 Delete entry at location 1 AT+CPBW=1 EXAMPLE 3 The following examples are provided to illustrate the effect of writing phonebook entries with different types of dial string modifiers in <number> AT+CPBW=5,"12345678",,"Arthur" AT+CPBW=6,"432!+-765()&54*654#",,"John" AT+CPBW=7,"432!+-765()&54*654#",129,"Eve" AT+CPBW=8,"432!+-765()&54*654#",145,"Tom" AT+CPBW=9,"432!+-765()&54*654#",209,"Richard" EXAMPLE 4 Read phonebook entries from locations 5 - 9 via AT+CPBR +CPBR:5,"12345678",129,"Arthur" +CPBR:6,"432!+-765()&54*654#",209,"John" +CPBR:7,"432+76554*654#",129,"Eve" +CPBR:8,"+432+76554*654#",145,"Tom" +CPBR:9,"432!+-765()&54*654#",209,"Richard" MC55_ATC_V04.00 Confidential / Released Page 389 of 475 3/17/06 16.5 AT^SPBC Find first matching entry in sorted phonebook The AT^SPBC write command searches the current phonebook for the index number of the first (lowest) entry that matches the character specified with <schar>. The AT^SPBC test command returns the list of phonebooks which can be searched through with AT^SPBC. CAUTION: Please note that AT^SPBC is assigned the same index as AT^SPBG or AT^SPBS which is not identical with the physical location numbers used in the various phonebooks. Therefore, do not use the index numbers retrieved with AT^SPBC to dial out or modify phonebook entries. Syntax Test Command AT^SPBC=? Response(s) ^SPBC: "FD","SM","ME" OK ERROR +CME ERROR Write Command AT^SPBC=<schar> Response(s) ^spbc: <index> OK ERROR +CME ERROR Reference(s) PIN SIEMENS % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <schar>(str) First character of the entry to be searched in the sorted list of phonebook entries. <index>(num) In the active phonebook, the first (lowest) index number of an entry beginning with <schar>. As stated above, the retrieved index number shall not be used to dial out or edit phonebook entries. If no matching phonebook entry is found, <index>=0 will be returned. Note • Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data may not yet be accessible, resulting in a short delay before the requested AT command response is returned. See Section 20.1, Restricted access to SIM data after SIM PIN authentication for further detail. MC55_ATC_V04.00 Confidential / Released Page 390 of 475 3/17/06 16.6 AT^SPBD Purge phonebook memory storage AT^SPBD can be used to purge the selected phonebook <storage> manually, i.e. all entries stored in the selected phonebook storage will be deleted. CAUTION! The operation cannot be stopped nor reversed! The AT^SPBD test command returns the list of phonebooks which can be deleted with AT^SPBD. An automatic purge of the phonebooks is performed when the SIM card is removed and replaced with a different SIM card. This affects the ME based part of the "LD" storage, and storages "MC" and "RC". Storage "ME" is not affected. Syntax Test Command AT^SPBD=? Response(s) ^SPBD: list of supported <storage>s OK +CME ERROR Write Command AT^SPBD=<storage> Response(s) OK +CME ERROR Reference(s) PIN SIEMENS % ASC0 ASC1 % MUX1 MUX2 % % % MUX3 Charge % ! ! Last ! Parameter Description <storage>(str) If test command: List of phonebooks which can be deleted by AT^SPBD. If write command: Phonebook to be deleted. For a detailed description of storages see AT+CPBS. "LD" Last number dialed phonebook "MC" Missed (unanswered received) calls list "RC" Received calls list Note • Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data may not yet be accessible, resulting in a short delay before the requested AT command response is returned. See Section 20.1, Restricted access to SIM data after SIM PIN authentication for further detail. MC55_ATC_V04.00 Confidential / Released Page 391 of 475 3/17/06 16.7 AT^SPBG Display phonebook entries in alphabetical order AT^SPBG sorts the entries of the current phonebook in alphabetical order by name (the first six characters matter). The sort order is described in Section 16.1, Sort Order for Phonebooks. There are two ways to use AT^SPBG: • If the optional parameter <RealLocReq> equals 0 or is omitted the sorted entries will be sequentially numbered. As these numbers are not identical with the location numbers stored in the various phonebooks AT^SPBG can be used for reading only. For example, it helps you find entries starting with matching characters. Do not use the serial numbers to dial out or modify entries. • If parameter <RealLocReq>=1 is given by the write command, the response parameter <location> additionally appended to each entry indicates the actual location number. This number can be used for editing with AT+CPBW or dialing with ATD><mem><n>. The first index number of each entry is only the serial number of the sorted list. Before using the AT^SPBG write command it is recommended to query the number of records currently stored in the active phonebook (refer to test command parameter <used>). The test command also includes the parameters <nlength> and <tlength>. Note that if SIM storage is selected the length may not be available. If storage does not offer format information, the format list should be empty parenthesises. Syntax Test Command AT^SPBG=? Response(s) ^SPBG: (1-<used>), <nlength>, <tlength> OK ERROR +CME ERROR Write Command AT^SPBG=<index1>[, <index2>][, <RealLocReq>] Response(s) [^SPBG: <index1>, <number>, <type>, <text>[, <location>]] [^SPBG: <index2>, <number>, <type>, <text>[, <location>]] OK ERROR +CME ERROR Reference(s) PIN SIEMENS % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <index1>(num) First index number in the sorted list where to start reading. The supported range is given in the test command response. If <index 1> exceeds the upper bound <used>, "+CME ERROR: "invalid index" will be returned. <index2>(num) Last index number in the sorted list where to stop reading. The supported range is given in the test command response. If <index2> is not given via write command, only the entry located at <index1> will be displayed. If both <index1> and <index2> are in the range indicated by the test command parameter <used>, the list of entries will be output and terminated with OK. If <index2> exceeds the range indicated by the test command parameter <used>, the list of entries will be output but terminated with a "+CME ERROR: "invalid index". MC55_ATC_V04.00 Confidential / Released Page 392 of 475 3/17/06 <RealLocReq>(num) Is a display of the "real" <location> of the entry required? [0] Do not show an entry's "real" location number. Parameter <location> will not be displayed. 1 Show the "real" location number as parameter <location> at the end of each entry. <number>(str) String type phone number in format specified by <type>. The number parameter may be an empty string. <type>(num) Type of address octet, which defines the used type of number (ton) and the numbering plan identification (npi). Please consider that for types other than 129 or 145 dialing from phonebook with ATD><mem><n> is, depending on the network, not always possible (refer to GSM 04.08 subclause 10.5.4.7 for details). See also <type> of AT+CPBW. Possible values are: 145 Dialing string <number> includes international access code character '+' 161 National number. Network support of this type is optional. 209 Dialing string <number> has been saved as ASCII string and includes nondigit characters other than "*", "#" or "+". Note that phonebook entries saved with this type cannot be dialed. 255 Dialing string <number> is a command to control a Supplementary Service, i.e. "*", "#" codes are contained. Network support of this type is optional. 129 Otherwise <text>(str)(+CSCS) Text assigned to the phone number. The maximum length for this parameter is given in test command response <tlength>. <used>(num) Value indicating the number of used locations in selected memory storage. <location>(num) The location within phonebook memory at which the corresponding entry is located. This location may be used for other commands (e.g. AT+CPBR or ATD><mem><n>) <nlength>(num) Maximum length of phone number for "normal" locations. Depending on the storage, a limited number of locations with extended memory is available per phonebook. Please refer to AT command AT+CPBW for detail. <tlength>(num) Maximum length of <text> assigned to the telephone number. The value indicated by the test command is given in octets. If the <text> string is given in GSM characters, each character corresponds to one octet. If the <text> string is given in UCS2, the maximum number of characters depends on the coding scheme used for the alpha field of the SIM according to GSM 11.11, Annex B [21]. In the worst case the number of UCS2 characters is at least one less than half the number of GSM characters. MC55_ATC_V04.00 Confidential / Released Page 393 of 475 3/17/06 Notes • The command can be used for the phonebooks "SM", "FD", "ME" (cf. AT+CPBS). • Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data may not yet be accessible, resulting in a short delay before the requested AT command response is returned. See Section 20.1, Restricted access to SIM data after SIM PIN authentication for further detail. Examples EXAMPLE 1 Using AT^SPBG without <RealLocReq>: First run the AT^SPBG test command to find out the range of entries stored in the current phonebook. TA returns the range, where 33 is the number of entries stored in the current phonebook. Now, enter the write command. To obtain best results it is recommended to query the full range of entries. TA returns phonebook entries in alphabetical order. AT^SPBG=? ^SPBG: (1-33),20,17 AT^SPBG=1,33 ^SPBG:1,"+999999",145,"Arthur" ^SPBG:2,"+777777",145,"Bill" ^SPBG:3,"+888888",145,"Charlie" ...................... The numbers at the beginning of each line are not the memory locations in the phonebook, but only serial numbers assigned to the entries' positions in the alphabetical list. EXAMPLE 2 Using AT^SPBG with <RealLocReq>: AT^SPBG=? ^SPBG: (1-33),20,17 AT^SPBG=1,33,1 ^SPBG:1,"+999999",145,"Arthur",27 ^SPBG:2,"+777777",145,"Bill",6 ^SPBG:3,"+888888",145,"Charlie",15 ...................... First run the AT^SPBG test command to find out the range of entries stored in the current phonebook. TA returns the range, where 33 is the number of entries stored in the current phonebook. Now, enter the write command including parameter <RealLocReq>=1 to get the actual location numbers. The numbers at the end of each line are the memory locations in the phonebook and can be used for dialing or editing phonebook entries: AT+CPBR=27 +CPBR: 27,"+999999",145,"Arthur" MC55_ATC_V04.00 Confidential / Released Read out phonebook location 27. This entry can be edited with AT+CPBW or used for dialing with ATD><mem><n>. Page 394 of 475 3/17/06 16.8 AT^SPBS Step through the selected phonebook alphabetically AT^SPBS can be used to scroll sequentially through the active phonebook records in alphabetical order by name. Three entries will be displayed at a time. Every time the write command is executed, 3 rows of phonebook records are returned. Each triplet overlaps with the next one. The actual index depends on parameter <value>. This parameter determines whether the index will be increased or decreased. If the index in one output line reaches the last index in the alphabetical list, the next output line will display the first list entry. After the last record of the phonebook has been reached (see parameter <used> for AT^SPBG), the <internal-counter> switches over to the first. There are two ways to use AT^SPBS: • If the optional parameter <RealLocReq> is omitted or (0) the sorted entries will be sequentially numbered. As these numbers are not identical with the location numbers stored in the various phonebooks AT^SPBS can be used for reading only. For example, it helps you find entries starting with matching characters. Do not use the serial numbers to dial out or modify entries. • If parameter <RealLocReq>=1 is given by the write command, the response parameter <location> additionally appended to each entry indicates the actual location number. This number can be used for editing with AT+CPBW or dialing with ATD><mem><n>. The first index number of each entry is only the serial number of the sorted list. See examples below. Syntax Test Command AT^SPBS=? Response(s) ^SPBS: (list of supported <value>) OK Write Command AT^SPBS=<value>[, <RealLocReq>] Response(s) ^SPBS: <index-a>, <number>, <type>, <text>[, <location>] ^SPBS: <index-b>, <number>, <type>, <text>[, <location>] ^SPBS: <index-c>, <number>, <type>, <text>[, <location>] OK +CME ERROR Reference(s) PIN SIEMENS % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <value>(num) 1 To make a step forward in the alphabetically sorted phonebook. 2 To make a step backward in the alphabetically sorted phonebook. <index-a>(num) 1...maxindex MC55_ATC_V04.00 Confidential / Released The index in the sorted list of phonebook entries that identifies the first entry displayed. The value of <index-a> is determined by the value of the <internalcounter> and by parameter <value>. Page 395 of 475 3/17/06 After a write command has terminated successfully with "OK", the value from parameter <index-a> is saved and retained as the new <internalcounter> value. Mind after the last record of phonebook, the first entry follows. <index-b>(num) 1...maxindex The index in the sorted list of phonebook entries that identifies the second entry displayed. <index-b>= (<index-a>+1). Mind after the last record of phonebook, the first entry follows. <index-c>(num) 1...maxindex The index in the sorted list of phonebook entries that identifies the third entry displayed. <index-c>= (<index-b>+1). Mind after the last record of phonebook, the first entry follows. <number>(str) String type phone number in format specified by <type>. the number parameter may be an empty string. <type>(num) Type of address octet, which defines the used type of number (ton) and the numbering plan identification (npi). Please consider that for types other than 129 or 145 dialing from phonebook with ATD><mem><n> is, depending on the network, not always possible (refer to GSM 04.08 subclause 10.5.4.7 for details). See also <type> of AT+CPBW. Possible values are: 145 Dialing string <number> includes international access code character '+' 161 National number. Network support of this type is optional. 209 Dialing string <number> has been saved as ASCII string and includes nondigit characters other than "*", "#" or "+". Note that phonebook entries saved with this type cannot be dialed. 255 Dialing string <number> is a command to control a Supplementary Service, i.e. "*", "#" codes are contained. Network support of this type is optional. 129 Otherwise <text>(str)(+CSCS) Text assigned to the phone number. <RealLocReq>(num) Is a display of the "real" <location> of the entry required? [0] Do not show an entry's "real" location number. Parameter <location> will not be displayed 1 Show the "real" location number as parameter <location> at the end of the entry <location>(num) The location within phonebook memory at which the corresponding entry is located. This location may be used for other phonebook commands (e.g. AT+CPBR, AT+CPBW, ATD><mem><n>). MC55_ATC_V04.00 Confidential / Released Page 396 of 475 3/17/06 <internal-counter>(num) 0(&F)...maxindex This parameter is only an internal parameter and cannot modified directly. The internal counter will be reset to index 0 after a call to ATZ or AT&F. Notes • The complete list of sorted entries can be retrieved using AT command AT^SPBG. • The command can be used for the phonebooks "SM", "FD", "ME" (cf. AT+CPBS). • Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data may not yet be accessible, resulting in a short delay before the requested AT command response is returned. See Section 20.1, Restricted access to SIM data after SIM PIN authentication for further detail. Examples EXAMPLE 1 This example illustrates how to search down and up again using AT^SPBS=1 and 2: First, AT&F is issued to make sure that AT^SPBS=1 starts from the first character in alphabetical order. at&f OK at^spbs=1 ^SPBS:1,"+999999",145,"Arthur" ^SPBS:2,"+777777",145,"Bill" ^SPBS:3,"+888888",145,"Charlie" OK at^spbs=1 ^SPBS:2,"+777777",145,"Bill" ^SPBS:3,"+888888",145,"Charlie" ^SPBS:4,"0304444444",129,"Esther" OK at^spbs=1 ^SPBS:3,"+888888",145,"Charlie" ^SPBS:4,"0304444444",129,"Esther" ^SPBS:5,"03033333333",129,"Harry" OK at^spbs=2 ^SPBS:2,"+777777",145,"Bill" ^SPBS:3,"+888888",145,"Charlie" ^SPBS:4,"0304444444",129,"Esther" OK EXAMPLE 2 This example shows that when the last index in the sorted list has been reached, the internal counter overflows to the first index. at&f OK at^spbs=2 ^SPBS:33,"+49301234567",145,"TomTailor" ^SPBS:1,"+999999",145,"Arthur" ^SPBS:2,"+777777",145,"Bill" Reset internal counter to 0. Step down one entry starting from (internal counter)=0 - overflow occurs. OK MC55_ATC_V04.00 Confidential / Released Page 397 of 475 3/17/06 EXAMPLE 3 Using AT^SPBS with <RealLocReq>=1 in order to obtain the entries' location numbers: at^spbs=1,1 ^SPBS:1,"+999999",145,"Arthur",27 ^SPBS:2,"+777777",145,"Bill",6 ^SPBS:3,"+888888",145,"Charlie",15 The numbers at the end of each line are the memory locations in the phonebook and can be used for dialing or editing phonebook entries: at+cpbr=27 +CPBR: 27,"+999999",145,"Arthur" MC55_ATC_V04.00 Confidential / Released Read out phonebook location 27. This entry can be edited with AT+CPBW or used for dialing with ATD><mem><n>. Page 398 of 475 3/17/06 16.9 AT+CNUM Read own numbers AT+CNUM returns the subscribers own number(s) from the SIM. Syntax Test Command AT+CNUM=? Response(s) OK Exec Command AT+CNUM Response(s) [+CNUM: [<alpha>], <number>, <type>] [+CNUM: ... ] OK ERROR +CME ERROR: <err> Reference(s) PIN GSM 07.07 % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <alpha>(str) Optional alphanumeric string associated with <number>. <number>(str) Phone number in format specified by <type>. <type>(str) Type of address octet, see also: AT+CPBR <type>. Note • Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data may not yet be accessible, resulting in a short delay before the requested AT command response is returned. See Section 20.1, Restricted access to SIM data after SIM PIN authentication for further detail. MC55_ATC_V04.00 Confidential / Released Page 399 of 475 3/17/06 16.10 AT^SDLD Delete the 'last number redial' memory AT^SDLD deletes all numbers stored in the "LD" memory. Syntax Test Command AT^SDLD=? Response(s) OK Exec Command AT^SDLD Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN SIEMENS % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Note • Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data may not yet be accessible, resulting in a short delay before the requested AT command response is returned. See Section 20.1, Restricted access to SIM data after SIM PIN authentication for further detail. MC55_ATC_V04.00 Confidential / Released Page 400 of 475 3/17/06 17. Audio Commands The AT Commands described in this chapter are related to the MC55's audio interface. 17.1 Audio programming model The following figure illustrates how the signal path can be adjusted with the parameters <inCalibrate>, <inBbcGain>, <outBbcGain>, <outCalibrate> and <sideTone> as well as <io>, <mic> and <ep>. Figure 17.1: Audio programming model for MC55 Module MC55_ATC_V04.00 Confidential / Released Page 401 of 475 3/17/06 17.2 ATL Set monitor speaker loudness ATL is implemented for V.250ter compatibility reasons only, and has no effect. In multiplex mode (refer AT+CMUX) the command is supported on logical channel 1 only. Syntax Exec Command ATL[<val>] Response(s) OK Reference(s) PIN V.250 ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Parameter Description <val>(num) 17.3 ATM Set monitor speaker mode ATM is implemented for V.250ter compatibility reasons only, and has no effect. In multiplex mode (refer AT+CMUX) the command is supported on logical channel 1 only. Syntax Exec Command ATM[<val>] Response(s) OK Reference(s) V.250 PIN ! ASC0 ASC1 % ! MUX1 MUX2 % ! MUX3 Charge ! ! ! Last ! Parameter Description <val>(num) MC55_ATC_V04.00 Confidential / Released Page 402 of 475 3/17/06 17.4 AT+CLVL Loudspeaker volume level Syntax Test Command AT+CLVL=? Response(s) +CLVL: (list of supported<level>s) OK Read Command AT+CLVL? Response(s) +CLVL: <level> OK ERROR +CME ERROR: <err> Write Command AT+CLVL=<level> Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN GSM 07.07 ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <level>(num) Loudspeaker Volume Level 0...4(D) Notes • The write command can only be used in audio mode 2 - 6. • The values of the volume steps are specified with the parameters <outCalibrate>[0],...<outCalibrate>[4] of the AT^SNFO command. • As an alternative to AT+CLVL, you can use AT^SNFO and AT^SNFV. The parameter <level> is identical with <outStep> used by both commands. • Any change to <level> (or <outStep>) takes effect in audio modes 2 to 6. That is, when you change <level> (or <outStep>) and then select another mode with AT^SNFS, the same step will be applied. The only exception is audio mode 1 which is fixed to <level>=4 (or accordingly <outStep>=4). • <level> (or <outStep>) is stored non-volatile when the ME is powered down with AT^SMSO or reset with AT+CFUN=1,1. MC55_ATC_V04.00 Confidential / Released Page 403 of 475 3/17/06 17.5 AT+CMUT Mute control The AT+CMUT command mutes the microphone input. The command can be used in all audio modes (1 to 6) and during a voice call only. See AT^SNFS for more details on the various audio modes. As alternative, you can use the AT^SNFM command. During an active call, users should be aware that when they switch back and forth between different audio modes (for example handsfree on/off) the value of <mute> does not change, i.e. the microphone mode is retained until explicitly changed. Syntax Test Command AT+CMUT=? Response(s) +CMUT: (list of supported<mute>s) OK Read Command AT+CMUT? Response(s) +CMUT: <mute> OK ERROR +CME ERROR: <err> Write Command AT+CMUT=<mute> Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN GSM 07.07 ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <mute>(num) 0(P) Mute off 1 Mute on MC55_ATC_V04.00 Confidential / Released Page 404 of 475 3/17/06 17.6 AT+VTD Tone duration This command refers to an integer <duration> that defines the length of tones transmitted with the AT+VTS command. Syntax Test Command AT+VTD=? Response(s) +VTD: (list of supported<duration>s) OK Read Command AT+VTD? Response(s) <duration> OK Write Command AT+VTD=<duration> Response(s) OK ERROR +CME ERROR Reference(s) PIN GSM 07.07 ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <duration>(num) Duration of the DTMF signal in 1/10 seconds with tolerance. The minimum duration of DTMF signals is 300ms. DTMF tones below 300ms cannot be generated. 1(&F)(P)...255 MC55_ATC_V04.00 Confidential / Released Page 405 of 475 3/17/06 17.7 AT+VTS DTMF and tone generation AT+VTS is intended to send ASCII characters or strings which cause the Mobile Switching Center (MSC) to transmit DTMF tones to a remote subscriber. The command can only be used during active voice calls and offers the following variants: • AT+VTS=<dtmfString> allows to send a sequence of DTMF tones with a duration defined with AT+VTD. • AT+VTS=<dtmf>[,<duration>] allows to send a single DTMF tone. In this case, the duration can be indvidually determined during the call. Syntax Test Command AT+VTS=? Response(s) +VTS: (list of supported<dtmf>s), (list of supported<duration>s) OK Write Command AT+VTS=<dtmfString> Response(s) OK Write Command AT+VTS=<dtmf>[, <duration>] Response(s) OK ERROR +CME ERROR Reference(s) PIN GSM 07.07 ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <dtmfString>(str) String of ASCII characters in the set 0-9,#,*,A, B, C, D. Maximal length of the string is 29. The string must be enclosed in quotation marks ("..."). <dtmf>(str) ASCII character in the set 0...9,#,*, A, B, C, D. <duration>(num) Tone duration in 1/10 seconds with tolerance. If not specified current setting of AT+VTD is used. The minimum duration of DTMF signals is 300ms. DTMF tones below 300ms cannot be generated. 1...255 MC55_ATC_V04.00 Confidential / Released Page 406 of 475 3/17/06 17.8 AT^SAIC Audio Interface Configuration AT^SAIC configures the interface connections of the active audio mode. The write command is usable in audio modes 2 to 6 only. If AT^SNFS=1, any attempt to use AT^SAIC write command is rejected with error response. This is because all default parameters in audio mode 1 are determined for type approval and are not adjustable. To allocate a specific audio mode to one of the audio interfaces, first select the audio mode with AT^SNFS and then choose the interface using AT^SAIC. Syntax Test Command AT^SAIC=? Response(s) ^SAIC:(list of supported <io>s), (list of supported<mic>s), (list of supported<ep>s) OK Read Command AT^SAIC? Response(s) ^SAIC: <io>, <mic>, <ep> OK Write Command AT^SAIC=<io>[, <mic>[, <ep>]] Response(s) OK ERROR +CME ERROR: operation not allowed Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <io>(num)(^SNFW) Input and output selection 1 Digital input and output 2 Analog input and output <mic>(num)(^SNFW) Microphone selection 1 Microphone 1 2 Microphone 2 <ep>(num)(^SNFW) Select differential earpiece amplifier 1 Selects the earpiece amplifier 1 2 Selects the earpiece amplifier 2 3 Selects both amplifiers. Note that both amplifiers are connected in parallel and therefore, get the same output power if <ep>=3. MC55_ATC_V04.00 Confidential / Released Page 407 of 475 3/17/06 Notes • The factory defaults of AT^SAIC vary with the selected audio mode. If AT^SNFS=1 or 4 or 5, then AT^SAIC=2,1,1. If AT^SNFS=2 or 3 or 6, then AT^SAIC=2,2,2. AT^SNFD can be used to reset the factory defaults. • For use after restart of the ME, you are advised to store the settings of AT^SAIC and AT^SNFS to the audio profile saved with AT^SNFW. Otherwise, audio mode 1 (AT^SNFS=1) and audio interface 2 (AT^SAIC=2,1,1) will be active each time the ME is powered up. MC55_ATC_V04.00 Confidential / Released Page 408 of 475 3/17/06 17.9 AT^SNFA Set or query of microphone attenuation AT^SNFA specifies the large-scale attenuation on the microphone path of the audio device currently selected with AT^SNFS. The write command is only available in audio modes 2 to 6. Syntax Test Command AT^SNFA=? Response(s) ^SNFA: (list of supported <atten>s) OK Read Command AT^SNFA? Response(s) ^SNFA: <atten> OK Write Command AT^SNFA=<atten> Response(s) OK ERROR CME ERROR: <err> Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <atten>(num)(^SNFW) Multiplication factor for input samples. Parameter <atten> is identical with <inCalibrate> of AT^SNFI. Formula used to calculate microphone attenuation (negative gain): Gain in dB = 20 * log(<atten>/32768) 0...32767(P)...65535 0 Microphone is muted. Please note that AT^SNFA cannot be used to mute the microphone. Therefore, any attempt to enter 0 will be rejected with error response. Value 0 is returned only by the read command AT^SNFA? after the microphone was muted with AT^SNFM=0 during an active call. 32767 No attenuation on the microphone path Values greater than 32767 will be suppressed to 32767. Notes • This command is provided for compatibility with former products (e.g. M20) and is a subset of AT^SNFI. The parameter <inCalibrate> of AT^SNFI is identical with <atten> of AT^SNFA. • To make the changes persistent use AT^SNFW. MC55_ATC_V04.00 Confidential / Released Page 409 of 475 3/17/06 Example ^SYSSTART at^snfa=? ^SNFA: (0-65535) OK at^snfa? ^SNFA: 32767 OK at^snfs=4 OK at^snfa=1 OK at^snfa? ^SNFA: 1 OK at^snfi? ^SNFI: 5,1 OK at^snfi=5,45 OK at^snfa? ^SNFA: 45 OK MC55_ATC_V04.00 Confidential / Released Page 410 of 475 3/17/06 17.10 AT^SNFD Set audio parameters to manufacturer default values AT^SNFD sets the active audio parameters to manufacturer defined default values. The restored values are: AT^SNFA: <atten> AT^SNFI: <inBbcGain>, <inCalibrate> AT^SNFO: <outBbcGain>, <outCalibrate>[0 to 4], <sideTone> AT^SAIC: <io>, <mic>, <ep> AT^SNFS: <audMode> Syntax Test Command AT^SNFD=? Response(s) OK Exec Command AT^SNFD Response(s) OK Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Note • Remember that the factory set audio mode 1 is fixed to <outStep>=4. Consequently, AT^SNFD restores <audMode> together with <outStep>=4, but does not affect the values of <outStep> currently selected in audio modes 2 - 6. This means, if <audMode>=1, the read commands AT^SNFO, AT^SNFV and AT+CLVL will always deliver <outStep>=4. In all other modes the <outStep> value is retained until explicitly changed. MC55_ATC_V04.00 Confidential / Released Page 411 of 475 3/17/06 17.11 AT^SNFI Set microphone path parameters AT^SNFI controls the microphone path amplification. Read and write options of this command refer to the active audio mode. The write command works only in audio modes 2 to 6. Syntax Test Command AT^SNFI=? Response(s) ^SNFI: (list of supported <inBbcGain>s) , (list of supported <inCalibrate>s) OK Read Command AT^SNFI? Response(s) ^SNFI: <inBbcGain>, <inCalibrate> OK Write Command AT^SNFI=<inBbcGain>, <inCalibrate> Response(s) OK Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <inBbcGain>(num)(^SNFW) ADC gain adjustable in eight 6 dB steps from 0 dB to 42 dB (0=0dB, 7=42dB, 8 steps of 6 dB). 0...7 <inCalibrate>(num)(^SNFW) Multiplication factor for input samples. Formula to calculate the negative gain (attenuation) of the input signal: Gain in dB = 20 * log (inCalibrate / 32768) 0...32767 Notes • The range of <inCalibrate> is up to 65535 but will be suppressed to 32767. Values above <inCalibrate>= 65535 will cause a failure. • The parameter <inCalibrate> of AT^SNFI is identical with <atten> of AT^SNFA. • For use after restart, changed values can be stored with AT^SNFW. • Attention! When you adjust audio parameters avoid exceeding the maximum allowed level. Bear in mind that exposure to excessive levels of noise can cause physical damage to users! MC55_ATC_V04.00 Confidential / Released Page 412 of 475 3/17/06 17.12 AT^SNFM Set microphone audio path and power supply The AT^SNFM read command returns the microphone mute and supply voltage status. The AT^SNFM write command can be used to switch the microphone's audio path (muted / not muted) or to control the power supply of the MICP2 line (microphone input of the second analog audio interface). The microphone can be muted or activated by changing <MicSwitch> in all audio modes (1 to 6) and during a voice call only. As an alternative, you can use the AT+CMUT command to mute the microphone. Syntax Test Command AT^SNFM=? Response(s) ^SNFM: (list of supported <MicSwitch>s) , (list of supported <MicVccCtl>s) OK Read Command AT^SNFM? Response(s) ^SNFM: <MicSwitch>, <MicVccState> OK Write Command AT^SNFM=[<MicSwitch>][, <MicVccCtl>] Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <MicSwitch>(num) Microphone mute control parameter. Evaluated only during voice calls and if <MicVccCtl> is omitted, e.g. AT^SNFM=1. Command does not depend on audio mode. 0 (P) 1 Mutes the microphone. Activates the microphone. <MicVccCtl>(num) Microphone supply voltage control parameter. Setting applies to microphone input 2 only. CME error is given if <MicSwitch> is not omitted. Enter for example AT^SNFM=,1 or AT^SNFM=,2. 0 Supply voltage is always switched off. 1 Supply voltage is always switched on. (P) 2 MC55_ATC_V04.00 Confidential / Released Supply voltage state during voice calls is controlled by the ME. Actual value is determined by parameter data set of the selected audio mode. Page 413 of 475 3/17/06 <MicVccState>(num) Microphone supply voltage control status. 0 Supply voltage was set to a constant value. 2 Supply voltage state is controlled by the ME and depends on parameter data set of the selected audio mode. Notes • The programmable power supply of the MICP2 line gives you greater flexibility in connecting audio accessories or using MICP2 for a variety of functions other than audio. A detailed description of the extended usage of MICP2 can be found in [8]. • During an active call, users should be aware that when they switch back and forth between different audio modes (for example handsfree on/off) the value of <MicSwitch> does not change, i.e. the microphone mode is retained until explicitly changed. MC55_ATC_V04.00 Confidential / Released Page 414 of 475 3/17/06 17.13 AT^SNFO Set audio output (= loudspeaker path) parameter AT^SNFO controls the earpiece path amplification. The read and write commands refer to the active audio mode. The write command works only in audio modes 2 to 6. Syntax Test Command AT^SNFO=? Response(s) ^SNFO: (list of supported <outBbcGain>s), (list of supported <outCalibrate>s), (list of supported <outStep>s), (list of supported <sideTone>s) OK Read Command AT^SNFO? Response(s) ^SNFO: <outBbcGain>, <outCalibrate>[0] , <outCalibrate>[1] , <outCalibrate>[2] , <outCalibrate>[3] , <outCalibrate>[4] , <outStep>, <sideTone> OK Write Command AT^SNFO=<outBbcGain>, <outCalibrate>[0] , <outCalibrate>[1] , <outCalibrate>[2] , <outCalibrate>[3] , <outCalibrate>[4] , <outStep>, <sideTone> Response(s) OK Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <outBbcGain>(num)(^SNFW) Negative DAC gain (attenuation) adjustable in four 6 dB steps from 0 dB to -18 dB (0=0 dB, 3=-18 dB) 0...3 <outCalibrate>(num)(^SNFW) Formula to calculate the value of the 5 volume steps selectable with parameter <outStep>: Attenuation = 20 * log (2 * outCalibrate[n] / 32768) 0...32767 <outStep>(num) Volume steps 0 - 4, each defined with outCalibrate[n] 0...[4] <sideTone>(num)(^SNFW) Multiplication factor for the sidetone gain. Formula to calculate how much of the original microphone signal is added to the earpiece signal: Sidetone gain in dB = 20 * log (sideTone / 32768). 0...32767 MC55_ATC_V04.00 Confidential / Released Page 415 of 475 3/17/06 Notes • <outCalibrate> specifies the amount of volume of each <outStep>. The range of each <outCalibrate> is up to 65535, but will be suppressed to 32767. A value above <outCalibrate>= 65535 will cause an error. • The range of <sideTone> is up to 65535, but will be suppressed to 32767. A value above <sideTone>= 65535 will cause an error. • Any change to <outStep> takes effect in audio modes 2 to 6. That is, when you change <outStep> and then select another mode with AT^SNFS, the same step will be applied. Nevertheless, the sound quality and the amount of volume are not necessarily the same, since all remaining audio parameters can use different values in either mode. • Audio mode 1 is fixed to <outStep>=4. In this mode, any attempt to change <outStep> or other parameters returns an error. • The value of <outStep> is stored non-volatile when the ME is powered down with AT^SMSO or reset with AT+CFUN=x,1. Any other parameters changed with AT^SNFO need to be saved with AT^SNFW for use after restart. See also AT^SNFD for details on restoring factory defaults. • The values of <outStep> can also be changed with AT^SNFV and AT+CLVL. • CAUTION! When you adjust audio parameters avoid exceeding the maximum allowed level. Bear in mind that exposure to excessive levels of noise can cause physical damage to users! MC55_ATC_V04.00 Confidential / Released Page 416 of 475 3/17/06 17.14 AT^SNFPT Set progress tones AT^SNFPT controls the Call Progress Tones generated at the beginning of a mobile originated call setup. Please note that the setting is stored volatile, i.e. after restart or reset, the default value 1 will be restored. Syntax Test Command AT^SNFPT=? Response(s) ^SNFPT: (list of supported <pt>s) OK Read Command AT^SNFPT? Response(s) ^SNFPT: <pt> OK Write Command AT^SNFPT=<pt> Response(s) OK Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <pt>(num) 0 (P) 1 MC55_ATC_V04.00 Confidential / Released Disables Call Progress Tones Enables Call Progress Tones (audible tones shortly heard on the phone when ME starts to set up a call.) Page 417 of 475 3/17/06 17.15 AT^SNFS Select audio hardware set The AT^SNFS write command serves to set the audio mode required for the connected equipment. AT^SNFS can also be used in conjunction with AT^SAIC. This is useful, for example, if the audio interfaces are operated alternatively to benefit from different devices. Each audio mode can be assigned a specific interface. To do so, first select the audio mode with AT^SNFS, then activate the audio interface with AT^SAIC and finally enter AT^SNFW to store the settings to your audio profile. To switch back and forth it is sufficient to use AT^SNFS. Syntax Test Command AT^SNFS=? Response(s) ^SNFS: (list of supported <audMode>s) OK Read Command AT^SNFS? Response(s) ^SNFS: <audMode> OK Write Command AT^SNFS=<audMode> Response(s) OK ERROR CME ERROR: <err> Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <audMode>(num)(^SNFW) [1] Audio mode 1: Standard mode optimized for the reference handset, that can be connected to the analog interface 1 (see "MC55 Hardware Interface Description" for information on this handset.) To adjust the volume use the knob of the reference handset. In audio mode 4, this handset can be used with user defined parameters. Note: The default parameters are determined for type approval and are not adjustable with AT commands. AT^SNFD restores <audMode> 1. 2 Audio mode 2: Customer specific mode for a basic handsfree (speakerphone) device (Siemens Car Kit Portable). Analog interface 2 is assumed as default. 3 Audio mode 3: Customer specific mode for a mono-headset. Analog interface 2 is assumed as default. 4 Audio mode 4: Customer specific mode for a user handset. Analog interface 1 is assumed as default. 5 Audio mode 5: Customer specific mode. Analog interface 1 is assumed as default. 6 Audio mode 6: Customer specific mode. Analog interface 2 is assumed as default. MC55_ATC_V04.00 Confidential / Released Page 418 of 475 3/17/06 Notes • The write command can be used during a voice call to switch back and forth between different modes. This allows the user, for example, to switch handsfree operation (speakerphone) on and off. • Users should be aware that <outStep> is a global setting. This means, when another audio mode is selected during a call, the value of <outStep> does not change. This is also true for mute operation which can be set with AT^SNFM or AT+CMUT: If the microphone is muted and the user selects another audio mode during the call, then the microphone remains muted until explicitly changed. Exception: In audio mode 1 <outStep>=4 is fix. • For use after restart of the module, you are advised to store the selected mode to the audio profile saved with AT^SNFW. Otherwise, audio mode 1 will be active each time the module is powered up. Examples EXAMPLE 1 Suppose a user wishes to use alternatively a handsfree device (speakerphone) and a handset. The handset can be connected to the first analog interface and adjusted to audio mode 4. The handsfree device can be attached to the second analog interface and adjusted to audio mode 2. The factory defaults of AT^SAIC need not be changed. Settings for the handset: AT^SNFS=4 OK AT^SAIC? ^SAIC: 2,1,1 OK Factory default of AT^SAIC assigned to audio mode 4. Settings for the handsfree device: AT^SNFS=2 OK AT^SAIC? ^SAIC: 2,2,2 OK Factory default of AT^SAIC assigned to audio mode 2. To store the configuration to the user defined audio profile: AT^SNFW OK Stores the audio mode and the interface. To switch back and forth: AT^SNFS=4 OK AT^SNFS=2 OK Switches to the handset connected to analog interface 1. Switches to the handsfree device at analog interface 2. EXAMPLE 2 The following example illustrates a combination of a handset and a handsfree device connected to other interfaces than those assumed as factory default. Settings for a handset connected to the second analog interface and adjusted to audio mode 4: AT^SNFS=4 OK AT^SAIC=2,2,2 OK Settings for a handsfree device connected to the first analog interface and adjusted to audio mode 2: AT^SNFS=2 OK AT^SAIC=2,1,1 OK To store the configuration to the user defined audio profile: MC55_ATC_V04.00 Confidential / Released Page 419 of 475 3/17/06 AT^SNFW OK Stores the audio mode and the interface. To switch back and forth: AT^SNFS=4 OK AT^SNFS=2 OK MC55_ATC_V04.00 Confidential / Released Switches to the handset connected to analog interface 1. Switches to the handsfree device at analog interface 2. Page 420 of 475 3/17/06 17.16 AT^SNFTTY Signal TTY/CTM audio mode capability MC55 offers basic support for equipment using the CTM standard (Cellular Text Telephone Modems). The benefit of CTM is that text characters typed on a TTY device (Text Telephone Type-writer) can be transformed into special audio burst signals for reliable transmission via the existing speech channels of a cellular phone system. If CTM mode is activated, the ME will set the necessary bearer capability bit on outgoing (mobile originated) calls and incoming calls with this bearer capability bit set are accepted. The TE needs to decode the special audio burst signals. If CTM mode is disabled, the ME will clear the bearer capability bit on mobile originated calls and incoming calls with the bearer capability bit set are rejected because the MC55 expects that CTM coded speech data cannot be decoded by the TE. Designed to set the module's speech system into CTM mode, the AT^SNFTTY command allows a CTM device to be connected to one of the three audio interfaces of MC55. Traditional TTY devices that do not incorporate CTM functionality can be connected through an external TTY-to-CTM adapter. Related documents: Refer to the relevant standards, such as 3GPP TS 26.226 (ETSI TS 126 226) and 3GPP TS 23.228 (ETSI TS 123 226). 3GPP documentation can be retrieved, for example, from http://www.3gpp.org/ specs/specs.htm. Application Note 22 "Using TTY/CTM equipment" supplies information needed to connect TTY/CTM equipment to the MC55. Requirements for using TTY/CTM features: • TTY/CTM functionality requires audio mode 5 or 6 with all audio parameters set to their factory default. To do so, first enter the AT^SNFS command to select audio mode 5, then use AT^SNFI and AT^SNFO to restore the default values. Alternatively, factory defaults of all audio parameters in audio modes 2 - 6 can easily be set with AT^SNFD. • Depending on which audio interface the CTM device is connected to select the according settings via AT^SAIC. Syntax Test Command AT^SNFTTY=? Response(s) ^SNFTTY: (list of supported <audioState>s) OK Read Command AT^SNFTTY? Response(s) ^SNFTTY: <audioState> OK Write Command AT^SNFTTY=<audioState> Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN SIEMENS % ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <audioState>(num) 0 Audio path is in normal speech mode. 1 Audio path is in TTY/CTM mode. MC55_ATC_V04.00 Confidential / Released Page 421 of 475 3/17/06 17.17 AT^SNFV Set loudspeaker volume AT^SNFV can be used to set the volume of the loudspeaker to the value <outCalibrate> addressed by <outStep>. The read and write commands refer to the active audio mode. The write command works only in audio modes 2 to 6. Syntax Test Command AT^SNFV=? Response(s) ^SNFV: (list of supported <outStep>s) OK Read Command AT^SNFV? Response(s) ^SNFV: <outStep> OK Write Command AT^SNFV=<outStep> Response(s) OK ERROR +CME ERROR Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <outStep>(num) The actual volume of each step is defined by the parameter <outCalibrate>, which can be set with AT^SNFO. 0...4(P) Notes • Any change to <outStep> takes effect in audio modes 2 to 6. That is, when you change <outStep> and then select another mode with AT^SNFS, the same step will be applied. Nevertheless, the actual volume can be quite different, depending on the values of <outCalibrate> set in each mode. The only exception is audio mode 1 which is fixed to <outStep>=4. • <outStep> is stored non-volatile when the ME is powered down with AT^SMSO or reset with AT+CFUN=1,1. <outStep> is not stored by AT^SNFW. • <outStep> can also be changed by AT^SNFO (Section 17.13) and AT+CLVL (Section 17.4). MC55_ATC_V04.00 Confidential / Released Page 422 of 475 3/17/06 17.18 AT^SNFW Write audio setting in non-volatile store AT^SNFW causes the TA to write the currently selected audio parameters to non-volatile store. The saved audio profile includes the following parameters: AT^SNFA: <atten> AT^SNFI: <inBbcGain>, <inCalibrate> AT^SNFO: <outBbcGain>, <outCalibrate>[0 to 4], <sideTone> AT^SNFS: <audMode> AT^SAIC: <io>, <mic>, <ep>. Syntax Test Command AT^SNFW=? Response(s) OK Exec Command AT^SNFW Response(s) OK ERROR CME ERROR: <err> Reference(s) PIN SIEMENS ! MC55_ATC_V04.00 Confidential / Released ASC0 ASC1 % Page 423 of 475 % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! 3/17/06 17.19 AT^SRTC Ring tone configuration The AT^SRTC read command returns the current <type> and current <volume>. The read command can be used while test playback is off or on. In the latter case, see execute command for details. The AT^SRTC execute command is intended for testing. It starts to play a melody from the audio output currently selected with AT^SNFS. To deactivate test playback use AT^SRTC again. During test playback, you can enter the write command to select another melody and adjust the volume. Also, you can enter the read command to check the type and volume of the current ring tone, and to view the status of playback (on / off). The test ringing signal cannot be activated when an MTC is ringing (ERROR). Selecting <volume>=0 during the test, immediately stops playback. After this, ring tones will be muted until you change <volume> using the write command. The AT^SRTC write command chooses the type and volume of ring tones. The settings can be changed no matter whether or not the ME is ringing. The selected type and volume are saved in the non-volatile Flash memory and, thus, are retained after Power Down. An exception is <type>=0, that can be entered to quickly mute the tone or melody currently played to indicate an event. <type>=0 only stops immediately the audible ring tone, but does not terminate the URC that indicates the event (for example RING). No permanent settings are changed or saved. Syntax Test Command AT^SRTC=? Response(s) ^SRTC:(list of supported) <type>s, (list of supported) <volume>s OK Read Command AT^SRTC? Response(s) ^SRTC: <type>, <volume>, <status> OK Exec Command AT^SRTC Response(s) OK Write Command AT^SRTC=[<type>][, <volume>] Response(s) ^SRTC: <type>, <volume> OK ERROR Reference(s) PIN SIEMENS ! MC55_ATC_V04.00 Confidential / Released ASC0 ASC1 % Page 424 of 475 % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! 3/17/06 Parameter Description <type>(num) Type of ring tone. You have a choice of 7 different ring tones and melodies. All will be played from the audio output selected with the AT^SNFS command. <type>=0 is only intended for muting. 0 Mutes the currently played tone immediately. 1 Sequence 1 2 Sequence 2 (D) 3 Sequence 3 4 Sequence 4 5 Sequence 5 6 Sequence 6 7 Sequence 7 <volume>(num) Volume of ring tone, varies from low to high 0(D) Mute 1 Very low 2 Identical with 1 3 Low 4 Identical with 3 5 Middle 6 Identical with 5 7 High <status>(num) Status of test ringing. Indicates whether or not a melody is currently being played back for testing 0 Switched off 1 Switched on Notes • Before first using ring tones note that the following settings apply: We have chosen to let you decide your own preferences when you start using ring tones. Therefore, factory setting is AT^SRTC=3,0,0 (ring tones are muted). To activate ring tones for the very first time, first enter the write command and simply change the volume. After applying a firmware update the volume and type selected before the firmware update will be preserved. • The test ringing signal cannot be activated while an MTC is ringing (ERROR). • If an MTC arrives during test playback, test ringing will be deactivated and "normal" ringing reactivated (RING). Likewise, an MOC will also stop test ringing. • If no optional parameter is entered, the old value will be kept. MC55_ATC_V04.00 Confidential / Released Page 425 of 475 3/17/06 18. Hardware related Commands The AT Commands described in this chapter are related to the MC55's hardware interface. More information regarding this interface is available with the "MC55 Hardware Interface Description"[2]. 18.1 AT+CCLK Real Time Clock Syntax Test Command AT+CCLK=? Response(s) OK Read Command AT+CCLK? Response(s) +CCLK: <time> OK Write Command AT+CCLK=<time> Response(s) +CME ERROR: <err> ERROR OK Reference(s) PIN GSM 07.07 ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % % % Last ! Parameter Description <time>(str) Format is "yy/mm/dd,hh:mm:ss", where the characters indicate the two last digits of the year, followed by month, day, hour, minutes, seconds; for example 6th of July 2005, 22:10:00 hours equals to "05/07/06,22:10:00" Factory default is "02/01/01,00:00:00" Notes • <time> is retained if the device enters the Power Down mode via AT^SMSO. • <time> will be reset to its factory default if power is totally disconnected. In this case, the clock starts with <time>= "02/01/01,00:00:00" upon next power-up. • Each time MC55 is restarted it takes 2s to re-initialize the RTC and to update the current time. Therefore, it is recommended to wait 2s before using the commands AT+CCLK and AT+CALA (for example 2s after ^SYSSTART has been output). MC55_ATC_V04.00 Confidential / Released Page 426 of 475 3/17/06 18.2 AT+CALA Set alarm time The AT+CALA write command can be used to set an alarm time in the ME When the alarm time is reached and the alarm is executed the ME returns an Unsolicited Result Code (URC) and the alarm time is reset to "00/01/ 01,00:00:00". The alarm can adopt two functions, depending on whether or not you switch the GSM engine off after setting the alarm: • Reminder message: You can use the alarm function to generate reminder messages. For this purpose, set the alarm as described below and do not switch off or power down the ME. When executed the message comes as an Unsolicited Result Code which reads "+CALA". • Alarm mode: You can use the alarm function to restart the ME when powered down. For this purpose, set the alarm as described below. Then power down the ME by entering the AT^SMSO command. When the alarm time is reached, the ME will wake up to Alarm mode. To prevent the ME from unintentionally logging into the GSM network, Alarm mode provides restricted operation. Upon wake-up, the ME indicates an Unsolicited Result Code which reads: "+CALA". A limited number of AT commands is available during Alarm mode, for details see Section 20.4, Availability of AT Commands Depending on Operating Mode of ME. The ME remains deregistered from the GSM network. If you want the ME to return to full operation (normal operating mode) it is necessary to restart the ME by driving the ignition line (IGT pin of application interface) to ground. If your ME is battery powered note that the battery can be charged while the ME stays in Alarm mode. For details please refer to [2]. The AT+CALA test command returns the supported array index values <n>, the supported alarm types <type> and the maximum length of the text <tlength> to be output. The AT+CALA read command returns the current alarm settings in the ME. Syntax Test Command AT+CALA=? Response(s) +CALA: (list of supported<n>s), (list of supported<type>s), (list of supported<tlength>s) OK ERROR +CME ERROR: <err> Read Command AT+CALA? Response(s) +CALA: <time>[, <n>[, <type>[, <text>]]] OK ERROR +CME ERROR: <err> Write Command AT+CALA=<time>[, <n>[, <type>[, <text>]]] Response(s) OK ERROR +CME ERROR Reference(s) PIN GSM 07.07 ! MC55_ATC_V04.00 Confidential / Released ASC0 ASC1 % Page 427 of 475 % MUX1 MUX2 % % MUX3 Charge % % % Last ! 3/17/06 Unsolicited Result Codes URC 1 +CALA: [<text>] Indicates reminder message. URC 2 ^SYSSTART ALARM MODE +CALA: <text> Indicates ME wake-up into Alarm mode. If autobauding is active (AT+IPR=0) the line "+CALA" does not appear, but your individual <text> message will be displayed. Parameter Description <time>(str) Format is "yy/MM/dd,hh:mm:ss". For example, 6th of July 2005, 22:10:00 equals to "05/07/06,22:10:00" (see also AT+CCLK). Note: If <time> equals current date and time or is set to an earlier date, TA returns +CME ERROR: 21. <n>(num) Integer type value indicating the array index of the alarm. The ME allows to set only one alarm at a time. Therefore, the list of supported alarm events indicated by the test command AT+CALA=? is <n>=0. If a second alarm time is set, the previous alarm will be deleted. Therefore, the read command AT+CALA? will always return <n>=0. This is also true if individual settings are made on ASC0 and ASC1 or the various Multiplexer channels, for details see notes below. <type>(num) Integer type value indicating the type of the alarm. 0 Alarm indication: text message via serial interface <text>(str) String type value indicating the text to be displayed when alarm time is reached; maximum length is <tlength>. By factory default, <text> is undefined. Note: <text> will be stored to the non-volatile flash memory when the device enters the Power Down mode via AT^SMSO. Once saved, it will be available upon next power-up, until you overwrite it by typing another text. This eliminates the need to enter the full string when setting a fresh alarm. <text> should not contain characters which are coded differently in ASCII and GSM (e.g. umlauts), see also "Supported character sets" and "GSM alphabet tables". <tlength>(num) Integer type value indicating the maximum length of <text>. The maximum length is 16. Notes • After the alarm was executed the parameter <time> of AT+CALA will be reset to "00/01/01,00:00:00", but <text> will be preserved as described above. • If MC55 is totally disconnected from power supply the most recently saved configuration of +CALA: <time>[,<n>[,<type>[,<text>]]] will be presented when MC55 is powered up. • Each time MC55 is restarted with ignition it takes 2s to re-initialize the RTC and to update the current time. Therefore, it is recommended to wait 2s before using the commands AT+CCLK and AT+CALA (for example 2s after ^SYSSTART has been output). MC55_ATC_V04.00 Confidential / Released Page 428 of 475 3/17/06 • Alarm settings on ASC0 / ASC1 and different Multiplexer channels (see AT+CMUX): - On each interface an individual <text> message can be stored, but only one time setting applies. This means an alarm <time> set on one of the interfaces overwrites the time setting on all remaining interfaces. Therefore, the total number of alarm events returned by the read command AT+CALA? will always be <n>=0, no matter whether different text messages are stored. - When the scheduled alarm occurs, the ME sends the URC only on the interface where the most recent alarm setting was made. The alarm time will be reset to "00/01/01,00:00:00" on all interfaces. Examples EXAMPLE 1 You may want to configure a reminder message for July 31, 2005, at 9.30h, including the message "Good Morning". AT+CALA="05/07/31,09:30:00",0,0,"Good Morning" OK Do not switch off the GSM engine.When the alarm occurs the ME returns the following URC: +CALA: Good Morning EXAMPLE 2 To set a fresh alarm using the same message as in Example 1, simply enter date and time. <n>, <type>, <text>, <tlength> can be omitted: AT+CALA="05/07/31,08:50:00" OK When the alarm is executed the URC comes with the same message: +CALA: Good Morning EXAMPLE 3 To enable the ME to wake up into Alarm mode, e.g. on July 20, 2005, at 8.30h, enter AT+CALA="05/07/20,08:30:00" OK Next, power down the ME: AT^SMSO ^SMSO: MS OFF OK ^SHUTDOWN When the alarm is executed the ME wakes up to Alarm mode and displays a URC. If available, this line is followed by the individual <text> most recently saved. If no individual message was saved only the first line appears. "+CALA" +CALA: Good Morning MC55_ATC_V04.00 Confidential / Released Page 429 of 475 3/17/06 18.3 AT^SBC Battery Charge Control The functions of the AT^SBC differ depending on whether or not a battery is present. • General functions: The AT^SBC write command enables the presentation of URCs alerting the user of undervoltage conditions before the module switches off. The automatic shutdown caused by undervoltage is equivalent to the powerdown initiated with the AT^SMSO command, i.e. ME logs off from the network and the software enters a secure state avoiding loss of data. When the module is in IDLE mode it takes typically one minute to deregister from the network and to switch off. For further details regarding automatic shutdown and voltage ratings please refer to the Hardware Interface Description [2]. The AT^SBC read command displays the average current consumption of the module and, if specified, of the external application. • Functions available with battery connected: The AT^SBC read command can be used to query the status of the battery and the charger. The AT^SBC write command is important for entering the current consumption of the external application via <current>. It should be noted that the charge control supported by MC55 works only if the requirements described in the Hardware Interface Description [2] are met (battery type Lithium-Ion or Lithium Polymer, presence of an NTC and protection circuit etc.) and if <current> is correctly specified. If the battery does not incorporate an NTC, or the battery and the NTC are not compliant with the specified requirements the battery cannot be detected by MC55. Syntax Test Command AT^SBC=? Response(s) ^SBC:(list of supported <bcs>s), (list of supported <bcl>s), (list of supported <mpc>s) OK Read Command AT^SBC? Response(s) ^SBC: <bcs>, <bcl>, <mpc> OK ERROR +CME ERROR: <err> Write Command AT^SBC=<current> Response(s) OK ERROR +CME ERROR: <err> Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % § % Last ! Unsolicited Result Code MC55_ATC_V04.00 Confidential / Released Page 430 of 475 3/17/06 ^SBC: Undervoltage The message will be reported, for example, when the user attempts to set up a call while the voltage is close to the critical limit and further power loss is caused during the transmit burst. When the external charging circuit includes an NTC connected to the BATT_TEMP pin, the URC appears several times before the module switches off. The undervoltage protection is also efficient in applications which are not battery operated, i.e. where no NTC is connected to the BATT_TEMP pin. To use this feature it is sufficient to issue the write command which automatically enables the presentation of URCs. You do not need to specify <current>. Please note, that in contrast to applications with an NTC, MC55 will present the undervoltage URC only once and will then switch off without sending any further messages. Parameter Description <bcs>(num) Connection status of battery pack 0 No charging adapter is connected 1 Charging adapter is connected 2 Charging adapter is connected, charging in progress 3 Charging adapter is connected, charging has finished 4 Charging error, charging is interrupted 5 False charging temperature, charging is interrupted while temperature is beyond allowed range <bcl>(num) Battery capacity 0, 20, 40, 60, 80, 100 percent of remaining capacity (6 steps). 0 indicates that either the battery is exhausted or the capacity value is not available. While charging is in progress (charging adapter connected) the battery capacity is not available. Consequently, parameter <bcl>=0. To query the battery capacity disconnect the charger. <mpc>(num) Average current consumption. Value (0...5000) of average current consumption (mean value over a couple of seconds) in mA. <mpc> is obtained from the MC55's current consumption, plus the value you have specified for the application by using the write command AT^SBC=<current>. Remember that the current consumption of MC55 varies with its operating mode (IDLE, TALK, DATA, GPRS/DATA) and the power level. If <current> was not yet specified and no battery pack NTC is detected <mpc> returns only the module's present current consumption. If <current> was not yet specified, but the NTC of the connected battery pack is detected, an offset value of 200mA will, by default, be added. 200mA is an estimated value which represents the current consumption of a typical external application. Drawn from practical experience it serves as a precaution to ensure proper charging in case you have not entered <current>. It is strongly recommended that you enter the correct power consumption of your application as described below. <current>(num) Enter the current consumption of your host application in mA (0...5000). If used, the current provided over the 2.9V VDD pin of the application interface (maximum 70mA) must be added, too. When the MC55 is powered down or reset, the value of <current> is restored to its default. This affects the charging control and disables the presentation of Unsolicited Result Codes. Therefore, the parameter should be set every time when needed after rebooting the MC55. MC55_ATC_V04.00 Confidential / Released Page 431 of 475 3/17/06 Notes • If multiplex mode (AT+CMUX) is active, any virtual channel can be used for entering the read or write command. The undervoltage URC will be issued simultaneously on all three channels. • The URC "^SYSSTART CHARGE ONLY MODE" is indicated automatically when the module enters this mode (except when autobauding is active). Unlike the undervoltage URC, it cannot be disabled or enabled by the TE. 18.3.1 Responses returned by read command Responses returned by the AT^SBC read command vary with the operating mode of the MC55: • • • • Normal mode: MC55 is switched on by Ignition pin and running in SLEEP, IDLE, TALK or DATA mode. Charger is not connected. The AT^SBC read command indicates the battery capacity and the current consumption of the MC55 module and the application (if value of application was specified before as <current>). Normal mode + charging: Allows charging while MC55 is switched on by Ignition pin and running in SLEEP, IDLE, TALK or DATA mode. The AT^SBC read command returns only charger status and current consumption of the MC55 module and the application. Percentage of battery capacity is not available. CHARGE ONLY mode: Allows charging while MC55 is detached from GSM network. When started, the mode is indicated by the URC "^SYSSTART CHARGE ONLY MODE". The AT^SBC read command returns only the charger status and current consumption of the MC55 module and the application. Percentage of battery capacity is not available. In CHARGE ONLY mode a limited number of AT commands is accessible (see Appendix). There are several ways to activate the CHARGE ONLY mode: - from POWER DOWN mode: Connect charger while the MC55 was powered down with AT^SMSO - from Normal mode: Connect charger, then enter AT^SMSO. Alarm mode: The battery can be charged while the MC55 stays in Alarm mode, but the AT^SBC read command returns only charger status and current consumption of the MC55 module and the application. Percentage of battery capacity is not available. MC55_ATC_V04.00 Confidential / Released Page 432 of 475 3/17/06 18.4 AT^SBV Battery/Supply Voltage The AT^SBV execute command allows to monitor the supply (or battery) voltage of the module. The voltage is continuously measured at intervals depending on the operating mode of the RF interface. The duration of a measurement period ranges from 0.5s in TALK / DATA mode up to 50s when MC55 is in IDLE mode or Limited Service (deregistered). The displayed value is averaged over the last measuring period before the AT^SBV command was executed. The measurement is related to the test points of BATT+ and GND, both accessible on the bottom of the module. Refer to [1] for information on the module's test points. Syntax Test Command AT^SBV=? Response(s) OK ERROR +CME ERROR: Exec Command AT^SBV Response(s) ^SBV: <value> OK ERROR +CME ERROR: Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % % % Last ! Parameter Description <value>(num) Supply (or battery) voltage in mV MC55_ATC_V04.00 Confidential / Released Page 433 of 475 3/17/06 18.5 AT^SCTM Set critical operating temperature presentation mode or query temperature Use this command to monitor the temperature range of the module and the battery. The write command enables or disables the presentation of URCs to report critical temperature limits. CAUTION: During the first 15 seconds after start-up, the module operates in an automatic report mode: URCs can be always displayed regardless of the selected mode <n>. Syntax Test Command AT^SCTM=? Response(s) ^SCTM:(list of supported <n>s) OK Read Command AT^SCTM? Response(s) ^SCTM: <n>, <m> OK ERROR +CME ERROR Write Command AT^SCTM=<n> Response(s) OK ERROR +CME ERROR Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % % % Last ! Unsolicited Result Codes URC 1 URCs will be automatically sent to the TA when the temperature reaches or exceeds the critical level, or when it is back to normal. ^SCTM_A: <m> for battery temperature URC 2 ^SCTM_B: <m> for module (board) temperature MC55_ATC_V04.00 Confidential / Released Page 434 of 475 3/17/06 Command Description The read command returns: • the URC presentation mode • information about the current temperature range of the module Please note that the Read command does not indicate the temperature range of the battery. The battery temperature can only be reported by an Unsolicited Result Code. Select <n> to enable or disable the presentation of the URCs. Please note that the setting will not be stored upon Power Down, i.e. after restart or reset, the default <n>=0 will be restored. To benefit from the URCs <n>=1 needs to be selected every time you reboot the GSM engine. Parameter Description <n>(num) 0(&F)(P) Presentation of URCs is disabled (except for <m> equal to -2 or +2). 1 Presentation of URCs is enabled. <m>(num) -2 Below lowest temperature limit (causes immediate switch-off) -1 Below low temperature alert limit 0 Normal operating temperature 1 Above upper temperature alert limit 2 Above uppermost temperature limit (causes immediate switch-off) Notes • Please refer to the "Hardware Interface Description" for specifications on critical temperature ranges. • To avoid damage the module will shut down once the critical temperature is exceeded. The procedure is equivalent to the power-down initiated with AT^SMSO. • URCs indicating the alert level "1" or "-1" are intended to enable the user to take appropriate precautions, such as protect the module and the battery from exposure to extreme conditions, or save or back up data etc. The presentation of "1" or "-1" URCs depends on the settings selected with the write command: If <n>=0: Presentation is enabled for 15 s time after the module was switched on. After 15 s operation, the presentation will be disabled, i.e. no URCs will be generated. If <n>= 1: Presentation of "1" or "-1" URCs is always enabled. • Level "2" or "-2" URCs are followed by immediate shutdown. The presentation of these URCs is always enabled, i.e. they will be output even though the factory setting AT^SCTM=0 was never changed. • If the temperature limit is exceeded while an emergency call is in progress the engine continues to measure the temperature and to deliver alert messages, but deactivates the shutdown functionality. Once the call is terminated full temperature control will be resumed. If the temperature is still out of range ME switches off immediately. Examples EXAMPLE 1 URCs issued when the operating temperature is out of range: ^SCTM_A: ^SCTM_A: ^SCTM_B: ^SCTM_B: ^SCTM_A: ^SCTM_A: ^SCTM_B: ^SCTM_B: 1 2 1 2 -1 -2 -1 -2 MC55_ATC_V04.00 Confidential / Released Caution: Battery close to overtemperature limit. Alert: Battery above overtemperature limit. Engine switches off. Caution: Engine close to overtemperature limit. Alert: Engine is above overtemperature limit and switches off. Caution: Battery close to undertemperature limit. Alert: Battery below undertemperature limit. Engine switches off. Caution: Engine close to undertemperature limit. Alert: Engine is below undertemperature limit and switches off. Page 435 of 475 3/17/06 EXAMPLE 2 URCs issued when the temperature is back to normal (URC is output once): ^SCTM_A: 0 ^SCTM_B: 0 MC55_ATC_V04.00 Confidential / Released Battery temperature back to normal temperature. Engine back to normal temperature. Page 436 of 475 3/17/06 18.6 AT^SSYNC Configure SYNC Pin The AT^SSYNC command serves to configure the SYNC pin of the application interface. Please note that the SYNC pin may be assigned different functions: Depending on the design of the host application, the pin can either be used to indicate the current consumption in a transmit burst or to drive a status LED connected to the pin as specified in [2]. For detailed information on the SYNC pin and its LED functionality refer to [2]. Before changing the mode of the SYNC pin, carefully read the technical specifications. Syntax Test Command AT^SSYNC=? Response(s) ^SSYNC:list of supported <mode>s OK Read Command AT^SSYNC? Response(s) ^SSYNC:<mode> OK Write Command AT^SSYNC=<mode> Response(s) OK Reference(s) PIN SIEMENS ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <mode>(num) Operation mode of the SYNC pin. Setting is stored non-volatile. 0(D) SYNC mode: Enables the SYNC pin to indicate growing power consumption during a transmit burst. You can make use of the signal generated by the SYNC pin, if power consumption is your concern. To do so, ensure that your application is capable of processing the signal. Your platform design must be such that the incoming signal causes other components to draw less current. In short, this allows your application to accommodate current drain and thus, supply sufficient current to the GSM engine if required. 1 LED mode: Enables the SYNC pin to drive a status LED installed in your application according to the specifications provided in [2]. The coding of the LED is described in Section 18.6.1, ME status indicated by status LED patterns. MC55_ATC_V04.00 Confidential / Released Page 437 of 475 3/17/06 18.6.1 ME status indicated by status LED patterns The following table lists the possible patterns of status LED behavior, and describes the ME operating status indicated by each pattern if AT^SSYNC parameter <mode>=1. During the transition from one LED pattern to another the "on" and/or "off" periods of the LED may vary in length. This is because an event that triggers the change may occur any time and, thus, truncate the current LED pattern at any point. Table 18.1: Modes of the LED and indicated ME functions LED behavior ME operating status if AT^SSYNC=1 Permanently off ME is in one of the following modes: - POWER DOWN mode - ALARM mode - CHARGE ONLY mode - NON-CYCLIC SLEEP mode - CYCLIC SLEEP mode with no temporary wake-up event in progress 1) 600 ms on / 600ms off Limited Network Service: No SIM card inserted or no PIN entered, or network search in progress, or ongoing user authentication, or network login in progress. 75 ms on / 3 s off IDLE mode: The mobile is registered to the GSM network (monitoring control channels and user interactions). No call is in progress. 75 ms on / 75 ms off / 75 ms on / 3 s off One or more GPRS PDP contexts activated. 500 ms on / 25 ms off Packet switched data transfer is in progress. Permanently on Depending on type of call: Voice call: Connected to remote party. Data call: Connected to remote party or exchange of parameters while setting up or disconnecting a call. 1) When a temporary wake-up event (for example a call, a URC, a packet switched transfer) occurs in CYCLIC SLEEP mode the LED flashes according to the patterns listed above. See Section 2.8.1, Wake up the ME from SLEEP mode for details on the various SLEEP modes and wake-up events. MC55_ATC_V04.00 Confidential / Released Page 438 of 475 3/17/06 19. Miscellaneous Commands The AT Commands described in this chapter are related to various areas. 19.1 A/ Repeat previous command line Syntax Exec Command A/ Response(s) Reference(s) V.250 PIN ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description Repeat previous command line. Notes • Line does not need to end with terminating character. • After beginning with the character "a" or "A" a second character "t", "T" or "/" has to follow. In case of using a wrong second character, it is necessary to start again with character "a" or "A". • If autobauding is active, the command A/ cannot be used (see AT+IPR). MC55_ATC_V04.00 Confidential / Released Page 439 of 475 3/17/06 19.2 ATS3 Set command line termination character The ATS3 command determines the character recognized by the TA to terminate an incoming command line. Syntax Read Command ATS3? Response(s) <n> OK Write Command ATS3=<n> Response(s) OK ERROR Reference(s) V.250 PIN ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <n>(num)(&W)(&V) command line termination character 000...13(&F)...127 Notes • Using a value other than the default 13 may cause problems when entering commands. • Whenever you change the setting take into account that the new value has no effect on the URC "^SHUTDOWN". MC55_ATC_V04.00 Confidential / Released Page 440 of 475 3/17/06 19.3 ATS4 Set response formatting character The ATS4 command determines the character generated by the TA for result code and information text. Syntax Read Command ATS4? Response(s) <n> OK Write Command ATS4=<n> Response(s) OK ERROR Reference(s) V.250 PIN ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Parameter Description <n>(num)(&W)(&V) response formatting character 000...10(&F)...127 Note • Whenever you change the setting take into account that the new value has no effect on the URC "^SHUTDOWN". MC55_ATC_V04.00 Confidential / Released Page 441 of 475 3/17/06 19.4 ATS5 Write command line editing character Syntax Read Command ATS5? Response(s) <n> OK Write Command ATS5=<n> Response(s) OK ERROR Reference(s) V.250 PIN ! ASC0 ASC1 % % MUX1 MUX2 % % MUX3 Charge % ! ! Last ! Command Description This parameter setting determines the character recognized by TA as a request to delete the immediately preceding character from the command line. Parameter Description <n>(num)(&W)(&V) command line editing character 000...8(&F)...127 MC55_ATC_V04.00 Confidential / Released Page 442 of 475 3/17/06 20. Appendix 20.1 Restricted access to SIM data after SIM PIN authentication The following commands can be used only after data from the SIM have been read successfully for the first time. Reading starts after successful SIM authentication has been performed, and may take up to 30 seconds depending on the SIM used. While the read process is in progress, an attempt to use any of the following commands will result in "+CME Error: 14" (SIM busy). ; ... AT Command not available ! ... AT command accessible immediately after PIN entry has returned OK % ... AT command fully accessible after SIM PIN authentication has been completed AT Command Exec Test Read Write AT+CMGL % ! ; % AT^SMGL % ! ; % AT+CMGR ; ! ; % AT^SMGR ; ! ; % AT+CSCA ; ! % ! AT^SSTGI ; % % % AT^SSTR ; % % % AT+CPBR ; % ; % AT+CPBW ; % ; % AT+CPBS ; % % % AT^SDLD % % ; ; AT^SPBC ; % ; % AT^SPBD ; % ; % AT^SPBG ; % ; % AT^SPBS ; % ; % ATD><mem><n> % ; ; ; MC55_ATC_V04.00 Confidential / Released Page 443 of 475 3/17/06 20.2 Star-Hash (*#) Network Commands The following command strings can be sent to the network via ATD and have to be terminated with a semicolon. The command strings are defined with GSM 2.30 [16]. Table 20.1: Star-Hash (*#) Command Overview Star-Hash Code Functionality Response, also refer to Table 20.3 *#06# Query IMEI <IMEI> OK **04[2]*oldPin[2]*newPin[2]*newPin[2]# Change SIM pwd +CME ERROR: <err> / OK Phone Security **05[2]*unblKey[2]*newPin[2]*new- Change/Unblocking SIM pwd Pin[2]# +CME ERROR: <err> / OK *#0003*MasterPhoneCode# Unlock ''PS'' lock with Master Phone Code +CME ERROR: <err> / OK *[*]03*[ZZ]*oldPw*newPw*newPw# Registration of net password +CME ERROR: <err> / OK Phone number presentation *#30# Check status of CLIP (Calling Line Identification Presentation) +CLIP : <n>,<m> OK (see AT+CLIP) *#31# Check status of CLIR (Calling Line Identification Restriction) +CLIR : <n>,<m> OK (see AT+CLIR) *31#<Phonenumber>[;] Suppress CLIR (see AT+CLIR) #31#<Phonenumber>[;] Activate CLIR (see AT+CLIR) *#76# Check status of COLP (Connected Line Identification Presentation) +COLP : <n>,<m> OK (see: AT+COLP) *#77# Check status of COLR (Connected Line Identification Restriction) +COLR : 0,<m> OK (where <m> = active or not active) (choice of *,#,*#,**,##)21*DN*BS# Act/deact/int/reg/eras CFU ^SCCFC : <reason>, <status>, <class> [,...] like +CCFC *) (see: AT+CCFC) (choice of *,#,*#,**,##)67*DN*BS# Act/deact/int/reg/eras CF busy see above (choice of *,#,*#,**,##)61*DN*BS*T# Act/deact/int/reg/eras CF no reply see above (choice of *,#,*#,**,##)62*DN*BS# Act/deact/int/reg/eras CF no reach see above (choice of *,#,*#,**,##)002*DN*BS*T# Act/deact/int/reg/eras CF all see above (choice of *,#,*#,**,##)004*DN*BS*T# Act/deact/int/reg/eras CF all cond. see above Activation/deactivation/int WAIT +CCWA : <status>, <class> [,...] like +CCWA *) (see: AT+CCWA) Call forwarding Call waiting (choice of *,#,*#)43*BS# MC55_ATC_V04.00 Confidential / Released Page 444 of 475 3/17/06 Star-Hash Code Functionality Response, also refer to Table 20.3 (choice of *,#,*#)33*Pw*BS# Act/deact/int BAOC ^SCLCK : <fac>, <status>, <class> [, ...] like +CLCK *) (Refer to AT+CLCK) (choice of *,#,*#)331*Pw*BS# Act/deact/int BAOIC see above (choice of *,#,*#)332*Pw*BS# Act/deact/int BAOIC exc.home see above (choice of *,#,*#)35*Pw*BS# Act/deact/int. BAIC see above (choice of *,#,*#)351*Pw*BS# Act/deact/int BAIC roaming see above #330*Pw*BS# Deact. All Barring Services see above #333*Pw*BS# Deact. All Outg.Barring Services see above #353*Pw*BS# Deact. All Inc.Barring Services see above Call hold and multiparty +CME ERROR: <err> / OK [C]...[C]# Send USSD message +CME ERROR: <err> / OK C[C] (excluded 1[C]) Send USSD message +CME ERROR: <err> / OK Call barring Call Hold / Multiparty C[C] in call USSD messages *) Notes on ^SCCFC, +CCWA, ^SCLCK: The output depends on the affected basic service of the Star-Hash code. One line will be output for every tele- or bearer service coded in basic service code BS. ^SCCFC and ^SCLCK are modified by giving an additional <reason> or <fac> in front of the regular output string generated by the standard commands +CCFC and +CLCK. Table 20.2: Abbreviations of Codes and Parameters used in Table 20.1 Abbreviation Meaning Value ZZ Type of supplementary services: Barring services All services 330 Not specified DN Dialing number String of digits 0-9 BS Basic service equivalent to parameter class: Voice FAX SMS SMS+FAX Data circuit asynchron Data circuit synchron dedicated PAD access dedicated Packet access Data circuit asynchron+PAD Data circuit synchron+Packet Data circuit asynchron+synchron+Packet+PAD All Services 11 13 16 12 25 24 27 26 21 22 20 -- T Time in seconds MC55_ATC_V04.00 Confidential / Released In contrast to AT+CCFC, parameter T has no default value. If T is not specified, an operator defined default or the last known value may be used, depending on the network operator. Page 445 of 475 3/17/06 Abbreviation Meaning Value PW Password -- C Character of TE character set (e.g. asterics, hash or digit in case of USSD, or digits in case of held calls or multiparty calls) -- Table 20.3: Star-Hash Command Response Parameters Parameter Meaning <m> Mode: 0 = not active, 1 = active <n> Unsolicited result code: 0 = presentation disabled, 1 = presentation enabled <status> Status: 0 = not active, 1 = active <class> Represents BS = basic service, refer to AT+CCFC, AT+CLCK <fac> Facility lock, refer to AT+CLCK <reason> Call forwarding reason For exact specification of format and parameters for Star-Hash commands refer to GSM 02.04, Table 3.2 [15] and GSM 02.30, Annex C [16]. Table 20.4: Star-Hash Commands for Supplementary Services Star-Hash Code Abbreviations in Table 20.1 Functionality * act Activate (except for CLIR, see list above) ** reg Register and activate *# int Check status (interrogate) # deact Deactivate (except for CLIR, see list above) ## eras Unregister and deactivate MC55_ATC_V04.00 Confidential / Released Page 446 of 475 3/17/06 20.3 Available AT Commands and Dependency on SIM PIN ; ... Command not available ! ... Command does not require PIN1 % ... Command requires PIN1 § ... Command sometimes requires PIN1 Table 20.5: Available AT Commands and Dependency on SIM PIN AT Command Exec Test Read Write AT&F ! ; ; ; AT&V ! ; ; ; AT&W ! ; ; ; ATQ ! ; ; ; ATV ! ; ; ; ATX ! ; ; ; ATZ ! ; ; ; AT+CFUN ; ! ! ! AT^SMSO ! ! ; ; AT+GCAP ! ! ; ; AT+CMEE ; ! ! ! AT+CSCS ; ! ! ! AT^SCFG ; ! ! ! AT^SM20 ; ! ! ! AT+CMER ; % % % AT+CIND ; ! ! ! AT^SIND ; ! ! ! AT+CEER % % ; ; ATS18 ; ; ! ! AT+CPAS ! ! ; ; AT+WS46 ; ! ! ! Configuration Commands Status Control Commands Serial Interface Control Commands AT\Q ! ; ; ; AT&C ! ; ; ; AT&D ! ; ; ; AT&S ! ; ; ; ATE ! ; ; ; AT+ILRR ; % % % AT+IPR ; ! ! ! AT+CMUX ; ! ! ! MC55_ATC_V04.00 Confidential / Released Page 447 of 475 3/17/06 AT Command Exec Test Read Write AT+CPIN ; ! ! ! AT+CPIN2 ; % % % AT^SPIC ! ! ! ! AT+CLCK ; % ; % AT^SLCK ; % ; % AT+CPWD ; % ; % AT^SPWD ; % ; % ATI ! ; ; ; AT+CGMI ! ! ; ; AT+GMI ! ! ; ; AT+CGMM ! ! ; ; AT+GMM ! ! ; ; AT+CGMR ! ! ; ; AT+GMR ! ! ; ; AT+CGSN ! ! ; ; AT+GSN ! ! ; ; AT+CIMI % % ; ; ATA % ; ; ; ATD § ; ; ; ATD><mem><n> % ; ; ; ATD><n> % ; ; ; ATD><str> % ; ; ; ATDI % ; ; ; ATDL % ; ; ; ATH ! ; ; ; AT+CHUP % % ; ; ATS0 ; ; ! % ATS6 ; ; ! ! ATS7 ; ; ! ! ATS8 ; ; ! ! ATS10 ; ; ! ! ATO ! ; ; ; +++ ! ; ; ; AT+CBST ; ! ! ! AT+CRLP ; ! ! ! AT+CLCC % % ; ; AT^SLCC % % % % Security Commands Identification Commands Call related Commands MC55_ATC_V04.00 Confidential / Released Page 448 of 475 3/17/06 AT Command Exec Test Read Write AT+CR ; % % % AT+CRC ; ! ! ! AT+CSNS ; ! ! ! AT^SCNI % % ; ; AT^SLCD % % ; ; AT^STCD % % ; ; ATP ! ; ; ; ATT ! ; ; ; AT+COPN % % ; ; AT+COPS ; ! § § AT^SOPS ; % ; ; AT+CREG ; ! ! ! AT+CSQ ! ! ; ; AT^SMONC % % ; ; AT^SMOND % % ; ; AT^MONI ! ! ; ! AT^MONP ! ! ; ! AT^SMONG % % ; % AT^SALS ; % % % AT^SHOM ! ! ; ; AT^SPLM % % ; ; AT+CPOL ; % % % AT^SPLR ; % ; % AT^SPLW ; % ; % Network Service Commands Supplementary Service Commands AT+CACM ; % % % AT^SACM % % ; % AT+CAMM ; % % % AT+CAOC % % % % AT+CCUG ; % % % AT+CCFC ; % ; % AT+CCWA ; % % % AT+CHLD ; % ; % AT+CLIP ; ! % ! AT+CLIR ; % % % AT+COLP ; % % % AT+CPUC ; % % % AT+CSSN ; ! ! ! AT+CUSD ; % % % MC55_ATC_V04.00 Confidential / Released Page 449 of 475 3/17/06 AT Command Exec Test Read Write AT^SICS ; ! ! ! AT^SICI ; ! ! ! AT^SISS ; ! ! ! AT^SISI ; ! ! ! AT^SISO ; ! ! % AT^SISC ; ! ; % AT^SISR ; ! ; % AT^SISW ; ! ; % AT^SISE ; ! ; ! AT+CGACT ; % % % AT+CGANS ; % ; % AT+CGATT ; % % % AT+CGAUTO ; % % % AT+CGEREP ; % % % AT+CGDATA ; % ; % AT+CGDCONT ; % % % AT+CGPADDR ; % ; % AT+CGQMIN ; % % % AT+CGQREQ ; % % % AT+CGREG ; % % % AT+CGSMS ; % % % AT^SGAUTH ; ! ! ! AT^SGCONF ; ! ! ! ATA % ; ; ; ATD*99# % ; ; ; ATD*98# % ; ; ; ATH % ; ; ; ATS0 ; ; ! % AT+FBADLIN ; ; ! ! AT+FBADMUL ; ; ! ! AT+FBOR ; ! ! ! AT+FCIG ; ! ! ! AT+FCLASS ; ! ! ! AT+FCQ ; ! ! ! AT+FCR ; ; ; ! AT+FDCC ; ! ! ! AT+FDFFC ; ! ! ! Internet Service Commands GPRS Commands FAX Commands MC55_ATC_V04.00 Confidential / Released Page 450 of 475 3/17/06 AT Command Exec Test Read Write AT+FDIS ; ! ! ! AT+FDR ! ; ; ; AT+FDT ! ; ; ! AT+FET ; ; ; ! AT+FK ! ; ; ; AT+FLID ; ! ! ! AT+FMDL ; ; ! ; AT+FMFR ; ; ! ; AT+FOPT ; ; ; ! AT+FPHCTO ; ; ! ! AT+FREV ; ; ! ; AT+FRH ; ! ; ! AT+FRM ; ! ; ! AT+FRS ; ; ; ! AT+FTH ; ! ; ! AT+FTM ; ! ; ! AT+FTS ; ; ; ! AT+FVRFC ; ! ! ! Short Message Service (SMS) Commands AT+CMGC ; % ; % AT+CMGD ; % ; % AT+CMGF ; ! ! ! AT+CMGL % % ; % AT+CMGR ; % ; % AT+CMGS ; % ; % AT+CMGW % % ; % AT+CMSS ; % ; % AT+CNMA % % ; % AT+CNMI ; % % % AT+CPMS ; % % % AT+CSCA ; % % % AT+CSCB ; % % % AT+CSDH ; % % % AT+CSMP ; % % % AT+CSMS ; % % % AT^SLMS % % ; ; AT^SMGL % % ; % AT^SMGO ; % % % AT^SMGR ; % ; % AT^SSCONF ; ! ! ! AT^SSDA ; ! ! ! MC55_ATC_V04.00 Confidential / Released Page 451 of 475 3/17/06 AT Command Exec Test Read Write ; ! ! ! AT+CRSM ; % ; % AT^SXSM ; % ; % AT^SCKS ; ! ! ! AT^SCID ! ! ; ; AT+CXXCID ! ! ; ; AT^SSMSS SIM related Commands SIM Application Toolkit (SAT) Commands AT^SSTA ; ! ! ! ^SSTN ; ; ; ; AT^SSTGI ; ! ! ! AT^SSTR ; ! ! ! AT+CPBR ; % ; % AT+CPBS ; % % % AT+CPBW ; % ; % AT^SPBC ; % ; % AT^SPBD ; % ; % AT^SPBG ; % ; % AT^SPBS ; % ; % AT+CNUM % % ; ; AT^SDLD % % ; ; ATL ! ; ; ; ATM ! ; ; ; AT+CLVL ; ! ! ! AT+CMUT ; ! ! ! AT+VTD ; ! ! ! AT+VTS ; ! ; ! AT^SAIC ; ! ! ! AT^SNFA ; ! ! ! AT^SNFD ! ! ; ; AT^SNFI ; ! ! ! AT^SNFM ; ! ! ! AT^SNFO ; ! ! ! AT^SNFPT ; ! ! ! AT^SNFS ; ! ! ! AT^SNFTTY ; % % % AT^SNFV ; ! ! ! Phonebook Commands Audio Commands MC55_ATC_V04.00 Confidential / Released Page 452 of 475 3/17/06 AT Command Exec Test Read Write AT^SNFW ! ! ; ; AT^SRTC ! ! ! ! AT+CCLK ; ! ! ! AT+CALA ; ! ! ! AT^SBC ; ! ! ! AT^SBV ! ! ; ; AT^SCTM ; ! ! ! AT^SSYNC ; ! ! ! A/ ! ; ; ; ATS3 ; ; ! ! ATS4 ; ; ! ! ATS5 ; ; ! ! Hardware related Commands Miscellaneous Commands MC55_ATC_V04.00 Confidential / Released Page 453 of 475 3/17/06 20.4 Availability of AT Commands Depending on Operating Mode of ME ! ... Command not supported % ... Command supported Table 20.6: Availability of AT Commands Depending on Operating Mode of ME AT Command Normal Mode Charge AT&F % ! ! AT&V % ! ! AT&W % ! ! ATQ % ! ! ATV % ! ! ATX % ! ! ATZ % ! ! AT+CFUN % ! ! AT^SMSO % % % AT+GCAP % ! ! AT+CMEE % ! ! AT+CSCS % ! ! AT^SCFG % ! ! AT^SM20 % ! ! AT+CMER % ! ! AT+CIND % ! ! AT^SIND % ! ! AT+CEER % ! ! ATS18 % ! ! AT+CPAS % ! ! AT+WS46 % ! ! Configuration Commands Status Control Commands Serial Interface Control Commands AT\Q % ! ! AT&C % ! ! AT&D % ! ! AT&S % ! ! ATE % ! ! AT+ILRR % ! ! AT+IPR % ! ! AT+CMUX % ! ! % ! ! Security Commands AT+CPIN MC55_ATC_V04.00 Confidential / Released Page 454 of 475 3/17/06 AT Command Normal Mode Charge AT+CPIN2 % ! ! AT^SPIC % ! ! AT+CLCK % ! ! AT^SLCK % ! ! AT+CPWD % ! ! AT^SPWD % ! ! ATI % ! ! AT+CGMI % ! ! AT+GMI % ! ! AT+CGMM % ! ! AT+GMM % ! ! AT+CGMR % ! ! AT+GMR % ! ! AT+CGSN % ! ! AT+GSN % ! ! AT+CIMI % ! ! ATA % ! ! ATD % ! ! ATD><mem><n> % ! ! ATD><n> % ! ! ATD><str> % ! ! ATDI % ! ! ATDL % ! ! ATH % ! ! AT+CHUP % ! ! ATS0 % ! ! ATS6 % ! ! ATS7 % ! ! ATS8 % ! ! ATS10 % ! ! ATO % ! ! +++ % ! ! AT+CBST % ! ! AT+CRLP % ! ! AT+CLCC % ! ! AT^SLCC % ! ! AT+CR % ! ! AT+CRC % ! ! Identification Commands Call related Commands MC55_ATC_V04.00 Confidential / Released Page 455 of 475 3/17/06 AT Command Normal Mode Charge AT+CSNS % ! ! AT^SCNI % ! ! AT^SLCD % ! ! AT^STCD % ! ! ATP % ! ! ATT % ! ! AT+COPN % ! ! AT+COPS % ! ! AT^SOPS % ! ! AT+CREG % ! ! AT+CSQ % ! ! AT^SMONC % ! ! AT^SMOND % ! ! AT^MONI % ! ! AT^MONP % ! ! AT^SMONG % ! ! AT^SALS % ! ! AT^SHOM % ! ! AT^SPLM % ! ! AT+CPOL % ! ! AT^SPLR % ! ! AT^SPLW % ! ! Network Service Commands Supplementary Service Commands AT+CACM % ! ! AT^SACM % ! ! AT+CAMM % ! ! AT+CAOC % ! ! AT+CCUG % ! ! AT+CCFC % ! ! AT+CCWA % ! ! AT+CHLD % ! ! AT+CLIP % ! ! AT+CLIR % ! ! AT+COLP % ! ! AT+CPUC % ! ! AT+CSSN % ! ! AT+CUSD % ! ! % ! ! Internet Service Commands AT^SICS MC55_ATC_V04.00 Confidential / Released Page 456 of 475 3/17/06 AT Command Normal Mode Charge AT^SICI % ! ! AT^SISS % ! ! AT^SISI % ! ! AT^SISO % ! ! AT^SISC % ! ! AT^SISR % ! ! AT^SISW % ! ! AT^SISE % ! ! AT+CGACT % ! ! AT+CGANS % ! ! AT+CGATT % ! ! AT+CGAUTO % ! ! AT+CGEREP % ! ! AT+CGDATA % ! ! AT+CGDCONT % ! ! AT+CGPADDR % ! ! AT+CGQMIN % ! ! AT+CGQREQ % ! ! AT+CGREG % ! ! AT+CGSMS % ! ! AT^SGAUTH % ! ! AT^SGCONF % ! ! ATA % ! ! ATD*99# % ! ! ATD*98# % ! ! ATH % ! ! ATS0 % ! ! AT+FBADLIN % ! ! AT+FBADMUL % ! ! AT+FBOR % ! ! AT+FCIG % ! ! AT+FCLASS % ! ! AT+FCQ % ! ! AT+FCR % ! ! AT+FDCC % ! ! AT+FDFFC % ! ! AT+FDIS % ! ! AT+FDR % ! ! GPRS Commands FAX Commands MC55_ATC_V04.00 Confidential / Released Page 457 of 475 3/17/06 AT Command Normal Mode Charge AT+FDT % ! ! AT+FET % ! ! AT+FK % ! ! AT+FLID % ! ! AT+FMDL % ! ! AT+FMFR % ! ! AT+FOPT % ! ! AT+FPHCTO % ! ! AT+FREV % ! ! AT+FRH % ! ! AT+FRM % ! ! AT+FRS % ! ! AT+FTH % ! ! AT+FTM % ! ! AT+FTS % ! ! AT+FVRFC % ! ! Short Message Service (SMS) Commands AT+CMGC % ! ! AT+CMGD % ! ! AT+CMGF % ! ! AT+CMGL % ! ! AT+CMGR % ! ! AT+CMGS % ! ! AT+CMGW % ! ! AT+CMSS % ! ! AT+CNMA % ! ! AT+CNMI % ! ! AT+CPMS % ! ! AT+CSCA % ! ! AT+CSCB % ! ! AT+CSDH % ! ! AT+CSMP % ! ! AT+CSMS % ! ! AT^SLMS % ! ! AT^SMGL % ! ! AT^SMGO % ! ! AT^SMGR % ! ! AT^SSCONF % ! ! AT^SSDA % ! ! AT^SSMSS % ! ! MC55_ATC_V04.00 Confidential / Released Page 458 of 475 3/17/06 AT Command Normal Mode Charge AT+CRSM % ! ! AT^SXSM % ! ! AT^SCKS % ! ! AT^SCID % ! ! AT+CXXCID % ! ! SIM related Commands SIM Application Toolkit (SAT) Commands AT^SSTA % ! ! ^SSTN % ! ! AT^SSTGI % ! ! AT^SSTR % ! ! AT+CPBR % ! ! AT+CPBS % ! ! AT+CPBW % ! ! AT^SPBC % ! ! AT^SPBD % ! ! AT^SPBG % ! ! AT^SPBS % ! ! AT+CNUM % ! ! AT^SDLD % ! ! ATL % ! ! ATM % ! ! AT+CLVL % ! ! AT+CMUT % ! ! AT+VTD % ! ! AT+VTS % ! ! AT^SAIC % ! ! AT^SNFA % ! ! AT^SNFD % ! ! AT^SNFI % ! ! AT^SNFM % ! ! AT^SNFO % ! ! AT^SNFPT % ! ! AT^SNFS % ! ! AT^SNFTTY % ! ! AT^SNFV % ! ! AT^SNFW % ! ! Phonebook Commands Audio Commands MC55_ATC_V04.00 Confidential / Released Page 459 of 475 3/17/06 AT Command Normal Mode Charge % ! ! AT+CCLK % % % AT+CALA % % % AT^SBC % % § AT^SBV % % % AT^SCTM % % % AT^SSYNC % ! ! A/ % ! ! ATS3 % ! ! ATS4 % ! ! ATS5 % ! ! AT^SRTC Hardware related Commands Miscellaneous Commands MC55_ATC_V04.00 Confidential / Released Page 460 of 475 3/17/06 20.5 AT Command Settings storable with AT&W Table 20.7: Settings Stored to User Profile on ASC0 / MUX Channel 1 AT Command Stored Parameters Configuration Commands ATQ <n> ATV <value> ATX <value> AT+CMEE <errMode> Status Control Commands ATS18 <n> Serial Interface Control Commands AT\Q <n> AT&C <value> AT&D <value> AT&S <value> ATE <value> AT+ILRR <value> Call related Commands ATS0 <n> ATS6 <n> ATS7 <n> ATS8 <n> ATS10 <n> AT+CBST <speed>, <name>, <ce> AT+CRLP <iws>, <mws>, <T1>, <N2> AT^SLCC <n> AT+CR <mode> AT+CRC <mode> Network Service Commands AT+COPS <format> AT+CREG <n> Supplementary Service Commands AT^SACM <n> AT+CLIP <n> GPRS Commands ATS0 MC55_ATC_V04.00 Confidential / Released <n> Page 461 of 475 3/17/06 AT Command Stored Parameters FAX Commands AT+FCLASS <n> Short Message Service (SMS) Commands AT+CMGF <mode> AT+CNMI <mode>, <mt>, <bm>, <ds> AT+CSDH <show> AT+CSMS <service> AT^SMGO <n> SIM related Commands AT^SCKS <mode> Miscellaneous Commands ATS3 <n> ATS4 <n> ATS5 <n> Table 20.8: Settings Stored to User Profile on ASC1 / MUX Channels 2 and 3 AT Command Stored Parameters Configuration Commands ATQ <n> ATV <value> ATX <value> AT+CMEE <errMode> Serial Interface Control Commands AT\Q <n> AT&C <value> AT&D <value> AT&S <value> ATE <value> Call related Commands ATS0 <n> AT^SLCC <n> AT+CR <mode> AT+CRC <mode> Network Service Commands AT+COPS MC55_ATC_V04.00 Confidential / Released <format> Page 462 of 475 3/17/06 AT Command Stored Parameters AT+CREG <n> Supplementary Service Commands AT^SACM <n> AT+CLIP <n> GPRS Commands ATS0 <n> Short Message Service (SMS) Commands AT+CMGF <mode> AT+CNMI <mode>, <mt>, <bm>, <ds> AT+CSDH <show> AT+CSMS <service> AT^SMGO <n> SIM related Commands AT^SCKS <mode> Miscellaneous Commands ATS3 <n> ATS4 <n> ATS5 <n> MC55_ATC_V04.00 Confidential / Released Page 463 of 475 3/17/06 20.6 Factory Default Settings Restorable with AT&F Table 20.9: Factory Default Settings Restorable with AT&F AT Command Factory Defaults Configuration Commands ATQ <n>=0 ATV <value>=1 ATX <value>=4 AT+CFUN <fun>=1 AT+CMEE <errMode>=0 AT+CSCS <chset>="GSM" AT^SCFG <tcpIrt>="3", <tcpMr>="10", <tcpOt>="6000", <tcpWithUrc>="on" AT^SM20 <CallMode>=1, <CmgwMode>=1 Status Control Commands AT+CMER <mode>=0, <keyp>=0, <disp>=0, <ind>=0, <bfr>=0 AT+CIND <mode>=1 ATS18 <n>=0 Serial Interface Control Commands AT\Q <n>=0 AT&C <value>=1 AT&D <value>=2 AT&S <value>=0 ATE <value>=1 AT+ILRR <value>=0 Call related Commands ATS0 <n>=000 ATS6 <n>=000 ATS7 <n>=060 ATS8 <n>=0 ATS10 <n>=002 AT+CBST <speed>=7, <name>=0, <ce>=1 AT+CRLP <iws>=61, <mws>=61, <T1>=78, <N2>=6 AT^SLCC <n>=0 AT+CR <mode>=0 AT+CRC <mode>=0 Network Service Commands AT+COPS <format>=0 AT+CREG <n>=0 MC55_ATC_V04.00 Confidential / Released Page 464 of 475 3/17/06 AT Command Factory Defaults AT^SALS <view>=0, <line>=1 Supplementary Service Commands AT^SACM <n>=0 AT+CLIP <n>=0 AT+CSSN <n>=0, <m>=0 AT+CUSD <n>=0 GPRS Commands AT+CGAUTO <n>=3 AT+CGREG <n>=0 AT+CGSMS <service>=3 AT^SGAUTH <auth>=3 ATS0 <n>=000 FAX Commands AT+FCLASS <n>=0 Short Message Service (SMS) Commands AT+CMGF <mode>=0 AT+CNMI <mode>=0, <mt>=0, <bm>=0, <ds>=0, <bfr>=1 AT+CSCB <mode>=0 AT+CSDH <show>=0 AT+CSMP <fo>=17, <vp>=167, <dcs>=0, <pid>=0 AT+CSMS <service>=0 AT^SMGO <n>=0 AT^SSCONF <ra>=0 AT^SSDA <da>=0 AT^SSMSS <seq>=0 SIM related Commands AT^SCKS <mode>=0 Phonebook Commands AT+CPBS <storage>="SM" AT^SPBS <internal-counter>=0 Audio Commands AT+VTD <duration>=1 Hardware related Commands AT^SCTM MC55_ATC_V04.00 Confidential / Released <n>=0 Page 465 of 475 3/17/06 AT Command Factory Defaults Miscellaneous Commands ATS3 <n>=013 ATS4 <n>=010 ATS5 <n>=008 MC55_ATC_V04.00 Confidential / Released Page 466 of 475 3/17/06 20.7 Summary of Unsolicited Result Codes (URC) Table 20.10: Summary of Unsolicited Result Codes (URC) AT Command URC Configuration Commands AT+CFUN ^SYSSTART AT+CFUN ^SYSSTART CHARGE ONLY MODE AT^SMSO ^SHUTDOWN Status Control Commands AT+CMER +CIEV: <indDescr>, <indValue>1[, <indValue>2] AT^SIND +CIEV: <indDescr>, <indValue> AT^SIND +CIEV: <indDescr>, <indValue>, <vmCounter> AT^SIND +CIEV: <indDescr>, <indValue>, <eonsOperator>, <servProvider> AT^SIND +CIEV: <indDescr>, <nitzUT>, <nitzTZ>, <nitzDST> Call related Commands AT^SLCC if the list of current calls is empty: ^SLCC: if one or more calls are currently in the list: ^SLCC: <idx>, <dir>, <stat>, <mode>, <mpty>, <traffic channel assigned>[, <number>, <type>[, <alpha>]] [^SLCC: <idx>, <dir>, <stat>, <mode>, <mpty>, <traffic channel assigned>[, <number>, <type>[, <alpha>]]] [... ] ^SLCC: AT+CRC RING AT+CRC +CRING: <type> Network Service Commands AT+CREG +CREG: <stat> AT+CREG +CREG: <stat>[, <lac>, <ci>] AT^SALS ^SALS: <line> Supplementary Service Commands AT^SACM +CCCM: <ccm> AT+CCWA +CCWA: <calling number>, <type of number>, <class>, , <CLI validity> AT+CCWA ^SCWA AT+CLIP +CLIP: <number>, <type>, , [, <alpha>][, <CLI validity>] AT+CLIP +CLIP: <number>, <type> AT+COLP +COLP: <number>, <type> AT+CSSN +CSSI: <code 1> AT+CSSN +CSSU: <code 2> AT+CUSD +CUSD: <m>[<str_urc>[<dcs>]] MC55_ATC_V04.00 Confidential / Released Page 467 of 475 3/17/06 AT Command URC Internet Service Commands AT^SISR ^SISR: <srvProfileId>, <urcCauseId> AT^SISW ^SISW: <srvProfileId>, <urcCauseId> Internet Ser^SIS: <srvProfileId>, <urcCause>[, [<urcInfoId>][, <urcInfoText>]] vice URC "^SIS" GPRS Commands AT+CGEREP +CGEV: REJECT <PDP_type>, <PDP_addr> AT+CGEREP +CGEV: NW REACT <PDP_type>, <PDP_addr>, [<cid>] AT+CGEREP +CGEV: NW DEACT <PDP_type>, <PDP_addr>, [<cid>] AT+CGEREP +CGEV: ME DEACT <PDP_type>, <PDP_addr>, [<cid>] AT+CGEREP +CGEV: NW DETACH AT+CGEREP +CGEV: ME DETACH AT+CGEREP +CGEV: NW CLASS <class> AT+CGEREP +CGEV: ME CLASS <class> AT+CGREG +CGREG: <stat> Short Message Service (SMS) Commands AT+CNMI +CMTI: <mem3>, <index> AT+CNMI +CMT: <length><CR><LF><pdu> AT+CNMI +CMT: <oa>, <scts>[, <tooa>, <fo>, <pid>, <dcs>, <sca>, <tosca>, <length>]<CR><LF><data> AT+CNMI +CBM: <length><CR><LF><pdu> AT+CNMI +CBM: <sn>, <mid>, <dcs>, <page>, <pages><CR><LF><data> AT+CNMI +CDS: <length><CR><LF><pdu> AT+CNMI +CDS: <fo>, <mr>[, <ra>][, <tora>], <scts>, <dt>, <st> AT+CNMI +CDSI: <mem3>, <index> AT^SMGO ^SMGO: <mode> SIM related Commands AT^SCKS ^SCKS: <SimStatus> SIM Application Toolkit (SAT) Commands ^SSTN ^SSTN: <cmdType> ^SSTN ^SSTN: <cmdTerminateValue> ^SSTN ^SSTN: 254 ^SSTN ^SSTN: 255 Hardware related Commands AT+CALA +CALA: [<text>] AT+CALA ^SYSSTART ALARM MODE +CALA: <text> AT^SBC ^SBC: Undervoltage MC55_ATC_V04.00 Confidential / Released Page 468 of 475 3/17/06 AT Command URC AT^SCTM ^SCTM_A: <m> AT^SCTM ^SCTM_B: <m> MC55_ATC_V04.00 Confidential / Released Page 469 of 475 3/17/06 20.8 Alphabetical List of AT Commands Table 20.11: Alphabetical List of AT Commands AT Command Description Section and Page +++ Switch from data mode to command mode Section 7.17, page 144 ^SSTN SAT Notification Section 15.2, page 378 A/ Repeat previous command line Section 19.1, page 439 AT&C Set Data Carrier Detect (DCD) Line mode Section 4.2, page 86 AT&D Set circuit Data Terminal Ready (DTR) function mode Section 4.3, page 87 AT&F Set all current parameters to manufacturer defaults Section 2.1, page 29 AT&S Set circuit Data Set Ready (DSR) function mode Section 4.4, page 88 AT&V Display current configuration Section 2.2, page 30 AT&W Stores current configuration to user defined profile Section 2.3, page 32 AT+CACM Accumulated call meter (ACM) reset or query Section 9.1, page 191 AT+CALA Set alarm time Section 18.2, page 427 AT+CAMM Accumulated call meter maximum (ACMmax) set or query Section 9.3, page 194 AT+CAOC Advice of Charge information Section 9.4, page 195 AT+CBST Select bearer service type Section 7.18, page 145 AT+CCFC Call forwarding number and conditions control Section 9.6, page 198 AT+CCLK Real Time Clock Section 18.1, page 426 AT+CCUG Closed User Group Section 9.5, page 196 AT+CCWA Call Waiting Section 9.7, page 202 AT+CEER Extended Error Report Section 3.4, page 71 AT+CFUN Set phone functionality Section 2.8, page 37 AT+CGACT PDP context activate or deactivate Section 11.1, page 266 AT+CGANS Manual response to a network request for PDP context activation Section 11.2, page 268 AT+CGATT GPRS attach or detach Section 11.3, page 270 AT+CGAUTO Automatic response to a network request for PDP context activation Section 11.4, page 271 AT+CGDATA Enter data state Section 11.6, page 275 AT+CGDCONT Define PDP Context Section 11.7, page 277 AT+CGEREP GPRS event reporting Section 11.5, page 273 AT+CGMI Request manufacturer identification Section 6.2, page 121 AT+CGMM Request model identification Section 6.4, page 122 AT+CGMR Request revision identification of software status Section 6.6, page 123 AT+CGPADDR Show PDP address Section 11.8, page 279 AT+CGQMIN Quality of Service Profile (Minimum acceptable) Section 11.9, page 280 AT+CGQREQ Quality of Service Profile (Requested) Section 11.10, page 284 AT+CGREG GPRS Network Registration Status Section 11.11, page 288 AT+CGSMS Select service for MO SMS messages Section 11.12, page 290 AT+CGSN Request International Mobile Equipment Identity (IMEI) Section 6.8, page 124 AT+CHLD Call Hold and Multiparty Section 9.8, page 206 MC55_ATC_V04.00 Confidential / Released Page 470 of 475 3/17/06 AT Command Description Section and Page AT+CHUP Hang up call Section 7.10, page 137 AT+CIMI Request International Mobile Subscriber Identity (IMSI) Section 6.10, page 125 AT+CIND Indicator control Section 3.2, page 62 AT+CLCC List current calls of ME Section 7.20, page 147 AT+CLCK Facility lock Section 5.4, page 109 AT+CLIP Calling Line Identification Presentation Section 9.9, page 208 AT+CLIR Calling line identification restriction Section 9.10, page 210 AT+CLVL Loudspeaker volume level Section 17.4, page 403 AT+CMEE Mobile Equipment Error Message Format Section 2.11, page 44 AT+CMER Mobile Equipment Event Reporting Section 3.1, page 60 AT+CMGC Send an SMS command Section 13.2, page 335 AT+CMGD Delete short message Section 13.3, page 336 AT+CMGF Select SMS message format Section 13.4, page 337 AT+CMGL List SMS messages from preferred store Section 13.5, page 338 AT+CMGR Read SMS messages Section 13.6, page 340 AT+CMGS Send Short Message Section 13.7, page 342 AT+CMGW Write Short Messages to Memory Section 13.8, page 344 AT+CMSS Send short messages from storage Section 13.9, page 346 AT+CMUT Mute control Section 17.5, page 404 AT+CMUX Enter multiplex mode Section 4.8, page 95 AT+CNMA New Message Acknowledgement to ME/TE, only phase 2+ Section 13.10, page 347 AT+CNMI New short Message Indication Section 13.11, page 348 AT+CNUM Read own numbers Section 16.9, page 399 AT+COLP Connected Line Identification Presentation Section 9.11, page 211 AT+COPN Read operator names Section 8.1, page 162 AT+COPS Operator Selection Section 8.2, page 163 AT+CPAS Mobile equipment activity status Section 3.6, page 83 AT+CPBR Read from Phonebook Section 16.2, page 382 AT+CPBS Select phonebook memory storage Section 16.3, page 385 AT+CPBW Write into Phonebook Section 16.4, page 387 AT+CPIN PIN Authentication Section 5.1, page 99 AT+CPIN2 PIN2 Authentication Section 5.2, page 103 AT+CPMS Preferred SMS message storage Section 13.12, page 351 AT+CPOL Preferred Operator List Section 8.14, page 188 AT+CPUC Price per unit and currency table Section 9.12, page 213 AT+CPWD Change Password Section 5.6, page 115 AT+CR Service reporting control Section 7.22, page 155 AT+CRC Set Cellular Result Codes for incoming call indication Section 7.23, page 156 AT+CREG Network registration Section 8.4, page 168 AT+CRLP Select radio link protocol parameters for originated nontransparent data calls Section 7.19, page 146 MC55_ATC_V04.00 Confidential / Released Page 471 of 475 3/17/06 AT Command Description Section and Page AT+CRSM Restricted SIM Access Section 14.1, page 368 AT+CSCA SMS Service Center Address Section 13.13, page 353 AT+CSCB Select Cell Broadcast Message Indication Section 13.14, page 354 AT+CSCS Select TE character set Section 2.12, page 49 AT+CSDH Show SMS text mode parameters Section 13.15, page 355 AT+CSMP Set SMS text Mode Parameters Section 13.16, page 356 AT+CSMS Select Message Service Section 13.17, page 358 AT+CSNS Single Numbering Scheme Section 7.24, page 157 AT+CSQ Signal quality Section 8.5, page 171 AT+CSSN Supplementary service notifications Section 9.13, page 215 AT+CUSD Supplementary service notifications Section 9.14, page 217 AT+CXXCID Display card ID Section 14.5, page 375 AT+FBADLIN Bad Line Threshold Section 12.2, page 304 AT+FBADMUL Error Threshold Multiplier Section 12.3, page 305 AT+FBOR Query data Bit Order Section 12.4, page 306 AT+FCIG Query or set the Local Polling ID Section 12.5, page 307 AT+FCLASS Fax: Select, read or test service class Section 12.6, page 308 AT+FCQ Copy Quality Checking Section 12.7, page 309 AT+FCR Capability to Receive Section 12.8, page 310 AT+FDCC Query or set capabilities Section 12.9, page 311 AT+FDFFC Data Compression Format Conversion Section 12.10, page 312 AT+FDIS Query or set session parameters Section 12.11, page 313 AT+FDR Begin or continue phase C Data Reception Section 12.12, page 314 AT+FDT Data Transmission Section 12.13, page 315 AT+FET End a page or document Section 12.14, page 316 AT+FK Kill operation, orderly FAX abort Section 12.15, page 317 AT+FLID Query or set the Local Id setting capabilities Section 12.16, page 318 AT+FMDL Identify Product Model Section 12.17, page 319 AT+FMFR Request Manufacturer Identification Section 12.18, page 320 AT+FOPT Set bit Order independently Section 12.19, page 321 AT+FPHCTO DTE Phase C Response Timeout Section 12.20, page 322 AT+FREV Identify Product Revision Section 12.21, page 323 AT+FRH Receive Data Using HDLC Framing Section 12.22, page 324 AT+FRM Receive Data Section 12.23, page 325 AT+FRS Receive Silence Section 12.24, page 326 AT+FTH Transmit Data Using HDLC Framing Section 12.25, page 327 AT+FTM Transmit Data Section 12.26, page 328 AT+FTS Stop Transmission and Wait Section 12.27, page 329 AT+FVRFC Vertical Resolution Format Conversion Section 12.28, page 330 AT+GCAP Request complete TA capabilities list Section 2.10, page 43 AT+GMI Request manufacturer identification Section 6.3, page 121 AT+GMM Request model identification Section 6.5, page 122 MC55_ATC_V04.00 Confidential / Released Page 472 of 475 3/17/06 AT Command Description Section and Page AT+GMR Request revision identification of software status Section 6.7, page 123 AT+GSN Request International Mobile Equipment Identity (IMEI) Section 6.9, page 124 AT+ILRR Set TE-TA local rate reporting Section 4.6, page 90 AT+IPR Set fixed local rate Section 4.7, page 92 AT+VTD Tone duration Section 17.6, page 405 AT+VTS DTMF and tone generation Section 17.7, page 406 AT+WS46 Select wireless network Section 3.7, page 84 AT\Q Flow control Section 4.1, page 85 AT^MONI Monitor idle mode and dedicated mode Section 8.8, page 177 AT^MONP Monitor neighbour cells Section 8.9, page 180 AT^SACM Advice of charge and query of ACM and ACMmax Section 9.2, page 192 AT^SAIC Audio Interface Configuration Section 17.8, page 407 AT^SALS Alternate Line Service Section 8.11, page 184 AT^SBC Battery Charge Control Section 18.3, page 430 AT^SBV Battery/Supply Voltage Section 18.4, page 433 AT^SCFG Extended Configuration Settings Section 2.13, page 50 AT^SCID Display SIM card identification number Section 14.4, page 374 AT^SCKS Query SIM and Chip Card Holder Status Section 14.3, page 372 AT^SCNI List Call Number Information Section 7.25, page 158 AT^SCTM Set critical operating temperature presentation mode or query temperature Section 18.5, page 434 AT^SDLD Delete the 'last number redial' memory Section 16.10, page 400 AT^SGAUTH Set type of authentication for PPP connection Section 11.13, page 291 AT^SGCONF Configuration of GPRS related Parameters Section 11.14, page 292 AT^SHOM Display Homezone Section 8.12, page 186 AT^SICI Internet Connection Information Section 10.2, page 226 AT^SICS Internet Connection Setup Profile Section 10.1, page 222 AT^SIND Extended Indicator Control Section 3.3, page 65 AT^SISC Internet Service Close Section 10.6, page 244 AT^SISE Internet Service Error Report Section 10.9, page 251 AT^SISI Internet Service Information Section 10.4, page 237 AT^SISO Internet Service Open Section 10.5, page 239 AT^SISR Internet Service Read Data Section 10.7, page 245 AT^SISS Internet Service Setup Profile Section 10.3, page 228 AT^SISW Internet Service Write Data Section 10.8, page 248 AT^SLCC Siemens defined command to list current calls of ME Section 7.21, page 149 AT^SLCD Display Last Call Duration Section 7.26, page 159 AT^SLCK Facility lock Section 5.5, page 114 AT^SLMS List SMS Memory Storage Section 13.18, page 360 AT^SM20 Set M20 compatibility mode Section 2.14, page 59 AT^SMGL List Short Messages from preferred store without setting status to REC READ Section 13.19, page 361 MC55_ATC_V04.00 Confidential / Released Page 473 of 475 3/17/06 AT Command Description Section and Page AT^SMGO Set or query SMS overflow presentation mode or query SMS overflow Section 13.20, page 362 AT^SMGR Read short message without setting status to REC READ Section 13.21, page 364 AT^SMONC Cell Monitoring Section 8.6, page 172 AT^SMOND Cell Monitoring Section 8.7, page 174 AT^SMONG GPRS Monitor Section 8.10, page 182 AT^SMSO Switch off mobile station Section 2.9, page 42 AT^SNFA Set or query of microphone attenuation Section 17.9, page 409 AT^SNFD Set audio parameters to manufacturer default values Section 17.10, page 411 AT^SNFI Set microphone path parameters Section 17.11, page 412 AT^SNFM Set microphone audio path and power supply Section 17.12, page 413 AT^SNFO Set audio output (= loudspeaker path) parameter Section 17.13, page 415 AT^SNFPT Set progress tones Section 17.14, page 417 AT^SNFS Select audio hardware set Section 17.15, page 418 AT^SNFTTY Signal TTY/CTM audio mode capability Section 17.16, page 421 AT^SNFV Set loudspeaker volume Section 17.17, page 422 AT^SNFW Write audio setting in non-volatile store Section 17.18, page 423 AT^SOPS Extended Operator Selection Section 8.3, page 166 AT^SPBC Find first matching entry in sorted phonebook Section 16.5, page 390 AT^SPBD Purge phonebook memory storage Section 16.6, page 391 AT^SPBG Display phonebook entries in alphabetical order Section 16.7, page 392 AT^SPBS Step through the selected phonebook alphabetically Section 16.8, page 395 AT^SPIC Display PIN counter Section 5.3, page 105 AT^SPLM Read the PLMN list Section 8.13, page 187 AT^SPLR Read entry from the preferred operators list Section 8.15, page 189 AT^SPLW Write an entry to the preferred operators list Section 8.16, page 190 AT^SPWD Change Password Section 5.7, page 119 AT^SRTC Ring tone configuration Section 17.19, page 424 AT^SSCONF SMS Command Configuration Section 13.22, page 365 AT^SSDA Set SMS Display Availability Section 13.23, page 366 AT^SSMSS Set Short Message Storage Sequence Section 13.24, page 367 AT^SSTA SAT Interface Activation Section 15.1, page 376 AT^SSTGI SAT Get Information Section 15.3, page 379 AT^SSTR SAT Response Section 15.4, page 380 AT^SSYNC Configure SYNC Pin Section 18.6, page 437 AT^STCD Display Total Call Duration Section 7.27, page 160 AT^SXSM Extended SIM Access Section 14.2, page 370 ATA Answer a call Section 7.2, page 127 ATA Manual response to a network request for PDP context activation Section 11.15, page 293 ATD Mobile originated call to specified number Section 7.3, page 128 ATD*98# Request GPRS IP service Section 11.17, page 295 MC55_ATC_V04.00 Confidential / Released Page 474 of 475 3/17/06 AT Command Description Section and Page ATD*99# Request GPRS service Section 11.16, page 294 ATD><mem><n> Mobile originated call using specific memory and index number Section 7.4, page 130 ATD><n> Mobile originated call from active memory using index number Section 7.5, page 132 ATD><str> Mobile originated call from active memory using corresponding field Section 7.6, page 133 ATDI Mobile originated call to ISDN number Section 7.7, page 134 ATDL Redial last number used Section 7.8, page 135 ATE Enable command echo Section 4.5, page 89 ATH Disconnect existing connection Section 7.9, page 136 ATH Manual rejection of a network request for PDP context activation Section 11.18, page 296 ATI Display product identification information Section 6.1, page 120 ATL Set monitor speaker loudness Section 17.2, page 402 ATM Set monitor speaker mode Section 17.3, page 402 ATO Switch from command mode to data mode / PPP online mode Section 7.16, page 143 ATP Select pulse dialing Section 7.28, page 161 ATQ Set result code presentation mode Section 2.4, page 33 ATS0 Set number of rings before automatically answering a call Section 7.11, page 138 ATS0 Automatic response to a network request for PDP context activation Section 11.19, page 297 ATS10 Set disconnect delay after indicating the absence of data carrier Section 7.15, page 142 ATS18 Extended call release report Section 3.5, page 81 ATS3 Set command line termination character Section 19.2, page 440 ATS4 Set response formatting character Section 19.3, page 441 ATS5 Write command line editing character Section 19.4, page 442 ATS6 Set pause before blind dialing Section 7.12, page 139 ATS7 Set number of seconds to wait for connection completion Section 7.13, page 140 ATS8 Set number of seconds to wait for comma dialing modifier Section 7.14, page 141 ATT Select tone dialing Section 7.29, page 161 ATV Set result code format mode Section 2.5, page 34 ATX Set CONNECT result code format and call monitoring Section 2.6, page 35 ATZ Set all current parameters to user defined profile Section 2.7, page 36 MC55_ATC_V04.00 Confidential / Released Page 475 of 475 3/17/06
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
Download
PDF
advertisement