GC75 at Commands R2A

GC75

Sony Ericsson GPRS PC Card Modem GC75

AT-Commands Manual

EN/LZT 123 928 R2A

2

Contents

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Alphabet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8DTE command lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Command line general format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Command line editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Command line echo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Types of TE Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9TE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Basic Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Extended commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Action Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Parameter Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Concatenating commands after extended syntax commands . . . . . . . . 15Concatenating commands after basic format commands . . . . . . . . . . . 16Issuing commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Executing commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16TA responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17In-band Escape mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Control and Identification Commands . . . . . . . . . . . . . . . . . . . . . . . . . 22Z - Reset to Factory Defined Configuration . . . . . . . . . . . . . . . . . . . . . 22&F - Reset to Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 23I - Request HW Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23+CGMI (+GMI) - Request Manufacturer Identification . . . . . . . . . . . 24+CGMM (+GMM) - Request Model Id . . . . . . . . . . . . . . . . . . . . . . . . 25+CGMR (+GMR) - Request Revision Id . . . . . . . . . . . . . . . . . . . . . . . 26+CLAC - List All Available AT Commands. . . . . . . . . . . . . . . . . . . . 26* - List All AT Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27+GCAP - Request Modem Capability List. . . . . . . . . . . . . . . . . . . . . . 27+WS46 - select wireless network (PCCA STD-101) . . . . . . . . . . . . . . 28

Call Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29A - Answer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29H - Hang up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30D - Dial (non GPRS calls) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30<Dial-string> Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31MT originated PDP context activation . . . . . . . . . . . . . . . . . . . . . . . . . 32D*99* - Request GPRS service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32D*98* - Request GPRS IP service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Network requested PDP context activation . . . . . . . . . . . . . . . . . . . . . 35S0 - Automatic response to a network request for PDP context activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35A - Manual acceptance of a network request for PDP context activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35H - Manual rejection of a network request for PDP context activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

L - Monitor Speaker Loudness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36+CFUN - Set Phone Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37RING - Ring Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38O - Return to On-line Data Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38P - Select Pulse Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39T - Select Tone Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39+CAOC - Advice of Charge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40+CACM - Accumulated Call Meter . . . . . . . . . . . . . . . . . . . . . . . . . . . 41+CAMM - Accumulated Call Meter Maximum. . . . . . . . . . . . . . . . . . 42+CPUC - Price per unit and currency. . . . . . . . . . . . . . . . . . . . . . . . . . 43+CCWE - Call Meter Maximum Event . . . . . . . . . . . . . . . . . . . . . . . . 44+CPWC - Power class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45+CPAS - Phone Activity Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46+CSTA - Select Type of Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Interface Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48+++AT - Escape Sequence Character. . . . . . . . . . . . . . . . . . . . . . . . . . 48S3 - Command Line Termination Character . . . . . . . . . . . . . . . . . . . . 48S4 - Response Formatting Character . . . . . . . . . . . . . . . . . . . . . . . . . . 49S5 - Command Line Editing Character . . . . . . . . . . . . . . . . . . . . . . . . 50E - Command Echo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Q - Result Code Suppression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51V - TA Response Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51&C - Circuit 109 (DCD) Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52&D - Circuit 108 (DTR) Response. . . . . . . . . . . . . . . . . . . . . . . . . . . . 53+IFC - TE-TA Local Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . 54S0 - Automatic Answer Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55S6 - Blind Dial Delay Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56S7 - Connection Completion Timeout . . . . . . . . . . . . . . . . . . . . . . . . . 56S10 - Automatic Disconnect Delay Control . . . . . . . . . . . . . . . . . . . . . 57M - Monitor Speaker Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57X - Call Progress Monitoring Control . . . . . . . . . . . . . . . . . . . . . . . . . 58+ILRR - TE-TA Local , 4Rate Reporting . . . . . . . . . . . . . . . . . . . . . . 59

Error Control (LAPM/MNP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60+ES - Error Control Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60+ETBM - Call Termination Buffer Management. . . . . . . . . . . . . . . . . 61+ER - Error Control Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Data Compression (V24bis/MNP5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63+DS - Data Compression Mode Selection . . . . . . . . . . . . . . . . . . . . . . 63+DR - Data Compression Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Fax Class 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65+FCLASS - Select Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65+FBO - Phase C Bit Order Parameter . . . . . . . . . . . . . . . . . . . . . . . . . 66+FCQ - Copy Quality Checking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67+FCC - TA Capability Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67+FCS - Current Session Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69+FDR - Fax Data Receive Command. . . . . . . . . . . . . . . . . . . . . . . . . . 70+FDT - Fax Data Transmission Command . . . . . . . . . . . . . . . . . . . . . 71

3

4

+FEA - Phase C received EOL alignment . . . . . . . . . . . . . . . . . . . . . . 72+FET - Page Punctuation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72+FIE - Procedure interrupt enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73+FIP - Initialise Fax Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74+FIS - Current Session Negotiation Parameter . . . . . . . . . . . . . . . . . . 75+FIT - Inactivity timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75+FKS - Session Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76+FLI - Local ID String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77+FPI - Local Polling ID String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78+FLP - Indicated Document to Poll . . . . . . . . . . . . . . . . . . . . . . . . . . . 78+FNR - Negotiation reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79+FPP - Packet protocol control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80+FPS - Page Transfer Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81+FSP - Request to Poll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82+FIS: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82+FTC: Report DTC frame information . . . . . . . . . . . . . . . . . . . . . . . . 82+FHR: - Report received HDLC frames. . . . . . . . . . . . . . . . . . . . . . . . 83+FHS - Call termination status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83+FCI: - Called station id (CSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84+FCS: - Report DCS frame information. . . . . . . . . . . . . . . . . . . . . . . . 84+FTI: - Remote station id (TSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84+FPI: - Report Remote id, CIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85+FPS: - Page status report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85+FPO: - Remote polling indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 85+FNC: - Report non-standard command frame . . . . . . . . . . . . . . . . . . 86+FNF: - Non standard facilities report . . . . . . . . . . . . . . . . . . . . . . . . . 86+FNS: - Non standard setup report. . . . . . . . . . . . . . . . . . . . . . . . . . . . 86+FET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86+FCO: - indicates connection with a fax terminal . . . . . . . . . . . . . . . . 87+FDM: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87+FHT: - Report transmit HDLC frames . . . . . . . . . . . . . . . . . . . . . . . . 88

GSM 07.10 Multiplexor Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89+CMUX - Multiplexing Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

GSM TE-TA Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91+CSCS - Select TE Character Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

GSM Call Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92+CRC - Cellular Result Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92+CR - Service Reporting control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

GSM Data/Fax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94+CBST - Select bearer service type . . . . . . . . . . . . . . . . . . . . . . . . . . . 94+CRLP - Radio link protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

GSM Network Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97+CNUM - Subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97*EBSE - Band Selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98+CREG - Network Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99+COPS - Operator Selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

+CLIP - Calling Line Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . 102+CLIR - Calling Line Identification. . . . . . . . . . . . . . . . . . . . . . . . . . . 103+COLP - Connected Line Identification . . . . . . . . . . . . . . . . . . . . . . . 104+CCFC - Call Forwarding Number and Conditions. . . . . . . . . . . . . . . 105+CSSN - Supplementary service notifications . . . . . . . . . . . . . . . . . . . 107

GSM Facility Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110+CLCK - Facility lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110+CPWD - Change password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

GSM Mobile Equipment Control and Status . . . . . . . . . . . . . . . . . . . . 113+CPIN - Enter PIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113+CGSN - Request product serial number identification. . . . . . . . . . . . 114+CSQ - Signal quality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

GSM Mobile Equipment Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116+CEER - GSM Extended Error Reporting . . . . . . . . . . . . . . . . . . . . . . 116+CMEE - Report Mobile Equipment Error . . . . . . . . . . . . . . . . . . . . . 117

SMS General Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118+CSMS - Select Message Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122+CPMS - Preferred Message Storage . . . . . . . . . . . . . . . . . . . . . . . . . . 123+CMGF - Message Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124+CSCA - Service Center Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124+CSCB Select Cell Broadcast Message Types. . . . . . . . . . . . . . . . . . 125+CNMI - New Message Indications to TE. . . . . . . . . . . . . . . . . . . . . . 126 +CMGD - Delete Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

SMS Text mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132+CSMP - Set Text Mode Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 132+CSDH - Show Text Mode Parameters . . . . . . . . . . . . . . . . . . . . . . . . 133+CNMI - New Message Indications to TE. . . . . . . . . . . . . . . . . . . . . . 133+CMGL - List Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134+CMGR - Read Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135+CNMA - New Message Acknowledgement to ME/TA . . . . . . . . . . . 136+CMGS - Send Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 +CMSS - Send Message from Storage . . . . . . . . . . . . . . . . . . . . . . . . 138+CMGW - Write Message to Memory. . . . . . . . . . . . . . . . . . . . . . . . . 139+CMGC - Send Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139+CMMS - More Messages to Send . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

SMS PDU mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141+CNMI - New Message Indications to TE. . . . . . . . . . . . . . . . . . . . . . 141+CMGL - List Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141+CMGR - Read Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142+CMGS - Send Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142+CMGW - Write Message to Memory. . . . . . . . . . . . . . . . . . . . . . . . . 143+CMGC - Send Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144+CNMA - New Message Acknowledgement to ME/TA . . . . . . . . . . . 144+CMSS - Send Message from Storage . . . . . . . . . . . . . . . . . . . . . . . . . 145

5

6

GSM Phonebook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147+CPBS - Select phone book memory . . . . . . . . . . . . . . . . . . . . . . . . . . 147+CPOL Preferred operator list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148+CIMI - Request IMSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149+CPBR - Read phone book entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . 149+CPBF - Find phonebook entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150+CPBW - Write phonebook entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151+CRSM - Restricted SIM access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Phone Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154+COPN - Read operator names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154+CMEC - Mobile Equipment control mode . . . . . . . . . . . . . . . . . . . . . 154+CMER - Mobile Equipment Event Reporting . . . . . . . . . . . . . . . . . . 155+CMAR - Master Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

HSCSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158+CHSD - HSCSD device parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 158+CHST - HSCSD transparent call configuration . . . . . . . . . . . . . . . . 159+CHSN - HSCSD non-transparent call configuration . . . . . . . . . . . . . 159+CHSC HSCSD current call parameters . . . . . . . . . . . . . . . . . . . . . . . 160+CHSR - HSCSD parameters report . . . . . . . . . . . . . . . . . . . . . . . . . . 161

GPRS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162+CGDCONT - Define PDP Context . . . . . . . . . . . . . . . . . . . . . . . . . . 162+CGQREQ - Quality of Service Profile (Requested). . . . . . . . . . . . . . 164+CGQMIN - Quality of Service Profile (Minimum acceptable) . . . . . 165+CGATT - GPRS attach or detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166+CGACT - PDP context activate or deactivate . . . . . . . . . . . . . . . . . . 167+CGDATA - Enter data state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168+CGPADDR - Show PDP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169+CGEREP - GPRS event reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . 170+CGREG - GPRS network registration status . . . . . . . . . . . . . . . . . . . 172+CGSMS - Select service for MO SMS messages. . . . . . . . . . . . . . . . 173

SATK 2.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Display Text (Module -> PDA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174GET INKEY (Module -> PDA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174GET INPUT (Module -> PDA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175MENU SELECTION (Module <- PDA) . . . . . . . . . . . . . . . . . . . . . . . 176PLAY TONE (Module -> PDA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176REFRESH (Module -> PDA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177SELECT ITEM (Module -> PDA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177SEND SHORT MESSAGE (Module -> PDA) . . . . . . . . . . . . . . . . . . 178SEND SS (Module -> PDA). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178SEND USSD (Module -> PDA) (Class 3 Feature). . . . . . . . . . . . . . . . 179SET UP CALL (Module -> PDA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179SET UP MENU (Module -> PDA). . . . . . . . . . . . . . . . . . . . . . . . . . . . 181TERMINAL RESPONSE (PDA->Module) . . . . . . . . . . . . . . . . . . . . . 181Polling Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Provide Local Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Sony Ericsson Specific Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184*ECAM - Sony Ericsson Call Monitoring . . . . . . . . . . . . . . . . . . . . . . 184*ESIMC - SIM Insert/Removal indication. . . . . . . . . . . . . . . . . . . . . . 186*EPRO . Sony Ericsson get provider name . . . . . . . . . . . . . . . . . . . . . 186*ECIPC - Enable/Disable Ciphering Command . . . . . . . . . . . . . . . . . 187*EPNR - Sony Ericsson Read SIM Preferred Network . . . . . . . . . . . . 187*EPNW - Sony Ericsson Write SIM Preferred Network . . . . . . . . . . . 188

Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189+CME ERROR: <err> - Mobile Equipment error result code . . . . . . . 189+CMS ERROR . Message Failure Result Code . . . . . . . . . . . . . . . . . . 191

References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

7

8

General

This chapter specifies concepts and definitions that are common to both ITU-T V.25ter [28] and ITU-T V.250 [29] recommendations (V.250 supersedes V.25ter), extended with Sony Ericsson specific implementations.

Alphabet

The ITU-T T.50 [27] International Alphabet 5, hereinafter cited as “IA5”, is used in this specification. Only the low-order seven bits of each character are significant to the TA; any eighth or higher-order bit(s), if present, are ignored for the purpose of identifying commands and parameters. Lower-case characters (IA5 values from 6/1 to 7/10) are considered identical to their up-per-case equivalents (IA5 values from 4/1 to 5/10) when received by the TA from the TE. Result codes from the TA, which are defined in this Recommendation, shall be in upper case.

DTE command lines

In the descriptions that follow, words enclosed in <angle brackets> are references to syntactical elements defined in this Specification. When they appear in a command line, the brackets are not used. Words enclosed in [square brackets] represent optional items; such items may be omitted from the command line at the point where they are specified, and when they appear the square brackets are not included in the command line. Other characters that appear in syntax descriptions shall appear in the places shown.

In the following sub-clauses regarding TE commands, references are made to responses issued by the TA, which are defined in “TA responses”, page 17. In order to provide a clearer presentation, TA responses are mentioned in terms of their alphabetic format; the actual response issued will depend on the setting of parameters that affect response formats (e.g. Q and V commands).

Command line general format

A command line is made up of three elements: the prefix, the body, and the termination character.

The command line prefix consists of the characters “AT” (IA5 4/1, 5/4) or “at” (IA5 6/1, 7/4).

The body is made up of individual commands as specified later in this Recommendation. Space characters (IA5 2/0) are ignored and may be used freely for formatting purposes, unless they are embedded in numeric or string constants, see “Numeric constants”, page 12 or “String constants”, page 12. The termination character may not appear in the body. The TA shall be capable of accepting at least 40 characters in the body.

General

The termination character may be selected by a user option (parameter S3), the default being CR (IA5 0/13).

Command line editing

The character defined by parameter S5 (default, BS [IA5 0/8]) shall be interpreted as a request from the TE to the TA to delete the previous character. Any control characters (IA5 0/0 through 1/15, inclusive) that remain in the command line after receipt of the termination character shall be ignored by the TA.

The TA checks characters from the TE, first to see if they match the termination character (S3), then the editing character (S5), before checking for other characters. This insures that these characters will be properly recognized even if they are set to values that the TA uses for other purposes. If S3 and S5 are set to the same value, a matching character will be treated as matching S3 (S3 is checked before S5).

Command line echo

The TA may echo characters received from the TE during command state and online command state back to the TE, depending on the setting of the E command. If so enabled, characters received from the TE are echoed at the same rate, parity, and format as received.

Types of TE Commands

There are two types of commands: action commands and parameter commands. Action commands may be “executed” (to invoke a particular function of the equipment, which generally involves more than the simple storage of a value for later use), or “tested” (to determine whether or not the equipment implements the action command, and, if sub-parameters are associated with the action, the ranges of sub-parameter values that are supported). Parameters may be “set” (to store a value or values for later use), “read” (to determine the current value or values stored), or “tested” (to determine whether or not the equipment implements the parameter, and the ranges of values supported).

TE Command

“Basic Command”, page 10 defines Basic Syntax TE commands, which are implemented in common TA. This specification also defines Extended Syntax TE commands in “Extended commands”, page 11. Commands of either type may be included in command lines, in any order.

General 9

1

Basic Command

Basic Command Format

The format of Basic Syntax commands, except for the D and S commands, is as follows:

• <cmd>[...<number >]

• <cmd>[=][<number>]

where <cmd> is either a single character, or the “&” character (IA5 2/6) followed by a single character. Characters used in <cmd> shall be taken from the set of alphabetic characters.

<number> may be a string of one or more characters from “0” through “9” representing a decimal integer value. Commands that expect a <number> are noted in the description of the command. If a command expects <number> and it is missing (<cmd> is immediately followed in the command line by another <cmd> or the termination character), the value “0” is assumed. If a command does not expect a <number> and a number is present, an ERROR is generated. All leading “0”s in <number> are ignored by the TA. Additional commands may follow a command (and associated parameter, if any) on the same command line without any character required for separation. The actions of some commands cause the remainder of the command line to be ignored (e.g. A).

See the D command “D - Dial (non GPRS calls)”, page 30 for details on the format of the information that follows it.

S-parameters

Commands that begin with the letter “S” constitute a special group of parameters known as “S-parameters”. These differ from other commands in important respects. The number following the “S” indicates the “parameter number” being referenced. If the number is not recognized as a valid parameter number, an ERROR result code is issued.

Immediately following this number, either a “?” or “=” character (IA5 3/15 or 3/13, respectively) shall appear. “?” is used to read the current value of the indicated S-parameter; “=” is used to set the S-parameter to a new value.

• S<parameter_number>?

• S<parameter_number>=[<value>]

If the “=” is used, the new value to be stored in the S-parameter is specified in decimal following the “=”. If no value is given (i.e. the end of the command line occurs or the next command follows immediately), the S-parameter specified may be set to 0, or an ERROR result code issued and the.stored value left unchanged. The ranges of acceptable values are given in the description of each S-parameter.

If the “?” is used, the TA transmits a single line of information text to the TE.

0 General

For S-parameters defined in this specification, the text portion of this information text consists of exactly three characters, giving the value of the S-parameter in decimal, with leading zeroes included.

Extended commands

Command naming rules

Both actions and parameters have names, which are used in the related commands. Names always begin with the character “+” (IA5 2/15). Following the “+”, from one to sixteen (16) additional characters appear in the command name. These characters shall be selected from the following set:

• A through Z (IA5 4/1 through 5/10)

• 0 through 9 (IA5 3/0 through 3/9)

• ! (IA5 2/1)

• % (IA5 2/5)

• - (IA5 2/13)

• . (IA5 2/14)

• / (IA5 2/15)

• : (IA5 3/10)

• _ (IA5 5/15)

• *E (IA5 2/10 and 4/5)

The first character following the “+” shall be an alphabetic character in the range of “A” through “Z”. This first character generally implies the application in which a command is used or the standards committee that defined it (e.g. command names beginning with “F” are generally associated with facsimile-related standards, promulgated by Study Group 8). See Appendix I for information on first command characters reserved for use by particular standards committees. All other +leadin character sequences are reserved for future standardization by the ITU-T. The command interpreter in the Data Circuit-terminating Equipment (TA) considers lower-case characters to be the same as their upper-case equivalents; therefore, command names defined in standards referencing this Recommendation that include alphabetic characters should be defined using only the upper-case characters.

Standards that reference this Recommendation may choose to establish internal naming conventions that permit implicit recognition of a name as an action or as a parameter. For example, the standard could choose to end all action names with an exclamation point (“!”), or all parameter names with a percent sign (“%”). This Recommendation imposes no such conventions, however.

General 11

1

Sony Ericsson Specific Command

Both actions and parameters have names, which are used in the related commands. Names always begin with the two characters “*E” (IA5 2/10 and 4/5). Following the “*E”, from one to fifteen (15) additional characters shall appear in the command name.

Values

When sub-parameters are associated with the execution of an action, or when setting a parameter, the command may include specification of values. This is indicated by the appearance of <value> in the descriptions below.

<value> shall consist of either a numeric constant or a string constant.

Numeric constants

Numeric constants are expressed in decimal, hexadecimal, or binary.

Decimal numeric constants shall consist of a sequence of one or more of the characters “0” (IA5 3/0) through “9” (IA5 3/9), inclusive.

Hexadecimal numeric constants shall consist of a sequence of one or more of the characters “0” (IA5 3/0) through “9” (IA5 3/h), inclusive, and “A” (IA5 4/1) through “F” (IA5 4/6) inclusive. The characters “A” through “F” represent the equivalent decimal values 10 through 15.

Binary numeric constants shall consist of a sequence of one or more of the characters “0” (IA5 3/0) and “1” (IA5 3/1).

In all numeric constants, the most significant digit is specified first. Leading “0” characters shall be ignored by the TA. No spaces, hyphens, periods, commas, parentheses, or other generally-accepted numeric formatting characters are permitted in numeric constants.

Note! No “H” suffix is appended to the end of hexadecimal constants.

String constants

String constants shall consist of a sequence of displayable IA5 characters, each in the range from 2/0 to 7/15, inclusive, except for the characters “““ (IA5 2/2) and “\” (IA5 5/12). String constants shall be bounded at the beginning and end by the double-quote character (“““, IA5 2/2).

A “null” string constant, or a string constant of zero length, is represented by two adjacent delimiters (“”).

2 General

Compound values

Actions may have more than one sub-parameter associated with them, and parameters may have more than one value. These are known as “compound values”, and their treatment is the same in both actions and parameters.

A compound value consists of any combination of numeric and string values (as defined in the description of the action or parameter). The comma character (IA5 2/12) shall be included as a separator, before the second and all subsequent values in the compound value. If a value is not specified (i.e. defaults assumed), the required comma separator shall be specified; however, trailing comma characters may be omitted if all associated values are also omitted.

Action Command

Action execution command

There are two general types of action commands: those that have associated sub-parameter values that affect only that invocation of the command, and those that have no sub-parameters. If sub-parameters are associated with a command, the definition of the action command shall indicate, for each sub-parameter, whether the specification of a value for that sub-parameter is mandatory or optional. For optional sub-parameters, the definition shall indicate the assumed (default) value for the sub-parameter if no value is specified for that sub-parameter; the assumed value may be either a previous value (i.e. the value of an omitted sub-parameter remains the same as the previous invocation of the same command, or is determined by a separate parameter or other mechanism), or a fixed value (e.g. the value of an omitted sub-parameter is assumed to be zero).

Generally, the default value for numeric sub-parameters is 0, and the default value for string sub-parameters is “” (empty string).

The following syntax is used for actions that have no sub-parameters:

• +<cmd

• *E<cmd>

The following syntax is used for actions that have one sub-parameter:

• +<cmd>[=<value>]

• *E<cmd>[=<value>]

The following syntax is used for actions that have two or more sub-parameters:

• +<cmd>[=<compound_value>]

• *E<cmd>[=<compound_value>]

For actions that accept sub-parameters, if all sub-parameters are defined as being optional, and the default values for all sub-parameters are satisfactory, the Data Terminal Equipment (TE) may use the first syntax above (i.e. omit the “” from the action execution command as well as all of the sub-parameter value string).

General 13

1

If the named action is implemented in the TA and other relevant criteria are met (e.g. the TA is in the proper state), the command shall be executed with any indicated sub-parameters. If <cmd> is not recognized, the TA issues the ERROR result code and terminates processing of the command line.

An ERROR is also generated if a sub-parameter is specified for an action that does not accept sub-parameters, if too many sub-parameters are specified, if a mandatory sub-parameter is not specified, if a value is specified of the wrong type, or if a value is specified that is not within the supported range.

Action test command

The TE may test if an action command is implemented in the TA by using the syntax:

• +<cmd>=?

• *E<cmd>=?

If the TA does not recognize the indicated name, it shall return an ERROR result code and terminate processing of the command line. If the TA does recognize the action name, it shall return an OK result code. If the named action accepts one or more sub-parameters, the TA shall send an information text response to the TE, prior to the OK result code, specifying the values supported by the TA for each such sub-parameter, and possibly additional information.

The format of this information text is defined for each action command; general formats for specification of sets and ranges of numeric values are described in “Responses”, page 17 and “Extended syntax result codes”, page 18.

Parameter Command

Parameters may be defined as “read-only” or “read-write”.

“Read-only” parameters are used to provide status or identifying information to the TE, but are not settable by the TE; attempting to set their value is an error. In some cases (specified in the description of the individual parameter), the TA may ignore attempts to set the value of such parameters rather than respond with an ERROR result code, if the continued correct operation of the interface between the TA and TE will not be affected by such action. Read-only parameters may be read and tested.

“Read-write” parameters may be set by the TE, to store a value or values for later use. Read-write parameters may be set, read, and tested.

Parameters may take either a single value, or multiple (compound) values.

Each value may be either numeric or string; the definition of the parameter shall specify the type of value for each sub-parameter. Attempting to store a string value in a numeric parameter, or a numeric value in a string parameter, is an error.

4 General

Parameter set command

The definition of the parameter shall indicate, for each value, whether the specification of that value is mandatory or optional. For optional values, the definition shall indicate the assumed (default) value if none is specified; the assumed value may be either a previous value (i.e. the value of an omitted sub-parameter retains its previous value), or a fixed value (e.g. the value of an omitted sub-parameter is assumed to be zero). Generally, the default value for numeric parameters is 0, and the default value for string parameters is “” (empty string).

The following syntax is used for parameters that accept a single value:

• +<cmd>=[<value>]

• *E<cmd>=[<value>]

The following syntax is used for parameters that accept more than one value:

• +<cmd>=[<compound_value>]

• *E<cmd>=[<compound_value>]

If the named parameter is implemented in the TA, all mandatory values are specified, and all values are valid according to the definition of the parameter, the specified values shall be stored. If <cmd>is not recognized, one or more mandatory values are omitted, or one or more values are of the wrong type or outside the permitted range, the TA issues the ERROR result code and terminates processing of the command line. An ERROR is also generated if too many values are specified. In case of an error, all previous values of the parameter are unaffected.

Parameter read command syntax

The TE may determine the current value or values stored in a parameter by using the following syntax:

• +<cmd>?

• *E<cmd>?

If the named parameter is implemented in the TA, the current values stored for the parameter are sent to the TE in an information text response. The format of this response is described in the definition of the parameter. Generally, the values will be sent in the same form in which they would be issued by the TE in a parameter setting command; if multiple values are supported, they will generally be separated by commas, as in a parameter setting command.

Concatenating commands after extended syntax commands

Additional commands may follow an extended syntax command on the same command line if a semicolon (“;” IA5 3/11) is inserted after the preceding extended command as a separator. The semicolon is not necessary when the extended syntax command is the last command on the command line.

General 15

1

Concatenating commands after basic format commands

Extended syntax commands may appear on the same command line after a basic syntax command without a separator, in the same manner as concatenation of basic syntax commands.

Issuing commands

All characters in a command line shall be issued at the same data rate, and with the same parity and format.

If the maximum number of characters that the TA can accept in the body is exceeded, an ERROR result code shall be generated after the command line is terminated.

The TE shall not begin issuing a subsequent command line until at least one-tenth of a second has elapsed after receipt of the entire result code issued by the TA in response to the preceding command line.

Executing commands

Upon receipt of the termination character, the TA shall commence execution of the commands in the command line in the order received from the TE.

Should execution of a command result in an error, or a character be not recognized as a valid command (or command string), execution is terminated, the remainder of the command line is ignored, and the ERROR result code is issued. Otherwise, if all commands execute correctly, only the result code associated with the last command shall be issued; result codes for preceding commands are suppressed. If no commands appear in the command line, the OK result code is issued.

Aborting commands

Some action commands that require time to execute may be aborted while in progress; these are explicitly noted in the description of the command. Aborting of commands is accomplished by the transmission from the TE to the TA of any character. A single character shall be sufficient to abort the command in progress; however, characters transmitted during the first 125 milliseconds after transmission of the termination character shall be ignored (to allow for the TE to append additional control characters such as line feed after the command line termination character). To insure that the aborting character is recognized by the TA, it should be sent at the same rate as the.preceding command line; the TA may ignore characters sent at other rates. When such an aborting event is recognized by the TA, it shall terminate the command in progress and return an appropriate result code to the TE, as specified for the particular command.

6 General

Handling of invalid numbers and S-parameter values

The TA shall react to undefined numbers and S-parameter values in the following way; issue the ERROR result code, and leave the previous value of the parameter unchanged;

TA responses

While in command state and online command state, the TA shall issue responses using the same rate, word length, and parity as the most recently received TE command line. In the event that no TE command has yet been received, rate, word length, and parity used will depend on the capabilities of the TA.

When the TA transitions from the command state or online command state to the online data state, the result code CONNECT should be issued at the bit rate and parity used during the command state. When the TA transitions from the online data state to the command state or online command state, the result codes should be issued at the bit rate used during the online data state.

Thereafter, any unsolicited result codes should use the bit rate and parity of the last command line issued by the TE to the TA.

The characters of a response shall be contiguous, with no more than 100 milliseconds of mark idle issued between characters in addition to stop elements.

Responses

There are two types of responses that may be issued by the TA: information text and result codes.

Information text responses consist of three parts: a header, text, and a trailer. The characters transmitted for the header are determined by a user setting (see the V command). The trailer consists of two characters, being the character having the ordinal value of parameter S3 followed by the character having the ordinal value of parameter S4.

Result codes consist of three parts: a header, the result text, and a trailer. The characters transmitted for the header and trailer are determined by a user setting (see the V command). The result text may be transmitted as a number or as a string, depending on a user selectable setting (see the V command).

There are three types of result codes: final, intermediate, and unsolicited.

A final result code indicates the completion of a full TA action and a willingness to accept new commands from the TE. An intermediate result code is a report of the progress of a TA action. The CONNECT result code is an intermediate result code (others may be defined by manufacturers). In the case of a dialing or answering command, the TA moves from command state to online data state, and issues a CONNECT result code. This is an intermediate result code for the TA because it is not prepared to accept commands from the TE while in online data state. When the TA moves back to the command state, it will then issue a final result code (such as OK or NO CARRIER).

General 17

1

Unsolicited result codes (such as RING) indicate the occurrence of an event not directly associated with the issuance of a command from the TE.

Table 1 indicates result codes that shall be implemented by the TA, their numeric equivalents, and a brief description of the use of each. In clause 6, the description of each command includes the specific result codes that may be issued in relation to that command and the circumstances under which they may be issued.

Table 1/V.250 - Result codes

Extended syntax result codes

Extended syntax result codes may be issued in response to either basic or extended commands, or both. The appropriate responses shall be specified in the definitions of the commands, the responses, or both.

The general format of extended syntax result codes is the same as result codes defined in TIA-602 with regard to headers and trailers. The characters specified in S-parameters S3 and S4 shall be used in headers and trailers of extended syntax result codes as they are in basic format result codes. The setting of the “V” command shall affect the headers and trailers associated with extended syntax result codes in the same manner as basic format result codes; however, unlike basic format result codes, extended syntax result codes have no numeric equivalent, and are always issued in alphabetic form.

Extended syntax result codes shall be subject to suppression by the “Q1” command, as with basic format result codes. The issuance of extended syntax result codes shall not be affected by the setting of the “X” command.

Result code (ATV1)

Numeric (ATV0)

Description

OK 0 Acknowledges execution of a command

CONNECT 1 A connection has been established; the TA is moving from command state to online data state

RING 2 The TA has detected an incoming call signal from the network

NO CARRIER

3 The connection has been terminated or the attempt to establish a connection failed

ERROR 4 Command not recognized, command line maximum length exceeded, parameter value invalid, or other problem with processing the command line

BUSY 7 Engaged (busy) state detected

NO ANSWER

8 “@” (Wait for Quiet Answer) dial modifier was used, but remote ringing followed by five seconds of silence was not detected before expiration of the connection timer (S7)

CONNECT <text>

Manufacturer- specific

Same as CONNECT, but includes manufacturer-specific text that may specify TE speed, line speed, error control, data compression, or other status

8 General

Extended syntax result codes may be either final, intermediate, or unsolicited; the type shall be indicated in the definition of the result code.

Extended syntax result codes shall be prefixed by the “+” or “ *E” character to avoid duplication of basic format result codes specified in TIA-602 and by manufacturers. Following the “+” and “ *E” character(s), the name of the result code appears; result code names shall follow the same rules as command names (see “Command naming rules”, page 11).

Extended syntax result codes may include the reporting of values. The definition of the result code shall specify whether or not values are appended to the result code, and, if so, how many, their types, and their assumed default values if omitted. When no values are to be reported, the result code appears in the simplest form:

• +<cmd>

• *E<cmd>

If a single value is to be reported, the form of the result code shall be:

• +<cmd>:<space><value>

• *E<cmd>:<space><value>

Note! A single space character (ASCII 20h) separates the colon character (ASCII 3Ah) from the <value>; no space appears between the result code name and the colon.

If multiple values are to be reported with the result code, the form is:

• +<cmd>:<space><compound_value>

• *E<cmd>:<space><compound_value>

where <compound_value>follows the rules specified in “Compound values”, page 13.

Information text formats for test commands

In general, the format of information text returned by extended syntax commands shall be specified in the definition of the command. This subclause describes recommended formats for information text returned in response to action test (for actions that accept one or more sub-parameters) and parameter test commands. The definitions of the responses to such testing commands, as described in the definitions of the associated commands in standards that reference this Recommendation, may use this recommended format or any other suitable format that is adequately specified.

Note! The TA may insert intermediate <CR characters in very long information text responses, in order to avoid overrunning TE receive buffers. If intermediate <CR characters are included, the TA shall not include the character sequences “0 <CR ” (3/0, 0/13) or “OK...CR ” (4/15, 4/11, 0/13), so that TE can avoid false detection of the end of these information text responses.

General 19

2

Range of values

When the action accepts a single numeric sub-parameter, or the parameter accepts only one numeric value, the set of supported values may be presented in the information text as an ordered list of values. The list shall be preceded by a left parenthesis (“(”, IA5 2/8), and is followed by a right parenthesis (“)”, IA5 2/9). If only a single value is supported, it shall appear between the parentheses.

If more than one value is supported, then the values may be listed individually, separated by comma characters (IA5 2/12), or, when a continuous range of values is supported, by the first value in the range, followed by a hyphen character (IA5 2/13), followed by the last value in the range. The specification of single values and ranges of values may be intermixed within a single information text. In all cases, the supported values shall be indicated in ascending order.

For example, the following are some examples of value range indications:

(0) Only the value 0 is supported.

(1,2,3) The values 1, 2, and 3 are supported.

(1-3) The values 1 through 3 are supported.

(0,4,5,6,9,11,12) The several listed values are supported.

(0,4-6,9,11-12) An alternative expression of the above list.

Compound range of values

When the action accepts more than one sub-parameter, or the parameter accepts more than one value, the set of supported values may be presented as a list of the parenthetically-enclosed value range strings described in 5.7.3.1 above, separated by commas. For example, the information text in response to testing an action that accepts three sub-parameters, and supports various ranges for each of them, could appear as follows:

(0),(1-3),(0,4-6,9,11-12)

This indicates that the first sub-parameter accepts only the value 0, the second accepts any value from 1 through 3 inclusive, and the third sub-parameter accepts any of the values 0, 4, 5, 6, 9, 11, or 12.

In-band Escape mechanism

An in-band escape mechanism is an identifiable sequence of characters sent from the TE to the TA that when received, causes the TA to switch from on-line data mode to on-line command mode. These characters are called escape sequence.

This specification covers the use of the Time Independent Escape Sequence (TIES) by Ventel.

The TIES method is as follows:

• Start with the escape sequence (three +)

• Followed by “AT”

0 General

• Followed by an optional AT-command

• Followed by the terminating character stored in S3

General 21

2

Control and Identification Commands

In the following syntax tables the final result codes “OK” and “ERROR” are implied and are omitted from the command syntax

Z - Reset to Factory Defined Configuration

Action command syntax

Description

This command resets the values to user default settings and closes all connections. If the TA has a data-call in progress, it is disconnected from the call, terminating any (GSM) data-connection in progress. GPRS connection isn’t affected by this command.

All of the functions of the command shall be completed before the TA issues the result code.

An OK result code for this command is issued using the same rate, parity, and word format as the TE command line containing the command, but using the new values for parameters that affect the format of result codes (e.g. Q, V, S3, S4).

Comments

ATZ is the same as ATH&F.

The TE should not include additional commands on the same command line after the Z command because such commands may be ignored.

Because this command may take into consideration the settings of nonvolatile parameter storage, it does not necessarily return the TA to a “known state”. In particular, the TA may, as a result of execution of this command, be placed in a state in which it appears to not respond to TE commands, or respond in a completely different format than was being used prior to execution of the command.

Command Possible response(s)

Z

2 Control and Identification Commands

&F - Reset to Default Configuration


Description

This command instructs the TA to set all parameters to factory default values specified by the manufacturer, which may take into consideration hardware configuration switches and other manufacturer-defined criteria.

Comments

An OK result code for this command is issued using the same rate, parity, and word format as the TE command line containing the command, but using the factory-defined values for other parameters that affect the format of result codes (e.g. Q, V, S3, S4) and dependent upon other commands that may follow on the same command line.

I - Request HW Version

Action command syntax Command

Description

This command causes the TA to transmit one or more lines of information text, determined by the manufacturer.

Parameter-Values<Value> <Information>

0 same info as +GMM

1 same info as +GMR.

8 TA hardware revision (Type approved HW revision).

Comments

Hardware revision must be stored so it does not change when the software is upgraded.


&F


ATI<value> <information>

Control and Identification Commands 23

2

+CGMI (+GMI) - Request Manufacturer Identification



Description

The +CGMI command is used to get the identity of the manufacturer of the phone (ME).

AT+GMI command is used to get the identity of the manufacturer of the modem (TA). The +GMI command will never give an ERROR response.

Test command is used to determine if the command is supported.

Parameter-Values<manufacturer> .Sony Ericsson.

<err> “Error Messages”, page 189

CommandPossible response(s): +CME ERROR: <err>

+CGMI SONYERICSSON

+CGMI=?


+GMI SONYERICSSON

+GMI=?


+CGMM (+GMM) - Request Model Id



Description

The +CGMM command is used to get the model of the phone (MS) determined by the manufacturer.

The +GMM command is used to get the model of the modem (TA). The +GMM command will never give an ERROR response.


Parameter-Values<model-type> : “6130201-BV”: A unique ASCII character/digit that may include

blank characters. Always 10 characters long (padded with space if less than 10 digits long).

<model-name>: “GC75”: model name for the transceiver unit.

<err> Refer to “+CME ERROR: <err> - Mobile Equipment error result code”, page 189.


+CGMM <model-type><model-name>

+CGMM=?


+GMM <model-name>

+GMM=?


2

+CGMR (+GMR) - Request Revision Id



Description

The +CGMR command is used to get the SW version of the phone (ME).

The +GMR command is used to get the SW version of the modem (TA). The +GMR command will never give an ERROR response.


Parameter-Values<revision>: An ASCII string containing a six digit date (year, month, day),

<space>, a four digit time (hour, minute), <space>, <softwareidentity>.


+CLAC - List All Available AT Commands


Description

Execution command causes the ME to return one or more lines of AT Commands.


+CGMR <revision>

+CGMR=?


+GMR <revision>

+GMR=?


+CLAC <AT Command-1> [<CR><LF><AT Command-2>[...]]

+CLAC=?


Parameter-Values<AT Command-n>:Defines the AT command including the prefix AT. Text shall not

contain the sequence 0<CR> or OK<CR>


Comments

This command only returns the AT commands that are available for the end user. This command is equivalent to AT*.

* - List All AT Commands


Description

This command is used to get the list of the supported commands.

Parameter-Values<Commandx>: defines the AT Command. Text shall not contain the sequence

0<CR> or OK<CR>

Comments

This command only returns the AT commands that are available for the end user.

+GCAP - Request Modem Capability List


Description

This command is used to request the list of valid Modem Command Prefixes.


* <Command-1> <CR><LF><Command-2>[...]]


+GCAP +GCAP: (list of supported <capability>s)

+GCAP=?


2

Parameter-Values<capability> Description

+CGSM GSM commands

+FCLASS Facsimile 2 commands

+DS V42bis, compression

+ES V42, Error correction

+WS46 - select wireless network (PCCA STD-101)

Parameter command syntax

Description

Set command to select the WDS side stack <n> to be used by the TA. Read command shows current setting and test command displays side stacks implemented in the TA.

Defined values <n>

0 Indicates that no wireless stack is active i.e +CFUN=4. Only possible in a response.

12 GSM digital cellular i.e. +CFUN=1. Default.

240 Indicates that no wireless stack is active and the phone is connected to a power source (charge only mode) i.e. +CFUN=0. Only possible in a response.


+WS46=[<n>]

+WS46? <n>

+WS46=? (list of supported <n>s)


Call Control

A - Answer


Unsolicited Result Codes

Description

This command is used to signal the MS to answer an incoming data-call. The command is followed by an intermediate result code such as CONNECT and enters Online State.

Any additional commands that appear after A on the same command line are ignored.

Parameter-Values <text>

9600 9.600 bps

14400 14.400 bps

19200 19.200 bps

28800 28.800 bps

Abortability

The A command may be aborted in the manner described in “Aborting commands”, page 16. If the TA is connected to the line, it disconnects from the line in an orderly manner as required by the state of the connection. Aborting the connection by reception of a character is generally possible at any time before the TA enters online data state, but may not be possible during some states of connection establishment, such as handshaking. The TA shall issue a final result code; which result code to issue shall be determined by the manufacturer, and may depend upon the state of the connection at the time the character was received from the TE. If a CONNECT or CONNECT <text> result code is received by the TE, this indicates that the attempt to abort the command was not successful, possibly due to the state of connection establishment at the time the character was sent.


A CONNECT CONNECT <text> NO CARRIER

A=?

RING

+CRING

Call Control 29

3

Comments

This command may only initiate a data-call setup, so an “OK” result code would indicate an unsuccessful call-setup.

H - Hang up


Description

This command is used to signal the MS to terminate an active call. All of the functions of the command shall be completed before the TA issues any result code.

Parameter-Values <value>

0 Disconnect and terminate active data-call. Default.

D - Dial (non GPRS calls)

Execute command syntax

Description

This command is used to signal the MS to dial a call.

All characters appearing on the same command line after the “D” are considered part of the call addressing information to be signalled to the network, or modifiers used to control the signalling process (collectively known as a “dial string”), up to a semicolon character (IA5 3/11) or the end of the command line.

Any characters appearing in the dial string that the TA does not recognize as a valid part of the call addressing information or as a valid modifier shall be ignored. This permits characters such as parentheses and hyphens to be included that are typically used in formatting of telephone numbers.


H[<value>]


D<dial_string> CONNECT CONNECT <text> NO CARRIER ERROR BUSY

0 Call Control

V.25ter [28] dial command D lists characters that may be used in a dialling string for making a call or controlling supplementary services in accordance with GSM 02.30 [3]. Their use in GSM is listed in this subclause, as well as new dial modifiers applicable only to GSM are introduced. For a ME supporting AT commands only, it is mandatory to support the control of supplementary services in accordance with GSM 02.30 [3] through the dial command or through the specific supplementary service commands (+CCFC, +CLCK, etc.), where GSM 02.30 [3] identifies the supplementary services as mandatory.

<Dial-string> Parameter

V.25ter [28] dialling digits 1 2 3 4 5 6 7 8 9 0 * # + A B C (implementation of these characters is mandatory for GSM)

“+” When given before dialing digits the call is originated to an international ISDN address (TON/NPI = 145) else the call is originated to an un-known type of ISDN address (TON/NPI = 169)

V.25ter [28] modifier characters , (implementation of this character is mandatory for GSM, but it is

ignored)

T P (implementation of these characters is mandatory for GSM, but they are ignored)

V.25ter [28] semicolon character ; In GSM, when semicolon character is given after dialling digits (and

modifiers), a voice call is originated to the given address. GC75 will issue an ERROR response when this dial modifier is found in the dial-string.

GSM modifier characters > (refer subclause “Direct dialling from phonebooks”)

I or i (override the CLIR supplementary service subscription default value for this call; I = invocation (restrict CLI presentation) and i = suppression (allow CLI presentation); refer subclause “+CLIR - Calling line identification restriction”)

Possible responses to ATD command are following:

• CONNECT if a data-call is successfully established.

• NO CARRIER if unable to establish a connection or if the Mobile phone is not registered or if the connection attempt was aborted by the user.

• ERROR if ATD is unsuccessfully executed by the MS.

• NO DIALTONE if the mobile is not within coverage of the network.

• BUSY if the phone number called is engaged.

Call Control 31

3

• DELAYED if calling attempt is delayed because of repeat restrictions, this is an intermediate result code.

• BLACKLISTED when modem is blocked because of repeat restrictions.

Comments

Note! Command also supports Supplementary Service Code (SSC) strings, e.g. ATD**61*<adr>*11*25# (See GSM 07.07 [18] §6.23)

This subclause describes how existing AT commands, designed for use with a modem, may be used to control a GPRS MO and GPRS MT connection. This is to provide backwards compatibility with existing communications software. For new applications it is recommended that the GPRS-specific commands be used.

MT originated PDP context activation

In this mode of operation, the MT behaves like an originating modem and accepts the normal V.25ter commands associated with placing and clearing a call. If GPRS-specific configuration commands are required, they may be sent to the MT as part of the modem initialisation commands.

D*99* - Request GPRS service


Description

This command causes the CG75 to perform whatever actions are necessary to establish communication between the TE and the external PDN. The V.25ter ’D’ (Dial) command causes the MT to enter the V.25ter online data state and, with the TE, to start the specified layer 2 protocol. The MT returns CONNECT to confirm acceptance of the command prior to entering the V.25ter online data state. No further commands may follow on the AT command line.

The detailed behaviour after the online data state has been entered is dependent on the PDP type. It is described briefly in clauses 8 (for X.25) and 9 (for IP) of GSM 07.60. GPRS attachment and PDP context activation procedures may take place prior to or during the PDP start-up if they have not already been performed using the +CGATT and +CGACT commands.


D*99[*[<called_address>] [*[<L2P>][*[<cid>]]]]#

CONNECTCONNECT <text>ERROR

2 Call Control

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.25ter command state and returns the NO CARRIER final result code.

If <called address> is supported and provided, the MT shall automatically set up a virtual call to the specified address after the PDP context has been activated.

If <L2P> and <cid> are supported, their usage shall be the same as in the +CGDATA command. The +CGDCONT, +CGQREQ, etc. commands may then be used in the modem initialisation AT command string to set values for PDP type, APN, QoS etc.

If <L2P> is not supported or is supported but omitted, the MT shall use a layer 2 protocol appropriate to the PDP type.

If <cid> is not supported or is supported but omitted, the MT shall attempt to activate the context using:

(a) any information provided by the TE during the PDP start-up procedure, e.g. the TE may provide a PDP type and/or PDP address to the MT, or

(b) a prior knowledge, e.g. the MT may implement only one PDP type, or

(c) using the ’Empty PDP type’ (GSM 04.08). (No PDP address or APN shall be sent in this case and only one PDP context subscription record shall be present in the HLR for this subscriber.)

This command may be used in both normal and modem compatibility modes.

Note! The dial string conforms to the syntax specified in GSM 02.30.

Parameter-Values<value> Description

<called_address>: a string that identifies the called party in the address, equivalent may be used. Also, the character comma ’,’ may be used as a substitute for the character period ’.’.

<L2P>: a string which indicates the layer 2 protocol to be used (see +CGDATA command). For communications software that does not support arbitrary characters in the dial string, the following numeric equivalents shall be used: 0 NULL (Obsolete) 1 PPP 2 PAD 3 X25 9yyyy M-xxxx Other values are reserved and will result in an ERROR response to the set command.

Note! V.250 (and certain communications software) does not permit arbitrary characters in the dial string. The <L2P> and <called_address> strings are therefore specified as containing digits (0-9) only.

Call Control 33

3

<cid>: a digit string which specifies a particular PDP context definition (see +CGDCONT command).

D*98* - Request GPRS IP service


Description

This command causes the MT to perform whatever actions are necessary to establish communication between the TE and the external PDN.

The V.25ter ’D’ (Dial) command causes the MT to enter the V.25ter online data state and, with the TE, to start the specified layer 2 protocol. The MT shall return CONNECT to confirm acceptance of the command prior to entering the V.25ter online data state. No further commands may follow on the AT command line.

The detailed behaviour after the online data state has been entered is described briefly in clause 9, for IP, of GSM 07.60. GPRS attachment and PDP context activation procedures may take place prior to or during the PDP start-up if they have not already been performed using the +CGATT and +CGACT commands.

When the layer 2 protocol has terminated, either as a result of an orderly shut down of the PDP or an error, the MT shall enter V.25ter command state and return the NO CARRIER final result code.

If <cid> is supported, its usage shall be the same as in the +CGDATA command. The +CGDCONT, +CGQREQ, etc. commands may then be used in the modem initialisation AT command string to set values for PDP type, APN, QoS etc.

If <cid> is not supported or is supported but omitted, the MT shall attempt to activate the context using:

(a) any information provided by the TE during the PDP start-up procedure, e.g. the TE may provide a PDP type and/or PDP address to the MT, or

(b) a prior knowledge, e.g. the MT may implement only one PDP type, or

(c) using the ’Empty PDP type’ (GSM 04.08). (No PDP address or APN shall be sent in this case and only one PDP context subscription record shall be present in the HLR for this subscriber.)


Note! The dial string conforms to the syntax specified in GSM 02.30.


D*98[*<cid>]# CONNECTCONNECT <text>ERROR

4 Call Control

Defined Values<value> Description

<GPRS_SC_IP>: (GPRS Service Code for IP) a digit string (value 98) which identifies a request to use the GPRS with IP (PDP types IP and PPP)

<cid>: a digit string which specifies a particular PDP context definition(see +CGDCONT command).

Network requested PDP context activation

In this mode of operation, the MT behaves like an answering modem and accepts the normal V.25ter commands associated with answering a call. If GPRS-specific configuration commands are required, they may be sent to the GC75 as part of the modem initialisation commands.

The +CGAUTO command is used to select modem compatibility mode.

S0 - Automatic response to a network request for PDP context activation

Description

The V.25ter ’S0=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.

When the ’S0=n’ (n>0) command is received, the GC75 shall attempt to perform a GPRS attach if it is not already attached. Failure will result in ERROR being returned to the TE. Subsequently, the GC75 will announce a network request for PDP context activation by issuing the unsolicited result code RING to the TE, followed by the intermediate result code CONNECT. The GC75 then enters V.25ter online data state and follows the same procedure as it would after having received a +CGANS=1 with no <L2P> or <cid> values specified.

Note! The ’S0=n’ (n=0) command does not perform an automatic GPRS detach.

A - Manual acceptance of a network request for PDP context activation

Description

The V.25ter ’A’ (Answer) command may be used to accept a network request for a PDP context activation announced by the unsolicited result code RING. The GC75 responds with CONNECT, enters V.25ter online data state and follows the same procedure as it would after having received a +CGANS=1 with no <L2P> or <cid> values specified. It is an error to issue the ’A’ command when there is no outstanding network request.

Call Control 35

3

H - Manual rejection of a network request for PDP context activation

Description

The V.25ter ’H’ or ’H0’ (On-hook) command may be used to reject a network request for PDP context activation announced by the unsolicited result code RING. The GC75 responds with OK. It is an error to issue the ’H’ command when there is no outstanding network request.

Note! This is an extension to the usage of the ’H’ command that is described in ITU-T V.25ter.

L - Monitor Speaker Loudness


Description

This command is ignored

Read command is used to show the current setting

Test command is used to show the list of the supported values for monitor speaker.

Parameter-Values <value> Description

0 Min speaker volume (Silent). Default.

1-255 OK but ignored


L[<value>]

L? L: <value>

L=? L: (list of supported <value>s)

6 Call Control

+CFUN - Set Phone Functionality


Description

Set command +CFUN is used to set the MS functionality and to select the level of the functionality.

Read command is used to show the current setting.

Test command is used to show the list of the supported power levels and supported reset modes, as compound values.

Parameter-Values <fun> Description

0 Minimum functionality. Default.

1 Full functionality.

4 Disable MS transmit and receive RF circuits.

<rst> Description

0 Do not reset. Default.

1 Reset the MS before setting it to <fun> power level .


Comments

The only commands available when +CFUN=0 are; +CFUN, +GMI, +CGMI, +GMM, +CGMM, +GMR, +CGMR and +CGSN.


+CME ERROR: <err>

+CFUN=[<fun>[,<rst>]]

+CFUN? +CFUN: <fun>

+CFUN=? +CFUN: (list of supported <fun>s), (list of supported <rst>s)

Call Control 37

3

RING - Ring Indication

Unsolicited result code

Description

This result code is issued by the MS to report an incoming call. This result code should be repeated each time the network repeats the incoming call indication.

The transmitting of RING result codes from the MS to the TE may be suppressed during command entry and execution. Circuit 125, if provided, may be unaffected by the status of command entry and execution and continue to indicate incoming calls even though transmitting of RING result codes is suppressed.

Comments

See “+CRC - Cellular Result Code”, page 92.

O - Return to On-line Data Mode

Execution command syntax

Description

Returns GC75 to on-line data mode from on-line command mode.

Parameter-Values <action>

0 (default) switch from on-line command to on-line data state.

Comments

Possible responses

ERROR <action> is outside legal range or not in on-line command mode.

CONNECT Re-established data connection.


RING


O[=][<action>] ERROR CONNECT CONNECT <text> NO CARRIER

O=?

8 Call Control

NO CARRIER data connection lost or aborted by user.

P - Select Pulse Dialing


Description

This command is ignored and implemented for compatibility only. It would normally cause the next D command (see “D - Dial (non GPRS calls)”, page 30) to use pulses when dialing the number.

T - Select Tone Dialing


Description

This command is ignored and implemented for compatibility only. It would normally cause the next D command (see “D - Dial (non GPRS calls)”, page 30) to use tones when dialing the number.


P

P=?


T

T=?

Call Control 39

4

+CAOC - Advice of Charge

Action/Parameter command syntax

Unsolicited Result Code

Description

This refers to Advice of Charge supplementary service (GSM 02.24 [2] and GSM 02.86 [16]) that enables subscriber to get information about the cost of calls. With <mode>=0, the execute command returns the current call meter value from the ME.

The command also includes the possibility to enable an unsolicited event reporting of the CCM information. The unsolicited result code +CCCM is sent when the CCM value changes, but not more that every 10 seconds. Deactivation of the unsolicited event reporting is made with the same command.

Read command indicates whether the unsolicited reporting is activated or not.

Test command returns the supported mode values.

Parameter-Values <mode>

0 query CCM value

1 deactivate the unsolicited reporting of CCM value

2 activate the unsolicited reporting of CCM value

<ccm> string type; three bytes of the current call meter value in hexadecimal format (e.g. “00001E” indicates decimal value 30); value is in home units and bytes are similarly coded as ACMmax value in the SIM.


Comments

Also see “+CACM - Accumulated Call Meter”, page 41; “+CAMM - Accumulated Call Meter Maximum”, page 42;


+CME ERROR <err>

+CAOC[=<mode>] [+CAOC: <ccm>]

+CAOC? +CAOC: <mode>

+CAOC=? [+CAOC: (list of supported <mode>s]

+CAOC: <ccm>

0 Call Control

“+CPUC - Price per unit and currency”, page 43; “+CCWE - Call Meter Maximum Event”, page 44.

+CACM - Accumulated Call Meter


Description

Set command resets the Advice of Charge related accumulated call meter value in SIM file EF_ACM. ACM contains the total number of home units for both the current and preceding calls. SIM PIN2 is usually required to reset the value. If setting fails in a +CME ERROR is returned.

Read command returns the current value of ACM.

Parameter-Values <passwd> string type; SIM PIN2

<acm> string type; accumulated call meter value similarly coded as <ccm> under +CAOC


Comments

Also see “+CAOC - Advice of Charge”, page 40; “+CAMM - Accumulated Call Meter Maximum”, page 42; “+CPUC - Price per unit and currency”, page 43; “+CCWE - Call Meter Maximum Event”, page 44.


+CME ERROR <err>

+CACM=[<passwd>]

+CACM? +CACM: <acm>

+CACM=?

Call Control 41

4

+CAMM - Accumulated Call Meter Maximum


Description

Set command sets the Advice of Charge related 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. When ACM (refer to “+CACM - Accumulated Call Meter”, page 41) reaches ACMmax, calls are prohibited (see also GSM 02.24 [2]). SIM PIN2 is usually required to set the value. If setting fails an +CME ERROR is returned.

Read command returns the current value of ACMmax

Parameter-Values <acmmax>: string type; accumulated call meter maximum value similarly coded

as <ccm>: under “+CAOC - Advice of Charge”, page 40; value zero disables ACMmax feature

<passwd>: string type; SIM PIN2

<err> Refer to “+CME ERROR: <err> - Mobile Equipment error result code”, page 189

Comments

Also see: “+CAOC - Advice of Charge”, page 40; “+CACM - Accumulated Call Meter”, page 41; “+CPUC - Price per unit and currency”, page 43; “+CCWE - Call Meter Maximum Event”, page 44.


+CME ERROR <err>

+CAMM=[<acmmax>[,<passwd>]]

+CAMM? +CAMM: <acmmax>

+CAMM=?

2 Call Control

+CPUC - Price per unit and currency


Description

Set command sets the parameters of Advice of Charge related price per unit and currency table in SIM file EF_PUCT. PUCT information can be used to convert the home units (as used in +CAOC, +CACM and +CAMM) into currency units. SIM PIN2 is usually required to set the parameters.

Read command returns the current parameters of PUCT.

Parameter-Values <currency>: string type; three-character currency code (e.g. .GBP., .DEM.);

character set as specified by command Select TE Character Set +CSCS

<ppu>: string type; price per unit; dot is used as a decimal separator (e.g. .2.66.)

<passwd>: string type; SIM PIN2


Comments

Also see:

“+CAOC - Advice of Charge”, page 40; “+CACM - Accumulated Call Meter”, page 41; “+CAMM - Accumulated Call Meter Maximum”, page 42; “+CCWE - Call Meter Maximum Event”, page 44.


+CME ERROR <err>

+CPUC=<currency>,<ppu>[,<passwd>]

+CPUC? +CPUC: <currency>,<ppu>

+CPUC=?

Call Control 43

4

+CCWE - Call Meter Maximum Event



Description

Shortly before the ACM (Accumulated Call Meter) maximum value is reached, an unsolicited result code +CCWV will be sent, if enabled by this command.

The warning is issued approximately when 30 seconds call time remains. It is also issued when starting a call if less than 30 s call time remains. If setting fails in an +CME ERROR is returned.

Read command returns the current setting.

Test command returns supported settings.

Parameter-Values <mode> Description

0 (default) Disable the call meter warning event

1 Enable the call meter warning event


Comments

Also see:

“+CAOC - Advice of Charge”, page 40; “+CACM - Accumulated Call Meter”, page 41; “+CAMM - Accumulated Call Meter Maximum”, page 42; “+CPUC - Price per unit and currency”, page 43.


+CME ERROR <err>

+CCWE=<mode>

+CCWE? +CCWE: <mode>

+CCWE=? +CCWE: (list of supported <mode>s)

+CCWV

4 Call Control

+CPWC - Power class


Description

This command is used to set the preferred ME power class for each GSM frequency band supported. If setting fails +CME ERROR is returned.

Read command returns the currently selected output power class and default output power class for each supported frequency band. Parameter <band1> and its associated power class parameters refer to the currently used frequency band. For example, +CPWC: 2,1,1,5,4,0 in case of a dual-band ME currently using band GSM1800, for which the power class is currently set to 2, the default being class 1, and for which the currently set power class value for GSM900 is class 5 the default being class 4.

Test command returns supported bands and their power classes. For example, +CPWC: (0,(0,4,5)),(1,(0-2)) in case of a dual-band hand-held ME.

Parameter-Values <class>

<curr_classn>s

<def_classn>s

0 default (not applicable to <curr_class>s or <def_classn>s)

1 MS output power class as in GSM 05.05 [15]

<band>

<bandn>s

0 GSM900. Default.

1 GSM1800

2 GSM1900



+CME ERROR <err>

+CPWC=[<class>[,<band>]]

+CPWC? +CPWC: <curr_class1>,<def_class1>,<band1> [,<curr_class2>,<def_class2>,<band2>[...]]

+CPWC=? +CPWC: list of supported (<band>, (list of <class>s)) pairs

Call Control 45

4

+CPAS - Phone Activity Status


Description

Execution command returns the activity status <pas> of the ME. It can be used to interrogate the ME before requesting action from the phone.

Test command returns values supported by the ME as a compound value.

Parameter-Values <pas>

0 Ready (ME allows commands from TA/TE).

3 Ringing (ME is ready for commands from TA/TE, but the ringer is active).

4 Call in progress (ME is ready for commands from TA/TE, but a call is in progress).


+CSTA - Select Type of Address


Description

Set command selects the type of number for further dialing commands (D) according to GSM specifications.

Test command returns values supported by the TA as a compound value.


+CME ERROR <err>

+CPAS +CPAS: <pas>

+CPAS=? +CPAS: (list of supported <pas>s)


+CSTA=[<type>]

+CSTA? +CSTA: <type>

+CSTA=? +CSTA: (list of supported <type>s)

6 Call Control

Parameter-Values <type>: type of address octet in integer format (refer GSM 04.08 [13] sub

clause 10.5.4.7); default 145 when dialing string includes international access code character “+”, otherwise 129

Call Control 47

4

Interface Commands

+++AT - Escape Sequence Character


Description

This command is used for switching from on-line data mode to on-line command mode.

Parameter-Values <cmd>

H[0] Hook Control, “Hang-up” (“H - Hang up”, page 30).

S3 - Command Line Termination Character


Description

This S-parameter represents the decimal IA5 value of the character recognized by the TA from the TE to terminate an incoming command line. It is also generated by the TA as part of the header, trailer, and terminator for result codes and information text, along with the S4 parameter (see the description of the V parameter for usage).

The previous value of S3 is used to determine the command line termination character for entry of the command line containing the S3 setting command. However, the result code issued shall use the value of S3 as set during the processing of the command line. For example, if S3 was previously set to 13 and the command line “ATS3=30” is issued, the command line shall be terminated with a CR character (IA5 0/13), but the result code issued will use the character with the ordinal value 30 (IA5 2/14) in place of the CR.


Test command is used to show the list of the supported <value>s.


+++AT[<cmd>]<cr>


S3=[<value>]

S3? <value>

S3=? S3: (list of supported <value>s)

8 Interface Commands


13 Default command line termination character

0-127 other values, not supported

S4 - Response Formatting Character


Description

This S-parameter represents the decimal IA5 value of the character generated by the TA as part of the header, trailer, and terminator for result codes and information text, along with the S3 parameter (see the description of the V parameter for usage (“V - TA Response Format”, page 51)). If the value of S4 is changed in a command line, the result code issued in response to that command line will use the new value of S4.

Read command is a command that is used to show the current setting.



10 formatting character, default value 0-127 other values, not supported


S4=[<value>]

S4? <value>


Interface Commands 49

5

S5 - Command Line Editing Character


Description

This S-parameter represents the decimal IA5 value of the character recognized by the TA as a request to delete from the command line the immediately preceding character (see“Command line editing”, page 9).




8 line editing character, default value

0-127 other values, not supported

E - Command Echo


Description

The setting of this parameter determines whether or not the TA echoes characters received from the TE during command state and online command state (see “Command line echo”, page 9).





S5=[<value>]

S5? <value>



E[<value>]

E? <value>

E=? E=? (list of supported <value>s)


0 TA does not echo characters during command state and online command state

1 TA echoes characters during command state and online command state, default value

Q - Result Code Suppression


Description

The setting of this parameter determines whether or not the TA transmits result codes to the TE. When result codes are being suppressed, no portion of any intermediate, final, or unsolicited result code “header, result text, line terminator, or trailer” is transmitted. Information text transmitted in response to commands is not affected by the setting of this parameter.




0 TA transmits result codes, default value.

1 Result codes are suppressed and not transmitted.

V - TA Response Format


Description

This command is used to Request TA Response Format.


Q[<value>]

Q? <value>

Q=? (list of supported <value>s)


V[<value>]

V? <value>

V=? (list of supported <value>s)


5

The setting of this parameter determines the contents of the header and trailer transmitted with result codes and information responses. It also determines whether result codes are transmitted in a numeric form or an alphabetic (or “verbose”) form. The text portion of information responses is not affected by this setting.

Table 3 shows the effect of the setting of this parameter on the format of information text and result codes. All references to <CR> mean “the character with the ordinal value specified in parameter S3”; all references to <LF> likewise mean “the character with the ordinal value specified in parameter S4”.

Effect of V parameter on response formats




0 TA transmits limited headers, trailers and numeric text.

1 TA transmits full headers, trailers and verbose response text. Default.

Comments

TA Responses are described in “TA responses”, page 17.

&C - Circuit 109 (DCD) Control


Description

This parameter determines how the state of DCD (circuit 109) relates to the detection of received line state/signal from the distant end. Changing the parameter will take effect immediately in both the command and online command states.

Table 3/V.25 ter V0 V1

Information responses <text><cr><lf> <cr><lf> <text><cr><lf>

Result Codes <numeric code><cr> <cr><lf> <verbose code><cr><lf>


&C[<value>]



0 DCD always on. Default.

Comments

For compatibility reasons only.

&D - Circuit 108 (DTR) Response


Description

This command controls all action initiated by data terminal ready (DTR) from TE.

This parameter determines how the TA responds when DTR (circuit 108/2) is changed from the ON to the OFF condition during online data state.


0 Ignore DTR. Default

1 Upon an on-to-off transition of DTR (circuit 108/2), the TA enters online command state and issues an OK result code; the call remains connected.

2 Upon an on-to-off transition of DTR (circuit 108/2), the TA instructs the underlying TA to perform an orderly cleardown of the call. The disposition of any data in the TA pending transmission to the remote TA is controlled by the +ETBM parameter (see “+ETBM - Call Termination Buffer Management”, page 61), unless the remote TA clears the call first (in which case pending data is discarded). The TA disconnects from the line. Automatic answer is disabled while DTR (circuit 108/2) remains off.


&D[=][<value>]


5

+IFC - TE-TA Local Flow Control


Description

This extended format compound parameter is used to control the operation of local flow control between the TE and TA during the data state when V42 error control is being used, or when fallback to non-error control mode is specified to include buffering and flow control. It accepts two numeric sub-parameters:

• <by_te>, which specifies the method to be used by the TE to control the flow of received data from the TA; and

• <by_ta>, which specifies the method to be used by the TA to control the flow of transmitted data from the TE.

Parameter-Values < by_te >

0 No flow control on TE.

1 Xon/Xoff flow control on TA. Control characters are removed by the TA interface.

2 RTS flow control on TA, default value <by_ta>

0 No flow control on TA.

1 Xon/Xoff flow control on TE.

2 CTS flow control on TA, default value


+IFC=[<by_te>],[<by_ta>]

+IFC? +IFC: <by_te>,<by_ta>

+IFC=? +IFC: (list of supported <by_te>s,<by_ta>s)


S0 - Automatic Answer Control



Description

This S-parameter controls the automatic answering feature of the TA. If set to 0, automatic answering is disabled. If set to a non-zero value, the TA shall cause the TA to answer when the incoming call indication (ring) has occurred the number of times indicated by the value.

Parameter-Values <rcnt>

0 Disable automatic answer. Default. 1-7 Answer after the specified number of rings.

Comments

The call is always answered in the current Fax Class, regardless of whether the incoming call is voice, data or fax.


S0=[<rcnt>]

S0? <rcnt>

S0=? S0: (list of supported < rcnt >s)

RING

+CRING


5

S6 - Blind Dial Delay Control


Description

This command is used to define the number of seconds to wait before call addressing when a dial-tone is not detected. This command is ignored by the Modem and is only included for compatibility.

Parameter-Values <dly>

2-255 seconds. (default = 2 seconds)

S7 - Connection Completion Timeout


Description

This command is used to define the maximum time allowed between completion of dialing and the connection being established. If this time is exceeded then the connection is aborted.

Parameter-Values <tmo>

50 Timeout value in seconds, default value 1-255 other values


S6=[<dly>]

S6? <dly>

S6=? S6: (list of supported <dly>s)


S7=[<tmo>]

S7? <tmo>

S7=? S7: (list of supported < tmo >s)


S10 - Automatic Disconnect Delay Control


Description

This parameter specifies amount of time that TA will remain connected to the line after the absence of received line signal. This command is ignored by the Modem and is only included for compatibility.

Parameter-Values <val>

1-254 seconds

M - Monitor Speaker Control


Description

This command defines the activity of the speaker.

Parameter-Values <speaker>

0 Off during the entire call

1-2 Ignored

Comments

This command is ignored by the Modem and is only included for compatibility.


S10=[<val>]

S10? <val>

S10=? S10: (list of supported < val >s)


M[=][<speaker>]

M? M: <speaker>

M=? M: (list of supported <speaker>s)


5

X - Call Progress Monitoring Control


Description

The setting of this parameter determines whether or not the TA transmits particular result codes to the TE. This command defines whether the dial tone detection and busy tone detection are to be used during call setup.

Parameter-Values

<text> Reported line speed at connection

Comments

BUSY state and Dial-tone detection is always ignored and is only included for compatibility, i.e. 2, 3 and 4 are same as 1.


X[=][<n>]

X? X: <n>

X=? X: (list of supported <n>s)

<n> On-line data state result code

BUSY state detection (ignored)

Dial-tone detection (ignored)

0 CONNECT OFF OFF

1 CONNECT <text> OFF OFF

2 CONNECT <text> ON OFF

3 CONNECT <text> OFF ON

4 CONNECT <text> ON ON


+ILRR - TE-TA Local , 4Rate Reporting


Description

This extended-format numeric parameter controls whether or not the extended-format “+ILRR: <rate>” information text is transmitted from the TA to the TE. The <rate> reported shall represent the current (negotiated or renegotiated) TE-TA rate. If enabled, the intermediate result code is transmitted after any modulation, error control or data compression reports are transmitted, and before any final result code (e.g. CONNECT) is transmitted. The <rate> is applied after the final result code is transmitted.

The TE-TA port rate will change only if neither buffered mode nor error-controlled means are enabled (+ES=x,0) and if the negotiated carrier rate (+MRR) does not match the current DTE-DCE port rate (set by +IPR command or auto detected from the previous command line).

The format of this intermediate result code is: +ILRR: <rate> e.g. +ILRR: 19

200 <rate> values are decimal values.


0 disable

1 enable

<rate>

9600 9.600 bps

14400 14.400 bps

19200 19.200 bps

28800 28.800 bps

38400 38.400 bps


+ILRR =[<value>]

+ILRR? +ILRR: <rate>

+ILRR=? +ILRR: (list of supported values)


6

Error Control (LAPM/MNP)

+ES - Error Control Selection

Parameter Command Syntax

Description

This command is used to control the manner of operation of the V42 protocol in the TA (if present).

Parameter-Values <orig_rqst>: specifies the initial requested mode of operation when the TA is

operating as the originator.

1 Initiate call in buffer mode

4 Initiate MNP protocol. Default <orgig_fbk>: specifies the acceptable fallback mode of operation when the TA is

operating as the originator.

0 LAPM or MNP error control option, if no error code protocol established use of buffered mode with flow control. Default

2 LAPM or MNP error control required, Disconnect if no error code protocol is established.

4 MNP error control required, Disconnect if no error code protocol is established.

<ans_fbk>: specifies the acceptable fallback mode of operation when the TA is operating as the answerer.

1 Disable error control, Buffer mode is used.

2 LAPM or MNP error control option, if no error code protocol established use of buffered mode with flow control. Default

4 LAPM error control required, Disconnect if no error code protocol is established.

6 MNP error control required, Disconnect if no error code protocol is established.


+ES=[<orig_rqst> [,<orig_fbk> [,<ans_fbk>]]]

+ES? ES: <orig_rqst>s,<orgig_fbk>s,<ans_fbk>s

+ES =? ES: (list of supported <orig_rqst>s,<orgig_fbk>s, <ans_fbk>s)

0 Error Control (LAPM/MNP)

+ETBM - Call Termination Buffer Management


Description

This command controls the handling of data remaining in TA buffers upon call termination.

Parameter-Values <pending_TD>: controls how previously-transmitted data remaining in the TA

buffers should be handled when the local TE request disconnection of the call.

0 Discard all data in the transmit buffer and disconnect.

1 Wait for all the data in the transmit buffer to be send and acknowledged. If the remote TA disconnects, clear the buffer and disconnect. Default

2 Wait for all the data in the transmit buffer to be send and acknowledged. If the remote TA disconnects or timer expires, clear the buffer and disconnect.

<pendig_RD>: controls how previously-received data remaining in the TA buffers should be handled when the remote TA disconnects the call.

0 Discard all data in the receive buffer and disconnect.

1 Wait for all the data in the receive buffer to be send and acknowledged. If the remote TA disconnects, clear the buffer and disconnect. Default

2 Wait for all the data in the receive buffer to be send and acknowledged. If the remote TA disconnects or timer expires, clear the buffer and disconnect.

<timer>: sets a maximum time limit on how long the TA will attempt to deliver the buffered data before abandoning the attempt and discarding remaining data.

0-30 The Delay used by timer as the timeout value for data to be sent or received. Default = 20 seconds.

Other Higher value may be supported at manufacture’s option.


+ETBM=[<pending_TD> [,<pendig_RD>[,<timer>]]]

+ ETBM? +ETBM: <pending_TD>,<pendig_RD>,<timer>)

+ ETBM =? +ETBM: (list of supported <pending_TD>s, <pendig_RD>s, <timer>s)

Error Control (LAPM/MNP) 61

6

+ER - Error Control Reporting


Intermediate result code

Description

This extended-format numeric parameter controls whether or not the extended-format “+ER:” intermediate result code is transmitted from the DCE to the DTE. The +ER:<type> reported shall represent the current (negotiated or renegotiated) DCE-DCE error control type. If enabled, the intermediate result code is transmitted at the point during error control negotiation (handshaking) at which the DCE has determined which error control protocol will be used (if any), before the final result code (e.g. CONNECT) is transmitted.

The +ER intermediate result code, if enabled, is issued after the Modulation report (+MCR and +MRR) and before the Data Compression Report (+DR).


0 No intermediate reporting. Default

1 Intermediate error control reporting with the Answer (A) and Dial (D) command.

2 Intermediate error control reporting with the On-line Data (O) command

3 Intermediate error control reporting with the Answer (A), Dial (D) and On-line Data (O) command.

<text>

NONE Error control is not in use

LAPM V42 LAPM protocol is in use

ALT V42 Alternative protocol is in use


+ER=[<value>]

+ER? +ER: <value>

+ER=? +ER: (list of supported <values>s)

+ER: <text>

2 Error Control (LAPM/MNP)

Data Compression (V24bis/MNP5)

+DS - Data Compression Mode Selection


Description

This command controls the V42 bis/MNP5 data compression function if provided in the TA.

Parameter-Values <direction>: specifies the desired direction(s) of operation of the data

compression function; from the TE point of view.

0 Disable V.42 bis/MNP5

1 Enable V.42 bis/MNP5 in transmit direction only

2 Enable V.42 bis/MNP5 in receive direction only

3 Enable V.42 bis/MNP5 compression in both direction. Default <compression_negotiation>:

specifies whether or not the TA should continue to operate if the desired result is not obtained.

0 Accept connection if compression is negotiated according to direction, Default

1 Disconnect if compression is not negotiated according to direction

<max_dict>: specifies the maximum number of dictionary entries which should be negotiated (may be used by the TE to limit the codeword size transmitted, based on its knowledge of the nature of the data to be transmitted)

512-2048 Maximum dictionary size.

<max_string>: specifies the maximum string length to be negotiated (V.42bis/MNP5 P2).

6-32 Maximum string length, Default value = 32


+DS=[<direction> [,<compresion_negotiation> [,<max_dict> [,<max_string>]]]]

+DS? DS: direction>s, <compression_negotiation>s, <max_dict>s, <max_string>s

+DS=? DS: (list of supported <direction>s, <compresion_negotiation>s, <max_dict>s, <max_string>s)

Data Compression (V24bis/MNP5) 63

6

+DR - Data Compression Reporting


Intermediate result code

Description

This extended-format numeric parameter controls whether or not the extended-format “+DR:” intermediate result code is transmitted from the TA to the TE. The +DR: <type> reported shall represent the current (negotiated or renegotiated) TA-TE data compression type. If enabled, the intermediate result code is transmitted at the point after error control negotiation (handshaking) at which the TA has determined which data compression technique will be used (if any) and the direction of operation.

The +DR intermediate result code, if enabled, is issued after the Error Control Report (+ER) and before the final result code (e.g. CONNECT).

Parameter-Values

<value>

0 Intermediate compression mode reporting disabled, Default

1 Intermediate compression mode reporting enabled

<text>

NONE Data compression is not in use

V42B V.42bis is in use in both directions

V42B RD V.42bis is in use in receive direction only

V42B TD V.42bis is in use in transmit direction only


+DR=[<value>]

+DR? +DR: <value>

+DR=? +DR: (list of supported <value>s)

+DR: <text>

4 Data Compression (V24bis/MNP5)

Fax Class 2

Note! In some cases EIA and ITU use different names for one AT command. AT command names in this document are according to ITU and the EIA equivalent names are given in Comment sections.

+FCLASS - Select Mode


Description

The Service Class may be set by the TE from the choices available (see Parameter-Values section, below), using the .AT+FCLASS=<value>. command.

The read command (AT+FCLASS?) is used to read the current setting.

The Service Classes available from a facsimile TA are tested by the .AT+FCLASS=?. command. The information text response is a list of values, separated by commas.

Parameter-Values < value>

0 indicates a data modem (e.g. Recommendation V.25ter)

2 indicates a Service Class 2 facsimile TA (e.g. ITU-T T.32).


+FCLASS=[<value>]

+FCLASS? +FCLASS: <value>

+FCLASS=? +FCLASS: (list of supported <value>s)

Fax Class 2 65

6

+FBO - Phase C Bit Order Parameter


Description

This command controls the mapping between PSTN facsimile data and TE-TA. There are two choices:

• Direct: the first bit transferred of each byte on the TE-TA link is the first bit transferred on the PSTN data carrier.

• Reserved: the last bit transferred of each byte on the TE-TA link is the first bit transferred on the PSTN data carrier.

There are two data types to control:

• Phase C data: T.4 [24] encoded data, transferred during execution of +FDT or +FDR commands.

• Phase E/D data: T.4 [24] Phase B and Phase D control message, reported to the TE in +FHT: and +FHR: reports, enabled by the +FBUG parameter.


0 selects direct bit error for both Phase C data and for Phase B/D data. Default

1 selects reserved bit order for Phase C data and selects direct bit order Phase B/D data.

2 selects direct bit order for Phase C data and selects direct bit order Phase B/D data.

3 selects reserved bit order for Phase C data and for Phase B/D data.

Comments

The equivalent AT command according to EIA = AT+FBOR.


+FBO=<value>

+FBO? <value>

+FBO=? (list of supported <value>s)

6 Fax Class 2

+FCQ - Copy Quality Checking


Description

This command controls Copy Quality Checking. The TA shall generate a page transfer report, indicated with the +FPS: <ppr>, <lc>, <blc>, <cblc> response and posted in the +FPS parameter. The +FCQ parameter setting also conditions to the generation of bad line <blc> and consecutive bad line count <cblc> sub-parameters.

Parameter-Values <value>:

0 No Copy Quality Checking. The TA will generate Copy Quality OK (MCF) response to complete pages, and set +FPS =1, Mandatory

1 The TA can check 1-D Phase C data. The TE must check copy quality for 2-D Phase C data, Optional, not implemented.

2 The TA can check 1-D and 2-D Phase C data, Optional, not implemented.

+FCC - TA Capability Parameter


Description

This command allows the TA to sense and constrain the capabilities of the facsimile TA, from the choice defined in ITU-T T.30 Table 2. Modification to +FCC are copied into +FIS.


+FCQ=<value>

+FCQ? <value>

+FCQ=? (list of supported <value>s)


+FCC=<VR>,<BR>, <WD>,<LN>,<DF>,<EC>, <BF>,<ST>

+FCC? <VR>,<BR>,<WD>,<LN>,<DF>,<EC>,<BF>,<ST>

+FCC=? (0,1),(0,3),(0,4),(0,2), 0, 0, 0,(0,7)

Fax Class 2 67

6

Parameter-Values <VR>: Vertical Resolution

0 Normal, 98 dpi

1 Fine, 196 dpi

< BR>: Bit Rate

2 7200 bit/s

3 9600 bit/s

4 12000 bit/s, Not supported 5 14400 bit/s, Not supported <WD>: Page width

0 1728 pixels in 215 mm

1 2048 pixels in 255 mm, Optional 2 2432 pixels in 303 mm, Optional 3 1216 pixels in 151 mm, Optional 4 864 pixels in 107 mm, Optional <LN>: Page Length

0 A4, 297 mm

1 B4, 364, Optional 2 unlimited length, Optional <DF>: Data Compression Format

0 1-D modified Huffman

1 2-D modified Read, Optional 2 2-D uncompressed mode, Optional 3 2-D modified Read, Optional <EC>: Error Correction

0 Disable ECM

1 enable ECM, 64 bytes/frame, Optional, Not supported 2 enable ECM, 256 bytes/frame, Optional, Not supported <BF>: Binary File Transfer

0 disable ECM

1 enable ECM, 64 bytes/frame, Optional, Not supported

8 Fax Class 2

<ST>: Scan Time/Line

VR = normal VR = fine

0 0 ms 0 ms

1 5 ms 5 ms

2 10 ms 10 ms

3 10 ms 10 ms

4 20 ms 20 ms

5 20 ms 20 ms

6 40 ms 40 ms

7 40 ms 40 ms

Comments

The equivalent AT command according to EIA = AT+FCC

+FCS - Current Session Parameter


Description

Read command reads the current values.

Test command shows if a parameter is implemented.

Parameter-Values

See previous chapter (AT+FCC).


+FCS? +FCS: <VR>,< BR>,<WD>,<LN>,<DF>,<EC>,<BF>,<ST>

+FCS=? List of <VR>s,< BR>s, <WD>s, <LN>s, <DF>s, <EC>s, <BF>s, <ST>s

Fax Class 2 69

7

+FDR - Fax Data Receive Command


Description

The command initiates transition to Phase C data reception. This can occur after answering, after dialing, after a document received or after a page is received.

The TA shall report the negotiated T.32 [26] parameters, with the remote ID and NSS frame information if available. When TA is ready to commence data transfer, it will issue a CONNECT response code, optionally preceded by the block mode count. If the TA cannot resume data transfer, because there is no more data, it shall respond OK. When the TE is ready to accept data, it shall issue a <DC2> character (018) to the TA.

If the TE issue an <XOFF> character to the TA for flow control. the TA when its buffers are empty, by sending a <DLE><DC2>(<016><018> character pair. In block mode, this must be delayed until after the block transfer is complete.

When the TA delivers that last byte of page or partial page, the TA shall report the Page Transfer Status via the +FPS:<ppr> response. After Page Transfer Status Report, the TA shall report the post page message from the remote facsimile station via the +FET:<ppm> response.

The TA shall hold the post page response message to the remote facsimile station (MCF), etc, represented in the +FPS parameter until the next +FDR command. The TE may modify the +FPS parameter before issuing the +FDR command, which release that message. The TE must issue a +FDR command to release Post Page Messages.

The +FDR Command may be issued in Phase B after an answer command, or in Phase B after previous document. The TA responses shall be as follows:

Stream mode:

• +FCFR when CFR sent AAAA

• [FNSS:<NS FIF data] if new NSS received AAAA

• [FTSI:<remoteID>] if new TSI received AAAA

• [+FCS:<negotiated sub-parameters>] if new DCS AAAA

• CONNECT


+FDR See Description

0 Fax Class 2

+FDT - Fax Data Transmission Command


Description

The FDT command prefixes Phase C data transmission. When the TA is ready to accept Phase C data transmission, it will issue the negotiation response and the CONNECT result code to the TA.

In Phase B, the +FDT command releases the TA to proceed with negotiation and release the DCS message to remote station. In Phase C, +FDT command resumes transmission after the end of prior transmit data stream Block.

Parameter-Values <DF>: Data Compression Format

0 1-D modified Huffman

1 2-D modified Read, Optional 2 2-D uncompressed mode, Optional 3 2-D modified Read, Optional <VR>: Vertical Resolution

0 Normal, 98 dpi

1 Fine, 196 dpi

<WD>: Page width

0 1728 pixels in 215 mm

1 2048 pixels in 255 mm, Optional 2 2432 pixels in 303 mm, Optional 3 1216 pixels in 151 mm, Optional 4 864 pixels in 107 mm, Optional <LN>: Page Length

0 A4, 297 mm

1 B4, 364, Optional 2 unlimited length, Optional


AT+FDT=[<DF>,<VR>,<wd>,<LN>]

AT+FDT=? +FDT: (List of supported <DF>s, <VR>s, <wd>s, <LN>s)

Fax Class 2 71

7

+FEA - Phase C received EOL alignment


Description

This parameter enables optional octet-alignment of EOL markers in received T.4 data streams. It does not apply to T.6 data, or to any other form of data (e.g. T.434 BFT).


0 Determines that T.4 EOL patterns are bit aligned (as received).

1 Determines that the last received bits of T.4 EOL patterns are octet aligned by the TA, with necessary zero fill bits inserted.

There are two 2- octet patterns:

+FBO= binary EOL pattern

0 or 2 0000xxxx 10000000

1 or 3 xxxx0000 00000001 xxxx represent previous data bits, zero bits, or other leading data.

As per 4.2.2/T.4, the tag bit for two dimensional coding, which indicates the coding used for the following line, shall be included in that line in the octet following the previous EOL.

+FET - Page Punctuation


Description

This command is used to punctuate page and document transmission, after one or more +FDT commands. This command generates T.30 Post Page Messages, by the <ppm> code. The +FET=<ppm> command indicates that the current page or partial page is complete; no more data will be appended to it. The value indicates if any additional page are to be sent and, if so, whether there is a change in any of the document parameters. The TE can command the


+FEA=<value>

+FEA=? +FEA: (List of supported <value>s)


+FET=<ppm>[,<px>,<bc>,<fc>]

+FET? Current <values>

+FET=? <range of values>

2 Fax Class 2

TA to generate PRI-Q message with +FDT=<ppm>, command using ppm codes 4-6 (see section Parameter-Values). This command must be sent within the timeout specified by the +FPHCTO after sending Phase C data, else the TA must end the page and document transmission. If the Phase C data timeout is reached, the TA shall send an EOP post message and terminate the session.

Parameter-Values <ppm>:

0 another page next, same document

1 another document next.

2 no more page or documents

3 another partial page next,

4 another page, procedure interrupt,

5 another document, procedure interrupt,

6 all done, procedure interrupt,

7 continue to correct,

8-15 End-of-Retransmission (8) + Post page Message,

<pc>: Parameter Page Count defined in A.4.3.1/T.30[24],

<bc>: Parameter Block Count defined in A.4.3.1/T.30[24],

<fc>: Parameter Frame Count defined in A.4.3.1/T.30[24],

+FIE - Procedure interrupt enable


Description

Recommendation T.30 provides for either station to initiate Procedure Interrupts. The other station may choose to accept or ignore these requests. A service Class 2 facsimile TA may negotiate or ignore Procedure Interrupts, conditioned by this parameter.

Parameter-Values < value>

0 Procedure Interrupt Requests from the remote station are ignored, and not reported to the TE. For the +FET: response (T.30 phase A responses), PRI-Q reports will be replaced by non-PRI equivalents.


+FIE=<value>

+FIE? Current <value>

+FIE=? <range of values>

Fax Class 2 73

7

1 Procedure Interrupt Requests from the remote station are accepted, , negotiated and reported using the +FVO response ( T.30 phase B negotiation responses).

Comments

For transmission (+FDT), Procedure Interrupt Requests from the remote station are not reported directly; only the +FVO response is reported.

For reception (+FDR), Procedure Interrupt Requests from the remote station are reported in the +FET: response. The value stored in the +FPS parameter will be adjusted to values 4 or 5. If the TE issues a subsequent +FDR command with the +FPS value intact, the TA will complete the negotiation and issue a +FVO response.

+FIP - Initialise Fax Parameters


Description

The +FIP command causes the TA to initialize all Service Class 2 Facsimile Parameters to the manufacturer determined default settings. This command does not change the setting of +FCLASS. This command has the same effect as if the TE had issued individual parameter setting commands.

This command may be issued during a session. The TA shall use the new settings at the next time they are sampled; for example, a new +FIS setting would be used the next time the TA enters Phase B.

Parameter-Values

See “+FCLASS - Select Mode”, page 65.

Comments

Manufacturers may also provide a selection of default profiles, chosen by the optional <value>. For other <value>s, the manufacturer determines the profile settings.


+FIP =<value>

+FIP? Current <value>

+FIP =? <range of values>

4 Fax Class 2

+FIS - Current Session Negotiation Parameter


Description

The AT+FIS parameter allows the TE to sends and constrain the capabilities used for the current session. The TA uses +FIS to generate DIS or DTC message directly, and uses +FIS and received DIS message to generate DCS messages.

The TA shall initialize the +FIS parameter from the +FCC parameter on initialization, when +FCC is written, and at the end of session.

Parameter-Values

See “+FCC - TA Capability Parameter”, page 67.

Comments

The equivalent AT command according to EIA is +FDIS

+FIT - Inactivity timeout


Description

A service Class 2 facsimile TA shall provide an inactivity timer that allows the TA to break away from an unsuccessful connection attempt at any stage of a facsimile transfer. The inactivity timer only works while the TA is off-hook.


+FIS=<VR>,< BR>,<WD>, <LN>,<DF>,<EC>,<BF>,<ST>

+FIS? +FIS: <VR>,<BR>,<WD>,<LN>,<DF>,<EC>, <BF>,<ST>

+FIS=? List of <VR>s, <BR>s, <WD>s, <LN>s, <DF>s, <EC>s, <BF>s, <ST>s


+FIT=<time>,<action>

+FIT? Current <time>, <action>

+FIT=? <range of time>, <action>

Fax Class 2 75

7

Parameter-Values <time> indicates the inactivity timeout in seconds. The required timeout is 1

to 255 seconds. The value of 0 indicates that timeout is disabled. Any values greater than 255 are optional values for the TA manufacturer. Default value = 0

<action> The <action> parameter has two meanings. The inactivity timer starts when the TA has taken some action that requires TE response. If the TE does respond, the TA shall reset the inactivity timer. Tables 25 and 26 define these sets of events. Default value = 0

Comments

For inactivity timer start and stop events see T.32 [26] Table 25.

+FKS - Session Termination


Description

The +TF command causes the TA to terminate the session in orderly manner. In particular, it will send a DCN message at the next opportunity and hang up. At the end of termination process, the TA shall report the +FHNG response with result code.

This operation can be invoked by using the ASCII <CAN> (cancel) character during Phase C data reception. The TA should wait until the current page completes, except in reception of unlimited length, in that case, the TA may halt reception and terminate at any time. On receipt of <CAN > character, in block or stream mode, the TA shall terminate reporting of received data by sending trailing <DLE><ETX> characters to the TE and the TE shall execute an implied +FKS command, conducting an orderly disconnection. If the <CAN> character is followed by any other characters before the TA returns an “OK” response. The TA may abort the session and hang up.

Parameter-Values

Comments

The equivalent AT command according to EIA is +FK.


+FKS

6 Fax Class 2

+FLI - Local ID String


Description

The TA shall send the corresponding ID frame if either +FLI or +FPI is not a null string. +FLI is used for CSI or TSI; +FPI is used for CIG. Table 3/T.30 [25] includes digits 0-9, “+” and space.

The TA shall transmit ID string characters to the remote station in reversed time order from the order in the command line. For example, if the command line:

ATFLI=“1 234 567 8901”<CR> is issued, the TA would send a CSI or TSI frame with FIF (hexadecimal) consisting of:

<20><20><20><20><20><31><30><39><38><20><37><36><35><20><34> <33><32><20><31><2B>

The +FLI=? or +FPI=? test commands reports the range of character values supported. For example, if the TA supports use of Table 3/T.30 only, the response to a +FLI=? command is “(20,2B,30-39)” (hexadecimal values); if the TA supports printable T.50, the response is: “(20-7E)”.

If less than 20 characters are specified in a non-null string, the TA shall append space characters (2/0). If the specified string is more than 20 characters in length, an ERROR result code is generated.

Parameter-Values <local id string>: Valid values are 20 character ASCII string, default value

manufacture.s option. Mandatory values are 20 character numeric string, table 3/T.30 [24].

Comments

The equivalent AT command according to EIA is +FLID

1 If the TAE supports Table 3/T.30 only

2 If the TAE supports printable ASCII only


+FLI=“<local id string>”+ FLI? “<local id string>”+ FLI=? “(20((32,43,48-57)” 1

“(20)(32-127)<CRLF>” 2

Fax Class 2 77

7

+FPI - Local Polling ID String


Description

See “+FLI - Local ID String”, page 77.

Parameter-Values

See “+FLI - Local ID String”, page 77.

+FLP - Indicated Document to Poll


Description

This command is used to indicate document to poll.


0 indicates that the TE has a document to poll. Default value 1 indicates that the TE has a document ready for polling. The TA

reports this to the remote station in DIS frame. The TA shall reset this parameter to 0 after a polled document is sent.

Comments

The equivalent AT command according to EIA is +FLPL


+FPI=“<local id string>”+FPI? +FPI:“< local polling ID string >”+FPI=? +FPI:“(20((32,43,48-57)” 3

“(20)(32-127)<CRLF>” 4


+FLP=<value>

+FLP? <value>

+FLP=? <range of values>

8 Fax Class 2

+FNR - Negotiation reporting


Description

+FNR is a compound parameter, used to control the reporting of messages generated during T.30 Phase B negotiations.

Parameter-Values

There are four switches, for four types of reports.

These switches are described in T.32 [26] Table 22:


+FNR=<rpr>,<tpr>,<idr>,<nsr>

+FNR? <value>

+FNR=? List of supported <value>s

Fax Class 2 79

8

TABLE 22T.32 FNR switch sub-parameters

+FPP - Packet protocol control


Description

This command enable/disables the TA-to-TE Packet Protocol.

This command takes effect after the +FPP command is executed, before the final result code is issued by the TA. If this command is embedded in a command line containing multiple commands, it applies to information text and result codes of subsequent commands.

Switch setting

Message reference

Description

rpr=0 rpr=1

8.4.2.1 Receiver parameters are not reported +FIS: and +FTC: reports are suppressed. Receiver parameters are reported +FIS: and +FTC: reports are generated.

tpr=0 tpr=1

8.4.2.1 Transmitter parameters are not reported +FCS: reports are suppressed (+FCS parameter is still loaded). Transmitter parameters are reported +FCS: reports are generated

idr=0 idr=1

8.4.2.3 ID strings are not reported. +FTI:, +FCI: and +FPI: reports are suppressed ID strings are reported. +FTI:, +FCI: and +FPI: reports are generated

nsr=0 nsr=1

8.4.2.4 Non-standard frames are not reported. +FNF:, +FNS: and +FNC: reports are suppressed. Non-standard frames are reported. +FNF:, +FNS: and +FNC: reports are generated

Note! 1 If tpr=0, the negotiated image data format will not be reported. Without that report, the TE must send image data that is mandated by Recommendation T.30 (normal resolution, A4 length, 1728 width, 1-D coding) or it must enable the corresponding format conversion (+FFC). Otherwise, the data format negotiated and the data format sent might not match, causing the facsimile session to fail. 2 The use of additional sub-parameters for +FNR, in order to control reporting of future optional T.30 negotiation reports, is for future study.


+FPP=<value>

+FPP? <value>

+FPP=? List of supported <value>s

0 Fax Class 2


0 Disables the TA-to-TE Packet Protocol.

1 Enables the TA-to-TE Packet Protocol (clause 9). All multi-character messages from the TA are sent to the TE using a simple Packet Protocol data link, to assure reliable delivery of data.

+FPS - Page Transfer Status


Description

The +FPS parameter contains a value representing the post page response, including copy quality and related end of-page status. These values correspond to post page response message defined in T.30 [25]. The receiving TA sets this parameter after it receives a page of Phase C data. The transmitting TA sets this parameter with the status reported by the receiving station. The TA may inspect or modify this parameter with the status reported by the receiving station.

Parameter-Values <ppr>

1 Page good, Valid value for +FPS, Default value

2 Page bad, retrain requested, Valid value for +FPS

3 Page good, retrain requested, Valid value for +FPS

Comments

The equivalent AT command according to EIA = +FPTS


+FPS=[<ppr>]

+FPS? +FPS: <ppr>s

+FPS=? +FPS: (list of supported <ppr>s)

Fax Class 2 81

8

+FSP - Request to Poll


Description

This command is used to Request for polling.


0 Indicates that the TE does not want to poll. Default 1 Indicates that the TE can receive a polled document. The TA shall

reset this parameter to 0 after a polled document is received, Mandatory

Comments

The equivalent AT command according to EIA = +FSPL

+FIS:

See “+FIS:”, page 82.

+FTC: Report DTC frame information

Syntax

Description

+FTC: report remote facsimile station capabilities and intentions

Parameter-Values

See “+FCC - TA Capability Parameter”, page 67


+FSP=<value>

+FSP? <value>

+FSP=? List of supported <value>s

Response

+FTC: <VR>,<BR>,<WD>,<LN>,<DF>,<EC>,<BF>,<ST>

2 Fax Class 2

+FHR: - Report received HDLC frames

Syntax

Description

This reports the HDLC data that was received by the TA.

Parameter-Values

The frame octets will be represented in hex notation and separated by spaces. The TA shall delete HDLC Flags and FCS octets. Frame octets are reported in the order sent or received. An example received DIS string report is shown:

+FHR: FF 13 80 00 4E 78 FE AD<CR><LF>

+FHS - Call termination status


Description

This read only parameter indicates the cause of a hang-up. +FHS is set by the TA at the conclusion of a fax session. The TA shall reset this parameter to 0 at the beginning of Phase A.


0 Another page next, same document.

1 Another document next.

2 No more pages or documents.

3 Another page next, same document, procedure interrupt requested.

4 Another document next, procedure interrupt requested.

5 No more pages or documents, procedure interrupt requested.

Response

+FHR: <received HDLC frame octets>

Response

+FHS? <value>

Fax Class 2 83

8

+FCI: - Called station id (CSI)

Syntax

Description

These responses report the received Called station ID string. The TA shall report the characters in the ID string in reversed time order from the order received from the remote station.

Parameter-Values “<CSI ID string>” Called Station ID

+FCS: - Report DCS frame information

See “+FCS - Current Session Parameter”, page 69.

+FTI: - Remote station id (TSI)

Syntax

Description

These responses report the received remote station ID string. The TA shall report the characters in the ID string in reversed time order from the order received from the remote station

Parameter-Values “<TSI ID string>” Transmit Station ID

Response

+FCI: “<CSI ID string>”

Response

FTI: “<TSI ID string>”

4 Fax Class 2

+FPI: - Report Remote id, CIG

Syntax

Description

These responses report the received CIG ID string. The TA shall report the characters in the ID string in reversed time order from the order received from the remote station.

Parameter-Values “<CIG ID string>” Polling Station ID

+FPS: - Page status report

See “+FPS: - Page status report”, page 85.

+FPO: - Remote polling indication


Description

+FPO indicates that the remote station has a document to poll and invites the TE to poll it. The +FPO response is delivered between the +FIS:<string>, and the OK final result code, if enabled. The TE may respond to a +FPO message with either a +FDR command, to poll the remote station, or a +FDT command, if it does not wish to poll.

Response

FPI: “< CIG ID string>”

Response

+FPO

Fax Class 2 85

8

+FNC: - Report non-standard command frame

+FNF: - Non standard facilities report

+FNS: - Non standard setup report

Syntax

Description

These responses report any received Non-Standard negotiation frames, one response per frame. Originate (ATD), Answer (ATA), Data transmission (+FDT) or Data reception (+FDR) command execution may generate these responses if the corresponding frames are received.

The NSF Facsimile Information Field (FIF) frame octets (beginning with the country code, but not including the FCS) are presented in hex notation, and separated by spaces. HDLC flags, and zero bits inserted for transparency are removed. Frame octets are reported in the order received. For each frame octet the LSB is the first bit sent or received. For example, the two octet bit string 0001101101000101 would be reported D8 A2.

The facsimile TA reports the frame; it need not act on it. Specification of any other Non Standard behaviour is beyond the scope of this Recommendation.

Parameter-Values <NSF FIF string> Non-Standard Facilities;

<NSS FIF string> Non-Standard Setup;

<NSC FIF string> Non-Standard Commands.

+FET

See “+FET - Page Punctuation”, page 72.

Response

+FNC: <NSC FIF string>

+FNF: <NSF FIF string>

+FNS: <NSC FIF string>

6 Fax Class 2

+FCO: - indicates connection with a fax terminal

Syntax

Description

The +FCO response indicates connection with a Group 3 facsimile station.

The TA shall deliver this message to the TE upon detection of HDLC flags in the first received frame, in execution of Originate commands (ATD) or Answer commands (ATA) only.

+FDM:


Description

+FDM response indicates that the TA has identified that the calling device is a data modem. The TA shall issue this response immediately upon recognition of a data modem. For example, the TA might detect a V.32 AA pattern, or V.22 bis S1 signal, or V.25 1300 Hz calling tone. The +FDM response shall precede any data modem information text or result codes (e.g. CONNECT).

The TE should respond to a +FDM message by preparing itself to handle a data call. The +FDM response is enabled by TE command to set the FAA parameter to 1 (+FAA). The TE should not set +FAA_1 unless it is able to handle this result.

FDM response indicates that the TA has identified that the calling device is a data modem. The TA shall issue this response immediately upon recognition of a data modem. For example, the TA might detect a V.32 AA pattern, or V.22 bis S1 signal, or V.25 1300 Hz calling tone. The FDM response shall precede any data modem information text or result codes (e.g. CONNECT).

The TE should respond to a FDM message by preparing itself to handle a data call. The FDM response is enabled by TE command to set the FAA parameter to 1 (+FAA). The TE should not set FAA_1 unless it is able to handle this result.

Response

+FCO

Response

+FDM

Fax Class 2 87

8

+FHT: - Report transmit HDLC frames

Syntax

Description

Report transmit HDLC frames

Parameter-Values

See chapter +FHR section Parameter-Values.

Response

FHT:<transmitted HDLC frame octets>

8 Fax Class 2

GSM 07.10 Multiplexor Protocol

+CMUX - Multiplexing Mode


Description

This command is used to enable/disable the GSM 07.10 [19] multiplexing protocol control channel. The AT command sets parameters for the Control Channel. If the parameters are left out, the default value is used. Read command returns the current mode and the settings. Test command returns the supported modes and parameters.

Parameter-Values <transparency> with the following values:

0 means No transparency

1 means HDLC Transparency Not supported

<subset> with the following values:

0 means that only UIH frames used.

<port_speed> with the following values:

5 means 115200bits/s

<N1> with the following values:

1...128 means maximum frame size. Not supported.


+CME ERROR: <err>

+CMUX=<transparency>[,<subset>[,<port_speed>[,<N1>[,<T1>[,<N2>[,<T2>[,<T3>[,<k>]]]]]]]]

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

+CMUX=? +CMUX: (list of supported <mode>s), (list of supported <subset>s), (list of supported <port_speed>s), (list of supported <N1>s), (list of supported <T1>s), (list of supported <N2>s), (list of supported <T2>s), (list of supported <T3>s), (list of supported <k>s)

GSM 07.10 Multiplexor Protocol 89

9

31 maximum frame size. Default

<T1> with the following values:

1...255 means Acknowledgement timer (tens of milliseconds) Not supported.

10 means 100ms default timer.

<N2> with the following values:

1...100 means maximum number of re-transmission Not supported. 3 means default number of re-transmission


2...255 means Control Channel response timer (tens of milliseconds)

Not supported. 30 means 300ms default timer.


1...255 means wake up response timer (seconds) Not supported. 10 means 10s default timer

<K> with the following values:

1...7 means Window size Not supported.

<err> Refer to subclause 25.1

Comments

The +CMUX command allows multiple virtual channels to be setup over one physical channel. The current requirements call for support of 3 virtual channels. One dedicated to command/status, one dedicated to data calls and the other is a spare channel. Per the 07.10 specification DLC0 is reserved as the control channel for the 07.10 protocol. An additional virtual channel for message tracing should be added and the following conventions for numbering the virtual channels should be established:

• DLC1 - Dedicated command/status channel

• DLC2 - Dedicated data channel

• DLC3 - Message Log channel

• DLC4 - Spare

0 GSM 07.10 Multiplexor Protocol

GSM TE-TA Interface 91

GSM TE-TA Interface

+CSCS - Select TE Character Set


Description

Set command is used to inform the TA which character set is used by the TE. TA is then able to convert character strings correctly between TE and ME character sets.

When TA-TE interface is set to 8 bit operation and the current alphabet of the TE is 7 bit, the highest bit must be set to 0.


Test command is used to show the list of the supported character sets.

Parameter-Values <chset>

“GSM” GSM 7-bit alphabet

“IRA” International Reference Alphabet. Default. “8859-n” ISO 8859 Latin n (1-6) character set.

Comments

Characterset conversions for SMS text mode can be found in GSM 07.05 [17] Annex A.


+CSCS=[<chset>]

+CSCS? +CSCS: <chset>

+CSCS=? +CSCS: (list of supported <chset>s)

9

GSM Call Control

+CRC - Cellular Result Code



Description

Set command is used to control whether or not the extended format of incoming call indication is used. When enabled, an incoming call is indicated to the TE with unsolicited result code +CRING instead of the normal RING.


Test command is used to show the list of the supported modes.


0 Disable extended format

1 Enable extended format

<type>:

ASYNC asynchronous transparent

REL ASYNC asynchronous non-transparent

FAX facsimile (TS 62)

GPRS <PDP_type>, <PDP_addr> GPRS network request for PDP context activation.

<PDP_type> both parameters are defined in

<PDP_addr> the Define PDP Context (+CGDCONT) command.


+CRC=[<mode>]

+CRC? +CRC:<mode>

+CRC=? Supported <mode>s

+CRING: <type>

RING

2 GSM Call Control

+CR - Service Reporting control


Intermediate Result Codes

Description

Set command controls whether or not intermediate result code +CR is returned from the TA to the TE. If enabled, the intermediate result code is transmitted at the point during connect negotiation at which the TA has determined which speed and quality of service will be used, before any error control or data compression reports are transmitted, and before the intermediate result code CONNECT is transmitted.


Comments

This command replaces V.25ter [28] command Modulation Reporting Control +MR, which is not appropriate for use in the GSM network. Possible error control (other than radio link protocol) and data compression reporting can be enabled with V.25ter [28] commands Error Control Reporting +ER and Data Compression Reporting +DR.

Parameter-Values <mode>:

0 disables reporting. Default. 1 enables reporting

<serv>

ASYNC asynchronous transparent

REL ASYNC asynchronous non-transparent

GPRS XXX GPRS (XXX is a text string, the variable contents of which are

specified in 07.60)


+CR=[<mode>]

+CR? +CR: <mode>

+CR=? +CR: (list of supported <mode>s)

+CR: <serv>

GSM Call Control 93

9

GSM Data/Fax

+CBST - Select bearer service type


Description

Set command selects the bearer service <name> with data rate <speed>, and the connection element <ce> to be used when data calls are originated (refer GSM 02.02 [1]). Values may also be used during mobile terminated data call setup.

Test command returns values supported by the TA as compound values.

Parameter-Values

Note! Not all combinations of these sub-parameters are supported by GSM (refer GSM 02.02 [1]).

<speed>:

7 9600 bps (V.32) Default.

12 9600 bps (V.34)

14 14400 bps (V.34)

15 19200 bps (V.34)

16 28800 bps (V.34)

71 9600 bps (V.110 or X.31 flag stuffing)





<name>:

0 data circuit asynchronous (UDI or 3.1 kHz modem)

<ce>:

0 transparent. Default.


+CBST=[<speed>[,<name>[,<ce>]]]

+CBST? +CBST: <<speed>[,<name>[,<ce>

+CBST=? +CBST: (list of supported <speed>s), (list of supported <name>s), (list of supported <ce>s)

4 GSM Data/Fax

1 non-transparent

+CRLP - Radio link protocol


Description

Radio link protocol (RLP) parameters used when non-transparent data calls are originated may be altered with set command. Available command sub-parameters depend on the RLP versions implemented by the device (e.g. <ver> may not be available if device supports only versions 0 and 1).

Note! If radio link protocol (RLP) is not used, but some other error correcting protocol (for transparent data calls), V.25ter [28] Error Control Selection test command +ES=? may be used to indicate the presence of the protocol.

Read command returns current settings for each supported RLP version <verx>. Only RLP parameters applicable to the corresponding <verx> are returned.

Test command returns values supported by the TA as a compound value. If ME/TA supports several RLP versions <verx>, the RLP parameter value ranges for each <verx> are returned in a separate line.

Parameter-Values <ver>, <verx>: RLP version number in integer format; when version indication is not

present it shall equal 0


+CRLP=[<iws>[,<mws>[,<T1>[,<N2>[,<ver>[,<T4>]]]]]]

+CRLP? +CRLP: <iws>,<mws>,<T1>,<N2>[,<ver1>[,<T4>]] [<CR><LF> +CRLP: <iws>,<mws>,<T1>,<N2>[,<ver2>[,<T4>]] [...]]

+CRLP=? +CRLP: (list of supported <iws>s), (list of supported <mws>s), (list of supported <T1>s),(list of supported <N2>s)[,<ver1> [,(list of supported <T4>s)]] [<CR><LF> +CRLP: (list of supported <iws>s), (list of supported <mws>s), (list of supported <T1>s),(list of supported <N2>s) [,<ver1>[,(list of supported <T4>s)]] [...]]

GSM Data/Fax 95

9

Note! Versions 0 and 1 share the same parameter set. Read and test commands shall return only one line for this set (where <verx> is not present).

<iws>, <mws>, <T1>, <N2>, <T4>: IWF to MS window size, MS to IWF window size, acknowledgement timer T1, retransmission attempts N2, resequencing period T4 in integer format (default values and ranges depend on RLP version; refer GSM 04.22 [8]): T1 and T4 are in units of 10 ms.

6 GSM Data/Fax

GSM Network Reporting

+CNUM - Subscriber


Description

Action command returns the MSISDNs related to the subscriber (this information can be stored in the SIM). If subscriber has different MSISDN for different services, each MSISDN is returned in a separate line.

Test command Is a command that shows if the command is supported.

Parameter-Values <alphax>: optional alphanumeric string associated with <numberx>; used

character set should be the one selected with command Select

TE Character Set +CSCS.

<numberx>: string type phone number of format specified by <typex>.

<typex>: type of address octet in integer format (refer GSM 04.08 [13]

subclause 10.5.4.7).



+CME ERROR: <err>

+CNUM +CNUM: [<alpha1>],<number1>,<type1> [<CR><LF> +CNUM: [<alpha2>],<number2>,<type2>] [...]

+CNUM=?

GSM Network Reporting 97

9

*EBSE - Band Selection


Description

This command is used to select the band of operation. AT*EBSE? is the read command that returns the current band and AT*EBSE=? Returns the supported bands.


Parameter-Values <band>

0 GSM 900

1 DCS 1800

2 Dual Band

3 PCS 1900

4 Auto


+CME ERROR: <err>

*EBSE=[<band>]

*EBSE? *EBSE: <band>

*EBSE =? *EBSE: (list of supported <bands>s)

8 GSM Network Reporting

+CREG - Network Registration



Description

This command controls the presentation of an unsolicited result code +CREG when there is a change in the ME network registration status. AT+CREG? Is the read command that returns the status of the result code presentation and shows whether the network has currently indicated the registration of the ME.

Test command shows if the command is supported.

Parameter-Values <n>:

0 disable network registration unsolicited result code

1 enable network registration unsolicited result code +CREG: <stat>

2 enable network registration and location information unsolicited

result

<stat>

0 not registered, ME is not currently searching a new operator to register to

1 registered, home network

2 not registered, but ME is currently searching a new operator to register to

3 registration denied

4 unknown

5 registered, roaming

<lac> string type, two byte location area code in hexadecimal format

<ci> string type, two byte cell id in hexadecimal format


+CME ERROR: <err>

AT+CREG=[<n>]

AT+CREG? +CREG: <n>,<stat>[,<lac>,<ci>]

AT+CREG=? +CREG: (list of supported <n>s)

+CREG: <stat>

99 General

1


+COPS - Operator Selection


Description

Set command forces an attempt to select and register the GSM network operator. <mode> is used to select whether the selection is done automatically by the ME or is forced by this command to operator <oper> (it shall be given in format <format>). If the selected operator is not available, no other operator shall be selected (except <mode>=4). The selected operator name format shall apply to further read commands also. <mode>=2 forces an attempt to deregister from the network. The selected mode affects to all further network registration (e.g. after <mode>=2, ME shall be unregistered until <mode>=0 or 1 is selected). This command should be abortable when registration/deregistration attempt is made.

Read command returns the current mode and the currently selected operator. If no operator is selected, <format> and <oper> are omitted.

Test command returns a list of quadruplets, each representing an operator present in the network. Quadruplet consists of an integer indicating the availability of the operator <stat>, long and short alphanumeric format of the name of the operator, and numeric format representation of the operator. Any of the formats may be unavailable and should then be an empty field. The list of operators shall be in order: home network, networks referenced in SIM, and other networks.


0 (default) automatic (<oper> field is ignored)

1 manual (<oper> field shall be present)

2 deregister from network

3 set only <format> (for read command +COPS?), do not attemptregistration/deregistration (<oper> field is ignored); this value is not applicable in read command response


+CME ERROR: <err>

+COPS=[<mode>[,<format>[,<oper>]]]

+COPS? +COPS: <mode>[,<format>,<oper>]

+COPS=? +COPS: [list of supported (<stat>, long alphanumeric <oper>, short alphanumeric <oper>, numeric <oper>)s]


4 manual/automatic (<oper> field shall be present); if manual selection fails, automatic mode (<mode>=0) is entered

<format>

0 (Default) long format alphanumeric <oper>

1 short format alphanumeric <oper>

2 numeric <oper>

<oper>: string type; <format> indicates if the format is alphanumeric ornumeric; long alphanumeric format can be upto 16 characters long and short format up to 8 characters (refer GSM MoU SE.13 [22]); numeric format is the GSM Location Area Identification number (refer GSM 04.08 [13] subclause 10.5.1.3) which consists of a three BCD digit country code coded as in ITU-T E.212 Annex A [23], plus a three BCD digit network code, which is administration specific; returned <oper> shall not be in BCD format, but in IRA characters converted from BCD; hence the number has structure: (country code digit 3)(country code digit 2)(country code digit 1)(network code digit 2)(network code digit 1)

<stat>

0 unknown

1 available

2 current

3 forbidden



1

+CLIP - Calling Line Identification



Description

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. Set command (AT+CLIP = <n>) 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.

When the presentation of the CLI at the TE is enabled (and calling subscriber allows), +CLIP unsolicited result code response is returned after every RING (or +CRING; see “+CRC - Cellular Result Code”, page 92) result code sent from TA to TE.

Read command gives the status of <n>, and also triggers an interrogation of the provision status of the CLIP service according GSM 02.81 [5] (given in <m>).


Parameter-Values <n>: parameter sets/shows the result code presentation status in TA

0 Disable. Default 1 Enable

<m>: parameter shows the subscriber CLIP service status in the network

0 CLIP not provisioned

1 CLIP provisioned

2 unknown (e.g. no network, etc.)

<number>: string type phone number of format specified by <type>


+CLIP=[<n>]

+CLIP? +CLIP: <<n>, <m>

+CLIP=? +CLIP: (list of supported <n>s)

+CLIP: <number>,<type>[,<subadr>,<satype> [,<alpha>][<CLIvalidity]]]


<type>: type of address octet in integer format (refer GSM 04.08 [13] subclause 10.5.4.7)

<subaddr>: string type subaddress of format specified by <satype>

<satype>: type of subaddress octet in integer format (refer GSM 04.08 [13] subclause 10.5.4.8)

<alpha>: optional string type alphanumeric representation of <number> corresponding to the entry found in phone book; used character set should be the one selected with command Select TE Character Set +CSCS

<CLI validity>

0 CLI valid

1 CLI withheld by the originator.

2 CLI is not available due to interworking problems or limitations of originating network.

When CLI is not available (<CLI validity>=2), <number> shall be an empty string (“”) and <type> value will not be significant. Nevertheless, TA may return the recommended value 128 for <type> (TON/NPI unknown in accordance with GSM 04.08 [13] 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 [5] and GSM 03.81 [12]), <number> and <type> is provided. Otherwise, TA shall return the same setting for <number> and <type> as if the CLI was not available.

+CLIR - Calling Line Identification


Description

This command refers to CLIR-service according to GSM 02.81 [5] that allows a calling subscriber to enable or disable the presentation of the CLI to the called party when originating a call.

Set command overrides the CLIR subscription (default is restricted or allowed) when temporary mode is provisioned as a default adjustment for all following outgoing calls. This adjustment can be revoked by using the opposite command. If this command is used by a subscriber without provision of CLIR in permanent mode the network will act according GSM 02.81 [5].


+CLIR=[<n>]

+CLIR? +CLIR: <n>,<m>

+CLIR=? +CLIR: (list of supported <n>s)


1

Read command gives the default adjustment for all outgoing calls (given in <n>), and also triggers an interrogation of the provision status of the CLIR service (given in <m>).


Note! On a per call base CLIR functionality is explained in subclause “ITU-TV.25ter [28] dial command”.

Parameter-Values <n>: parameter sets the adjustment for outgoing calls:

0 presentation indicator is used according to the subscription of the CLIR service. Default.

1 CLIR invocation

2 CLIR suppression

<m>: parameter shows the subscriber CLIR service status in the network

0 CLIR not provisioned

1 CLIR provisioned in permanent mode


3 CLIR temporary mode presentation restricted

4 CLIR temporary mode presentation allowed

+COLP - Connected Line Identification


Intermediate Result Code

Description

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


+COLP=[<n>]

+COLP? +COLP: <n>,<m>

+COLP=? +COLP: (list of supported <n>s)

+COLP: <number>,<type>[,<subaddr>,<satype> [,<alpha>]]


disables the presentation of the COL at the TE. It has no effect on the execution of the supplementary service COLR in the network.

When enabled (and called subscriber allows), +COLP intermediate result code is returned from TA to TE before any +CR or V.25ter [28] responses. Read command gives the status of <n>, and also triggers an interrogation of the provision status of the COLP service according GSM 02.81 [5] (given in <m>).


Parameter-Values <n>: parameter sets/shows the result code presentation status in TA

0 disable. Default. 1 enable

<m>: parameter shows the subscriber COLP service status in the network

0 COLP not provisioned

1 COLP provisioned


<number>: refer 13.5 +CLIP

<type>: refer 13.5 +CLIP

<subaddr>: refer 13.5 +CLIP

<satype>: refer 13.5 +CLIP

<alpha>: refer 13.5 +CLIP

+CCFC - Call Forwarding Number and Conditions


Description

This command allows control of the call forwarding supplementary service according to GSM 02.82 [6]. Registration, erasure, activation, deactivation, and status query are


+CME ERROR: <err>

+CCFC=<reason>,<mode> [,<number>[,<type>[,<class>]]]

when <mode>=2 and command successful: +CCFC: <status>,<class1>[,<number>,<type> <satype>]][<CR><LF> +CCFC: <status>,<class2>[,<number>,<type>] [...]]

+CCFC=? +CCFC: (list of supported <reason>s)


1

supported. When querying the status of a network service (<mode>=2) the response line for .not active. case (<status>=0) should be returned only if service is not active for any <class>.

Test command returns reason values supported by the TA as a compound value.

Parameter-Values <reason>

0 unconditional

1 mobile busy

2 no reply

3 not reachable

4 all call forwarding (refer GSM 02.30 [3])

5 all conditional call forwarding (refer GSM 02.30 [3])

<mode>

0 disable

1 enable

2 query status

3 registration

4 erasure

<number>: string type phone number of forwarding address in format specified by <type>

<type>: type of address octet in integer format (refer GSM 04.08 [13] subclause 10.5.4.7); default 145 when dialling string includes international access code character “+”, otherwise 129

<classx>: is a sum of integers each representing a class of information (default 7):

1 voice (telephony)

2 data (refers to all bearer services; with <mode>=2 this may refer only to some bearer service if TA does not support values 16, 32, 64 and 128)

4 fax (facsimile services)

8 short message service

16 data circuit sync

32 data circuit async

64 dedicated packet access

128 dedicated PAD access


<status>

0 not active

1 active


<time>:

1...30 when “no reply” is enabled or queried, this gives the time in seconds to wait before call is forwarded, default value = 20.

+CSSN - Supplementary service notifications


Unsolicited Result codes

Description

This command refers to supplementary service related network initiated notifications. The set command enables/disables the presentation of notification result codes from TA to TE.

When <n>=1 and a supplementary service notification is received after a mobile originated call setup, intermediate result code +CSSI is sent to TE before any other MO call setup result codes presented in this spec or in V.25ter [28]. When several different <code1>s are received from the network, each of them shall have its own +CSSI result code.

When <m>=1 and a supplementary service notification is received during a mobile terminated call setup or during a call, or when a forward check supplementary service notification is received, unsolicited result code +CSSU is sent to TE. In case of MT call setup, result code is sent after every +CLIP result code (refer 13.5 command +CLIP “Calling line identification presentation”) and when several different <code2>s are received from the network, each of them shall have its own +CSSU result code.



+CME ERROR: <err>

+CSSN=[<n>[,<m>]]

+CSSN? +CSSN: <n>,<m>

AT+CLCK=? +CSSN: (list of supported <n>s), (list of supported <m>s)

+CSSI: <code1> [,<index>]

+CSSU: <code2> [,<index> [,<number>, <type> [,<subaddr>, <satype>]]]


1

Parameter-Values <n> sets/shows the +CSSI result code presentation status in the TA

0 disable. Default 1 enable

<m> sets/shows the +CSSU result code presentation status in the TA

0 disable. Default 1 enable

<code1> (it is manufacturer specific, which of these codes are supported):

0 unconditional call forwarding is active

1 some of the conditional call forwardings are active

2 call has been forwarded

3 call is waiting

4 this is a CUG call (also <index> present). Not supported. 5 outgoing calls are barred

6 incoming calls are barred

7 CLIR suppression rejected

8 call has been deflected. Not supported.

<index>: refer “Closed user group +CCUG”. Not supported.

<code2> (it is manufacturer specific, which of these codes are supported):

0 this is a forwarded call (MT call setup)

1 this is a CUG call (also <index> present) (MT call setup). Not supported.

2 call has been put on hold (during a voice call). Not supported. 3 call has been retrieved (during a voice call). Not supported. 4 multiparty call entered (during a voice call). Not supported.

5 call on hold has been released (this is not a SS notification)

(during a voice call). Not supported.

6 forward check SS message received (can be received whenever)

7 call is being connected (alerting) with the remote party in alertingstate in explicit call transfer operation (during a voice call). Not supported.

8 call has been connected with the other remote party in explicit call transfer operation (also number and subaddress parameters may be present) (during a voice call or MT call setup). Not supported.

9 this is a deflected call (MT call setup). Not supported.


<number>: string type phone number of format specified by <type>


<subaddr>: string type subaddress of format specified by <satype>. Not supported. <satype>: type of subaddress octet in integer format (refer GSM 04.08 [13]

subclause 10.5.4.8). Not supported.



1

GSM Facility Lock

+CLCK - Facility lock


Description

Execute command is used to lock, unlock or interrogate a ME or a network facility <fac>. Password is normally needed to do such actions. This command should be abortable when network facilities are set or interrogated.

Call barring facilities are based on GSM supplementary services (refer GSM 02.88 [7]). The interaction of these with other commands based on other GSM supplementary services is described in the GSM standard.

Test command returns facility values supported by the TA as a compound value.

Parameter-Values <fac> values reserved by this ETS:

“PS” PH-SIM (lock PHone to SIM card) (ME asks password when other than current SIM card inserted)

“SC” SIM (lock SIM card) (SIM asks password in ME power-up and when this lock command issued)

“AO” BAOC (Barr All Outgoing Calls) (refer GSM 02.88 [7] clause 1)

“OI” BOIC (Barr Outgoing International Calls) (refer GSM 02.88 [7] clause 1)

“AI” BAIC (Barr All Incoming Calls) (refer GSM 02.88 [7] clause 2)

“IR” BIC-Roam (Barr Incoming Calls when Roaming outside the home country) (refer GSM 02.88 [7] clause 2)

“OX” BOIC-exHC (Barr Outgoing International Calls except to Home Country) (refer GSM 02.88 [7] clause 1)

“NT” barr incoming calls from numbers Not stored to TA memory

“NM” barr incoming calls from numbers Not stored to ME memory


+CME ERROR: <err>

+CLCK=<fac>,<mode>[,<passwd> [,<class>]]

when <mode>=2 and command successful: +CLCK: <status>[,<class1>[<CR><LF> +CLCK: <status>,<class2> [...]]

+CLCK=? +CLCK: (list of supported <fac>s)

10 GSM Facility Lock

“NS” barr incoming calls from numbers Not stored to SIM memory

“NA” barr incoming calls from numbers Not stored in Any memory

“AB” All Barring services (refer GSM 02.30 [3])

“AG” All outGoing barring services (refer GSM 02.30 [3])

“AC” All inComing barring services (refer GSM 02.30 [3]) (applicable only for <mode>=0)

“FD” SIM fixed dialling memory feature (if PIN2 authentication has not been done during the current session, PIN2 is required as <passwd>)

<mode>:

0 unlock

1 lock

2 query status

10 full lock (only valid for fac = .PS., after power on always ask for password

<status>:

0 not active

1 active

<passwd>: string type; shall be the same as password specified for the facility from the ME user interface or with command Change Password +CPWD

<classx> is a sum of integers each representing a class of information (default 6):

2 data

4 fax


+CPWD - Change password


Description

Action command sets a new password for the facility lock function defined by command Facility Lock +CLCK.


+CME ERROR: <err>

+CPWD=<fac>,<oldpwd>,<newpwd>

+CPWD=? +CPWD: list of supported (<fac>, <pwdlength>)s

GSM Facility Lock 111

1

Test command returns a list of pairs which present the available facilities and the maximum length of their password.

Parameter-Values <fac>:

“PS” PH-SIM (lock PHone to SIM card) (ME asks password when other than current SIM card inserted)

“P2” SIM PIN2

“SC” SIM (lock SIM card) (SIM asks password in ME power-up and when this lock command issued)

“AO” BAOC (Barr All Outgoing Calls) (refer GSM 02.88 [7] clause 1)

“OI” BOIC (Barr Outgoing International Calls) (refer GSM 02.88 [7] clause 1)

“AI” BAIC (Barr All Incoming Calls) (refer GSM 02.88 [7] clause 2)

“IR” BIC-Roam (Barr Incoming Calls when Roaming outside the home country) (refer GSM 02.88 [7] clause 2)

“OX” BOIC-exHC (Barr Outgoing International Calls except to Home Country) (refer GSM 02.88 [7] clause 1)

“NT” barr incoming calls from numbers Not stored to TA memory

“NM” barr incoming calls from numbers Not stored to ME memory

“NS” barr incoming calls from numbers Not stored to SIM memory

“NA” barr incoming calls from numbers Not stored in Any memory

“AB” All Barring services (refer GSM 02.30 [3])

“AG” All outGoing barring services (refer GSM 02.30 [3])

“AC” All inComing barring services (refer GSM 02.30 [3]) (applicable only for <mode>=0)

“FD” SIM fixed dialling memory feature (if PIN2 authentication has not been done during the current session, PIN2 is required as <passwd>)

<oldpwd>: string type; <oldpwd> shall be the same as password specified for the facility from the ME user interface or with command Change Password +CPWD

<newpwd> is the new password; maximum length of password can be determined with <pwdlength>

<pwdlength>: integer type maximum length of the password for the facility


12 GSM Facility Lock

GSM Mobile Equipment Control and Status

+CPIN - Enter PIN


Description

The Set command sends to the ME a password which is necessary before it can be operated (SIM PIN, SIM PUK, PH-SIM PIN, etc.). If the PIN is to be entered twice, the TA shall automatically repeat the PIN. If no PIN request is pending, no action is taken towards ME and an error message, +CME ERROR, is returned to TE.

If the PIN required is SIM PUK or SIM PUK2, the second pin is required. This second pin, <newpin>, is used to replace the old pin in the SIM.

Read command returns an alphanumeric string indicating whether some password is required or not.

Parameter-Values <pin>: string type values (the range of the SIM PIN and the PH-SIM PIN is

4-8 bits).

<newpin>: same as <pin>

<code> values reserved by this ETS:

READY ME is not pending for any password

SIM PIN ME is waiting SIM PIN to be given

SIM PUK ME is waiting SIM PUK to be given

PH-SIM PIN ME is waiting phone-to-SIM card password to be given

PH-FSIM PIN: ME is waiting phone-to-very first SIM card password to be given

PH-FSIM PUK: ME is waiting phone-to-very first SIM card unblocking password to be given

SIM PIN2 ME is waiting SIM PIN2 to be given (this <code> is recommended to be returned only when the last executed command resulted in PIN2 authentication failure (i.e. +CME ERROR: 17); if PIN2 is not entered right after the failure, it is recommended that ME does not block its operation)


+CME ERROR: <err>

+CPIN=<pin>[,<newpin>]

+CPIN? +CPIN: <code>

+CPIN=?

GSM Mobile Equipment Control and Status 113

1

SIM PUK2 ME is waiting SIM PUK2 to be given (this <code> is recommended to be returned only when the last executed command resulted in PUK2 authentication failure (i.e. +CME ERROR: 18); if PUK2 and new PIN2 are not entered right after the failure, it is recommended that ME does not block its operation)

PH-NET PIN ME is waiting network personalisation password to be given

PH-NET PUK: ME is waiting network personalisation unblocking password to be given

PH-NETSUB PIN: ME is waiting network subset personalisation password to be given

PH-NETSUB PUK: ME is waiting network subset personalisation unblocking password to be given

PH-SP PIN ME is waiting service provider personalisation password to be given

PH-SP PUK ME is waiting service provider personalisation unblocking password to be given

PH-CORP PIN: ME is waiting corporate personalisation password to be given

PH-CORP PUK: ME is waiting corporate personalisation unblocking password to be given

<err> Refer to subclause 25.1

+CGSN - Request product serial number identification


Description

Execution command causes the TA to return one or more lines of information text <sn>, which is intended to permit the user of the TA to identify the individual ME to which it is connected to.

Parameter-Values <sn>: the total number of characters, including line terminators, in the

information text shall not exceed 2048 characters. Text shall not contain the sequence 0<CR> or OK<CR>


+CME ERROR: <err>

+CGSN <sn>

+CGSN=?

14 GSM Mobile Equipment Control and Status


+CSQ - Signal quality


Description

Execution command returns received signal strength indication <rssi> and channel bit error rate <ber> from the ME.

Test command returns values supported by the TA as compound values.

Parameter-Values <rssi>:

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> (in percent):

0...7 as RXQUAL values in the table in GSM 05.08 [16] subclause 8.2.4

99 not known or not detectable



+CME ERROR: <err>

+CSQ +CSQ: <rssi>, <ber>

+CSQ=? +CSQ: (list of supported <rssi>s), (list of supported <ber>s)

GSM Mobile Equipment Control and Status 115

1

GSM Mobile Equipment Error

+CEER - GSM Extended Error Reporting


Description

Execution command causes the TA to return one or more lines of information text <report>, determined by the ME manufacturer, which should offer the user of the TA an extended report of the reason of the failure in the last unsuccessful call setup (originating or answering) or in-call modification, or the reason for last call release. Typically, the text will consist of a single line containing the failure information given by GSM network in textual format.

Test command shows if the command is supported.

Parameter-Values <report>: one or more lines of information text (characters). See the Description

section.

Comments

The total number of characters including line terminators, in the information text (in <report>), shall not exceed 2041 characters. Text shall not contain the sequence 0<CR> or OK<CR>.


+CEER +CEER: <report>

+CEER=?

16 GSM Mobile Equipment Error

+CMEE - Report Mobile Equipment Error



Description

Set command disables or enables the use of result code +CME ERROR as an indication of an error relating to the functionality of the ME. When enabled, ME related errors cause +CME ERROR final result code instead of the regular ERROR final result code. ERROR is returned normally when error is related to syntax, invalid parameters, or TA functionality.


Parameter-Values <n>

0 disable +CME ERROR result code and use ERROR instead. Default. 1 enable +CME ERROR result code, use numeric <err> values

2 enable +CME ERROR result code, use verbose <err> values



+CMEE=[<n>]

+CMEE? +CMEE: <n>

+CMEE=? +CMEE: (list of supported <n>s)

+CME ERROR: <err>

GSM Mobile Equipment Error 117

1

SMS General Commands

Parameter Definitions

The following parameters are used in chapters SMS Text mode through to18.1 which describe all SMS commands. The formats of integer and string types referenced here are defined in chapter 2 and V.25ter [28]. The default values are for command parameters, not for result code parameters.

Message Storage Parameters <index> integer type; value in the range of location numbers supported by the

associated memory

<mem1> string type; memory from which messages are read and deleted (commands List Messages +CMGL, Read Message +CMGR and Delete Message +CMGD); defined values (others are manufacturer specific):

“BM” broadcast message storage

“ME” ME message storage

“MT” any of the storages associated with ME

“SM” SIM message storage

“TA” TA message storage

“SR” status report storage

<mem2> string type; memory to which writing and sending operations are made (commands Send Message from Storage +CMSS and Write Message to Memory +CMGW) ); refer <mem1> for defined values

<mem3> string type; memory to which received SMs are preferred to be stored (unless forwarded directly to TE; refer 17.8 command +CNMI - New Message Indications); refer <mem1> for defined values; received CBMs are always stored in “BM” (or some manufacturer specific storage) unless directly forwarded to TE; received status reports are always stored in “SR” (or some manufacturer specific storage) unless directly forwarded to TE

<stat> integer type in PDU mode (default 0), or string type in text mode (default “REC UNREAD”); indicates the status of message in memory; defined values:

0 “REC UNREAD” received unread message (i.e. new message)

1 “REC READ” received read message

2 “STO UNSENT” stored unsent message (only applicable to SMks)

3 “STO SENT” stored sent message (only applicable to SMs)

4 “ALL” all messages (only applicable to +CMGL command)

<total1> integer type; total number of message locations in <mem1>

18 SMS General Commands



<used1> integer type; number of messages currently in <mem1>



Message Data Parameters <ackpdu> GSM 03.40 [9] RP-User-Data element of RP-ACK PDU; format is

same as for <pdu> in case of SMS, but without GSM 04.11 [14] SC address field and parameter shall be bounded by double quote characters like a normal string type parameter

<alpha> string type alphanumeric representation of <da> or <oa> corresponding to the entry found in MT phone book; implementation of this feature is manufacturer specific; used character set should be the one selected with command Select TE Character Set +CSCS (see definition of this command in chapter AT+CSCS Select TE Character Set)

<cdata> GSM 03.40 [9] TP-Command-Data in text mode responses; ME/TA converts each 8-bit octet into two IRA character long hexadecimal number (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65)

<ct> GSM 03.40 [9] TP-Command-Type in integer format (default 0)

<da> GSM 03.40 [9] TP-Destination-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 10.1 and command +CSCS in GSM 07.07 [18]); type of address given by <toda>

<data> In the case of SMS: GSM 03.40 [9] TP-User-Data in text mode responses; format:

- if <dcs> indicates that GSM 03.38 [8] default alphabet is used and <fo> indicates that GSM 03.40 [9] TP-User-Data-Header-Indication is not set:

- if TE character set other than “HEX” (refer 10.1 and command +CSCS - Select TE Character Set - in GSM 07.07 [18]): ME/TA converts GSM alphabet into current TE character set according to rules of Annex A

- if TE character set is “HEX”: ME/TA converts each 7-bit character of GSM alphabet into two IRA character long hexadecimal number (e.g. character Ð (GSM 23) is presented as 17 (IRA 49 and 55))

- if <dcs> indicates that 8-bit or UCS2 data coding scheme is used, or <fo> indicates that GSM 03.40 [9] TP-User-Data-Header-Indication is set: ME/TA converts each 8-bit octet into two IRA character long hexadecimal number (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65)

In the case of CBS: GSM 03.41 [10] CBM Content of Message in text mode

SMS General Commands 119

1

responses; format:

- if <dcs> indicates that GSM 03.38 [8] default alphabet is used:

- if TE character set other than “HEX” (refer 10.1 and command +CSCS in GSM 07.07 [18]): ME/TA converts GSM alphabet into current TE character set according to rules of Annex A

- if TE character set is “HEX”: ME/TA converts each 7-bit character of GSM alphabet into two IRA character long hexadecimal number

- if <dcs> indicates that 8-bit or UCS2 data coding scheme is used: ME/TA converts each 8-bit octet into two IRA character long hexadecimal number

<dcs> depending on the command or result code: GSM 03.38 [8] SMS Data Coding Scheme (default 0), or Cell Broadcast Data Coding Scheme in integer format

<dt> GSM 03.40 [9] 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. E.g. 6th of May 1994, 22:10:00 GMT+2 hours equals to “94/05/06,22:10:00+08”

<fo> depending on the command or result code: first octet of GSM 03.40 [9] SMS-DELIVER, SMS-SUBMIT (default 17), SMS-STATUS-REPORT, or SMS-COMMAND (default 2) in integer format

<length> integer type value indicating in the text mode (+CMGF=1) the length of the message body <data> > (or <cdata>) in characters; or in PDU mode (+CMGF=0), the length of the actual TP data unit in octets (i.e. the RP layer SMSC address octets are not counted in the length)

<mid> GSM 03.41 [10] CBM Message Identifier in integer format

<mn> GSM 03.40 [9] TP-Message-Number in integer format

<mr> GSM 03.40 [9] TP-Message-Reference in integer format

<oa> GSM 03.40 [9] TP-Originating-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 10.1 and command +CSCS in GSM 07.07 [18]); type of address given by <tooa>

<page> GSM 03.41 [10] CBM Page Parameter bits 4-7 in integer format

<pages> GSM 03.41 [10] CBM Page Parameter bits 0-3 in integer format

<pdu> In the case of SMS: GSM 04.11 [14] SC address followed by GSM 03.40 [9] TPDU in hexadecimal format: ME/TA converts each octet of TP data unit into two IRA character long hexadecimal number (e.g. octet with integer value 42 is presented toTE as two characters 2A (IRA 50 and 65))

In the case of CBS: GSM 03.41 [10] TPDU in hexadecimal format

<pid> GSM 03.40 [9] TP-Protocol-Identifier in integer format (default 0)


<ra> GSM 03.40 [9] TP-Recipient-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 10.1 and command +CSCS in GSM 07.07 [18]); type of address given by <tora>

<sca> GSM 04.11 [14] 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 10.1 and command +CSCS in GSM 07.07 [18]); type of address given by <tosca>

<scts> GSM 03.40 [9] TP-Service-Centre-Time-Stamp in time-string format (refer <dt>)

<sn> GSM 03.41 [10] CBM Serial Number in integer format

<st> GSM 03.40 [9] TP-Status in integer format

<toda> GSM 04.11 [14] TP-Destination-Address Type-of-Address octet in integer format (when first character of <da> is + (IRA 43) default is 145, otherwise default is 129)

<tooa> GSM 04.11 [14] TP-Originating-Address Type-of-Address octet in integer format (default refer <toda>)

<tora> GSM 04.11 [14] TP-Recipient-Address Type-of-Address octet in integer format (default refer <toda>)

<tosca> GSM 04.11 [14] RP SC address Type-of-Address octet in integer format (default refer <toda>)

<vp> depending on SMS-SUBMIT <fo> setting: GSM 03.40 [9] TP-Validity-Period either in integer format (default 167) or in time-string format (refer <dt>)

<vp> depending on SMS-SUBMIT <fo> setting: GSM 03.40 [9] TP-Validity-Period either in integer format (default 167), in time-string format (refer <dt>), or if $(EVPF)$ is supported, in enhanced format (hexadecimal coded string with double quotes)


1

+CSMS - Select Message Service


Description

Set command selects messaging service <service>. It returns the types of messages supported by the ME: <mt> for mobile terminated messages, <mo> for mobile originated messages and <bm> for broadcast type messages. If chosen service is not supported by the ME, final result code +CMS ERROR shall be returned.

Parameter-Values <service>

0 GSM 03.40 and 03.41 (the syntax of SMS AT commands is compatible with GSM 07.05 Phase 2 version 4.7.0; Phase 2+ features which do not require new command syntax may be supported (e.g. correct routing of messages with new Phase 2+ data coding schemes). Default.

1 GSM 03.40 and 03.41 (the syntax of SMS AT commands is compatible with GSM 07.05 Phase 2+ version; the requirement of <service> setting 1 is mentioned under corresponding command descriptions)

<mt> Mobile terminated message

1 Mobile terminated message supported

<mo> Mobile originated message

1 mobile terminated message supported

<bm> same as <mt>

1 Mobile terminated message supported



+CMS ERROR: <err>

+CSMS=<service> +CSMS: <mt>, <mo>, <bm>

+CSMS? +CSMS: <service>, <mt>, <mo>, <bm>

+CSMS=? +CSMS: (list of supported <service>s)


+CPMS - Preferred Message Storage


Description

Set command selects memory storages <mem1>, <mem2> and <mem3> to be used for reading, writing, etc. If chosen storage is not appropriate for the ME, final result code +CMS ERROR shall be returned.

Test command returns lists of memory storages supported by the TA.

Parameter-Values <mem1> String type, memory from which message are read and deleted

(commands List Messages +CMGL, Read Message +CMGR and Delete Message +CMGD).

“ME” ME message storage

“SM” SIM message storage

<mem2> String type, memory to which reading and sending operation are made (commands Send Messages from Storage +CMSS, and Write Message to memory +CMGM and Delete Message +CMGD). See <mem1>.

<mem3> String type, memory to which received SMS messages are preferred to be stored (unless forwarded directly to TE). Received CBMs are always stored in .BM. (or some manufacture specific storage) unless directly forwarded to the TE.

<MT> Any of the storage associated with ME.

<used1> String type, Total number of messages currently in <mem1>.

<used2> string type, Total number of messages currently in <mem2>.

<used3> string type, Total number of messages currently in <mem3>.

<total1> total number of message locations in <mem1>.



<err> Refer to “+CMS ERROR . Message Failure Result Code”, page 191


+CMS ERROR: <err>

+CPMS=<mem1> [,<mem2>[,<mem3>]]

+CPMS: <used1>,<total1>,<used2>,<total2>, <used3>,<total3>

+CPMS? +CPMS: <mem1>,<used1>,<total1>,<mem2>, <used2>,<total2>,<mem3>,<used3>,<total3>

+CPMS=? +CPMS: (list of supported <mem1>s),(list of supported <mem2>s),(list of supported <mem3>s)


1

+CMGF - Message Format


Description

Set command tells the TA, which input and output format of messages to use. <mode> indicates the format of messages used with send, list, read and write commands and unsolicited result codes resulting from received messages. Mode can be either PDU mode (entire TP data units used) or text mode (headers and body of the messages given as separate parameters).

Test command returns supported modes as a compound value.

Parameter-Values

<mode>: 0 PDU mode. Default. 1 Text mode

+CSCA - Service Center Address


Description

Set command updates the SMSC address, through which mobile originated SMS.s are transmitted. In text mode, setting is used by send (+CMGS) and write (+CMGW) commands. In PDU mode, setting is used by the same commands, but only when the length of the SMSC address coded into <pdu> parameter equals zero.


+CMGF=[<mode>]

+CMGF? +CMGF: <mode>

+CMGF=? +CMGF: (list of supported <mode>s)


+CSCA=<sca>[,<tosca>]

+CSCA? +CSCA: <sca>, <tosca>

+CSCA=?


Parameter-Values <sca> String type, GSM 04.11 [14] 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.

<tosca> Integer type, GSM 04.11 [14] RP SC address Type-Of-Address octet in integer format.

129 ISDN/telephony numbering plan, national/international unknown, Default if no .+. in <sca>.

145 ISDN/telephony numbering plan, international number, Default if “+” in <sca>.

161 ISDN/telephony numbering plan, notional number

128-255 Other values refer GSM 04.08 [13] section 10.5.4.7.

Comments

Note! A “+” in front of the <sca> has precedence over the <tosca> parameter, so that a number starting with “+” will always be treated as an international number.

+CSCB Select Cell Broadcast Message Types


Description

Set command selects which types of CBMs are to be received by the ME.

Test command returns supported modes as a compound value.


0 message types specified in <mids> and <dcss> are accepted

1 message types specified in <mids> and <dcss> are not accepted

<mids> string type; all different possible combinations of CBM message identifiers (refer <mid>) (default is empty string); e.g. “0,1,5,320-478,922”

<dcss> string type; all different possible combinations of CBM data coding schemes (refer <dcs>) (default is empty string); e.g. “0-3,5”


+CSCB=[<mode>[,<mids>[,<dcss>]]]

+CSCB? +CSCB: <mode>, <mids>, <dcss>

+CSCB=? +CSCB: (list of supported <mode>s)


1

+CNMI - New Message Indications to TE


Description

Set command selects the procedure for how receiving of new 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 [8]. If the command fails and error is related to the ME or network, return final result code CMS ERROR: <err>.

Parameter-Values <mode> (refer figure 1;)

0 Buffer unsolicited result codes in the TA. If TA result code buffer is full, indications can be buffered in some other place or the oldest indications may be discarded and replaced with the new received indications.

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

Note! It is possible that ME/TA result code buffer is in volatile memory. In this case messages may get lost if the power of ME/TA is switched off before codes are sent to TE. Thus, it is not recommended to use direct message routing (<mt>=2 or 3, <bm>=2 or 3, or <ds>=1) with <mode> value 0 or 2.

<mt> (the rules for storing received SMs depend on its data coding scheme (refer GSM 03.38 [8]), preferred memory storage (+CPMS) setting and this value; refer table 1)

Note! If AT command interface is acting as the only display device, the ME must support storing of class 0 messages and messages in the message waiting indication group (discard message); refer table 2):


+CMS ERROR: <err>

+CNMI=[<mode>[,<mt> [,<bm>[,<ds>[,<bfr>]]]]]

+CNMI? +CNMI: <mode>, <mt>, <bm>, <ds>, <bfr>

+CNMI=? +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)


0 No SMS-DELIVER indications are routed to the TE. Default.

1 If SMS-DELIVER is stored into ME/TA, indication of the memory location is routed to the TE using unsolicited result code: +CMTI

2 SMS-DELIVERs (except class 2 messages and messages in the message waiting indication group (store message)) are routed directly to the TE using unsolicited result code: +CMT Class 2 messages and messages in the message waiting indication group (store message) result in indication as defined in <mt>=1.

3 Class 3 SMS-DELIVERs are routed directly to TE using unsolicited result codes defined in <mt>=2. Messages of other data coding schemes result in indication as defined in <mt>=1.


1

Table 1: <mt> parameter

Table 2: SMS-DELIVER result code and acknowledgement summary

<mt>Receiving procedure for different message data coding schemes (refer GSM 03.38 [8])

0 no class: as in GSM 03.38, but use <mem3> as preferred memory class 0: as in GSM 03.38, but use <mem3> as preferred memory if message is tried to be stored class 1: as in GSM 03.38, but use <mem3> as preferred memory class 2: as in GSM 03.38 class 3: as in GSM 03.38, but use <mem3> as preferred memory message waiting indication group (discard message): as in GSM 03.38, but use <mem3> as preferred memory if message is tried to be stored message waiting indication group (store message): as in GSM 03.38, but use <mem3> as preferred memory

1 as <mt>=0 but send indication if message stored successfully 2 no class: route message to TEclass 0: as in GSM 03.38, but also route

message to TE and do not try to store it in memory class 1: route message to TE class 2: as <mt>=1 class 3: route message to TE message waiting indication group (discard message): as in GSM 03.38, but also route message to TE and do not try to store it in memory message waiting indication group (store message): as <mt>=1 3 class 3: route message to TE

3 class 3: route message to TE

others: as <mt>=1

<mt>no class or class 1

class 0 or message waiting indication group (discard)

class 2 or message waiting indication group (store)

class 3

1 +CMTI [+CMTI1)] +CMTI +CMTI

2 +CMT & +CNMA3)

+CMT [& +CNMA2)] +CMTI +CMT & +CNMA3 )

3 +CMTI [+CMTI1)] +CMTI +CMT & +CNMA3)

1) result code is sent when ME does not have other display device than AT interface 2) acknowledgement command must be sent when +CSMS <service> value equals 1 and ME does not have other display device than AT interface 3) acknowledgement command must be sent when +CSMS <service> value equals 1


<bm> (the rules for storing received CBMs depend on its data coding scheme (refer GSM 03.38 [8]), the setting of Select CBM Types (+CSCB) and this value; refer table 3):

0 No CBM indications are routed to the TE.

1 If CBM is stored into ME/TA, indication of the memory location is routed to the TE using unsolicited result code: +CBMI

2 New CBMs are routed directly to the TE using unsolicited result code: +CBM

If ME supports data coding groups which define special routing also for messages other than class 3 (e.g. SIM specific messages), ME may choose not to route messages of such data coding schemes into TE (indication of a stored CBM may be given as defined in <bm>=1).

3 Class 3 CBMs are routed directly to TE using unsolicited result codes defined in <bm>=2. If CBM storage is supported, messages of other classes result in indication as defined in <bm>=1.

Table 3: <bm> parameter

<ds>:

0 No SMS-STATUS-REPORTs are routed to the TE.

1 SMS-STATUS-REPORTs are routed to the TE using unsolicited result code: +CDS

2 If SMS-STATUS-REPORT is stored into ME/TA, indication of the memory location is routed to the TE using unsolicited result code: +CDSI

<bm>Receiving procedure for different message data coding schemes (refer GSM 03.38 [8])

0 all schemes: as in GSM 03.38; if CBM storage is supported, store message to “BM” (or some manufacturer or data coding scheme specific memory)

1 all schemes: as <bm>=0 but send indication if message stored successfully

2 all schemes: route message to TE unless ME has detected a special routing to somewhere else (e.g. to SIM; an indication may be sent if message stored successfully)

3 Class 3: route message to TE others: as <bm>=1 (if CBM memory storage is supported)


1

Table 4: SMS-STATUS-REPORT result code and acknowledgement summary

<bfr>:

0 TA buffer of unsolicited result codes defined within this command is flushed to the TE when <mode> 1...3 is entered (OK response shall be given before flushing the codes).

1 TA buffer of unsolicited result codes defined within this command is cleared when <mode> 1...3 is entered.

<mem>

“SM” SIM

“ME” GC75

<index>


Comments

<mode> has other values according to GSM 07.05 [17] (unsolicited result code are not buffered here!).

+CMGD - Delete Message


Description

Execution command deletes message from preferred message storage <mem1> location <index>. If <delflag> is present and not set to 0 then the ME shall ignore <index> and follow the rules for <delflag> shown below. If deleting fails, final result code +CMS ERROR is returned.

<ds> result codes and commands

1 +CDS & +CNMA1)

2 +CDSI

1) acknowledgement command must be sent when +CSMS <service> value equals 1


+CMS ERROR: <err>

+CMGD=<index>[,<delflag>]

+CMGD=? +CMGD: (list of supported <index>s) [,(list of supported <delflag>s)]


Parameter-Values <index> Integer type, Value in the range of location numbers supported by the

associated memory.

<delflag> an integer indicating multiple message deletion request as follows:

0 (or omitted) Delete the message specified in <index>

1 Delete all read messages from preferred message storage, leaving unread messages and stored mobile originated messages (whether sent or not) untouched

2 Delete all read messages from preferred message storage and sent mobile originated messages, leaving unread messages and unsent mobile originated messages untouched

3 Delete all read messages from preferred message storage, sent and unsent mobile originated messages leaving unread messages untouched.

4 Delete all messages from preferred message storage including unread messages.


1

SMS Text mode

Any command syntax presented in this chapter is only valid when text mode format is selected (+CGMF=1).

+CSMP - Set Text Mode Parameters

Parameter command syntax (if SMS TEXT mode, +CMGF=1)

Description

Set command is used to select values for additional parameters needed when SM is sent to the network or placed in a storage when text format message mode is selected. It is possible to set the validity period starting from when the SM is received by the SMSC (<vp> is in range 0... 255) or define the absolute time of the validity period termination (<vp> is a string). The format of <vp> is given by <fo>. If TA supports the enhanced validity period format ($(EVPF)$, see GSM 03.40 [9]), it shall be given as a hexadecimal coded string (refer e.g. <pdu>) with double quotes.

Parameter-Values

See previous section


Note! When storing a SMS-DELIVER from the TE to the preferred memory storage in text mode (refer 18.9 command +CMGW, Write Message to Memory), <vp> field can be used for <scts>.


+CSMP=[<fo>[,<vp>[,<pid>[,<dcs>]]]]

+CSMP? +CSMP: <fo>, <vp>, <pid>, <dcs>

+CSMP=?

32 SMS Text mode

+CSDH - Show Text Mode Parameters


Description

Set command controls whether detailed header information is shown in text mode result codes.

Test command returns supported values as a compound value.

Parameter-Values <show>

0 no header information shown

1 header information shown



Unsolicited Result Code (if SMS TEXT mode, +CMGF=1)

Parameters in italics, refer to “+CSDH - Show Text Mode Parameters”, page 133.


+CSDH=[<show>]

+CSDH? +CSDH: <show>

+CSDH=? +CSDH: (list of supported <show>s)

+CMTI: <mem>, <index>

+CMT: <oa>, [<alpha>], <scts>[, <tooa>, <fo>, <pid>, <dcs>, <sca>, <tosca>, <length>]<CR><LF> <data>

+CBMI: <mem>, <index>

+CBM: <sn>, <mid>, <dcs>, <page>, <pages><CR><LF><data>

+CDSI: <mem>, <index>

+CDS: <fo>, <mr>, [<ra>], [<tora>], <scts>, <dt>, <st>

SMS Text mode 133

1

+CMGL - List Messages

Action command syntax (if SMS TEXT mode, +CMGF=1)

Description

Execution command returns messages with status value <stat> from message storage <mem1> to the TE. About text mode parameters in italics, see “+CSDH - Show Text Mode Parameters”, page 133. If status of the message is 'received unread', status in the storage changes to 'received read'.

If listing fails, final result code +CMS ERROR is returned.

Parameter-Values <err> Refer to “+CMS ERROR . Message Failure Result Code”, page 191

Comments

Note! If 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.


+CMS ERROR: <err>

+CMGL[=<stat>] SMS-SUBMITs and/or SMS-DELIVERs+CMGL: <index>, <stat>, <oa/da>, [<alpha>], [<scts>][,<tooa/toda>, <length>]<CR><LF><data>[<CR><LF>+CMGL: <index>, <stat>, <da/oa>, [<alpha>], [<scts>] [,<tooa/toda>, <length>]<CR><LF> <data>[...]] SMS-STATUS-REPORTs: +CMGL: <index>,<stat>,<fo>,<mr>,[<ra>],[<tora>],<scts>,<dt>,<st>[<CR><LF>+CMGL: <index>, <stat>, <fo>, <mr>, [<ra>], [<tora>], <scts>, <dt>, <st>[...]] SMS-COMMANDs:+CMGL: <index>, <stat>, <fo>, <ct>[<CR><LF>+CMGL: <index>, <stat>, <fo>, <ct>[...]]CBM storage:+CMGL: <index>, <stat>, <sn>, <mid>, <page>, <pages><CR><LF><data>[<CR><LF>+CMGL: <index>, <stat>, <sn>, <mid>, <page>, <pages><CR><LF><data>[...]]

+CMGL=? +CMGL: (list of supported <stat>s)

34 SMS Text mode

Test command shall give a list of all status values supported by the TA.

+CMGR - Read Message

Action Command Syntax (if SMS TEXT mode, +CMGF=1)

Description

Execution command returns message with location value <index> from message storage <mem1> to the TE. About text mode parameters in italics, refer command Show Text Mode Parameters +CSDH. If status of the message is ’received unread’, status in the storage changes to ’received read’. If reading fails, final result code +CMS ERROR: <err> is returned. See chapter Message Service Failure Result Code for <err> values.

Parameter-Values <err> Refer to “+CMS ERROR . Message Failure Result Code”, page 191


+CMS ERROR: <err>

+CMGR=<index> SMS-DELIVER:+CMGR: <stat>, <oa>, [<alpha>], <scts>[, <tooa>, <fo>, <pid>, <dcs>, <sca>, <tosca>, <length>]<CR><LF><data> SMS-SUBMIT: +CMGR: <stat>,<da>,[<alpha>][,<toda>,<fo>,<pid>,<dcs>,[<vp>],<sca>,<tosca>,<length>]<CR><LF><data> SMS-STATUS-REPORT: +CMGR: <stat>, <fo>, <mr>, [<ra>], [<tora>], <scts>, <dt>, <st> SMS-COMMAND: +CMGR: <stat>,<fo>,<ct>[,<pid>,[<mn>],[<da>],[<toda>],<length><CR><LF><cdata>]CBM storage: +CMGR: <stat>, <sn>, <mid>, <dcs>, <page>, <pages><CR><LF> <data>

+CMGR=?

SMS Text mode 135

1

+CNMA - New Message Acknowledgement to ME/TA


Description

Execution command confirms correct reception of a new message (SMS-DELIVER or SMS-STATUS-REPORT) which is routed directly to the TE, see “+CNMI - New Message Indications to TE”, page 133, tables 2 and 4). This acknowledgement command (causing ME to send RP-ACK to the network) shall be used when +CSMS parameter <service> equals 1. TA shall not send another +CMT or +CDS result code to TE before previous one is acknowledged.

If ME does not get acknowledgement within required time (network timeout), ME should send RP-ERROR to the network. ME/TA shall automatically disable routing to TE by setting both <mt> and <ds> values of +CNMI to zero.

If command is executed, but no acknowledgement is expected, or some other ME related error occurs, final result code +CMS ERROR: <err> is returned.

Note! In case that a directly routed message must be buffered in ME/TA (possible when +CNMI parameter <mode> equals 0 or 2) or AT interpreter remains too long in a state where result codes cannot be sent to TE (e.g. user is entering a message using +CMGS), acknowledgement (RP-ACK) must be sent to the network without waiting +CNMA command from TE. Later, when buffered result codes are flushed to TE, TE must send +CNMA acknowledgement for each result code. In this way, ME/TA can determine if message should be placed in non-volatile memory and routing to TE disabled (+CNMA not received). Refer to “+CNMI - New Message Indications to TE”, page 133 for more details how to use <mode> parameter reliably.

Parameter-Values <err> Refer to “+CME ERROR: <err> - Mobile Equipment error result code”,

page 189.


+CMS ERROR: <err>

+CNMA

+CNMA=?

36 SMS Text mode

+CMGS - Send Message


Description

Execution command sends message from a TE to the network (SMS-SUBMIT). Message reference value <mr> is returned to the TE on successful message delivery. Values can be used to identify message upon unsolicited delivery status report result code. If sending fails in a network or an ME error, final result code +CMS ERROR is returned. This command should be abortable.

• entered text (GSM 03.40 TP-Data-Unit) is sent to address <da> and all current settings (refer Set Text Mode Parameters +CSMP and Service Centre Address +CSCA) are used to construct the actual PDU in ME/TA

• the TA shall send a four character sequence <CR><LF><greater_than><space> (IRA 13, 10, 62, 32) after command line is terminated with <CR>; after that text can be entered from TE to ME/TA

• the DCD signal shall be in ON state while text is entered

• the echoing of entered characters back from the TA is controlled by V.25ter echo command E

• the entered text should be formatted as follows: • if <dcs> (set with +CSMP) indicates that GSM 03.38 default alphabet is used

and <fo> indicates that GSM 03.40 TP-User-Data-Header-Indication is not set:

• if TE character set other than “HEX” (refer command Select TE Character Set +CSCS in TS 07.07): ME/TA converts the entered text into GSM alphabet according to rules of Annex A; backspace can be used to delete last character and carriage returns can be used (previously mentioned four character sequence shall be sent to the TE after every carriage return entered by the user)

• if TE character set is “HEX”: the entered text should consist of two IRA character long hexadecimal numbers which ME/TA converts to 7-bit characters of GSM alphabet (e.g. 17 (IRA 49 and 55) will be converted to character Ð (GSM 23))

• if <dcs> indicates that 8-bit or UCS2 data coding scheme is used or <fo> indicates that GSM 03.40 TP-User-Data-Header-Indication is set: the entered text should consist of two IRA character long hexadecimal numbers which ME/TA converts into 8-bit octet (e.g. two characters 2A (IRA 50 and 65) will


+CMS ERROR: <err>

+CMGS=<da>[,<toda>]<CR>text is entered<ctrl-Z/ESC>

+CMGS: <mr>

+CMGS=?

SMS Text mode 137

1

be converted to an octet with integer value 42).

• sending can be cancelled by giving <ESC> character (IRA 27)

• . <ctrl-Z> (IRA 26) must be used to indicate the ending of the message body


page 189.

+CMSS - Send Message from Storage


Description

Execution command sends message with location value <index> from preferred 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. Optionally (when +CSMS <service> value is 1 and network supports) <scts> is returned. Values can be used to identify message upon unsolicited delivery status report result code. If sending fails in a network or an ME error, final result code +CMS ERROR: <err> is returned. See chapter Message Service Failure Result Code for a list of <err> values. This command should be abortable.


page 189.


+CMS ERROR: <err>

+CMSS=<index>[,<da>[,<toda>]] +CMSS: <mr>[,<scts>]

+CMSS=?

38 SMS Text mode

+CMGW - Write Message to Memory


Description

Execution command stores message (either SMS-DELIVER or SMS-SUBMIT) to memory storage <mem2>. Memory location <index> of the stored message is returned. By default message status will be set to ’stored unsent’, but parameter <stat> allows also other status values to be given. The entering of text is done similarly as specified in command Send Message +CMGS. If writing fails, final result code +CMS ERROR: <err> is returned.

Parameter-Values <err> “Error Messages”, page 189

Comments

Note! SMS-COMMANDs and SMS-STATUS-REPORTs can not be stored in text mode.

+CMGC - Send Command


Description

Execution command sends a command message from a TE to the network (SMS-COMMAND). The entering of text (GSM 03.40 TP-Command-Data) is done similarly as specified in command Send Message +CMGS, but the format is fixed to be a sequence of two IRA character long hexadecimal numbers which ME/TA converts into 8-bit octets (refer +CMGS). Message reference value <mr> is returned to the TE on successful message delivery. Optionally (when +CSMS <service> value is 1 and network supports) <scts> is


+CMS ERROR: <err>

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

+CMGW: <index> +CMS ERROR: <err>

+CMGW=?


+CMS ERROR: <err>

+CMGC=<fo>,<ct>[,<pid>[,<mn> [,<da>[,<toda>]]]]<CR> text is entered<ctrl-Z/ESC>

+CMGC: <mr>[,<scts>] if sending fails: +CMS ERROR: <err>

+CMGC=?

SMS Text mode 139

1

returned. Values can be used to identify message upon unsolicited delivery status report result code. If sending fails in a network or an ME error, final result code +CMS ERROR: <err> is returned. See chapter Message Service Failure Result Code for a list of <err> values. This command should be abortable.

+CMMS - More Messages to Send

Parameter Command Syntax (if SMS TEXT mode, +CMGF=1)

Description

Set command controls the continuity of SMS relay protocol link. When feature is enabled (and supported by network) multiple messages can be sent much faster as link is kept open.

Test command returns supported values as a compound value.

Defined Values <n>

0 disable

1 keep enabled until the time between the response of the latest message send command (+CMGS, +CMSS, etc.) and the next send command exceeds 1-5 seconds (the exact value is up to ME implementation), then ME shall close the link and TA switches <n> automatically back to 0

2 enable (if the time between the response of the latest message send command and the next send command exceeds 1-5 seconds (the exact value is up to ME implementation), ME shall close the link but TA shall not switch automatically back to <n>=0)


+CMMS=[<n>]

+CMMS? +CMMS: <n>

+CMMS=? +CMMS: (list of supported <n>s)

40 SMS Text mode

SMS PDU mode

The PDU mode uses the same commands and responses as the Text Mode described in “SMS Text mode”, page 132. However, the following commands and responses have a different format. In the PDU mode, a complete SMS Message including all header information is passed as a binary string. This binary string is composed of hexadecimal IA5 characters.


Unsolicited Result Code (if PDU mode, +CGMF=0)

+CMGL - List Messages

Action Command Syntax (if PDU mode, +CGMF=0)

Description

Execution command returns messages with status value <stat> from preferred message storage <mem1> to the TE. Entire data units <pdu> are returned. If status of the message is 'received unread', status in the storage changes to 'received read'. If listing fails, final result code +CMS ERROR: <err> is returned. See chapter Message Service Failure Result Code for <err> values.

Test command shall give a list of all status values supported by the TA.

+CMTI: <mem>, <index>

+CMT: [<alpha>], <length><CR><LF> <pdu>

+CBMI: <mem>, <index>

+CBM: <length><CR><LF> <pdu>

+CDSI: <mem>, <index>

+CDS: <length><CR><LF> <pdu>


+CMS ERROR: <err>

+CMGL[=<stat>] +CMGL: <index>, <stat>, [<alpha>], <length><CR><LF> <pdu>[<CR><LF> +CMGL: <index>, <stat>, [<alpha>], <length><CR><LF> <pdu>[...]]

+CMGL=? +CMGL: (list of supported <stat>s)

SMS PDU mode 141

1

+CMGR - Read Message

Action command syntax (if PDU mode, +CGMF=0)

Description

Execution command returns message with location value <index> from message storage <mem1> to the TE. Status of the message and entire data units <pdu> are returned If status of the message is .received unread., status in the storage changes to .received read.. If listing fails, final result code +CMS ERROR: <err> is returned.

+CMGS - Send Message


Description

Execution command sends message from a TE to the network (SMS-SUBMIT). Message reference value <mr> is returned to the TE on successful message delivery. Optionally (when +CSMS <service> value is 1 and network supports) <scts> is returned. Values can be used to identify message upon unsolicited delivery status report result code. If sending fails in a network or an ME error, final result code +CMS ERROR is returned. This command should be abortable.

• <length> must indicate the number of octets coded in the TP layer data unit to be given (i.e. SMSC address octets are excluded)

• the TA shall send a four character sequence <CR><LF><greater_than><space> (IRA 13, 10, 62, 32) after command line is terminated with <CR>; after that PDU can be given from TE to ME/TA

• the DCD signal shall be in ON state while PDU is given

• the echoing of given characters back from the TA is controlled by V.25ter echo command E

• the PDU shall be hexadecimal format (similarly as specified for <pdu>) and given in one line; ME/TA converts this coding into the actual octets of PDU


+CMS ERROR: <err>

+CMGR=<index> +CMGR: <stat>, <length><CR><LF><pdu>

+CMGR=?


+CMS ERROR: <err>

+CMGS=<length><CR> PDU is given<ctr-z/ESC>

+CMGS: <mr>[,<ackpdu>]

+CMGS=?

42 SMS PDU mode

• when the length octet of the SMSC address (given in the PDU) equals zero, the SMSC address set with command Service Centre Address +CSCA is used; in this case the SMSC Type-of-Address octet shall not be present in the PDU, i.e. TPDU starts right after SMSC length octet

• sending can be cancelled by giving <ESC> character (IRA 27)

• <ctrl-Z> (IRA 26) must be used to indicate the ending of PDU

Parameter-Values <mr>: String type, GSM 03.40 [9] TP-Message-Reference in integer format.

<length>: String type, Value indicating in PDU mode (+CMGF=0), the length of the actual TP data unit in octets (i.e. the RP layer SMSC address octets are not counted in the length)

<ackpdu> GSM 03.40 [9] RP-User Data element of RP-ACK PDU; format as for <pdu> in case of SMS, but without GSM 04.11 [14] SC address field and parameter shall be bounded by double quote characters like a normal string parameter.

+CMGW - Write Message to Memory


Description

Execution command stores a message to memory storage <mem2>. Memory location <index> of the stored message is returned. By default message status will be set to ’stored unsent’, but parameter <stat> allows also other status values to be given. (ME/TA manufacturer may choose to use different default <stat> values for different message types.) The entering of PDU is done similarly as specified in command Send Message +CMGS. If writing fails, final result code +CMS ERROR: <err> is returned. See chapter Message Service Failure Result Code for <err> values.


+CMS ERROR: <err>

if PDU mode (+CMGF=0): +CMGW=<length>[,<stat>]<CR>PDU isgiven<ctrl-Z/ESC>

+CMGW: <index>

+CMGW=?

SMS PDU mode 143

1

+CMGC - Send Command


Description

Execution command sends a command message from a TE to the network (SMS-COMMAND). The entering of PDU is done similarly as specified in command Send Message +CMGS. Message reference value <mr> is returned to the TE on successful message delivery. Optionally (when +CSMS <service> value is 1 and network supports) <ackpdu> is returned. Values can be used to identify message upon unsolicited delivery status report result code. If sending fails in a network or an ME error, final result code +CMS ERROR: <err> is returned. See chapter Message Service Failure Result Code for a list of <err> values. This command should be abortable.

+CNMA - New Message Acknowledgement to ME/TA


Description

Execution command confirms reception of a new message (SMS-DELIVER or SMS-STATUS-REPORT) which is routed directly to the TE (refer command +CNMI tables 2 and 4). This acknowledgement command shall be used when +CSMS parameter <service> equals 1. In PDU mode, it is possible to send either positive (RP-ACK) or negative (RP-ERROR) acknowledgement to the network. Parameter <n> defines which one will be sent. Optionally (when <length> is greater than zero) an acknowledgement TPDU (SMS-DELIVER-REPORT for RP-ACK or RP-ERROR) may be sent to the network. The entering of PDU is done similarly as specified in command Send Message +CMGS, except that the format of <ackpdu> is used instead of <pdu> (i.e. SMSC address field is not present). PDU shall not be bounded by double quotes. TA shall not send another +CMT or +CDS result code to TE before previous one is acknowledged.


+CMS ERROR: <err>

+CMGC=<length><CR> PDU is given<ctrl-Z/ESC>

+CMGC: <mr>[,<ackpdu>]

+CMGC=?


+CMS ERROR: <err>

+CNMA[=<n>[,<length>[<CR> PDU is given<ctrl-Z/ESC>]]]

+CNMA=? +CNMA: (list of supported <n>s)

44 SMS PDU mode

If ME does not get acknowledgement within required time (network timeout), ME should send RP-ERROR to the network. ME/TA shall automatically disable routing to TE by setting both <mt> and <ds> values of +CNMI to zero.

If command is executed, but no acknowledgement is expected, or some other ME related error occurs, final result code +CMS ERROR: <err> is returned. See chapter Message Service Failure Result Code for a list of <err> values.

Note! In case that a directly routed message must be buffered in ME/TA (possible when +CNMI parameter <mode> equals 0 or 2) or AT interpreter remains too long in a state where result codes cannot be sent to TE (e.g. user is entering a message using +CMGS), acknowledgement (RP-ACK) must be sent to the network without waiting +CNMA command from TE. Later, when buffered result codes are flushed to TE, TE must send +CNMA[=0] acknowledgement for each result code. In this way, ME/TA can determine if message should be placed in non-volatile memory and routing to TE disabled (+CNMA[=0] not received). Refer command +CNMI for more details how to use <mode> parameter reliably.

Test command returns a list of supported <n> values. If the only value supported is 0, the device does not support sending of TPDU.

Defined Values <n>:

0 command operates similarly as defined for the text mode

1 send RP-ACK (or buffered result code received correctly)

2 send RP-ERROR (if PDU is not given, ME/TA shall send SMS-DELIVER-REPORT with GSM 03.40 TP-FCS value set to .FF. (unspecified error cause))

+CMSS - Send Message from Storage


Description

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


+CMS ERROR: <err>

+CMSS=<index>[,<da>[,<toda>]] +CMSS: <mr>[,<ackpdu>]

+CMSS=?

SMS PDU mode 145

1

(when +CSMS <service> value is 1 and network supports) <ackpdu> is returned. Values can be used to identify message upon unsolicited delivery status report result code. If sending fails in a network or an ME error, final result code +CMS ERROR: <err> is returned. See chapter Message Service Failure Result Code for a list of <err> values. This command should be abortable.

46 SMS PDU mode

GSM Phonebook

+CPBS - Select phone book memory


Description

Set command selects phone book memory storage <storage>, which is used by other phone book commands. If setting fails in an ME error, +CME ERROR, is returned. Read command returns currently selected memory, and number of used locations and total number of locations in the memory.

Test command returns supported storages as compound value.

Parameter-Values <storage>

“FD” SIM fixdialling-phone book

“ME” ME phone book

“SM” SIM phone book

“EN” SIM (or ME) emergency number



+CME ERROR: <err>

+CPBS=<storage>

+CPBS? +CPBS: <storage>[,<used>,<total>]

+CPBS=? +CPBS: (list of supported <storage>s)

GSM Phonebook 147

1

+CPOL Preferred operator list


Description

This command is used to edit the SIM preferred list of networks. Execute command writes an entry in the SIM list of preferred operators (EF-PLMNsel). If <index> is given but <oper> is left out, entry is deleted. If <oper> is given but <index> is left out, <oper> is put in the next free location. If only <format> is given, the format of the <oper> in the read command is changed.

Note! ME may also update this list automatically when new networks are selected.

Read command returns all used entries from the SIM list of preferred operators.

Test command returns the whole index range supported by the SIM.

Parameter-Values <indexn>: integer type; the order number of operator in the SIM preferred operator

list

<format>:

0 long format alphanumeric <oper>

1 short format alphanumeric <oper>

2 numeric <oper>. Default.

<opern>: string type; <format> indicates if the format is alphanumeric or numeric (see +COPS)



+CME ERROR: <err>

+CPOL=[<index>][,<format> [,<oper>]]

+CPOL? +CPOL:<index1>,<format>,<oper1>[<CR><LF> +CPOL: <index2>,<format>,<oper2> [...]]

+CPOL=? +CPOL: (list of supported <index>s), (list of supported <format>s)

48 GSM Phonebook

+CIMI - Request IMSI


Description

Execution command causes the TA to return <IMSI>, which is intended to permit the TE to identify the individual SIM which is attached to ME.

Parameter-Values <IMSI>: International Mobile Subscriber Identity (string without double quotes)


+CPBR - Read phone book entries


Description

Execution command returns phonebook entries in location number range <index1>... <index2> from the current phonebook memory storage selected with +CPBS. If <index2> is left out, only location <index1> is returned. Entry fields returned are location number <indexn>, phone number stored there <number> (of format <type>) and text <text> associated with the number. If all queried locations are empty (but available), no information text lines may be returned. If listing fails in an ME error, +CME ERROR is returned.

Test command returns location range supported by the current storage as a compound value and the maximum lengths of <number>.


+CME ERROR: <err>

+CIMI <IMSI>

+CIMI=?


+CME ERROR: <err>

+CPBR=<index1>[,<index2>] +CPBR: <index1>,<number>,<type>,<text>[[...] <CR><LF> +CPBR: <index2>,<number>,<type>,<text>]]

+CPBR=? +CPBR: (list of supported <index>s), [<nlength>], [<tlength>]

GSM Phonebook 149

1

Parameter-Values <indexn> integer type, values in the range of location numbers of phonebook

memory

<number>: string type, phone number of format <type>


129 ISDN /telephony numbering plan, international unknown

145 ISDN /telephony numbering plan, international number

161 ISDN/telephony numbering plan, national number

128-255 Other values refer GSM 04.08 [13] section 10.5.4.7

<text>: string type, field of maximum length <tlength>; character set as specified by command Select TE Character Set +CSCS

<nlength>: integer type, value indicating the maximum length of field <number>

<tlength>: integer type, value indicating the maximum length of field <text>


+CPBF - Find phonebook entries


Description

Execution command returns phonebook entries (from the current phonebook memory storage selected with +CPBS) which alphanumeric field start with string <findtext>. Entry fields returned are location number <indexn>, phone number stored there <number> (of format <type>) and text <text> associated with the number. If listing fails in an ME error, +CME ERROR: <err> is returned.

Test command returns the maximum lengths of <number> and <text> fields. In case of SIM storage, the lengths may not be available. If ME is not currently reachable, +CME ERROR: <err> is returned.

Parameter-Values <index1>


+CME ERROR: <err>

+CPBF=<findtext> [+CPBF: <index1>,<number>,<type>,<text>[[...] <CR><LF> +CBPF: <index2>,<number>,<type>,<text>]]

+CPBF=? +CPBF: [<nlength>], [<tlength>]

50 GSM Phonebook

<index2>: integer type values in the range of location numbers of phonebook memory

<number>: string type phone number of format <type>


<findtext>,

<text>: string type field of maximum length <tlength>; character set as specified by command Select TE Character Set +CSCS

<nlength>: integer type value indicating the maximum length of field <number>

<tlength>: integer type value indicating the maximum length of field <text>


+CPBW - Write phonebook entry


Description

Execution command writes phonebook entry in location number <index> in the current phonebook memory storage selected with +CPBS. Entry fields written are phone number <number> (in the format <type>) and text <text> associated with the number. If those fields are omitted, phonebook entry is deleted. If <index> is left out, but <number> is given, entry is written to the first free location in the phonebook (the implementation of this feature is manufacturer specific). If writing fails in an ME error, +CME ERROR, is returned.

Test command returns location range supported by the current storage as a compound value, the maximum length of <number> field, supported number formats of the storage, and the maximum length of <text> field. In case of SIM storage, the lengths may not be available. If ME is not currently reachable, +CME ERROR is returned. If storage does not offer format information, the format list should be empty parenthesis

Parameter-Values <index>: integer type, values in the range of location numbers of phonebook

memory

<number>: string type, phone number of format <type>


+CME ERROR: <err>

+CPBW=[<index>][,<number> [,<type>[,<text>]]]

+CPBW=? +CPBW: (list of supported <index>s), [<nlength>], (list of supported <type>s), [<tlength>]

GSM Phonebook 151

1

<type>: type of address octet in integer format (refer GSM 04.08 [13] subclause 10.5.4.7) ; default 145 when dialling string includes international access code character “+”, otherwise 129

129 ISDN /telephony numbering plan, international unknown, Default if no .+. in sca.

145 ISDN /telephony numbering plan, international number, Default if .+. in sca.

161 ISDN/telephony numbering plan, national number

128-255 Other values refer GSM 04.08 [13] section 10.5.4.7

<text>: string type, field of maximum length <tlength>; character set as specified by command Select TE Character Set +CSCS

<nlength>: integer type, value indicating the maximum length of field

<number>

<tlength>: integer type, value indicating the maximum length of field <text>


+CRSM - Restricted SIM access


Description

By using this command instead of Generic SIM Access +CSIM TE application has easier but more limited access to the SIM database. Set command transmits to the ME the SIM <command> and its required parameters. ME handles internally all SIM-ME interface locking and file selection routines. As response to the command, ME sends the actual SIM information parameters and response data. ME error result code +CME ERROR may be returned when the command cannot be passed to the SIM, but failure in the execution of the command in the SIM is reported in <sw1> and <sw2> parameters.

Coordination of command requests to SIM and the ones issued by GSM application inside the ME is implementation dependent. However the TE should be aware of the precedence of the GSM application commands to the TE commands.


+CME ERROR: <err>

+CRSM=<cmd>[,<fileid> [,<P1>,<P2>,<P3>[,<data>]]]

+CRSM: <sw1>,<sw2>[,<response>]

+CRSM=?

52 GSM Phonebook

Parameter-Values <command> (command passed on by the ME to the SIM; refer GSM 11.11 [21]):

176 READ BINARY

178 READ RECORD

192 GET RESPONSE

214 UPDATE BINARY

220 UPDATE RECORD

242 STATUS

Note! The ME internally executes all commands necessary for selecting the desired file, before performing the actual command.

<fileid>: integer type; this is the identifier of a elementary datafile on SIM. Mandatory for every command except STATUS

Note! The range of valid file identifiers depends on the actual SIM and is defined in GSM 11.11 [21]. Optional files may not be present at all.

<P1>, <P2>, <P3>: integer type; parameters passed on by the ME to the SIM. These parameters are mandatory for every command, except GET RESPONSE and STATUS. The values are described in GSM 11.11 [21].

<data>: information which shall be written to the SIM (hexadecimal character format; refer 10.1 +CSCS)

<sw1>, <sw2>: integer type; information from the SIM about the execution of the actual command. These parameters are delivered to the TE in both cases, on successful or failed execution of the command

<response>: response of a successful completion of the command previously issued (hexadecimal character format; refer 10.1 +CSCS). STATUS and GET RESPONSE return data, which gives information about the current elementary datafield. This information includes the type of file and its size (refer GSM 11.11 [21]). After READ BINARY or READ RECORD command the requested data will be returned. <response> is not returned after a successful UPDATE BINARY or UPDATE RECORD command


GSM Phonebook 153

Phone Control

+COPN - Read operator names


Description

Execute command returns the list of operator names from the ME. Each operator code <numericn> that has an alphanumeric equivalent <alphan> in the ME memory shall be returned.

Parameter-Values <numericn>: string type; operator in numeric format (see +COPS)

<alphan>: string type; operator in long alphanumeric format (see +COPS)


+CMEC - Mobile Equipment control mode


Description

Set command selects the equipment, which operates ME keypad, writes to ME display and sets ME indicators. If operation mode is not allowed by the ME, +CME ERROR is returned.


+CME ERROR: <err>

+COPN +COPN: <numeric1>,<alpha1>[<CR><LF> +COPN: <numeric2>,<alpha2> [...]]

+COPN=?


+CME ERROR: <err>

+CMEC=[<keyp>[,<disp>[,<ind>]]]

+CMEC? +CMEC: <keyp>, <disp>, <ind>

+CMEC=? +CMEC: (list of supported <keyp>s), (list of supported <disp>s), (list of supported <ind>s)

154 General

Test command returns the modes supported by the TA as compound values.

Parameter-Values <keyp>: no values allowed.

<disp>: no values allowed.

<ind>:

0 only ME can set the status of its indicators (command +CIND can only be used to read the indicators)


+CMER - Mobile Equipment Event Reporting



Description

Set command enables or disables sending of unsolicited result codes from TA to TE in the case of key pressings, display changes, and indicator state changes. <mode> controls the processing of unsolicited result codes specified within this command. <bfr> controls the effect on buffered codes when <mode> 1, 2 or 3 is entered. If setting is not supported by the ME, +CME ERROR: <err> is returned.

Test command returns the modes supported by the TA as compound values.

The +CIEV result code is used to indicate SMS memory status.



+CME ERROR: <err>

+CMER=[<mode>[,<keyp>[,<disp>[,<ind>[,<bfr>]]]]]

+CMER? +CMER: <mode>, <keyp>, <disp>, <ind>, <bfr>

+CMER=? +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)


+ CIEV : <event>, <value>

Phone Control 155

1

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

<keyp>

0 No keypad event reporting. Default.

<disp>

0 No display event reporting. Default.

<ind>

1 indicator event reporting using result code +CIEV:

<ind>, <value>. <ind> indicates the indicator order number and <value> is the new value of indicator.

<bfr>

0 TA buffer of unsolicited result codes defined within this command is cleared when <mode> 1...3 is entered

1 TA buffer of unsolicited result codes defined within this command is flushed to the TE when <mode> 1...3 is entered (OK response shall be given before flushing the codes)

<event> integer type value, which shall be in range of corresponding <descr> (see GSM 07.07 [18] §8.9 signal quality (0-5), smsfull (0-1))

9 SMS-memory full.

<value> is the new value of indicator.

0 memory locations are available

1 a short message memory storage in the MT has become full


56 Phone Control

+CMAR - Master Reset


Description

This command requests the ME to reset user data. The user data in the phone will be reset to default values. If setting fails, a ME error, +CME ERROR is returned.

If the ME is locked and this command is used, then the ME will be unlocked after the master reset.

Test command returns OK.

Parameter-Values <phone lock code>: string type; Security code (Phone Lock code) must be verified

before performing the master reset.



+CME ERROR: <err>

+CMAR=<phone lock code>

AT+CMAR=?

Phone Control 157

1

HSCSD

+CHSD - HSCSD device parameters


Description

Execution command returns information about HSCSD features (refer GSM 02.34 [4]) supported by the ME/TA.

Parameter-Values <mclass>: integer type; multislot class

<maxRx>: integer type; maximum number of receive timeslots that ME can use

<maxTx>: integer type; maximum number of transmit timeslots that ME can use

<sum>: integer type; total number of receive and transmit timeslots that ME can use at the same time (per TDMA frame). The following applies in a HSCSD call: 1 � (receive slots) + (transmit slots) ��<sum>

<codings> is a sum of integers each representing a supported channel coding (e.g. value 12 indicates that 9.6k and 14.4k channel codings are supported):

4 9.6k full rate data traffic channel

8 14.4k full rate data traffic channel



+CME ERROR: <err>

+CHSD +CHSD: <mclass>, <maxRx>, <maxTx>, <sum>, <codings>

+CHSD=?

58 HSCSD

+CHST - HSCSD transparent call configuration


Description

Set command controls parameters for transparent HSCSD calls. Changing them during a call does not affect the current call.

Parameter-Values <wRx>: integer type; wanted amount of receive timeslots. Default value 0

indicates that TA shall calculate a proper value from currently selected fixed network user rate (<speed> sub-parameter from +CBST command) and <codings>

<codings>: a sum of integers each representing a channel coding that is accepted for transparent HSCSD calls. Default value 0 indicates that all supported codings are accepted (refer to “+CHSD - HSCSD device parameters”, page 158 for other values)

+CHSN - HSCSD non-transparent call configuration


Description

Set command controls parameters for non-transparent HSCSD calls. Changing <topRx> or <codings> value during a call does not affect the current call. Changing of <wAiur> or <wRx> affects the current call only if <topRx> was non-zero when call was established.

Parameter-Values <wAiur>: integer type; wanted air interface user rate. Default value 0 indicates

that TA shall calculate a proper value from currently selected fixed


+CHST=[<wRx>[,<codings>]]

+CHST? +CHST: <wRx>, <codings>

+CHST=?


+CHSN=[<wAiur>[,<wRx>[,<topRx>[,<codings>]]]]

+CHSN? +CHSN: <wAiur>, <wRx>, <topRx>, <codings>

+CHSN=?

HSCSD 159

1

network user rate (<speed> sub-parameter from +CBST command), <codings>, and <wRx> (or <maxRx> from +CHSD command if <wRx>=0). Other values:

1 9600 bps

2 14400 bps

3 19200 bps

4 28800 bps

5 38400 bps

6 43200 bps

7 57600 bps

<wRx>: integer type; wanted amount of receive timeslots. Default value 0 indicates that TA shall calculate a proper value from currently selected <wAiur> and <codings>

<topRx>: integer type; top value for <wRx> that user is going to request during the next established non-transparent HSCSD call. Default value 0 indicates that user is not going to change <wAiur>/<wRx> during the next call

<codings>: a sum of integers each representing a channel coding that is accepted for non-transparent HSCSD calls. Default value 0 indicates that all supported codings are accepted (refer to “+CHSD - HSCSD device parameters”, page 158 for other values)

+CHSC HSCSD current call parameters


Description

Execution command returns information about current HSCSD call. If no HSCSD call is active, all parameters returned shall equal zero (it is manufacturer specific whether non-zero information is returned in case of an active normal single-slot data call).

Parameter-Values <rx>: integer type; number of receive timeslots currently in use

<tx>: integer type; number of transmit timeslots currently in use

<aiur>: integer type; current air interface user rate (in case of transparent service this equals fixed network user rate) (refer to “+CHSN -


+CHSC +CHSC: <rx>, <tx>, <aiur>, <coding>

+CHSC=?

60 HSCSD

HSCSD non-transparent call configuration”, page 159 for possible values)

<coding>: current channel coding (refer to “+CHSD - HSCSD device parameters”, page 158 for possible values)

+CHSR - HSCSD parameters report


Description

Enabled command returns intermediate result code +CHSR: <type> from the TA to the TE when an HSCSD call is being set up. The result code represents the current (negotiated or renegotiated) HSCSD parameters. If enabled, the intermediate result code is transmitted at the point of the call setup negotiation where the TA has determined what type of an HSCSD connection will be used. Result code transmission is done after possible service (+CR), error control (+ER), and/or compression (+DR) reporting but before possible TE-TA rate (+ILRR) reporting and before the intermediate result code CONNECT is transmitted. The format of the intermediate result code is:

+CHSR: <rx>, <tx>, <aiur>, <coding>

For the value definitions, refer 22.3 +CHSN and 22.4 +CHSC commands. For instance, for a non-transparent HSCSD call, result code “+CHSR: 2,2,4,8” means that the call has two timeslots in both up- and downlink, the air interface user rate is 28800 bps, and the used channel coding TCH/F14.4.


0 disables reporting

1 enables reporting


+CHSR=[<mode>]

+CHSR? +CHSR: <mode>

+CHSR=? +CHSR: (list of supported <mode>s)

HSCSD 161

1

GPRS

+CGDCONT - Define PDP Context


Description

The set command specifies PDP context parameter values for a PDP context identified by the (local) context identification parameter, <cid>. The number of PDP 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 set command, +CGDCONT= <cid> causes the values for context number <cid> to become undefined.

The read command returns the current settings for each defined context.

The test command returns values supported as a compound value. If the GC75 supports several PDP types, <PDP_type>, the parameter value ranges for each <PDP_type> are returned on a separate line.

Parameter-Values <cid>: (PDP Context Identifier) a numeric parameter which specifies a

particular PDP context definition. The parameter is local to the TE-GC75 interface and is used in other PDP context-related commands. The range of permitted values (minimum value = 1) is returned by the test form of the command.


+CGDCONT=[<cid>[,<PDP_type>[,<APN>[,<PDP_addr>[,<d_comp>[,<h_comp>[,<pd1>[,.[,pdN]]]]]]]]]

+CGDCONT? +CGDCONT: <cid>,<PDP_type>,<APN>,<PDP_addr>,<data_comp>,<head_comp> [,<pd1>[,.[,pdN]]][<CR><LF> +CGDCONT: <cid>, <PDP_type>,<APN>,<PDP_addr>, <data_comp>,<head_comp> [,<pd1>[,.[,pdN]]] [...]]

+CGDCONT=? +CGDCONT: (range of supported <cid>s), <PDP_type>,,,(list of supported <d_comp>s),(list of supported <h_comp>s) [,(list of supported <pd1>s)[,.[,(list of supported <pdN>s)]]] [<CR><LF> +CGDCONT: (range of supported <cid>s), <PDP_type>,,, (list of supported <d_comp>s),(list of supported <h_comp>s) [,(list of supported <pd1>s)[,.[,(list of supported <pdN>s)]]] [...]]

62 GPRS

<PDP_type>: (PDP type) a string parameter which specifies the type of packet data protocol IP Internet Protocol (IETF STD 5)

<APN>: (Access Point Name) a string parameter which is a 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_address>: a string parameter that identifies the MT in the address space applicable to the PDP. If the value is null or omitted, then a value may be provided by the TE during the PDP start-up procedure or, failing that, a dynamic address will be requested. The read form of the command will continue to return the null string even if an address has been allocated during the PDP start-up procedure. The allocated address may be read using the +CGPADDR command.

<d_comp>: a numeric parameter that controls PDP data compression

0 off (default if value is omitted)

1 on

<h_comp>: a numeric parameter that controls PDP header compression

0 off (default if value is omitted)

1 on

Note! At present only one data compression algorithm (V42bis) is provided in SNDCP. If and when other algorithms become available, a command will be provided to select one or more of these.

<pd1>, . <pdN>: zero to N string parameters whose meanings are specific to the <PDP_type>. At present none is defined.

GPRS 163

+CGQREQ - Quality of Service Profile (Requested)


Description

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>. Since this is the same parameter that is used in the +CGDCONT command, the +CGQREQ command is effectively an extension to the +CGDCONT command. The QoS profile consists of a number of parameters, each of which may be set to a separate value.

A special form of the set command, +CGQREQ=<cid> causes the requested profile for context number <cid> to become undefined.


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.

Parameter-Values <cid>: a numeric parameter which specifies a particular PDP context

definition (see +CGDCONT command).

The following parameters are defined in GSM 03.60 [11] -


+CGQREQ=[<cid> [,<precedence > [,<delay>[,<reliability.> [,<peak>[,<mean>]]]]]]

+CGQREQ? +CGQREQ: <cid>, <precedence >, <delay>, <reliability>, <peak>, <mean>[<CR><LF> +CGQREQ: <cid>, <precedence >, <delay>, <reliability.>, <peak>, <mean> [.]]

+CGQREQ=? +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) [<CR><LF> +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) [.]]

164 General

<precedence>: a numeric parameter which specifies the precedence class

<delay>: a numeric parameter which specifies the delay class

<reliability>: a numeric parameter which specifies the reliability class

<peak>: a numeric parameter which specifies the peak throughput class

<mean>: a numeric parameter which specifies the mean throughput class

If a value is omitted for a particular class then the value is considered to be

unspecified.

+CGQMIN - Quality of Service Profile (Minimum acceptable)


Description

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>. Since this is the same parameter that is used in the +CGDCONT command, the +CGQMIN command is effectively an extension to the +CGDCONT command. The QoS profile consists of a number of parameters, each of which may be set to a separate value.

A special form of the set command, +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.


+CGQMIN=[<cid> [,<precedence> [,<delay> [,<reliability> [,<peak> [,<mean>]]]]]]

+CGQMIN? +CGQMIN: <cid>, <precedence >, <delay>, <reli-ability>, <peak>, <mean>[<CR><LF> +CGQMIN: <cid>, <precedence >, <delay>, <reli-ability.>, <peak>, <mean> [.]]

+CGQMIN=? +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)[<CR><LF> +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) [.]]

GPRS 165

1


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.

Parameter-Values

See Parameter-Values section in previous chapter.

+CGATT - GPRS attach or detach


Description

The execution 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. If the requested state cannot be achieved, an ERROR or +CME ERROR response is returned

Any active PDP contexts will be automatically deactivated when the attachment state changes to detached.

The read command returns the current GPRS service state.

The test command is used for requesting information on the supported GPRS service states.

Note! This command has the characteristics of both the V.250 action and parameter commands. Hence it has the read form in addition to the execution/set and test forms.

Parameter-Values <state>: indicates the state of GPRS attachment

0 detached

1 attached


+CGATT= <state>

+CGATT? +CGATT: <state>

+CGATT=? +CGATT: (list of supported <state>s)

66 GPRS

+CGACT - PDP context activate or deactivate

Action/Parameter command syntax

Description

The execution 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 requested state for any specified context cannot be achieved, an ERROR or +CME ERROR response is returned.

If the MT is not GPRS attached when the activation form of the command is executed, the MT first performs a GPRS attach and them attempts to activate the specified contexts. If the attach fails then the MT responds with ERROR or, if extended error responses are enabled, with the appropriate failure-to-attach error message.

If no <cid>s are specified the activation form of the command activates all defined contexts.

The read command returns the current activation states for all the defined PDP contexts.

The test command is used for requesting information on the supported PDP context activation states.

Note! This command has the characteristics of both the V.250 action and parameter commands. Hence it has the read form in addition to the execution/set and test forms.

Parameter-Values <state> indicates the state of PDP context activation

0 deactivated

1 activated

<cid> a numeric parameter which specifies a particular PDP context definition (see AT +CGDCONT command).


+CGACT=<state>,[<cid>[,<cid>[,.]]]

+CGACT? +CGACT: <cid>, <state>[<CR><LF> +CGACT: <cid>, <state> [...]]

+CGACT=? +CGACT: (list of supported <state>s)

GPRS 167

1

+CGDATA - Enter data state


Description

The execution command causes the MT to perform whatever actions 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. If the <L2P> parameter value is unacceptable to the MT, the MT shall return an ERROR or +CME ERROR response. Otherwise, the MT issues the intermediate result code CONNECT and enters V.250 online data state.

Commands following +CGDATA command in the AT command line shall not be processed by the MT.

The detailed behaviour after the online data state has been entered is dependent on the PDP type. It is described briefly in more detail in GSM 09.61 [20] and the specifications for the relevant PDPs. GPRS attachment and PDP context activation procedures may take place prior to or during the PDP start-up if they have not already been performed using the AT+CGATT and AT +CGACT commands.

If context activation takes place during the PDP start-up, one or more <cid>s may be specified in order to provide the information needed for the context activation request(s).

During each PDP start-up procedure the MT may have access to some or all of the following information:

• The MT may have a prior knowledge, for example, it may implement only one PDP type.

• The command may have provided an <L2P> parameter value.

• The TE may provide a PDP type and/or PDP address to the MT during in the PDP start-up procedure.

If any of this information is in conflict, the command will fail.

Any PDP type and/or PDP address present in the above information shall be compared with the PDP type and/or PDP address in any context definitions specified in the command in the order in which their <cid>s appear.

For a context definition to match:

• The PDP type must match exactly.

• The PDP addresses are considered to match if they are identical or if either or both addresses are unspecified. For example, a PPP NCP request specifying PDP type = IP and no PDP address would cause the MT to search through the specified context definitions for one with PDP type = IP and any PDP address.


+CGDATA=[<L2P>,[<cid>[,<cid> [,.]]]] CONNECT

+CGDATA=? +CGDATA: (list of supported <L2P>s)

68 GPRS

• The context shall be activated using the matched value for PDP type and a static PDP address if available, together with the other information found in the PDP context definition. If a static PDP address is not available then a dynamic address is requested.

If no <cid> is given or if there is no matching context definition, the MT shall attempt to activate the context with whatever information is available to the MT. The other context parameters shall be set to their default values.

If the 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 re-entered 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.

The test command is used for requesting information on the supported layer 2 protocols.


Parameter-Values <L2P> a string parameter that indicates the layer 2 protocol to be used

between the TE and MT

“PPP” Point-to-point protocol for a PDP such as IP

<cid> a numeric parameter which specifies a particular PDP context definition (see “+CGDCONT - Define PDP Context”, page 162).

+CGPADDR - Show PDP address


Description

The execution command returns a list of PDP addresses for the specified context identifiers.

The test command returns a list of defined <cid>s.


+CGPADDR=[<cid> [,<cid> [,.]]]

+CGPADDR: <cid>,<PDP_addr>[<CR><LF> +CGPADDR: <cid>,<PDP_addr> [...]]

+CGPADDR=? +CGPADDR: (list of defined <cid>s)

GPRS 169

1

Parameter-Values <cid>: a numeric parameter which specifies a particular PDP context

definition (see AT+CGDCONT command). If no <cid> is specified, the addresses for all defined contexts are returned.

<PDP_address>: a string that identifies the MT in the address space applicable to the PDP. The address may be static or dynamic. For a static address, it will be the one set by the AT+CGDCONT command when the context was defined. For a dynamic address it will be the one assigned during the last PDP context activation that used the context definition referred to by <cid>. <PDP_address> is omitted if none is available.

+CGEREP - GPRS event reporting



Description

Set command enables or disables sending of unsolicited result codes, +CGEV: <text> 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.


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


+CGEREP=[<mode>[,<bfr>]]

+CGEREP? +CGEREP: <mode>, <bfr>

+CGEREP=? +CGEREP: (list of supported <mode>s), (list of supported <bfr>s)

+CGEV: <text>

70 GPRS

MT-TE link becomes available; otherwise forward them directly to the TE.

<bfr>:

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 shall be given before flushing the codes)

<text>

• REJECT <PDP_type>, <PDP_addr>

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

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

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

• NW DETACH The network has forced a GPRS detach. This implies that all active contexts have been deactivated. These are not reported separately.

• ME DETACH The mobile equipment has forced a GPRS detach. This implies that all active contexts have been deactivated. These are not reported separately.

• NW CLASS <class> The network has forced a change of MS class. The highest available class is reported (see +CGCLASS).

• ME CLASS <class> The mobile equipment has forced a change of MS class. The highest available class is reported (see +CGCLASS).

GPRS 171

1

+CGREG - GPRS network registration status



Description

The set command controls the presentation of an unsolicited result code +CGREG and there is a change in the MT’s GPRS network registration status, or there is a change of the network cell.

Note! If the GPRS MT also supports circuit mode services, the +CREG command and +CREG result code apply to the registration status and location information for those services.

The read command returns the status of result code presentation and an integer <stat> which shows whether the network has currently indicated the registration of the MT. Location information elements <lac> and <ci> are returned only when <n>=2 and MT is registered in the network.

Refer to “+CME ERROR: <err> - Mobile Equipment error result code”, page 189 for possible <err> values.

Parameter-Values <n>

0 disable network registration unsolicited result code. Default.

1 enable network registration unsolicited result code +CGREG:

<stat>

2 enable network registration and location information unsolicited result code +CGREG: <stat>[,<lac>,<ci>]

<stat>

0 not registered, ME is not currently searching a new operator to register to

1 registered, home network

2 not registered, but ME is currently searching a new operator to register to


+CME ERROR: <err>

+CGREG=[<n>]

+CGREG? +CGREG: <n>, <stat>[,<lac>, <ci>]

+CGREG=? +CGREG: (list of supported <n>s)

+CGREG: <stat>[,<lac>,<ci>]

72 GPRS

3 registration denied

4 unknown

5 registered, roaming

<lac> string type; two byte location area code in hexadecimal format (e.g. “00C3” equals 195 in decimal)

<ci> string type; two byte cell ID in hexadecimal format


+CGSMS - Select service for MO SMS messages


Description

The set command is used to specify the service or service preference that the MT will use to send MO SMS messages.

The read command returns the currently selected service or service preference.

The test command is used for requesting information on the currently available services and service preferences.

Parameter-Values <service> a numeric parameter which indicates the service or service

preference to be used

0 GPRS

1 circuit switched

2 GPRS preferred (use circuit switched if GPRS not available).

3 circuit switched preferred (use GPRS if circuit switched not available). Default.


+CGSMS=[<service>]

+CGSMS? +CGSMS: <service>

+CGSMS=? +CGSMS: (list of currently available <service>s)

GPRS 173

1

SATK 2.0

Display Text (Module -> PDA)

Upon receiving this command, PDA will display the text to the user. After the text has been displayed, a response will be returned back to GSM/GPRS module.

Command

*MTDISP:<priority>,<clear><CR><LF><data>

Response

AT*MTRES = 0,<result>,[<result2>]

GET INKEY (Module -> PDA)

PDA will display the text message provided in *MTKEY. The single character or digit shall be returned to GSM/GPRS module.

Command

*MTKEY: <input>,<alphabet>,<resp> <CR><LF><data>

<priority> 0 = normal priority1 = high priority

<clear> 0 = clear message after a delay (60s)1 = wait for user to clear message

<data> Text of message to be displayed. 160 characters or 140 bytes

<result> Possible results are as follows. Please see “TERMINAL RESPONSE (PDA->Module)”, page 181 for more details.0 = command performed successfully10 = Proactive SIM session terminated successfully11 = backward move in proactive SIM session requested 20 = ME currently unable to process command (<result2> required)

<result2> 1 = screen busy

<input> 0 = 0-9,*,#,+ only1 = alphabet set

<alphabet> 0 = SMS default alphabet1 = UCS2 alphabete

<resp> 0 = <input> and <alpha> enabled1 = <input> and <alpha> disabled, yes/no expected.

<data> Text to be displayed.

74 SATK 2.0

Response

The response to GET INKEY is TERMINAL RESPONSE as follows:

AT*MTRES=1,<result>,,<text>]

GET INPUT (Module -> PDA)

PDA will display this request for input from the SIM Toolkit application. Data entered by the user shall be returned to GSM/GPRS module.

Command

*MTGIN: <input>,<alphabet>,<echo>,<minl>,<maxl> <CR><LF><data>

Response

The response to GET INPUT is TERMINAL RESPONSE as follows:

<result> Possible results are as follows. 0 = command performed successfully10 = Proactive SIM session terminated successfully11 = backward move in proactive SIM session requested 12 = no response from user

<text> 0-9,*,# or + single digitA single character from GSM 3.38 SMS default alphabet, unpacked"YES""NO"

<input> 0 = 0-9,*,#,+ only1 = alphabet set

<alphabet> 0 = SMS default alphabet1 = UCS2 alphabete

<echo> 0 = echo user input on display1 = hide user input

<minl> 0 = no minimum length1-255 = minimum length

<maxl> 255 = no maximum length0-254 = maximum length

<data> Text to be displayed

SATK 2.0 175

1

AT*MTRES=2,<result>,,<text>

MENU SELECTION (Module <- PDA)

User has selected a menu item set up by the SET UP MENU proactive command from the SIM.

Command

AT*MTMENU=<item>

Response

N/A

PLAY TONE (Module -> PDA)

GSM/GPRS module supports GSM 2.40 and handle those tones as follows:

Command

*MTTONE: [<alphaid>],<tone>, [<unit>,<duration>]

<result> Possible results are as follows.Please see “TERMINAL RESPONSE (PDA->Module)”, page 181 for more details.0 = command performed successfully10 = Proactive SIM session terminated successfully11 = backward move in proactive SIM session requested 12 = no response from user

<text> 0-9,*,# or + single digitGSM 3.38 SMS default alphabet, unpacked.

<Item> 1-255 = menu item selected (corresponds with item in SET UP MENU)

<alphaid> Text to display during tone

<tone> 8 = Ringing tone10 = General beep11 = positive acknowledgement12 = negative acknowledgement

<unit> 0 = Minutes1 = Seconds2 = Tenths of seconds

<interval> 1-255 of units

76 SATK 2.0

Response

The response to PLAY TONE is TERMINAL RESPONSE as follows:

AT*MTRES=3,<result>

REFRESH (Module -> PDA)

The only option of REFRESH command PDA is interested in is SIM Reset. After receive REFRESH command, PDA can notify user about the SIM reset. It can then reset GSM/GPRS module if necessary.

Command

*MTRSH

Response

AT*MTRES=10, 0

SELECT ITEM (Module -> PDA)

PDA will display a list of items and return the selected item to GSM/GPRS module.

Command

*MTITEM: [<title>],<id1>,<text>[<CR><LF><id2>,<text><CR><LF>….<idn><textn>]

Response

The response to SELECT ITEM is TERMINAL RESPONSE as follows.

<result> Possible results are as follows.Please see “TERMINAL RESPONSE (PDA->Module)”, page 181 for more details.0 = command performed successfully10 = Proactive SIM session terminated successfully11 = backward move in proactive SIM session requested 30 = Command beyond ME’s capabilities

<title> text describing menu

<id> 1-255 Identifier of menu item

<text> text of menu item

SATK 2.0 177

1

AT*MTRES=4,<result>,,,<id>

SEND SHORT MESSAGE (Module -> PDA)

GSM/GPRS will be responsible for sending the SIM Toolkit application SMS message. The result of sending the message shall be reported to PDA, which will display an information box indicating that an SMS message was sent. However, this will be received "after the fact". If <alphaid> is not sent with the AT command, then PDA will inform the user that an SMS had been sent with a generic display message. If the Alpha id is valid then it will be displayed. If the SEND SHORT MESSAGE command from the SIM contains an empty/NULL Alpha Identifier, then this AT command shall not be sent to PDA.

Command

*MTSMS: [<alphaid>],<result>

Response

AT*MTRES=11, 0

SEND SS (Module -> PDA)

The PDA need to parse the SSstring and initiate the SS procedures. When the alpha id is sent by the SIM toolkit application, it will be displayed while PDA is processing the Supplementary Service procedure. If the alpha id indicates that it is empty, then no indication is given to the user that a supplementary service procedure is being processed. If no alpha id is provided, then the normal procedures for processing a supplementary service procedure shall be followed. The SS procedure will not be included in the Last Number Dialed list.

<result> Possible results are as follows.Please see “TERMINAL RESPONSE (PDA->Module)”, page 181 for more details.0 = command performed successfully10 = Proactive SIM session terminated successfully11 = backward move in proactive SIM session requested 12 = No response from user


<alphaid> Text message to be displayed for SMS message

<result> 0 = message succeeded1 = message failed

78 SATK 2.0

Command

*MTSS: [<alphaid>],<SSstring>

Response

The response to SEND SS is TERMINAL RESPONSE as follows:

AT*MTRES=5,0

SEND USSD (Module -> PDA) (Class 3 Feature)

The PDA will support parsing the USSDstring and initiating the USSD procedures. When the alpha id is sent by the SIM toolkit application, it will be displayed while PDA is processing the initial USSD procedure. If the alpha id indicates that it is empty, then no indication is given to the user that a USSD procedure is being processed. If no alpha id is provided, then the normal procedures for processing a USSD procedure shall be followed. The USSD procedure will not be included in the Last Number Dialed list.

Command

*MTUSSD: [<alphaid>],<USSDstring>

Response

The response to SEND USSD is TERMINAL RESPONSE as follows:

AT*MTRES=6,0

SET UP CALL (Module -> PDA)

PDA will handle the initiation of new calls by the SIM Toolkit.

<alphaid> Text message to be displayed while processing Supplementary Service string. "NULL" indicates an empty <alphaid>

<SSstring> a supplementary service control procedure

<alphaid> Text message to be displayed while processing USSD string. "NULL" indicates an empty <alphaid>

<USSDstring> The USSD string to be sent to the network

SATK 2.0 179

1

Command

*MTCALL: <mode>,[<alphaid>],<dest>,[<unit>,<interval>]

Response

The response to SET UP CALL is TERMINAL RESPONSE as follows:

AT*MTRES=7,<result>,<result2>

<mode> 0 = set up call, but only if not currently busy on another call 1 = set up call, but only if not currently busy on another call, with redial 2 = set up call, putting all other calls (if any) on hold 3 = set up call, putting all other calls (if any) on hold, with redial 4 = set up call, disconnecting all other calls (if any) 5 = set up call, disconnecting all other calls (if any), with redial

<alphaid> Text message to be displayed while setting up the call

<dest> Destination address (called party number)

<unit> time unit for redial duration

0 = minutes

1 = seconds

2 = tenths of seconds

<interval> 1-255 of <unit>

<result> Possible results are as follows. Please see 1.13 for more. 0 = command performed successfully 10 = Proactive SIM session terminated successfully 11 = backward move in proactive SIM session requested 12 = No response from user 20 = ME currently unable to process command (require <result2>) 21 = Network currently unable to process command 22 = User did not accept call set-up request 23 = User cleared down call before connection or network release 30 = Command beyond ME’s capabilities 34 = SS Return Error (GSM module must provide the error cause)

<result2> 2 = ME currently busy on call 3 = ME currently busy on SS transaction

80 SATK 2.0

SET UP MENU (Module -> PDA)

The SET UP MENU command is used to add SIM applications for selection to the PDA application menu system. The SET UP MENU command is also used to remove SIM applications from the menu system.

Command

*MTSMENU: <alphaid>,<id1>,<text1>[,<CR><LF><id2>,<text2><CR><LF>,…<idn>,<textn>

Response

The response to SET UP MENU is TERMINAL RESPONSE as follows:

AT*MTRES=8,<result>

TERMINAL RESPONSE (PDA->Module)

This AT command provides the method for responding to the SIM Toolkit command. PDA will provide as much information that is known. But in some instances, GSM/GPRS will have more detailed information and is expected to provide it in the final TERMINAL RESPONSE sent to the SIM.

<alphaid> Text description of menu. "NULL" if <alphaid> is not available

<id> 1-255 Item number of menu item

<text> Text for menu item

<result> 0 = command performed successfully 30 = Command beyond ME's capabilities

SATK 2.0 181

1

Command

AT*MTRES=<command>,<result>,[<result2>],[<text>],[<id>]

Response

OK

<command> 0 = DISPLAY TEXT 1 = GET INKEY 2 = GET INPUT 3 = PLAY TONE 4 = SELECT ITEM 5 = SEND SS 6 = SEND USSD 7 = SET UP CALL 8 = SET UP MENU

<result> 0 = command performed successfully 10 = Proactive SIM session terminated successfully 11 = backward move in proactive SIM session requested 12 = no response from user 14 = USSD transaction terminated by the user 20 = ME currently unable to process command 21 = Network currently unable to process command 22 = User did not accept call set-up request 23 = User cleared down call before connection or network release 30 = Command beyond ME’s capabilities 31 = Command type not understood by ME 32 = Command data not understood by ME 33 = Command number not known by ME 34 = SS Return Error (GSM module must provide the error cause) 36 = Error, required values are missing 37 = USSD Return Error (GSM module must provide the error cause)

<result2> 0 = No specific cause can be given 1 = screen is busy 2 = ME currently busy on call 3 = ME currently busy on SS transaction 7 = not in speech call 8 = ME currently busy on USSD transaction

<text> 0-9,*,#,+ GSM 3.38 SMS default alphabet (unpacked) Yes/No


82 SATK 2.0

CME ERROR

Polling Off

N/A

Provide Local Information

N/A

SATK 2.0 183

1

Sony Ericsson Specific Commands

*ECAM - Sony Ericsson Call Monitoring



Description

This command activates or deactivates the call monitoring function in the ME.

When this log function is activated in the ME, the ME informs about call events, such as incoming call, connected, hang up, etc.

Current status shall always be sent with result code *ECAV when activating the log function. The purpose of this is following:

• To gather relevant information for the call log in a TE.

• To make it possible for the TE to display call state information for an ongoing call.

This is an unsolicited result code which reports changes in Call State for a certain call indicated by <ccid> when the unsolicited event has been enabled with the *ECAM command and any state change occur.

Parameter-Values <onoff>:

0 The call log function is disabled (off)

1 The call log function is enabled (on)

<ccid>: Integer (1-7), A number which uniquely defines a call in the phone (= number of call control process). There can not be two call id.s with the same number simultaneously. The maximum number of call control process is 7, 5 multiparty members, one call on hold and one waiting call.


+CME ERROR: <err>

*ECAM =<onoff>

*ECAM? *ECAM: <onoff>

*ECAM =? *ECAM: (list of supported <onoff>s)


*ECAV: <ccid>, <<ccstatus>, <calltype>, [<processid>], [<exutcause>], [<number>, <type>]

84 Sony Ericsson Specific Commands

<ccstatus>:

0 Idle5

1 Calling (MO)

2 Connected (MO) 5Idle state means that the MS is registered to the network, but there is no call/session is established from/to the MS. In this state, the MS informs the network about its new location when it moves from one Location/Routing area to another one.

3 Active (connection between A and B)

4 Hold

5 Waiting (MT)

6 Alerting (MT)

7 Busy

<calltype>:

2 Data

4 Fax

<porcessid>: Reported when returning to the Idle state (<ccstatus> = 0)

8 H’08’ = CC (Call Control)

68 H’44’ = MM (Mobile Management)

69 H’45’ = MS (Mobile Station)

122 H’7A’ = RR (Radio Resources)

<exitcause>: Exit cause according to GSM 04.08 [13]. Reported when returning to Idle state (<ccstatus> = 0).

<number>: String type phone number of format specified by <type>. Only valid for <ccstatus> = 1 (CALLING)

<type>: Integer. Type of address octet in integer format (refer to GSM 04.08 [13]). Default 145 when dialing string includes international access code character “+”, otherwise 129. Only valid for <ccstatus> =1 (CALLINT).


Sony Ericsson Specific Commands 185

1

*ESIMC - SIM Insert/Removal indication



Description

Disables sending of unsolicited result codes (see comments) from TA to TE in the case of the insertion or removal of the SIM.

Read command returns the current mode.

Test command returns the modes supported by the TA as a compound value.


0 This turns on the notification.

1 This turns off the notification

<status>

0 Removed

1 Inserted

*EPRO . Sony Ericsson get provider name


Description

This command is used to get the name of the service provider stored in the SIM card.



*ESIMC=[<mode>]

*ESIMC? *ESIMC: <mode>

*ESIMC=? *ESIMC: (list of currently available <mode>s)

*ESIMM: <status>


*EPRO *EPRO: <name>

*EPRO=?


Parameter-Values <name> String value (Service provider name)

*ECIPC - Enable/Disable Ciphering Command



Description

This command is used to indicate to the user that ciphering is turned on or turned off.

Parameter-Values <onOff>

0 This turns off the notification. Default.

1 This turns on the notification

<mode>

0 Ciphering Disabled

1 Ciphering Enabled

*EPNR - Sony Ericsson Read SIM Preferred Network


Description

Used to read the SIM preferred list of network (EFPLMNsel). It returns entries in location range <index1> - <index2>. If <index2> is omitted only location <index1> is returned. If both <index1> and <index2> is omitted, i.e. only <format> is stated, the whole list is presented.


*ECIPC=[<OnOff>]

*ECIPC? *ECIPC: <OnOff>

*ECIPC=? *ECIPC: (0,1)

*ECIPM: <mode>


*EPNR=<format>[,<index1>[,<index2]] *EPNR: <index1>,<oper1>[...]

*EPNR =? *EPNR: (1-2),2

Sony Ericsson Specific Commands 187

1

Parameter-Values <format>

0 Long format alphanumeric <oper>. Not supported

1 Short format alphanumeric <oper>. Not supported

Numeric <oper>.Default=2

<index1> Integer Start index (>0)

<index2> Integer Stop index (>0)

<oper> String indicates the code for the operator. E.g. GSM/DCS: “24008” Sweden - Europolitan (3 + 2). PCS: 3 digits for Country and 3 digits for Network.

*EPNW - Sony Ericsson Write SIM Preferred Network


Description

Used to edit the SIM preferred list of networks (EF-PLMNsel).

Parameter-Values <index> Integer Index to entry in SIM preferred list. The SIM preferred list

contains at least 8 positions according to GSM 11.11 [21].

<format>

0 Long format alphanumeric <oper>. Not supported

1 Short format alphanumeric <oper>. Not supported

<oper> String indicates the code for the operator. E.g. GSM .Sweden - Europolitan:“24008” (3 + 2). PCS: 3 digits for Country and 3 digits for Network.


*EPNW=[<index>][,<format>,<oper>] *EPNW: [<index>] [,<format>, <oper>]

*EPNW =? *EPNW: (1-2),2


Error Messages

+CME ERROR: <err> - Mobile Equipment error result code


Description

The operation of +CME ERROR result code is similar to the regular ERROR result code: if +CME ERROR is the result code for any of the commands in a command line, none of the following commands in the same command line is executed (neither ERROR nor OK result code shall be returned as a result of a completed command line execution). The format of <err> can be either numeric or verbose. This is set with command +CMEE.

Note! ITU-T V.25ter [28] command V does not affect the format of this result code.

Parameter-Values <err> <text>

0 phone failure

1 no connection to phone

2 phone-adaptor 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

+CME ERROR: <err>

189 General

1

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 personalisation PIN required

41 network personalisation PUK required

42 network subset personalisation PIN required

43 network subset personalisation PUK required

44 service provider personalisation PIN required

45 service provider personalisation PUK required

46 corporate personalisation PIN required

47 corporate personalisation PUK required

100 unknown

103 Illegal MS (GPRS #3)

106 Illegal ME (GPRS #6)

107 GPRS services not allowed (GPRS #7)

111 PLMN not allowed (GPRS #11)

112 Location area not allowed (GPRS #12)

113 Roaming not allowed in this location area (GPRS #13)

132 service option not supported (GPRS #32)

133 requested service option not subscribed (GPRS #33)

134 service option temporarily out of order (GPRS #34)

148 unspecified GPRS error

149 PDP authentication failure (GPRS) (#Values in parentheses are GSM 04.08 [13] cause codes.)

150 invalid mobile class

256 busy, is in search of current operator

90 Error Messages

+CMS ERROR . Message Failure Result Code

Message Failure Result Code Syntax

Description

Final result code +CMS ERROR: <err> indicates an error related to mobile equipment or network. The operation is similar to ERROR result code. None of the following commands in the same command line is executed. Neither ERROR nor OK result code shall be returned. ERROR is returned normally when error is related to syntax or invalid parameters.

Parameter-Values <err> values used by common messaging commands:

0...127 GSM 04.11 [14] Annex E-2 values

128...255 GSM 03.40 [9] subclause 9.2.3.22 values

300 ME failure

301 SMS service of ME reserved

302 operation not allowed

303 operation not supported

304 invalid PDU mode parameter

305 invalid text mode parameter

310 SIM not inserted

311 SIM PIN required

312 PH-SIM PIN required

313 SIM failure

314 SIM busy

315 SIM wrong

316 SIM PUK required

317 SIM PIN2 required

318 SIM PUK2 required

320 memory failure

321 invalid memory index

322 memory full

330 SMSC address unknown

331 no network service

332 network timeout

340 no +CNMA acknowledgement expected

500 unknown error

+CMS ERROR: <err>

Error Messages 191

1

References

[1] GSM 02.02: “Digital Cellular telecommunications system (Phase 2+); Bearer Services (BS) supported by a GSM Public Land Mobile Network (PLMN)” version 7.0.2 Release 1998

[2] GSM 02.24: “Digital cellular telecommunication system (Phase 2+); Description of Charge Advice Information (CAI)”.

[3] GSM 02.30: “Digital cellular telecommunication system (Phase 2+); Man Machine Interface (MMI) of the Mobile Station (MS)”.

[4] GSM 02.34:“Digital cellular telecommunication system (Phase 2+); High Speed Circuit Switched Data (HSCSD) - Stage 1”.

[5] GSM 02.81: “Digital cellular telecommunication system (Phase 2+); Line identification supplementary services - Stage 1”.

[6] GSM 02.82: “Digital cellular telecommunication system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 1”.

[7] GSM 02.88: “Digital cellular telecommunication system (Phase 2+); Call Barring (CB) supplementary services - Stage 1”.

[8] GSM 03.38: “Digital cellular telecommunication system (Phase 2+); Alphabet and language specific information”.

[9] GSM 03.40: “Digital cellular telecommunication system (Phase 2+); Technical Realisation of the Short Message Service (SMS)”, version 7.4.0 Release 1998.

[10] GSM 03.41: “Digital Cellular telecommunications system (Phase 2+); Technical realisation of Cell Broadcast Service (CBS)”. version 7.3.0 Release 1998

[11] GSM 03.60: “Digital Cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Service description; Stage 2” version 7.4.0 Release 1998

[12] GSM 03.81: “Digital Cellular telecommunications system (Phase 2+); Line identification supplementary services; Stage 2”, version 7.0.1 Release 1998).

[13] GSM 04.08: “Digital cellular telecommunication system (Phase 2+); Mobile radio interface layer 3 specification”.

[14] GSM 04.11: “Digital cellular telecommunication system (Phase 2+); Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface” version 7.0.0 Release 1998

[15] GSM 04.22: “Digital cellular telecommunication system (Phase 2+); Radio Link Protocol (RLP) for data and telematic services on the Mobile Station - Base Station System (MS - BSS) interface and the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface”.

[16] GSM 05.08: “Digital cellular telecommunication system (Phase 2+); Radio subsystem link control”.

[17] GSM 07.05: “Digital cellular telecommunication system (Phase 2+); Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)”.

92 References

[18] GSM 07.07: “Digital Cellular telecommunications system (Phase 2+); AT command set for GSM Mobile Equipment (ME) ”.

[19] GSM 07.10: “Digital Cellular telecommunications system (Phase 2+); Terminal Equipment to Mobile Station (TE-MS) Multiplexer Protocol”, version 7.1.0 Release 1998

[20] GSM 09.61: “Digital cellular telecommunication system (Phase 2+); GPRS”[21] GSM 11.11: “Digital cellular telecommunication system (Phase 2+); Specification of the

Subscriber Identity Module - Mobile Equipment (SIM-ME) interface”.

[22] GSM MoU SE.13, GSM MoU Permanent Reference Document SE.13: “GSM Mobile Network Codes and Names”.

[23] ITU-T Recommendation E.212: “Identification plan for land mobile stations”.

[24] ITU-T Recommendation T.4: “Standardization of Group 3 Facsimile terminals for Document Transmission”.

[25] ITU-T Recommendation T.30: “Procedures for document facsimile transmission in the general switched telephone network”

[26] ITU-T Recommendation T.32: “Asynchronous facsimile DCE control, service class 2”.

[27] ITU-T Recommendation T.50: “International Reference Alphabet (IRA) (Formerly International Alphabet No. 5 or IA5) - Information technology - 7-bit coded character set for information exchange”.

[28] ITU-T Draft new Recommendation V.25ter: “Data communication over the telephone network; Serial asynchronous automatic dialing and control”.

[29] ITU-T Recommendation V.250: “Data communication over the telephone network; Control Procedures; Serial asynchronous automatic dialing and control”, version 05/99

References 193

Index

Symbols&C 52&D 53&F 23* 27+ 42, 85+++AT 48+CACM 41+CAMM 42+CAOC 40+CCWE 44+CFUN 37+CLAC 26+CPAS 46+CPUC 43+CPWC 45+CSTA 46+DR 64+DS 63+ER 62+ES 60+ETBM 61+FBO 66+FCC 67+FCI 84+FCLASS 65+FCO 87+FCQ 67+FCS 69, 84+FDM 87+FDR 70+FDT 71+FEA 72+FET 72+FHR 83+FHS 83+FHT 88+FIE 73+FIP 74+FIS 75, 82+FIT 75+FKS 76

+FLI 77+FLP 78+FNC 86+FNF 86+FNR 79+FNS 86+FPI 78, 85+FPO 85+FPP 80+FPS 81, 85+FSP 82+FTC 82+FTI 84+GCAP 27+GMI 24+GMM 25+GMR 26+IFC 54+ILRR 59+WS46 28

AA 29

DD 30D - Dial (non GPRS calls) 30

EE 50

HH 30

II 23

LL 36

MM 57

194 Index

OO 38

PP 39

QQ 51

SS0 55S10 57S3 48S4 49S5 50

S6 56S7 56

TT 39

VV 51

XX 58

ZZ 22

Index 195

GC75 at Commands R2A

Documents

Transcript of GC75 at Commands R2A