TANGO55/56

This document is available at HTTP://WWW.FALCOM.DE/

TANGO55/56

Hardware description

Version 1.00 16/06/2005

Preliminary

TANGO55/56 AT COMMAND SET VERSION 1.01

Contents

0 INTRODUCTION.....................................................................11

0.1

S

COPE OF THE DOCUMENT

.................................................................................................... 11

0.2

R

ELATED DOCUMENTS

........................................................................................................... 11

0.3

D

OCUMENT CONVENTIONS

................................................................................................... 12

0.3.1

Q

UICK REFERENCE TABLE

..........................................................................................................................12

0.3.2

S

UPERSCRIPT NOTATION FOR PARAMETERS AND VALUES

................................................................................12

0.4

AT

COMMAND SYNTAX

......................................................................................................... 13

0.4.1

U

SING PARAMETERS

.................................................................................................................................13

0.4.2

C

OMBINING

AT

COMMANDS ON THE SAME COMMAND LINE

.......................................................................14

0.5

S

UPPORTED CHARACTER SETS

................................................................................................. 14

0.5.1

GSM

ALPHABET TABLES AND

UCS2

CHARACTER VALUES

............................................................................17

0.5.2

UCS2

AND

GSM

DATA CODING AND CONVERSION FOR

SMS

TEXT MODE

...................................................18

0.5.2.1

Implementing input of Terminal data to SIM (direction TE to ME)......................................... 19

0.6

F

LOW

C

ONTROL

.................................................................................................................. 20

0.6.1

S

OFTWARE FLOW CONTROL

(XON/OFF

FLOW CONTROL

) ..........................................................................21

0.6.2

H

ARDWARE FLOW CONTROL

(RTS/CTS

FLOW CONTROL

) ...........................................................................21

0.7

U

NSOLICITED

R

ESULT

C

ODE

P

RESENTATION

............................................................................. 21

0.7.1

C

OMMUNICATION BETWEEN

C

USTOMER

A

PPLICATION AND

TANGO55/56 ................................................22

0.8

C

OMMON

PCN H

ANDSET

S

PECIFICATION

(CPHS)................................................................ 22

0.9

E

RRORS AND

M

ESSAGES

....................................................................................................... 23

1 CONFIGURATION COMMANDS...........................................24

1.1

AT&F S

ET ALL CURRENT PARAMETERS TO MANUFACTURER DEFAULTS

......................................... 24

1.2

AT&V D

ISPLAY CURRENT CONFIGURATION

............................................................................ 24

1.2.1

AT&V

RESPONSES

...................................................................................................................................25

1.3

AT&W S

TORES CURRENT CONFIGURATION TO USER DEFINED PROFILE

....................................... 25

1.4

ATQ S

ET RESULT CODE PRESENTATION MODE

......................................................................... 26

1.5

ATV S

ET RESULT CODE FORMAT MODE

................................................................................... 26

1.5.1

V

ERBOSE AND NUMERIC RESULT CODES

......................................................................................................27

1.6

ATX S

ET

CONNECT

RESULT CODE FORMAT AND CALL MONITORING

...................................... 27

1.7

ATZ S

ET ALL CURRENT PARAMETERS TO USER DEFINED PROFILE

.................................................. 27

1.8

AT+CFUN S

ET PHONE FUNCTIONALITY

................................................................................... 28

1.8.1

W

AKE UP THE

ME

FROM

SLEEP

MODE

......................................................................................................32

1.9

AT

^

SMSO S

WITCH OFF MOBILE STATION

................................................................................ 32

1.10

AT+GCAP R

EQUEST COMPLETE

TA

CAPABILITIES LIST

............................................................. 33

1.11

AT+CMEE R

EPORT MOBILE EQUIPMENT ERROR

..................................................................... 33

1.11.1

S

UMMARY OF

CME ERRORS

RELATED TO

GSM 07.07 ............................................................................35

1.11.2

S

UMMARY OF

GPRS-

RELATED

CME ERRORS..........................................................................................35

1.11.3

S

UMMARY OF

CMS ERRORS

RELATED TO

GSM 07.05 ............................................................................36

1.12

AT+CSCS S

ELECT

TE

CHARACTER SET

................................................................................... 37

1.13

AT

^

SCFG E

XTENDED

C

ONFIGURATION

S

ETTINGS

.................................................................. 38

1.14

AT

^

SM20 S

ET

M20

COMPATIBILITY MODE

............................................................................ 44

2 STATUS CONTROL COMMANDS...........................................45

2.1

AT+CMER M

OBILE

E

QUIPMENT

E

VENT

R

EPORTING

............................................................... 45

2.2

AT+CIND I

NDICATOR CONTROL

.......................................................................................... 46

This confidential document is the property of FALCOM GmbH and may not be copied or circulated without permission.

Page 2


2.3

AT

^

SIND E

XTENDED

I

NDICATOR

C

ONTROL

........................................................................... 49

2.4

AT+CEER E

XTENDED ERROR REPORT

.................................................................................... 51

2.4.1

C

AUSE

L

OCATION

ID

FOR THE EXTENDED ERROR REPORT

..............................................................................53

2.4.2

GSM

RELEASE CAUSE FOR

L3 R

ADIO

R

ESOURCE

(RR)................................................................................54

2.4.3

SIEMENS

RELEASE CAUSE FOR

L3 R

ADIO

R

ESOURCE

(RR) .........................................................................54

2.4.4

GSM

RELEASE CAUSE FOR

M

OBILITY

M

ANAGEMENT

(MM) ........................................................................55

2.4.5

SIEMENS

RELEASE CAUSE FOR

L3 M

OBILITY

M

ANAGEMENT

(MM) .............................................................55

2.4.6

GSM

RELEASE CAUSE FOR

L3 C

ALL

C

ONTROL

(CC).................................................................................55

2.4.7

SIEMENS

RELEASE CAUSE FOR

L3 C

ALL

C

ONTROL

(CC)...........................................................................57

2.4.8

SIEMENS

RELEASE CAUSE FOR

L3 A

DVICE OF

C

HARGE

(AOC).................................................................57

2.4.9

GSM R

ELEASE CAUSE FOR

S

UPPLEMENTARY

S

ERVICE

C

ALL

.........................................................................57

2.4.10

SIEMENS

RELEASE CAUSE FOR

C

ALL

-

RELATED

S

UPPLEMENTARY

S

ERVICES

(CRSS) ........................................58

2.4.11

SIEMENS

RELEASE CAUSE FOR

S

ESSION

M

ANAGEMENT

(SM) .....................................................................59

2.4.12

GSM

CAUSE FOR

L3 P

ROTOCOL MODULE OR OTHER LOCAL CAUSE

............................................................59

2.4.13

SIEMENS

RELEASE CAUSE FOR

GPRS API................................................................................................59

2.4.14

SIEMENS

RELEASE CAUSE FOR

E

MBEDDED

N

ETCORE

..................................................................................60

2.5

ATS18 E

XTENDED CALL RELEASE REPORT

............................................................................... 60

2.6

AT+CPAS M

OBILE EQUIPMENT ACTIVITY STATUS

.................................................................... 61

2.7

AT+WS46 S

ELECT WIRELESS NETWORK

.................................................................................. 61

3 SERIAL INTERFACE CONTROL COMMANDS ........................63

3.1

AT\Q F

LOWCONTROL

........................................................................................................ 63

3.2

AT&C S

ET CIRCUIT

D

ATA

C

ARRIER

D

ETECT

(DCD)

FUNCTION MODE

..................................... 63

3.3

AT&D S

ET CIRCUIT

D

ATA

T

ERMINAL

R

EADY

(DTR)

FUNCTION MODE

....................................... 64

3.4

AT&S S

ET CIRCUIT

D

ATA

S

ET

R

EADY

(DSR)

FUNCTION MODE

................................................. 64

3.5

ATE E

NABLE COMMAND ECHO

............................................................................................ 64

3.6

AT+ILRR S

ET

TE-TA

LOCAL RATE REPORTING

......................................................................... 65

3.7

AT+IPR S

ET FIXED LOCAL RATE

............................................................................................. 66

3.7.1

A

UTOBAUDING

........................................................................................................................................67

4 SECURITY COMMANDS ........................................................69

4.1

AT+CPIN E

NTER

PIN.......................................................................................................... 69

4.1.1

W

HAT TO DO IF

PIN

OR PASSWORD AUTHENTICATION FAILS

?........................................................................71

4.2

AT+CPIN2 E

NTER

PIN2...................................................................................................... 72

4.3

AT

^

SPIC D

ISPLAY

PIN

COUNTER

......................................................................................... 74

4.4

AT+CLCK F

ACILITY LOCK

................................................................................................... 78

4.5

AT

^

SLCK F

ACILITY LOCK

..................................................................................................... 83

4.6

AT+CPWD C

HANGE

P

ASSWORD

....................................................................................... 84

4.7

AT

^

SPWD C

HANGE

P

ASSWORD

......................................................................................... 88

5 IDENTIFICATION COMMANDS .............................................89

5.1

ATI D

ISPLAY PRODUCT IDENTIFICATION INFORMATION

............................................................. 89

5.2

AT+CGMI R

EQUEST MANUFACTURER IDENTIFICATION

............................................................ 89

5.3

AT+GMI R

EQUEST MANUFACTURER IDENTIFICATION

............................................................... 89

5.4

AT+CGMM R

EQUEST MODEL IDENTIFICATION

...................................................................... 90

5.5

AT+GMM R

EQUEST

TA

MODEL IDENTIFICATION

.................................................................... 90

5.6

AT+CGMR R

EQUEST REVISION IDENTIFICATION OF SOFTWARE STATUS

...................................... 91

5.7

AT+GMR R

EQUEST

TA

REVISION IDENTIFICATION OF SOFTWARE STATUS

................................... 91


Page 3


5.8

AT+CGSN R

EQUEST PRODUCT SERIAL NUMBER IDENTIFICATION

(IMEI)

IDENTICAL TO

GSN....... 91

5.9

AT+GSN R

EQUEST

TA

SERIAL NUMBER IDENTIFICATION

(IMEI) ................................................ 92

5.10

AT+CIMI R

EQUEST INTERNATIONAL MOBILE SUBSCRIBER IDENTITY

............................................. 92

6 CALL RELATED COMMANDS ................................................94

6.1

C

ALL

S

TATUS

I

NFORMATION

................................................................................................... 94

6.2

ATA A

NSWER A CALL

.......................................................................................................... 95

6.3

ATD M

OBILE ORIGINATED CALL TO DIAL A NUMBER

................................................................ 95

6.4

ATD><

MEM

><

N

> O

RIGINATE CALL TO PHONE NUMBER IN MEMORY

....................................... 98

6.5

ATD><

N

> O

RIGINATE CALL TO PHONE NUMBER SELECTED FROM ACTIVE MEMORY

................... 99

6.6

ATD><

STR

> O

RIGINATE CALL TO PHONE NUMBER IN MEMORY WITH CORRESPONDING FIELD

.... 100

6.7

ATDI M

OBILE ORIGINATED CALL TO DIALABLE

ISDN

NUMBER

<

N

> ........................................ 101

6.8

ATDL R

EDIAL LAST TELEPHONE NUMBER USED

....................................................................... 102

6.9

ATH D

ISCONNECT EXISTING CONNECTION

.......................................................................... 102

6.10

AT+CHUP H

ANG UP CALL

................................................................................................ 103

6.11

ATS0 S

ET NUMBER OF RINGS BEFORE AUTOMATICALLY ANSWERING THE CALL

.......................... 103

6.12

ATS6 S

ET PAUSE BEFORE BLIND DIALING

............................................................................... 104

6.13

ATS7 S

ET NUMBER OF SECONDS TO WAIT FOR CONNECTION COMPLETION

............................. 105

6.14

ATS8 S

ET NUMBER OF SECONDS TO WAIT FOR COMMA DIALING MODIFIER

.............................. 105

6.15

ATS10 S

ET DISCONNECT DELAY AFTER INDICATING THE ABSENCE OF DATA CARRIER

................. 106

6.16

ATP S

ELECT PULSE DIALING

................................................................................................ 106

6.17

ATO S

WITCH FROM COMMAND MODE TO DATA MODE

/PPP

ONLINE MODE

.......................... 106

6.18

+++ S

WITCH FROM DATA MODE TO COMMAND MODE

......................................................... 107

6.19

ATT S

ELECT TONE DIALING

................................................................................................. 107

6.20

AT+CBST S

ELECT BEARER SERVICE TYPE

.............................................................................. 107

6.21

AT+CRLP S

ELECT RADIO LINK PROTOCOL PARAM

.

FOR ORIG

.

NON

-

TRANSPARENT DATA CALL

108

6.22

AT+CLCC L

IST CURRENT CALLS OF

ME.............................................................................. 109

6.23

AT

^

SLCC S

IEMENS DEFINED COMMAND TO LIST THE CURRENT CALLS OF THE

ME .................... 111

6.24

AT+CR S

ERVICE REPORTING CONTROL

............................................................................... 117

6.25

AT+CRC S

ET

C

ELLULAR

R

ESULT

C

ODES FOR INCOMING CALL INDICATION

............................ 118

6.26

AT+CSNS S

INGLE

N

UMBERING

S

CHEME

............................................................................. 118

6.27

AT^SCNI L

IST

C

ALL

N

UMBER

I

NFORMATION

....................................................................... 119

6.28

AT

^

SLCD D

ISPLAY

L

AST

C

ALL

D

URATION

........................................................................... 120

6.29

AT

^

STCD D

ISPLAY

T

OTAL

C

ALL

D

URATION

......................................................................... 120

7 NETWORK SERVICE COMMANDS ......................................122

7.1

AT+COPN R

EAD OPERATOR NAMES

................................................................................. 122

7.2

AT+COPS O

PERATOR SELECTION

...................................................................................... 122

7.3

AT+CREG N

ETWORK REGISTRATION

.................................................................................. 124

7.4

AT+CSQ S

IGNAL QUALITY

................................................................................................ 126

7.5

AT

^

SMONC C

ELL

M

ONITORING

...................................................................................... 127

7.6

AT

^

MONI M

ONITOR IDLE MODE AND DEDICATED MODE

..................................................... 128

7.6.1

AT

^

MONI

RESPONSES

..........................................................................................................................129


Page 4


7.6.2

S

ERVICE STATES

......................................................................................................................................130

7.6.3

N

OTES

..................................................................................................................................................131

7.7

AT

^

MONP M

ONITOR NEIGHBOUR CELLS

............................................................................ 131

7.7.1

AT

^

MONP

RESPONSES

.........................................................................................................................132

7.8

AT

^

SMONG GPRS M

ONITOR

......................................................................................... 133

7.8.1

AT

^

SMONG C

ELL

I

NFO

T

ABLE

.............................................................................................................133

7.9

AT

^

SALS A

LTERNATE

L

INE

S

ERVICE

..................................................................................... 134

7.10

AT

^

SHOM D

ISPLAY

H

OMEZONE

........................................................................................ 135

7.11

AT

^

SPLM R

EAD THE

PLMN

LIST

......................................................................................... 135

7.12

AT

^

SPLR R

EAD ENTRY FROM THE PREFERRED OPERATORS LIST

................................................ 136

7.13

AT

^

SPLW W

RITE AN ENTRY TO THE PREFERRED OPERATORS LIST

............................................... 137

8 SUPPLEMENTARY SERVICE COMMANDS ...........................138

8.1

AT+CACM A

CCUMULATED CALL METER

(ACM)

RESET OR QUERY

...................................... 138

8.2

AT

^

SACM A

DVICE OF CHARGE AND QUERY OF

ACM

AND

ACM

MAX

............................... 138

8.3

AT+CAMM A

CCUMULATED CALL METER MAXIMUM

(ACM

MAX

)

SET OR QUERY

................... 140

8.4

AT+CAOC A

DVICE OF

C

HARGE INFORMATION

................................................................ 140

8.5

AT+CCUG C

LOSED

U

SER

G

ROUP

.................................................................................... 141

8.6

AT+CCFC C

ALL FORWARDING NUMBER AND CONDITIONS CONTROL

.................................. 142

8.7

AT+CCWA C

ALL

W

AITING

.............................................................................................. 146

8.8

AT+CHLD C

ALL

H

OLD AND

M

ULTIPARTY

........................................................................... 149

8.9

AT+CLIP C

ALLING LINE IDENTIFICATION PRESENTATION

........................................................ 151

8.10

AT+CLIR C

ALLING LINE IDENTIFICATION RESTRICTION

........................................................... 153

8.11

AT+CPUC P

RICE PER UNIT AND CURRENCY TABLE

............................................................... 154

8.12

AT+CSSN S

UPPLEMENTARY SERVICE NOTIFICATIONS

............................................................ 155

8.13

AT+CUSD S

UPPLEMENTARY SERVICE NOTIFICATIONS

........................................................... 156

9 GPRS COMMANDS .............................................................158

9.1

AT+CGACT PDP

CONTEXT ACTIVATE OR DEACTIVATE

........................................................ 158

9.2

AT+CGANS M

ANUAL RESPONSE TO A NETWORK REQUEST FOR

PDP

CONTEXT ACTIVATION

.... 159

9.3

AT+CGATT GPRS

ATTACH OR DETACH

............................................................................. 160

9.4

AT+CGAUTO A

UTOMATIC RESPONSE TO A NETWORK REQUEST FOR

PDP

CONTEXT

ACTIVATION

....................................................................................................................... 161

9.5

AT+CGDATA E

NTER DATA STATE

....................................................................................... 162

9.6

AT+CGDCONT D

EFINE

PDP C

ONTEXT

............................................................................. 164

9.7

AT+CGPADDR S

HOW

PDP

ADDRESS

............................................................................... 165

9.8

AT+CGQMIN Q

UALITY OF

S

ERVICE

P

ROFILE

(M

INIMUM ACCEPTABLE

)................................. 166

9.9

AT+CGQREQ Q

UALITY OF

S

ERVICE

P

ROFILE

(R

EQUESTED

).................................................. 169

9.10

AT+CGREG GPRS

NETWORK REGISTRATION STATUS

........................................................... 172

9.11

AT+CGSMS S

ELECT SERVICE FOR

MO SMS

MESSAGES

....................................................... 174

9.12

AT

^

SGAUTH S

ET TYPE OF AUTHENTICATION FOR

PPP

CONNECTION

...................................... 175

9.13

AT

^

SGCONF C

ONFIGURATION OF

GPRS

RELATED

P

ARAMETERS

......................................... 175

9.14

ATA M

ANUAL RESPONSE TO A NETWORK REQUEST FOR

PDP

CONTEXT ACTIVATION

................. 176

9.15

ATD*99# R

EQUEST

GPRS

SERVICE

..................................................................................... 176


Page 5


9.16

ATD*98# R

EQUEST

GPRS IP

SERVICE

................................................................................ 177

9.17

ATH M

ANUAL REJECTION OF A NETWORK REQUEST FOR

PDP

CONTEXT ACTIVATION

................ 178

9.18

ATS0 A

UTOMATIC RESPONSE TO A NETWORK REQUEST FOR

PDP

CONTEXT ACTIVATION

............ 179

9.19

U

SING

GPRS AT

COMMANDS

(E

XAMPLES

).......................................................................... 180

9.20

U

SING THE

GPRS

DIAL COMMAND

ATD .............................................................................. 182

10 FAX COMMANDS ...............................................................183

10.1

FAX

PARAMETERS

.............................................................................................................. 183

10.2

AT+FBADLIN B

AD

L

INE

T

HRESHOLD

................................................................................... 185

10.3

AT+FBADMUL E

RROR

T

HRESHOLD

M

ULTIPLIER

.................................................................... 185

10.4

AT+FBOR Q

UERY DATA BIT ORDER

..................................................................................... 186

10.5

AT+FCIG Q

UERY OR SET THE

L

OCAL

P

OLLING

ID................................................................. 186

10.6

AT+FCLASS F

AX

: S

ELECT

,

READ OR TEST SERVICE CLASS

....................................................... 187

10.7

AT+FCQ C

OPY

Q

UALITY

C

HECKING

.................................................................................. 187

10.8

AT+FCR C

APABILITY TO RECEIVE

........................................................................................ 188

10.9

AT+FDCC Q

UERY OR SET CAPABILITIES

............................................................................... 188

10.10

AT+FDFFC D

ATA

C

OMPRESSION

F

ORMAT

C

ONVERSION

..................................................... 189

10.11

AT+FDIS Q

UERY OR SET SESSION PARAMETERS

...................................................................... 189

10.12

AT+FDR B

EGIN OR CONTINUE PHASE

C

DATA RECEPTION

..................................................... 190

10.13

AT+FDT D

ATA

T

RANSMISSION

............................................................................................. 190

10.14

AT+FET E

ND A PAGE OR DOCUMENT

.................................................................................. 191

10.15

AT+FK K

ILL OPERATION

,

ORDERLY

FAX

ABORT

..................................................................... 191

10.16

AT+FLID Q

UERY OR SET THE

L

OCAL

I

D SETTING CAPABILITIES

.................................................. 192

10.17

AT+FMDL I

DENTIFY

P

RODUCT

M

ODEL

................................................................................ 192

10.18

AT+FMFR R

EQUEST

M

ANUFACTURER

I

DENTIFICATION

........................................................... 192

10.19

AT+FOPT S

ET BIT ORDER INDEPENDENTLY

............................................................................. 193

10.20

AT+FPHCTO DTE P

HASE

C R

ESPONSE

T

IMEOUT

................................................................. 193

10.21

AT+FREV I

DENTIFY

P

RODUCT

R

EVISION

............................................................................... 194

10.22

AT+FRH R

ECEIVE

D

ATA

U

SING

HDLC F

RAMING

................................................................. 194

10.23

AT+FRM R

ECEIVE

D

ATA

.................................................................................................... 194

10.24

AT+FRS R

ECEIVE

S

ILENCE

.................................................................................................. 195

10.25

AT+FTH T

RANSMIT

D

ATA

U

SING

HDLC F

RAMING

................................................................ 195

10.26

AT+FTM T

RANSMIT

D

ATA

................................................................................................... 196

10.27

AT+FTS S

TOP

T

RANSMISSION AND

W

AIT

............................................................................... 196

10.28

AT+FVRFC V

ERTICAL RESOLUTION FORMAT CONVERSION

.................................................... 197

11 SHORT MESSAGE SERVICE (SMS) COMMANDS ................198

11.1

SMS

PARAMETERS

.............................................................................................................. 198

11.2

AT+CMGC S

END AN

SMS

COMMAND

............................................................................. 201

11.3

AT+CMGD D

ELETE

SMS

MESSAGE

.................................................................................... 202

11.4

AT+CMGF S

ELECT

SMS

MESSAGE FORMAT

........................................................................ 202

11.5

AT+CMGL L

IST

SMS

MESSAGES FROM PREFERRED STORE

..................................................... 202

11.6

AT+CMGR R

EAD

SMS

MESSAGES

..................................................................................... 204


Page 6


11.7

AT+CMGS S

END

SMS

MESSAGE

....................................................................................... 205

11.8

AT+CMGW W

RITE

SMS

MESSAGES TO MEMORY

................................................................ 206

11.9

AT+CMSS S

END

SMS

MESSAGES FROM STORAGE

............................................................... 207

11.10

AT+CNMA N

EW

SMS

MESSAGE ACKNOWLEDGE TO

ME/TE,

ONLY PHASE

2+ ...................... 208

11.11

AT+CNMI N

EW

SMS

MESSAGE INDICATIONS

...................................................................... 208

11.12

AT+CPMS P

REFERRED

SMS

MESSAGE STORAGE

.................................................................. 211

11.13

AT+CSCA SMS

SERVICE CENTRE ADDRESS

......................................................................... 213

11.14

AT+CSCB S

ELECT

C

ELL

B

ROADCAST

M

ESSAGE

I

NDICATION

................................................. 213

11.15

AT+CSDH S

HOW

SMS

TEXT MODE PARAMETERS

.................................................................. 214

11.16

AT+CSMP S

ET

SMS

TEXT MODE PARAMETERS

...................................................................... 215

11.17

AT+CSMS S

ELECT

M

ESSAGE

S

ERVICE

................................................................................. 216

11.18

AT

^

SLMS L

IST

SMS M

EMORY

S

TORAGE

.............................................................................. 217

11.19

AT

^

SMGL L

IST

SMS

MESSAGES FROM PREFERRED STORE WITHOUT SETTING STATUS TO

REC

READ 218

11.20

AT

^

SMGO S

ET OR QUERY

SMS

OVERFLOW PRESENTATION MODE OR QUERY

SMS

OVERFLOW

218

11.21

AT

^

SMGR R

EAD

SMS

MESSAGE WITHOUT SETTING STATUS TO

REC READ ............................. 219

11.22

AT

^

SSCONF SMS C

OMMAND

C

ONFIGURATION

................................................................ 220

11.23

AT

^

SSDA S

ET

SMS D

ISPLAY

A

VAILABILITY

........................................................................... 220

11.24

AT

^

SSMSS S

ET

S

HORT

M

ESSAGE

S

TORAGE

S

EQUENCE

......................................................... 221

12 SIM RELATED COMMANDS.................................................223

12.1

AT+CRSM R

ESTRICTED

SIM A

CCESS

.................................................................................. 223

12.2

AT

^

SCKS Q

UERY

SIM

AND

C

HIP

C

ARD

H

OLDER

S

TATUS

...................................................... 224

12.3

AT

^

SCID D

ISPLAY

SIM

CARD IDENTIFICATION NUMBER

......................................................... 225

12.4

AT+CXXCID D

ISPLAY CARD

ID ......................................................................................... 226

13 PHONE BOOK COMMANDS...............................................227

13.1

S

ORT

O

RDER FOR

P

HONE BOOKS

......................................................................................... 227

13.2

AT+CPBR R

EAD FROM

P

HONE BOOK

................................................................................. 227

13.3

AT+CPBS S

ELECT PHONE BOOK MEMORY STORAGE

............................................................. 230

13.4

AT+CPBW W

RITE INTO

P

HONEBOOK

.................................................................................. 231

13.5

AT^SPBC S

EARCH THE FIRST ENTRY IN THE SORTED TELEPHONE BOOK

...................................... 234

13.6

AT

^

SPBD P

URGE PHONE BOOK MEMORY STORAGE

.............................................................. 235

13.7

AT

^

SPBG R

EAD CURRENT

P

HONE BOOK ENTRIES

.................................................................. 235

13.8

AT

^

SPBS S

TEP THROUGH THE SELECTED PHONE BOOK ALPHABETICALLY

................................... 239

13.9

AT

^

SDLD D

ELETE THE

"

LAST NUMBER REDIAL

"

MEMORY

.......................................................... 242

14 AUDIO COMMANDS...........................................................243

14.1

ATL S

ET MONITOR SPEAKER LOUDNESS

.................................................................................. 243

14.2

ATM S

ET MONITOR SPEAKER MODE

...................................................................................... 243

14.3

AT+CLVL L

OUDSPEAKER VOLUME LEVEL

............................................................................. 243

14.4

AT+CMUT M

UTE CONTROL

............................................................................................... 244

14.5

AT+VTD T

ONE DURATION

................................................................................................... 245


Page 7


14.6

AT+VTS DTMF

AND TONE GENERATION

.............................................................................. 245

14.7

AT

^

SNFD S

ET AUDIO PARAMETERS TO MANUFACTURER DEFAULT VALUES

................................. 246

14.8

AT

^

SNFI S

ET MICROPHONE PATH PARAMETERS

..................................................................... 246

14.9

AT

^

SNFO S

ET AUDIO OUTPUT

(=

LOUDSPEAKER PATH

)

PARAMETER

........................................ 247

14.10

AT

^

SNFPT S

ET PROGRESS TONES

......................................................................................... 248

14.11

AT

^

SNFV S

ET LOUDSPEAKER VOLUME

.................................................................................. 249

14.12

AT

^

SNFW W

RITE AUDIO SETTING IN NON

-

VOLATILE STORE

..................................................... 250

14.13

AT

^

SRTC R

ING TONE CONFIGURATION

................................................................................ 250

15 HARDWARE RELATED COMMANDS ...................................253

15.1

AT+CALA S

ET ALARM TIME

................................................................................................ 253

15.1.1

S

UMMARY OF

AT

COMMANDS AVAILABLE IN

A

LARM MODE

......................................................................255

15.2

AT+CCLK R

EAL

T

IME

C

LOCK

............................................................................................ 256

15.3

AT

^

SCTM S

ET CRITICAL OPERATING TEMPERATURE PRESENTATION MODE OR QUERY

TEMPERATURE

..................................................................................................................... 256

16 MISCELLANEOUS COMMANDS..........................................259

16.1

A/R

EPEAT PREVIOUS COMMAND LINE

.................................................................................. 259

16.2

ATS3 W

RITE COMMAND LINE TERMINATION CHARACTER

........................................................ 259

16.3

ATS4 S

ET RESPONSE FORMATTING CHARACTER

..................................................................... 259

16.4

ATS5 W

RITE COMMAND LINE EDITING CHARACTER

................................................................ 260

17 APPENDIX............................................................................261

17.1

R

ESTRICTED ACCESS TO

SIM

DATA AFTER

SIM PIN

AUTHENTICATION

....................................... 261

17.2

L

IST OF

*# C

ODES

.............................................................................................................. 261

17.3

A

VAILABLE

AT C

OMMANDS AND

D

EPENDENCY ON

SIM PIN................................................ 263

17.4

AT C

OMMAND

S

ETTINGS STORABLE WITH

AT&W .................................................................. 268

17.5

F

ACTORY

D

EFAULT

S

ETTINGS

R

ESTORABLE WITH

AT&F............................................................ 269

17.6

S

UMMARY OF

U

NSOLICITED

R

ESULT

C

ODES

(URC)................................................................ 271

17.7

A

LPHABETICAL

L

IST OF

AT C

OMMANDS

............................................................................... 271


Page 8


Version history

Version number

1.00

Author

Fadil Beqiri

Changes

Initial version


Page 9


Cautions

Information furnished herein by FALCOM are accurate and reliable. However, no responsibility is assumed for its use.

Please read carefully the safety precautions.

If you have any technical questions regarding this document or the product described in it, please contact your vendor.

General information about FALCOM and its range of products is available at the following internet address: http://www.falcom.de/ .

Trademarks

Some mentioned products are registered trademarks of their respective companies.

Copyright

This AT Command Set is copyrighted by FALCOM GmbH with all rights reserved. No part of this user’s guide may be produced in any form without the prior written permission of FALCOM GmbH.

FALCOM GmbH.

No patent liability is assumed with respect to the use of the information contained herein.


Page 10

TANGO55/56 AT COMMAND SET

0 INTRODUCTION

VERSION 1.01

0.1 Scope of the document

This document presents the AT Command Set for the Falcom Cellular Engine

TANGO55/56 Version 1.00.

Before using the Cellular Engine or upgrading to a new firmware version please read the latest product information provided in the Release Notes [1].

More information is available at the Falcom website: http://www.falcom.de/

0.2 Related documents

[1] TANGO55/56 55/56 user manual

[2] GPRS Startup User's Guide

[2] ITU-T Recommendation V.24: List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-terminating equipment (DCE)

[3] ITU-T Recommendation V.25ter: Serial asynchronous automatic dialling and control

[4] 3GPP TS 23.038 (GSM 03.38): Alphabets and language specific information

[5] 3GPP TS 27.005 (GSM 07.05): Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE-DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)

[6] 3GPP TS 27.007 (GSM 07.07): AT command set for User Equipment (UE)

[7] 3GPP TS 27.060 (GSM 07.60): Mobile Station (MS) supporting Packet Switched

Services

[8] 3GPP TS 51.011 (GSM 11.11): Specification of the Subscriber Identity Module -

Mobile Equipment (SIM - ME) interface

[9] 3GPP TS 11.14 (GSM 11.14): Specification of the SIM Application Toolkit for the

Subscriber Identity Module -Mobile Equipment (SIM - ME) interface


Page 11


0.3 Document conventions

Throughout the document, the GSM engines are referred to as ME (Mobile

Equipment), MS (Mobile Station), TA (Terminal Adapter), DCE (Data Communication

Equipment) or facsimile DCE (FAX modem, FAX board). To control your GSM engine you can simply send AT commands via its serial interface. The controlling device at the other end of the serial line is referred to as TE (Terminal Equipment), DTE (Data

Terminal Equipment) or plainly 'the application' (probably running on an embedded system).

All abbreviations and acronyms used throughout this document are based on the

GSM specifications. For definitions please refer to TR 100 350 V7.0.0 (1999-08), (GSM

01.04, version 7.0.0 release 1998).

0.3.1 Quick reference table

Each AT command description includes a table similar to the example shown below.

The table is intended as a quick reference to indicate the following functions:

PIN: Is the AT command PIN protected?

●

Yes

○ No

◑

Usage is dependent on conditions specified for the command, or not all command types are PIN protected (for example write command PIN protected, read command not).

Note: The table provided in the chapter

17.3

uses the same symbols.

SERIAL: Is the AT command supported on the first physical serial interface SERIAL?

●

○

Yes

No

PIN

○

Example:

SERIAL

●

0.3.2 Superscript notation for parameters and values

Parameter option

<param>

(&W)

<param>

(&V)

<param>

(^SNFW)

<param>

(+CSCS)

Meaning

Parameter value will be stored with AT&W

Parameter value will be displayed with AT&V

Parameter value will be stored with AT^SNFW

Parameter value has to be (is) coded according to current setting of

<chset>

(see AT+CSCS for details)

Value option

[x] x

(&F) x

(P) x

(D)

Table 0.1: Symbols used to indicate the correlations with other commands

Meaning

Default value: if the parameter is omitted, the value 'x' will be assumed

Factory default value, will be restored to 'x' with

AT&F

Powerup default value of a parameter which is not stored at power down

Delivery default value of a parameter which cannot be restored automatically


Page 12


Table 0.2: Symbols used to mark different types of default values of parameters

0.4 AT command syntax

The "AT" or "at" prefix must be set at the beginning of each command line. To terminate a command line enter <CR>.

Commands are usually followed by a response that includes

"<CR><LF><response><CR><LF> ". Throughout this document, only the responses are presented, <

CR

><

LF

> are omitted intentionally.

Types of AT commands and responses:

AT command type

Test command

Read command

Write command

Exec(ution) command

Syntax

AT+CXXX=?

AT+CXXX?

AT+CXXX=<...>

AT+CXXX

Function

The mobile equipment returns the list of parameters and value ranges set with the corresponding Write command or by internal processes.

This command returns the currently set value of the parameter or parameters.

This command sets user-definable parameter values.

The execution command reads nonvariable parameters determined by internal processes in the GSM engine.

• Optional parameters are enclosed in square brackets. If optional parameters are omitted, the current settings are used until you change them.

• Optional parameters or subparameters can be omitted unless they are followed by other parameters. If you want to omit a parameter in the middle of a string it must be replaced by a comma. See also example 1.

• A parameter value enclosed in square brackets represents the value that will be used if an optional parameter is omitted. See also example 2.

• When the parameter is a character string, e.g. <text>

or

<number> ,

the string must be enclosed in quotation marks, e.g. "Charlie Brown" or

"+49030xxxx". Symbols within quotation marks will be recognized as strings.

• All spaces will be ignored when using strings without quotation marks.

• It is possible to omit the leading zeros of strings which represent numbers.

• If an optional parameter of a V.25ter command is omitted, its value is assumed to be 0.

Example 1:

Omitting parameters in the middle of a string at+ccug? Query current setting

+CCUG:1,10,1

OK

AT

+

CCUG

=,9 Set only the middle parameter

OK

AT+CCUG? Query new setting

+CCUG: 1,9,1

OK

Example 2:

Using default parameter values for optional parameters


Page 13


AT

+

CFUN

=5,0 Activate CYCLIC SLEEP mode, don't reset ME

OK

AT+CFUN? Query ME mode

+CFUN: 5

OK

AT+CFUN= Set ME back to normal (default parameters: 1,0)

OK

+CFUN: 1

OK

0.4.2 Combining AT commands on the same command line

You may enter several AT commands on the same line. This eliminates the need to type the "AT" or "at" prefix before each command. Instead, it is only needed once at the beginning of the command line. Use a semicolon as command delimiter.

The command line buffer accepts a maximum of 391 characters. If this number is exceeded none of the commands will be executed and TA returns ERROR.

The table below lists the AT commands you cannot enter together with other commands on the same line. Otherwise, the responses may not be in the expected order.

AT command type

V.25ter commands

GSM 7.07 commands

GSM 7.05 commands (SMS)

Commands starting with AT&

AT+IPR

Comment

with FAX commands (Prefix AT+F) with commands, Prefix AT^S)

To be used standalone



Note: When concatenating AT commands please keep in mind that the sequence of processing may be different from the sequential order of command input. Therefore, if the consecutive order of the issued commands is your concern, avoid concatenating commands on the same line.

0.5 Supported character sets

The ME supports two character sets: GSM 03.38 (7 bit, also referred to as GSM

alphabet or SMS alphabet) and UCS2 (16 bit, refer to ISO/IEC 10646). See AT+CSCS

for information about selecting the character set. Character tables can be found below.

Explanation of terms

• International Reference Alphabet ( IRA)

IRA means that one byte is displayed as two characters in hexadecimal format, for example, the byte 0x36 (decimal 54) is displayed as "36" (two chars).

• Escape sequences

The escape sequence used within a text coded in the GSM default alphabet (0x1 B) must be correctly interpreted by the TE, both for character input and output. To the module, an escape sequence appears like any other byte received or sent.

• Terminal Adapter (TA)


Page 14


TA is used equivalent to Mobile Equipment (ME) which stands for the GSM module described here. It uses GSM default alphabet as its character set.

• Terminal Equipment ( TE)

TE is the terminal equipment that uses the GSM default alphabet as its character set. MS Hyperterminal (often used with the module) is an

ANSI/ASCII terminal that does not support the GSM default alphabet.

• Data Coding Scheme (dcs)

The Data Coding Scheme (dcs) is part of a short message and is saved on the SIM. When writing a short message to the SIM in textmode, the dcs stored with AT+CSMP is used.

• TE Character Set

The currently used TE character set is selected with AT+CSCS.

The behavior when encountering characters, that are not valid characters of the supported alphabets, is undefined.

Due to the constraints described below it is recommended to prefer the USC2 alphabet in any external application.

If the GSM alphabet is selected all characters sent overthe serial line are in the range from 0 ... 127. CAUTION: GSM alphabet is not ASCII alphabet!

Several problems resulting from the use of the GSM alphabet:

• "@" character with GSM alphabet value 0 is not printable by an ASCII terminal program (e.g. Microsoft© Hyperterminal®).

• "@"character with GSM alphabet value of binary 0 will terminate any C string! This is because the 0 is defined as C string end tag. Therefore, the

GSM Null character may cause problems on application level when using a 'C'-function as "strlenO". This can be avoided if it is represented by an escape sequence as shown in the table below.

• By the way, this may be the reason why even network providers often replace "@"with "@=*" in their SIM application.

• Other characters of the GSM alphabet are misinterpreted by an ASCII terminal program. For example, GSM "6" (as in "Bbrse") is assumed to be "|" in ASCII, thus resulting in "B|rse". This is because both alphabets mean different characters with values hex. 7C or 00 and so on.

• In addition, decimal 17 and 19 which are used as XON/XOFF control characters when software flow control is activated, are interpreted as normal characters in the GSM alphabet.

When you write characters differently coded in ASCII and GSM (e.g. A, O, 0), you need to enter escape sequences. Such a character is translated into the corresponding GSM character value and, when output later, the GSM character value can be presented. Any ASCII terminal then will show wrong responses. Table below shows examples for character definitions depending on alphabet.

“

ò

@

GSM 03.38 character hex. Value

Corresponding

ASCII character

Ö 5C \

22

08

00

“

BSP

NULL

ASCII Esc sequence

Hex Esc sequence

\5C 5C 35 43

\22

\08

\00

5C 32 32

5C 30 38

5C 30 30


Page 15


CAUTION: OFTEN, THE EDITORS OF TERMINAL PROGRAMS DO NOT RECOGNIZE ESCAPE

SEQUENCES. IN THIS CASE, AN ESCAPE SEQUENCE WILL BE HANDLED AS

NORMAL CHARACTERS. THE MOST COMMON WORKAROUND TO THIS

PROBLEM IS TO WRITE A SCRIPT WHICH INCLUDES A DECIMAL CODE INSTEAD

OF AN ESCAPE SEQUENCE. THIS WAY YOU CAN WRITE, FOR EXAMPLE, SHORT

MESSAGES WHICH MAY CONTAIN DIFFERENTLY CODED CHARACTERS.


Page 16


0.5.1 GSM alphabet tables and UCS2 character values

This section provides tables for the GSM 03.38 alphabet supported by the ME. Below any GSM character find the corresponding two byte character value of the UCS2 alphabet.

Main character table of GSM 03.38 alphabet

b4 b3 b2 b1

0 0 0 0

0

0

0

0

0

0

0

1

1

1

1

1

1

1

1

0 0 1

0 1 0

0 1 1

1 0 0

1 0 1

1 1 0

1 1 1

0 0 0

0 0 1

0 1 0

0 1 1

1 0 0

1 0 1

1 1 0

1 1 1

b7 b6 b5

0

1

2

3

4

5

6

7

8

9

10/A

11/B

12/C

13/D

14/E

15/F

0

0

0

0

@

0040

£

00A3

$

0024

¥

00A5

è

00E8

é

00E9

ù

00F9

ì

00EC

ò

00F2

ç

00E7

LF

[LF]

2)

Ø

00D8

ø

00D8

CR

[CR]

2)

Å

00C5

å

00

E5

Ė

00C9

0

0

1

1

∆

0394

Ω

03A9

Π

03A0

Ψ

03A8

Σ

03A3

Θ

0398

Ξ

039E f)

_

005F

Ф

03A6

Γ

0393

Λ

039B

Æ

00C6

æ

00E6

ß

00DF

∫

002F

0

1

0

2

SP

0020

0

1

1

3

0

0030

1

0

0

4

1

0

1

5

P

0050

!

0021

"

0022

#

0023

☼

00A4

%

0025

&

0026

1

0031

2

0032

3

0033

4

0034

5

0035

6

0036

7

0037

¡

00A1

A

0041

B

0042

C

0043

D

0044

E

0045

F

0046

G

0047

Q

0051

R

0052

S

0053

T

0054

U

0055

V

0056

W

0057

'

0027

(

0028

)

0029

*

002A

8

0038

9

0039

:

003A

H

0048

I

0049

J

004A

X

0058

Y

0059

Z

005A

+

002B

ֽ

002C

-

002D

.

002E

?

003F

;

003B

<

003C

=

003D

>

003E

O

004F

K

004B

L

004C

M

004D

N

004E

§

00A7

Ä

00C4

O

00D6

Ń

00D1

Ü

00DC

1

1

0

6

¿

00BF h

0068 i

0069 j

006A k

006B

׀

006C m

006D n

006E o

006F a

0061 b

0062 c

0063 d

0064 e

0065 f

0066 g

0067

1

1

1

7 p

0070 q

0071 r

0072 s

0073 t

0074 u

0075 v

0076 w

0077 x

0078 y

0079 z

007°

ä

00E4

ö

00F6

ñ

00F1

ü

00FC

à

00E0

Table 0.3: Main character table of GSM 03.38 alphabet

1)

This code is an escape to the following extension of the 7 bit default alphabet table.

2)

This code is not a printable character and therefore not defined for the UCS2 alphabet. It shall be treated as the accompanying control character.

Extension character table of GSM 03.38 alphabet

b4 b3 b2

0 0 0

0

0

0

0

0

0

0

1

1

b1

0

1

0

1

1

2

3

b7 b6 b5

0

0

0

0

0

0

0

1

1

0

1

0

2

0

1

1

3

1

0

0

4

|

007C

1

0

1

5

1

1

0

6

1

1

1

7


Page 17


0

0

0

0

1

1

1

1

1

1

1

1

1

1

1

1

0

0

0

0

1

1

1

1

0

0

1

1

0

0

1

1

0

0

1

1

0

1

4

5

^

005E

0

1

0

1

6

7

8

9

{

007B

}

007B

0

1

10/A

11/B

3)

[LF] f)

0

1

0

12/C

13/D

14/E

[

005B

~

007E

]

005D

1 15/F Ù

005C

Table 1.4: Extension character table of GSM 03.38 alphabet

€

2)

20AC

1)

This code value is reserved for the extension to another extension table. On receipt of this code, a receiving entity shall display a space until another extension table is defined.

2)

This code represents the EURO currency symbol. The code value is the one used for the character'e'. Therefore a receiving entity which is incapable of displaying the EURO currency symbol will display the character 'e' instead.

3)

This code is defined as a Page Break character and may be used for example in compressed CBS messages. Any mobile which does not understand the 7 bit default alphabet table extension mechanism will treat this character as Line

Feed.

In the event that an MS receives a code where a symbol is not represented in table

1.4 the MS shall display the character shown in the main default 7 bit alphabet table

(see table 1.3).

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

This chapter provides basic information on how to handle input and output character conversion for SMS text mode and Remote-SAT if internal (ME) and external (TE) character representation differ, i.e. if the Data Coding Scheme and the

TE character use different coding. Implementing output of SIM data to the TE

(direction ME to TE). dcs CSCS

GSM

UCS2

Case 1

7-Bit (GSM default)

Case 1 GSM (1:1)

Case 4 GSM to UCS2 (1:2)

8-Bit

Case 2 IRA (1:1)

16-Bit (UCS2)

Case 3 GSM (2:2)

Case 5 GSM to UCS2 (1:2) Case 6 IRA (2:2)

Every byte will be sent as GSM character (or ASCII with Hyperterminal).

Example: 0x41,0x21 → "AB" (because of conversion from 7-bit to 8-bit)

Case 2

Every byte will be sent as IRA. No conversion.

Example: 0x41,0x42 → "4142"


Page 18


Case 3

Every byte will be sent as IRA. No conversion to GSM to avoid data loss.

Example: 0x00,0x41 → "0041"

Problems:

• 0x41,0x42 → "4142" (invalid GSM character, but ignored with respect to

GSM 07.05)

• 0x41 → Error (there are two bytes needed)

Case 4

Every byte will be converted from GSM to UCS2.

Example: 0x41,0x42 → "00410042"

Case 5

Every byte will be converted from GSM to UCS2.

Example: 0x41,0x42 → "00410042"

Case 6

Example: 0x41,0x42 → "4142"

Problems:

• 0x41 → Error (there are two bytes needed)

0.5.2.1 Implementing input of Terminal data to SIM (direction TE to ME)

CSCS dcs

7-Bit (GSM default)

8-Bit

16-Bit (UCS2)

GSM

Case 1 GSM (1:1)

Case 2 IRA (1:1)

Case 3 IRA (2:2)

Case 1

Data will be packed to 7-bit.

Maximum text length: 160 characters

Example: "AB" → 0x41,0x21

Case 2

Data will be saved without any conversion.


Example: "4142" →0

X

41 ,0

X

42

Problems:

UCS2

Case 4 UCS2 to GSM (2:1)

Case 5 UCS2 to GSM (2:1)

Case 6 IRA (2:2)

Case 3

Two bytes are needed. No conversion.


Example: "0041" -^ 0x00,0x41

Problems:

• "41" → Error (there are two bytes needed)

Case 4


Page 19


Two bytes are needed. Two bytes will be converted to 1 byte GSM and 7-bit packed.


Example: "00410042" → 0

X

41,0

X

21

Problems:


• "4142" → Error (invalid character)

• "0000" → Error (not an UCS2 character)

• "007B" → 0x1 B,0x28 (The saved data are two bytes long, not 1 byte like in all other cases. This effects the maximum input length of a string)

Case 5

Two bytes are needed. Two bytes will be converted to 1 byte GSM.


Example: "00410042" → 0

X

41 ,0

X

42

Problems:


• "4142" → Error (invalid character)


• "007B" → 0x1 B,0x28 (The saved data are two bytes long, not 1 byte like in all other cases. This effects the maximum input length of a string).

Case 6

Two bytes are needed.


Example: "00410042" → 0x00,0x41,0x00,0x21

Problems:



• "007B" → 0x00,0x7B

0.6 Flow Control

Flow control is essential to prevent loss of data or avoid errors when, in a data or fax call, the sending device is transferring data faster than the receiving side is ready to accept. When the receiving buffer reaches its capacity, the receiving device should be capable to cause the sending device to pause until it catches up. There are basically two approaches to regulate data flow: software flow control and hardware flow control. The High Watermark of the input/output buffer should be set to approximately 60% of the total buffer size. The Low Watermark is recommended to be about 30%. The data flow should be stopped when the capacity rises close to the

High Watermark and resumed when it drops below the Low Watermark. The time required to cause stop and go results in a hysteresis between the High and Low

Watermarks.


Page 20


0.6.1 Software flow control (XON/OFF flow control)

Software flow control sends different characters to stop (XOFF, decimal 19) and resume (XON, decimal 17) data flow. The only advantage of software flow control is that three wires would be sufficient on the serial interface.

0.6.2 Hardware flow control (RTS/CTS flow control)

Hardware flow control sets or resets the RTS/CTS wires. This approach is faster and more reliable, and therefore, the better choice. When the High Watermark is reached, CTS is set inactive until the transfer from the buffer has completed. When the Low Watermark is passed, CTS goes active once again.

To achieve smooth data flow, ensure that the RTS/CTS lines are present on your application platform. The application should include options to enable RTS/CTS handshake with the GSM engine. This needs to be done with the AT command

AT\Q 3

- it is not sufficient to set RTS/CTS handshake in the used terminal program

only. The default setting of the GSM engine is AT\Q O

(no flow control) which must be

altered to AT\Q 3

(RTS/CTS hardware handshake on). The setting is stored volatile and must be restored each time after the GSM engine was switched off.

AT\Q has no read command. To verify the current setting of AT\Q ,

simply check the

settings of the active profile with AT&V .

Often, fax programs run an initialization procedure when started up. The initialization commonly includes enabling RTS/CTS hardware handshake, eliminating the need to set

AT\Q 3

once again. However, before setting up a CSD call, you are advised to check that RTS/CTS handshake is set.

RTS/CTS hardware handshake must also be set if you want to take advantage of the

CYCLIC SLEEP modes. For further details refer to AT+CFUN .

After deactivating the RTS line, the ME may still send up to 264 bytes (worst case). This can be easily handled if the buffer of the host application is sufficiently sized, and if a hysteresis is implemented in its Rx buffer. For host applications that are required to handle a large amount of data at high speed, a total buffer capacity of 512 bytes is recommended.

0.7 Unsolicited Result Code Presentation

URC stands for Unsolicited Result Code and is a report message issued by the ME without being requested by the TE, i.e. a URC is issued automatically when a certain event occurs. Hence, a URC is not issued as part of the response related to an executed AT command.

Typical events leading to URCs are incoming calls ("RING"), received SMS etc.

A summary of all URCs is given in chapter

0 .

To announce a pending URC transmission the ME will do the following:

• Activates its Ring line (logic "1") for one second, i.e. the line changes to physical "Low" level. This allows the TE to enter power saving mode until ME related events request service.

• If the AT command interface is busy a "BREAK" will be sent immediately but the URC will not be issued until the line is free. This may happen if the URC is pending

- while an AT command is being processed, i.e. during the time from sending the first character "A" of an AT command by the TE until the ME has responded with "OK" or "ERROR", or


Page 21


- during a data call.

Please note that AT command settings may be necessary to enable inband signaling, e.g. refer to

AT+CMER or

AT+CNMI

.

For most of these messages, the ME needs to be configured whether or not to send an URC. Depending on the AT command, the URC presentation mode can be

saved to the user defined profile (see AT&W ),

or needs to be activated every time you reboot the ME. Several URCs are not user definable, such as "

^

SYSSTART",

"

^

SYSSTART <text> ", "^

SHUTDOWN

"

and the fax class 2 URCs listed in chapter 0 .

If autobauding is enabled (as factory default mode or set with

AT

+

IPR

= 0), URC

S generated after restart will be output with 57600 bps until the ME has detected the current bit rate. The URCs "

^

SYSSTART", "

^

SYSSTART <text> ", however, are not presented at all. For details please refer to chapter

3.7.1.

To avoid problems we recommend to configure a fixed bit rate rather than using autobauding.

0.7.1 Communication between Customer Application and TANGO55/56

Leaving hardware flow control unconsidered the Customer Application (TE) is coupled with the TANGO55/56 (ME) via a receive and a transmit line.

Since both lines are driven by independent devices collisions may (and will) happen, i.e. while the TE issues an AT command the TANGO55/56 starts sending an URC. This probably will lead to the TE's misinterpretation of the URC being part of the AT command's response.

To avoid this conflict the following measures must be taken:

• If an AT command is finished (with "OK" or "ERROR") the TE shall always wait at least 100 milliseconds before sending the next one.

• This gives the TANGO55/56 the opportunity to transmit pending URCs and get necessary service.

• Note that some AT commands may require more delay after "OK" or

"ERROR" response, refer to the following command specifications for details.

• The TE shall communicate with the TANGO55/56 using activated echo

(

ATE

1), i.e. the TANGO55/56 echoes characters received from the TE.

• Hence, when the TE receives the echo of the first character "A" of the AT command just sent by itself it has control over both the receive and the transmit paths. This way no URC can be issued by the TANGO55/56 in between.

0.8 Common PCN Handset Specification (CPHS)

The ME provides features to implement a device following the prerequisites of the

Common PCN Handset Specification (CPHS) Phase 2.

CPHS Feature

Alternate Line Service

Voice Message Waiting Indication

Operator (Service provider) name from

SIM

Network and Service Provider Lock

Call Forwarding

Customer Service Profile (CSP)

Description/Remarks

Using two phone numbers with one SIM card.

Indicate the receipt of a short message coded as

Voice Message Waiting Indicator as defined bythe CPHS Phase 2 standard

Read specific Elementary Files (6F14h,6F18h) from SIM

Lock/Unlock an ME to specific HPLMN and service provider

Get and set diverted call status. Access specific

Elementary File (6F13h) from SIM.

Setting services and their menu entries

AT command

AT^SALS

AT^SIND

AT+CMER ,

indicators

“vmwait1” and “vmwait2”

AT+CRSM

AT+CLCK ,(

AT

+

CPIN

)

AT+CCFC ,

AT+CRSM

AT+CRSM


Page 22


Information numbers depending on customer profiles.

Hierarchically structured service numbers phone book on SIM according to CPHS 4.2 (mandatory).

AT+CRSM

0.9 Errors and Messages

The final result codes "+ CME ERROR: <err> " and "+ CMS ERROR: <err> " indicate errors related to mobile equipment or network. The effect is similar to an ERROR result code.

A final result error code terminates the execution of the command and prevents the execution of all remaining commands that may follow on the same command line. If so, neither ERROR nor OK result code are returned for these commands. A 30 seconds timeout causes ERROR to be returned when the input of a command is not complete. The format of <err> can be either numeric or verbose. This is set with the

command AT+CMEE .

See also:

-

1.11.1

-

-

1.5.1

AT+CEER


Page 23


1 CONFIGURATION COMMANDS

The AT commands described in this chapter allow the external application to determine the TANGO55/56's behaviour under various conditions.

1.1 AT&F Set all current parameters to manufacturer defaults

Syntax

Exec Command

AT&F[ <value> ]

Reference(s)

Response(s)

OK

PIN SERIAL

V.25ter

○ ●

Command Description

TA sets all current parameters to the manufacturer defined profile.

Parameter Description

<value>

(num)

[0] set all TA parameters to manufacturer defaults

Notes

• List of parameters reset to manufacturer default can be found in chapter

17.5

.

• In addition to the default profile, you can store an individual one AT&W . To

alternate between the two profiles enter either ATZ (loads user profile) or

AT&F

(restores factory profile).

• Every ongoing or incoming call will be terminated.

1.2 AT&V Display current configuration

Syntax

Exec Command

AT&V[ <value> ]

Response(s)

ACTIVE PROFILE: ... (see section 1.2.1

)

OK

Reference(s) PIN SERIAL

V.25ter

○ ●


TA returns the current parameter setting. The configuration varies depending on whether or not PIN authentication has been done .


<value>

(num)

[0] Profile

Notes


Page 24


• The parameters of AT^SMGO

can only be displayed after the SMS data from the SIM have been read success fully for the first time. Reading starts after successful SIM authentication has been performed, and may take up to 30 seconds depending on the SIM used. While the read process is in progress, an attempt to read the parameter will result in empty values.

• The parameter of AT+CSDH

will only be displayed in SMS text mode, see

AT+CMGF .

The following tables show four different kinds of responses depending on whether or not the PIN is entered .

PIN authentication done

ACTIVE PROFILE:

E1 Q0 V1 X4 &C1 &D2 &S0\Q0

S0:000 S3:013 S4:010 S5:008 S6:000 S7:060

S8:000S10:002S18:000

+CBST:7,0,1

+CRLP:61,61,78,6 +CRC: 0

+FCLASS:0

+CMGF:0

+CSDH:0

+CNMI:0,0,0,0,1 +ILRR: 0

+IPR:57600

+CMEE:2

^

SMGO:0,0

+CSMS:0,1,1,1

^

SACM:0,"000000","000000"

^

SLCC:0

^

SCKS:0,1

+CREG:0,1

+CLIP:0,2

+CAOC:0

+COPS:0,0,"operator"

+CGSMS:3

OK

No PIN authentication

ACTIVE PROFILE:

E1 Q0 V1 X4 &C1 &D2 &S0\Q0

S0:000 S3:013 S4:010 S5:008 S6:000 S7:060 S8:000 S10:002

S18:000

+CBST: 7,0,1

+CRLP:61,61,78,6

+CR:0

+FCLASS:0

+ILRR:0 +IPR:57600

+CMEE:2

^

SCKS: 0,1

OK

Table 2.1: Current configuration on SERIAL 1 (example)

1.3 AT&W Stores current configuration to user defined profile

Syntax

Exec Command

AT&W[ <value> ]

Response(s)

OK

ERROR/+CME

ERROR <err>


V.25ter

○ ●


TA stores the currently set parameters to a user defined profile in the nonvolatile memory.


Page 25



<value>

(num)

[0] Number of profile

Notes

• The user defined profile will be restored automatically after PowerUp. Use

ATZ

to restore user profile and AT&F

to restore factory settings. Until the first use of

AT&W ,

ATZ

works as

AT&F .

• A list of parameters stored to the user profile can be found in Chapter

17.4

.

1.4 ATQ Set result code presentation mode

Syntax

Exec Command

ATQ[ <n> ]

Response(s) lf <n> =0:

OK

If <n> =1:

(none)


V.25ter

○ ●


This parameter setting determines whether or not the TA transmits any result code to the TE. Information text transmitted in response is not affected by this setting.


<n>

(num)(&W)(&V)

[0]

(&F)

1

DCE transmits result code

Result codes are suppressed and not transmitted

1.5 ATV Set result code format mode

This command determines the contents of header and trailer transmitted with AT command result codes and information responses. Possible responses are described at

1.5.1

.

Syntax

Exec Command

ATV[ <value> ]

Response(s) If <value>=0 0

If <value> =1

OK


V.25ter

○ ●


<value>

(num)(&W)(&V)

[0] Information <text><CR><LF>

Short result code format: <numeric code><CR>


Page 26

TANGO55/56 AT COMMAND SET VERSION 1.01 response:

Long result code format: <CR><LF><verbose code><CR>

1.5.1 Verbose and numeric result codes

Verbose format

OK

CONNECT

RING

NO CARRIER

ERROR

NO DIALTONE

BUSY

CONNECT 2004/RLP

CONNECT 4800/RLP

CONNECT 9600/RLP

CONNECT 14400/RLP

ALERTING

DIALING

7

47

48

49

50

Numeric format

0

1

2

3

4

6

Meaning

Command executed, no errors

Link established

Ring detected

Link not established or disconnected

Invalid command or command line too long

No dial tone , dialling impossible, wrong mode

Remote station busy

Link with 2400 bps and Radio Link Protocol




Alerting at called phone

Mobile phone is dialing

1.6 ATX Set CONNECT result code format and call monitoring

Syntax

Exec Command

ATX[ <value> ]

Reference(s)

Response(s)

OK

PIN SERIAL

V.25ter

○ ●


This parameter setting determines whether or not the TA detects the presence of dial tone and busy signal and whether or not TA transmits particular result codes.


<value>

(num)(&W)(&V)

[0]

detection are both disabled.

1 result code only returned, dial tone and busy detection are both disabled.

2 result code returned, dial tone detection is enabled, busy detection is disabled.

3 result code returned, dial tone detection is disabled, busy detection is enabled.

4

(&F)

<text> result code returned, dial tone and busy detection are both enabled.

1.7 ATZ Set all current parameters to user defined profile

Syntax


Page 27


Exec Command

ATZ [ <value> ]

Reference(s)

Response(s)

OK

PIN SERIAL

V.25ter

○ ●


TA sets all current parameters to the user profile stored with AT&W .

If a connection is in progress, it will be terminated.

All defined GPRS contexts which are not activated or not online will be

undefined (see AT+CGDCONT ,

AT+CGQREQ

and AT+CGQMIN command). The

user defined profile is stored to the non-volatile memory.


<value>

( num)

[0] Reset to user profile

Notes

• First the profile will be set to factory default (see AT&F ).

If there is a valid

user profile (stored with AT&W

),

this profile will be loaded afterwards.

• Any additional commands on the same command line may be ignored. A delay of 300 ms is required before next command is sent, otherwise "OK" response may be corrupted.

1.8 AT+CFUN Set phone functionality

This command serves to control the functionality level of the ME. It can be used to reset the ME, to choose one of the SLEEP modes or to return to full functionality.

Intended for power saving, SLEEP mode reduces the functionality of the ME to a minimum and thus minimizes the current consumption. SLEEP mode falls in two categories:

• NON-CYCLIC SLEEP mode <fun>=0

• and CYCLIC SLEEP modes, selectable as <fun>= 5, 6, 7,8 or 9.

NON-CYCLIC SLEEP mode permanently blocks the serial interface. The CYCLIC SLEEP mode, however, is a dynamic process which alternatingly enables and disables the serial interface. The major benefit of all CYCLIC SLEEP modes is that the serial interface remains accessible and that, in intermittent wake-up periods, characters can be sent or received without terminating the selected mode. The best choice is using <fun>= 5, 6, 7, 8 or 9, since in these modes TANGO55/56 automatically resumes power saving, after you have sent or received a short message or made a call.

<fun>=5 or 6 do not offer this feature to the same extent and are only supported for compatibility with earlier releases. In all CYCLIC SLEEP modes, you can enter <fun>=1 to permanently wake up TANGO55/56 and take it back to full functionality. Please refer to section

1.8.1

for a summary of all SLEEP modes and the different ways of waking up the module.

For CYCLIC SLEEP mode (<fun>= 5, 6, 7, 8 or 9 ) both the ME and the application must be configured to use hardware flow control. This is necessary since the CTS signal is set/reset every time when the ME listens to a paging message from the base station.

This is the way how the module indicates to the application when the UART is active.

For detailed information on the timing of the CTS signal refer to [2]. The default

setting of hardware flow control is AT\Q O which must be altered to AT\Q 3.

For use

after restart you are advised to add it to the user profile saved with AT&W .

If both


Page 28

TANGO55/56 AT COMMAND SET VERSION 1.01 interfaces SERIAL is connected, hardware flow control must be set in either application.

Syntax

Test Command

AT+CFUN=?

Read Command

AT+CFUN?

Write Command

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

Response(s)

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

OK

Response(s)

+CFUN: <fun>

OK

Response(s)

OK

ERROR

+CME ERROR


GSM 07.07

○ ●


The test command returns the values of the supported parameters. The read command returns the current functionality value.

The write command can be used to reset the ME, to choose one of the

SLEEP modes or to return to full functionality.


<fun>

(num)

0 NON-CYCLIC SLEEP mode:

In this mode, the AT interface is not accessible. Consequently, once you have set <fun> level 0, do not send further characters.

Otherwise these characters remain in the input buffer and may delay the output of an unsolicited result code.

The first wake-up event stops power saving and takes the ME back to full functionality level <fun>=1.

[1]

(&F)

Full functionality.

5

If the ME is in one of the CYCLIC SLEEP modes you can issue

AT+CFUN =1 to stop power saving and return to full functionality.

Keep in mind that, unlike the reset command described below, this action does not restart the ME but only changes the level of functionality. See parameter <rst> for details on the reset.

CYCLIC SLEEP mode:

6

7

In this mode, the serial interface is shortly enabled during paging. If characters are recognized on the serial interface, the ME stays active for 2 seconds after the last character was sent or received.

CYCLIC SLEEP mode:

In this mode, the serial interface is shortly enabled during paging.

If characters are recognized on the serial interface, the ME stays active for 10 minutes after the last character was sent or received.

To ensure that power saving takes effect immediately, the ME stays active for only 2 seconds after <fun>=6 was entered.

CYCLIC SLEEP mode:


If characters are recognized on the serial interface, the ME stays


Page 29

TANGO55/56 AT COMMAND SET VERSION 1.01 active for 2 seconds after the last character was sent or received.

ME exits SLEEP mode only, if AT+CFUN =1

is entered.

8

9

CYCLIC SLEEP mode:


If characters are recognized on the serial interface, the ME stays active for 10 minutes after the last character was sent or received. ME exits SLEEP mode only, if

AT+CFUN =1

is entered.

To ensure that power saving takes effect immediately, the ME stays active for only 2 seconds after <fun>=8 was entered.

CYCLIC SLEEP mode:


If characters are recognized on the serial interface, the ME stays active after the last character was sent or received for at least the time, which can be configured by

AT^SCFG ="PowerSaver/Mode9/Timeout",

<cfun9-timeout>

(temporary wakeup).

In contrast to SLEEP modes 5,6,7 and 8 assertion of RTS can also be used to temporarily wake up the ME. In this case too, activity time is at least the time set with

AT^SCFG

="PowerSaver/Mode9/Timeout", <cfun9-timeout> . RTS can be

activated from SERIAL. ME exits SLEEP mode only, if AT+CFUN =1

is entered.

<rst>

(num)

The parameter can only be used if the serial interface is enabled.

Due to the command syntax, you need to enter parameter <fun>, followed by <rst>, where <fun> is only a placeholder and has no effect.

See examples below.

[0] Placeholder as stated above.

1 ME resets and restarts to full functionality. After reset and restart,

PIN 1 authentication is necessary (

AT

+

CPIN

). If autobauding is enabled, it is recommended to wait 3 to 5 seconds before entering the first AT command. For details on autobauding refer to chapter

3.7.1.

Notes

• If both serial interfaces is connected, any functionality level set with

AT+CFUN

takes effect on both of them.

• When a circuit-switched call is in progress, < fun>=7 or 8 or 9 can be activated without terminating the call. However, setting < f un> = 0, 5 or 6 during a circuit-switched call immediately disconnects this call.

• Please keep in mind that power saving works properly only when PIN authentication has been done. If you attempt to activate power saving while the SIM card is not inserted or the PIN is not correctly entered, the selected <fun> level will be set, though power saving does not take effect. For the same reason, power saving cannot be used if

TANGO55/56 operates in Alarm mode. Furthermore, in order to accept incoming calls, SMS or network related URCs in SLEEP mode the ME must be registered when it enters the SLEEP mode.

• To check whether power saving is on, you can query the status with the read command

AT+CFUN ?

only if the module is in full functionality mode or in CYCLIC SLEEP mode. The green LED remains "off" while the


Page 30

TANGO55/56 AT COMMAND SET VERSION 1.01 module is in any of the SLEEP modes. However, the module can wake up temporarily from power saving without leaving its CYCLIC SLEEP mode (without changing +CFUN " <fun>"), e.g. for a network scan after a loss of radio coverage, or after receipt of serial data during CYCLIC

SLEEP mode. During this "temporary wake up state" the LED will operate as if the ME was in full functionality mode.

• Recommendation: In NON-CYCLIC SLEEP mode, you can set an RTC alarm to wake up the ME and return to full functionality. This is a useful approach because, in this mode, the AT interface is not accessible.

Examples

EXAMPLE 1

To check the level of functionality use the read command:

AT+CFUN?

+CFUN: 1 Default mode after ME was restarted

Remember that the AT interface is not accessible in NON-CYCLIC SLEEP mode. Consequently, the read command is only useful when the ME is set to full functionality or, when <fun> is set to 5, 6, 7, 8 or 9.

AT+CFUN?

+CFUN: 5 CYCLIC SLEEP mode

EXAMPLE 2

To set the ME to NON-CYCLIC SLEEP mode enter

AT+CFUN=0

OK

When, for example, an SMS is being received and indicated by an unsolicited result code (URC), the ME wakes up to full operation.

+CMTI: "SM",5

Note that the URC used in this example will appear only, if

AT+CNMI =1

,1 was configured before. After this, you may want to verify the operating status:

AT+CFUN?

+CFUN: 1 Indicates that ME has entered full functionality mode.

EXAMPLE 3

To stop CYCLIC SLEEP mode and return to full functionality:

AT+CFUN?

+CFUN: 5

OK

AT+CFUN=1

OK

Remember that this approach is not applicable to the NON-CYCLIC SLEEP mode (since the serial interface is disabled). The NON-CYCLIC SLEEP mode ends with the first wake-up event.

EXAMPLE 4

To reset and restart the ME:

AT

+

CFUN alternatively,

AT+CFUN =

0,1 or 5,1 or 6,1 or 7,1 or 8,1 or 9,1

OK


Page 31


^

SYSSTART

The

^

SYSSTART URC confirms that the ME has been rebooted. Note that

^

SYSSTART appears only if

AT+IPR

≠ 0. If the ME is in autobaud mode, it is recommended to wait 3 to 5 seconds before entering the first AT command. Remember to enter the SIM PIN after restart.

1.8.1 Wake up the ME from SLEEP mode

A wake-up event is any event that causes the ME to draw current. Depending on the selected mode, the wake-up event either switches the SLEEP mode off and takes the ME back to full functionality

AT+CFUN =1

, or activates the ME temporarily without terminating the selected SLEEP mode.

Definitions of the state transitions described in table 2.3:

• Quit: ME exits SLEEP mode.

• Temporary: ME becomes active temporarily for the duration of the event and the mode-specific follow-up time after the last character was sent or received on the serial interface.

Event

• No effect: Event is not relevant in the selected SLEEP mode. The ME does not wake up.

Ignition line

/RTS0 or RTS1 activation

Selected mode:

<fun> =0

No effect

Quit

Selected mode: <fun> =5 or

6

No effect

No effect (RTS is only used for flow control)

Quit

Quit

Temporary

Selected mode: <fun> =7 or

8 or 9

No effect

Mode 7 and 8: No effect (RTS is only used for flow control)

Mode 9: Temporary

Temporary

Temporary

Temporary

Unsolicieted Result Code (URC) Quit

Incoming voice or data call Quit

Any AT command (incl. Outgoing

SMS,voice or data call)

Incoming SMS ( AT+CNMI is set

to 0,0 (this is the default setting)

Not possible (UART disabled)

No effect

Incoming SMS ( AT+CNMI is set

to 1,1)

GPRS data transfer

Quit

RTC alarm line

AT+CFUN =1


Quit


No effect

Quit

Temporary

Quit

Quit

No effect

Temporary

Temporary

Temporary

Quit

Table 2.3: Wake-up events in NON-CYCLIC and CYCLIC SLEEP modes

1.9 AT

^

SMSO Switch off mobile station

Syntax

Test Command

AT^SMSO=?

Exec Command

AT^SMSO

Response(s)

OK

Response(s)

^SMSO: MS OFF

OK


SIEMENS

Unsolicited Result Code

○ ●


Page 32


^SHUTDOWN

Indicates that the power-off procedure is finished and the module will be switched off within 1 second.


The exec command initiates the power-off procedure. Low level of the module's VDD pin and display of URC "^

SHUTDOWN

" verifies that the procedure has completed and the module has entered the POWER

DOWN mode. Therefore, be sure not to disconnect the operating voltage until VDD is low or until URC "^

SHUTDOWN

" is displayed. Otherwise, you run the risk of losing data. For further details on how to turn off the module see the [2].

Notes

• Do not send any command after this command.

• If serial interface is connected the URC appears on both of them.

1.10 AT+GCAP Request complete TA capabilities list

Syntax

Test Command

AT+GCAP=?

Exec Command

AT+GCAP

Response(s)

OK

Response(s)

+GCAP: <name>

OK

Reference(s) PIN Serial

V.25ter

○ ●


TA reports a list of additional capabilities.


<name>

(str) e.g.: +CGSM,+FCLASS

Note

• +CGSM: The response text shows which GSM commands of the ETSI standard are supported.

1.11 AT+CMEE Report mobile equipment error

Syntax

Test Command

AT+CMEE=?

Read Command

AT+CMEE?

Write Command

AT+CMEE= <n>

Response(s)

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

OK

Response(s)

+CMEE: <n>

OK

Response(s)

OK

ERROR

+CME ERROR: <err>


Page 33



GSM 07.07

○ ●


This command controls the presentation of the result code +CME ERROR: <err> that indicates errors relating to ME functionality.

When you power down or reset the ME with AT+CFUN =1

,1 the setting will be reset to its default. The levels 1 or 2 need to be selected every time you reboot the ME, or may be included, for permanent use, in the user profile saved with

AT&W .


<n>

(num)(&W)(&V)

0

(&F) disable result code (only 'ERROR' will be displayed)

1 enable code

2 enable result code and use verbose values

Notes

• The possible error result codes are listed in

1.11.1

, 1.11.2

and

1.11.3

.

Example

To obtain enhanced error messages it is recommended to choose <n> =2.

AT+CMEE=2

OK


Page 34


1.11.1 Summary of CME ERRORS related to GSM 07.07

133

134

256

257

258

259

260

261

262

40

41

42

43

44

45

46

47

48

100

132

25

26

27

30

31

32

18

20

21

22

23

24

4

5

6

7

10

11

12

13

14

15

16

17

Code of <err>

0

1

2

3

1.11.2 Summary of GPRS-related CME ERRORS

Text (if AT+CMEE =2)

Phone failure

No connection to phone

Phone-adapter link reserved

Operation not allowed

Operation not supported

PH-SIM PIN required

PH-FSIM PIN required

PH-FSIM PUK required

SIM not insert

SIM PIN required

SIM PUK required

SIM failure

SIM busy

SIM wrong

Incorrect password

SIM PIN2 required

SIM PUK2 required

Memory full

Invalid index

Not found

Memory failure

Text string too long

Invalid characters in text string

Dial string too long

Invalid character in dial string

No network service

Network timeout

Network not allowed emergency calls only

Network personalization PIN required

Network personalization PUK required

Network subset personalization PIN required

Network subset personalization PUK required

Service provider personalization PIN required

Service provider personalization PUK required

Corporate personalization PIN required

Corporate personalization PUK required

Master Phone Code required

Unknown

Service option not supported

Requested service option not subscribed

Service option temporarily out of order

Operation temporary not allowed

Call barred

Phone is busy

User abort

Invalid dail string

Ss not executed

SIM blocked

Code of <err>

103

106

107

111


Illegal MS

Illegal ME

GPRS services not allowed

PLMN not allowed


Page 35


112

113

148

149

150

Location area not allowed

Roaming not allowed in this location area

Unspecified failure

PDP authentication failure

Invalid mobile class

1.11.3 Summary of CMS ERRORS related to GSM 07.05

176

192

193

194

195

196

197

198

199

208

209

144

145

159

160

161

175

111

127

128

129

130

143

210

211

212

213

255

300

301

302

41

42

47

50

69

81

95

96

97

98

99

21

27

28

29

30

38

Code of <err>

1

8

10


Unassigned (unallocated) number

Operator determined barring

Call barred

Short message transfer rejected

Destination out of service

Unidentified subscriber

Facility rejected

Unknown subscriber

Network out of order

Temporary failure

Congestion

Resources unavailable, unspecified

Requested facility not subscribed

Requested facility not implemented

Invalid short message transfer reference value

Invalid message, unspecified

Invalid mandatory information

Message type non-existent or not implemented

Message not compatible with short message protocol state

Information element non-existent or not implemented

Protocol error,unspecified

Interworking, unspecified

Telmatic interworking not supported

Short message Type 0 not supported

Cannot replace short message

Unspecified TP-PID error

Data coding scheme (alphabet) not supported

Message class not supported

Unspecified TP-DCS error

Command cannot be actioned

Command unsupported

Unspecified TP-Command error

TPDU not supported

SC busy

No SC subscribtion

SC system failure

Invalid SME address

Destination SME barred

SM Rejected-Dublicate SM

TP-VPF not supported

TP-VP not supported

D0 SIM SMS storage full

No SMS storage capability in SIM

Error in MS

Memory Capacity Exceeded

SIM Application Toolkit Busy

SIM data download error

Unspecified error cause

ME failure

AMA service of ME reserved

Operation not allowed


Page 36


320

321

322

330

331

332

340

500

512

513

514

515

303

304

305

310

311

312

313

314

315

316

317

318

516

517

518

519

520

521

522

Operation not supported

Invalid PDU mode parameter

Invalid text mode parameter

SIM not inserted

SIM PIN required

PH-SIM PIN required

SIM failure

SIM busy

SIM wrong

SIM PUK required

SIM PIN2 required

SIM PUK2 required

Memory failure

Invalid memory index

Memory full

SMSC address unknown

No network service

Network timeout

NO +CNMA ACK EXPECTED

Unknown error

User abort

Unable to store

Invalid status

Invalid character in address string

Invalid length

Invalid charcter in pdu

Invalid parameter

Invalide length or character

Invalide charakter in text

Timer expired

Operation temporary not allowed

1.12 AT+CSCS Select TE character set

Syntax

Test Command

AT+CSCS=?

Read Command

AT+CSCS?

Response(s)

+CSC: (list of supported <chset> s)

OK

Response(s)

+CSCS: <chset>

OK

Response(s)

OK

Write Command

AT+CSCS=[ <chset> ]


GSM 07.07, GSM 11.11

○ ●


Write command informs TA which character set <chset> is used by the TE. TA is then able to convert character strings correctly between TE and ME character

sets. See also section 0.5.

Note that when TA-TE interface is set to 8-bit operation and used TE alphabet is 7-bit, the highest bit will be set to zero.


<chset>

(str)

"GSM"

(&F)

GSM default alphabet (GSM 03.38 subclause 6.2.1);


Page 37


Note: This setting may cause software flow control problems since the codes used to stop and resume data flow (XOFF = decimal 19, XON = decimal 17) are interpreted as normal characters.

"UCS2" 16-bit universal multiple-octet coded character set

(ISO/IEC10646 [32]);

UCS2 character strings are converted to hexadecimal numbers from 0000 to FFFF; e.g. "004100620063" equals three 16-bit characters with decimal values 65, 98 and 99,

$(AT R97)$

1.13 AT

^

SCFG Extended Configuration Settings

Command can be used to query and set various ME settings of TANGO55/56.

Parameter names are coded in GSM alphabet, parameter values in the alphabet as specified by

AT+CSCS (GSM or UCS2).

Syntax

Test Command

AT^SCFG=?

Read Command

AT^SCFG?

Write Command

Adaptive Multi Rate (AMR):

AT^SCFG = "Audio/AMR"[,< amr> ]

Write Command

GPRS

ATS0 with automatic attach

AT^SCFG="GPRS/ATSO/withAttach"[,< gaa> ]

Write Command

Ring on incoming GPRS IP data packets

AT^SCFG="GPRS/RingOnlncomingData"[,< g roid> ]

Response(s)

^SCFG: "Audio/AMR", (list of supported <amr>s) ^SCFG:

"GPRS/

ATS0 /withAttach", (list of supported

<gaa>s)

^SCFG: "GPRS/RingOnIncomingData", (list of supported <groid>s)

^SCFG: "PowerSaver/Mode9/Timeout", (list of supported <cfun9-timeout>s )

^SCFG: "Radio/Band/HandOver", (list of supported <HandOverStatus>s )

^SCFG: "URC/CallStatus/CIEV", (list of supported <succ>s )

^SCFG: "URC/CallStatus/SLCC", (list of supported <sucs>s )

^SCFG: "URC/Datamode/Ringline", (list of supported <udri>s )

^SCFG: "URC/Ringline", (list of supported <uri >s)

^SCFG: "URC/Ringline/ActiveTime", (list of supported <urat>s )

OK

Response(s)

^SCFG: "Audio/AMR",< amr>

1

[,<amr>

2

[,< amr>

3

...[ <amr>

10

]]]

^SCFG:: "GPRS/ ATS0 /withAttach",<

gaa>

^SCFG: "GPRS/RingOnIncomingData",< groid>

^SCFG: "PowerSaver/Mode9/Timeout", (list of supported <cfun9-timeout>s )

^SCFG: "Radio/Band/HandOver",< HandOverStatus>

^SCFG: "URC/CallStatus/CIEV",< succ>

^SCFG: "URC/CallStatus/SLCC",< sucs>

^SCFG: "URC/Datamode/Ringline",< udri>

^SCFG: "URC/Ringline",< uri>

^SCFG: "URC/Ringline/ActiveTime",< urat>

OK

Response(s)

^SCFG: "Audio/AMR",< amr>

1

[,<amr>

2

[,< amr>

3

...[ <amr>

10

]]]

OK

ERROR

+CME ERROR

Response(s)

^SCFG: "GPRS/

ATS0 /withAttach",<

gaa>

OK

ERROR

+CME ERROR

Response(s)

^SCFG: "GPRS/RingOnIncomingData",< groid>

OK

ERROR

+CME ERROR


Page 38


Write Command

Query/Set timeout value for power saving mode 9.

AT^SCFG="PowerSaver/Mode9/Timeout"[,< cf un9-timeout> ]

Response(s)

^SCFG: "PowerSaver/Mode9/Timeout",<

OK

ERROR cfun9-timeout>

Write Command

Control Special Call Handover Setting.

AT^SCFG="Radio/Band/HandOver"[,< HandO verStatus> ]

Write Command

+CME ERROR

Response(s)

^SCFG: "Radio/Band/HandOver",< HandOverStatus>

Configuration of URC "+CIEV:call" Call Status

Indication

AT^SCFG="URC/CallStatus/CIEV"[,< succ> ]

Response(s)

^SCFG: "URC/CallStatus/CIEV",< succ>

OK

ERROR

Write Command

Configuration of URC "^

SLCC

" Call Status

Indication

AT

^

SCFG="URC/Calistatus/SLCC"[,< sucs> ]

+CME ERROR

Response(s)

^SCFG: "URC/CallStatus/SLCC",< sucs>

OK

ERROR

+CME ERROR

Response(s) Write Command

URC indication in datamode via RING line:

AT^SCFG="URC/Datamode/Ringline"[,< udri >

]

^SCFG: "URC/Datamode/Ringline",<

OK

ERROR udri>

Write Command

URC indication via RING line:

AT^SCFG="URC/Ringline"[,< uri >]

Write Command

Duration of active RING line for URC indications:

AT^SCFG="URC/Ringline/ActiveTime"[,< urat

> ]

+CME ERROR

Response(s)

^SCFG: "URC/Ringline",< uri>

OK

ERROR

+CME ERROR

Response(s)

^SCFG: "URC/Ringline/ActiveTime",< urat>

OK

ERROR

+CME ERROR

PIN SERIAL

○ ●


The read command returns a list of all supported parameters with their current values.

The write command allows to query a configuration parameter (no value was given) or to set its value(s). The following error codes are used:

• "+CME ERROR: operation temporary not allowed"...

• "+CME ERROR:

• "+CME ERROR:

• "+CME ERROR: change of parameter value(s) temporarily not allowed invalid index"... invalid parameter name or invalid value(s). invalid characters in text string"... a character set conversion of parameter value(s) failed unknown"... other errors


<amr>

(str)(+cscs)

Adaptive Multi Rate


Page 39


This parameter can be used to control the usage of the feature

"Adaptive Multi Rate" (AMR). It is possible to enable or disable this feature for all network operators, or to enabled it for selected operators (max.

10). If the feature is enabled for all operators, any request to enable it for a specific operator will result in a"+CME ERROR: operation temporary not allowed".

Changes of this parameter become active with the next call.

Parameter is global for all interfaces, volatile and will not be reset by

AT&F .

"enabled"

"disabled"

00000...999999

AMR is used for every operator.

AMR is not used for any operator.

Enable AMR for the specified operator (in BCD or

IRA format; see AT+COPS ).

<gaa>

(str)(+cscs)

GPRS ATS0 with Attach

This parameter can be used to control the behaviour of

ATSO

.

Parameter is global for all interfaces, volatile and will not be reset by

AT&F .

"on"

(P)

When the ATS0 =<n>

( <n> > 0) command is received, the MT will attempt to perform a GPRS attach.

"off When

( <n> > 0) command is received, the MTwill not attempt to perform a GPRS attach.

<groid>

(str)(+CSCS)

Ring on incoming GPRS IP data packets

This parameter can be used to control the behaviour of the RING line for incoming IP packets in GPRS online mode.

Parameter is local for the interface, volatile and will not be reset by AT&F .

"on"

"off

(P)

If ME is in power saving mode 7 or 8 (see

AT+CFUN

hardware flow control is in use

( AT\Q 3)

and RTS line is inactive and there are incoming IP packets for a GPRS context which is online, then the RING line will be activated once, for a time which is configured by the parameter "URC/Ringline/ActiveTime" ( <urat> ).

The

RING line which will be used, can be configured by the parameter "URC/Ringline" ( <uri> ).

RING line is not activated for incoming IP packets.

)

and

<cfun9-timeout>

(str)(+CSCS)

Power saving mode 9 timeout

This parameter can be used to query or configure the wake up time for

power saving mode 9 (see AT+CFUN

with parameter <fun> =9). The granularity of the timeout value is 100 ms (i.e. a value of 10 equals to 1 second). The minimum timeout value that can be applied is 5, but accuracy is guaranteed for timeout values greater than 20 only.

Parameter is global for the ME, volatile and will not be reset by AT&F .

5...20

(P)

...36000

<HandOverStatus>

(str)(+CSCS)

Call Handover Status

This parameter offers a workaround to prevent problems during call handover into the 1900 MHz band, caused by non-conforming configurations of the 1900 MHz GSM network.


Page 40


"0"

(P)

"1"

Disable workaround.

Enable workaround. This value should be selected when handover into a 1900 MHz GSM network fails. If required for permanent use the value needs to be set each time the ME is restarted.

<uri>

(str)(+CSCS)

URC RING line

This parameter can be used to control the behaviour of the RING line to indicate URCs (both for idle interfaces and, if configured by the parameter "URC/Datamode/Ringline", if link is reserved) and, if configured, the indicator for incoming IP packets (see parameter

"GPRS/RingOnIncomingData" ( <groid> ). Parameter is local for the

interface, volatile and will not be reset by AT&F .

"off

"local"

(P)

URC is not indicated by RING.

URC will be indicated by an activated RING line of the interface on which the URC appears.

URC is indicated by an activated RING0 line. "SERIAL"

<urat>

(str)(+CSCS)

URC RING line Active Time

This parameter can be used to control how long the RING line is activated to indicate URCs (both for idle interfaces and, if configured by the parameter "URC/Datamode/Ringline" ( <udri> ), if link is reserved) and, if configured by the parameter "GPRS/RingOnlncomingData", to indicate incoming GPRS IP data packets ( <groid> ). Parameter is global for all

interfaces, volatile and will not be reset by AT&F .

"0" RING line will be activated for a time between 4.6 and

9.2 ms.

"1"

"2"

(P)

RING line will be activated for about 100 ms.

RING line will be activated for about 1 s.

<udri>

(str)(+cscs)

URC Datamode RING line

This parameter specifies whether RING or BREAK is used for the signaling of URCs when the TA-TE link is reserved (e.g. during circuit-switched data calls, fax connections, in GPRS data mode or during the execution of an

AT command). Parameter is global for all interfaces, volatile and will not

be reset by AT&F .

"off

(P)

"on"

URC will be indicated by BREAK

URC is indicated by an active RING line for a time which is configured by the parameter

"URC/Ringline/ActiveTime" ( <urat> ). The RING line which will be used, can be configured by the parameter

"URC/Ringline" ( <uri> ).

<succ>

(str)(+cscs)

CIEV Call Status Indication

This parameter can be used to control the behaviour of URC

"+CIEV": call. See also AT+CIND ,

AT+CMER and

6.1.

Parameter is global for all interfaces and will not be reset by AT&F .

"restricted"

(P)

URC ""+

CIEV

": call" will be issued only when a call status transition ends in state "active" or "unknown" (see

6.1)

for a call in the list of active calls


Page 41


"verbose" URC ""+

CIEV

": call" will be issued when any state transition (including transitions beginning or ending in state "unknown") occurs in the list of active calls, or when a traffic channel is established

<sucs>

(str)(+cscs)

SLCC Call Status Indication

This parameter can be used to control the behaviour of URC "^

SLCC

". See

also AT^SLCC

and

6.1.

Parameter is global for all interfaces and will not be reset by AT&F .

"restricted" URC " will be issued only when a call status transition ends in state

"active" or "unknown" (see

6.1)

for a call in the list of active calls

"verbose"

(P)

URC "^

SLCC

" will be issued when any state transition

(including transitions beginning or ending in state

"unknown") occurs in the list of active calls, or when a traffic channel is established.

Note

• Parameters "GPRS/ ATS0 /withAttach" (

<gaa> ) and

"GPRS/RingOnIncomingData" ( <groid> ) are available only for modules supporting GPRS.

Examples

EXAMPLE 1

Usage of "Audio/AMR":

AT+CSCS="UCS2" Switch to UCS2 character

set.

OK

AT^SCFG?

…

Query all parameters.

^

SCFG:"Audio/AMR","0065006E00610062006C00650064 "

…

OK

AT+CSCS="GSM"

OK

AT^SCFG?

…

^SCFG:"Audio/AMR","enabled" operator.

…

AMR will be used for any

OK

AT

^

SCFG="Audio/AMR","disabled"

^

SCFG:"Audio/AMR","disabled" AMR is disabled for any operator.

OK

AT

^

SCFG="Audio/AMR","23405"

^

SCFG:"Audio/AMR","23405" AMR is disabled for any operator, but enabled for

"23405".

OK


Page 42


AT

^

SCFG="Audio/AMR","23203"

^

SCFG:"Audio/AMR","23405","23203" AMR is disabled for any operator, but enabled for

operators 23405" and

"23203".

OK

AT

^

"Audio/AMR"

^

SCFG:"Audio/AMR","23405", "23203 "

OK

EXAMPLE 2

Usage of "URC/Ringline" and "URC/Datamode/Ringline":

AT

+

CSCS

="GSM" Switch to GSM character

set.

OK

AT

^

SCFG

?

…

Query all parameters.

"SCFG:"URC/Datamode/Ringline","off" URCs while TA-TE link is reserved will be indicated by BREAK.

"SCFG:"URC/Ringline","local" URCs on this interface will be indicated by RING line associated to the interface (e.g. RING0 for

SERIAL).

…

OK

AT

^

SCFG="URC/Datamode/Ringline", "on"

^

SCFG:"URC/Datamode/Ringline","on" URCs while TA-TE link is

reserved will be indicated by an activated

"local" RING line.

OK

AT

^

SCFG="URC/Ringline","SERIAL"

^

SCFG:"URC/Ringline","SERIAL" URCs on this (!)

interface will be indicated by an activated

RING0 regardless whether or not the TA-TE link is

reserved.

OK

AT

^

SCFG="URC/Datamode/Ringline","off"

^

SCFG:"URC/Datamode/Ringline","off" URCs on this (!)

interface will be indicated by an activated

RING0 if TA-TE link is not (!) reserved and by

BREAK if TA-TE link is

reserved.

OK

AT

^

SCFG="URC/Ringline" Disable any RING line indication for URCs on interface.


Page 43


^

SCFG:"URC/Ringline","off"

OK

1.14 AT

^

SM20 Set M20 compatibility mode

Syntax

Test Command

AT^SM20=?

Read Command

AT^SM20?

Response(s)

OK

Response(s)

^SM20: : <CallMode>,<CmgwMode>

OK

Response(s)

OK

Write Command

AT^SM20 = <CallMode>[,<CmgwMode>]


SIEMENS

○ ●


The

AT^SM20

command selects different modes of responses returned upon

execution of the commands ATD

and SMS commands like e.g. AT+CMGW .


<CallMode>

(num)

Call setup response mode

Applies only to voice calls.

0

1

(&F)

Set compatibility to Siemens mobile phones.

ME will return "OK" immediately after attempting a call with the

ATD

command. In case of failure, additional call release indications, such as "NO DIAL TONE, "NO

CARRIER", "BUSY" will follow.

Default call setup mode, compatible to M20.

ME will return "OK" in case of a successful connection, otherwise one of the call release indications "NO DIAL

TONE, "NO CARRIER", "BUSY" are indicated.

<CmgwMode>

(num)

Response mode for sending and writing short messages

Applies to the SMS commands like e.g. AT+CMGS

and

AT+CMGW

command.

0 Set compatibility to Siemens mobile phones.

ME will return +CMS ERROR: <err> when writing or sending of short messages fails.

1

(&F)

Default mode for sending and writing short messages.

ME will return "OK", no matter whether or not sms command was successfully executed.


Page 44


2 STATUS CONTROL COMMANDS

The AT commands described in this chapter allow the external application to obtain various status information from the TANGO55/56 .

2.1 AT+CMER Mobile Equipment Event Reporting

This command controls details of the "+

CIEV

"

URC presentation related to AT^SIND

and

AT+CIND .

If registered via these commands the URCs are sent whenever a value

of the related indicator changes. In addition, AT+CMER

controls "^

SLCC

" URC

S related

to AT^SLCC .

For details refer to

6.1 , AT^SLCC

and AT^SCFG ,

parameter <sucs>. After

AT+CMER

has been switched on, URCs for all registered indicators will be issued.

Syntax

Test Command

AT+CMER=?

Read Command

AT+CMER?

Response(s)

+CMER: (list of supported <mode>s ), ( list of supported <keyp>s ), (list of supported <disp>s ), ( list of supported <ind>s ) , ( list of supported

<bfr>s )

OK

Response(s)

+ CMER : <mode>,<keyp>,<disp>,<ind>,<bfr> OK

Write Command

AT+CMER=[< mode>[,< keyp>[,< disp>[,<ind>[,<bfr>[,

<indDescr>[, <indValue>]]]]]] ]

Response(s)

OK

ERROR

+CME ERROR


GSM 07.07

●


+CIEV: <indDescr>, <indValue>

A value of an indicator has changed.

●


The read command returns the URC presentation mode <mode> and among others, the indicator event reporting status

<ind>.

The write command enables and disables the presentation of "+

CIEV

:

<indDescr>,<indValue>" URCs. <indDescr> refers to the name of a "+

CIEV

" indicator and <indValue> is the new value of this indicator. All registered indicator events will be issued to the TE.


<mode>

(num)

0

(&F)

Discard "+

CIEV

" and "^

SLCC

" URC

S

.

1

2

Discard "+

CIEV

" and "^

SLCC

" URC

S when TA-TE link is reserved, e.g. in online data mode. Otherwise they are forwarded directly to the TE.

Buffer "+

CIEV

" and "^

SLCC

" URC

S in the TA while TA-TE link is reserved, e.g. in online data mode, and flush them to the TE afterwards. Otherwise they are forwarded directly to the TE.

3 Forward "+

CIEV

" and "^

SLCC

" URC

S directly to the TE. If

TANGO55/56 is in online data mode, URCs are signaled via sending BREAK (100 ms) and stored in a buffer. Once it is


Page 45

TANGO55/56 AT COMMAND SET VERSION 1.01 back in command mode e.g. after

+++

was entered, all

URCs stored in the buffer will be output.

<keyp>

(num)

0

(&F)

<disp>

(num)

0

(&F)

<ind>

(num)

Keypad event reporting is not supported by TANGO55/56.

Display event reporting is not supported by TANGO55/56.

0

(&F)

2

Disable indicator event reporting.

Enable indicator event reporting.

<bfr>

(num)

0

(&F)

TA buffer of URCs defined within this command is cleared when <

MODE

> 1..3 is entered.

<indDescr>

(str)

Name of indicator; for a list of all supported indicators please refer to

AT+CIND and

AT^SIND .

<indValue>

(num)

Value of indicator; for a list of all values for the supported indicators

please refer to AT+CIND

and AT^SIND .

2.2 AT+CIND Indicator control

This command controls information about status changes via URC presentation of the TANGO55/56 or connected items, e.g., signal quality, service availability, sound generation, indication of unread short messages, full SMS storage, call in progress or roaming activities. Use of this command is outdated since additional indications and functionality are available with

AT^SIND .

AT+CIND supports two ways to get the values related to indicators:

• Query the current status of each indicator by using the read command

AT+CIND ?.

It returns the status no matter whether the indicator has been

registered with the write command AT+CIND =[<state>[,<state

> [,...]]].

• Evaluate one of the "+

CIEV

" URCs which the ME automatically sends to the application, whenever the value of the associated indicator changes.

The presentation of these URCs depends on two settings:

-

-

The indicators must be registered with the write command

AT+CIND=[<state>[,<state>[,...]]].

By default, all of them are registered when the ME is switched on. Any URC can be excluded if deregistered with <state> =0.

URC presentation must be enabled with

AT+CMER.

Syntax

Test Command

AT+CIND=?

Read Command

AT+CIND?

Response(s)

+ CIND: (<indDescr>, list of supported <indValue>s)[, (<indDescr>, list of supported <indValue>s)[,…]]

OK

Response(s)

+ CIND: <indValue>[,<indValue>[, ...

] ]

OK

ERROR

+CME ERROR: <err>


Page 46


Write Command AT+CIND=<state>[,< state>[, ...

] ] Response(s)

OK

ERROR

+CME ERROR: <err>


GSM 07.07

○ ●


The read command returns the status of the ME indicators.

The write command is used to switch the event report for each indicator type.

The Indicator Event Reports are displayed to the TE via "+

CIEV

" which can be

enabled using AT+CMER .


<indValue>

(num)

Integer type value,which shall be in range of corresponding <indDescr>

<indDescr>

(str)

String values and their <indValue> ranges. More indications are available via

AT^SIND .

Therefore use of

AT^SIND

for control of all indications is recommended. The following indications are accessible via

AT+CIND :

"signal" Signal quality (0..7) or (99) if not measurable. The indicated value is the bit error rate of the signal received. If there are bit errors this is not a constant but a estimated value which will

change in time. See also AT+CSQ .

"service" Service availability (0-1)

0: Not registered to any network

1: Registered to home network or, if "roam"=1 then registered to another network

"sounder" Sounder activity (0-1). The indicator provides information about tones generated in the ME. Value 1 means for example:

Incoming call - ME is ringing. Note that the URC "+

CIEV

":

"sounder" indicator will be output only if ringing tones are

activated with AT^SRTC .

Waiting call - ME generates waiting call tone (if call waiting is enabled).

Outgoing call - ME generates Call Progress tone. Outgoing call - ME generates BUSY tone.

The value changes to 0 if tone stops

"message" Unread short message at memory location <mem1> (0-1);

refer to AT+CPMS

"call" Call in progress (0-1). Indicator value is "1" if at least one call is in state "active" or "held". Depending on the value of

AT^SCFG setting (refer parameter

<succ> ), indicator "call" will be issued

-

- when a state transition ends in state "active" or in state

"unknown", if AT^SCFG setting

<suco="restricted">, when any state transition (including transitions beginning or ending in state "unknown") occurs in the list of active


Page 47

TANGO55/56 AT COMMAND SET VERSION 1.01 calls or when a traffic channel is established, if

AT^SCFG

setting <suco="verbose">.

Also refer

6.1.

"roam" Roaming indicator (0-1)

0: Registered to home network or not registered

1: Registered to other network

"smsfull" A short message memory storage in the MT has become full

(1) or memory locations are available (0), i.e. range is (0-1)

"rssi" Received signal (field) strength (0..5) or (99) if not measurable.

0: signal strength <= -112 dbm 1-4: signal strength in 15 dbm steps

5: signal strength >= -51 dbm

Received signal (field) strength can also be obtained with

AT+CSQ .

However, the signal strength is scaled to value range 0..31 by this command.

<state>

(num)

Indicator is deregistered. The indicator will not be presented as "+

CIEV

"

URC, but can be queried with AT+CIND ?.

[1]

(P)

Indicator is registered, indicator event report allowed.

Notes

• Due to its restrictive range of values, there are events when it is not entirely clear from the context, which event has led to the output of indicator

"call". Rather than as an information in itself, indicator "call" should therefore be used as a trigger to look up the new call status in the list of current calls

with AT commands AT^SLCC ,

AT+CLCC

or AT^SCNI .

• If

AT^SCFG

setting <suco="verbose"> , indicator "call" will be issued also when a traffic channel is established, or when a call enters states

"terminating" or "dropped" (see chapter

6.1).

In these cases, the relevant information about the cause of the display is available only from AT

command AT^SLCC .

• The indicator "sounder" signals every event a tone is generated in the ME.

For instance, if a waiting call produces a tone, this will be indicated.

• If the ME is switched on all indicators are in registered state.

• Use

AT+CMER

command to allow Indicator Event Report of all registered indicators.

Example

^SYSSTART

AT+CPIN=9999

OK

AT+CIND?

+CIND: 5,99,1,0,0,0,0,0 No battery is connected to the ME. The bit error rate of the signal quality is not available (since there is no call in progress). The ME is registered to its home network.

OK

AT+CMER=2,0,0,2 Now activate the Indicator Event Report with

AT+CMER .

OK


Page 48


+CIEV: battchg,5

+CIEV: signal,99

+CIEV: service,1

+CIEV: sounder,0

+CIEV: message,0

+CIEV: call,0

+CIEV: roam,0

+CIEV: smsfull,0

+CIEV: with full signal field strength.

ATD0123456;

OK

Make a call.

Receive a set of "+

CIEV

" URC

S reports. +CIEV: sounder,1

+CIEV: call,1

+CIEV: sounder,0

+CIEV: call,0 The receiver hangs up.

NO CARRIER

AT+CIND =,,,0,,0

OK

Deregister the indicators "call" and "sounder". the call.

OK

This time, no URCs are displayed.

NO CARRIER

2.3 AT

^

SIND Extended Indicator Control

AT^SIND

supplies extended event indicator control and

-

offers greater flexibility than standard AT+CIND ,

- offers several extra indicators,

-

- can show the current status of all indicators supported by

AT+CIND

and

AT^SIND ,

gives the possibility to register or deregister the indicators of both commands,

- displays all indicator event reports via "+

CIEV

" URC

S

.

Presentation mode of the generated URCs is controlled via AT+CMER .

Syntax

Test Command

AT^SIND=?

Read Command

AT^SIND?

Write Command

AT^SIND=<indDescr>,<Mode>

Response(s)

^SIND: (<indDescr>, list of supported <indValue>s)[, (<indDescr>, list of supported <indValue>s)[, ...]], (list of supported <Mode>s)

OK

Response(s)

^SIND: <indDescr>,<Mode>,<indValue>

OK

ERROR

+CME ERROR: <err>

Response(s)

OK

ERROR

+CME ERROR: <err>


Page 49



SIEMENS

○ ●


The read command provides a list of all indicators supported by AT+CIND

and

AT^SIND .

Each indicator is represented with its registration mode and current value.

The write command can be used to select a single indicator in order to modify its registration and to view the current value.


<indValue>

(num)

Integer type value in the range stated below for the corresponding

<indDescr> .

<indDescr>

(str)

String values and their <indValue> ranges.

All indicators supported by AT+CIND

are accessible with this command, too. A detailed description of these indicators can be found there. The

following indicators are accessible via AT^SIND only:

"audio" Activity of the internal audio unit (0-1). Value 1 means for example: Outgoing voice call: Indicator appears when dialing starts. Incoming voice call: Indicator appears prior to the RING result code.

"vmwaiti" Voice message waiting indication for line 1, (0-1)

"vmwait2" Voice message waiting indication for line 2, (0-1)

"ciphcall" Ciphering Status Change Indication

As stated in GSM specifications 02.07 and 02.09 the ciphering indicator feature allows the ME to detect that ciphering is not switched on and to indicate this to the user.

The ciphering indicator feature may be disabled by the home network operator setting data in the

"administrative data" field (EF

AD

) in the SIM, as defined in GSM 11.11.

If this feature is not disabled by the SIM, then whenever a connection is in place, which is, or becomes unenciphered, an indication shall be given to the user. This enables the user's decision how to proceed. Read command returns valid ciphering status only if a call is in progress or active.

If EF

AD

setting disables the ciphering indicator feature read command always indicates a ciphered link and no URC presentation will take place.

Note: The following restrictions apply if the same serial channel is used for

AT^SIND

"ciphcall" indication and for the action triggering this URC. In general, the recommended solution is to use a dedicated channel for all status signalling via URCs.

-

If an unciphered mobile originated SMS is performed,

AT^SIND

"ciphcall" URCs on the same


Page 50


-

0

1 serial channel will be issued after the related "OK" and indicate the ciphering state at this time.

Because the SMS is already sent at this time, you will get 2 URCs on this channel, but both are indicating that ciphering is enabled.

If an unciphered mobile originated data call is performed,

AT^SIND

"ciph call" URCs on the same serial channel will be issued after the interface is not longer blocked by the call (call is released or temporarily stopped) and indicate the ciphering state at this time.

Current call or SMS is not ciphered.

Current call or SMS is ciphered.

<Mode>

(num)

0

1

2

Indicator is deregistered, i.e. no such indicator event report (URC) will be issued.

Indicator is registered.

-

Indicator event reports are controlled via

AT+CMER .

-

-

Indicators defined by AT^SIND

remain deregistered until explicitly enabled.

On the other hand indicators supported by

AT+CIND

are registered while the TANGO55/56 is powered up.

Query the registration status and the current value of a single indicator type.

Note

• Notes regarding indicator voice message waiting:

-

-

-

-

"vmwaitT and "vmwait2" indicate the receipt of a short message coded as Voice Message Waiting Indicator, as defined by the CPHS

Phase 2 standard. The service must be provisioned by the operator.

The presentation mode of the indicators varies with the operator: If more than one message is received, some operators only indicate the first one, others deliver the indicator each time a new message is put into the mail-box.

The "vmwait" indicators do not apply if a network provider signals, via standard SMS, a message in the voice mailbox. In this case, the

indicator "message" will be displayed (see AT+CIND ).

The numbers 1 or 2 in "vmwait1/2" are related to the two lines of the

Alternate Line Service (ALS), also defined in CPHS Phase 2 standard. For

further details refer to the AT^SALS command.

2.4 AT+CEER Extended error report

Syntax


Page 51


Test Command

AT+CEER=?

Exec Command

AT+CEER

Response(s)

OK

Response(s)

+ CEER: <locationID>,<reason>,<ssRelease>

OK


GSM 07.07

● ●


TA returns an extended error report of the reason for the last

- call release

-

-

-

-

- failure to set up a call (both mobile originated or terminated) failure to modify a call by using Supplementary Services failed attempt to activate, register, query, deactivate or deregister a

Supplementary Service unsuccessful GPRS attach or unsuccessful PDP context activation

GPRS detach or PDP context deactivation.

The release cause report is presented in numeric format. A description associated with each number can be found in the tables given in the following subclauses. The first parameter <locationID> serves to locate the other two parameters. Depending on the failure or release cause either <reason> or

<ssRelease> are applicable.


<locationID>

(num)

Location ID as number code. Location IDs are listed in subclause 2.4.1.

Each ID is related with another table that contains a list of <reason>s or

<ssRelease>s.

<reason>

(num)

Reason for last call release as number code. The number codes are listed in several tables, sorted by different categories in the following subclauses. The tables can be found proceeding from the Location ID given in sub-clause

2.4.1.

<ssRelease>

(num)

Release cause for last Supplementary Service call (listed in subclause

2.4.9)

or last call related use of a Supplementary Service (listed in

subclause 2.4.10).

Notes

• AT+CEER

is not available for data calls, please use

ATSIS

=1 .

• Default output in the case of a no-error-situation is +CEER: 0,0,0.

• If <reason> ^ 0, then <ssRelease> = 0. Vice versa, if <reason> = 0, then

<ssRelease> may be ^ 0.

Examples

EXAMPLE 1

ATD

"01751223344" ;

NO CARRIER

A mobile originated call is rejected by the remote party.

Call set-up is terminated with NO CARRIER.


Page 52


AT

+

CEER

+CEER: 8,21,0

OK

To check the cause, the caller enters

AT+CEER.

The Location ID 8 stated in subclause

2.4.1

points to subclause

2.4.6,

where 21 = "Call rejected". 0 = No error (parameter

<ssRelease> is not applicable).

EXAMPLE 2

The user attempts to set up a multiparty call, though there are only two parties involved in the present conversation:

ATD"01751223344";

OK

AT+CHLD=2

OK

AT+CHLD=3

+CME ERROR:

AT+CEER operation temporary not allowed

+CEER: 22, 0,2 The Location ID 22 stated in subclause

2.4.1

points to subclause

2.4.10,

where 2 = "Initial conditions not fulfilled (one active, one held call)".

OK

No applicable). is not

EXAMPLE 3

The user attempts to activate call barring. Activation is denied by the network since the password is blocked after previous failures to enter the password.

AT + clck=oi,1,"0 000",3;

+CME ERROR:

AT+CEER

+CEER: 3 5, 0,43 incorrect password

The Location ID 35 stated in subclause

2.4.1

points to subclause

2.4.10,

where 43 =

"NumberOfPWAttemptsViolation" (for example if wrong password has been entered 3 times or more). 0 = No error (parameter <reason> is not applicable).

OK

2.4.1 Cause Location ID for the extended error report

ID

0

1

2

3

4

5

6

7

8

9

Description

No error (default)

SIEMENS L2 cause

GSM cause for L3 Radio Resource Sublayer (GSM 04.08 annex F)

SIEMENS cause for L3 Radio Resource Sublayer

GSM cause for L3 Mobility Management (GSM 04.08 annex G)

SIEMENS cause for L3 Mobility Management

GSM cause for L3 Mobility Management via MMR-SAP (GSM 04.08 annex G)

SIEMENS cause for L3 Mobility Management via MMR-SAP

GSM cause for L3 Call Control (GSM 04.08 10.5.4.11 and annex H)

SIEMENS cause for L3 Call Control


Page 53


96

97

98

100

101

111

5

8

9

10

65

95

Number

0

1

2

3

4

128

129

130

131

241

242

243

34

35

48

49

50

51

127

11

12

13

14

15

16

17

18

21

22

32

33

SIEMENS cause for L3 Advice of Charge Entity

GSM cause for L3 SMS CP Entity

SIEMENS cause for L3 SMS CP Entity

GSM cause for L3 SMS RL Entity

SIEMENS cause for L3 SMS RL Entity

GSM cause for L3 SMS TL Entity

SIEMENS cause for L3 SMS TL Entity

SIEMENS cause for DSM Entity

GSM cause for L3 Call-related Supplementary Services

SIEMENS cause for L3 Call-related Supplementary Services

SIEMENS cause for Supplementary Services Entity

SIEMENS cause for Supplementary Services Manager

Network cause for Supplementary Services (GSM 04.08 10.5.4.11 and annex H)

Supplementary Services network error (GSM 04.80 3.6.6)

GSM cause for GPRS Mobility Management (GSM 04.08 annex G.6)

SIEMENS cause for GPRS Mobility Management

GSM cause for Session Management (GSM 04.08 annex I)

SIEMENS cause for Session Management

SIEMENS cause for protocol module or other local cause

Supplementary Services general problem (GSM 04.80 3.6.7)

Supplementary Services invoke problem (GSM 04.80 3.6.7)

Supplementary Services result problem (GSM 04.80 3.6.7)

Supplementary Services error problem (GSM 04.80 3.6.7)

SIEMENS cause for GPRS API

SIEMENS cause for Link Management

SIEMENS cause for Embedded Netcore (Internet Protocol Stack)

2.4.2 GSM release cause for L3 Radio Resource (RR)

Description

Normalevent

Abnormal release, unspecified

Abnormal release, channel unacceptable

Abnormal release, timer expired

Abnormal release, no activity on the radio path

Pre-emptive release

Handover impossible, timing advance out of range

Channel mode unacceptable

Frequency not implemented

Call already cleared

Semantically incorrect message



Message type not compatible with protocol state

Conditional information element error

No cell allocation available

Protocol error unspecified

2.4.3 SIEMENS release cause for L3 Radio Resource (RR)

Number

1

2

3

4

5

6

7

8

9

Description

Racchs not answered

Racchs rejected

Access class of the SIM is barred by the network provider

SABM failure

Radio link counter expiry or PerformAbnormalRelease

Confirm ABORT of the MM

Respond to DEACT REQ

Loss of coverage

Reestablishment not possible


Page 54


2.4.4 GSM release cause for Mobility Management (MM)

7

8

9

10

14

16

Number Description

Causes related to MS identification

2

3

4

IMSI unknown in HLR

Illegal MS

IMSI unknown in VLR

5

6

IMEI not accepted

Illegal ME

Cause related to subscription options

11 PLMN not allowed

12

13

Location Area not allowed

Roaming not allowed in this location area

Causes related to PLMN specific network failures and congestion

17

22

Network failure

Congestion

Causes related to nature of request

32 Service option not supported

33 Requested service option not subscribed

34

38


Call cannot be identified

Causes related to invalid messages

95 Semantically incorrect message

96

97



98

99

100

101

Message not compatible with protocol state



Messages not compatible with protocol state

111 Protocol error, unspecified

Causes related GPRS

GPRS services not allowed

GPRS services not allowed in combination with non-GPRS services

MS identity cannot be identified by the network

Implicitly detached

GPRS services not allowed in current PLMN

MSC temporarily unreachable

2.4.5 SIEMENS release cause for L3 Mobility Management (MM)


1 No SIM available

8

9

11

17

18

19

20

21

22

23

24

25

No MM connection

Authentification failure

MM performs detach

Registration failed and will be re-attempted in a short term

CM connection establishment failed

Registration failed and will be re-attempted in a long term

RR connection is released

MS tries to register

SPLMN is not available

An MTC is in progress

A PLMN scan is in progress

The MM is detached, the MS is in MS class C GPRS only

VERSION 1.01

2.4.6 GSM release cause for L3 Call Control (CC)



Page 55


3

6

0 No error

Normal class

1 Unassigned (unallocated) number

No route to destination

Channel unacceptable

8

16

17

18

Operator determined barring

Normal call clearing

User busy

No user responding

19 User alerting, no answer

21

22

25

26

27

28

29

30

31

Call rejected

Number changed

Pre-emption

Non-selected user clearing

Destination out of order

Invalid number format (incomplete number)

Facility rejected

Response to STATUS ENQUIRY

Normal, unspecified

Resource unavailable class

34 No circuit/channel available

38

41

42

Network out of order

Temporary failure

Switching equipment congestion

43

44

Access information discarded

Requested circuit/channel not available

47 Resource unavailable, unspecified

Service or option not available class

49

50

Quality of service unavailable

Requested facility not subscribed

55

57

58

63

Incoming calls barred within the CUG

Bearer capability not authorized

Bearer capability not presently available

Service or option not available, unspecified

Service or option not implemented

65 Bearer service not implemented

96

97

98

99

100

101

102

111

68

69

70

79

ACM equal or greater than ACMmax

Requested facility not implemented

Only restricted digital information bearer capability is available

Service or option not implemented, unspecified

Invalid message (e.g. parameter out of range) class

81 Invalid transaction identifier value

87

88

91

95

User not member of CUG

Incompatible destination

Invalid transit network selection


Protocol error (e.g. unknown message) class


Message type non-existant or not implemented

Message type not comaptible with protocol state



Message not compatible with protocol

Recovery on timer expiry

Protocol error, unspecified


Page 56


Interworking class

127 Interworking, unspecified

2.4.7 SIEMENS release cause for L3 Call Control (CC)

Number

1

2

3

4

5

6

Description

Call dropped

Service not available

Hold procedure not available

Temporary no service, previous procedure not yet finished

No speech service available

Call reestablishment procedure active

7

8

Mobile received a release (complete) message during a modify procedure (modify reject)

Call clearing, because loss of radio connection, if no reestablishment is allowed (call not active)

10 Number not included in FDN list

Notifications

300 Called party barred incoming call

2.4.8 SIEMENS release cause for L3 Advice of Charge (AOC)

3

4

5

Number

1

2

Description

SIM data not available

SIM does not support AOC

SIM data access error

ACM limit almost reached ACM range overflow

ACM range overflow

2.4.9 GSM Release cause for Supplementary Service Call

13

15

16

17

18

19

20

21

27

29

30

10

11

12

Number

0

1

9

34

Description

No error (default)

UnknownSubscriber

IllegalSubscriber

BearerServiceNotProvisioned

TeleserviceNotProvisioned

NlegalEquipment

CallBarred

CUGReject

IllegalSSOperation

SSErrorStatus

SSNotAvailable

SSSubscriptionViolation

SSIncompatibility

FacilityNotSupported

AbsentSubscriber

ShortTermDenial

LongTermDenial

SystemFailure


Page 57


38

43

71

72

35

36

37

DataMissing

UnexpectedData Value

PWRegistrationFailure

NegativePWCheck

NumberOfPWAttemptsViolation

UnknownAlphabet

USSDBusy

126

127

MaxNumsOfMPTYCallsExceeded

ResourcesNotAvailable

General Problem Codes

300 Unrecognized Component

301

302

Mistyped Component

Badly Structured Component

Invoke Problem Codes

303 Duplicate Invoke ID

304 Unrecognized Operation

305 Mistyped Parameter

306

307

308

309

Resource Limitation

Initiating Release

Unrecognized Linked ID

Linked Response Unexpected

310 Unexpected Linked Operation

Return Result Problem Codes

311

312

313

Unrecognize Invoke ID

Return Result Unexpected

Mistyped Parameter

Return Error Problem Codes

314 Unrecognized Invoke ID

315

316

Return Error Unexpected

Unrecognized Error

317

318

Unexpected Error

Mistyped Parameter

2.4.10 SIEMENS release cause for Call-related Supplementary Services

(CRSS)


0

1

2

3

4

ECT procedure failed (timer expired)

Call has been cleared without receiving an answer to ECT request

Initial conditions not fulfilled (one active, one held call)

Received "return error"

Call has been cleared without receiving an answer to CCBS request

5 Initial conditions for CCBS not fulfilled (Idle CRSS)

Causes related to nature of request

25

26

LLC or SNDCP failure

Insufficient resources

27

28

Unknown or missing access point name

Unknown PDP address or PDP type

29

30

User authentification failed

Activation rejected by GGSN


Page 58


95

96

97

98

99

100

101

111

31

32

33

34

35

36

37

Activation rejected, unspecified

Service option not supported

Requested service option not subscribed


NSAPI already used

Regular PDP context deactivation

QoS not accepted

38

39

Network failure

Reactivation requested

40 Feature not supported

Causes related to invalid messages

81 Invalid transaction identifier value



Message type non-existant or not implemented

Message type not comaptible with protocol state



Message not compatible with protocol

Protocol error, unspecified

2.4.11 SIEMENS release cause for Session Management (SM)


3 The MS has not got any answer to the ACTIVATE PDP CONTEXT request message sent five times to the network

4

5

6

7

A MT PDP context which is active or in the activation process is deactivated because another MT PDP context with the same TI is requested by the network to be activated

A MT PDP context which is active or in the activation process is deactivated because another MT PDP context with the same TI is requested by the network to be activated. The activation request is rejected by the

SM sending the cause 'insufficient resources' to the network because the SM was not able to perform the necessary comparisons for a static PDP address collision detection.

A MT PDP context which is active or in the activation process is deactivated because another MT PDP context with the same TI is requested by the network to be activated. As a static PDP address collision with an MO activating PDP context has been detected by the SM the SM discards the activation request

A MT PDP context request has been indicated but could not be processed in time. The activation request is rejected by the SM sending the cause 'insufficient resources' to the network.

2.4.12 GSM cause for L3 Protocol module or other local cause


2 No detailed cause

Number

0

1

2

3

4

255

2.4.13 SIEMENS release cause for GPRS API

Description

Regular deactivation of the call

Action temporarily not allowed

Wrong connection type

Specified data service profile invalid

PDP type or address is unknown

Undefined


Page 59


2.4.14 SIEMENS release cause for Embedded Netcore

Number

0

1

255

Description

Regular call deactivation

LCP stopped

Undefined

2.5 ATS18 Extended call release report

Syntax

Read Command

ATS18?

Write Command

ATS18= <n>

Reference(s)

Response(s)

<n>

OK

Response(s)

OK

PIN SERIAL

V.25ter

○ ●


This command enables or disables the presentation of extended call release reports for fax and data calls. The call release report is presented in numeric format and includes the following parameters:

+CAUSE:

If enabled the message will be reported every time a fax or data call is released or fails to be established.


<n>

(num)(&W)(&V)

An odd number enables the presentation of the extended call release report. An even number disables this feature.

0

(&F)

...255

<locationID>

(num)

Location ID as number code (see also <locationID> of

AT+CEER ).

Location IDs are listed in section 2.4.1

.

Each ID is related to another table that contains a list of <reason>s.

<reason>

(num)

Reason for last call release as number code (see also <reason> of

AT+CEER ). <reason>

numbers and the associated descriptions are listed

in several tables, sorted by different categories in chapter AT+CEER .

The tables can be found proceeding from the Location IDs listed in

2.4.1

.

Note

• The command applies only to circuit switched data and fax calls. For voice calls extended call release reports can be retrieved using the command

AT+CEER .

Examples

EXAMPLE 1

ATS18 =1

Enables the presentation of extended call release reports.

OK


Page 60


ATD03012345678 Now, a mobile originated data call fails.

+CAUSE: 8:17

BUSY

An extended error report is output, followed by the result code BUSY.

The Location ID 8 stated in section

2.4.1

points to section

2.4.6,

where 17 = "User busy".

EXAMPLE 2

ATS18 =1

Enables the presentation of extended call release reports.

OK

ATD03012345678 Now, a mobile originated data call is set up.

CONNECT 9600/RLP

Hello,....

+++ Call ends after remote party hung up.

+CAUSE: 8:16 Normal call release is reported, followed by the result code NO CARRIER.

NO CARRIER The Location ID 8 stated in section

2.4.1

points to section

2.4.6,

where 16 = "Normal call clearing".

2.6 AT+CPAS Mobile equipment activity status

Syntax

Test Command

AT+CPAS=?

Exec Command

AT+CPAS

Response(s)

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

OK

Response(s)

+CPAS: <pas>

OK

ERROR

+CME ERROR: <err>


GSM 07.07

○


TA returns the activity status of ME.

●


<pas>

(num)

0 ready

3 incoming (ringing)

4 call in progress or call hold

2.7 AT+WS46 Select wireless network

Syntax

Test Command

AT+WS46=?

Response(s)

+WS46: (list of supported<n>s)

OK


Page 61


Read Command

AT+WS46?

Response(s)

<n>

OK

Write Command

AT+WS46 = [ <n> ]

Reference(s)

Response(s)

OK

PIN

GSM 07.07

○


<n>

(num)

12 GSM digital cellular

SERIAL

●

VERSION 1.01


Page 62


3 SERIAL INTERFACE CONTROL COMMANDS

The AT commands described in this chapter allow the external application to determine various settings related to the TANGO55/56's serial interface.

3.1 AT\Q Flowcontrol

Syntax

Exec Command

AT\Q[ <n> ]

Response(s)

OK

If RTS/CTS flow control is not supported by interface and <n> is 2 or

3:

ERROR


V.25ter

○ ●


<n>

(num)(&W)(&V)

[0]

(&F)

1 disable flow control

XON/XOFF software flow control

2

3 only CTS by DCE

RTS/CTS hardware flow control Recommended for the following procedures: incoming or outgoing data calls, fax calls.

Often, the initialization routine of fax programs includes enabling RTS/CTS handshake, eliminating the need to issue

AT\Q 3

once again.

Notes

• When using XON/XOFF flow control

( AT\Q 1)

in online mode,

+++

should not be used while the data transmission is paused with XOFF. Before entering the command mode with

+++

the paused transmission should be resumed using the XON character.

3.2 AT&C Set circuit Data Carrier Detect (DCD) function mode

Syntax

Exec Command

AT&C[ <value> ]

Reference(s)

Response(s)

OK

PIN SERIAL

V.25ter

○ ●


This parameter determines how the state of circuit 109 (DCD) relates to the detection of received line signal from the distant end.


<value>

(num)(&W)(&V)


Page 63


[0] DCD line is always ON

1

(&F)

DCD line is ON in the presence of data carrier only

3.3 AT&D Set circuit Data Terminal Ready (DTR) function mode

Syntax

Exec Command

AT&D[ <value> ]

Reference(s)

Response(s)

OK

PIN SERIAL

V.25ter

○ ●


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


<value>

(num)(&W)(&V)

[0]

1

TA ignores status of DTR.

ON->OFF on DTR: Change to command mode while retaining the connected call.

2

(&F)

ON->OFF on DTR: Disconnect data call, change to command mode. During state DTR = OFF is auto-answer off.

3.4 AT&S Set circuit Data Set Ready (DSR) function mode

Syntax

Exec Command

AT&S[ <value> ]

Reference(s)

Response(s)

OK

PIN SERIAL

V.25ter

○ ●


This parameter determines how the TA sets circuit 107 (DSR) depending on the communication state of the TA interfacing TE.


<value>

(num)(&W)(&V)

[0]

(&F)

1

DSR line is always ON

TA in command mode: DSR is OFF. TA in data mode: DSR is

ON.

3.5 ATE Enable command echo

Syntax

Exec Command

ATE[ <value> ]

Response(s)

OK


Page 64



V.25ter

○ ●


This setting determines whether or not the TA echoes characters received from

TE during command state.


<value>

(num)(&W)(&V)

[0]

1

(&F)

Echo mode off

Echo mode on

Note

• In case of using the command without parameter,< value> is set to 0.

3.6 AT+ILRR Set TE-TA local rate reporting

The command AT+ILRR controls whether or not the intermediate result code

"+

ILRR

" is transmitted from the DCE to the DTE.

Syntax

Test Command

AT+ILRR=?

Read Command

AT+ILRR?

Write Command

AT+ILRR= <value>

Response(s)

+ ILRR: (list of supported <value> s)

OK

Response(s)

+ILRR: <value>

OK

Response(s)

OK

ERROR

+CME ERROR


V.25ter

Intermediate Result Code

+ILRR: <rate>

○ ●

Indicates port rate setting on connection.


The write command determines whether or not an intermediate result code of local rate is reported at connection setup. The rate is reported before the final result code of the connection is transmitted to the TE.


<value>

(num)(&W)(&V)

0

(&F)

1

Disables reporting of local port rate

Enables reporting of local port rate

<rate>

(num)

0 port rate setting on connection (bps)

Autobauding (see chapter

3.7.1).

300


Page 65


600

1200

2400

4800

9600

14400

19200

28800

38400

57600

115200

230400

3.7 AT+IPR Set fixed local rate

The command

AT+IPR can be used to set or query the DTE-DCE interface bit rate.

Syntax

Test Command

AT+IPR=?

Read Command

AT+IPR?

Write Command

AT+IPR= <rate>

Response(s)

+ IPR: (list of supported auto-detectable <rate> s) , (list of supported fixed-only <rate> s)

OK

Response(s)

+IPR: <rate>

OK

Response(s)

OK

ERROR

+CME ERROR


V.25ter

○ ●


The test command returns the values of the supported automatically detectable bit rates and the values of the supported fixed bit rates.

The read command returns the current bit rate of the interface.

The write command specifies the bit rate to be used for the interface. When you set a fixed-rate, make sure that both DTE (TE) and DCE (TA) are configured to the same rate. When you select autobauding, the DCE will automatically recognize the bit rate currently used by the DTE.

The setting is stored in the non-volatile memory and will be used whenever the engine is powered up again. However, in case of autobaud mode

( AT+IPR =0)

the detected DCE bit rate will not be saved and, therefore, needs to be

resynchronized after restarting the GSM engine (see chapter 3.7.1).


<rate>

(num)(&V) bit rate per second (bps)

0

(D)

3.7.1).

300


Page 66


600

1200

2400

4800

9600

14400

19200

28800

38400

57600

115200

230400

Notes

• The factory default is autobauding enabled (

AT+IPR =0)

on SERIAL. It will not

be restored with AT&F .

• The current setting of AT+IPR

will be preserved when you download firmware (i.e. a firmware update does not restore the factory setting) or in the event of power failure.

• Generally,

AT+IPR

should be used as a standalone command. If nethertheless combinations with other commands on the same command line cannot be avoided, there are several constraints to be considered:

-

-

-

-

Avoid combinations with the AT commands listed in chapter 0.4.2

.

Take into account, that a delay of 100 ms is required between the response to the last command (e.g. OK) and the next command on the same line.

When you enter

AT+IPR =0,

autobauding will be activated after the response to the last command is received.

When local echo is active (

ATE

1)

and you enter AT+IPR =

X with other commands you may encounter the following problem: if switching to the new bit rate takes effect while a response is being transmitted, the last bytes may be sent with the new bit rate and thus, not properly transmitted. The following commands will be correctly sent at the new bit rate.

• In order to account for greater amounts of data it is recommended to choose a minimum bit rate of 2400 bps.

• A selected bit rate takes effect after the write commands returns OK.

3.7.1 Autobauding

To take advantage of autobaud mode specific attention must be paid to the following requirements:

• Synchronization between DTE and DCE

Ensure that DTE and DCE are correctly synchronized and the bit rate used by the DTE is detected by the DCE (ME). To allow the bit rate to be synchronized simply use an "AT" or "at" string. This is necessary

-

- after you have activated autobauding when you start up the GSM engine while autobauding is enabled. It is recommended to wait 3 to 5 seconds before sending the first AT character. Otherwise undefined characters might be returned.


Page 67


If you want to use autobauding and autoanswer at the same time, you can easily enable the DTE-DCE synchronization, when you activate autobauding first and then configure the autoanswer mode (

ATSO

≠0).

• Restrictions on autobauding operation

-

-

The serial interface shall be used with 8 data bits, no parity and 1 stop bit (factory setting), e.g. 2 stop bits are not supported for autobaud mode.

The command A/ cannot be used.

Only the strings "AT" or "at" can be detected (neither "At" nor "aT").

-

-

-

URCs that may be issued before the ME detects a new bit rate (by receiving the first AT character) will be sent at the previously detected bit rate or, after ME restart, at 57600 bps.

It is not recommended to switch to autobauding from a bit rate that cannot be detected by the the autobaud mechanism (e.g. 300 bps).

Responses to AT+IPR =0

and any commands on the same line might be corrupted.

• Autobauding and bit rate after restart

The most recently detected bit rate is stored when the ME is powered

down (with Table 2.3

).

Therefore, each time the module is restarted the correct bit rate must be found as described above. Unless the bit rate is determined, the following constraints apply:

-

-

An incoming CSD call or a network initiated GPRS request cannot be accepted. This must be taken into account when autobauding and autoanswer mode (

ATSO

≠0) are enabled at the same time, especially if SIM PIN 1 authentication is done automatically and the setting

ATS0

≠0 is stored to the user profile with AT&W .

Until the bit rate is found, URCs generated after restart will be output at 57600 bps. This applies only to user defined URCs, such as "+CREG",

"CCWA", "

^

SCKS" etc. The URCs "

^

SYSSTART" and "

^

SYSSTART ALARM

MODE" will not be indicated when autobauding is enabled.

Note: To avoid any problems caused by undetermined bit rates in the direction from DCE to DTE we strongly recommend to configure a fixed bit rate rather than autobauding.


Page 68


4 SECURITY COMMANDS

The AT commands described in this chapter allow the external application to determine various security related settings.

4.1 AT+CPIN Enter PIN

Syntax

Test Command

AT+CPIN=?

Read Command

AT+CPIN?

Write Command

AT+CPIN= <pin>[,<new pin>]

Response(s)

OK

Response(s)

+CPIN: <code>

OK

ERROR

+CME ERROR: <err>

Response(s)

OK

ERROR

+CME ERROR: <err>


GSM 07.07

○ ●


The read command returns an alphanumeric string indicating whether or not a password is required.

The write command lets the ME store the entered password. This may be for example the SIM PIN1 to register to the GSM network, or the SIM PUK1 to replace a disabled PIN with a new one, or the PH-SIM PIN if the client has taken precautions for preventing damage in the event of loss or theft etc. See above for the list of passwords.

If no PIN request is pending (for example if PIN authentication has been done and the same PIN is entered again) ME responds + CME ERROR: operation not allowed. No action is required from your part.


<pin>

(str)

Password (string type), usually SIM PIN1.

If the requested password was a PUK, such as SIM PUK1 or PH-SIM PUK or

PH-FSIM PUK or another password, then <pin> must be followed by <new pin>.

<new pin>

(text)

If the requested code was a PUK: specify a new password or restore the

former disabled password. See 4.1.1

for more information about when you may need to enter the PUK.

<code>

(text)

SIM PIN authentication

READY

SIM PIN

PIN has already been entered. No further entry needed.

ME is waiting for SIM PIN1.


Page 69


SIM PUK

SIM PIN2

SIM PUK2

VERSION 1.01

ME is waiting for SIM PUK1 if PIN1 was disabled after three failed attempts to enter PIN1.

ME is waiting for PIN2, when the attempt to access PIN2 requiring features was acknowledged with +CME ERROR:17 (e.g. if client attempts to edit the FD phone book).

This is only applicable if the AT+CPIN read command also prompts for SIM PIN2. Normally, the AT+CPIN2 command is intended for SIM

PIN2.

ME is waiting for PUK2 to unblock a disabled

PIN2. Necessary if preceding command was acknowledged with error + CME ERROR:18 and only if the AT+CPIN read command also prompts for SIM PUK2. Normally, the AT+CPIN2 command is intended for SIM PUK2.

Phone security locks set by client or factory

PH-SIM PIN

PH-SIM PUK

PH-FSIM PIN

PH-FSIM PUK

PH-NS PUK

PH-C PIN

ME is waiting for phone-to-SIM card password if "PS" lock is active and user inserts other SIM card than the one used for the lock. ("PS" lock is also referred to as phone or antitheft lock).

ME is waiting for Master Phone Code, if the above "PS" lock password was incorrectly entered three times.

ME is waiting for phone-to-very-first-SIM card.

Necessary when "PF" lock was set. When powered up the first time, ME locks itself to the first SIM card put into the card holder. As a result, operation of the mobile is restricted to this one SIM card (unless the PH-FSIM PUK is used as described below).

ME is waiting for phone-to-very-first-SIM card unblocking password to be given. Necessary when "PF" lock is active and other than first SIM card is inserted.

ME is waiting for network personalisation password

ME is waiting for network personalisation unblocking password

ME is waiting for network subset personalisation password

ME is waiting for network subset unblocking password

ME is waiting for service provider personalisation password

ME is waiting for service provider personalisation unblocking password

ME is waiting for corporate personalisation password


Page 70


PH-C PUK ME is waiting for corporate personalisation unblocking password

Notes

• Caution: After entering a password with AT+CPIN

all other commands that need access to data on the SIM card may be blocked for up to 20 seconds!

• Successful PIN authentication only confirms that the entered PIN was recognized and correct. The output of the result code OK does not necessarily imply that the mobile is registered to the desired network.

Typical example: PIN was entered and accepted with OK, but the ME fails to register to the network. This may due to missing network coverage, denied network access with currently used SIM card, no valid roaming agreement between home network and currently available operators etc.

• ME offers various options to verify the present status of network registration:

For example, the AT+COPS command indicates the currently used network.

With

AT+CREG

you can also check the current status and activate an unsolicited result code which appears whenever the status of the network registration changes (e.g. when the ME is powered up, or when the network cell changes).

• Wait 10 seconds after PIN input before using SMS related commands.

-

<pin> and <new pin> can also be entered in quotation marks (e.g.

"1234").

-

To check the number of remaining attempts to enter the passwords use the

AT^SPIC command.

-

-

See AT+CPWD

and AT^SPWD for information on passwords.

See AT+CLCK and

AT^SLCK

for information on lock types.

4.1.1 What to do if PIN or password authentication fails?

PIN1/PUK1:

After three failures to enter PIN 1, the SIM card is blocked (except for emergency calls). + CME ERROR: 12 will prompt the client to unblock the SIM card by entering the associated PUK (= PIN Unblocking Key/Personal

Unblocking Key). After ten failed attempts to enter the PUK, the SIM card will be invalidated and no longer operable. In such a case, the card needs to be replaced. PIN1 consists of 4 to 8 digits, PUK1 is an 8-digit code only. To unblock a disabled PIN1 you have two options:

-

-

You can enter

AT

+

CPIN

=PUK1 ,new PIN1.

You can use the ATD

command followed by the GSM code

**05*PUK*newPIN*newPIN#;.

PIN2/PUK2:

PIN2 prevents unauthorized access to the features listed in AT+CPIN2 .

The handling of PIN2 varies with the provider. PIN2 may either be a specific code supplied along with an associated PUK2, or a default code such as 0000. In either case, the client is advised to replace it with an individual code. Incorrect input of PUK2 will permanently block the additional features subject to PIN2 authentification, but usually has no effect on PIN1. PIN2 consists of 4 digits,

PUK2 is an 8-digit code only. To unblock a disabled PIN2 you have two options:

-

-

You can enter AT+CPIN2 =PUK2,new PIN2.

You can use the ATD


**052*PUK2*newPIN2*newPIN2#;.


Page 71


Phone lock:

If the mobile was locked to a specific SIM card (= "PS" lock or phone lock), the

PUK that came with the SIM card cannot be used to remove the lock. After three failed attempts to enter the correct password, ME returns +CPIN: PH-SIM

PUK (= response to read command

AT

+

CPIN

?), i.e. it is now waiting for the

Master Phone Code. This is an 8-digit device code associated to the IMEI number of the mobile which can only by obtained from the manufacturer or provider. When needed, contact Siemens AG and request the Master Phone

Code of the specific module. There are two ways to enter the Master Phone code:

-

-

You can enter AT+CPIN=Master Phone Code,new password.

You can use the ATD


*#0003*Master Phone Code#;.

Usually, the Master Phone Code will be supplied by mail or e-mail. If the

received number is enclosed in the *# codes typically used for the ATD

option, it is important to crop the preceding *#0003* characters and the appended #.

Example: You may be given the string *#0003*12345678#. When prompted for the PH-SIM PUK simply enter 12345678.

If incorrectly input, the Master Phone Code is governed by a specific timing algorithm: (n-1)*256 seconds (see table below). The timing should be considered by system integrators when designing an individual MMI.

Number of failed attempts

1st failed attempt

2nd failed attempt

3rd failed attempt

4th failed attempt

5th failed attempt

6th failed attempt

Time to wait before next input is allowed

No time to wait

4 seconds

3* 256 seconds

4* 256 seconds

5* 256 seconds

6* 256 seconds and so forth

SIM locks:

These are factory set locks, such as "PF", "PN", "PU", "PP", "PC". An 8-digit unlocking code is required to operate the mobile with a different SIM card, or to lift the lock. The code can only be obtained from the provider.

Failure to enter the password is subject to the same timing algorithm as the

Master Phone Code (see table above).

Call barring:

Supported modes are "AO", "Ol", "OX", "AI", "IR", "AB", "AG", "AC". If the call barring password is entered incorrectly three times, the client will need to contact the service provider to obtain a new one.

Summary of related chapters:

Related +CME errors are listed in 1.11.1

.

For further instructions and examples

see AT+CLCK ,

AT^SLCK ,

AT+CPWD

and AT^SPWD.

A complete list of *# codes is provided in List of *# Codes.

4.2 AT+CPIN2 Enter PIN2

Syntax

Test Command

AT+CPIN2=?

Response(s)

OK


Page 72


Read Command

AT+CPIN2?

Write Command

AT+CPIN2 = <pin>[,<new pin>]

Response(s)

+CPIN2: <code>

OK

ERROR

+CME ERROR: <err>

Response(s)

OK

ERROR

+CME ERROR: <err>


GSM 07.07

● ●


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

The write command lets the ME store the entered password. This may be for example the SIM PIN2 to benefit from the features listed below, or the SIM PUK2 to replace a disabled PIN2 with a new one. Note that PIN2 can only be entered if PIN1 authentication was done.

If the ME is requesting SIM PUK2, use <pin> to enter the PUK2, followed by <new pin> to specify your new PIN2.


<pin>

(str)

Password (string type), usually SIM PIN2 or, if requested, SIM PUK2.

<new pin>

(str)

If the requested code was SIM PUK2: new password (PIN2).

See Chapter

4.1.1

for more information about when you may need to enter the PUK.

<code>

(text)

READY

SIM PUK2

SIMPIN2

ME is not pending for any password.

ME is waiting for SIM PIN2. This <code> is returned only when PIN2 authentication has not yet been done or has failed (+CME ERROR:"!7).

ME is waiting for SIM PUK2.

This <code> is returned only when PIN2 authentication has failed and ME is pending for SIM PUK2 (i.e. +CME

ERROR:18).

Note

• Functions accessible only after PIN2 authentication:

AT+CACM :

Accumulated call meter (ACM) reset or query

AT+CAMM :

Accumulated call meter maximum (ACMmax) set or query

AT+CLCK :

Facility lock to "FD" (Fixed dialing phone book)

AT^SLCK :

Facility lock to "FD" (Fixed dialing phone book)

AT+CPWD :

Change "P2"password

AT^SPWD :

Change "P2"password

AT+CPUC :

Price per unit and currency table

AT+CPIN2: Enter SIM PIN2 or SIM PUK2 if requested.


Page 73


For example, SIM PIN2 will be needed when you attempt to edit the

"FD" phone book and ME returns +CME Error17or+CPIN:SIM PIN2.

Once the required <pin> has been entered correctly, PIN2 authentication code changes to READY. After 300 s, a repetition of the authentication process is required (PIN2 authentication code changes from READY to SIM PIN2).

Examples

EXAMPLE 1

To change PIN2:

AT+CPWD="P2","0000", "8888" (where "0000" = old PIN2 and "8888" = new

PIN2)

OK

EXAMPLE 2

To unblock a disabled PIN2:

AT+CPIN2?

+CPIN2: SIM PUK2 PIN2 has been disabled, PUK2 must be entered to define a new PIN2,

OK

AT+CPIN2=123456 78,8 888 where "12345678" is the PUK2, and

"8888" the new PIN2.

EXAMPLE 3

To write to "FD" phone book:

AT+CPBS="FD"

OK

AT+CPBW=2,"+4 93012345678",145,"Charly"

+

CME ERROR

17 access denied due to missing PIN2 authentication

AT+CPIN2=8888

OK

AT+CPBW=2,"+4 93012345678",145,"Charly"

OK

4.3 AT

^

SPIC Display PIN counter

Syntax

Test Command

AT^SPIC=?

Read Command

AT^SPIC?

Exec Command

AT^SPIC

Write Command

AT^SPIC=<facility>

Reference(s)

Response(s)

OK

Response(s)

^SPIC: <code>

OK

Response(s)

^SPIC: <counter>

OK

Response(s)

^SPIC: <counter>

OK

PIN SERIAL


Page 74


SIEMENS

○ ●


The read command returns an identification of the currently required password, e.g. the PIN, PUK, PH-SIM PUK etc. The <counter> returned by the execute command refers to this password. In case there is no currently required password (the responses to "

AT

+

CPIN

?" and

" AT+CPIN2 ?"

both read

"READY"), the read command nevertheless identifies the password to which the execute command response refers.

The execute command returns the number of attempts still available for entering the currently required password, e.g. the PIN, PUK, PH-SIM PUK etc. To check whether or not you need to enter a password use commands

AT

+

CPIN

? ,

Read command AT^SPIC ?

and AT+CPIN2 ?.

If the responses to "

AT

+

CPIN

?" and

" AT+CPIN2 ?"

both read "READY", there is no currently required password, and the referrerof the execute command

"AT

^

SPIC" is explicitly undefined.

In these cases, the read command "AT

^

SPIC?" may be used to determine, which password the response of the execute command actually refers to. Also, the write command may be used in order to retrieve the counter for a specific password.

The write command returns the number of attempts still available for entering the password identified by <facility>, e.g. the PIN, PIN 2, PH-SIM PIN etc.


<counter>

(num)

Number of attempts for the currently required password. This number will be counted down after each failure.

<facility>

(str)

Password for which the corresponding PIN counter is to be displayed

"SC" SIM PIN or SIM PUK. If the SIM PIN has been deactivated after three failed attempts, the counter for SIM PUK will be returned instead.

"PS"

"P2"

"phone code" or "device code" (cf. AT+CLCK

and

AT+CPWD ).

If incorrectly entered three times, the

Master Phone Code is required to lift the lock and the number of remaining attempts for the master phonecode will be returned.

SIM PIN 2 or SIM PUK 2. If the SIM PIN 2 has been deactivated after three failed attempts, the counter for SIM PUK 2 will be returned instead.

<code>

(text)

"PN"

Identification of the currently required password.

SIM PIN ME is waiting for SIM PIN1.

SIM PUK

SIM PIN2

ME is waiting for SIM PUK1 if PIN1 was disabled after three failed attempts to enter PIN1.

ME is waiting for PIN2, when the attempt to access PIN2 requiring features was acknowledged with +CME ERROR:17 (e.g. if client attempts to edit the FD phone book).


Page 75


SIM PUK2

PH-SIM PIN

ME is waiting for PUK2 to unblock a disabled PIN2.

Necessary if preceding command was acknowledged with error+CME ERROR: 18.

ME is waiting for phone-to-SIM card password if

"PS" lock is active and user inserts other SIM card than the one used for the lock. ("PS" lock is also referred to as phone or antitheft lock).

PH-SIM PUK ME is waiting for Master Phone Code, if the above

"PS" lock password was incorrectly entered three times.

PH-NET PIN ME is waiting for network personalisation password

PH-NET ME is waiting for network personalisation unblocking password

Notes

• Whenever the required password changes,< counter> changes to reflect that change. Please refer to the examples below.

• Use the read commands "

AT

+

CPIN

?" and

" AT+CPIN2 ?"

to check which password is currently required. If the responses to "

AT

+

CPIN

?" and

" AT+CPIN2 ?"

both read "READY", there is no currently required password, and the referrerof the execute command "AT

^

SPIC" is explicitly undefined.

• In these cases, the read command "AT^SPIC?" may be used to determine, which password the response of the execute command actually refers to.

Also, the write command may be used in order to retrieve the counter for a specific password.

• For passwords associated to the phone lock ("PS" lock set by client or factory) or other factory set locks, such as "PF", "PN", "PU", "PP", "PC" the number of attempts is subject to a timing algorithm explained in

AT

+

CPIN

. If these passwords are incorrectly entered the counter first returns 3, 2 and 1 remaining attempt(s), but then gives the total number of attempts which amounts to 63 (see example below).

• See also chapters

AT+CLCK, AT+CPIN, AT+CPIN2, AT+CPWD, AT^SLCK

for further information on locks and passwords.

Examples

EXAMPLE 1

The client fails to provide a correct SIM PIN three times. The counter decreases each time. After the counter reaches zero, the SIM PUK is required. After failure to enter a correct SIM PUK, the counter decreases. at+cpin?

+

CPIN

:

SIM PIN

(currently required password is

PIN1)

OK at

^ spic

(3 attempts left)

^

SPIC: 3

OK at+cpin=9999

+CME ERROR: incorrect password at

^ spic

^

SPiC: 2

OK

(2 attempts left)


Page 76

TANGO55/56 AT COMMAND SET VERSION 1.01 at+cpin=9999

+CME ERROR:

OK

At

^ spic

OK at+cpin=9999

+CME ERROR: at+cpin?

+

CPIN

:

SIM PUK

OK at

^ spic

^

SPIC: 10

OK at+cpin=0123456 7,12 34

+CME ERROR: at^spic "SPIC: 9

OK incorrect password incorrect password

(now required password is PUK 1)

(10 attempts left for PUK 1) incorrect password

(9 attempts left for PUK1)

EXAMPLE 2

Though a mobile is locked to a specific SIM card (phone lock), the client attempts to operate it with another SIM card. The client correctly enters the SIM PIN of the SIM card currently inserted, but then fails to give the "PS" lock password (PH-SIM PUK): at+cpin=9999

OK at+cpin?

+CPIN:

PH

-

SIM PIN

ME is waiting for the phone lock password

OK at spic

^

SPIC: 3 OK at+cpin=4711

+CME ERROR: PH-SIM PIN required at+cpin=4712

+CME ERROR: at

^ spic

^

SPIC: 1 incorrect password

OK at^spic?

^

SPIC: PH-SIM PIN The counter displayed refers to the phone lock password

OK at+cpin=4713

+CME ERROR: at

^ spic

^SPIC: 63

OK incorrect password


Page 77

TANGO55/56 AT COMMAND SET VERSION 1.01 at^spic?

^

SPIC: PH-SIM PUK The counter displayed refers to the master phone code

OK at+cpin=4714

+CME ERROR: incorrect password at

^ spic

^

SPIC: 63

OK

4.4 AT+CLCK Facility lock

Syntax

Test Command

AT+CLCK=?

Write Command

AT+CLCK= <facility>,<mode>[,<password>][,<class>

]

Response(s)

+CLCK: list of supported <facility> s

OK

Response(s) if <mode> is not equal 2 and command successful:

OK if <mode> = 2 and command successful:

+CLCK: <status> , <class>

[+CLCK: <status>,<class> ]

[+CLCK: ...]

OK

If error is related to ME functionality

+CME ERROR


GSM 07.07, GSM 02.04, GSM 02.88,

GSM 03.88, GSM 04.88

● ●


The Test command returns the supported parameters.

Use this command to lock, unlock or interrogate a network or ME <facility>. The command can be aborted when network facilities are being set or interrogated.


<facility>

(str)

Phone security locks set by client or factory

Primarily intended for the client to take safety precautions, "SC", "PS" and

"FD" can be configured individually.

"PS" may also be factory set.

Parameter <class> is not applicable to security locks.

See examples below for further details.

"SC" SIM (lock SIM cards). SIM requests password upon ME power-up and when this lock command is issued.

<password>: SIM PIN1.

"PS" Phone locked to SIM card. ME requests password when other than current SIM card is inserted.

"PS" lock is frequently referred to as "phone lock", or

"device lock". Accordingly, the password may be


Page 78


"FD" called "phone code" or "device code". The "PS" password is not associated with the PUK of the SIM card. If incorrectly entered three times, the Master

Phone Code is required to lift the lock. This is an 8-digit device code associated to the IMEI number of the mobile which can only by obtained from the manufacturer of the module. Once the Master Phone

Code has been acctepted, the mobile is operational, and the "PS" lock is no longer active. If needed it must be set once again.

<password> : User defined password. It is needed before the first use of <facility> "PS" and, therefore, must first be specified with

AT+CPWD

or

AT^SPWD ,

if it has not been predefined by factory settings. If set by factory (e.g. for a prepaid mobile), the password is supplied by the provider or operator.

SIM fixed dialling memory: If the mobile is locked to

"FD", only the phone numbers stored to the "FD" memory can be dialled. (Capacity of FD phone book depending on the SIM card.) <password> : SIM PIN 2. If a lock on the SIM fixed dialing memory is active, the following applies:

Outgoing voice, data or fax calls can be made only to numbers stored in "FD" phone book.

Result code depends on the type of the call: for voice calls, indication is "+CME Error 257: Call barred".

For data and fax calls, indication is "NO CARRIER".

Access to defined Supplementary Services such as call barring, call waiting, call forwarding, call hold and Multiparty is possible only if the exact corresponding public MMI *# code for the desired service is stored in the fixed dialing

number phone book, and used with ATD .

AT commands for supplementary service control are barred while "FD" lock is active.

Indication is "+CME Error 257: Call barred".

Access to Unstructured Supplementary Services ("USSD") is possible only if the exact desired USSD string is stored in the fixed dialling number phone book, and used with

ATD .

AT commands for USSD are barred while "FD" lock is active.

Indication is "+CME Error 257: Call barred".

SMS can be sent only to phone numbers which are stored in the "fixed dialling numbers" phone book "FD".

Indication is "+CMS Error 302: operation not allowed".

GPRS commands can be used only if the "fixed dialling numbers" phone book "FD" contains an entry with phone number "*99#". This single entry enables all GPRS commands, including AT commands and modem compatibility commands like "ATD*99***1#" or "ATD*98***1#". Indication is

"+CME Error 257: Call barred".

Factory defined SIM locks:

Typical examples of factory set SIM locks are prepaid phones or network locks, used to restrict the operation of a mobile to a specific


Page 79

TANGO55/56 AT COMMAND SET VERSION 1.01 provider or operator. The client should be aware that each of these lock types can only be unlocked if the associated password is available. For example, a mobile can be locked to accept only SIM cards from the respective provider, or even one single SIM card.

Once a different SIM card is inserted the ME will prompt the client to enter a specific code. This is not the PUK of the SIM card, but usually an 8-digit code which needs to be requested from the provider.

The locks can only be set by the manufacturer and need to be agreed upon between the parties concerned, e.g. provider, operator, distributor etc. on the one side and the manufacturer on the other side. For details contact your local dealer or Siemens AG.

Parameter <class> is not applicable to SIM locks.

<password> and instructions for unlocking must be obtained from the network provider.

"PF"

"PN"

"PU"

"PP" lock Phone to the very First SIM card

Network Personalisation

Network subset Personalisation

Service Provider Personalisation

Supplementary Service Call Barring:

Supplementary Service "Call Barring" allows to specify conditions under which calls will be disallowed by the network.

The availability of the Supplementary Services varies with the network. To benefit from call barring the client will need to subscribe them, though a limited number of call barring types may be included in the basic tariff package.

When you attempt to set a <facility> or <class> which is not provisioned, not yet subscribed to, or not supported by the module, the setting will not take effect regardless of the response returned.

The responses in these cases vary with the network (for example "OK",

"+CME ERROR: Operation not allowed", "+CME ERROR: Operation not supported" etc.). To make sure check the extended error response with

AT+CEER and the lock status with

<mode>=2.

<password> : Network password supplied from the provider or operator. Usually there is one password which applies to all call barring options. For details contact your provider.

"AO"

"OI"

"OX"

"AI"

"IR"

BAOC (Bar All Outgoing Calls)

BOIC (Bar Outgoing International Calls)

BOIC-exHC (Bar Outgoing International Calls except to Home Country)

BAIC (Bar All Incoming Calls)

BIC-Roam (Bar Incoming Calls when Roaming outside the home country)

"AB"

"AG"

"AC"

All Barring services (applicable only for

<mode>=0)

All outGoing barring services (applicable only for <mode>=0)

All inComing barring services (applicable only for <mode>=0)

<mode>

(num)


Page 80


0 unlock

1 lock

VERSION 1.01

<status>

(num)

0

1

<password>

(str) lock is inactive lock is active

Password string used to lock and to unlock a <facility>. Length and authority for passwords depend on the <facility> in question and are therefore listed in the section on parameter <facility>. Passwords can be

modified with AT+CPWD or

AT^SPWD .

<class>

(num)

Integer or sum of integers each representing a class of information, i.e. a bearer service, telecommunication service or bearer service group as defined in "GSM 02.04".

1 voice

2 class 2 ("data") comprises all those individual data classes between 16 and 128, that are supported both by the network and the MS. This means, a setting made for class 2 applies to all individual data classes

(if supported). In addition, you can assign a different setting to a specific class. For example, you can activate Call Forwarding for all data classes, but deactivate it for data class 64, "dedicated packet access".

4 fax

8 SMS

64

128

1...[7]...255 dedicated packet access dedicated PAD access combination of some of the above classes.

For example, the default setting 7 represents the sum of the integers 1, 2 and 4 (voice, data and fax).

The value 255 covers all classes.

If parameter "class" is omitted, the default value 7 is used.

Notes

• The

AT+CLCK command offers the full range of

<class> parameters according to the GSM specifications. However, when you attempt to use a service option which is not provisioned or not yet subscribed to, the setting will not take effect regardless of the response returned.

• The responses in these cases vary with the network (for example "OK",

"Operation not allowed", "Operation not supported" etc.). To make sure check the extended error response with

AT+CEER

and the lock status with

<mode>=2.

• The command has been implemented with the full set of <class> parameters according to GSM 07.07. For actual applicability of a desired

Call barring service to a specific service or service group (a specific <class> value) please consumable A.1 of GSM 02.04.


Page 81


• If an outgoing Fax or Data Call is rejected due to an active "call barring" supplementary service, the call will be terminated with result code NO

CARRIER.

• Under the same conditions, an outgoing Voice call will be terminated with result code NO DIALTONE.

Examples

EXAMPLE 1

Lock SIM card (<facility> = "SC")

AT+CLCK="SC", 1, "9999" The"SC" parameter enables or disables the

SIM PIN authentication (PIN 1) when you power up the GSM engine SIM card locked. As a result, SIM PIN 1 must be entered to enable ME to register to the

GSM network.

OK

AT+CLCK="SC",0, "9999" Unlocks SIM card.

When powered up, ME registers to the

GSM network without requesting SIM PIN1.

Note: Depending on the services offered by the provider, this feature is not supported by all SIM card types. If so, the command returns ERROR when you attempt to unlock the card.

OK

To query the status of the SIM card lock:

AT+CLCK="SC",2 Query the status of SIM card lock.

SIM card is locked. SIM PIN1 must be entered to enable ME to register to the

GSM network.

+CLCK: 1

OK

EXAMPLE 2

Phone lock ( <facility> ="PS")

AT+CPIN? Make sure that PIN1 authentication is valid.

OK

To lock the ME to the currently insertd SIM card, first specify a password for

<facility> "PS":

AT+CPWD="PS",,"1234" If "PS" lock has not been set before: enter new password.

OK

Optionally, if "PS" password was defined before, change existing password:

AT+CPWD="PS","1234","3333" To replace existing "PS" password: Enter old and new password.

OK

Then, activate the Phone Lock:

AT+CLCK="PS",1, "333 3" Locks the mobile to the current SIM card.


Page 82


OK

To operate the mobile with the SIM card for which "PS" lock was activated:

AT+CPIN?

+CPIN: SIM PIN

OK

AT+CPIN="9999" No additional password is required for operation (SIM recognized by mobile).

OK

To operate the mobile with other SIM card than the one used for the "PS" lock: Enter SIM PIN of present card, followed by "PS" lock password.

AT+CPIN?

+CPIN: SIM PIN

OK

AT+CPIN="1111"

OK

AT+CPIN?

+CPIN:

PH

-

SIM PIN

OK

PIN authentication accepted.

"PS" lock password is required.

AT+CPIN="3333"

OK

To deactivate the Phone Lock:

AT

+

CLCK

="PS",0, "333 3" Phone Lock password has to be provided again.

OK

"PS" Lock password has been accepted.

ME is fully operational now.

Now the mobile can be used with any SIM card, without the need of the phone lock password.

4.5 AT

^

SLCK Facility lock

AT command AT^SLCK

provides the "Facility lock" function as described for AT

command AT+CLCK

defined in GSM 07.07.

It is identical in every respect to

AT+CLCK ,

except that the command syntax and response prefix is "

^

SLCK" instead of "+CLCK".

Syntax

Test Command

AT^SLCK=?

Write Command

AT^SLCK= <facility>,<mode>[,<password>][,<class>]

Response(s)

^SLCK: list of supported <facility> s

OK

Response(s ) if <mode> is not equal 2 and command successful:


^SLCK: <status>,<class>

[^SLCK: <status>,<class>]

[^SLCK: ...]

OK


+CME ERROR


Page 83


Reference(s)

SIEMENS, GSM 07.07, GSM 02.04, GSM

02.88, GSM 03.88, GSM 04.88

PIN

●

SERIAL

●


The test command returns the supported parameters.

Use this command to lock, unlock or interrogate a network or ME <facility>. The command can be aborted when network facilities are being set or interrogated.

Note

• For further details please refer to AT+CLCK .

4.6 AT+CPWD Change Password

Use this command when you want to change the passwords defined for the "facility

lock" functions available from AT+CLCK .

A password consists of a string of numeric digits with a length in the range specified by <password length>.

Specifically the command can be used to change PIN1 orPIN2, change the password supplied from your provider for the "call barring" supplementary service, set individual phone security passwords, enter the unblocking key (Master Phone Code) to restore a disabled "PS" password.

See AT commands AT+CLCK

and

AT^SLCK

for more information on the various lock features.

Syntax

Test Command

AT+CPWD=?

Write Command

AT+CPWD= <facility>,<old password>[,<new password>]

Response(s)

+ CPWD: (list of supported ( <facility>,<password length> )

OK

Response(s)

New password has been registered for the facility lock function.

OK

If parameter <old password> was not correct:

+CME ERROR 16 (+CME ERROR: incorrect password)

If the password for the selected <facility> has been invalidated due to too many failed attempts:

+CME ERROR ...

If error is related to ME functionality:

+CME ERROR


GSM 07.07

● ●


The test command returns a list of pairs which represent the available facilities and the maximum length of the associated password.

The write command allows to define a new password for a password protected <facility> lock function. Each password is a string of digits, the length of which varies with the associated <facility>.


<facility>

(str)

Phone security locks set by client or factory:


Page 84


Primarily intended for the client to take safety precautions, passwords

"SC" (SIM PIN) and "P2" (SIM PIN2) are usually predefined, but can be configured individually. The password for lock facility "PS" may also be factory set.

"SC" SIM PIN. SIM requests password upon ME power-up and when this lock command is issued.

"PS"

If incorrectly entered three times, the SIM PUK is required to perform authentication. Input of the SIM

PUK password is possible only with AT command

AT+CPIN

or

ATD .

For further details please refer to chapter

4.1.1. <password length>

: 4 to 8 digits.

Phone locked to SIM card. ME requests password when other than current SIM card is inserted.

"PS" lock is frequently referred to as "phone lock", or

"device lock". Accordingly, the password may be called "phone code" or "device code". The "PS" password is not associated with the PUK of the SIM card. It must be defined before the first use of

<facility> "PS" with

AT+CLCK . <password length>:

digits.

If incorrectly entered three times, the Master Phone

Code is required to lift the lock. This unblocking

procedure is performed with AT+CPWD

using the following parameters: <facility>="PS",<old password>=

Master Phone Code (to be obtained from the module manufacturer), and <new password>= the new phone code ("PS" password for lock facility), if desired.

Mind that successful PIN authentication is a prerequisite for use of AT command

AT+CPWD .

If Pin authentication has not been completed, input of the

Master Phone code password is possible only with AT command

AT+CPIN

or

ATD .

For further detail please refer to chapter

4.1.1.

"P2"

Once the Master Phone Code has been acctepted, the mobile is operational, and the "PS" lock is no longer active. If needed it must be set once again with

AT+CLCK .

SIM PIN 2, e.g. required for authentication with q

"FD" ).

If incorrectly entered three times, the SIM PUK 2 is required to perform authentication. Input of the SIM

PUK 2 password is possible only with AT command

AT+CPIN2

or

ATD .

For further detail please refer to chapter

4.1.1. <password length>

: 4 to 8 digits.

Factory defined SIM locks:

Typical examples of factory set SIM locks are prepaid phones or network locks, used to restrict the operation of a mobile to a specific provider or operator. The client should be aware that each of these lock types can only be unlocked if the associated password is available. For example, a mobile can be locked to accept only SIM cards from the respective provider, or even one single SIM card. Once a different SIM card is inserted the ME will prompt the client to enter a


Page 85

TANGO55/56 AT COMMAND SET VERSION 1.01 specific code. This is not the PUK of the SIM card, but usually an 8-digit code which needs to be requested from the provider.

The locks can only be set by the manufacturer and need to be agreed upon between the parties concerned, e.g. provider, operator, distributor etc. on the one side and the manufacturer on the other side.

For details contact your local dealer or Siemens AG.

"PF" lock Phone to the very First SIM card

"PP"

"PC"

Service Provider Personalisation

Corporate Personalisation

Supplementary Service Call Barring :

Supplementary Service "Call Barring" allows to specify conditions under which calls will be disallowed by the network.

The availability of the Supplementary Services varies with the network.

To benefit from call barring the client will need to subscribe them, though a limited number of call barring types may be included in the basic tariff package.

<password length> : The Network Password needs to be supplied from the network provider or network operator. Usually there is one 4 digit password which applies to all call barring options. For details contact your provider.

"AO" BAOC (Bar All Outgoing Calls)

"OI"

"OX"

"AI"

"IR"

BOIC (Bar Outgoing International Calls)

BOIC-exHC (Bar Outgoing International Calls except to Home Country)

BAIC (Bar All Incoming Calls)

"AB"

"AG"

"AC"

<password length>

(num)

4...8

BIC-Roam (Bar Incoming Calls when Roaming outside the home country)

All Barring services

All outGoing barring services

All inComing barring services length of password. The range of permitted length for a password depends on the associated <facility>. It is available from the test command response, or in the description of parameter <facility>.

<old password>

(str)

Password specified for the facility.

Parameter <old password> can be ignored if no old password was allocated to the facility. Take into account that a password may have already been set by factory, or that the service is subject to a password issued by the provider. See notes above or contact provider.

<new password>

(str)

New password. Mandatory, if <old password> was an unblocking key

(such as the Master Phone Code).

Note

• To delete a password use the following syntax:


Page 86

TANGO55/56 AT COMMAND SET VERSION 1.01 at+cpwd= <f acility>,<old password>

Examples

EXAMPLE 1

To change PIN2

AT+CPWD="P2","0000", "8888" (where "0000" = old PIN2 and "8888"

= new PIN2) PIN2 password has been changed to "8888"

OK

EXAMPLE 2

To set password used to enable or disable barring of all outgoing calls:

AT+CPWD="AO","0000","3333" Requests the network to change the password for supplementary service

"call barring". Usually this request will affect all barring services, even though the request is issued for

Supplementary Service BAOC

("Barring of all outgoing calls") only.

Refer to the respective network provider for detail.

OK

EXAMPLE 3

Handling of the "PS" lock password

AT+CMEE=2 Enable text output of CME Error information

AT+CPWD="PS","1111","2222"

OK

AT+CPWD="PS","1111","2222"

(where "1111" = old password and

"2222" = new password)

Password for facility "PS" is now "2222"

Repeat command to provoke error

"incorrect password"

+CME ERROR: incorrect password ("1111" is no longer the correct password)

EXAMPLE 4

To specify a new "PS" lock password, after the old password was disabled

(e.g. after three failed attempts to change the "PS" password): use the master phone code.

CAUTION: THIS TEST SHOULD BE PERFORMED ONLY IF THE CORRECT MASTER

PHONE CODE FOR THE INDIVIDUAL ME USED IS DEFINITELY AVAILABLE!

Otherwise the module used will be rendered useless until the correct master phone code is entered!:

AT+CPWD="PS","12345678","1111" where 12345678 is the Master Phone

Code and 1111 is the new password.

You may also use <new password> to restore the former disabled password.

OK

Alternatively, without giving a new password:

AT+CPWD="PS","12345678" (where 12345678 is the Master Phone

Code). Deactivates the present phone lock.

OK


Page 87


4.7 AT

^

SPWD Change Password

Use this command when you want to change the passwords defined for the "facility

lock" functions available from AT+CLCK .

Specifically the command can be used to change PIN1 orPIN2, change the password supplied from your provider for the "call barring" supplementary service, set individual phone security passwords, enter the unblocking key (Master Phone Code) to restore a disabled "PS" password.

See AT commands AT+CLCK

and

AT^SLCK

for more information on the various lock features.

AT command AT^SPWD

is identical in every respect to AT+CPWD ,

except that the command syntax and response prefix is "^SPWD" instead of "+CPWD".

Syntax

Test Command

AT^SPWD=?

Write Command

AT^SPWD= <facility>,<old password>[,<new password>]

Response(s)

^SPWD: (list of supported ( <facility>,<password length> )

OK

Response(s)

New password has been registered forthe facility lock function.

OK

If parameter <old password> was not correct:

+CME ERROR 16 (+CME ERROR: incorrect password)

If the password forthe selected <facility> has been invalidated due to too many failed attempts:

+CME ERROR ...


+CME ERROR

PIN

○

SERIAL

●


The test command returns a list of pairs which represent the available facilities and the maximum length of the associated password.

The write command allows to define a new password for a password protected <facility> lock function. Each password is a string of digits, the length of which varies with the associated <facility>.

Note

• For further description please refer to AT+CPWD.


Page 88


5 IDENTIFICATION COMMANDS

The AT commands described in this chapter allow the external application to obtain various identification information related to the TANGO55/56 and linked entities.

5.1 ATI Display product identification information

Syntax

Exec Command

ATI

Exec Command

ATI [<value>]

Response(s)

SIEMENS TANGO55/56 REVISION xx.yy

OK

Response(s)

[SIEMENS Gipsy Soft Protocolstack V2.550]

OK


V.25ter

●


ME issues product information text.

●

Explanation of' Revision' parameter: Version xx and variant yy of software release.

ME issues additional identification information, after using with optional parameter. ATI9 delivers the information above. Other values are not supported and only return OK.


<value>

(num)

SIEMENS Gipsy Soft Protocol stack V2.550

5.2 AT+CGMI Request manufacturer identification

Syntax

Test Command

AT+CGMI=?

Exec Command

AT+CGMI

Response(s)

OK

Response(s)

SIEMENS

OK


GSM 07.07

○ ●


TA returns manufacturer identification text.

Note

• See also: AT+GMI .

5.3 AT+GMI Request manufacturer identification

Syntax


Page 89


Test Command

AT+GMI=?

Exec Command

AT+GMI

Reference(s)

Response(s)

OK

Response(s)

SIEMENS

OK

PIN SERIAL

V.25ter

○ ●


TA reports information to identify the manufacturer.

Note

• See also: AT+CGMI

5.4 AT+CGMM Request model identification

Syntax

Test Command

AT+CGMM=?

Response(s)

OK

Exec Command

AT+CGMM

Reference(s)

Response(s)

TANGO55/56

OK

PIN SERIAL

GSM 07.07

○ ●


TA returns product model identification text.

Note

• See also: AT+GMM .

5.5 AT+GMM Request TA model identification

Syntax

Test Command

AT+GMM=?

Exec Command

AT+GMM

Reference(s)

Response(s)

OK

Response(s)

TANGO55/56

OK

PIN SERIAL

V.25ter

○ ●


TA reports one or more lines of information text which permit the user to identify the specific model of device.

Note

• See also: AT+CGMM


Page 90


5.6 AT+CGMR Request revision identification of software status

Syntax

Test Command

AT+CGMR=?

Exec Command

AT+CGMR

Response(s)

OK

Response(s)

REVISION <xx.yy>

OK


GSM 07.07

○ ●


TA returns product firmware version identification text.


Version xx and variant yy of software release.

Note

• See also: AT+GMR .

5.7 AT+GMR Request TA revision identification of software status

Syntax

Test Command

AT+GMR=?

Exec Command

AT+GMR

Response(s)

OK

Response(s)

REVISION <xx.yy>

OK


V.25ter

○ ●


TA returns product software version identification text.


<xx.yy>

(text)

Version xx and variant yy of software release.

Note

• See also: AT+CGMR

5.8 AT+CGSN Request product serial number identification (IMEI) identical to GSN

Syntax

Test Command

AT+CGSN=?

Response(s)

OK


Page 91


Exec Command

AT+CGSN

Response(s)

<sn>

OK


GSM 07.07

○ ●


TA returns identification text for determination of the individual ME.


<sn>

(str)

IMEI of the telephone (International Mobile station Equipment Identity)

Note

• See also: AT+GSN .

5.9 AT+GSN Request TA serial number identification (IMEI)

Syntax

Test Command

AT+GSN=?

Exec Command

AT+GSN

Response(s)

OK

Response(s)

<sn>

OK


V.25ter

○ ●


TA reports one or more lines of information text which permit the user to identify the individual device.


<sn>

(str)

IMEI of the telephone (International Mobile station Equipment Identity)

Note

• The serial number (IMEI) varies for every individual ME device.

5.10 AT+CIMI Request international mobile subscriber identity

Syntax

Test Command

AT+CIMI=?

Exec Command

AT+CIMI

Response(s)

OK

Response(s)

OK

ERROR

+CME ERROR: <err>



Page 92


GSM 07.07

● ●


TA returns IMSI for identifying the individual SIM which is attached to ME.


<imsi>

(str)

International Mobile Subscriber Identity (string without quotes).


Page 93


6 CALL RELATED COMMANDS

The AT commands described in this chapter are related to Mobile Originated (MOC, i.e. outgoing) Calls and Mobile Terminated (MTC, i.e. incoming) Calls.

6.1 Call Status Information

For circuit switched calls, including voice, fax and data calls, call status information is available with URC ""+CIEV":

call" (configurable via AT commands AT+CIND

and

AT+CMER )

or - in more detail - from the list of current calls. This list can be displayed

on request via AT commands AT+CLCC

and

AT^SLCC .

It can also be issued by the

ME in the form of an unsolicited result code "^

SLCC

"

if configured with AT^SLCC

and

AT+CMER .

URC ""+CIEV": call" and URC "^

SLCC

" can be configured using AT command

AT^SCFG .

An overview of the possible configurations and their consequences for the availability of call status information will be given here.

Generally speaking, the call status values recognized by the ME are as follows:

• active

• held

• dialing (MOC)

• alerting (MOC)

• incoming (MTC)

• waiting (MTC)

• terminating: The call is not active anymore, but inband information is still available.

• dropped: The call has been suspended by the network, but may be resumed later.

The values "terminating" and "dropped" are not standardized for AT command

AT+CLCC ,

and therefore only available for command AT^SLCC .

A call in any of

these two states will not appear in the list of current calls as displayed with AT+CLCC .

A call that is not recognized by the ME is considered to be in "unknown" state. Some networks may schedule a traffic channel for a call that is not yet in the "active" state.

This is reflected in parameter <traffic channel assigned>

of AT command AT^SLCC

and the corresponding URC.

Depending on the value of AT^SCFG setting

<succ>, Indicator "+

CIEV

" will be issued (if configured with

AT+CIND

and

AT+CMER )

when a state transition ends in state

"active" or in state "unknown" (if AT^SCFG setting <

suco="restricted"> ).

When any state transition (including transitions beginning or ending in state

"unknown") occurs in the list of active calls, or when a traffic channel is established (if

AT^SCFG setting

<suco="verbose">).

The indicator value for indicator ""+ciEV":call" will be "1" if at least one call is in states

"held" or "active", and "0" otherwise.

Depending on the value of AT^SCFG

setting <sucs>, indicator "^

SLCC

" will be issued (if

configured with write command AT^SLCC

and

AT+CMER )

when a state transition

ends in state "active" or in state "unknown" (if AT^SCFG

setting <sucs> ="restricted") when any state transition (including transitions beginning or ending in state

"unknown") occurs in the list of active calls, or when a voice channel is established (if

AT^SCFG setting <sucs>="verbose").

Due to compatibility considerations, the power up default for AT^SCFG

setting

<succ> is "restricted", offering compatibility to the standard behaviour of indicator

""+

CIEV

" : call", while the default for setting <sucs> is "verbose".


Page 94


In order to see the URCs, event reporting for both indicators must be explicitely configured with the appropriate AT commands.

6.2 ATA Answer a call

Syntax

Exec Command

ATA

Response(s)

In case of data call, if successfully connected:

CONNECT <text> TA switches to data mode. In case of voice call, if successfully connected:

OK

When TA returns to command mode after call release:

OK

If no connection:

NO CARRIER


V.25ter

● ●


TA causes remote station to go off-hook (e.g. answer call).


<text>

(str)

Connection status

<text>

output only if ATX parameter setting with value greater 0.

Notes

• Any additional commands on the same command line are ignored.

• The command may be aborted generally by receiving a character during execution. It can't be aborted in some connection setup states, such as handshaking.

• If

AT+FCLASS

setting is 1 or 2, all incoming calls will be answered as fax calls.

For calls explicitly signalled as voice or data calls, this procedure will fail with result code "NO CARRIER", but the call in question will continue to ring.

• It is possible to change the setting for

AT+FCLASS

to 0 while the call is ringing, and accept the call normally afterwards with

ATA

.

• The

ATA

command may be used also to accept a network request for a

PDP context activation (see

ATA

).

• See also ATX

for <text>.

6.3 ATD Mobile originated call to dial a number

Syntax


Page 95


Exec Command

ATD <n>[<mgsm>][;]

Response(s)

If no dialtone (parameter setting ATX 2 or ATX 4):

NO DIALTONE

If busy (parameter setting ATX 3 or ATX 4):

BUSY

If a connection cannot be set up:

NO CARRIER OK

If successfully connected and non-voice call (TA switches to online data mode):

CONNECT <text>


OK

If successfully connected and voice call:

OK


V.25ter

◑ ●


This command can be used to set up outgoing voice, data or fax calls. It also serves to control Supplementary Services. The termination character ";" is mandatory to set up voice calls or to send *# codes for Supplementary

Services. It must not be used for data and fax calls.

Additional notes on the responses returned after dialing with ATD :

-

For voice calls, you have the choice of two different response modes that can be selected with

AT

^

SM

2 0:

AT

^

SM

2 0=1 (factory default) causes the ME to respond once the call setup is completed either successfully ("OK") or unsuccessfully ("NO CARRIER", "NO DIAL TONE",

"BUSY").

-

AT

^

SM

2 0=0 causes the ME to return "OK" immediately after dialing was completed (i.e. before call setup terminates successfully or unsuccessfully).

For data connections, call setup always terminates when the call has been established (indicated by the result code "CONNECT <text> ), or

when it fails (indicated by "NO CARRIER"). The settings of AT^SM20

do not apply.

Different call release indications:

-

Upon termination, an outgoing fax or data call may show a different result code than a voice call would show under identical conditions. In order to track down the actual reason for call termination,

AT+CEER

or

ATS18 should be used for all applicable connections.

Using ATD

during an active call:

-

When a user originates a second voice call while there is already an active voice call, the first call will automatically put on hold. The second call attempt is acknowledged with "OK" immediately after dialing with

ATD has completed, without relation to a successful call setup. In case

of failure, the additional result codes "NO CARRIER", "NO DIAL TONE",

"NO CARRIER" will be presented afterwards (see example below).


<n>

(text)

String of dialing digits and optional V.25ter modifiers: 0-9, *, #, +, A, B, C.

The following V.25ter modifiers are ignored: ,(comma), T, P, !, W ,@


Page 96


Emergency call: <n> = 112 , 911 or 08, standardized GSM emergency number (no SIM needed).

<mgsm>

(str)

String of GSM modifiers:

I Activates CLIR (disables presentation of own phone number to called party)

CLIR number to called party)

G Activate Closed User Group explicit invocation for this call only. g Deactivate Closed User Group explicit invocation for this call only.

Notes

• The command may be aborted generally when receiving an ATH

command during execution. It cannot be aborted in some connection setup states, such as handshaking.

• Parameter "I" and "i" only if no *#-code is within the dial string.

• <mgsm> is not supported for data calls.

• <n> is default for last number that can be dialled by

ATDL .

• See also ATX

for <text>.

• If

ATD

is used with a USSD command (e.g. ATD*100#;) an AT+CUSD=1 is

executed implicitly (see AT+CUSD ).

• Parameter 'G' or 'g' will be ignored if Closed User Group was already activated, respectively deactivated with

AT+CCUG

command before. Call by call invocation of CUG uses the settings provisioned by the provider or, if available, the settings of the parameters <index> and <info> made with

AT+CCUG .

• The ME is equipped with a "Blacklist" function according to GSM02.07

Annex A:

After a predefined number of failed call attempts, the dialed number is entered into a read-only phone book called "blacklist" (phone book "BL").

Call attempts to numbers contained in the blacklist will be barred by ME and not signalled to the network.

An attempt to start a voice call to a barred phone number will be stopped with a CME ERROR 257 "Call Barred".

An attempt to start a data or fax call to a barred phone number will be answered immediately with result code "NO CARRIER".

The barred numbers are automatically removed from the blacklist according to the timing conditions specified in GSM02.07 Annex A.

Example

The following example shows the call setup procedure when a call is already active and a second call attempt fails because the line of the called party is busy: atd03012345678

OK

ATD03022222222

Dialing out the first party's number.

The first call is established.

OK

The number of the second party is dialed.

The response "OK" is issued immediately though no call is established (same


Page 97


BUSY behavior as is you had chosen

AT

^

SM

2

0=0.)

Line of the second called party is busy.

6.4 ATD><mem><n> Originate call to phone number in memory

Syntax

Exec Command

ATD> <mem><n>[<mgsm>];

Response(s)

ERROR

+CME ERROR: <err>

If no dialtone (parameter

ATX 2 or ATX 4):

NO DIALTONE


BUSY

If connection cannot be set up:

NO CARRIER


OK

If successfully connected:

OK


V.25ter

● ●


TA attempts to set up an outgoing call to the specified number. The termination character ";" is mandatory since dialing from a phone book is only supported for voice calls and for sending *# codes of Supplementary Services or other functions.


<mem>

(str)

Phone book storage:

For detailed description of storages see AT+CPBS .

"FD"

"SM"

(&F)

Fixed dialing phone book

SIM phone book

"ON"

"ME"

"LD"

"MC"

MSISDN list

Mobile Equipment Phone book

Last number dialed phone book

Missed (unanswered received) calls list

Received calls list

<n>

(num)

"RC"

Integer type memory location in the range of locations available in the selected memory, i.e. the index number returned by

AT+CPBR .

<mgsm>

(str)


I i

Activates CLIR (disables presentation of own phone number to called party)

Deactivates CLIR (enables presentation of own phone number to called party)


Page 98


Notes

• This command may be aborted generally by receiving a character during execution. Abortion is not possible during some states of connection setup such as handshaking.

• There is no <mem> for emergency call ("EN").

• The command is not applicable to data calls. Any attempt to dial a data call number from <mem> causes the result code "NO CARRIER" to appear.

• Parameter <mgsm> only if no *# code is within the dialing string.

• See ATX for setting result code and call monitoring parameters.

Examples

EXAMPLE 1

To query the location number of the phone book entry:

AT+CPBR=1,xx

TA returns the entries available in the active phone book.

EXAMPLE 2

To dial a number from the SIM phone book, for example the number stored to location 15:

ATD>SM15;

OK

EXAMPLE 3

To dial a phone number stored in the last dial memory on the SIM card:

ATD>LD9;

OK

6.5 ATD><n> Originate call to phone number selected from active memory

Syntax

Exec Command

ATDxn>[ <mgsm> ];

Response(s)

ERROR

+CME ERROR: <err>


ATX 2 or ATX 4):

NO DIALTONE


BUSY


NO CARRIER


OK


OK


V.25ter

● ●


TA attempts to set up an outgoing call to the stored number. The termination character ";" is mandatory since dialing from a phone book is only supported


Page 99

TANGO55/56 AT COMMAND SET VERSION 1.01 for voice calls and for sending *# codes of Supplementary Services or other functions.


<n>

(num)

Integer type memory location in the range of locations available in the

selected memory, i.e. the index number returned by AT+CPBR .

<mgsm>

(str)


I i



Notes


• The command is not applicable to data calls. Any attempt to dial a data call number from <n> causes the result code "NO CARRIER" to appear.


6.6 ATD><str> Originate call to phone number in memory with corresponding field

Syntax

Exec Command

ATDxstr>[ <mgsm> ];

Response(s)

ERROR

+CME ERROR: <err>


ATX 2 or ATX 4):

NO DIALTONE


BUSY


NO CARRIER


OK


OK


V.25ter

● ●


This command searches the active phone book for a given string <str> and dials the assigned phone number. The termination character ";" is mandatory since dialing from a phone book is only supported for voice calls and for sending *# codes of Supplementary Services or other functions.


<str>

(str)(+CSCS)

String type value ("x"), which should equal an alphanumeric field in at least one phone book entry in the searched memories; used character


Page 100


set should be the one selected with AT+CSCS . <str>

can contain escape sequences as described in chapter "Supported character sets".

<str> must be wrapped in quotation marks (" "), if escape sequences or parameter <mgsm> are used or if the alphanumeric strings contains a blank. If not, quotation marks are optional.

If AT+CSCS

is set to "UCS2", with respect to the coding of UCS2-characters only phone book entries that contain an alphanumeric string with assize less than the half of the paramter <tlength> from

AT+CPBW

can be dialed.

<mgsm>

(str)


I i



Notes


• The command is not applicable to data calls. Any attempt to dial <str> without semicolon ";" causes the result code "NO CARRIER" to appear.


6.7 ATDI Mobile originated call to dialable ISDN number

<n>

Syntax

Exec Command

ATDI <n>[<; >]

Response(s)


ATX 2 or ATX 4):

NO DIALTONE


BUSY


NO CARRIER

All other error reasons:

+CME ERROR

If successfully connected and non-voice call (TA switches to data state):

CONNECT <text>


OK


OK


V.25ter

● ●


TA attempts to set up an outgoing call to ISDN number.


<n>

(str)

ISDN number [+]<d>


Page 101


String with maximum length of 20 characters. Allowed characters:

+: international dialing format

<;>

(str)

<d>: 0-9, A, B, C voice call.

Note


6.8 ATDL Redial last telephone number used

Syntax

Exec Command

ATDL[;]

Response(s)

If there is no last number or number is not valid:

+CME ERROR


ATX 2 or ATX 4):

NO DIALTONE


BUSY


NO CARRIER

If successfully connected and non-voice call (TA switches to online data mode):

CONNECT <text>


OK


OK


V.25ter

● ●


This command redials the last voice and data call number used in the

ATD

command. If terminated with semicolon ";"

ATDL dials the last voice call

number stored in the "LD" phone book. Otherwise, the last dialed data or fax number will be used (not contained in the "LD" phone book).

Notes


• Parameter "I" and "i" only if no *#-code is within the dial string.

6.9 ATH Disconnect existing connection

Syntax

Exec Command

ATH[ <n> ]

Reference(s)

Response(s)

OK

PIN SERIAL


Page 102


V.25ter

○ ●


Disconnect existing call from command line by local TE and terminate call.


<n>

(num)

[0] disconnect from line and terminate call

Notes

• OK is issued after circuit 109 (DCD) is turned off, if it was previously on.

•

ATH terminates every circuit switched call (voice, data or fax), even if it is

issued via another interface. This behavior is in accordance with ITU-T V.25 ter; (07/97, "Hook control":

" ATH is terminating any call in progress.").

•

ATH

clears any active PDP context or terminates any existing PPP connection, but only if issued on the same interface where GPRS is used and if there is no pending network request for PDP context activation. It does not affect PDP contexts and PPP connections on other interfaces (see also chapter "

ATH

Manual rejection of a network request for PDP context activation").

6.10 AT+CHUP Hang up call

Syntax

Test Command

AT+CHUP=?

Exec Command

AT+CHUP

Response(s)

OK

Response(s)

OK

ERROR

+CME ERROR


GSM 07.07

●


Cancels all active and held calls.

●

Note

• AT+CHUP

implements the same behaviour as ath.

6.11 ATS0 Set number of rings before automatically answering the call

Syntax

Read Command

ATS0?

Write Command

ATS0= <n>

Reference(s)

Response(s)

<n>

OK

Response(s)

OK

PIN SERIAL


Page 103


V.25ter

◑ ●


This parameter setting determines the number of rings before automatic answering.


<n>

(num)(&W)(&V)

000

(&F) automatic answering is disabled

001-255 enable automatic answering on the specified ring number

Notes

• This command works for MT data and fax calls.

• Autoanswering of CSD data and fax calls is supported on SERIAL.

• A CSD call will not be answered automatically if the module is in GPRS online mode. However, this is possible in GPRS command mode. The application can detect a call by evaluating the RING line and distinguish to change into GPRS command mode or stay in GPRS online mode until

GPRS is available again. To answer, to reject or to wait for automatic answering the incoming call the application has to switch into GPRS command mode.

• If <n> is set to higher values, the calling party may terminate the call establishment before the call can be automatically answered.

• The correlation between

ATS7

and ATS0 is important.

• Example: ATS7 =30 and

ATS0 =20 may not allow call establishment.

• Setting is local to the interface. It is allowed to have different settings on different interfaces. In such cases the interface 'wins', which is idle and uses the smallest <n> value.

• ATSO write command is PIN protected.

• The command ATS0 is also used as GPRS compatibility command to

answer automatically to a network request for PDP context activation (for

details see ATS0 for GPRS). So using ATS0 =

<n> with n > 0, will perform a GPRS attach, if the ME is not already GPRS attached and if ME is configured to

do this (see AT^SCFG ,

parameter <gaa>). If the GPRS attach fails (e.g. the network rejects the attach request), the write command returns with error, but the value of <n> is changed anyway.

The GPRS attach will not be performed on recalling a stored user profile with

ATZ

or on power up, if a n > 0 setting was stored in the user profile with

AT&W .

6.12 ATS6 Set pause before blind dialing

Syntax

Read Command

ATS6?

Response(s)

<n>

OK

Response(s)

OK

Write Command

ATS6= <n>

Reference(s)

V.25ter

PIN

○

SERIAL

●


Page 104



No effect for GSM.


<n>

(num)(&W)(&V)

000

(&F)

...255

6.13 ATS7 Set number of seconds to wait for connection completion

Syntax

Read Command

ATS7?

Write Command

ATS7= <n>

Reference(s)

Response(s)

<n>

OK

Response(s)

OK

PIN SERIAL

V.25ter

○ ●


This parameter setting determines the amount of time to wait for the connection completion when answering or originating a call.


<n>

(num)(&W)(&V) no. of seconds to wait for connection completion 000...060

(&F)

Notes

• Values bigger than 60 cause no error, but <n> will be set down to maximum value of 60.

• In <n> of

ATS0

of the called party is set to higher values the call establishment may not be successful.

• The correlation between

ATS7

and ATS0 is important.

Example: =30 and

ATS0 =20 may not allow call establishment.

6.14 ATS8 Set number of seconds to wait for comma dialing modifier

Syntax

Read Command

ATS8?

Write Command

ATS8= <n>

Reference(s)

Response(s)

<n>

OK

Response(s)

OK

PIN SERIAL

V.25ter

○ ●


No effect for GSM.


Page 105



<n>

(num)(&W)(&V)

6.15 ATS10 Set disconnect delay after indicating the absence of data carrier

Syntax

Read Command

ATS10?

Write Command

ATS10= <n>

Reference(s)

Response(s)

<n>

OK

Response(s)

OK

PIN SERIAL

V.25ter

○ ●


This parameter setting determines the amount of time, that the TA remains connected in absence of a data carrier. If the data carrier is detected before disconnect, the TA remains connected.


<n>

(num)(&W)(&V) number of tenths of seconds of delay

001...2

(&F)

...255

6.16 ATP Select pulse dialing

Syntax

Exec Command

ATP

Reference(s)

Response(s)

OK

PIN

○

SERIAL

●

V.25ter

Note

• No effect for GSM.

6.17 ATO Switch from command mode to data mode/PPP online mode

Syntax

Exec Command

ATO[<n>]

Response(s)

If connection is not successfully resumed:

NO CARRIER or

TA returns to data mode from command mode

CONNECT <text>

Note: <text> output only if

ATX

parameter setting with value > 0.


Page 106



V.25ter

○ ●


ATO

is the corresponding command to the

+++ escape sequence: When you

have established a CSD call or a GPRS connection and TA is in command mode,

ATO

causes the TA to resume the data or GPRS connection and takes you back to data mode or PPP online mode.


<n>

(num)

[0] Switch from command mode to data mode

6.18 +++ Switch from data mode to command mode

Syntax

Exec Command

+++

Reference(s)

Response(s)

OK

PIN SERIAL

V.25ter

○ ●


This command is only available during a CSD call or a GPRS connection. The

+++ character sequence causes the TA to cancel the data flow over the AT

interface and switch to command mode. This allows you to enter AT commands while maintaining the data connection to the remote device or, accordingly, the GPRS connection. To prevent the

+++ escape sequence from

being misinterpreted as data, it must be preceded and followed by a pause of at least 1000 ms. The

+++ characters must be entered in quick succession, all

within 1000 ms.

Note

• To return from command mode to data or PPP online mode: Enter

ATO

.

6.19 ATT Select tone dialing

Syntax

Exec Command

ATT

Reference(s)

V.25ter

Note

• No effect for GSM.

Response(s)

OK

PIN

○

SERIAL

●

6.20 AT+CBST Select bearer service type

Syntax


Page 107


Test Command

AT+CBST=?

Read Command

AT+CBST?

Write Command

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

Response(s)

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

OK

Response(s)

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

OK

Response(s)

OK

ERROR

+CME ERROR: <err>


GSM 07.07

○ ●


The write command selects the bearer service <name>, the data rate

<speed> and the connection element <ce> to be used when data calls are originated. The settings also apply to mobile terminated data calls, especially when single numbering scheme calls or calls from analog devices are

received (see also: AT+CSNS ).


<speed>

(num)(&W)(&V)

[7]

(&F)

9600 bps (V.32)

75

<name>

(num)(&W)

14400 bps(V. 110)

0

(&F) asynchronous modem

<ce>

(num)(&W)

Transparent mode is not supported.

1

(&F) non-transparent

Note

• GSM 02.02[1]: List of allowed combinations of subparameters.

6.21 AT+CRLP Select radio link protocol param. for orig. non-transparent data call

Syntax

Test Command

AT+CRLP=?

Read Command

AT+CRLP?

Response(s)

+CRLP: (list of supported <iws>s ), (list of supported <mws>s), (list of supported <Ti>s ), (list of supported <N2>s )

OK

Response(s)

+ CRLP: <iws>,<mws>,<T1>,<N2>[,<verx>] OK


Page 108


Write Command

AT+CRLP= [<iws>[,< mws>[,<T1>[,<N2>[,<verx>]]]]

Response(s)

OK

ERROR

+CME ERROR: <err>


GSM 07.07

○ ●


Read command returns current settings for the supported RLP version 0.

The Write command sets radio link protocol (RLP) parameters used when nontransparent data calls are originated.


<iws>

(num)(&W)(&V)

Interworking window size (IWF to MS)

<mws>

(num)(&W)(&V)

Mobile window size (MS to IWF)

<T1>

(num)(&W)(&V)

Acknowledgement timer (T1 in 10 ms units)

48...[78]

(&F)

...255

<N2>( num

)(

&w

)(

&v

)

Re-transmission attempts N2

1...[6]

(&F)

...255

<verx>

(num)

0 RLP version number in integer format; when version indication is not present it shall equal 0.

Notes

• RLP version 0: single-link basic version;

• RLP version 1: single-link extended version (e.g. extended by data compression);

• RLP version 2: multi-link version.

• Compression and multi-link are not supported.

6.22 AT+CLCC List current calls of ME

Syntax

Test Command

AT+CLCC=?

Exec Command

AT+CLCC

Response(s)

OK

Response(s)

[+CLCC:

<idx>,<dir>,<stat>,<mode>,<mpty>[,<number>,<type>[,<alpha>]] ]

[+CLCC:

<idx>,<dir>,<stat>,<mode>,<mpty>[,<number>,<type>[,<alpha>]] ]

[+CLCC: ...]

OK

ERROR

+CME ERROR



Page 109


GSM 07.07

● ●


The exec command returns a list of current calls of ME. If command is successful, but no calls are available, no information response is sent to TE.


<idx>

(num) call identification number as described in GSM02.30 subclause 4.5.5.1;

this number can be used in AT+CHLD command operations

<dir>

(num)

0 mobile originated call (MOC)

<stat>

(num) state of the call

0

1 active held

2

3

4

5 dialing (MOC) alerting (MOC) incoming (MTC) waiting (MTC)

<mode>

(num) bearer/teleservice

0 voice

1 data

2 fax

3

4 voice followed by data, voice mode (only in connection with

scheme )

alternating voice/data, voice mode (only in connection with

single numbering scheme AT+CSNS )

5

6

7

8 alternating voice/fax, voice mode (only in connection with


voice followed by data, data mode (only in connection with


alternating voice/data, data mode (only in connection with


alternating voice/fax, fax mode (only in connection with


9 unknown

<mpty>

(num)

0 call is not one of multiparty (conference) call parties call is one of

<number>

(str) phone number in format specified by <type>

<type>

(num) type of address octect

145 dialling <number> includes international access code


Page 110


<alpha>

(str)(+cscs)

Alphanumeric representation of <number> corresponding to the entry found in phone book; used character set should be the one selected

with command AT+CSCS

(Select TE Character Set).

The maximum displayed length of <alpha> is 16 characters. If the

<alpha> has more than 16 characters, only the first 15 characters will be displayed. To indicated an overflow, a special character will be used as the 16th character. This will be a space if the character set selected with

AT+CSCS is 'GSM', or'E400' if the character set is 'UCS2'.

Due to time constraints on the necessary evaluation of the phone book, this parameter may show a default value during early call phases (e.g. for <stat>= "dialling", "incoming" or "alerting"), even if a phone book entry is present for the number concerned.

Note

• Teleservices other than voice, data, fax are not fully supported by ME. They are used only in connection with the handling for

AT+CSNS ,

and may therefore occur in parameter <mode> for mobile terminated calls.

6.23 AT

^

SLCC Siemens defined command to list the current calls of the ME

Command

^

SLCC covers essentially the same information as GSM 07.07 command

AT+CLCC ,

with the following additions:

• The execute command response contains an additional parameter <traffic channel assigned> indicating whether the call has been assigned a traffic

channel by the network (transmission of data or inband information is

possible).

• The additional write command allows to activate event reporting for the list

of current calls. If event reporting is active for an interface, a call status

transition (see

6.1)

and (if desired) the assignment of a traffic channel will

generate an event report indication to this interface. In order to receive

this event report as an URC, the URC presentation mode for this interface

has to be configured with AT+CMER .

• The frequency of event report generation can be configured with AT command

AT^SCFG .

Refer to Call Status Information for further detail on

the configuration options.

• The additional read command allows to determine the event reporting mode <n> which indicates whether the interface receives event report

indications for the list of current calls. Mind that the URC will be displayed

only if the URC presentation mode for the interface concerned has been

configured with AT+CMER .

Syntax

Test Command

AT^SLCC=?

Read Command

AT^SLCC?

Response(s)

OK

Response(s)

^SLCC: <n>

OK

Exec Command

AT^SLCC

Response(s)

^PSLCC: <idx>,<dir>,<stat>,<mode>,<mpty>,<traffic channel assigned>[,<number>,<type>[,<alpha>]]]

^PSLCC: <idx>,<dir>,<stat>,<mode>,<mpty>,<traffic channel


Page 111


Write Command

AT^SLCC= [<n>] assigned>[,<number>,<type>[,<alpha>]]]

OK

ERROR

+CME ERROR

Response(s)

OK

ERROR

+CME ERROR: <err>

Reference(s)

SIEMENS

PIN

●

SERIAL

●


Unsolicited Call Status information if the list of current calls is empty:

^SLCC: if one or more calls are currently in the list:

^SLCC: <idx>,<dir>,<stat>,<mode>,<mpty>,<traffic channel assigned>[,<number>,<type>[,<alpha>] ]

[^SLCC: <idx>,<dir>,<stat>,<mode>,<mpty>,<traffic channel assigned>[,<number>,<type>[,<alpha>] ]]

[. . . ]

^SLCC:

URC "^

SLCC

" displays the list of current calls as displayed with the execute command AT^SLCC . The list is displayed in the state it has at the time of display, not in the state it had when the signal was generated. The URC's occurrence indicates call status changes for any of the calls in the list of current calls. Please refer to

6.1

and AT^SCFG for further information about the configuration of this URC.

Event reporting can be enabled separately for each interface. Interface settings are saved with AT&W and can be displayed with AT&V

.

Additionally, the URC presentation mode for the interface must be configured with AT+CMER .

Depending on the value of AT^SCFG setting <sucs>, Indicator "^

SLCC

" will be issued (if configured with write command AT^SLCC

and AT+CMER )

when a state transition ends in state "active" or in state "unknown"

(if AT^SCFG setting <sucs> ="restricted") when any state transition (including transitions beginning or ending in state "unknown") occurs in the list of active calls, or when a traffic channel is established (if AT^SCFG setting <sucs> ="verbose").

If multiple displays of identical list configurations occur, this happens because of short intermediate states of the list, that have already been overridden by new transitions and states. Thus, it is guaranteed that the configuration displayed is always the current configuration at the time of the last display.

The list of active calls displayed with this URC will always be terminated with an empty line preceded by prefix "

^

SLCC:", in order to indicate the end of the list.


The read command returns an indication whether event reporting is active for the current interface.


Page 112


The exec command returns a list of current calls of ME. If command is successful, but no calls are available, no information response is sent to TE.

Use the write command to activate or deactivate event reporting for URC

"^

SLCC

". Event reporting can be enabled separately for each interface.

Interface settings are saved with AT&W

and can be displayed with AT&V .


<idx>

(num) call identification number as described in GSM02.30 subclause 4.5.5.1;


<n>

(num)(&W)(&V)

0 presentation of URC "^

SLCC

" disabled

1 presentation URC " enabled

<dir>

(num)

0 mobile originated call (MOC)

1 mobile

<stat>


0 active

1 held

6

7 terminating: The call is not active anymore, but inband information is still available. dropped: The call has been suspended by the network, but may be resumed later.

<mode>

(num) bearer/teleservice

0 voice

1 data

2 fax

3 voice followed by data, voice mode (only in connection with


4

5

6 alternating voice/data, voice mode (only in connection with


alternating voice/fax, voice mode (only in connection with


voice followed by data, data mode (only in connection with


7

8 alternating voice/data, data mode (only in connection with


alternating voice/fax, fax mode (only in connection with


9 unknown

<mpty>

(num)

0 call is not one of multiparty (conference) call parties


Page 113


1 call is one of multiparty (conference) call parties

<traffic channel assigned>

(num)

0

1

No traffic channel is available to the call mobile has been assigned a traffic channel.

It is now possible to send or receive inband information, e.g. to send DTMF tones (cf.

AT+VTS ),

or to receive network announcements.

<number>

(str) phone number in format specified by <type>

<type>

(num) type of address octect

145 dialing includes international access code character'+'

129 otherwise

<alpha>

(str)

Alphanumeric representation of <number> corresponding to the entry found in phone book; used character set should be the one selected with

command AT+CSCS

(Select TE Character Set).

The maximum displayed length of <alpha> is 16 characters. If <alpha> has more than 16 characters, only the first 15 characters will be displayed. To indicate an overflow, a special character will be used as the 16th

character. This will be a space if the character set selected with AT+CSCS

is

'GSM', or 'E400' if the character set is 'UCS2'.

Due to time constraints on the necessary evaluation of the phone book, this parameter may show a default value during early call phases (e.g. for

<stat>= "dialing", "incoming" or "alerting"), even if a phone book entry is present for the number concerned.

Notes

• Teleservices other than voice, data, fax are not fully supported by ME. They

are used only in connection with the handling for AT+CSNS ,

and may therefore occur in parameter <mode> for mobile terminated calls.

• If a URC "^

SLCC

"

in verbose mode (see AT^SCFG )

has been buffered while the interface was in dedicated mode (depending on the settings of

AT+CMER

parameter <bfr>), each buffered event indicator will be output as a separate URC after the interface returns to idle mode.

• However, the output will deliver the list of current calls in the "current" state

(at the time when the output is generated), possibly leading to multiple displays of identical list configurations.

• Some parameters of AT command

AT+CHLD , as well as some situations

where the call status in the network changes very quickly (e.g. the transition between <stat>= "unknown", "dialing" and "alerting" for a call to a reachable subscriber within the registered network) may lead to quasisimultaneous changes to the states of one or several calls in the list, possibly leading to multiple displays of identical list configurations.

• If multiple displays of identical list configurations occur, this happens because of intermediate states of the list, that have already been overridden by new transitions and states. Thus, it is guaranteed that the configuration displayed in such cases is the current configuration at the time of the last display.

• It is adviseable to receive URC "^

SLCC

" on an interface that is not used for call initiation, if verbose output is configured. If only voice calls are


Page 114

TANGO55/56 AT COMMAND SET VERSION 1.01 expected, a setting of

AT

^

SM

20 =0 may be used alternatively in order to keep the call from blocking the interface.

Examples

EXAMPLE 1

^

SYSSTART at+cpin=9999

OK

+CREG: 2

+ CREG: 1, ' '0145' ', ' '0016' at

^ sm20=0

OK atd''1234567'' ; We start a voice call. response because of setting "

^

SM20=0" call B-party

1,0,2,0,0,0,''1234567'',129,''Called

Party''

We are now registered command

"ATD" for an outgoing voice call will terminate immediately with response

"OK"

^

SLCC:

1,0,2,0,0,1,''1234567'',129,''Called network may now transmit network

Party'' announcements, ME may now transmit

DTMF tones.

^SLCC:

1,0,3,0,0,1,''1234567'',129,''Called

Party''

^

SLCC:

^SLCC:

Call is now ringing at B-Party

B-Party has accepted the call, connection established

1,0,0,0,0,1,''1234567'',129,''Called

Party'' atd23456; We start a second voice call. response because another call is already active

(cf.

ATD )

SLCC: The active call is automatically put on hold, triggering the display of the list

1,0,1,0,0,0,''1234567'',129, ''Called

Party''

^SLCC: 2,0,2,0,0,1,"23456",129 The second call has already started before the indication for the held call could be displayed


Page 115


^SLCC: The identical list is displayed again, triggered by the start of the second voice call

1,0,1,0,0,0,''1234567'',129,''Called

Party''

^SLCC: 2,0,2,0,0,1,"23456",129 The status of the second list entry has already been displayed with the previous URC

^SLCC: The held call doesn't change status right now

1,0,1,0,0,0,''1234567'',129,''Called

Party''

^SLCC: 2,0,3,0,0,1,"23456",129 The second call is now alerting the B-

Party

^SLCC: The held call doesn't change status right now

1,0,0,0,0,1,''1234567'',129,''Called

Party''

^SLCC:

NO CARRIER

^SLCC:

NO CARRIER

End of current list: the B-Party of the second call has not accepted the call in time, the second call has ended.

The second call has ended list is now empty: B-Party has ended the first call

The second call has ended

EXAMPLE 2

^SLCC: 1,1,4,0,0,1,''1234567'',12 9 Incoming call is signalled.

Display is triggered by the incoming call, but the current status of the call at the time of display already comprises an active traffic channel.

RING Incoming call is signalled.

^SLCC: 1,1,4,0,0,1, ''12 34567' ',129 The incoming call had a traffic channel assigned from the start.

This second identical display is triggered by the traffic channel assignment.

Since the traffic channel was already indicated in the previous URC, both instances of the URC contain identical information.

RING ata

Incoming call is signalled.

Incoming call is accepted,

OK call is established.

^SLCC: 1,1,0,0,0,1,' '1234567' ',12 9 The call is now active.


Page 116


ATH

OK

^

SLCC

:

Hang up the call.

Hang up complete.

The list of current calls is empty again

6.24 AT+CR Service reporting control

Syntax

Test Command

AT+CR=?

Read Command

AT+CR?

Write Command

AT+CR= <mode>

Response(s)

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

OK

ERROR

+CME ERROR

Response(s)

+CR: <mode>

OK

ERROR +CME ERROR

Response(s)

OK

ERROR

+CME ERROR


GSM 07.07

●

●

Intermediate Result Code

If enabled, an intermediate result code is transmitted at the point during connect negotiation when the TA has determined the speed and quality of service to be used, before any error control or data compression reports are transmitted, and before any final result code (e.g. CONNECT) appears.

+CR: <serv>


Configures the TA whether or not to transmit an intermediate result code+CR:

<serv> to TE when a call is being set up.


<mode>

(num)(&W)(&V)

0

(&F)

disable

<serv>

(str)

"REL ASYNC" "GPRS- asynchronous non-transparent GPRS »

Notes

• The PLMN influences the second air interface (to the terminator), therefore another mode may be established from the network.

• Setting the value of <mode> to 1 may lead to connection failure, if the application (e.g. WinFax) waits for default result code/URC.


Page 117


6.25 AT+CRC Set Cellular Result Codes for incoming call indication

Syntax

Test Command

AT+CRC=?

Read Command

AT+CRC?

Write Command

AT+CRC= [<mode>]

Response(s)

+CRC: (list of supported <mode> s)

OK

ERROR

+CME ERROR

Response(s)

+CRC: <mode>

OK

ERROR

+CME ERROR

Response(s)

OK

ERROR

+CME ERROR


GSM 07.07

○ ●


When enabled, an incoming call is indicated to the TE with unsolicited result code + CRING: <type> instead of the normal RING.

+CRING: <type>


The command controls whether or not the extended format of incoming call indication is used.


<mode>

(num)(&W)(&V)

[0]

1

(&F) disable extended format enable extended format

<type>

(str)

“REL ASYNC” asynchronous non-transparent

“FAX” facsimile

“VOICE” voice

“GPRS” <PDP_type> , <PDP_addr>[,[<L2P>][,<

APN

>]] network request for PDP context activation

GPRS

Note

• Setting the value of <mode> to 1 may lead to connection failure, if the application (e.g. WinFax) waits for default result code/URC.

6.26 AT+CSNS Single Numbering Scheme

Syntax

Test Command

AT+CSNS=?

Response(s)

+CSNS: (list of supported <mode> s)

OK


Page 118


Read Command

AT+CSNS?

Write Command

AT+CSNS= [<mode>]

Response(s)

+CSNS: <mode>

OK

Response(s)

OK

ERROR

+CME ERROR


GSM 07.07

○ ●


The

AT+CSNS

command enables the ME to accept incoming calls when no bearer capability information is provided with the call, e.g. single numbering scheme calls or calls originitating from analog devices.


<mode>

(num)

[0]

(D)

2

4

Voice: Each call received without bearer element is assumed to be speech.

Fax: Each call received without bearer element is assumed to be an incoming fax.

Data: Each call received without bearer element is assumed to be a data call.

Please take into account that the bearer service parameters set with

AT+CBST

apply to all data calls including those received without bearer capability.

Notes

• The command must be set before the call comes. By default, when you do not modify the settings, all calls received without bearer element are assumed to be voice.

• The setting will be automatically saved when you power down the GSM

engine with Table 2.3

, provided that PIN authentication has been done.

This value will be restored when PIN authentication is done again.

6.27 AT^SCNI List Call Number Information

Syntax

Test Command

AT^SCNI=?

Response(s)

OK

Exec Command

AT^SCNI

Response(s)

^SCNI: <id>-|[,<cs>[,<number>,<type>]] ^SCNI:

<id>

2

[,<cs>[,<number>,<type>]]

[…]

OK

ERROR

+CME ERROR: <err>

Reference(s)

SIEMENS

PIN

●

SERIAL

●



Page 119


TA returns a list of current calls of ME.


<id>

(num) call identification number as described in GSM 02.30 [19] subclause 4.5.5.1;


1...7

<cs>

(num) call status of respective call number (first parameter)

<number>

(str) string type phone number in format specified by <type>

<type>

(num) type of address octet in integer format; 145 when dialling string includes international access code character"+", otherwise 129

Note

• See also GSM 07.07: AT+CLCC

6.28 AT

^

SLCD Display Last Call Duration

Syntax

Test Command

AT^SLCD=?

Exec Command

AT^SLCD

Response(s)

OK

ERROR

+CME ERROR

Response(s)

^SLCD: <time>

OK

ERROR

+CME ERROR

Reference(s)

SIEMENS

PIN

●

SERIAL

●


TA returns last call duration or current call duration.


<time>

(str)

Format is "hh:mm:ss", where characters indicate hours, minutes, seconds;

E.g. 22:10:00 "22:10:00" Max value is 9999:59:59

6.29 AT

^

STCD Display Total Call Duration

Syntax

Test Command

AT^STCD=?

Response(s)

OK

+CME ERROR


Page 120


Exec Command

AT^STCD

Response(s)

^STCD: <time>

OK

+CME ERROR

Reference(s)

SIEMENS

PIN

●

SERIAL

●


TA returns total call duration (accumulated duration of all calls).


<time>

(str)

Format is "hh:mm:ss", where characters indicate hours, minutes, seconds;

E.g. 22:10:00 "22:10:00" Max value is 9999:59:59

Note

• The Total Call Duration will not be reset by power off or other means.


Page 121


7 NETWORK SERVICE COMMANDS

The AT commands described in this chapter are related to various network services.

More commands related to this area can be found in chapter Supplementary

Service Commands .

7.1 AT+COPN Read operator names

Syntax

Test Command

AT+COPN=?

Exec Command

AT+COPN

Response(s)

OK

Response(s)

+ COPN: <numericn>,<alphan>

+ COPN: ...

OK


GSM 07.07

●

●


TA returns the list of operator names from the ME. Each operator code

<numericn> that has an alphanumeric equivalent <alphan> in the ME memory

is returned. See also: AT^SPLM .


<nuraericn>

(str)

Operator in numeric form; GSM location area identification number.

<alphan>

(str)

Operator in long alphanumeric format; can contain up to 16 characters.

7.2 AT+COPS Operator selection

This command can be used to query the present status of the ME's network registration and to determine whether automatic or manual network selection shall be used.

Automatic mode:

Lets the ME automatically search for the home operator. If successful the ME registers to the home network and enters the IDLE mode. If the home network is not found, ME goes on searching. If then a permitted operator is found, ME registers to this operator. If no operator is found the ME remains unregistered.

Manual mode: Desired operator can be manually entered, using the

AT+COPS write command syntax. If operator is found, ME registers to this

operator immediately. If the selected operator is forbidden, the ME remains unregistered.

Manual/automatic:

In this mode, the ME first tries to find the operator that was manually entered.

If the ME fails to register to this operator, then it starts to select automatically another network.

Syntax


Page 122


Test Command

AT+COPS=?

Read Command

AT+COPS?

Response(s)

+C0PS:[list of supported:( <stat> , long alphanumeric <oper> , , numeric <oper> )][, , list of supported <mode> s, list of supported

<format> s]

OK

ERROR

+CME ERROR

Response(s)

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

OK

ERROR

+CME ERROR

Write Command

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

Response(s)

OK

ERROR

+CME ERROR


GSM 07.07

○ ●


The test command returns a list of quadruplets, each representing an operator present in the network. Any of the formats may be unavailable and will then be an empty field (,,). The list of operators comes in the following order: Home network, networks referenced in SIM, and other networks.

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

The write command forces an attempt to select and register the GSM network operator. If the selected operator is not available, no other operator will be selected (except <mode>=4). The selected operator name format will apply to further read commands (+COPS?), too.


<stat>

(num)

Status

0 unknown

<oper>

(&V)

Operator

Parameter is stored non-volatile to the SIM. Operator as per <format> .

The numeric format is the GSM Location Area Identification number which consists of a 3-digit country code plus a 2- or 3-digit network code.

<mode>

(num)(&V)

Parameter values 0 and 1 are stored non-volatile in the ME

0

(D) automatic mode; <oper> field is ignored

1 manual operator selection

Write command requires <oper>.<format> value shall be 2.


Page 123


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

2 manual deregister from network and remain unregistered until <mode>=0,1,4 is selected

3 set (for read command +COPS?)

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

<format>

(num)(&W)(&V)

parameter can be stored non-volatile in the user profile using AT&W

0

(&F) long format alphanumeric <oper>; up to 16 characters

2 numeric GSM Location Area Identification number

Notes

•

AT+COPS settings are effective over all interfaces of the TANGO55/56.

• When using the

AT+COPS =?

command during an ongoing GPRS transfer, the transfer will be interrupted for up to 1 minute.

7.3 AT+CREG Network registration

Syntax

Test Command

AT+CREG=?

Read Command

AT+CREG?

Response(s)

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

OK

Response(s)

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

OK

ERROR

+CME ERROR: <err>

Write Command

AT+CREG= [<n>]

Response(s)

OK

ERROR

+CME ERROR: <err>


GSM 07.07

○ ●

Unsolicited Result Codes

URC1

If <n>=1 and there is a change in the ME network registration status:

+CREG: <stat>

URC2

If <n>=2 and there is a change in the ME network registration status or a change of the network cell:

+CREG: <stat>[, <lac>, <ci>]


Read command returns the URC presentation mode <n> and an integer <stat> that shows the registration status of the ME. The location information elements


Page 124


<lac> and <ci> are returned only when <n>=2 and ME is registered to the network.

Use the write command to select the type of URC. Two types of URCs are available:

<n> =1: +CREG: <stat>

<n> =2: +CREG: <stat> [ ,<lac>,<ci> ]


<n>

(num)(&W)(&V)(&F)

0(&F)

1 disable URCs enable URC +CREG: <stat> to report status of network registration enable <stat> [, <lac> , <ci> ] to report status of network registration including location information. Please note that optional parameters will not be displayed during call.

<stat>

(num)(&V)

0 Not registered, ME is currently not searching for new operator

There is a technical problem. User intervention is required. Yet, emergency calls can be made if any network is available.

Probable causes.

-

-

No SIM-card available

No PIN entered

1

2

-

No valid Home PLMN-Entry found on the SIM

Registered to home network

Not registered, but ME is currently searching for a new operator.

The ME searches for an available network. Failure to log in until after more than a minute may be due to one of the following causes:

-

No network available or insufficient Rx level.

-

The ME has no access rights to the networks available.

-

Networks from the SIM list of allowed networks are around, but login fails due to one of the following reasons:

-

#11 ... PLMN not allowed

-

#12 ... Location area not allowed

-

#13 ... Roaming not allowed in this location area

-

After this, the search will be resumed (if automatic network search is enabled).

The Home PLMN or an allowed PLMN is available, but login is rejected by the cell (reasons: Access Class or

LAC).

If at least one network is available, emergency calls can be made.

-

If automatic network search is enabled:

Authentication or registration fails after Location Update

Reject due to one of the following causes:


Page 125


-

-

#2 ... IMSI unknown at HLR

#3 ... Illegal MS

-

#6 ... Illegal ME

Either the SIM or the MS or the ME are unable to log into any network. User intervention is required. Emergency calls can be made, if any network is available.

-

Only if manual network search is enabled:

Manual registration fails after Location Update Reject due to the following causes:

-

-

#2 ... IMSI unknown at HLR

#3 ... Illegal MS

-

-

#6 ... Illegal ME

#11 ... PLMN not allowed

-

-

#12 ... Location area not allowed

#13 ... Roaming not allowed in this location area

No further attempt is made to search or log into a net-work.

Emergency calls can be made if any network is available.

4 Unknown

(not used)

5 Registered,

The ME is registered at a foreign network (national or international network)

<lac>

(str)

Two byte location area code in hexadecimal format (e.g. "00C3" equals

193 in decimal).

<ci>

(str)

Two byte cell ID in hexadecimal format.

Note

• Optional parameters will not be displayed during a call.

Example

OK network operator

OK

+CREG: 2 URC reports that ME is currently searching.

+CREG: 1, "0145", "291A" URC reports that operator has been found.

7.4 AT+CSQ Signal quality

Syntax

Test Command

AT+CSQ=?

Response(s)

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

OK


Page 126


Exec Command

AT+CSQ

Response(s)

+ CSQ: <rssi>,<ber>

OK


GSM 07.07

○ ●


TA returns received signal strength indication <rssi> and channel bit error rate

<ber> from the ME.


<rssi>

(num)

0 -113dBmorless

1 -111

31

99

-51 dBm or greater not known or not detectable

<ber>

(num)

To check the bit error rate there must be a call in progress to obtain realistic values. If no call is set up, there is no BER to be determined. In this case the indicated value may be 0 or 99, depending on the SIM card.

0..7

99 as RXQUAL values in the table in GSM 05.08 section 8.2.4. not known or not detectable

Note

• After using network related commands such as AT+CCWA ,

AT+CCFC ,

AT+CLCK ,

users are advised to wait 3s before entering AT+CSQ .

This is recommended to be sure that any network access required for the preceding command has finished.

7.5 AT

^

SMONC Cell Monitoring

Syntax

Test Command

AT^SMONC=?

Exec Command

AT^SMONC

Response(s)

OK

Response(s)

^SMONC:

<MCC> 1,< MNC> 1,< LAC> 1,< cell> 1,< BSIC> 1,< chann> 1,< RSSI> 1,< C

1> 1,< C2> 1,< MCC> 2,< MNC> 2,< LAC> 2,< cell> 2,< BSIC> 2,< chann> 2,<

RSSI> 2,< C1> 2,< C2> 2, ...

OK

CME ERROR

Reference(s)

SIEMENS, 3GPPTS 05.08

PIN

●

SERIAL

●


The output of the exec command contains 9 values from a maximum of 7 base stations. The first base station is the serving cell.


<MCC>

(num)


Page 127


Mobile country code

3 digits, e.g. 232

<MNC>

(num)

Mobile network code

3 digits, e.g.

003 000 not decoded

<LAC>

(num)

Location area code

4 digits, e.g. 3010

<cell>

(num)

Cell identifier

4 hexadecimal digits, e.g. 4EAF

<BSIC>

(num)

Base station identity code

2 digits, e.g. 32

VERSION 1.01

<chann>

(num)

ARFCN (Absolute Frequency Channel Number)

0 not decoded. In this case, all remaining parameters related to the same channel are neither decoded.

For example, a non-existing cell appears as follows:

000,000,0000,0000,00,0,0,-,-

<RSSI>

(num)

Received signal level of the BCCH carrier (0..63). The indicated value is composed of the measured value in dBm plus an offset. This is in accordance with a formula specified in 3GPP TS 05.08

<Cl>

(num)

Coefficient for base station reselection, e.g. 30. In dedicated mode, under certain conditions the parameter cannot be updated. In such cases a '-' is presented.

<C2>

(num)

Coefficient for base station reselection, e.g. 30. In dedicated mode, under certain conditions the parameter cannot be updated. In such cases a '-' is presented.

Note

•

To some extent, the cell monitoring commands AT^MONI ,

AT^MONP

and

AT^SMONC

cover the same parameters. The receiving level, for example, can be queried with all three commands. Yet the resulting values may be slightly different, even though obtained over a time period of a few seconds. This is quite normal and nothing to worry about, as the cell information is permanently updated.

7.6 AT

^

MONI Monitor idle mode and dedicated mode

Syntax


Page 128


Test Command

AT^MONI=?

Exec Command

AT^MONI

Response(s)

^

MONI

: (list of supported <period> s)

OK

Response(s) See: 7.6.1

OK

Write Command

AT^MONI= <period>

Reference(s)


OK

PIN SERIAL

SIEMENS

○

●


The execute command can be used to retrieve the cell parameters of the serving/dedicated cell on request.

The write command can be used to retrieve information of the serving/dedicated cell automatically every <period> seconds. To stop the presentation type "AT" or "at".


<period>

(num)

Display period in seconds

1...254

Notes

• The two header lines (see

7.6.1)

are output after every ten data lines.

• The length of following output lines exceeds 80 characters. Therefore a terminal program may draw a carriage return on a screen. However, this is not part of the response.

7.6.1 AT

^

MONI responses

ME is not connected: a) ME is camping on a cell and registered to the network: chann rs dBm PLMN LAC cell NCC BCC PWR RXLev C1

I chann TS timAdv PWR dBm Q ChMod

1013 21 -71 00101 1001 0103 7 7 33 -105 33 I No connection b) ME is camping on a cell but not registered to the network (only emergency call allowed): chann rs dBm PLMN LAC cell NCC BCC PWR RXLev C1


1013 21 -71 00101 1001 0103 7 7 33 -105 33 I Limited Service c) ME camping on a cell, but searching for a better cell (cell reselection): chann rs dBm PLMN LAC cell NCC BCC PWR RXLev C1


Page 129



1013 21 -71 00101 1001 0103 7 7 33 -105 33 d) ME is searching and could not (yet) find a suitable cell:

I Cell Reselection chann rs dBm PLMN LAC cell NCC BCC PWR RXLev C1


Searching e) ME is connected (Call in progress): chann rs dBm PLMN LAC cell NCC BCC PWR RXLev C1


1013 19 -76 00101 1001 0103 7 7 33 -105 33 I 1015 1 0 5 -76 0 S_HR

Columns for Serving Cell:

Column

chann rs dBm

PLMN

LAC cell

NCC

BCC

PWR

RXLev

C1

Description

ARFCN (Absolute Frequency Channel Number) of the BCCH carrier

RSSI value 0 - 63 (RSSI = Received signal strength indication) receiving level of the BCCH carrier in dBm

PLMN ID code location area code, see note below cell ID, see note below

PLMN colour code base station colour code maximal power level used on RACH channel in dBm minimal receiving level (in dBm) to allow registration coefficient for base station selection

Columns for Dedicated channel:

Column

chann

TS timAdv

PWR dBm

Q

ChMod

Description

ARFCN (Absolute Frequency Channel Number) of the TCH carrier Note: <chann> = h indicates frequency hopping. timeslot number timing advance in bits current power level receiving level of the traffic channel carrier in dBm receiving quality (0-7) channel mode (S_HR: Half rate, S_FR: Full rate, S_EFR: Enhanced Full Rate)

Depending on the service state, an additional textual output is generated (refer also to the response examples):

• 'Searching' - The MS is searching, but could not (yet) find a suitable cell. This output appears after restart of the MS or after loss of coverage.

• 'No connection' - The MS is camping on a cell and registered to the network. The service state is 'idle', i.e. there is no connection established or a dedicated channel in use.

• 'Cell Reselection' - The MS has not yet lost coverage but is searching for a better cell, since the cell reselection criterion is fulfilled.


Page 130


• 'Limited Service' - The MS is camping on a cell but not registered to the network. Only emergency calls are allowed. The MS enters this state, for example, when

-

-

-

- no SIM card is inserted, or PIN has not been given, neither Home PLMN nor any other allowed PLMN are found, registration request was not answered or denied by the network

(use command

AT+CREG to query the registration status),

authentication failed.

7.6.3 Notes

• The parameters LAC and cell are presented as hexadecimal digits, the remaining parameters are composed of decimal digits.

• If the radio cell changes during a connection, the parameters PWR, RXLev and C1 of the 'Serving Cell' part cannot be updated under certain conditions and therefore, are displayed as "-" (for conditions see also

AT+CREG ). This is because the MS does not update the cell selection and

reselection parameters since, in this mode, they are not relevant for operation. When the connection ends, and the mobile is back to IDLE mode, correct values will be given.

• If the radio cell changes during a connection, it normally takes 1 or 2 seconds to update the parameters cell, NCC and BCC. Until the information is received from the new base station, the default values will be shown instead: cell="0000", NCC="-", BCC="-".

If the BS supports frequency hopping during a connection, the dedicated channel (parameter chann) is not stable. This mode is indicated by chann

= 'h'.

• To some extent, the cell monitoring command AT^SMONC

covers the same parameters. The receiving level, for example, can be queried with both commands. Yet the resulting values may be slightly different, even though obtained over a time period of a few seconds. This is quite normal and nothing to worry about, as the cell information is permanently updated.

• For compatibility with earlier products and to support legacy applications, any input character may be used to stop the output in certain cases

(depending on the settings of

3.7

).

7.7 AT

^

MONP Monitor neighbour cells

Syntax

Test Command

AT^MONP=?

Response(s)

^MONP: (list of supported <period> s)

OK

Exec Command

AT^MONP

Write Command

AT^MONP=<period>

Reference(s)


OK


OK

PIN SERIAL


Page 131


SIEMENS

○

●


This command can be used to obtain information of up to six neighbour cells on request.

This command can be used to retrieve information of up to six neighbour cells automatically every n seconds. To stop the presentation type "at" or "AT".


<period>

(num)


1...254

Note

• Due to the fact that not all necessary information of the neighbour cells can be decoded during a connection, there are several constraints to be considered:

-

Only neighbour cells that have already been visible in IDLE mode will be further updated, as long as they are still included in the list.

-

-

Though new neighbour cells can be added to the list (e.g. due to handover), their C1 and C2 parameters cannot be displayed until the connection is released. In this case "-" is presented for C1 and

C2.

To some extent, the cell monitoring command AT^SMONC

covers the same parameters. The receiving level, for example, can be queried with both commands. Yet the resulting values may be slightly different, even though obtained over a time period of a few seconds. This is quite normal and nothing to worry about, as the cell information is permanently updated.

7.7.1 AT

^

MONP responses

Response of AT^MONP (Example):

Chann rs dBm MCC MNC BCC C1 C2

653 26 -84 262 07 0 22 22

660 20 -90 262 07 3 16 16

687 19 -91 262 07 1 15 15

678 14 -96 262 07 3 10 10

671 14 -96 262 07 1 10 10

Column chann rs dBm

MCC

MCC

BCC

C1

C2

Description

ARFCN (Absolute Radio Frequency Channel Number) of the BCCH carrier RSSI value 0 - 63

RSSI value 0 - 63 (RSSI = Received signal strength indication) receiving level in dBm

Mobile Country Code (first part of the PLMN code)

Mobile Network Code (second part of the PLMN code)

Base Station colour code cell selection criterion cell reselection criterion


Page 132


7.8 AT

^

SMONG GPRS Monitor

Syntax

Test Command

AT^SMONG=?

Response(s)

^SMONG: (list of supported <table> s), (list of supported <period> s)

OK

Exec Command

AT^SMONG

Response(s)

GPRS Monitor

Cell Info Table (see: 7.7.1

)

OK

Write Command

AT^SMONG= <table>[,<period>]

Response(s)

^SMONG: GPRS Monitor Cell Info Table (see: 7.7.1

)

OK

ERROR

+CME ERROR

Reference(s)

SIEMENS

PIN

●

SERIAL

●


The execute command can be used to retrieve GPRS specific cell information directly on request. The cell data will be output only once on a single line.

The write command can be used to retrieve GPRS specific cell information directly on request or automatically every n seconds. To stop the presentation type "at" or "AT".


<table>

(num)

<period>

(num)


If <period> is omitted the cell data will be presented only once on a single line (as if Execute command was issued).

If <period> is given, the cell data will be listed repeatedly on 10 data lines. Every 10 th

data line is followed by the header, simply to repeat the column titles.

1...100

Note

• For compatibility with earlier products and to support legacy applications, often any input character will stop the periodic output of the write command. But since this applies only in certain cases (depending on the settings of chapter

3.7,

it is recommended to always use "at" or "AT".

7.8.1 AT

^

SMONG Cell Info Table

Example output for AT^SMONG :

GPRS Monitor

BCCH G PBCCH PAT MCC MNC NOM TA RAC # Cell #


Page 133


Column

BCCH

G

PBCCH

PAT

MCC

MNC

NOM

TA

RAC

Columns of the cell info table:

Description

ARFCN of BCCH carrier

GPRS supported ("1") or not supported "-"

If PBCCH is present, indication of ARFCN, else "-" or if Frequency Hopping is used "H"

Priority Access Threshold (GSM Rec. 04.08 /10.5.2.37b)

0 Packet access is not allowed in the cell

1

2

Spare, shall be interpreted as "000" (packet access not allowed)

Spare, shall be interpreted as "000" (packet access not allowed)

3

4

Packet access is allowed for priority level 1

Packet access is allowed for priority level 1 to 2

Mobile Country Code

Mobile Network Code

Network Operation Mode (1 ...3)

Timing Advance Value

Routing Area Code (as hexadecimal value)

7.9 AT

^

SALS Alternate Line Service

The

AT^SALS

command is designed to support Alternate Line Service. This allows the subscriber to use two voice numbers on the same SIM card (service requires a dual line SIM card).

Syntax

Test Command

AT^SALS=?

Response(s)

^SALS: (list of supported <^

SALS

>

S

), (list of supported <line> s)

OK

Read Command

AT^SALS?

Response(s)

^SALS: <^SALS> ,< line>

OK

ERROR

Write Command

AT^SALS= <^SALS> [,< line> ]

Reference(s)

Response(s)

OK

ERROR

SIEMENS

PIN

●

SERIAL

●


If switched on with <^

SALS

>=1:

Indicates the line used by an incoming call.


The read command returns the presentation mode of <^

SALS

> and the currently selected <line>. The write command enables or disables the presentation mode of <^

SALS

> and selects the preferred <line>.


<^SALS>

(num) view

Controls the presentation mode of the URC "

^

SALS" which indicates the line number used by an incoming call:


Page 134


0

(&F)

Disables indication of the called line

1 Enables indication of the called line

<line>

(num)

Selects the line to be used for outgoing calls.

[1] ALSLinei

2 ALS Line 2

Notes

• The selected <line> will be saved at non-volatile Flash memory and thus retained after Power Down.

• The <line>

will be reset by AT&F

and

ATZ

and afterwards saved at nonvolatile memory too.

• The <^sals>

will be reset after Power Down as well as by ATZ or

AT&F

.

• If a non ALS SIM is inserted, the <line> will be reset to line 1 as well.

Example

at^sals=1, 1 ring

Line 1 has been selected for outgoing calls. "^SALS" URC is enabled.

You receive a notification that you have an incoming call on line 2.

^SALS: 2

7.10 AT

^

SHOM Display Homezone

Syntax

Test Command

AT^SHOM=?

Response(s)

OK

Exec Command

AT^SHOM

Response(s)

^SHOM: <homezonestate>

OK

ERROR

+CME ERROR: <err>

Reference(s)

SIEMENS

PIN

○

SERIAL

●


TA returns homezone state. Result is valid only, if network registration state

<stat>

is 1 (registered) (see AT+CREG ).

Feature is available only for supported network operators (Viag, One2One,

Orange and LCI) and requires a suitable SIM card. If the homezone feature is not supported by the network operator or SIM card, result is always 0.


<homezonestate>

(num)

0

1

ME is out of Homezone

ME is within the Homezone

7.11 AT

^

SPLM Read the PLMN list

Syntax


Page 135


Test Command

AT^SPLM=?

Response(s)

OK

ERROR

+CME ERROR: <err>

Exec Command

AT^SPLM

Response(s)

^SPLM: <numeric> , long <alpha> [... ]

OK

ERROR

+CME ERROR

Reference(s)

SIEMENS

PIN

●

SERIAL

●


TA returns the list of operator names from the ME. Each operator code

<numeric> that has an alphanumeric equivalent <alpha> in the ME memory is returned.


<numeric>

(str)

Operator in numeric form; GSM location area identification number

<alpha>

(str)

Operator in long alphanumeric format; can contain up to 16 characters

Note

• See also GSM 07.07: AT+COPN , AT+COPS

7.12 AT

^

SPLR Read entry from the preferred operators list

Syntax

Test Command

AT^SPLR=?

Write Command

AT^SPLR= <indexl>[,<index2>]

Response(s)

^SPLR: (list of supported) <indexa> s

OK

ERROR

+CME ERROR: <err>

Response(s)

R: <index1><oper> : <index2><oper>

OK

ERROR

+CME ERROR: <err>

Reference(s)

SIEMENS

PIN

●

SERIAL

●


The test command returns the whole index range supported by the SIM.

The write command returns used entries from the SIM list of preferred operators with <indexa> between <index1> and <index2>. If <index2> is not given, only entry at <index1> is returned.


<indexl>

(num)

Location number to start reading from


Page 136


<index2>

(num)

Location number where to stop reading

<indexa>

(num)

Index range supported by the SIM card (between <index1> and

<index2>)

<oper>

(str)

Operator in numeric form; GSM location area identification number

Note

• See also GSM 07.07: AT+CPOL

7.13 AT

^

SPLW Write an entry to the preferred operators list

Syntax

Test Command

AT^SPLW=?

Write Command

AT^SPLW= <index>[,<oper>]

Response(s)

^SPLW: (list of supported) <index> s

OK

ERROR

+CME ERROR:

Response(s)

OK

ERROR

+CME ERROR: <err>


SIEMENS

●

●


Test command returns the whole index range supported by the SIM

Write command writes an entry to the SIM list of preferred operators at location number <index>. If <index> is given but <oper> is left out, the entry is deleted. If

<oper> is given but <index> is left out,< oper> is inserted in the next free location.


<index>

(num) location number

<oper>

(str)

Operator in numeric format (GSM Location Area Identification number which consists of a 3-digit country code plus a 2- or 3-digit network code).

Note

• See also GSM 07.07: AT+CPOL


Page 137


8 SUPPLEMENTARY SERVICE COMMANDS

The AT commands described in this chapter are related to the Supplementary

Services offered by the GSM network.

8.1 AT+CACM Accumulated call meter (ACM) reset or query

Syntax

Test Command

AT+CACM=?

Read Command

AT+CACM?

Response(s)

OK

Response(s)

+CACM: <acm>

OK

ERROR

+CME ERROR: <err>

Write Command

AT+CACM=[ <passwd>]

Response(s)

OK

ERROR

+CME ERROR: <err>


GSM 07.07

●

●


The read command returns the current ACM value.

The write command resets the Advice of Charge related to the accumulated call meter (ACM) value in SIM file EF(ACM). ACM contains the total number of home units for both the current and preceding calls.


<acm>

(str)

Three bytes of the current ACM value in hexadecimal format (e.g.

"00001E" indicates decimal value 30) 000000 - FFFFFF.

<passwd>

(str)

SIM PIN2

8.2 AT

^

SACM Advice of charge and query of ACM and

ACMmax

Syntax

Test Command

AT^SACM=?

Response(s)

^SACM:(list of supported <n> s)

OK


Page 138


Exec Command

AT^SACM

Response(s)

^SACM: <n>,<acm>,<acmMax>

OK

ERROR

+CME ERROR: <err>

VERSION 1.01

Write Command

AT^SACM= <n>

Response(s)

OK

ERROR

+CME ERROR: <err>

Reference(s)

SIEMENS

PIN

●

SERIAL

●


+CCCM: <ccm>

When activated, an unsolicited result code is sent when the CCM value changes, but not more often than every 10 seconds.


The execute command can be used to query the current mode of the Advice of Charge supplementary service, the SIM values of the accumulated call meter (ACM) and accumulated call meter maximum (ACMmax).

The write command enables or disables the presentation of unsolicited result codes to report the call charges.


<n>

(num)(&W)(&V)

[0]

(&F) suppress unsolicited result code

1 display unsolicited result code

<acm>

(str)(W)

Three bytes of the current ACM value in hexadecimal format FFFFFF (e.g.

"00001E" indicates decimal value 30) 000000-

<acnmax>

(str)(SV)

Three bytes of the max. ACM value in hexadecimal format disable

ACMmax feature 000001-FFFFFF (e.g. "00001E" indicates decimal value

30) 000000

<ccm>

(str)

Three bytes of the current CCM value in hexadecimal format (e.g.

"00001E" indicates decimal value 30); bytes are coded in the same way as ACMmax value in the SIM 000000-FFFFFF

Notes

• When you power down or reset the ME with AT+CFUN =1,1

the URC presentation mode will be reset to its default. To benefit from the URC it is recommended to have the setting included in the user profile saved with

AT&W ,

or to select <n>=1 every time you reboot the ME.

• See also GSM07.07:

AT+CACM, AT+CAMM, AT+CAOC.


Page 139


8.3 AT+CAMM Accumulated call meter maximum

(ACMmax) set or query

Syntax

Test Command

AT+CAMM=?

Response(s)

OK

VERSION 1.01

Read Command

AT+CAMM?

Write Command

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

Response(s)

+CAMM: <acmmax>

OK

ERROR

+CME ERROR: <err>

Response(s)

OK

ERROR

+CME ERROR: <err>


GSM 07.07

●

●


The read command returns the current ACMmax value.

The write command sets the Advice of Charge related to the accumulated call meter maximum value in SIM file EF (ACMmax). ACMmax contains the maximum number of home units allowed to be consumed by the subscriber.


<acmmax>

(str)

Three bytes of the max. ACM value in hexadecimal format (e.g. "00001E" indicates decimal value 30) 000000 disable ACMmax feature 000001-

FFFFFF.

<passwd>

(str)

SIMPIN2

8.4 AT+CAOC Advice of Charge information

Syntax

Test Command

AT+CAOC=?

Read Command

AT+CAOC?

Response(s)

+CAOC: (list of supported <mode> s)

OK

Response(s)

+CAOC: <mode>

OK

Exec Command

AT+CAOC

Response(s)

ERROR

+CME ERROR: <err> If <mode> =0, TA returns the current call meter value:

+CAOC: <ccm>

OK


Page 140


Write Command

AT+CAOC= [<mode>]

Response(s)

ERROR

+CME ERROR: <err>

If <mode> =0, TA returns the current call meter value.

OK


GSM 07.07

●

●


Execute command returns the current call meter value.

The write command sets the Advice of Charge supplementary service function mode.


<mode>

(num)(&V)

<ccm>

(str)

Three bytes of the current CCM value in hexadecimal format (e.g.

"00001E" indicates decimal value 30); bytes are similarly coded as

ACMmax value in the SIM 000000-FFFFFF.

8.5 AT+CCUG Closed User Group

Syntax

Test Command

AT+CCUG=?

Read Command

AT+CCUG?

Write Command

AT+CCUG= [[<n>][,<index>][,<info>]]

Response(s)

+CCUG: list of supported <n> , range of supported <index> , range of supported

<info>

OK

ERROR

+CME ERROR

Response(s)

+CCUG: <n> ,< index> ,< info>

OK

ERROR

+CME ERROR

Response(s)

OK

ERROR

+CME ERROR


GSM 07.07, GSM 02.85, GSM 03.85,

GSM 04.85

● ●



The Read command returns if the Explicit CUG invocation is activated (in parameter <n> ), which CUG <index> is chosen, and if Preferential Group or

Outgoing Access is suppressed (in parameter <info> ).

The write command serves to activate or deactivate the explicit CUG invocation, to set the desired index, and to specify if Preferential Group or

Outgoing Access shall be suppressed.


Page 141



<n>

(num) explicit CUG invocation options

0

(D)

Deactivate explicit CUG invocation

1 Activate explicit CUG invocation

<index>

(num)

0-9 explicit selection of CUG index

10

(D)

No index (preferred CUG taken from subscriber data)

<info>


0

(D) no information

1 suppress outgoing access

3 Suppress preferential CUG and Outgoing Access.

Notes

• The active settings for omitted parameters are retained without changes.

• Explicit CUG invocation means that at each call setup, CUG information is added to the called number.

• Upon delivery, settings are predefined with

<n>=0,

<index>=10,

<info>=0.

• These delivery defaults cannot be recalled automatically.

• When starting a call with

ATD ,

Parameter 'G' or 'g' of command

ATD

will have no effect if the option selected for this single call is identical to the option already selected with

AT+CCUG .

• Current settings are saved in the ME automatically.

• ATZ or AT&F

do not influence the current settings.

• Some combinations of parameters may lead to rejection of CUG calls by the network. For more information, please consult GSM 04.85

8.6 AT+CCFC Call forwarding number and conditions control

Syntax

Test Command

AT+CCFC=?

Write Command

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

Response(s)

+CCFC: (list/range of supported <reason> s)

OK


OK if <mode> = 2,< reason> is not equal 2 and command successful:

+ CCFC: <status> ,< class> [,< number> ,< type> ]

OK if <mode> = 2,< reason> = 2 and command successful:

+ CCFC: <status> ,< class> [,< number> ,< type> ,< time> ]

OK


+CME ERROR


Page 142



GSM 07.07, GSM 02.04, GSM 02.82,

GSM 03.82, GSM 04.82

○ ●



The write command controls the call forwarding supplementary service.

Registration, erasure, activation, deac-tivation and status query are supported.


<reason>

(num) reason for call forwarding

0 unconditional

4

5 all call forwarding (includes reasons 0,1,2 and 3) all conditional call forwarding (includes reasons 1, 2 and 3)

<mode>

(num) network operation to be performed for Supplementary service "call forwarding"

0

1 disable call forwarding (disable service) enable call forwarding (enable service)

2 query status of call forwarding (query service status)

3 register and activate call forwarding (register service)

4 erase and deactivate call forwarding (erase service)

<number>

(str) string type phone number of forwarding address in format specified by

<type>. If you select <mode> = 3, the phone <number> will be registered in the network. This allows you to disable/enable CF to the same destination without the need to enter the phone number once again.

Depending on the services offered by the provider the registration may be mandatory before CF can be used. The number remains registered in the network until you register another number or erase it using <mode> =

4.

<type>

(num) type of address octect string includes international access code character'+'

<class>

(num)

129 otherwise integer or sum of integers each representing a class of information, i.e. a bearer service, telecommunication service or bearer service group as defined in "GSM 02.04"

1 voice

2 data


Page 143


<time>

(num)

<class> 2 (data) comprises all those <class> values between 16 and 128, that are supported both by the network and the MS. This means, a setting made for

<class> 2 applies to all remaining data classes (if supported). In addition, you can assign a different setting to a specific class. For example, you can activate Call Forwarding for all data classes, but deactivate it for a specific data class.

4 fax

[7] voice, data and fax (1+2+4)

8 SMS

16

32

64

128 dedicated packet access dedicated PAD access

1...[7]...255 combination of some of the above classes. For example, the default setting 7 represents the sum of the integers 1, 2 and 4 (CF for voice, data and fax).

The value 255 covers all classes. If the <class> parameter is omitted, the default value 7 is used. multiple of 5 sec. (only for <reason> =no reply)

<status>

(num)

0

1

Call Forwarding not active

Call Forwarding active

Notes

• You can register, disable, enable and erase <reason> 4 and 5 as described above. However, querying the status of <reason>

4 and 5 with AT+CCFC

will result in an error ("CME error: Operation not supported"). As an

alternative, you may use the ATD command followed by *'# codes to

check the status of these two reasons. See List of *# Codes for a complete list of *# GSM codes. See also examples below.

• Most networks will not permit registration of new parameters for conditional call forwarding (reasons 1,2,3,5) while unconditional call forwarding is enabled.

• The

AT+CCFC command offers a broad range of call forwarding options

according to the GSM specifications. However, when you attempt to set a call forwarding option which is not provisioned or not yet subscribed to, the setting will not take effect regardless of the response returned. The responses in these cases vary with the network (for example "OK",

"Operation not allowed", "Operation not supported" etc.). To make sure check the call forwarding status with <mode>=2.

• Some networks may choose to have certain call forwarding conditions permanently enabled (e.g. forwarding to a mailbox if the mobile is not reachable). In this case, erasure or deactivation of call forwarding for these conditions will not be successful, even if the CCFC request is answered with response "OK".

• The command has been implemented with the full set of <class> parameters according to GSM 07.07. For actual applicability of SS "call


Page 144

TANGO55/56 AT COMMAND SET VERSION 1.01 forwarding" to a specific service or service group (a specific <class> value) please consult table A.1 of GSM 02.04.

• There is currently no release of GSM standard "GSM 02.04", in which the

"Call Forwarding" Supplementary Service is defined as applicable to SMS services.

Example

Please note that when you configure or query call forwarding without specifying any classes, the settings will refer to classes 1, 2 and 4 only

(=default). The handling of classes is equivalent to AT+CLCK .

• To register the destination number for unconditional call forwarding

(CFU): at+ccfc=0,3,"+4 93012345678",145

OK

The destination number will be registered for voice, data and fax services (default <class> 7).

In most networks, the registration will also cause call forwarding to be activated for these <class> values.

• To query the status of CFU without specifying <class>: at+ccfc=0,2

+CCFC: 1,1,"+493012345678",145

+CCFC: 1,2,"+493012345678",145

+CCFC: 1,4,"+493012345678",145

OK

• To deactivate CFU without specifying <class>: at+ccfc=0,0

OK

To check whether CFU was successfully deactivated (note that the destination number remains registered in the network when you disable

CFU): at+ccfc=0,2

+CCFC: 0,1,"+493012345678",145

+CCFC: 0,2,"+493012345678",145

+CCFC: 0,4,"+493012345678",145

OK

• To erase the registered CFU destination number: at+ccfc=0,4

OK

Now, when you check the status, no destination number will be indicated: at+ccfc=0,2

+CCFC: 0,1

+CCFC: 0,2

+CCFC: 0,4

OK

To query the status of CFU for all classes: at + ccfc = 0,2,, ,255

+CCFC:0,1


Page 145


+CCFC:0,2

+CCFC:0,4

+CCFC:0,8

+CCFC:0,16

+CCFC:0,32

+CCFC:0,64

+CCFC:0,128

OK

• <reason> 4 or 5 cannot be used to query the status of all call forwarding reasons (see also notes above): at+ccfc=4,2

+CME error: operation not supported at+ccfc=5,2

+CME error: operation not supported

8.7 AT+CCWA Call Waiting

This command controls the "Call Waiting" supplementary service according to GSM

02.83. Activation, deactiva-tion and status query are supported.

Syntax

Test Command

AT+CCWA=?

Read Command

AT+CCWA?

Write Command

AT+CCWA=[[ <n> ][,< mode> ][,< class> ]]

Response(s)

+ccwA:(list of supported <n> s)

OK

Response(s)

+CCWA: <n>

OK



+CCWA: <status> , <class> [+CCWA: <status> ,< class> ] [+CCWA: ...]

OK


+CME ERROR


GSM 07.07, GSM 02.04, GSM 02.83,

GSM 03.83, GSM 04.83

● ●


URC1

Indication of a call that is currently waiting and can be accepted.

+CCWA: <calling number>,<type of number>,<class>,<CLI validity>

If <n>=1 and the call waiting supplementary service is enabled in the network, URC "+

CCWA

" indicates a waiting call to the TE. It appears while the waiting call is still ringing.

URC 2

Indication of a call that has been waiting.

If <n> =1 and the call waiting supplementary service is enabled in the network, this URC indicates that a waiting call rang when the ME was in


Page 146

TANGO55/56 AT COMMAND SET VERSION 1.01 online mode during a CSD call, but the calling party hung up before the

ME went back to command mode.


The test command returns the list of supported " <n> "s.

The read command returns the current value of parameter <n>.

The write command controls the call waiting supplementary service.

Activation, deactivation and status query are supported.


<n>

(num)

Switch URCs "+

CCWA

" and "^

SCWA

" for call waiting on/off

0 Disable display of URCs "+

CCWA

" and

1 Enable display of URCs "+

CCWA

" and "

<mode>

(num)

Network operation to be performed for Supplementary service call waiting

0 Disable call waiting (disable service)

1 Enable call waiting (enable service)

2 Query status of call waiting (query service status)

<class>

(num)

Integer or sum of integers each representing a class of information, i.e. a bearer service, telecommunication service or bearer service group as defined in "GSM 02.04".

In the write command, parameter <class> specifies the class of the active call during which an incoming call of any class is to be regarded as a waiting call.

In URC "+CCWA: <calling number>,<type of number>,<class>,<CLI validity>", parameter <class> specifies the class of the waiting call.

1 voice

2 data

<class> 2 (data) comprises all those <class> values between 16 and 128, that are supported both by the network and the MS. This means, a setting made for

<class> 2 applies to all remaining data classes (if supported). In addition, you can assign a different setting to a specific class. For example, you can activate call waiting for all data classes, but deactivate it for a specific data class.

4 fax

8 SMS

16 data sync

32 data async

64 dedicated packet access

128 dedicated PAD access

1...[7]...255 Combination of some of the above classes. For example, the default setting 7 represents the sum of the integers 1, 2 and 4 (CF for voice, data and fax).

The value 255 covers all classes. If parameter "class" is omitted, the default value 7 is used.


Page 147


<status>

(num)

0 Call waiting service is not active

1 Call waiting service is active

<calling number>

(str)

Phone number of waiting caller in the format specified by parameter

< type of number>.

<type of number>

(num)

Type of address octet in integer format (refer to GSM 04.08, subclause

10.5.4.7)

145 <calling number> includes international access code character'+'

129 Otherwise

<CLIvalidity>

(num)

1

2

CLI has been withheld

CLI is not available

Notes

• If the active call is a CSD call, and a waiting call is received, then the ME produces a BREAK while still in online mode, and displays

- the +CCWA URC (as above) when the ME goes back to command mode while the waiting call is still active and can be accepted; the SCWA URC (as above) when the ME goes back to command mode after the waiting call has ended.

the command, it is possible to establish a multiparty

call or to set the active voice call on hold and then accept a waiting voice call (not possible with fax and data call). See also

AT+CHLD

• Users should be aware that if call waiting is activated ( <mode>=1 ), the presentation of URCs needs to be enabled, too ( <n>=1 ).

• Otherwise, on the one hand, awaiting caller would be kept waiting due to lack of BUSY signals, while, on the other hand, the waiting call would not be indicated to the called party.

• The

AT+CCWA command offers a broad range of options according to the

GSM specifications. However, when you attempt to enable call waiting for a <class> for which the service is not provisioned or not supported , the setting will not take effect regardless of the response returned. The responses in these cases vary with the network (for example "OK",

"Operation not allowed", "Operation not supported" etc.). To make sure check the current call waiting settings with <mode>=2.

• The

AT+CCWA command has been implemented with the full set of

<class> parameters according to GSM 07.07. For actual applicability of SS call waiting to a specific service or service group (a specific <class> value) please consult table A.1 of GSM 02.04.

• Despite the specifications stated in GSM 02.04 call waiting is not handled uniformly among all networks: GSM 02.04, Annex A, provides the following specification:

• "The applicability of call waiting refers to the telecommunication service of the active call and not of the waiting call. The incoming, waiting, call may be of any kind." Nevertheless, networks do differ on the actual implementation of the service. For example, the activation of call waiting


Page 148

TANGO55/56 AT COMMAND SET VERSION 1.01 for <class> 4, "fax", causes some networks to send a call waiting indication if a call "of any kind" comes in during an active fax call, but others may

(with the same settings active) indicate a waiting fax call during any kind of active call. Thus, the only reliable way to receive or prevent a call waiting indication under any circumstances and in any network, is to activate or deactivate call waiting for all tele- and bearer services ( <class>

255).

Examples

EXAMPLE 1

Parameter <n> at+ccwa=1

OK

To enable the presentation of the URC

EXAMPLE 2

Parameter <mode> at+ccwa=,1 To activate the supplementary service in the network for voice, data, and fax calls (default classes). Note that parameter <n> is left out. In this case, the current value of <n> will be retained.

OK at+ccwa=,2 at+ccwa=1,1 at+ccwa=1,2 at+ccwa=1,4

OK

To query the network status of call waiting for default classes.

Call Waiting is activated during voice calls.

Call Waiting is activated during data calls.

Call Waiting is activated during fax calls.

EXAMPLE 3

Parameter <class>

AT+CCWA=,0,1 To deactivate call waiting for voice calls.

OK

8.8 AT+CHLD Call Hold and Multiparty

Syntax

Test Command

AT+CHLD=?

Write Command

AT+CHLD=[ <n> ]

Response(s)

+CHLD: (list of supported <n> s)

OK

Response(s)

OK

ERROR

+CME ERROR: <err>


GSM 07.07

● ●


TA controls the Supplementary Services Call Hold and Multiparty. Calls can be put on hold, recovered, released, and added to a conversation.

Like for all Supplementary Services, the availability and detailed functionality of

Call Hold and Multiparty services depends on the configuration of the GSM


Page 149

TANGO55/56 AT COMMAND SET VERSION 1.01 network. The TANGO55/56 can only request the service, but the network decides whether and how the request will be answered.


<n>

(num)

0 Release all held calls or set User Determined User Busy (UDUB) for a waiting call:

• If a call is waiting, release the waiting call. The calling party will receive a "BUSY" indication (Supplementary Service User

Determined User Busy "UDUB")

• Otherwise, terminate all held calls (if any).

1 Terminate all active calls (if any) and accept "the other call" as the active call:

• If a call is waiting, the waiting call will be accepted.

• Otherwise, if a held call is present, the held call becomes active.

1X Terminate a specific call X (X= 1-7). The call may be active, held or waiting. The remote party of the terminated call will receive a "NO

CARRIER" indication. Parameter X is the call number <idx> of the targeted call in the list of current calls available with AT command

AT+CLCC .

2 Place all active calls on hold (if any) and accept "the other call" as the active call:

• If a call is waiting, the waiting call will be accepted.

• Otherwise, if a held call is present, the held call becomes active.

2X Place all active calls except call X (X= 1-7) on hold. Parameter X is the call number <idx> of the targeted call in the list of current calls

available with AT command AT+CLCC .

3 Add a held call to the active calls in order to set up a conference

(multiparty) call.

Notes

• The

AT+CHLD

command offers a broad range of options according to the

GSM specifications. However, if you attempt to invoke an option which is not provisioned by the network, or not subscribed to, invocation of this option will fail. The responses in these cases may vary with the network (for example "Operation not allowed", "Operation not supported" etc.).

• This Supplementary Service is only applicable to Teleservice 11 (Speech telephony), that is, voice calls can be put on hold, while data or fax calls

cannot. For example, with AT+CHLD =2

you can simultaneously place a voice call on hold and accept another waiting voice call. But it is possible to place a voice call on hold in order to accept a waiting data of fax call, and afterwards recover the voice call. In this case, the only difference over speech telephony is that the data or fax call needs to be manually accepted via

ATA (see example below).

• In conflict situations, e.g. when a waiting call comes while there are already held calls, the above procedures apply to the waiting call only. For example,<n>=0 rejects the waiting call, but does not affect the held calls.

• See also the

AT+CCWA

command for details on how to display waiting calls.

Example

^

SYSSTART


Page 150

TANGO55/56 AT COMMAND SET VERSION 1.01 at+cpin="9999"

OK

+CREG: 2

+CREG: 1,"0145","0016" at+ccwa=1,1,1

The mobile is now registered.

You activate the indication of waiting calls during voice calls.

OK atd"1234567"; You make a voice call.

OK

+CCWA: "+491791292364",145,32,,0 You receive a URC indicating a waiting data call. at+chld=2

RING

OK

RING

RING

You put the voice call on hold.

You now receive the RING of the data call.

the

CONNECT 9600/RLP hello

OK

With

at+clcc You interrogate the status of all established calls.

+CLCC: 1,0,1,0,0, "03038639268",129

+ CLCC: 2,1,0,1,0,"+491791292364",145

OK at+chld=1 The active data call is terminated and the held voice call becomes active.

OK at+clcc

+CLCC: 1,0,0,0,0, "03038639268",129

OK

8.9 AT+CLIP Calling line identification presentation

Syntax

Test Command

AT+CLIP=?

Read Command

AT+CLIP?

Response(s)

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

OK

Response(s)

+ CLIP: <n>,<m>

OK

ERROR

+CME ERROR: <err>


Page 151


Write Command

AT+CLIP= <n>

Response(s)

OK

ERROR

+CME ERROR: <err>


GSM 07.07

● ●


URC1

Voice call response format:

+CLIP: <number>,<type>, , , ,< CLI validity>

URC2

Data/FAX call response format:

+CLIP: <number>,<type>

When CLIP is enabled at the TE (and is permitted by the calling subscriber), an unsolicited result code is returned after every RING (or

+CRING: <type>) at a mobile terminating call.


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.

Write command enables or disables the presentation of the CLI at the TE. It has no effect on the execution of the supplementary service CLIP in the network.


<n>

(num)(&W)(&V)

[0]

1

(&F)

<m>

(num)(&V) suppress unsolicited result codes display unsolicited result codes

0 CLIP not provisioned

1 CLIP

2 unknown

<number>

(str) string type phone number of calling address in format specified by

<type>

<type>

(num) type of address octet in integer format; 145 when dialling string includes international access code character "+", otherwise 129.

<CLIvalidity>

( num)

1 CLI has been withheld by the originator.

2 CLI is not available due to interworking problems or limitations of originating network. <number> shall be an empty string ("") and

<type> value will not be significant.

When CLI is not available ( <

CLI validity>=2) ,< number> shall be an empty string

("") and <type> value will not be significant. Nevertheless, TA shall return the


Page 152

TANGO55/56 AT COMMAND SET VERSION 1.01 recommended value 128 for <type> (TON/NPI unknown in accordance with

GSM 04.08 subclause 10.5.4.7).

When CLI has been withheld by the originator, (<

CLI validity>=1) and the CLIP is provisioned with the "override category" option (refer GSM 02.81 and GSM

03.81),< number> and <type> is provided. Otherwise, TA shall return the same setting for <number> and <type> as if the CLI was not available.

8.10 AT+CLIR Calling line identification restriction

Syntax

Test Command

AT+CLIR=?

Response(s)

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

OK

Read Command

AT+CLIR?

Response(s)

+ CLIR <n> ,< m>

OK

ERROR

+CME ERROR: <err>

Write Command

AT+CLIR=[ <n> ]

Response(s)

OK

ERROR

+CME ERROR: <err>


GSM 07.07

◑ ●


This command refers to the GSM supplementary service CLIR (Calling Line

Identification Restriction).


<n>

(num)

Parameter shows the settings for outgoing calls:

[0]

(P)

Presentation indicator is used according to the subscription of the CLIR service

2

3

LIR invocation

LIR suppression

<m>

(num)

Parameter shows the subscriber CLIR service status in the network:

0

1

2

3

4

IR not provisioned

IR provisioned in permanent mode known (e.g. no network, etc.)

IR temporary mode presentation restricted

IR temporary mode presentation allowed

Note

• The settings made with

AT+CLIR =1

or

AT+CLIR =2

are used for all outgoing

calls until the ME is switched off or AT+CLIR =0

is used.


Page 153


8.11 AT+CPUC Price per unit and currency table

Syntax

Test Command

AT+CPUC=?

Response(s)

OK

VERSION 1.01

Read Command

AT+CPUC?

Response(s)

+ CPUC: <currency> ,< ppu>

OK

ERROR

+CME ERROR: <err>

Write Command

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

Response(s)

OK

ERROR

+CME ERROR: <err>


GSM 07.07

● ●


Read command returns the current parameters of PUC.

Write command sets the parameters of Advice of Charge related price per unit and currency table. SIM PIN2 is usually required to set the parameters.


<currency>

(str)(+CSCS)

Three-character currency code (e.g. "GBP", "EUR"). If the currency name is longer than three characters, all characters will be cut off after the third position. Before they are written to the SIM card, these characters are converted to the standard GSM alphabet.

<ppu>

(str)

Price per unit; dot is used as a decimal separator (e.g. "2.66"). The length is limited to 20 characters. If the string length is exceeded, the command is terminated with an error. This string may only contain digits and a dot.

Leading zeros are removed from the string. The minimum and maximum value are determined by the structure of the SIM-PUCT file. The maximum price per unit value is 999 999 999.00. When successfully entered, this value is rounded to maximum accuracy. Note: Due to storage in mantisse (range 0-4095) and exponent (-7 to 7) it is possible that rounding errors occur.

<passwd>

(str)

SIM PIN2. String parameter which can contain any combination of characters. The maximum string length is limited to 8 characters. If this value is exceeded, the command terminates with an error message. If the PIN2 is incorrect, a CME error (+CME ERROR: incorrect password) is output.

Example

To change currency and/or price per unit you have two ways:

You can enter PIN2 along with the

AT+CPUC command:

AT

+

CPUC

="EUR","0.10","8888" (where "8888" = PIN2)


Page 154


OK

Alternatively, you can first use the

AT+CPIN2

command to enter PIN2. When

you execute the AT+CPUC

command, subsequently, take into account that

PIN2 authentication expires after 300 ms (see notes in AT+CPIN2 ).

AT+CPUC="EUR","0.10"

OK

successful

AT+CPUC="EUR","0.10"

+CME ERROR: SIM PIN2 required Attempt not successful. PIN2 authentication has expired.

8.12 AT+CSSN Supplementary service notifications

Syntax

Test Command

AT+CSSN=?

Response(s)

+CSSN: (list of supported <n> s), (list of supported <m> s)

OK

Read Command

AT+CSSN?

Write Command

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

Response(s)

+ CSSN: <n> ,< m>

OK

Response(s)

OK

ERROR

+CME ERROR


GSM 07.07

● ●


URC 1

+CSSI: <code 1>

When <n>=1 and a supplementary service notification is received after a mobile originated call setup, intermediate result code "+cssi": <code 1> is sent to TE before any other MO call setup result codes

URC 2

+CSSU: <code 2>

When <m>=1 and a supplementary service notification is received during a mobile terminated call setup or during a call, unsolicited result code

"+cssu": <code 2> is sent to TE.


The write command enables or disables the presentation of URCs for supplementary services.


<n>

(num)

0

(&F)

Suppress URCs

1 Activate URCs

<m>

(num)

0

(&F)

Suppress URCs


Page 155


1 Activate URCs

<code l>

(num)

3 Waiting call is pending

<code 2>

(num)

0

5

The incoming call is a forwarded call.

Held call was terminated

Note

• The URCs will be displayed only if the call concerned is a voice call.

8.13 AT+CUSD Supplementary service notifications

This command allows control of the Unstructured Supplementary Service Data (USSD) according to GSM 02.90. Both network and mobile initiated operations are supported.

Syntax

Test Command

AT+CUSD=?

Response(s)

+CUSD: (list of supported <n> s)

OK

Read Command

AT+CUSD?

Write Command

AT+CUSD= <n> [,< str> [,< dcs> ]]

Response(s)

+CUSD: <n>

OK

Response(s)

OK

+CME ERROR


GSM 07.07, GSM 02.90, GSM 03.90,

GSM 04.90

● ●


+ CUSD: <m> [ <str>[<dcs>] ]

URC "+CUSD" indicates an USSD response from the network, or network initiated operation


The read command returns the current <n> value

Write command parameter <n> is used to disable/enable the presentation of an unsolicited result code (USSD response from the network, or network initiated operation) "+

CUSD

: <m>[<str>[<dcs>]]" to the TE.

When <str> is given, a mobile initiated USSD string or a response USSD string to a network initiated operation is sent to the network. The response USSD string from the network is returned in a subsequent unsolicited result code "+

CUSD

".

The interaction of this command with other commands based on other GSM supplementary services is described in the GSM standard.


<n>

(num)

0

(&F)

1

Disable the result code presentation in the TA

Enable the result code presentation in the TA


Page 156


2

<str>

(str)

Cancel session (not applicable to read command response)

Stringtype USSD-string (when <str> parameter is not given, network is not interrogated).

If <dcs> indicates that GSM 03.38 default alphabet is used TA converts

GSM alphabet into current TE character set according to rules of GSM

07.05 Annex A.

<dcs>

(num)

GSM 03.38 Cell Broadcast Data Coding Scheme in integer format

(default 15)

<m>

(num)

0

1

2

No further user action required (network initiated USSD-Notify, or no further information needed after mobile initiated operation)

Further user action required (network initiated USSD-Request, or further information needed after mobile initiated operation).

If <m>=1 , then the URC ends with ">" to prompt the user for input. The user action is finished with <

CTRL

-

Z

> or aborted with

<

ESC

> .

USSD terminated by network.

Notes

• For the write command, only <dcs>= 15 is supported.

• When a USSD string is sent via

ATD ,

a

" AT+CUSD =1"

is executed implicitly.


Page 157


9 GPRS COMMANDS

This chapter describes AT commands that a TE (Terminal Equipment, e.g. an application running on a controlling PC) may use to control the TANGO55/56 acting as GPRS Mobile Termination (MT). Please use chapter "Using GPRS

AT commands

(Examples) " as a first guidance.

9.1 AT+CGACT PDP context activate or deactivate

Syntax

Test Command

AT+CGACT=?

Read Command

AT+CGACT?

Write Command

AT+CGACT=[ <state> [,< cid> [,< cid> [,... ]]]]

Response(s)

+CGACT: (list of supported <state>s)

OK

Response(s)

+ CGACT: <cid>,<state>

[+CGACT: <cid>,<state> ]

OK

Response(s)

OK

ERROR

+CME ERROR


GSM 07.07

● ●


The test command is used for requesting information on the supported PDP context activation states. The read command returns the current activation states for all the defined PDP contexts.

The write command is used to activate or deactivate the specified PDP context(s). After the command has completed, the MT remains in V.25ter command state. If any PDP context is already in the requested state, the state for that context remains unchanged. If the MT is not GPRS attached when the activation form of the command is executed, the MT first performs a GPRS attach and them attempts to activate the specified contexts. If no <cid>s are specified the activation/deactivation form of the command activates/deactivates all defined contexts. If the MT is not able to activate a context because of a failed attach, command returns with "ERROR" or with

"+CME ERROR: unknown" after 385 seconds (timer T3310 expired).

If the MT is attached but is not able to activate a context for more than 160 seconds (timer T3380 expired), command returns with "ERROR" or with "+CME

ERROR: unspecified GPRS error. In this case

AT+CEER returns "+CEER:51,3,0".


<state>

(num)

Indicates the state of PDP context activation.

0 detached

[1] attached


Page 158


<cid>

(num)

PDP Context Identifier is a numeric parameter which specifies a particular PDP context definition. The parameter is local to the TE-MT interface and is used in other PDP context-related commands.

1...2

Notes

• ATH will deactivate any PDP context.

• If the MT is in dedicated mode, write command returns with "+CME ERROR: operation temporary not allowed.

• A maximum of 2 contexts can be activated at the same time, no matter on which interface. Trying to activate more than 2 contexts will cause

"+CME ERROR: operation temporary not allowed. Note that, depending on the provider, the number of activated contexts may be further restricted. In such cases "+CME ERROR: unspecified GPRS error" will be returned and

AT+CEER

returns "+CEER: 50,26,0".

Remember that contexts may be activated implicitly by using the

ATD*98#

or ATD*99# GPRS compatibility commands without specifying a

<cid>.

9.2 AT+CGANS Manual response to a network request for

PDP context activation

Syntax

Test Command

AT+CGANS=?

Response(s)

+CGANS: (list of supported <response>s ), (list of supported <L2P>s )

OK

Write Command

AT+ CGANS=[ <response> [,< L2P> [,< cid> ]]]

Response(s)

OK

ERROR

+CME ERROR


GSM 07.07

● ●


The write command requests the MT to respond to a network request for GPRS

PDP context activation which has been signaled to the TE by the RING or

CRING unsolicited result code. The <response> parameter allows the TE to accept or reject the request.


<response>

(num)

[0] the request is rejected and the MT returns OK to the TE

1 accept and request that the PDP context be activated

<L2P>

(str) a string parameter which indicates the layer 2 protocol to be used

(see AT+CGDATA command)

<cid>

(num)


Page 159

TANGO55/56 AT COMMAND SET VERSION 1.01 a numeric parameter which specifies a particular PDP context

definition (see AT+CGDCONT command).

Note

• If <response> is 1, the following procedure is followed by the MT:

• If the <L2P> parameter value is unacceptable to the MT, the MT will return an ERROR or +CME ERROR response. Otherwise, the MT issues the intermediate result code CONNECT and enters V.25ter online data state.

• A <cid> may be specified for use in the context activation request.

During the PDP startup procedure the MT has the PDP type and the PDP address provided by the network in the Request PDP context activation message. If this is in conflict with the information provided by a specified

<cid>, the command will fail. There will be no conflict, if the PDP type matches exactly and the PDP address given by the context definition for

<cid> is empty or matches exactly with the address specified with the network PDP context activation message.

The context will be activated using the values for PDP type and address provided by the network, together with all other information found in the

PDP context definition. An APN may or may not be required, depending on the application.

If no <cid> is given or if there is no matching context definition, the MT will attempt to activate the context using the values for PDP type and address provided by the network. The other parameters will be set to their default

values (see AT+CGDCONT ).

If activation is successful, data transfer may proceed.

After data transfer is completed, and the layer 2 protocol termination procedure has completed successfully, the V.25ter command state is reentered and the MT returns the final result code OK. In the event of an erroneous termination or a failure to start up, the V.25ter command state is reentered and the MT returns the final result code NO CARRIER, or if enabled, +CME ERROR. Attach, activate and other errors may be

reported. It is also an error to issue the AT+CGANS command when there is

no pending network request. The command may be used in both normal and modem compatibility modes.

9.3 AT+CGATT GPRS attach or detach

Syntax

Test Command

AT+CGATT=?

Response(s)

+CGATT: (list of supported <state>s )

OK

Read Command

AT+CGATT?

Write Command

AT+CGATT=[ <state> ]

Response(s)

+CGATT: <state>

OK

Response(s)

OK

ERROR

+CME ERROR



Page 160


GSM 07.07

● ●


The test command is used for requesting information on the supported GPRS service states. The read command returns the current GPRS service state.

The write command is used to attach the MT to, or detach the MT from the

GPRS service. After the command has completed, the MT remains in V.25ter command state. If the MT is already in the requested state, the command is ignored and the OK response is returned. Any active PDP contexts will be automatically deactivated when the attachment state changes to detached.

If the MT is not able to attach for more than 5 minutes, command returns with

"ERROR" or "+CME ERROR: unknown", but MT is still trying to attach.

If the MT is not able to detach for more than 1 minute, command returns with

"ERROR" or "+CME ERROR: unknown", but MT is still trying to detach. If an attach is issued during a running detach, command returns with "ERROR" or "+CME

ERROR: unspecified GPRS error.


<state>

(num)

Indicates the state of GPRS attachement .

0

(P) detached

[1] attached

Notes

• If the MT is in dedicated mode, write command returns with "+CME ERROR: operation temporary not allowed.

• When the module is GPRS attached and a PLMN reselection occurs to a non-GPRS capable network or to a network where the SIM is not subscribed to for using GPRS, the resulting GMM (GPRS mobility management) state according to GSM 24.008 is REGISTERED/NO CELL, meaning that the read command will still show <state>=1.

9.4 AT+CGAUTO Automatic response to a network request for PDP context activation

Syntax

Test Command

AT+CGAUTO=?

Read Command

AT+CGAUTO?

Write Command

AT+CGAUTO=[ <n> ]

Reference(s)

GSM 07.07


Response(s)

+

CGAUTO

: (list of supported <n> s)

OK

Response(s)

+CGAUTO: <n>

OK

Response(s)

OK

ERROR

+CME ERROR

PIN

●

SERIAL

●


Page 161


The test command returns the values of <n> supported by the MT as a compound value.

The write command disables or enables an automatic positive response (autoanswer) to the receipt of a Request PDP Context Activation message from the network. It also provides control over the use of the V.25ter basic commands

ATSO

,

ATA and

ATH for handling network requests for PDP context activation.


<n>

(num)

0

1

Disable automatic response for network requests for

GPRS PDP context activation. GPRS network requests

are manually accepted or rejected by the AT+CGANS

command.

Enable automatic response for network requests for

GPRS PDP context activation. GPRS requests are automatically accepted according to the description below.

3

(P)

Modem compatibility mode. The automatic acceptance of both GPRS and incoming CSD calls is controlled by the

ATS0 command. Manual control uses

the

ATA

and

ATH

commands, respectively, to accept or reject GPRS network requests or incoming CSD calls.

Notes

• It is allowed to have different AT+CGAUTO settings on different interfaces.

• When the AT+CGAUTO =0

command is received, the MT will not perform a

GPRS detach if it is attached. Subsequently, when the MT announces a network request for PDP context activation by issuing the URC RING or

CRING, the TE may manually accept or reject the request by issuing the

AT+CGANS

command or may simply ignore the network request.

• When the

AT+CGAUTO =1

command is received, the MT will attempt to perform a GPRS attach if it is not yet attached. Failure will result in ERROR or, if enabled +CME ERROR being returned to the TE. Subsequently, the MT announces a network request for PDP context activation by issuing the

URC RING to the TE, followed by the intermediate result code CONNECT.

The MT then enters V.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.

• If a GPRS attach will be initiated by this command and the MT is not able to attach for more than 385 seconds (timer T3310 expired), command returns with "ERROR" or "+CME ERROR: unknown", but MT is still trying to attach and the requested automatic mode <n> is in use.

• If a network request for PDP context activation is answered automatically and if another AT command is issued at the same time on the same interface, then this AT command is not executed. Any response belongs to the automatic context activation procedure. If the AT command which caused the collision was a circuit switched data call, the CONNECT response does not belong to this data call but to the GPRS. This can be detected if

ATX is not set to 0. CS data call will issue CONNECT

<text> , GPRS will issue CONNECT only.

9.5 AT+CGDATA Enter data state

Syntax


Page 162


Test Command

AT+CGDATA=?

Write Command

AT+CGDATA=[ <L2P> [,< cid> [,< cid> [,... ]]]]

Response(s)

+CGDATA: (list of supported <L2P>s )

OK

Response(s)

CONNECT

NO CARRIER

ERROR

+CME ERROR

VERSION 1.01


GSM 07.07

● ●


The test command is used for requesting information on the supported layer 2 protocols to be used between the TE and MT.

The write command causes the MT to perform all actions which are necessary to establish communication between the TE and the network using one or more GPRS PDP types. This may include performing a GPRS attach and one or more PDP context activations. Commands following the

AT+CGDATA

command in the AT command line will not be processed by the MT.

If no <cid> is given or if there is no matching context definition, the MT will attempt to activate the context with PDP type IP and all other context

parameters set to their default values (see AT+CGDCONT ,

AT+CGQREQ ,

AT+CGQMIN ).

If the <L2P> parameter is omitted, the layer 2 protocol is unspecified and PPP will be used.

If the write command is successful, the MT issues the intermediate result code

CONNECT and enters V.25ter online data state.

After data transfer is complete, and the layer 2 protocol termination procedure has completed successfully, the command state is reentered and the MT returns the final result code OK.

If the <L2P> parameter value is unacceptable to the MT, the MT returns ERROR or +CME ERROR.

In the event of erroneous termination or a failure to start up, the command state is reentered and the MT returns NO CARRIER, or if enabled +CME ERROR.


<L2P>

(str)

Layer 2 protocol to be used between the TE and MT.

["PPP"] layer 2 protocol PPP

"1" layer 2 protocol PPP

<cid>

(num)

Parameter specifies a particular PDP context definition. The parameter is local to the TE-MT interface and is used in other PDP context-related commands.

1...2

Notes


Page 163


• If the MT is in dedicated mode, write command returns with "+CME ERROR: operation temporary not allowed".

• It is possible to leave the GPRS data mode and enter the command mode by using the V.25ter command

+++ .

By using the command

AT+CGDATA

again, the data mode is reentered. Which context is used to return to data mode, depends on the supplied parameter <cid>.

• If no <cid> is specified, this is equivalent to using the V.25ter command

ATO

, which is usable for GPRS connections too. In this case the first context is used, which is active and which was already in data mode since it was activated (the internal context, which is used for GPRS connection without explicitely specifiying a context identifier, has the highest priority).

• It is possible, to use

AT+CGDATA

to enter the data mode for a context,

which was not in data mode since it was activated. With ATO

this is not possible.

9.6 AT+CGDCONT Define PDP Context

Syntax

Test Command

AT+CGDCONT=?

Response(s)

+CGDCONT: (range of supported <cid> s), <PDP_type>, ,,(list of supported <d_comp>s), (list of supported <h_comp>s)

OK

ERROR

+CME ERROR

Read Command

AT+CGDCONT?

Response(s)

+CGDCONT: <cid>,<PDP_type>,<APN>,<PDP_addr>,<d_comp>,<h_ comp>

OK

ERROR

+CME ERROR

Write Command

AT+CGDCONT=[ <cid> [, <PDP_type> [, <APN> [, <PDP

_addr> ]]]]

Response(s)

OK

ERROR

+CME ERROR


GSM 07.07

● ●


The test command returns supported values as a compound value.

The read command returns the current settings for each defined PDP context.

The write command specifies the parameters for a PDP context identified by the context identifier <cid>. The number of contexts that may be in a defined state at the same time is given by the range returned by the test command. A special form of the write command (

AT+CGDCONT =<cid>)

causes the values for context <cid> to become undefined.


<cid>

(num)

PDP Context Identifier


Page 164



1...2

<PDP_type>

(str)

Packet Data Protocol type

Specifies the type of the packet data protocol.

<APN>

(str)

"IP" Internet Protocol (IETF STD 5)

Access Point Name

The logical name that is used to select the GGSN or the external packet data network. If the value is null or omitted, then the subscription value will be requested.

<PDP_addr>

(str)

Packet Data Protocol address

Identifies the MT in the address space applicable to PDP (e.g. IP V4 address for PDP type IP). If the value is null or omitted, then a value may be provided by the TE during the PDP startup procedure or, failing that, a dynamic address will be requested. The read command will continue to return the null string even if an address has been allocated during the PDP startup procedure. The

allocated address may be read using AT+CGPADDR .

<d_comp>

(num)

Data Compression

Controls the PDP data compression (applicable for Subnetwork

Dependent Convergence Protocol (SNDCP) only) 3GPP TS 44.065

[0] off

<h_comp>

(num)

Header Compression

Controls the PDP header compression 3GPP TS 44.065, 3GPP TS

25.323

[0] off

Notes

• The MT supports PDP type IP only.

• AT&F and ATZ

will undefine every context which is not active or not online.

9.7 AT+CGPADDR Show PDP address

Syntax

Test Command

AT+CGPADDR=?

Response(s)

+

CGPADDR

: (list of supported <cid>s )

OK

Write Command

AT+CGPADDR=[ <cid> [ <cid> [...]]]

Response(s)

+ CGPADDR: <cid>,<PDP_address>

+ CGPADDR: ...

OK

ERROR

+CME ERROR


Page 165



GSM 07.07

● ●


The test command returns a list of defined <cid>s.

The write command returns a list of PDP addresses for the specified context identifiers.


<cid>

(num) a numeric parameter which specifies a particular PDP context

definition (see AT+CGDCONT command).

<PDP address>

(str) a string that identifies the MT in the address space applicable to the

PDP. The address may be static or dynamic.

Note

• If no <cid> is specified, the write command will return a list of all defined contexts.

9.8 AT+CGQMIN Quality of Service Profile (Minimum acceptable)

Syntax

Test Command

AT+CGQMIN=?

Read Command

AT+CGQMIN?

Response(s)

+CGQMIN: <PDP_type>, (list of supported <precedence>s ), (list of supported <delay>s ), (list of supported <reliability>s ), (list of supported <peak>s), (list of supported <mean>s )

OK

ERROR

+CME ERROR

Response(s)

+ CGQMIN:

<cid>,<precedence>,<delay>,<reliability>,<peak>,<mean>

OK

ERROR

+CME ERROR

Write Command

AT+CGQMIN=[<cid>[,< precedence> [,< delay> [,< reliabili ty> [,< peak> [,< mean> ]]]]]]

Response(s)

OK

ERROR

+CME ERROR


GSM 07.07

● ●


The test command returns values supported as a compound value. If the MT supports several PDP types, the parameter value ranges for each PDP type are returned on a separate line.

The read command returns the current settings for each defined context. If no minimum profile was explicitly specified for a context, simply OK will be returned, but default values will be used for that context.


Page 166


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, a special form of the set command,

AT+CGQMIN =<cid>

causes the minimum acceptable profile for context number

<cid>

to become undefined. In this case no check is made against

the negotiated profile. AT&F

and ATZ

will undefine the minimum QoS profiles of every context which is not active or not online.


<cid>

(num)


1...2

<precedence>

(num)

Precedence class subscribed

1 High

Service commitments shall be maintained ahead of precedence classes 2 and 3

2 Normal

Service commitments shall be maintained ahead of precedence class 3

3 Low

Service commitments shall be maintained

<delay>

(num)

Delay class

The delay parameter defines the end-to-end transfer delay incurred in the transmission of SDUs through the GPRS network(s).

subscribed

1..4 SDU size: 128 octets:

Delay Class

1 (Predictive)

2 (Predictive)

Mean Transfer Delay

<0.5

<5

95 percentile

<1.5

<25

3 (Predictive)

4 (Best Effort)

<50

Unspecified

<250

SDU size: 1024 octets:

Delay Class

1 (Predictive)

2 (Predictive)

Mean Transfer Delay

<0.5

<5

95 percentile

<1.5

<25

<250 3 (Predictive) <50

4 (Best Effort)

<reliability>

(num)

Reliability class

Unspecified subscribed


Page 167


1

2

3

Non real-time traffic, error-sensitive application that cannot cope with data loss

Non real-time traffic, error-sensitive application that can cope with infrequent data loss

Non real-time traffic, error-sensitive application that can cope with data loss, GMM/SM, and SMS

4

5

Real-time traffic, error-sensitive application that can cope with data loss

Real-time traffic, error non-sensitive application that can cope with data loss

<peak>

(num)

Peak throughput class (in octets per second).

1 Up to 1 000 (8 kbit/s).

2 Up to 2 000 (16 kbit/s).

3 Up to 4 000 (32 kbit/s).

4 Up to 8 000 (64 kbit/s).

5 Up to 16 000 (128 kbit/s).

6 Up to 32 000 (256 kbit/s).

7 Up to 64 000 (512 kbit/s).

8 Up to 128 000 (1024 kbit/s).

9 Up to 256 000 (2048 kbit/s).

<mean>

(num)

Mean throughput class (in octets per hour).

11 200 000(~0.44 kbit/s)

12 500 000(~1.11 kbit/s)

13 000 000 (-2.2 kbit/s)

14 000 000 (-4.4 kbit/s)

15 000 000 (-11.1 kbit/s)

16 000 000 (-22 kbit/s)

17 000 000 (-44 kbit/s)

18 000 000 (-111 kbit/s)

31 best effort

<PDP_type>

(str)

Packet Data Protocol Type


Page 168


"IP"

Notes

• If parameters are not defined, the parameter default values depend on the HLR-stored subscribed default values.

• Definitions of parameters in GSM 02.60 and GSM 03.60 paragraph 15.2

"Quality of Service Profile".

Example

If some of the QoS parameters are omitted, they will keep their current value (orthe default value if not specified so far), e.g.:

AT+CGDCONT=1,''ip''

OK

AT+CGQMIN=

OK

AT+CGQMIN?

OK

AT+CGQMIN=1,0

OK

AT+CGQMIN?

+CGQMIN:1,0,0,0,0,0

OK

AT+CGQMIN=1,0,0,0,1

OK

AT+CGQMIN?

+CGQMIN:1,0,0,0,1,0

OK

AT+CGQMIN=1,1

OK

AT+CGQMIN?

+CGQMIN:1,1,0,0,1,0

OK

9.9 AT+CGQREQ Quality of Service Profile (Requested)

Syntax

Test Command

AT+CGQREQ=?

Read Command

AT+CGQREQ?

Response(s)

+CGQREQ: <PDP_type>, (list of supported <precedence>s ), (list of supported <delay>s ), (list of supported <reliability>s ), (list of supported <peak>s ), (list of supported <mean>s )

OK

+CME ERROR

Response(s)

+ CGQREQ:

<cid>,<precedence>,<delay>,<reliability>,<peak>,<mean>

[+CGQREQ:

<cid>,<precedence>,<delay>,<reliability>,<peak>,<mean> ]

…


Page 169


Write Command

AT+CGQREQ=[<cid>[, <precedence> [, <delay> [, <reliabil ity> [, <peak> [ ,< mean> ]]]]]]

Response(s)

OK

ERROR

+CME ERROR

VERSION 1.01


GSM 07.07

● ●


The test command returns values supported as a compound value. If the MT supports several PDP types, the parameter value ranges for each PDP type are returned on a separate line.

The read command returns the current settings for each defined context. If no requested profile was explicitly specified for a context, simply OK will be returned, but default values will be used for that context.

This command allows the TE to specify a Quality of Service Profile that is used when the MT sends an Activate PDP Context Request message to the network.

The set command specifies a profile for the context identified by the (local) context identification parameter <cid> .

A special form of the set command, +CGQREQ= <cid> causes the requested profile for context number <cid> to become undefined.

AT&F

and ATZ

will undefine the QoS profiles of every context which is not active or not online.


<cid>

(num)


1...2

<precedence>

(num)

Precedence class subscribed

1 High

Service commitments shall be maintained ahead of precedence classes 2 and 3

2 Normal

Service commitments shall be maintained ahead of precedence class 3

3 Low

Service commitments shall be maintained

<delay>

(num)

Delay class

This parameter defines the end-to-end transfer delay incurred in the transmission of SDUs through the GPRS network(s).

subscribed

1 ..4 with SDU size = 128 octets:


Page 170


Delay Class

1 (Predictive)

2 (Predictive)

3 (Predictive)

4 (Best Effort)

Mean Transfer Delay

<0.5

<5

<50

Unspecified

95 percentile

<1.5

<25

<250 with SDU size = 1024 octets:

Delay Class

1 (Predictive)

2 (Predictive)

Mean Transfer Delay

<0.5

<5

95 percentile

<1.5

<25

<250 3 (Predictive) <50

4 (Best Effort) Unspecified -

<reliability>

(num)

Reliability class

[0]

1 network subscribed value

Non real-time traffic, error-sensitive application that cannot cope with data loss

2

3

Non real-time traffic, error-sensitive application that can cope with infrequent data loss

Non real-time traffic, error-sensitive application that can cope with data loss, GMM/SM, and SMS

4 Real-time traffic, error-sensitive application that can cope with data loss Real-time traffic, error non-sensitive application that can cope with data loss

<peak>

(num)

Peak throughput class in octets per second

1 Up to 1 000 (8 kbit/s)

2 Up to 2 000 (16 kbit/s)

3 Up to 4 000 (32 kbit/s)

4 Up to 8 000 (64 kbit/s)

5 Up to 16 000 (128 kbit/s)

6 Up to 32 000 (256 kbit/s)

7 Up to 64 000 (512 kbit/s)

8 Up to 128 000 (1024 kbit/s)

9 Up to 256 000 (2048 kbit/s)

<mean>

(num)

Mean throughput class in octets per hour

1 100 (~0.22 bit/s)

2 200 (~0.44 bit/s)

3 500 (~1.11 bit/s)

4 1 000 (~2.2 bit/s)

5 2 000 (~4.4 bit/s)


Page 171


6 5 000 (~11.1 bit/s)

7 10 000 (~22 bit/s)

8 20 000 (~44 bit/s)

9 50 000 (~111 bit/s)

10 100 000 (~0.22 kbit/s)

11 200 000(~0.44 kbit/s)

12 500 000(~1.11 kbit/s)

13 1 000 000 (~2.2 kbit/s)

14 2 000 000 (~4.4 kbit/s)

<PDP_type>

(str)

Packet Data Protocol type

"IP"

Notes

• If parameters are not defined, the parameter default values depend on the HLR-stored subscribed default values.

• Definitions of parameters in GSM 02.60 and GSM 03.60 paragraph 15.2

"Quality of Service Profile".

Example

If some of the QoS parameters are omitted, they will keep their current value (or the default value if not specified so far), e.g.:

AT+CGDCONT=1,''ip''

OK

AT+CGQREQ=

OK

AT+CGQREQ?

OK

AT+CGQREQ=1,0

OK

AT+CGQMIN?

+CGQREQ:1,0,0,0,0,0

OK

AT+CGQREQ=1,0,0,0,1

OK

AT+CGQREQ?

+CGQREQ:1,0,0,0,1,0

OK

AT+CGQREQ=1,1

OK

AT+CGQREQ?

+CGQREQ:1,1,0,0,1,0

OK

9.10 AT+CGREG GPRS network registration status

Syntax


Page 172


Test Command

AT+CGREG=?

Read Command

AT+CGREG?

Write Command

AT+CGREG=[ <n> ]

Response(s)

+CGREG: (list of supported <n> s)

OK

Response(s)

+CGREG: <n>,<stat>

OK

Response(s)

OK

ERROR

+CME ERROR


GSM 07.07

● ●


+CGREG: <stat>

Indicates a change in the MT's GPRS network registration status.


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.

The write command controls the presentation of an unsolicited result code

"+

CGREG

" when <n>=1 and there is a change in the MT's GPRS network registration status.


<n>

(num)

0

(P)

1 disable network registration unsolicited result code enable network registration unsolicited result code

"+

CGREG

"

<stat>

(num)

1

2

3

4 not registered, ME is not currently searching an operator to register to the MS is in GMM state GMM-

NULL or GMM-DEREGISTERED-INITIATED. The GPRS service is disabled, the MS is allowed to attach for

GPRS if requested by the user. registered, home network. The MS is in GMM state

GMM-REGISTERED or GMM-ROUTING-AREA-UPDATING-

INITIATED initiated on the home PLMN. not registered, but ME is currently trying to attach or searching an operator to register to. The MS is in GMM state GMM-DEREGISTERED or GMM-REGISTERED-

INITIATED. The GPRS service is enabled, but an allowable PLMN is currently not available. The MS will start a GPRS attach as soon as an allowable PLMN is available. registration denied. The MS is in GMM state GMM-NULL.

The GPRS service is disabled, the MS is not allowed to attach for GPRS if requested by the user unknown. roaming. MS is in GMM state GMM-

REGISTERED or GMM-ROUTING-AREA-UPDATING-

INITIATED on a visited PLMN.


Page 173


Note

• When the module is GPRS attached and a PLMN reselection occurs to a non-GPRS capable network or to a network where the SIM is not subscribed to for using GPRS, the resulting GMM (GPRS mobility management) state according to GSM 24.008 is REGISTERED/NO CELL, meaning that the read command will still show <stat>=1 or <stat>=5 .

9.11 AT+CGSMS Select service for MO SMS messages

Syntax

Test Command

AT+CGSMS=?

Response(s)

+CGSMS: (list of supported <service>s )

OK

Read Command

AT+CGSMS?

Write Command

AT+CGSMS=[ <service> ]

Response(s)

+CGSMS: <service>

OK

Response(s)

OK

ERROR

+CME ERROR


GSM 07.07

○ ●


The test command is used for requesting information on which services and

service preferences can be set by using the AT+CGSMS

write command.

The read command returns the currently selected service or service preference.

The write command is used to specify the service or service preference that the MT will use to send MO SMS messages. If parameter <service> is not given, the current value remains unchanged.


<service>

(num)

A numeric parameter which indicates the service or service preference to be used

0 GPRS

2 GPRS prefered (use circuit switched if mobile is not GPRS attached)

[3] circuit switched preferred (use GPRS if circuit switched is not available)

Note

•

Parameter cannot be stored using AT&W


Page 174


9.12 AT

^

SGAUTH Set type of authentication for PPP connection

Syntax

Test Command

AT^SGAUTH=?

Read Command

AT^SGAUTH?

Write Command

AT^SGAUTH=<auth>

Response(s)

^SGAUTH: (list of supported <auth>s )

OK

ERROR

+CME ERROR

Response(s)

^SGAUTH: <auth>

OK

ERROR

+CME ERROR

Response(s)

OK

ERROR

+CME ERROR

Reference(s)

SIEMENS

PIN

●

SERIAL

●


<auth>

(num)

Indicates types of supported authentication.

0 none

1 PAP

2 CHAP

3

(P)

PAP and CHAP

9.13 AT

^

SGCONF Configuration of GPRS related Parameters

Syntax

Test Command

AT^SGCONF=?

Read Command

AT^SGCONF?

Write Command

AT^SGCONF=[<llc_pdu_length>][,< class> ]

Response(s)

^SGCONF: (list of supported <llc_pdu_length>s ), (list of supported

<class>es )

OK

Response(s)

^SGCONF: <llc_pdu_length>,<class>

OK

Response(s)

OK

ERROR

+CME ERROR

Reference(s)

SIEMENS


<llc_pdu_length>

(num)

LLC-PDU-length

0

PIN

○

SERIAL

● no negotiation with network (500 will be used)


Page 175


<class>

(num)

14O...152O

(P) lower values diminish performance

GPRS Multislot Class. The parameter can be changed only when the

MT is detached, otherwise "CME ERROR: operation temporary not allowed" will be returned. The value can be one of the classes indicated with the test command.

Notes

• +CME ERROR: invalid index: Parameter is out of range.

• +CME ERROR: operation temporary not allowed: The command is blocked as long as GPRS is already in use (as long as mobile is GPRS attached).

• Writing to user profile with AT&W

and restoring with AT&F are not supported.

9.14 ATA Manual response to a network request for PDP context activation

Syntax

Exec Command

ATA

Response(s)

CONNECT

NO CARRIER


GSM 07.07

● ●


The V.25ter ATA

command may be used to accept a network request for a

PDP context activation announced by the unsolicited result codes RING or

"+

CRING

: GPRS". The MT responds with CONNECT, enters V.25ter online data state and follows the same procedure as it would after having received a

AT+CGANS =1

with no <L2P> or <cid> values specified.

If you try to answer a request which is no longer present or which is already answered by another instance, NO CARRIER is returned.

9.15 ATD*99# Request GPRS service

Syntax

Exec Command

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

Response(s)

CONNECT

NO CARRIER


GSM 07.07

● ●


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. No further commands may follow on the AT command line. GPRS attachment and PDP context activation procedures may take place prior to or during the PDP


Page 176


startup if they have not already been performed using the AT+CGATT

and

AT+CGACT

commands. If the context to be used is already activated, it will be deactivated first. This ensures that the right context parameters will be used

(e.g. QoS changes since the last context activation or the called address

specified by ATD*99# ).

Examples on how to use this command are provided in chapter "using GPRS

AT commands (Examples)".

To confirm acceptance of the command before entering the V.25ter online data state command will respond with CONNECT.

When the layer 2 protocol has terminated, either as a result of an orderly shutdown of the PDP or an error, the MT enters V.25ter command state and returns NO CARRIER.


<called_address>

(str)

IP V4 address in the form w.x.y.z, which identifies the called party; if it is provided, the MT will automatically set up a virtual call to the specified address after the context has been activated. This parameter is currently not used and needs not to be specified.

<L2P>

(str)

Layer 2 protocol to be used between the TE and MT.

"PPP" layer 2 protocol PPP

"1" layer 2 protocol PPP

<cid>

(num)

Parameter specifies a particular PDP context definition (see

AT+CGDCONT

command). If no context is specified, an internal context 0 with default properties is used (see

AT+CGDCONT ,

AT+CGQREQ and

AT+CGQMIN ).

1...2

Notes

• If TANGO55/56 is in dedicated mode, command returns with "+CME ERROR: phone busy".

• ATD is used as a standard V.25ter AT command, too.

9.16 ATD*98# Request GPRS IP service

Syntax

Exec Command

ATD*98[* <cid> ]#

Response(s)

CONNECT

NO CARRIER


GSM 07.07

● ●


This command causes the MT to perform whatever actions are necessary to establish a 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 layer 2 protocol.


Page 177


GPRS attachment and PDP context activation procedures may take place prior to or during the PDP startup if they have not already been performed

using the AT+CGATT

and

AT+CGACT

commands. If the context to be used is already activated, it will be deactivated first. This ensures that the right context parameters will be used (e.g. QoS changes since the last context activation).

To confirm acceptance of the command before entering the V.25ter online data state command will respond with CONNECT.

When the layer 2 protocol has terminated, either as a result of an orderly shutdown of the PDP or an error, the MT enters V.25ter command state and returns NO CARRIER.


<cid>

(num)

Parameter specifies a particular PDP context definition (see

AT+CGDCONT

command). If no context is specified, an internal context 0 with default properties is used (see

AT+CGDCONT ,

AT+CGQREQ and

AT+CGQMIN ).

1...2

Notes

• If TANGO55/56 is in dedicated mode, command returns with "+CME ERROR: phone busy".

• ATD is used as a standard V.25ter AT command, too.

9.17 ATH Manual rejection of a network request for PDP context activation

Syntax

Exec Command

ATH

Reference(s)

Response(s)

OK

PIN SERIAL

GSM 07.07

● ●


The V.25ter

ATH

command may be used to deactivate all PDP contexts which are active or online on the same interface.

The

ATH

command may also be used to reject a network request for PDP context activation announced by the unsolicited result codes "RING" or

"+

CRING

:GPRS".

Notes

• In contrast to GSM 07.07 it is possible to cancel a connection with ATH

after a break. This is done for compatibility reasons due to the "dial-up network" drivers of Microsoft Windows.

•

ATH is used as a standard V.25ter AT command, too.

• If

ATH

is used to reject a network request for PDP context activation, then other PDP contexts on the same interface which are active or online will not be deactivated.


Page 178


9.18 ATS0 Automatic response to a network request for PDP context activation

Syntax

Read Command

ATS0?

Write Command

ATS0= <n>

Reference(s)

Response(s)

<n>

OK

Response(s)

OK

PIN SERIAL

GSM 07.07

◑ ●


The V.25ter ATS0 =<n>

(Automatic answer) command may be used to turn off

(n=0) and on (n>0) the automatic response to a network request for a PDP context activation.

When the

ATS0 =<n> (<n>

> 0) command is received, the MT will attempt to perform a GPRS attach if it is not yet attached and if ME is configured to do this

(see

AT^SCFG ,

parameter <gaa> ). Failure will result in ERROR being returned to the TE. Subsequently, the MT will announce a network request for PDP context activation by issuing the URC RING or CRING to the TE, followed by the intermediate result code CONNECT. The MT then enters V.25ter online data state and follows the same procedure as it would after having received a

AT+CGANS =1

command with no <L2P> or <cid>

values specified. ATS0 =O

does not perform an automatic GPRS detach.


<n>

(num)(&W)(&V)

000

(&F) automatic answering is disabled

001-255 enable automatic answering on the specified ring number

Notes

• If different settings are used on each interface, and a request for PDP context activation is received, the interface 'wins' which is idle and uses the

smallest ATS0 value.

• If a network request for PDP context activation is answered automatically and another AT command is issued at the same time on the same interface then this AT command will not be executed. Any response belongs to the automatic context activation procedure. If the AT command which caused the collision was a CS data call, the CONNECT response does not belong to this data call but to the GPRS. This can be detected if

ATX is not set to 0. CS data call will issue CONNECT <text>, GPRS

will issue CONNECT only.

• A network request for PDP context activation has a maximum duration of approximately 40 seconds (for details see GSM 04.08). A RING/CRING URC is issued every 5 seconds, so setting parameter <n> to values greater than 7 will not allow a successful context activation and is not recommended.

• The automatic GPRS attach will not be performed on recalling a stored

user profile with ATZ or on power up, if an > 0 setting was stored in the user

profile with

AT&W .


Page 179


• If the automatic GPRS attach fails (e.g. the network rejects the attach request), the write command returns with error, but the value of <n> is changed anyway. This is necessary because ATS0 is used for circuit

switched calls too (see ATS0 ).

• ATSO write command is PIN protected.

9.19 Using GPRS AT commands (Examples)

Examples:

EXAMPLE 1

Defining and using a Context Definition ID (CID):

Every time a CID is used as a parameter for a GPRS command the CID

has to be defined before by using the AT+CGDCONT command. To get the parameter of a CID use the AT+CGDCONT

read option. If the

response of ‘ AT+CGDCONT ? ' is OK only, there is no CID defined.

AT+CGDCONT?

OK There is no CID defined.

All parameters of the CID are initiated by NULL or not present values, and the CID itself is set to be undefined. To define a CID use the

AT+CGDCONT

command with at least one CID parameter. At the moment the mobile supports CID 1 and CID 2 by using the

AT+CGDCONT command.

Define CID 1 and set the PDP type to IP, access point name and IP address are not set:

AT + CGDCONT=1, "IP"

OK

Define CID 2 and sets PDP type, APN and IP addr:

AT+CGDCONT=2,"IP","internet.t-d1.gprs",111.222.123 . 234

OK

A following read command will respond:

AT+CGDCONT?

+ CGDCONT:1,"IP","", "",0,0

+CGDCONT:2,"IP","internet.t-d1.gprs",111.222.123 . 234

OK

Set the CID 1 to be undefined:

AT+CGDCONT=1

OK


AT+CGDCONT?

+CGDCONT:2,"IP","internet.t-d1.gprs",111.222.123.234

OK

EXAMPLE 2

Quality of Service (QoS) is a special parameter of a CID which consists of several parameters itself. The QoS consists of

- the precedence class

- the delay class

- the reliability class


Page 180


- the peak throughput class

- the mean throughput class and is divided in "requested QoS" and "minimum acceptable QoS".

All parameters of the QoS are initiated by default to the "network subscribed value (= 0)" but the QoS itself is set to be undefined. To

define a QoS use the AT+CGQREQ

or AT+CGQMIN

command.

Overwrite the precedence class of QoS of CID 1 and set the QoS of

CID 1 to be present:

AT+CGQREQ=1,2

OK


AT+CGQREQ?

+CGQREQ: 1,2,0,0,0,0

OK

All QoS values of CID 1 are set to network subscribed now, except precedence class which is set to 2. Now set the QoS of CID 1 to not present:

AT+CGQREQ=1

OK

Once defined, the CID it can be activated. To activate CID 2 use:

AT+CGACT=1,2

OK

If the CID is already active, the mobile responds OK at once.

If no CID and no STATE is given, all defined CIDs will be activated by:

AT+CGACT=

OK

If no CID is defined the mobile responds +CME ERROR: invalid index

Remark: If the mobile is NOT attached by AT+CGATT =1

before

activating, the attach is automatically done by the AT+CGACT

command.

After defining and activating a CID it may be used to get online by:

AT + CGDATA="PPP" ,1

CONNECT The mobile is connected using the parameters of CID

1.

AT+CGDATA=

CONNECT The mobile is connected using default parameters (<L2P>="PPP" and <cid> as

described for command AT+CGDATA ).

The mobile supports Layer 2 Protocol (L2P) PPP only.

Remark: If the mobile is NOT attached by AT+CGATT =1

and the CID is

NOT activated before connecting, attaching and activating is

automatically done by the AT+CGDATA command.

Some providers (e.g. D2 or E-Plus) require to use an APN to establish a

GPRS connection. So if you use the Microsoft Windows Dial-Up Network and ATD*9... to connect to GPRS you must provide the context definition as part of the modem definition (Modem properties/Connection/Advanced.../Extra settings). As an alternative, you can define and activate the context in a terminal program (e.g.


Page 181


Microsoft Hyperterminal) and then use the Dial-Up Network to send only

the ATD command.

9.20 Using the GPRS dial command ATD

Example

In addition to the GPRS AT commands you can use the "D" command to dial into to the GPRS network.

There are two GPRS Service Codes for the ATD command: Values 98

and 99. Examples:

ATD*99#

CONNECT

ATD*99*123.124.12 5.12 6*PPP*1#

CONNECT

Establish a connection by service code 99.

Establish a connection by service code 99, IP address 123 and L2P =

PPP and using CID 1. The CID has to be defined by AT+CGDCONT .

ATD*99**PPP#

CONNECT

ATD*99***1#

CONNECT

ATD*99**PPP*1#

CONNECT

Establish a connection by service code 99 and L2P = PPP.

Establish a connection by service code 99 and using CID 1.

Establish a connection by service code 99 and L2P = PPP and using CID

1. The CID has to be defined by AT+CGDCONT .

ATD*98#

CONNECT

ATD*98*1#

CONNECT

Establish a connection by service code 98.

Establish an IP connection by service code 98 using CID 1. The CID has

to be defined by AT+CGDCONT .


Page 182


10 FAX COMMANDS

The following commands can be used for FAX transmission. If the ME is acting as a

Fax-Modem to a PC-based application (e.g. "WinFax") it is necessary to select the proper Service Class (Fax Class) provided by the ME. The ME reports its Service Class capabilities, both the current setting and the range of services avaible. This is

provided by the AT+FCLASS command. Service Classes supported by ME:

AT+FCLASS Parameter

0

Service class data modem

Reference, Standard e.g. TIA/EIA-602 or ITU V.25ter

1

2

Service Class 1 manufacture specific

EIA/TIA-578-A this document and EIA PN-2388 (draft)

The following AT commands are dummy commands:

AT+FAA Auto Answer mode

AT+FECM Error Correction Mode control

AT+FLNFC Page Length format conversion

AT+FLPL Indicate document available for polling

AT+FMINSP Minimum Phase C speed

AT+FRBC

AT+FREL

AT+FSPL

AT+FTBC

Phase C data receive byte count

Phase C received EOL alignment

Enable polling

Phase C data transmit byte count

AT+FWDFC Page width format conversion

Invoking these commands will not cause ERROR result codes, but these commands have no functionality .

10.1 FAX parameters


<bf>

(num)

Binary File Transfer Mode

Note: Only the default value needs to be implemented. Use test command to check which parameter values are really possible!

[0] disable

<br>

(num)

Bit Rate bit/s, bit/s, bit/s, bit/s,

<df>

(num)

Data Compression Format


[0] 1-D modified Huffman

1 2-D modified read


Page 183


2 2-D uncompressed mode

<ec>

(num)

Error Correction Mode


1 enable ECM, 64 bytes/frame

2 enable ECM, 256 bytes/frame

<ln>

(num)

Page Length

1 B4, 364 mm

<mod>

(num) modulation mode

3 V21 Ch2 - 300 bps

24 V.27ter - 2400 bps

48 V.27ter - 7200 bps

72 V.29 - 7200 bps

96 V.29 - 9600 bps

<st>

(num)

Scan Time/Line

Note: Only the default value needs to be implemented. Use test command to check which parameter values are really possible![0] 0 ms (at VR= normal)

1 5 ms

2 10 ms

3 10 ms

4 20 ms

5 20 ms

6 40 ms

7 40 ms

<vr>

(num)

Vertical Resolution

0 normal, 98 lpi

[1] fine, 196 lpi

<wd>

(num)

Page Width

[0] 1728 pixels in 215mm

1 2048 pixels in 255 mm




Note


Page 184


• Only the default value needs to be implemented. Use test command to check which parameter values are really possible.

10.2 AT+FBADLIN Bad Line Threshold

Syntax

Read Command

AT+FBADLIN?

Write Command

AT+FBADLIN= <badlin>

Response(s)

<badlin>

OK

OK

Response(s)

OK


ERROR


EIA PN-2388

○ ●


This command defines the Copy-Quality-OK-threshold. If <badlin> consecutive lines have pixel count errors in normal resolution (98 dpi) mode, then the copy quality is unacceptable. If <badlin> * 2 consecutive lines have pixel count errors in fine resolution (196 dpi) mode, then the copy quality is unacceptable.

"Copy Quality Not OK" occurs if either the error percentage is too high or too many consecutive lines contain errors. A value of 0 implies that error checking is not present or disabled.


<badlin>

(num) bad lines

0...10

(P)

...255

Note

• Used for Fax Class 2 only

10.3 AT+FBADMUL Error Threshold Multiplier

Syntax

Read Command

AT+FBADMUL?

Write Command

AT+FBADMUL= <badmul>

Response(s)

<badmul>

OK

Response(s)

OK


ERROR


EIA PN-2388

○ ●


This command defines the "Copy-Quality-OK" multiplier. The number of lines received with a bad pixel count is multiplied by this number. If the result exceeds the total number of lines on the page the error rate is considered too


Page 185

TANGO55/56 AT COMMAND SET VERSION 1.01 high. A threshold multiplier value of 20 corresponds to a 5 per cent error rate. A value of 0 implies that error checking is not present or disabled.


<badmul>

(num)

0...20

(P)

...255

Note


10.4 AT+FBOR Query data bit order

Syntax

Test Command

AT+FBOR=?

Read Command

AT+FBOR?

Write Command

AT+FBOR= <bor>

Response(s)

(list of supported <bor>s )

OK

Response(s)

<bor>

OK

Response(s)

OK


EIA PN-2388

○ ●


Query the bit order for receive-mode. The mode is set by the ME depending on the selected Service Class, see

" AT+FCLASS

Fax: Select, read or test service class".


<bor>

(num) bit order modes

0 Direct bit order for both Phase C and for Phase B/D data.

[1] Reversed bit order for Phase C data, direct Bit Order for

Phase B/D data.

Note


10.5 AT+FCIG Query or set the Local Polling ID

Syntax

Test Command

AT+FCIG=?

Read Command

AT+FCIG?

Write Command

AT+FCIG= <id>

Response(s)

(max. length of Local Polling ID string) (range of supported ASCII character values)

OK

Response(s)

<id>

OK

Response(s)

OK


Page 186



EIA PN-2388

○ ●


<id>

(num)

Local Polling ID string, max. length and possible content as reported by test command. Default value is empty string ("").

Notes

• Used for Fax Class 2 only.

• See also

AT

+

FLID

Query or set the Local Id setting capabilities.

10.6 AT+FCLASS Fax: Select, read or test service class

Syntax

Test Command

AT+FCLASS=?

Read Command

AT+FCLASS?

Write Command

AT+FCLASS= <n>

Reference(s)

Response(s)

(list of supported <n> s)

OK

Response(s)

<n>

OK

Response(s)

OK

PIN SERIAL

EIA/TIA-592-A

○ ●


The ME is set to a particular mode of operation (data, fax). This causes the MA to process information in a manner suitable for that type of information.


<n>

(num)(&W)(&V)

[0]

1

2

(&F) data (e.g. EIA/TIA-602 or ITU V.25ter)

Fax class 1 (EIA/TIA-578-A, Service class 1)

Fax class 2 (EIA/TIA SP-2388, an early draft version of EIA/TIA-592-A - Service class 2.1)

Notes

• Using Error Correcting Mode (ECM) when sending FAXes over GSM should be avoided.

• If <n> is set to 1 or 2, all incoming calls will be answered as fax calls with

ATA

.

For calls explicitly signalled as voice or data calls, this procedure will fail with result code "NO CARRIER", but the call in question will continue to ring.

• It is possible to change the setting of <n> to 0 while the call is ringing, and accept the call normally afterwards with

ATA

.

10.7 AT+FCQ Copy Quality Checking

Syntax


Page 187


Test Command

AT+FCQ=?

Response(s)

(list of supported copy quality checking <cq>s )

OK

Read Command

AT+FCQ?

Write Command

AT+FCQ= <cq>

Reference(s)

Response(s)

<cq>

OK

Response(s)

OK

PIN SERIAL

EIA PN-2388

○ ●


This command controls Copy Quality checking when receiving a fax.


<cq>

(num)

0

[1]

No copy quality checking. The ME will generate Copy

Quality OK (MCF) responses to complete pages.

ME can check 1-D phase data. The connected application must check copy quality for2-D phase C data.

Note


10.8 AT+FCR Capability to receive

Syntax

Write Command

AT+FCR= <cr>

Reference(s)

Response(s)

OK

PIN SERIAL

EIA PN-2388

○ ●


<cr>

(num)

[0] ME will not receive message data. This can be used when the application has insufficient storage. The ME can send and can be polled for a file.

1 ME can receive message data.

Note


10.9 AT+FDCC Query or set capabilities

Syntax

Test Command

AT+FDCC=?

Response(s)

(list of <vr> s), (list of <br>s ), (list of <wd>s ), (list of <ln> s), (list of

<df > s), (list of <ec> s), (list of <bf > s), (list of <st>s )

OK


Page 188


Write Command

AT+FDCC= <vr> ,< br>,<wd>,<ln>,<df>, <ec>,<bf

>,<st>

Reference(s)

Response(s)

OK

PIN SERIAL

EIA PN-2388

○ ●


This command allows the connected application to sense and constrain the capabilities of the facsimile DCE (=ME), from the choices defined in CCITT T.30 table 2.

Notes

• For further information see AT+FDIS.


10.10 AT+FDFFC Data Compression Format Conversion

Syntax

Test Command

AT+FDFFC=?

Read Command

AT+FDFFC?

Response(s)

(list of <df>s )

OK

Response(s)

<df>

OK

Write Command

AT+FDFFC= <df>

Response(s)

OK


EIA PN-2388

○ ●


This parameter determines the ME response to a mismatch between the data format negotiated for the fax session, reported by the <df> subparameter, and the Phase C data desired by the controlling application, indicated by the optional

AT+FDT

<df>

subparameter, or the AT+FDIS

<df> subparameter for

AT+FDR operation.


<df>

(num)

[0] Mismatch checking is always disabled. The controlling application has to check the <df> subparameter and transfer matching data.

Notes

• For further information see AT+FDIS.


10.11 AT+FDIS Query or set session parameters

Syntax


Page 189


Test Command

AT+FDIS=?

Read Command

AT+FDIS?

Write Command

AT+FDIS= <vr> ,< br>,<wd>,<ln>,<df>, <ec>,<bf

>,<st>

Reference(s)

Response(s)

(list of <vr> s), (list of <br>s ), (list of <wd>s ), (list of <ln> s), (list of

<df >s), (list of <ec> s), (list of <bf > s), (list of <st>s)

OK

Response(s)

<vr>,<br>,<wd>,<ln>,<df>,<ec>,<bf>,<st>

OK

Response(s)

OK

PIN SERIAL

EIA PN-2388

○ ●


This command allows the controlling application to sense and constrain the

capabilities used for the current session. It uses AT+FDIS

to generate DIS or DTC

messages directly, and uses AT+FDIS

and received DIS messages to generate

DCS messages.

Note


10.12 AT+FDR Begin or continue phase C data reception

Syntax

Exec Command

AT+FDR

Response(s)

CONNECT or

OK

If error related to ME functionality

ERROR


EIA PN-2388

○ ●


The command initiates transition to Phase C data reception.

Note


Syntax

Exec Command

AT+FDT

Write Command

AT+FDT= <df >,<vr>,<wd>,<ln>

Reference(s)

Response(s)

CONNECT

Response(s)

CONNECT

PIN SERIAL


Page 190


EIA PN-2388

○ ●


This command requests the ME to transmit a Phase C page. When the ME is ready to accept Phase C data, it issues the negotiation responses and the

CONNECT result code to the application.

In Phase B, the

AT+FDT

command releases the ME to proceed with negotiation,

and releases the DCS message to the remote station. In Phase C, the AT+FDT

command resumes transmission after the end of a data stream transmited before.

Note


10.14 AT+FET End a page or document

Syntax

Write Command

AT+FET= <ppm>

Reference(s)

Response(s)

OK

PIN SERIAL

EIA PN-2388

○ ●


This command indicates that the current page or partial page is complete. An

ERROR response code results if this command is issued while the mode is onhook.


<ppm>

(num)

Post Page Message Codes

1 another document next

2 no more pages or documents

3

4 another page, procedure interrupt another document, procedure interrupt

Note


10.15 AT+FK Kill operation, orderly FAX abort

Syntax

Exec Command

AT+FK

PIN SERIAL

○

Response(s)

OK

●


This command causes the TA to terminate the session in an orderly manner.


Page 191


Note


10.16 AT+FLID Query or set the Local Id setting capabilities

Syntax

Test Command

AT+FLID=?

Read Command

AT+FLID?

Response(s)

(max. character length of Local ID string) (range of supported ASCII character values)

OK

Response(s)

<lid>

OK

Response(s)

OK

Write Command

AT+FLID= <lid>


EIA PN-2388

○ ●


<lid>

(num)

Local ID string max. length and possible content as reported by test command.

Default value is empty string ("").

Notes


• See also AT+FCIG

Query or set the Local polling id.

10.17 AT+FMDL Identify Product Model

Syntax

Read Command

AT+FMDL?

Reference(s)

Response(s)

Gipsy Soft Protocolstack OK

SIEMENS

PIN

○


Send the model identification to the TA.

Note


SERIAL

●

10.18 AT+FMFR Request Manufacturer Identification

Syntax

Read Command

AT+FMFR?

Response(s)

SIEMENS

OK


Page 192


Reference(s)

SIEMENS

PIN

○

SERIAL

●


Send the manufacturer identification to the TA.

Note


10.19 AT+FOPT Set bit order independently

Syntax

Write Command

AT+FOPT= <opt>

Reference(s)

Response(s)

OK

SIEMENS

PIN

○

SERIAL

●


Model specific command to set bitorder independently of the understanding which is "mirrored" and which is direct.


<opt>

(num)

0 non-standard

1 standard

Note


10.20 AT+FPHCTO DTE Phase C Response Timeout

Syntax

Read Command

AT+FPHCTO?

Write Command

AT+FPHCTO= <tout>

Response(s)

<tout>

OK

Response(s)

OK


ERROR


EIA PN-2388

○ ●


The time-out value <tout> determines how long the DCE will wait for a command after reaching the end of data when transmitting in Phase C. When time-out is reached, the DCE assumes that there are no more pages or documents to send.



Page 193


<tout>

(num)

Timeout

Value in 100ms units

0...30

(P)

...255

Note


10.21 AT+FREV Identify Product Revision

Syntax

Read Command

AT+FREV?

Response(s)

V2.550

OK

Reference(s) PIN

SIEMENS

○


Sends the revision identification to the TA.

SERIAL

●

Note


10.22 AT+FRH Receive Data Using HDLC Framing

Syntax

Write Command

AT+FRH= <mod>

Response(s)

CONNECT


ERROR


TIA/EIA-578

○ ●


This command causes the TA to receive frames using the HDLC protocol and the modulation defined below. An ERROR response code results if this command is issued while the modem is on-hook.

Note


10.23 AT+FRM Receive Data

Syntax

Test Command

AT+FRM=?

Response(s)

(list of <mod>s )

OK


Page 194


Write Command

AT+FRM= <mod>

Response(s)

CONNECT


ERROR


TIA/EIA-578

○ ●


This command causes the TA to enter the receiver-mode using the modulation defined below. An ERROR response code results if this command is issued while the modem is on-hook.

Notes


• <mod> = 3 is not possible

Syntax

Write Command

AT+FRS= <time>

Response(s)

OK


ERROR


TIA/EIA-578

○ ●


<time>=n causes the TA to report an OK result code to the TE after <time> 10 millisecond intervals of silence have been detected on the line. This command is aborted if any character is received by the DTE. The modem discards the aborting character and issues an OK result code. An ERROR response code results if this command is issued while the mode is on-hook.


<time>

(num) no. of 10 millisecond intervals

0...255

Note


10.25 AT+FTH Transmit Data Using HDLC Framing

Syntax

Write Command

AT+FTH=<mod>

Response(s)

CONNECT



Page 195


TIA/EIA-578

○ ●


This command causes the TA to transmit data using HDLC protocol and the modulation mode defined below. An ERROR response code results if this command is issued while the modem is on-hook.

Notes


• Only <mod> = 3 is possible

10.26 AT+FTM Transmit Data

Syntax

Test Command

AT+FTM=?

Write Command

AT+FTM= <mod>

Response(s)

(list of <mod>s )

OK

Response(s)

CONNECT


ERROR


TIA/EIA-578

○ ●


This command causes the TA to transmit data using the modulation mode defined below. An ERROR response code results if this command is issued while the modem is on-hook.

Notes


• <mod> = 3 is not possible

10.27 AT+FTS Stop Transmission and Wait

Syntax

Write Command

AT+FTS= <time>

Response(s)

An ERROR response code results if this command is issued while the modem is on-hook.


TIA/EIA-578

○ ●


This command causes the TA to terminate a transmission and wait for <time>

10 millisecond intervals before responding with the OK result code to the DTE.


<time>

(num) no. of 10 millisecond intervals

0...85


Page 196


Note


10.28 AT+FVRFC Vertical resolution format conversion

Syntax

Test Command

AT+FVRFC=?

Read Command

AT+FVRFC?

Write Command

AT+FVRFC= <vrfc>

Reference(s)

Response(s)

(list of supported <vrfc>s )

OK

Response(s)

<vrfc>

OK

Response(s)

OK

PIN SERIAL

EIA PN-2388

○ ●


This command determines the DCE response to a mismatch between the vertical resolution negotiated for the facsimile session and the Phase C data desired by the DTE.


<vrfo>

(num)

0 Disable mismatch checking.

[2] Enable mismatch checking, with resolution conversion of 1-D data in the DCE, and an implied

AT

+

FK command executed on 2-D mismatch detection.

Note



Page 197


11 SHORT MESSAGE SERVICE (SMS) COMMANDS

The AT commands described in this chapter allow an external application to use the

Short Message Service with the TANGO55/56.

11.1 SMS parameters


<ackpdu>

(num)

Format is same for <pdu> in case of SMS, but without GSM 24.11 SC address field and parameter shall be bounded by double quote characters like a normal string type parameter

<alpha>

(str)(+CSCS)

String type alphanumeric representation of <da> or <oa> corresponding to the entry found in phone book; implementation of this feature is manufacturer specific

<cdata>

(num)

Command Data

GSM 03.40 TP-Command-Data in text mode responses; ME/TA converts each 8-bit octet into two IRA character long hexadecimal numbers (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65))

<ct>

(num)

Command Type

GSM 03.40 TP-Command-Type in integer format

[0]...255

<da>

(num)(+CSCS)

Destination Address

GSM 03.40 TP - Destination-Address Address-Value field in string format; BCD numbers (or GSM default alphabet characters) are converted into characters; type of address given by <toda>

<data>

(num)(+CSCS)

User Data

In case of SMS: GSM 03.40 TP-User-Data in text mode responses; format:

• If <dcs> indicates that GSM 03.38 default alphabet is used and

<fo> indicates that GSM 03.40 TP-User-Data-Header-Indication is not set: ME/TA converts GSM alphabet into current TE character set according to rules covered in Annex A.

• If <dcs> indicates that 8-bit or UCS2 data coding scheme is used, or <fo> indicates that GSM 03.40 TP-User-Data-Header-Indication is set: ME/TA converts each 8-bit octet into hexadecimal numbers con-taining two IRA characters (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65).

• In case of CBS: GSM 03.41 CBM Content of Message in text mode responses; format:

• If <dcs> indicates that GSM 03.38 default alphabet is used:

ME/TA converts GSM alphabet into current TE character set according to rules covered in Annex A.


Page 198


• If <dcs> indicates that 8-bit or UCS2 data coding scheme is used:

ME/TA converts each 8-bit octet into hexadecimal numbers containing two IRA characters.

<dt>

(num)

Discharge Time

GSM 03.40 TP-Discharge-Time in time-string format:

"yy/MM/dd,hh:mm:ss+zz", where characters indicate year (two last digits), month, day, hour, minutes, seconds and time zone. For example, 6th of May 1994, 22:10:00 GMT+2 hours equals

"94/05/06,22:10:00+08"

<index>

(num)

Integer type; value in the range of location numbers supported by the associated memory

<length>

(num)

Message Length

Integer type value indicating in the text mode

( AT+CMGF =1)

the length of the message body <data> (or <cdata>) in characters; or in

PDU mode (

AT+CMGF =0),

the length of the actual TP data unit in octets (i.e. the RP layer SMSC address octets are not counted in the length) In text mode, the maximum length of an SMS depends on the used coding scheme: It is 160 characters if the 7 bit GSM coding scheme is used, and 140 characters according to the 8 bit GSM coding scheme.

If the SMS message format is "text mode" (

AT+CMGF =1)

and the character set is set to "UCS2" with

AT+CSCS and the SMS is also coded

as "UCS2" (see <dcs> of

AT+CSMP ),

then the length is in octets instead of characters.

<meml>

(str)

Memory to be used when listing, reading and deleting messages:

"SM"

"ME" Mobile Equipment message storage

"MT"

(D)

Sum of "SM" and "ME" storages

<mem2>

(str)

Memory to be used when writing and sending messages:

"SM"

"ME" Mobile Equipment message storage

"MT"

(D)


<mem3>

(str)

Received messages will be placed in this memory storage if routing to

TE is not set. See command

AT+CNMI with parameter

<mt> =2.

"MT"

(D)


<mid>

(num)

Message Identifier

GSM 03.41 CBM Message Identifier in integer format

<mn>

(num)

Message Number

GSM 03.40 TP-Message-Number in integer format

<mr>

(num)


Page 199


Message Reference

GSM 03.40 TP-Message-Reference in integer format

<oa>

(num)(+CSCS)

Originating Address

GSM 03.40 TP-Originating-Address Address-Value field in string format;

BCD numbers (or GSM default alphabet characters) are converted into characters; type of address given by <tooa>

<page>

(num)

Page Parameter

GSM 03.41 CBM Page Parameter bits 4-7 in integer format

<pages>

(num)

Page Parameter

GSM 03.41 CBM Page Parameter bits 0-3 in integer format

<pdu>

(num)

In the case of SMS: GSM 04.11 SC address followed by GSM 03.40

TPDU in hexadecimal format: ME/TA converts each octet of TP data unit into hexadecimal numbers containing two IRA characters (e.g. octet with integer value 42 is presented to TE as two characters 2A

(IRA 50 and 65)). In the case of CBS: <ra> GSM 03.40 TP-Recipient-

Address Ad-dress-Value field in string format; BCD numbers (or GSM default alphabet characters) are converted into characters; type of address given by <tora>.

<ra>

(num)(+CSCS)

Recipient Address

GSM 03.40 TP-Recipient-Address Address-Value field in string format;

BCD numbers (or GSM default alphabet characters) are converted to characters of the currently selected TE character set (refer to

command AT+CSCS .

); type of address given by <tora>.

<sca>

(num)(+CSCS)

Service Center Address

GSM 04.11 RP SC address Address-Value field in string format; BCD numbers (or GSM default alphabet characters) are converted to characters of the currently selected TE character set (refer to

command AT+CSCS );

type of address given by <tosca>.

<scts>

(num)

Service Centre Time Stamp

GSM 03.40 TP-Service-Centre-Time-Stamp in time-string format (refer

<dt> )

<sn>

(num)

Serial Number

GSM 03.41 CBM Serial Number in integer format

<st>

(num)

Status

GSM 03.40 TP-Status in integer format

0...255

<stat>

(str)

Message status

3GPP 27.005 Interface of SMS and CB. Indicates the status of message in memory .


Page 200


Description

Received unread messages

Received read messages

Stored unsent messages

Stored sent messages

All messages

<toda>

(num) text mode

(

<mode>

=1)

"REC UNREAD"

"REC READ"

"STO UNSENT"

"STO SENT"

"ALL"

1

2

3

4

PDU mode

(

<mode>

=0)

0

Default

for SMS reading commands for SMS writing commands

Type of Destination Address

GSM 04.11 TP-Destination-Address Type-of-Address octet in integer format (when first character of <da> is + (IRA 43) default is 145, otherwise default is 129)

0...255

<tooa>

(num)

Type of Originating Address

GSM 04.11 TP-Originating-Address Type-of-Address octet in integer format (default refer <toda> )

<tora>

(num)

Type of Recipient Address

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

<tosca>

(num)

Type of Service Center Address

GSM 04.11 RP SC address Type-of-Address octet in integer format

(default refer <toda> )

11.2 AT+CMGC Send an SMS command

Syntax

Test Command

AT+CMGC=?

Write Command

If text mode (see

AT+CMGF =1

)

AT+CMGC= <fo> ,< ct> [,< pid> [,< mn> [,< da> [,< toda> ]]]] <CR>.

Text can be entered <

CTRL

-

Z

>/<

ESC

>

Write Command

If PDU mode (see

AT+CMGF =0

)

AT+CMGC= <length><CR> PDU can be entered <

CTRL

-

Z

>/<

ESC

>

Response(s)

OK

Response(s)

+ CMGC: <mr>[,<scts>] If sending fails

ERROR

+CMS ERROR

Response(s)

+ CMGC: <mr>[,<ackpdu>]

OK

If sending fails

ERROR

+CMS ERROR


GSM 07.05

● ●

Notes

• After invoking the commands

AT+CMGW ,

AT+CMGS

or

AT+CMGC

it is necessary to wait for the prompt ">" before entering text or PDU. After the prompt a timer will be started to observe the input.

• At baudrates below 19200 it is recommended to use the line termination character only (refer to

ATS3 ,

default <

CR

>) before entering the text or PDU.


Page 201


Use of the line termination character followed by the response formatting character (refer to

ATS4 ,

default <

LF

> can cause problems .

11.3 AT+CMGD Delete SMS message

Syntax

Test Command

AT+CMGD=?

Write Command

AT+CMGD= <index>

Response(s)

OK

Response(s)

OK

ERROR

+CMS ERROR


GSM 07.05

● ●


Write command deletes message from preferred message storage <mem1> location <index>.

Note

• If there is no SMS stored at the selected index, the response is OK too.

11.4 AT+CMGF Select SMS message format

Syntax

Test Command

AT+CMGF=?

Response(s) +

CMGF

: (list of supported <mode >s)

OK

Read Command

AT+CMGF?

Write Command

AT+CMGF= <mode>

Reference(s)

Response(s)

+CMGF: <mode>

OK

Response(s)

OK

PIN SERIAL

GSM 07.05

○ ●


The write command specifies the input and output format of the short messages.


<mode>

(num)(&W)(&V)

[0]

(&F)

PDU mode

11.5 AT+CMGL List SMS messages from preferred store

Syntax


Page 202


Test Command

AT+CMGL=?

Exec Command

AT+CMGL

Response(s) +CMGL: (list of supported <stat>s )

OK

Response(s)

+CMGL: (see write command for default of <stat> )

OK

Write Command

AT+CMGL= <stat>

Response(s)

Output if text mode

( AT+CMGF =1)

and command successful: For SMS- SUBMITs and/or SMS-DELIVERs

+CMGL: <index>,<stat>,<oa>/<da>,[<alpha>],[<scts>][,<tooa>/<toda>,<length>]

<data>

[…]

OK

For SMS-STATUS-REPORTs

+ CMGL: <index>,<stat>,<fo>,<mr >,[<ra>], [<tora>],<scts>,<dt>,<st>

[…]

OK

For SMS-Commands

+ CMGL: <index>,<stat>,<fo>,<ct>

[…]

OK

Output if PDU mode AT+CMGF =0

and command successful: For SMS-SUBMITs and/or SMS-DELIVERs

+ CMGL: <index>,<stat>,[<alpha>],<length> <pdu>

[…]

OK


ERROR

+CMS ERROR


GSM 07.05

● ●


The execute command is the same as the write command with the given default for <stat>.

The write command returns messages with status value <stat> from message storage <mem1> to the TE. If status of the message is 'received unread', status in the storage changes to 'received read'.

Notes

• The selected <mem1> can contain different types of SMs (e.g. SMS-

DELIVERs, SMS-SUBMITs, SMS-STA-TUS-REPORTs and SMS-COMMANDs), the response may be a mix of the responses of different SM types. TE application can recognize the response format by examining the third response parameter.

• The parameters <ra> and <tora> will only be displayed if parameter <ra> of

the AT^SSCONF command is set to 1.

• This command can be used only after the SMS data from the SIM have been read successfully for the first time. Reading starts after successful SIM authentication has been performed, and may take up to 30 seconds depending on the SIM used. While the read process is in progress, an attempt to use any of the SMS read commands will result in "+CME Error: 14"

(SIM busy).


Page 203


11.6 AT+CMGR Read SMS messages

Syntax

Test Command

AT+CMGR=?

Response(s)

OK

Write Command

AT+CMGR= <index>

Response(s)

Output if text mode (

AT+CMGF =1)

and command successful: For SMS-DELIVER

+ CMGR:

<stat>,<oa>,[<alpha>],<scts>[,<tooa>,<fo>,<pid>,<dcs>,<sca>,<tosca>,<length>]<dat a>

[…]

OK

For SMS-SUBMIT

+ CMGR:

<stat>,<da>,[<alpha>][,<toda>,<fo>,<pid>,<dcs>,[<vp>],<sca>,<tosca>,<length>]<dat a>

[…]

OK

For SMS-STATUS-REPORT

+ CMGR: <stat>,<fo>,<mr >,[<ra>], [<tora>],<scts>,<dt>,<st>

<data>

[…]

OK

For SMS-Commands

+CMGR: <stat>,<fo>,<ct>[,<pid>,[<mn>],[<da>],[<toda>],<length>] <data>

[…]

OK

Output if PDU mode (

AT+CMGF =0)

and command successful: For SMS-SUBMITs and/or SMS-DELIVERs

+ CMGR: <stat>,[<alpha>],<length> <pdu>

OK

ERROR

+CMS ERROR


GSM 07.05

● ●


The write command returns SMS message with location value <index> from message storage <mem1> to the TE. If status of the message is 'received unread', status in the storage changes to 'received read'.

Notes

• Response if AT+CMGR is used to read an empty record index: +CMGR: 0,,0

• Response if AT+CMGR

is used to read a non-existent record index: +CMS

ERROR: invalid memory index

• The parameters <ra> and <tora> will only be displayed if parameter <ra> of

the AT^SSCONF command is set to 1.


(SIM busy).


Page 204


11.7 AT+CMGS Send SMS message

Syntax

Test Command

AT+CMGS=?

Write Command

If text mode (see

AT+CMGF =1)

AT+CMGS= <da> [,< toda> ] <CR>

Text can be entered. <

CTRL

-

Z

>/<

ESC

>

Write Command

If PDU mode (see

AT+CMGF =0)

AT+CMGS=< length><CR>

PDU can be entered. <

CTRL

-

Z

>/<

ESC

>

Reference(s) PIN

Response(s)

OK

Response(s)

+ CMGS: <mr>[,<scts>]

OK

If sending fails see notes below.

Response(s)

+ CMGS: <mr>[,<ackpdu>]

OK

If sending fails see notes below

SERIAL

GSM 07.05

● ●


The write command transmits a short message from TE to network (SMS-

SUBMIT).

After invoking the write command wait for the prompt ">" and then start to write the message. To send the message simply enter <

CTRL

-

Z

>. After the prompt a timer will be started to observe the input. To abort sending use <

ESC

>.

Abortion is acknowledged with "OK", though the message will not be sent. The message reference <mr> is returned to the TE on successful message delivery.

The value can be used to identify the message in a delivery status report provided as an unsolicited result code.

Notes

• If sending fails, for example, if a message is too long, the result code depends on the current setting of the

AT

^

SM

2 0 command:

If the

AT

^

SM

2 0 <CmgwMode> equals 1 (factory default) any failure to send a message is responded with "OK". Users should be aware, that despite the "OK" response, the message will not be sent to the subscriber. If the

AT^SM20

<CmgwMode> equals 0 any failure to send a message is responded with "ERROR".

• If sending fails due to timeout, then

AT^SM20

<CmgwMode>=1 causes "+CMS ERROR: Unknown error" to be returned;

AT^SM20

<CmgwMode>=0 causes "+CMS ERROR: timer expired" to be returned.

• Note that some providers do not recognize an @ symbol used in a short message. A widely used alternative is typing "*" as defined in GSM 03.40

(GPP TS 23.40).

• All characters entered behind the prompt ">" will be recognized as GSM characters. For example, "Backspace" (ASCII character 8) does not delete a character, but will be inserted into the short message as an additional physical character. As a result, the character you wanted to delete still appears in the text, plus the GSM code equivalent of the backspace key.

• In text mode, the maximum length of an SMS depends on the used coding scheme: It is 160 characters if the 7 bit GSM coding scheme is used, and

140 characters according to the 8 bit GSM coding scheme.


Page 205


• At baudrates lower than 19200 it is recommended to use the line termination character only (refer to <n> of

ATS3 ,

default <

CR

>) before entering text or PDU. Use of the line termination character followed by the response formatting character (see <n> of

ATS4 ,

default <

LF

>) can cause problems.

11.8 AT+CMGW Write SMS messages to memory

Syntax

Test Command

AT+CMGW=?

Response(s)

OK

Exec Command

If text mode (see AT+CMGF =1):

AT+CMGW

Write Command

If text mode (see AT+CMGF =1):

AT+CMGW=< oa>/<da>[, [<tooa>/<toda>][,<stat>]]<CR>

Text can be entered. <

CTRL

-

Z

>/<

ESC

>

Write Command

If PDU mode (see

AT+CMGF =0):

AT+CMGW= <length>[,<stat>]<CR> PDU can be entered.

<

CTRL

-

Z

>/<

ESC

>

Reference(s) PIN

Response(s)

<

CR

> Text can be entered. <

CTRL

-

Z

>/<

ESC

>

+CMGW: <index>

OK

If writing fails

ERROR +CMS ERROR

Response(s)

+CMGW: <index>

OK

If writing fails see notes below.

Response(s)

+CMGW: <index>

OK

If writing fails see notes below.

SERIAL

GSM 07.05

● ●


The execute and write commands transmit SMS (either SMS-DELIVER or SMS-

SUBMIT) from TE to memory storage <mem2>. Memory location <index> of the stored message is returned. Message status will be set to 'stored unsent' unless otherwise given in parameter <stat>.

After invoking the execute or write command wait for the prompt ">" and then start to write the message. To save the message simply enter <

CTRL

-

Z

>. After the prompt a timer will be started to observe the input.

To abort writing use <

ESC

>. Abortion is acknowledged with "OK", though the message will not be saved.

Notes

• If writing fails, for example, if a message is too long, the result code depends on the current setting of the

AT

^

SM

2 0 command:

• If the

AT

^

SM

2 0 <CmgwMode>=1 (factory default) any failure to send a message is responded with "OK". Users should be aware, that despite the

"OK" response, the message will not be written to the selected SMS storage.

If the

AT^SM20

<CmgwMode> equals 0 any failure to write a message is responded with "ERROR".

• If writing fails due to timeout, then

• AT^SM20

<CmgwMode>=1 causes "+CMS ERROR: Unknown error" to be

returned; AT^SM20 <CmgwMode>=0

causes "+CMS ERROR: timer expired" to be returned.


Page 206


• Note that some providers do not recognize an @ symbol used in a short message. A widely used alternative is typing "*" as defined in GSM 03.40

(GPP TS 23.40).

• For baudrates lower than 19200 it is recommended to use the line

termination character only (refer to ATS3 =

<n>, default <

CR

>) before entering the text or PDU. Use of the line termination character followed by

the response formating character (see ATS4 =<n>,

default <

LF

>) may cause problems.

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

• All characters entered behind the ">" prompt will be recognized as GSM characters. For example, "Backspace" (ASCII character 8) does not delete a character, but will be inserted into the short message as an additional physical character. As a result, the character you wanted to delete still appears in the text, plus the GSM code equivalent of the backspace key.

• In text mode, the maximum length of an SMS depends on the used coding scheme: It is 160 characters if the 7 bit GSM coding scheme is used, and

140 characters according to the 8 bit GSM coding scheme.

• The length of 8-bit data coded short messages has to be greater than 0.

11.9 AT+CMSS Send SMS messages from storage

Syntax

Test Command

AT+CMSS=?

Write Command

If text mode (

AT+CMGF =1):

AT+CMSS= <index> [,< da> [,< toda> ]]

Write Command

If PDU mode (

AT+CMGF =0):

AT+CMSS= <index> [,< da> [,< toda> ]]

Response(s)

OK

Response(s)

+ CMSS: <mr> [,< scts> ]

OK

If sending fails

ERROR

+CMS ERROR

Response(s)

+ CMSS: <mr> [,< ackpdu> ]

OK

If sending fails

ERROR

+CMS ERROR


GSM 07.05

● ●


The write command sends message with location value <index> from message storage <mem2> to the network (SMS-SUBMIT or SMS-COMMAND). If new recipient address <da> is given for SMS-SUBMIT, it shall be used instead of the one stored with the message. Reference value <mr> is returned to the TE on successful message delivery. Value can be used to identify message upon unsolicited delivery status report result code. If the optional parameter <da> is given, the old status of the short message at <index> remains unchanged (see

<stat> ).


Page 207


11.10 AT+CNMA New SMS message acknowledge to

ME/TE, only phase 2+

Syntax

Test Command

AT+CNMA=?

Exec Command

AT+CNMA

Write Command

AT+CNMA= <n>

Response(s)

+CNMA: (list of supported <n>s)

OK

Response(s)

OK

ERROR

+CMS ERROR

Response(s)

OK

ERROR

+CMS ERROR


GSM 07.05

● ●


The write/execute command confirms successful receipt of a new message

(SMS-DELIVER or SMS-STATUS-REPORT) routed directly to the TE. TA shall not send another +CMT or +CDS result code to TE until previous one is acknowledged. If

ME does not receive acknowledgment within required time (network time-out),

ME sends RP-ERROR to the network. TA shall automatically disable routing to TE by setting both <mt> and <ds>

values of AT+CNMI to zero.


<n>

(num)

0 Parameter is only required for PDU mode. Command operates similarly as in text mode

Notes

• The execute/write command shall only be used when AT+CSMS parameter

<service> equals 1 (= phase 2+).

• Both the execute and the write command can be used no matter whether text mode or PDU mode is activated.

11.11 AT+CNMI New SMS message indications

Syntax

Test Command

AT+CNMI=?

Read Command

AT+CNMI?

Write Command

AT+CNMI = [<mode>][,<mt>][,<mb>] [,<ds>][,<bfr>]

Response(s)

+

CNMI

: (list of supported <mode>s ), ( list of supported <mt>s ),

(list of supported <bm>s ), ( list of supported <ds>s ), ( list of supported <bfr>s )

OK

Response(s)

+ CNMI: <mode>,<mt>,<bm>,<ds>,<bfr>

OK

Response(s)

OK

ERROR

+CMS ERROR


Page 208



GSM 07.05

● ●


URC1

<mt> =1:

+CMTI: <mem3>,<index>

Indicates that new message has been received

URC2

<mt> =2 (PDU mode enabled):

+ CMT: <length><CR><LF><pdu>


URC3

<mt> =2 (text mode enabled):

+CMT: <oa>,<scts>[,<tooa>,<fo>,<pid>,<dcs>,<sca>,<tosca>,<length

>] <CR><LF><data>


URC4

<bm>=2 (PDU mode enabled):

+ CBM: <length><CR><LF><pdu>

Indicates that new cell broadcast message has been received

URC5

<bm>=2 (text mode enabled):

+CBM: <sn>,<mid>,<dcs>,<page>,<pages><CR><LF><data>

Indicates that new cell broadcast message has been received

URC6

<ds>=1 (PDU mode enabled):

+ CDS: <length><CR><LF><pdu>

Indicates that new SMS status report has been received

URC7

<ds>=1 (text mode enabled):

+CDS: <fo>,<mr>[,<ra>] [,< tora>] ,< scts>,<dt>,<st> Indicates that new

SMS status report has been received

URC8

<ds> =2:

+CDSI: <mem3>,<index>

Indicates that new SMS status report has been received


The write command selects the procedure how the receipt of new SMS messages from the network is indicated to the TE when TE is active, e.g. DTR signal is ON. If TE is inactive (e.g. DTR signal is OFF), message receiving should be done as specified in GSM 03.38. If the DTR signal is not available or the state

of the signal is ignored (V.25ter command AT&D O,

reliable message transfer

can be assured by using AT+CNMA

acknowledgment procedure. The rules

<mt>=2 and <mt>=3 for storing received SM are possible only if phase 2+ compatibility is activated with

AT+CSMS =1

. The parameter <ds>=1 is only available in phase 2+.


Page 209



<mode>

(num)(&W)

[0]

(&F)

Buffer unsolicited result codes in the TA. If TA result code buffer is full, indications can be buffered in some other place or the oldest indications may be discarded and replaced with the new received indications.

1 Discard indication and reject new received message unsolicited result codes when TA-TE link is reserved (e.g. in on-line data mode). Otherwise forward them directly to the TE.

2

3

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.

Forward unsolicited result codes directly to the TE. TA-TE link specific in-band technique used to embed result codes and data when TA is in on-line data mode.

<mt>

(num)(&W)(&V)

Rules for storing received SMS depend on the relevant data coding method (refer to GSM 03.38), preferred memory storage

( AT+CPMS )

setting and this value.

Note: If AT command interface is acting as the only display device, the ME must support storage of class 0 messages and messages in the message waiting indication group (discard message).

[0]

(&F)

No SMS-DELIVER indications are routed to the TE.

1 If SMS-DELIVER is stored in ME/TA, indication of the memory location is routed to the TE using unsolicited result code:

2

3

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:

Class 3 SMS-DELIVERs are routed directly to the TE using unsolicited result codes defined in <mt>=2 . Messages of other data coding schemes result in indication as defined in <mt>=1.

<bm>

(num)(&W)(&V)

Rules for storing received CBMs depend on the relevant data coding method (refer to GSM 03.38), the setting of Select CBM Types

(

AT+CSCB )

and this value :

[0]

(&F)

No CBM indications are routed to the TE.

2 New CBMs are routed directly to the TE using unsolicited result code:

3 Class 3 CBMs are routed directly to TE using unsolicited result codes defined in <bm>=2.

<ds>

(num)(&W)(&V)

[0]

(&F)

No SMS-STATUS-REPORTs are routed to the TE.

1 SMS-STATUS-REPORTs are routed to the TE using unsolicited result code:


Page 210


2 If SMS-STATUS-REPORT is routed into ME/TA, indication of the memory location is routed to the TE using unsolicited result code:

<bfr>

(num)(&W)(&V)

[1]

(&F)

TA buffer of unsolicited result codes defined within this command is cleared when <mode> 1...3 is entered .

< index >

(num) integer type; value in the range of location numbers supported by the associated memory

Notes

• Each time an SMS or Cell Broadcast Message is received, the Ring Line goes Logic "1" for one second.

• Parameters <mt>=2,3 and <ds>=1 are only available with GSM phase 2+

(see

AT+CSMS =1).

Incoming SMS or Status Reports have to be

acknowledged with AT+CNMA =0

when using these phase 2+ parameters.

• Due to GSM 03.38 the ME treats short messages with message class 0 as though there was no message class, i.e. it will ignore bits 0 and 1 in the TP-

DCS and normal rules for memory capacity exceeded shall apply.

• To allow SMS overflow presentation during data transfers via Break, use

AT+CNMI =3,1

(see AT^SMGO ).

11.12 AT+CPMS Preferred SMS message storage

Syntax

Test Command

AT+CPMS=?

Read Command

AT+CPMS?

Write Command

AT+CPMS= <meml> [, <mem2> [, <mem3> ]]

Response(s)

+CPMS: (list of supported <meml>s ), (list of supported <mem2>s ),

(list of supported <mem3>s )

OK

Response(s)

+ CPMS:

<meml>,<usedl>,<totall>,<mem2>,<used2>,<total2>,<mem3>,<used

3>,<total3>

OK

ERROR

+CMS ERROR

Response(s)

+CPMS: <usedl>,<total1> >,< used2>,<total2>,<used3>,

<total3>

OK

ERROR

+CMS ERROR


GSM 07.05

● ●


The write command selects memory storages <memi>,<mem2>,<mem3> to be used for reading, writing, etc.


<usedl>

(num)

Number of messages currently in <mem1>

<used2>

(num)


Page 211



<used3>

(num)


<totall>

(num)

Number of messages storable in <mem1>

<total2>

(num)

Number of messages storable in <mem2>

<total3>

(num)

Number of messages storable in <mem3 >

Notes

• The Mobile Equipment storage "ME" offers space for 25 short messages, see

<memi>.

• "MT" is the sum of "ME" (= 25 locations) and "SM" (capacity varies with SIM card). The indices <index> of the "MT" storage are dependent on the order selected with

AT^SSMSS .

• The <memi>,<mem2> and <mem3> parameter will be stored in non-volatile memory.

• The user should be aware that the setting "MT" involves "ME" and "SM", with

"ME" being filled up first. If the "ME" storage is full, TANGO55/56 will proceed with the "SM" storage.

• Incoming Class 1 short messages (ME specific) will be preferably stored to

"ME" and may be transferred to the "SM" storage if "ME" is used up.

• Incoming Class 2 messages (SIM specific) will be stored to the SIM card only, no matter whether or not there is free "ME" space. As a result, the

^

SMGO: 2 indication (see

AT^SMGO )

may be presented without prior indication of

^

SMGO: 1. For more information regarding SIM and ME specific message classes refer to <dcs> and the following specifications:

GSM 03.38 and 3GPP TS23038.

• When <mem3> is switched over from "MT" to "SM" all free "ME" locations will be filled with dummy short messages. This procedure can take up to 35 seconds, until all the 25 records are written.

• If switching from "MT" to "SM" was not finished due to error or user break, the value of <mem3> remains "MT", but some of the dummy records remain in the "ME" storage. These records have to be deleted manually. When

<mem3> equals "SM", do not delete the dummy messages in the "ME", storage. They will be automatically deleted when you switch back from

"SM" to "MT". Again, this may take up to 35 seconds. If switching from "SM" to

"MT" was not finished due to an error or user break, the value of <mem3> remains "SM", but the "ME" storage will no longer be filled with dummy records. New incoming short messages may now be written to the "ME"

storage, if "SM" is already full. To avoid this, repeat the AT+CPMS

command as soon as possible to switch <mem3> back to "MT". As an alternative, you

can manually delete the dummy records and issue AT+CPMS =MT,MT,MT.

• While <mem3> equals "SM" and <mem1> equals "ME" it is possible that, after deleting short messages from "ME", the freed space on "ME" is reclaimed for new incoming short messages, when there is no space left on the "SM" storage. As it is often the clients concern to have received short messages stored only to the SIM card, inconsistent settings should be generally avoided. This can be achieved simply by using the same parameter for all memory indices.


Page 212


• The indices <index> of the storage are dependent on the order selected

with AT^SSMSS .

11.13 AT+CSCA SMS service centre address

Syntax

Test Command

AT+CSCA=?

Read Command

AT+CSCA?

Response(s)

OK

Response(s)

+CSCA: <sca>,<tosca>

OK

Response(s)

OK

Write Command

AT+CSCA= <sca> [,< tosca> ]


GSM 07.05

● ●


Write command updates the SMSC address, through which mobile originated

SMS are transmitted. In text mode, setting is used by send and write commands. In PDU mode, setting is used by the same commands, but only when the length of the SMSC address coded into <pdu> parameter equals zero.

Notes

• In case of using no parameter after AT+CSCA= the content of <sca> will be deleted.

• This command writes the service centre address to non-volatile memo.

• The SMS service centre address should be entered as specified by the service provider.

11.14 AT+CSCB Select Cell Broadcast Message

Indication

Syntax

Test Command

AT+CSCB=?

Read Command

AT+CSCB?

Write Command

AT+CSCB=[<mode>[,< mids> [,< dcss> ]]]

Reference(s)

Response(s)

+CSCB: (list of supported <mode>s )

OK

Response(s)

+ CSCB: <mode>,<mids>,<dcss>

OK

Response(s)

OK

PIN SERIAL

GSM 07.05

● ●


Test command returns supported modes as a compound value.

Write command selects which types of CBMs are to be received by the ME.



Page 213


<mode>

(num)

Message mode

[0] Accept messages that are defined in <mids> and

<dcss>

1 Forbid messages that are defined in <mids> and <dcss>

<mids>

(str)

Cell Broadcast Message ID specification

For <mode>=0: Six different possible combinations of

CBM IDs (e.g. "0,1,5,320-478,922,2000-3000"), default is empty string.

In certain configurations, e.g. if using SIMs that contain data in Elementary File EF-CBMID (Cell Broadcast

Message Identifier for Data download) less than six combinations may be available. To access a SIMs

Elementary File data refer to command

AT+CRSM .

For <mode>=1 : One CBM ID or range of IDs (e.g. "320-

478"), default is empty string.

<dcss>

(str)

CBM data coding scheme specification

All different possible combinations of CBM data coding schemes

(e.g. "0-3,5"). Using default empty string leads to get all CBMs independent of their dcss.

A given <dcss> replaces any former value and is used for consecutive requests.

11.15 AT+CSDH Show SMS text mode parameters

Syntax

Test Command

AT+CSDH=?

Read Command

AT+CSDH?

Write Command

AT+CSDH= <show>

Response(s)

+CSDH: (list of supported <show> s)

OK

Response(s)

+CSDH: <show>

OK

Response(s)

+CSDH: <show>

OK


GSM 07.05

● ●


Write command sets whether or not detailed header information is shown in text mode result codes.


<show>

(num)(&W)

[0]

(&F)

Do not show header values defined in commands

AT+CSCA

and

AT+CSMP

(<sca>,<tosca>,<fo>,<vp>,<pid> and <dcs>) nor

<length>,<toda> or <tooa> in "+

CMTI

",

AT+CMGL ,

AT+CMGR

result codes for SMS-DELIVERs and SMS-


Page 214


1

SUBMITs in text mode; for SMS-COMMANDs in +CMGR result code, do not show

<pid>,<mn>,<da>,<toda>,<length> or <cdata>.

Show the values in result codes.

11.16 AT+CSMP Set SMS text mode parameters

Syntax

Test Command

AT+CSMP=?

Read Command

AT+CSMP?

Write Command

AT+CSMP= <fo>[,<vp>/<scts>[,<pid>[,<dcs>]]]

Response(s)

OK

Response(s)

+ CSMP: <fo> ,< vp>/<scts> ,< pid> ,< dcs>

OK

Response(s)

+CSMP: <index>

OK

If sending fails

ERROR

+CMS ERROR


GSM 07.05

● ●


The write command selects 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 <f o>. If TA supports the enhanced validity period format, see GSM 03.40), it shall be given as a hexadecimal coded string (e.g. <pdu> ) with quotes.


<fo>

(num)

First Octet depending on the command or result code: first octet of GSM

03.40 SMS-DELIVER, SMS-SUBMIT (default 17), SMS-STATUS-REPORT, or

SMS-COMMAND (default 2) in integer format

0...17

(&F)

...255

<vp>

(num)

Depending on SMS-SUBMIT <fo> setting: GSM 03.40 TP-Validity-Period either in integer format or in time-string format (refer <dt> )

0...167

(&F)

...255

<dcs>

(num)

Data Coding Scheme

GSM 03.38 SMS Data Coding Scheme, or Cell Broadcast Data

Coding Scheme in integer format

0

(&F)

...247

<pid>

(num)

Protocol Identifier


Page 215


GSM 03.40 TP-Protocol-Identifier in integer format

0<

&F

>...255

Notes

• When storing a SMS DELIVER from the TE to the preferred memory storage in

text mode (using the AT+CMGW

write command),< vp> field can be used for <scts> .

• The command writes the parameters to the non-volatile memory.

11.17 AT+CSMS Select Message Service

Syntax

Test Command

AT+CSMS=?

Read Command

AT+CSMS?

Write Command

AT+CSMS= <service>

Response(s)

+CSMS: (list of supported <service> s)

OK

Response(s)

+ CSMS: <service>,<mt>,<mo>,<bm>

OK

Response(s)

+ CSMS: <mt>,<mo>,<bm>

OK

ERROR

+CMS ERROR


GSM 07.05

● ●


<service>

(num)

0 GSM 03.40 and GSM 03.41 (the syntax of SMS AT commands is compatible with GSM 07.05 Phase 2 version

4.7.0; Phase 2+ features which do not require new command syntax may be supported, e.g. correct routing of messages with new Phase 2+ data coding schemes).

1 GSM 03.40 and GSM 03.41 (the syntax of SMS AT commands is compatible with GSM 07.05 Phase 2+ version; the requirement of <service> setting 1 is mentioned under corresponding command descriptions).

<mt>

(num)

Mobile Terminated Messages:

0 Type not supported

<mo>

(num)

Mobile Originated Messages:


<bm>

(num)

Broadcast Type Messages:


Notes


Page 216


• If CSMS mode is switched from Phase 2+ to Phase 2 and one or more

AT+CNMI parameter are Phase 2+ specific a '+CMS ERROR: unknown error' will appear. It is recommended to switch the AT+CNMI

parameters to

Phase 2 specific values before entering Phase 2.

• Phase 2+ ( <service>=1 ) must be set before the following features can be used:

-

-

-

Configuring procedures for indicating received short messages with the

AT+CNMI parameters <mt>=2 or <mt>=3 and

<ds>=1.

Acknowledging incoming short messages with

AT+CNMA .

Receiving Status Reports and acknowledging them with

AT+CNMA .

11.18 AT

^

SLMS List SMS Memory Storage

Syntax

Test Command

AT^CLMS=?

Exec Command

AT^SLMS

Response(s)

OK

Response(s)

^SLMS: "MT" <total3>,<used3>

^SLMS: "SM" ,<totall>,<used1>

^SLMS: "ME" ,<total2>,<used2>

OK

ERROR

+CMS ERROR

Reference(s)

SIEMENS

PIN

●

SERIAL

●


The execute command indicates the maximum capacity of each SMS storage type and the number of locations currently used.


<total1>

(num)

Maximum number of messages storable in the SMS memory of the

SIM (physical storage "SM")

<total2>

(num)

Maximum number of messages storable in the SMS memory of the

Mobile Equipment (physical storage "ME")

<total3>

(num)

Sum of "SM" and "ME", indicated as "MT". Maximum number of all messages storable in the SIM memory and the Mobile Equipment memory.

<usedl>

(num)

Number of messages currently stored in the SMS memory of the SIM

(physical storage "SM")

<used2>

(num)

Number of messages currently stored in the SMS memory of the Mobile

Equipment (physical storage "ME")

<used3>

(num)


Page 217


Concatenated logical SMS storages of SIM ("SM") and Mobile

Equipment ("ME"). Sum of all messages currently stored, indicated as

"MT".

11.19 AT

^

SMGL List SMS messages from preferred store without setting status to REC READ

Syntax

Test Command

AT^SMGL=?

Response(s) same as

AT+CMGL

Exec Command

AT^SMGL

Write Command

AT^SMGL= <stat>

Reference(s)

Response(s)

^SMGL: (For default values of <stat> , see Chapter "

SMS parameters”.)

OK

Response(s) same as

AT+CMGL

SIEMENS

PIN

●

SERIAL

●


The execute command is the same as the write command, but uses the given default of <stat> .

The write command allows to select a status type and lists, from the message storage <memi> , all messages that currently have the specified <stat> . The major difference over the standard command

AT+CMGL

is that the status of the listed messages remains unchanged (unread remains unread).

Notes

•

The selected <mem1> can contain different types of SMs (e.g. SMS-

DELIVERs, SMS-SUBMITs, SMS-STA-TUS-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.


(SIM busy)

11.20 AT

^

SMGO Set or query SMS overflow presentation mode or query SMS overflow

Syntax

Test Command

AT^SMGO=?

Response(s)

^SMGO: (list of supported <n> s)

OK


Page 218


Read Command

AT^SMGO?

Write Command

AT^SMGO= <n>

Response(s)

^SMGO: <n>,<mode>

OK

ERROR

+CMS ERROR

Response(s)

OK

ERROR

CME ERROR

Reference(s)

SIEMENS

PIN

●

SERIAL

●


SMS buffer change:

^SMGO: <mode>

Status of SMS buffer has changed.


The read command returns overflow presentation mode and SMS overflow status. The write command sets overflow presentation mode.


<n>

(num)(&W)(&V)

SMS overflow presentation mode

[0]

(&F) disable

1 enable

<mode>

(num)(&V)

SMS overflow status

1

2

SMS buffer full (The buffer for received short messages is

<mem3>. See

AT+CPMS

.)

Buffer full and new message waiting in SC for delivery to phone

Notes

• Incoming short messages with message class 1 (ME specific short messages) or class 2 (SM specific short messages), see <dcs> in GSM 03.38, will be stored either in "ME" or in "SM" storage. Therefore the "^

SMGO

:2" indication could occur, without issuing the indication "^

SMGO

:1" before. The indication "^

SMGO

:1" means that both buffers ("ME" and "SM") are full.

• For more information regarding SIM and ME specific message classes refer to <dcs> and the following specifications: GSM 03.38 and 3GPP TS 23.038 .

11.21 AT

^

SMGR Read SMS message without setting status to REC READ

Syntax

Test Command

AT^SMGR=?

Response(s)

^SMGR:

OK


Page 219


Write Command

AT^SMGR= <index>

Response(s) see

AT+CMGR

Reference(s)

SIEMENS

PIN

●

SERIAL

●

Notes

• The

AT^SMGR

command is a specific Siemens command with the same

syntax as AT+CMGR

Read SMS message. The only difference is that the status "REC UNREAD" of a short message is not overwritten to "REC READ".


(SIM busy).

11.22 AT

^

SSCONF SMS Command Configuration

AT^SSCONF

controls details of some SMS releated commands. Please note that

AT^SSCONF settings are stored volatile, i.e. after restart or reset the default values will

be restored.

Syntax

Test Command

AT^SSCONF=?

Read Command

AT^SSCONF?

Write Command

AT^SSCONF= <ra>

PIN SERIAL

Response(s)

^SSCONF: list of supported <ra>s

OK

Response(s)

^SSCONF :<ra>

OK

Response(s)

OK

○ ●


<ra>

(num)

Display recipient address

[0]

(&F)

TANGO55/56 does not display <ra> and <tora>. These parameters are used with the result codes of

AT+CMGL ,

AT^SMGL ,

AT+CGMR ,

AT^SMGR and the URC

"+

CDS

" .

1 TANGO55/56 displays <ra> and <tora> .

11.23 AT

^

SSDA Set SMS Display Availability

This command allows to notify the TANGO55/56 of its controlling application's capability to immediately display incoming SMS on a display.

If the application is able to display incoming SMS, class 0 SMS shall be displayed immediately. However, if it does not, class 0 SMS shall be treated as if no message class is determined (GSM 03.38[14]).


Page 220


The effect of this command if <da>=1 is to determine the behavior of parameter

<mt>

of AT+CNMI :

If <da>=1 and <mt>=1 incoming class 0 SMS need to be acknowledged with

AT+CNMA (see also AT+CNMI and

AT+CSMS

).

Syntax

Test Command

AT^SSDA=?

Read Command

AT^SSDA?

Response(s)

^SSDA:list of supported <da> s

OK

Response(s)

^SSDA: <da>

OK

Response(s)

OK

Write Command

AT^SSDA= <da>


SIEMENS

○

●


The read command returns ME's current capability setting.


<da>

(num)

Display Availability

0

(&F)

Application is not able to display incoming SMS

1 Application is able to display incoming SMS

11.24 AT

^

SSMSS Set Short Message Storage Sequence

Syntax

Test Command

AT^SSMSS=?

Response(s)

^SSMSS: (list of supported) <seq>s

Read Command

AT^SCKS?

Response(s)

^SCKS: <mode>,<SimStatus>

OK

ERROR

+CME ERROR: <err>

Response(s)

OK

Write Command

AT^SSMSS= <seq>

Reference(s)

SIEMENS

PIN

○

SERIAL

●


The short message storage "MT" (see AT+CPMS ) is a logical storage. It consists of

two physical storages "ME" and "SM". This command allows to select the sequence of addressing this storage.


<seq>

(num)

MT sequence

0

(&F)

"MT" storage is "ME" then "SM


Page 221


1 "MT" storage is "SM" then "ME"

Note

• Access to the SIM storage is faster. For compatibility with previous software releases, the "MT" sequence <seq>=0 is the factory default.


Page 222


12 SIM RELATED COMMANDS

The AT commands described in this chapter are related to the Subscriber Identity

Modul (SIM) connected to the TANGO55/56.

12.1 AT+CRSM Restricted SIM Access

Syntax

Test Command

AT+CRSM=?

Response(s)

OK

Write Command

AT+CRSM= <command> [,< fileID> [,< P1> ,< P2 >,< P3> [

,< data> ]]]

Response(s)

+ CRSM: <swl>,<swl>,[<response>]

OK

ERROR

+CME ERROR: <err>


GSM 07.07

● ●


By using this command the TE has access to Elementary Files on the SIM.

Access to the SIM database is restricted to the commands which are listed at

<command> .

As response to the command the ME sends the current SIM information parameters and response data. ME error result code +CME ERROR may be returned if the command cannot be passed to the SIM, e.g. if the SIM is not inserted. However, errors related to SIM data are reported in <sw1> and <sw2> parameters as defined in GSM 11.11.


<command>

(num)

All values not listed below are reserved; refer GSM 11.11.

176 READ

178 READ RECORD

192 GET RESPONSE

214 UPDATE BINARY

220 UPDATE RECORD

<fileID>

(num)

242 STATUS

This is the identifier for an elementary data file on SIM. Mandatory for every command except STATUS

<P1>

(num)

Parameter to be passed on by the ME to the SIM; refer GSM 11.11.

0...255

<P2>

(num)


0...255

<P3>

(num)


Page 223



0...255

<data>

(str)

Information which shall be written to the SIM (hexadecimal character format)

<swl>

(num)

Status 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; refer GSM 11.11.

0...255

<sw2>

(num)

Status 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; refer GSM 11.11.

0...255

<response>

(str)

Response of a successful completion of the previously issued command.

STATUS and GET RESPONSE commands return data, which gives information about the current elementary data field. This information includes the type of file and its size (refer GSM 51.011).

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.

12.2 AT

^

SCKS Query SIM and Chip Card Holder Status

This command controls the SIM connection presentation mode and queries the connection status of the SIM and the card holder tray of the TANGO55/56.

Syntax

Test Command

AT^SCKS=?

Response(s)

^SCKS:(list of supported <mode> s)

OK

Read Command

AT^SCKS?

Write Command

AT^SCKS= <mode>

Response(s)

^SCKS: <mode>,<SimStatus>

OK

ERROR

+CME ERROR: <err>

Response(s)

OK

ERROR

+CME ERROR: <err>

Reference(s)

SIEMENS


^SCKS: <SimStatus>

PIN

○

SERIAL

●


Page 224


During startup, and if the TANGO55/56's SIM connection status has changed an unsolicited result code (URC) is issued.


The read command returns the URC presentation mode and the status of the

SIM card connection.

The write command enables or disables the presentation of URCs to report whether or not the SIM card is connected.

If the ME is powered down or reset (

AT+CFUN

or

Table 2.3

)

the current presentation mode setting <mode> will not be retained. Therefore the setting

<mode>=1 needs to be restored after power on the TANGO55/56 or may be saved in the user profile

( AT&W )

.


<mode>

(num)(&W)(&V)

0

(&F)

Suppress unsolicited result codes

1 Output unsolicited result codes

<SimStatus>

(num)(&V)

0 Card holdertray removed or SIM connection error

1 SIM inserted (refer to note)

Note

• <SimStatus> reflects the status of the SIM and the card holdertray.

Therefore if an empty SIM card tray is inserted, two URCs will be presented, indicating the status 1 followed by 0, i.e. a SIM is inserted into the card holdertray but no SIM connection could be established.

Example:

AT

^

SCKS

=

I

Activates the presentation of unsolicited result codes

OK

Now, after inserting an empty card tray the following URCs appear:

^

SCKS: 1

^

SCKS

: 0

Tray connected

No SIM card found

12.3 AT

^

SCID Display SIM card identification number

Syntax

Test Command

AT^SCID=?

Response(s)

OK

Exec Command

AT^SCID

Response(s)

^SCID: <cid>

OK

ERROR

+CME ERROR: <err>

Reference(s)

SIEMENS

PIN

○

SERIAL

●


TA returns the card identification number in SIM (SIM file EF|

CaD

, see GSM 11.11

Chap.10.1.1) as string type.



Page 225


<cid>

(str) card identification number of SIM card

12.4 AT+CXXCID Display card ID

Syntax

Test Command

AT+CXXCID=?

Response(s)

OK

Exec Command

AT+CXXCID

Response(s)

+CXXCID: <cid>

OK

ERROR

+CME ERROR: <err>


SIEMENS

○

●


TA returns the card identification number in SIM (SIM file EF ICCID, see GSM

11.11 Chap.10.1.1) as string type.

Note

• See also:

AT^ACID


Page 226


13 PHONE BOOK COMMANDS

The AT commands described in this chapter allow the external application to access the phone books located in the TANGO55/56's memory or on the attached

Subscriber Identity Modul (SIM).

13.1 Sort Order for Phone books

Due to the support of UCS2 for the <text> part of phone book entries, the sort order for phone book records follows the algorithm published as Unicode Technical

Standard #10, "Unicode Collation Algorithm". A memory-optimized version of the proposed collation tables "[AllKeys]" from Unicode Technical Standard #10 is used in order to determine collation weights for code points between 0000 and 06FF, and composed keys are used for code points from ranges 0700 to 33FF, A000 to D7FF and

E000 to FFFD. Code Points not referenced in these tables will be assigned a default collation weight with their Unicode value as level 1 weight. Decomposition is not supported.

Phone book entries whose names contain only characters from the GSM07.07 default alphabet are converted internally into their UCS2 equivalents in order to achieve consistent sorting results.

For the user, this means that:

• Punctuation marks and other non-alphabetical characters from the common latin-based character sets, and from the standard GSM character set, will be sorted before any alphabetical characters. The ordering in which these marks appear as compared to other nonalphabetical characters from the same group is determined by their collation weights and does not reflect their code values in the UCS2 or

GSM alphabet tables above. Please refer to www.unicode.org for detail.

• Alphabetical characters from the common latin-based character sets, and from the standard GSM character set, will be sorted according to their underlying base characters, plus the collation weights of their accent signs.

• Only collation levels 1 and 2 are regarded, so sorting is not case-sensitive.

Example: the european letters "A" (GSM 0EH, UCS2 00C5h), "ae" (GSM 1DH, UCS2

00E6h), "c" (GSM09h, UCS2 00E7h), "a" (GSM 61H, UCS2 0061 h ) and "b" (GSM 62H,

UCS2 0062h) will be sorted in order "a", "A", "as" "b","c" although their numerical values in GSM and UCS2 suggest a different ordering.

Unicode Technical Standard #10,

"Unicode C ollation Algorithm"

13.2 AT+CPBR Read from Phone book

This command serves to read one or more entries from the phone book selected with AT command

AT+CPBS . It can be used only after the phone book's data has

been read from the SIM successfully. Reading starts after successful SIM authentication has been performed and may take up to 30 seconds depending on the SIM used. While this read process is in progress, an attempt to use any of the phone book commands will result in "+CME Error: SIM busy".

Syntax


Page 227


Test Command

AT+CPBR=?

Write Command

AT+CPBR= <locationl> [,< location2> ]

Response(s)

+ CPBR: (1<maxloc> ),< nlength> ,< tlength>

OK

+CME ERROR

Response(s)

[+CPBR: <locationl> ,< number> ,< type> ,< text> ]

[+CPBR: <location2> ,< number> ,< type> ,< text> ]

OK

+CME ERROR


GSM 07.05, GSM 11.11

● ●


The test command returns the location range supported by the current phone book storage, the maximum length of <number> field and the maximum length of <text> field. Note: Length information may not be available while SIM storage is selected. If storage does not offer format information, the format list contains empty parenthesizes.

The write command determines the phone book entry to be displayed with

<location1> or a location range from <location1> to <location2> .

Hence, if no

<location2> is given only the entry at <location1> will be displayed. If no entries are found at the selected location "OK" will be returned.


<locationl>

(num)

The first (lowest) location number within phone book memory for which the corresponding entry is to be displayed. The supported range is given in the test command response.

If <location1> exceeds the upper bound <maxloc> (as indicated by the test command), command will respond with "+CME ERROR:

INVALID INDEX".

<location2>

(num)

The last (highest) location number within phone book memory for which the corresponding entry is to be displayed. The supported range is given in the test command response.

If both <location1> and <location2> are in the range indicated by the test command with parameter <max-loo> , the list of entries will be output and terminated with "OK".

If <location2> exceeds the range indicated by the test command with parameter <maxloc> , the list of entries will be output but terminated with "+CME ERROR: INVALID INDEX".

<number>

(str)

Phone number in format specified by <type> , it may be an empty string.

<type>

(num)

Address type string includes international access code character'+'

209 dialling string <number> contains printable nonalphabetic non-digit characters saved with the number string.


Page 228


For phone book entries with this <type> , dialling from phone book with ATD><mem><n> is not possible. For further detail, check the parameter descriptions for at command

AT+CPBW .

129 otherwise

<text>

(str)(+cscs)

Text assigned to a phone number. The maximum length for this parameter is given with test command response parameter

<tlength> .

If using an ASCII terminal characters which are coded differently in

ASCII and GSM have to be entered via escape sequences as

described in chapter 0.5

Supported character sets

.

<maxloo>

(num)

Maximum location number for the currently selected storage. For phone books located on the SIM this value depends on the SIM card type.

<nlength>

(num)

Maximum length of phone number for "normal" locations.

Depending on the storage a limited number of locations with extended memory is available per phone book. These locations allow storing numbers with twice the standard length, which is

2*<nlength> digits for normal numbers, but only <nlength> digits for numbers saved with <type> =209.

<tlength>

(num)

Maximum length of <text> assigned to the telephone number. The value indicated by the test command is given in octets. If <text> is given as GSM characters each character corresponds to one octet.

If the <text> string is given in UCS2, the maximum number of characters depends on the coding scheme used for the alpha field of the SIM according to GSM 11.11, Annex B [16] . As a worst case the number of UCS2 characters is less than half the number of GSM characters. For a detailed description please refer to GSM 11.11,

Annex B [15] .

Examples:

EXAMPLE 1

First run the test command to find out the maximum range of entries stored in the active phone book

AT+CPBR=?

+ CPBR: (1-100) ,20,17

TANGO55/56 returns the supported values, where 100 is the supported range of location numbers, 20 is the length of the phone number and 17 is the maximum length of the associated text.

EXAMPLE 2

Then use the execute command to display the phone book entries sorted by location numbers

AT+CPBR =1,3

+CPBR:1,"+999999",145,"Charlie"+CPBR:2," + 777777",145, "Bill"

+CPBR:3,"+888888",145,"Arthur"


Page 229


13.3 AT+CPBS Select phone book memory storage

This command is used to select the active phone book storage, i.e. the phone book storage that all subsequent phone book commands will be operating on.

The read command can be used only after the phone book data from the SIM have been read successfully for the first time. Reading starts after successful SIM authentication has been performed, and may take up to 30 seconds depending on the SIM used. While the read process is in progress, an attempt to use any of the phone book commands will result in "+CME Error: 14" (SIM busy).

Syntax

Test Command

AT+CPBS=?

Read Command

AT+CPBS?

Write Command

AT+CPBS= <storage>

Response(s)

+CPBS: (list of supported <storage> s)

OK

+CME ERROR

Response(s)

+ CPBS: <storage> ,< used> ,< total>

OK

+CME ERROR

Response(s)

OK

+CME ERROR:


GSM 07.05

● ●


The test command returns supported <storage>s as compound value.

The read command returns the currently selected <storage> , the number of

<used> entries and the <total> number of entries available for this storage.

The write command selects the phone book memory <storage> , which is used by other phone book commands.


<storage>

(str)

For phone books "MC", "RC" and "LD", automatic deletion of the entries stored in ME will be performed if the SIM card is changed. If the same SIM is removed and reinserted, no automatic deletion is performed. Calls made after last switch on will be lost from "MC",

"RC" and "LD" phone book, if the SIM is removed and reinserted during normal operation

"FD" Fixed dialling phone book capacity: depending on SIM card

"SM"

(&F)

"ON"

"ME" location: SIM

IM phone book capacity: depending on SIM card location: SIM

SISDN list capacity: depending on SIM card location: SIM

Mobile Equipment Phone book capacity: max. 250 entries


Page 230


"LD" location: ME last number dialled phone book. Stores all voice call numbers dialed with

ATD , but no data call

numbers.

capacity: max. 10 entries location: depending on SIM this phone book may reside partly or completely in ME

AT command +CPBW is not applicable to this storage. The LD list can be deleted with

AT^SDLD

or with

AT^SPBD .

"MC"

"RC" issed (unanswered received) calls list capacity: max. 10 entries location: ME

+CPBW is not applicable to this storage. The

MC list can be deleted with AT^SPBD .

Received calls list capacity: max. 10 entries location: ME

+CPBW is not applicable to this storage. The RC list can be deleted with

AT^SPBD .

<used>

(num) value indicating the number of used locations in selected memory storage.

<total>

(num) value indicating the maximum number of locations allowed in the selected memory storage.

13.4 AT+CPBW Write into Phonebook

This command serves to write onto an entry of the phone book selected with

AT+CPBS .

It can be used only after the phone book's data has been read successfully from the SIM. Reading starts after successful SIM authentication has been performed and may take up to 30 seconds depending on the SIM used. While the read process is in progress, an attempt to use any of the phone book commands will result in "+CME Error: SIM busy".

Syntax

Test Command

AT+CPBW=?

Write Command

AT+CPBW=[ <location> ][,< number> [[,< type> ][,< text> ]

]]

Response(s)

+ CPBW: (1<maxloc> ),< nlength> , (list of supported

<type> s),< tlength>

OK

ERROR

+CME ERROR

Response(s)

OK

ERROR

+CME ERROR


GSM 07.07

● ●



Page 231


The test command returns the location range supported by the current storage, the maximum length of <number> field, the range of supported

<type> values and the maximum length of <text> field. Note: The length may not be available while SIM storage is selected. If storage does not offer format information, the format list contains empty parenthesizes.

The write command fills a phone book entry at memory location <location> of the active storage selected with

AT+CPBS .

If <storage>="FD" (SIM fixed dialling numbers) is selected, PIN2 authentication has to be performed prior to any write access.

If no <location> is given, the first free entry will be used.

If <location> is given as the only parameter, the phone book entry specified by

<location> is deleted.

If write attempt fails "+CME ERROR" is indicated.


<location>

(num)

Location number within phone book memory.

The supported range is given with the test command response.

<number>

(str)

Phone number with format specified by <type> . Parameter must be present, although it may be an empty string. However, alphabetic characters are not permitted.

<number> may contain printable non-alphabetic characters of the standard GSM alphabet as dialstring modifiers, including "*", "#" or"+".

However, if <number> contains modifiers otherthan "*", "#" or"+" the following constraints shall be considered:

• If no <type> was specified explicitly, all accepted modifiers from the GSM alphabet will be saved in the number string.

<type> will be set to 209 (ASCII). However, limitations as listed below for <type> 209 apply.

• A <number> saved with <type>=209 requires double memory.

In order to fit into a standard location, the number needs to be reduced to a maximum length of <nlength>/2 , including all digits and dial string modifiers. Extended locations may be used as stated below for <nlength> .

<type>

(num)

Type of address octet

If <type> is specified as 129 or 145, any non-digit characters otherthan "*", "#", or"+" will be removed from the number string. If the number string contains such characters, they can be saved with the number string by using <type> 209, see below.

string includes international access code character'+'

209 dialling string <number> contains printable nonalphabetic non-digit characters that should be saved with the number string. Remarks as under parameter

<number> apply. For phone book entries with this type, dialling from phone book with ATD><mem><n> is not possible.

129 otherwise

<text>

(str)(+cscs)


Page 232


Text assigned to the phone number. The maximum length for this parameter is given in test command response <tlength> . When using an ASCII terminal, characters which are coded differently in ASCII and GSM have to be entered via escape sequences as described in chapter

0.5

“ Supported character sets” .

<maxloo>

(num)

Max. location for the currently selected storage. For phone books located on SIM, this value may vary between SIM cards. See

AT+CPBS for typical values.

<nlength>

(num)

Max. length of phone number for "normal" locations. - Depending on the storage, a limited number of locations with extended memory is available per phone book. These locations allow storing numbers with twice the standard length, which is 2*<nlength> digits for normal numbers, but only <nlength> digits for numbers saved with parameter <type>= 209. If all extended locations of the selected phone book are used up, then any attempt to write a number which requires extended memory will be denied with CME ERROR 260:

INVALID DIAL STRING.

<tlength>

(num)

Maximum length of <text> assigned to the telephone number. The value indicated by the test command is given in octets. If the <text> string is given in GSM characters, each character corresponds to one octet. If the <text> string is given in UCS2, the maximum number of characters depends on the coding scheme used for the alpha field of the SIM according to GSM 11.11, Annex B [16] . As a worst case the number of UCS2 characters is less than half the number of

GSM characters. For a detailed description please refer to GSM

11.11, Annex B [15] .

Examples:

EXAMPLE 1

Make a new phone book entry at the first free location.

AT+CPBW=1,"+431234567",145,"international"

Delete entry at location 1

AT+CPBW=1

EXAMPLE 2

The following examples are provided to illustrate the effect of writing phone book entries with different types of dial string modifiers in

<number>

AT+CPBW=5,"12345678",,"Arthur"

AT+CPBW=6,"432!+-765()&54*654#",,"John"

AT+CPBW=7,"432!+-765()&54*654#",129,"Eve"

AT+CPBW=8,"432!+-765()&54*654#",145,"Tom"

AT+CPBW=9,"432!+-765()&54*654#",209,"Richard"

EXAMPLE 3

Read phone book entries from locations 5 - 9 via AT+CPBR

+CPBR:5,"12345678",129,"Arthur"

+CPBR:6,"432!+-765()&54*654#",209,"John"

+CPBR:7,"432+76554*654#",129,"Eve"

+CPBR:8,"+432+76554*654#",145,"Tom"


Page 233


+CPBR:9,"432!+-765()&54*654#",20 9,"Richard"

13.5 AT^SPBC Search the first entry in the sorted telephone book

This command can be used to retrieve the index of the first entry starting with selected character <schar> in the sorted list of phone book records of the phone book currently selected with

AT+CPBS .

The sorted list of phone book records can be accessed with AT command

AT^SPBG .

The sort order is described in chapter

13.1

.

CAUTION: Please note that the sorted entries are assigned an index of their own which is not identical with the location numbers used in the various phone books.

Therefore, the index retrieved with command AT^SPBC

command can be used only as an index for

AT^SPBG . Do

not use the listed index numbers to dial out or modify entries.

This command can be used only after the phone book data from the SIM have been read successfully for the first time. Reading starts after successful SIM authentication has been performed, and may take up to 30 seconds depending on the SIM used.

While the read process is in progress, an attempt to use any of the phone book commands will result in "+CME Error: 14" (SIM busy).

Syntax

Test Command

AT^SPBC=?

Write Command

AT^SPBC= <schar>

Response(s)

"SPBC: "FD","SM","ME"

OK

ERROR

+CME ERROR

Response(s) spbc: <index>

OK

ERROR

+CME ERROR


SIMENS

● ●


The test command returns the list of phone books for which

AT^SPBC is

supported, in the syntax used for phone book selection in AT command

AT+CPBS )

.

The write command retrieves the first (lowest) index in the list of sorted phone book entries beginning with character <schar> .


<schar>

(str)(+cscs)

The character to be searched in the sorted list of phone book entries.

Character coding and formatting according to the settings made with

AT+CSCS .

Search algorithms follow the sorting algorithms referenced in chapter

13.1

.

<index> (num)

The first (lowest) index number within the phone book memory selected with

AT+CPBS for which the corresponding <text> parameter


Page 234

TANGO55/56 AT COMMAND SET VERSION 1.01 starts with character <schar> . If no matching phone book entry is found,< index> =0 will be returned.

The index retrieved with

AT^SPBC

can be used only as an index for

AT^SPBG . Do

not use the listed index numbers to dial out or modify entries.

13.6 AT

^

SPBD Purge phone book memory storage

This command is used to purge the selected phone book <storage> manually, i.e. all entries previously stored in the selected phone book storage will be deleted.

CAUTION! The operation cannot be stopped nor reversed!

Automatic purging of phone books is performed when the SIM card is removed and replaced by a different SIM card. This affects the ME-based part of the "LD" storage, and storages "MC" and "RC". Storage "ME" is not affected.



Syntax

Test Command

AT^SPBD=?

Write Command

AT^SPBD= < storage>

Response(s)

^SPBD: list of supported <storage>s

OK

+CME ERROR

Response(s)

OK

+CME ERROR


SIEMENS

● ●


The test command returns a list of supported <storage>s.

The write command is used to select the phone book <storage> to be purged.


<storage>

(str)

If test command: List of phone books which can be deleted by

AT^SPBD .

If write command: Phone book to be deleted.

For a detailed description of storages see AT+CPBS .

"LD" Last number dialed phone book

"MC" Missed (unanswered received) calls list

"RC" Received calls list

13.7 AT

^

SPBG Read current Phone book entries

This command can be used to display the phone book records of the phone book currently selected with

AT+CPBS

in sorted order by name. The sort order is described in chapter

13.1

, "Sort order for Phone books". There are two ways to use command

AT^SPBG :


Page 235


• If the optional parameter <RealLocReq> is omitted: Please note that the sorted entries are assigned an index of their own which is not identical with the location numbers used in the various phone books.

In this case, command AT^SPBG

can be used for reading only. For example, it helps you find entries starting with matching characters. Do not use the listed index numbers to dial out or modify entries.

•

To access an entry found with AT^SPBG for editing or dialing, enter

AT^SPBG with the parameter

<RealLo-cReq>=1 .

Then extract the "real" location number of the entry from response parameter <location> and use this "real" location number with

ATD><mem><n>

or AT+CPBW .



Syntax

Test Command

AT^SPBG=?

Write Command

AT^SPBG= <indexl> [,< index2>][,<RealLocReq>]

Response(s)

^SPBG: (1-<used>),<nlength>,<tlength>

OK

ERROR

+CME ERROR

Response(s)

[^SPBG: <indexl>,<number>,<type>,<text>[,<location>] ]

[^SPBG: <index2>,<number>,<type>,<text>[,<location>] ]

OK

ERROR

+CME ERROR


SIEMENS

● ●


The test command returns the index range for this command, the maximum length of <number> field, and the maximum length of <text> field.

Note: The length may not be available while SIM storage is selected. If storage does not offer format information, the format list should be empty parenthesises.

The write command selects the index of the phone book entry, that is to be displayed, in the sorted list of phone book, or the range of indices to display.

If no <index2> is given, only the entry at <index1> will be displayed.

If parameter <RealLocReq>=1 , the actual location of the entry displayed will be indicated in parameter <loca-tion>. If <RealLocReq> is omitted or

<RealLocReq>=0 , parameter <location> will not be displayed. The indices displayed in the first parameter of the write command response are indices in the sorted list of entries, and not related to the entries' location in the phone book. They may not be used for other phone book commands or

ATD><mem><n> . Instead, parameter <location> must be used for these purposes.


Page 236



<indexl>

(num)

The first index number within the sorted list of phone book for which the corresponding entry is to be displayed.

The supported range is given in the test command response.

If <index1> exceeds the upper bound <used> , the AT command will return a CME ERROR 21.

<index2>

(num)

The last index number within the sorted list of phone book for which the corresponding entry is to be displayed.

The supported range is given in the test command response.

If both <index1> and <index2> are in the range indicated by the test command in parameter <used> , the list of entries will be output and terminated with OK.

If <index2> exceeds the range indicated by the test command in parameter <used> , the list of entries will be output but terminated with a +CME ERROR 21 "INVALID INDEX".

<RealLocReq>

(num)

Is a display of the "real" <location> of the entry required?

[0] Do not display an entries "real" location number.

Parameter <location> will not be displayed.

1 Display the "real" location number as parameter

<location> at the end of the entry.

<number>

(str)

String type phone number in format specified by <type> . The number parameter may be an empty string.

<type>

(num) type of address octet

145 dialling string <number> includes international access code character'+'

209 dialling string contains printable nonalphabetic non-digit characters saved with the number string. For further detail, check the

parameter descriptions for at command AT+CPBW .

129 otherwise

<text>

(str)(+cscs)

Text assigned to the phone number. The maximum length for this parameter is given in test command response <tlength> .

<used>

(num)

Value indicating the number of used locations in selected memory storage.

<location>

(num)

The location within phone book memory at which the corresponding entry is located. This location may be used for other commands, (e.g.

AT+CPBR

or ATD><mem><n> )

<nlength>

(num)

Max. length of phone number for "normal" locations. - Depending on the storage, a limited number of locations with extended memory is


Page 237


available per phone book. Please refer to AT command AT+CPBW

for detail.

<tlength>

(num)

Max. length of <text> assigned to the telephone number. The value indicated by the test command is given in octets. If the <text> string is given in GSM characters, each character corresponds to one octet.

If the <text> string is given in UCS2, the maximum number of characters depends on the coding scheme used for the alpha field of the SIM according to GSM 11.11, Annex B. In the worst case, the number of UCS2 characters is less than half the number of GSM characters. For a detailed description see GSM 11.11, Annex B.

Notes

• The AT^SPBG feature is able to sort by the first 6 matching characters only.

All following characters will be ignored.

• The command can be used for the phone books "SM", "FD", "ME" (cf.

AT+CPBS ).

Examples

EXAMPLE 1:

Using APSPBG without <RealLocReq> . a) First, run the test command to find out the range of phone book entries stored in the active phone book by using:

AT^SPBG=?

TA returns the number of entries in the format:

^SPBG: (1-33),20,17 where 33 is the number of used entries in the active phone book storage.

b) Now, run the write command to display the phone book entries by alphabetical order. It is recommended to enter the full range to obtain best results.

AT^SPBG=1,33

TA returns phone book entries by alphabetical order:

^SPBG:1,"+999999",145,"Arthur"

^SPBG:2,"+7777 77",145,"Bill"

^SPBG:3,"+888888",145,"Charlie"

The numbers at the beginning of each line are not the memory locations in the phone book, but only serial numbers assigned to the entries' positions in the alphabetical list.

EXAMPLE 2:

Using AT^SPBG with <RealLocReq> a) First, run the test command to find out the range of phone book entries stored in the active phone book:

AT^SPBG=?

TA returns the number of entries in the format:

^SPBG: (1-33),20,17 where 33 is the total number of entries in the active phone book storage.

b) Now, run the write command to display the phone book entries by alphabetical order. It is recommended to enter the full range to obtain best results.


Page 238


Use parameter <RealLocReq>=1 in order to obtain the entries' location numbers.

AT^SPBG=1,33,1

TA returns phone book entries by alphabetical order:

^SPBG:1,"+999999",145,"Arthur",27

^SPBG:2,"+777777",145,"Bill",6

^SPBG:3,"+888888",145,"Charlie",15 c) The numbers at the end of each line are now the memory locations in the phone book and can be used for dialing or editing phone book entries:

AT+CPBR=27

Read out phone book location 27.

+CPBR: 2 7," + 999 999",145,"Arthur" d) This entry can now be edited with

AT+CPBW .

13.8 AT

^

SPBS Step through the selected phone book alphabetically

This command can be used to scroll sequentially through the active phone book records in alphabetical order by name. Three entries will be displayed at a time.


While the read process is in progress, an attempt to use any of the phone book commands will result in "+CME Error: 14" (SIM busy). This command can be used for the ME, SM and FD phone book.

Syntax

Test Command

AT^SPBS=?

Write Command

AT^SPBS=<value>[, <RealLocReq> ]

Response(s)

^SPBS: (list of supported <value > )

OK

Response(s)

^SPBS: <index-a><number>,<type> , text>[,<location>]

^SPBS: <index-b><number>,<type> ,< text>[,<location>]

^SPBS: <index-c><number>,<type> ,< text>[,<location>]

OK

+CME ERROR


SIEMENS

● ●


Test command returns a list of supported <value> .

Every time the write command is executed, 3 rows of phone book records are returned. Each triplet overlaps with the next one. The actual index depends on parameter <value> . This parameter determines whether the index will be increased or decreased.

If the index in one output line reaches the last index in the alphabetical list, the next output line will display the first list entry.


Page 239


After the last record of the phone book has been reached (see parameter

<used>

for AT^SPBG ), the

<internalcounter> switches over to the first. There are

two ways to use command AT^SPBS :

• If the optional parameter <RealLocReq> is omitted or (0): In this case, the sorted list is assigned an index of its own which is not identical with location numbers used in the various phone books. For example, it helps you find entries starting with matching characters. However, do not use the listed index numbers to dial out with ATD><mem><n> or to modify entries with

AT+CPBW .

• To access an entry found with

AT^SPBS for editing or dialing, enter AT^SPBS

with the parameter <RealLo-cReq>=1 . Then extract the "real" location number of the entry from response parameter <location> and use this "real" location number with ATD><mem><n> or

AT+CPBW .

• See examples below.


< value>

(num)

1 To make a step forward in the alphabetically sorted phone book.

2 To make a step backward in the alphabetically sorted phone book.

<index-a>

(num)

1….maxindex The index in the sorted list of phone book entries that identifies the first entry displayed.

The value of <index-a> is determined by the value of the <internalcounter> and by parameter

<value> .

After a write command has terminated successfully with "OK", the value from parameter

<index-a> is saved and retained as the new

<internalcounter> value.

<index-b>

(num)

1...maxindex The index in the sorted list of phone book entries that identifies the third entry displayed.

<index-b>= (<index-a>+1).

Mind after the last record of phone book, the first entry follows.

<index-c>

(num)

1...maxindex The index in the sorted list of phone book entries that identifies the third entry displayed.

<index-c>= (<index-b>+1) .


<number>

(num)


<number> (str) string type phone number in format specified by

<type> . The number parameter may be an empty string.

<type>

(num) type of address octet string includes international access code character'+'


Page 240


209 dialling string <number> contains printable nonalphabetic non-digit characters saved with the number string.

For phone book entries with this <type>, dialling from phone book with ATD><mem><n> is not possible. For further detail, check the parameter descriptions for at command

AT+CPBW .

129 otherwise

<text>

(str)(+CSCS)

Text assigned to the phone number.

<RealLocReq>

(num)

Is a display of the "real" <location> of the entry required?

[0] Do not display an entries "real" location number.

Parameter <location> will not be displayed.

1 Display the "real" location number as parameter

<location> at the end of the entry.

<location>

(num)

The location within phone book memory at which the corresponding entry is located.

This location may be used for other phone book commands (e.g.

AT+CPBR ,

AT+CPBW , ATD><mem><n>)

.

<internal-counter >

(num)

0(&F)...maxindex This Parameter is only an internal parameter and cannot modified directly.

The internal counter will be reset to index 0 after

a call to ATZ

or AT&F .

Note

• The complete list of sorted entries can be retrieved using AT command

AT^SPBG .

Example

How to use AT^SPBS to browse through the sorted list forward and backward.

Using AT^SPBS without <RealLocReq> or with <RealLocReq>=0 .

a) First,

is issued to make sure that AT^SPBS=1 starts from the first character in alphabetical order. The example illustrates how to search down and up again. at&f

OK at^spbs=l

^SPBS:1,"+999999",145,"Arthur"

^SPBS:2,"+777777",145,"Bill"

^SPBS:3,"+888888",145,"Charlie"

OK

At^spbs=l

^SPBS:2,"+777777",145,"Bill" ^SPBS:3,"+888888",145,"Charlie"

^SPBS:4,"0304444444",129,"Esther"

OK at^spbs=l

^SPBS:3,"+888888",145,"Charlie" ^SPBS:4,"0304444444",129,"Esther"

^SPBS:5,"03033333333",129,"Harry"


Page 241


OK

At^spbs=2

^SPBS:2,"+777777",145,"Bill" ^SPBS:3,"+888888",145,"Charlie"

^SPBS:4,"0304444444",129,"Esther"

OK

• If the last index in the sorted list has been reached, then the internal counter overflows to the first index: at&f

OK reset internal counter to 0

At^spbs=2 step down 1 entry starting from (internal counter)=0 overflow occurs.

^SPBS:33,"+49301234567",145,"TomTailor"

ASPBS:1,"+999999",145,"Arthur" ^SPBS:2,"+777777",145,"Bill"

OK

Using AT^SPBS with <RealLocReq>=1 in order to obtain the entries' location numbers.

At^spbs=l,1

^SPBS:1,"+999999",145,"Arthur",27 ^SPBS:2,"+777777",145,"Bill",6

^SPBS:3,"+888888",145,"Charlie",15

The numbers at the end of each line are now the memory locations in the phone book and can be used for dialing or editing phone book entries:

This entry can now be read with AT+CPBR

or edited with AT+CPBW .

AT+CPBR=27

Read out phone book location 27.

+CPBR:27,"+999999",145,"Arthur"

13.9 AT

^

SDLD Delete the "last number redial" memory

Reading starts after successful SIM authentication has been performed, and may take up to 30 seconds depending on the SIM used. While the read process is in progress, an attempt to use any of the phone book commands will result in "+CME

Error: 14" (SIM busy).

Syntax

Test Command

AT^SDLD=?

Exec Command

AT^SDLD

Response(s)

OK

Response(s)

OK

ERROR

+CME ERROR: <err>


SIEMENS

● ●


The execute command deletes all numbers stored in the LD memory.


Page 242


14 AUDIO COMMANDS

VERSION 1.01

14.1 ATL Set monitor speaker loudness

Syntax

Exec Command

ATL[ <val> ]

Reference(s)

Response(s)

OK

PIN SERIAL

V 25ter

○ ●


<val>

(num)

Notes

• Commands

ATL and ATM are implemented only for V.25ter compatibility

reasons and have no effect.

14.2 ATM Set monitor speaker mode

Syntax

Exec Command

ATM[ <val> ]

Reference(s)

Response(s)

OK

PIN SERIAL

V.25ter


<val>

(num)

○ ●

Notes

• Commands

ATL

and

ATM

are implemented only for V.25ter compatibility reasons and have no effect.

14.3 AT+CLVL Loudspeaker volume level

Syntax

Test Command

AT+CLVL=?

Read Command

AT+CLVL?

Write Command

AT+CLVL= <level>

Response(s)

+CLVL: (list of supported <level > s)

OK

Response(s)

+CLVL: <level>

OK

ERROR

+CME ERROR: <err>

Response(s)

OK

ERROR

+CME ERROR: <err>


Page 243



GSM 07.07

○


<level>

(num)

Loudspeaker Volume Level

0...4(D)

●

Notes

• The write command can only be used in audio mode 2 - 6.

• The values of the volume steps are specified with the parameters

<outCalibrate>[0],...<outCalibrate>[4] of the

AT^SNFO command.

• As an alternative to AT+CLVL, you can use AT^SNFO

and AT^SNFV. The

parameter <level> is identical with <outStep> used by both commands.

• Any change to <level> (or <outstep> ) takes effect in audio modes 2 to 6.

The only exception is audio mode 1 which is fixed to <level>=4 (or accordingly <outstep>=4 ).

• <level> (or <outstep> ) is stored non-volatile when the ME is powered down

with Table 2.3

or reset with AT+CFUN =1,1

.

14.4 AT+CMUT Mute control

Syntax

Test Command

AT+CMUT=?

Read Command

AT+CMUT?

Write Command

AT+CMUT= <mute>

Response(s)

+CMUT: (list of supported <mute>s )

OK

Response(s)

+CMUT: <mute>

OK

ERROR

+CME ERROR: <err>

Response(s)

OK

ERROR

+CME ERROR: <err>


GSM 07.07

○ ●


This command can be used in all audio modes (1 to 6) and during a voice call only. During an active call, users should be aware that when they switch back and forth between different audio modes (for example handsfree on/off) the value of <mute> does not change, i.e. the microphone mode is retained until explicitly changed.


<mute>

(num)

0

(P)

mute


Page 244


14.5 AT+VTD Tone duration

Syntax

Test Command

AT+VTD=?

Read Command

AT+VTD?

Write Command

AT+VTD= <duration>

Response(s)

+VTD: (list of supported <duration> s)

OK

Response(s)

<duration>

OK

Response(s)

OK


GSM 07.07

○ ●


This command refers to an integer <duration> that defines the length of tones

transmitted with the AT+VTS

command.


<duration>

(num) duration of the tone in 1/10 second

1(&F)...255

14.6 AT+VTS DTMF and tone generation

The Write command is intended to send ASCII characters or strings which cause the

Mobile Switching Center (MSC) to transmit DTMF tones to a remote subscriber. It works during active voice calls only and offers the following variants:

AT+VTS =<dtmf String>

allows to send a sequence of DTMF tones with a duration defined with

AT+VTD .

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

allows to send a single DTMF tone. In this case, the duration can be individually determined during the call.

Syntax

Test Command

AT+VTS=?

Write Command

AT+VTS=<dtmfString>

Write Command

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

Reference(s)

Response(s)

+VTS: (list of supported <dtmf > s), (list of supported <duration> s)

OK

Response(s)

OK

Response(s)

OK

PIN SERIAL

GSM 07.07

○ ●


<dtmfString>

(str)

String of ASCII characters in the set 0-9,#,*,A, B, C, D. Maximal length of the string is 29. The string must be enclosed in quotation marks

("...").

<dtmf>

(str)


Page 245


ASCII character in the set 0...9,#,*, A, B, C, D.

<duration>

(num)

Tone duration in 1/10 second. If not specified current setting of

AT+VTD is used.

1...255

14.7 AT

^

SNFD Set audio parameters to manufacturer default values

Syntax

Read Command

AT^SNFA?

Exec Command

AT^SNFD

Reference(s)

Response(s)

^SNFA: (list of supported <atten>s )

OK

Response(s)

OK

PIN SERIAL

SIEMENS

○ ●


TA sets the active audio parameters to manufacturer defined default values.

Notes

• The restored values are:

• Remember that the factory set audio mode 1 is fixed to <outstep>=4 .

Consequently,

AT^SNFD

restores <audMode> together with <outstep>=4 , but does not affect the values of <outStep> currently selected in audio modes 2 - 6. This means, if <audMode>=1 , the read commands

AT^SNFO ,

AT^SNFV

and

AT+CLVL

will always deliver <outstep>=4 . In all other modes the <outStep> value is retained until explicitly changed.

14.8 AT

^

SNFI Set microphone path parameters

Syntax

Test Command

AT^SNFI=?

Read Command

AT^SNFI?

Response(s)

^SNFI: (list of supported <inBbcGain>s ) , (list of supported

<inCalibrate>s )

OK

Response(s)

^SNFI: (list of supported <inBbcGain>s ) , (list of supported

<inCalibrate>s )

OK

Response(s)

OK

Write Command

AT^SNFI = <inBbcGain>,<inCalibrate>

Reference(s) PIN

SIEMENS

○


TA sets microphone path amplifying.


SERIAL

●


Page 246


<inBbcGain>

(num)(^SNFW)

ADC gain adjustable in eight 6 dB steps from 0 dB to 42 dB (0=0dB,

7=42dB, 8 steps of 6 dB).

0...7

<inCalibrate>

(num)(^SNFW)

Multiplication factor for input samples. Formula to calculate the negative gain (attenuation) of the input signal: Gain in dB = 20 * log

(inCalibrate / 32768)

0...32767

Notes

• Write command works only in audio modes 2 to 6!

• Read and write options of this command refer to the active audio mode.

• The range of <inCalibrate> is up to 65535 but will be suppressed to 32767.

Values above <inCalibrate>= 65535 will cause a failure.

• Changed values have to be stored with AT^SNFW.

• Attention! When you adjust audio parameters avoid exceeding the maximum allowed level. Bear in mind that exposure to excessive levels of noise can cause physical damage to users!

• The default values are customer specific.

14.9 AT

^

SNFO Set audio output (= loudspeaker path) parameter

Syntax

Test Command

AT^SNFO=?

Read Command

AT^SNFO?

Response(s)

^SNFO: (list of supported <outBbcGain>s ) (list of supported <outCalibrate>s ) (list of supported

<outstep>s ) (list of supported <sideTone>s )

OK

Response(s)

^SNFO: <outBbcGain>,<outCalibrate>[0] ,

< outCalibrate>[1] ,< outCalibrate>[2]

<outCalibrate>[3] ,< outCalibrate>[4] ,

< outStep>,<sideTone>

OK

Response(s)

OK

Write Command

AT^SNFO=<outBbcGain>,<outCalibrate>[0] ,

< outCalibrate>[1] ,< outCalibrate>[2] ,

< outCalibrate>[3] ,< outCalibrate>[4] , < outStep>,<sideTone>


SIEMENS

○


TA sets earpiece path amplifying.

●


<outBbcGain>

(num)(^SNFW)

Negative DAC gain (attenuation) adjustable in four 6 dB steps from

0 dB to -18 dB (0=0 dB, 3=-18 dB)

0...3

<outCalibrate>

(num)(^SNFW)


Page 247


Formula to calculate the value of the 5 volume steps selectable with parameter <outstep> : Attenuation = 20 log * (2 * outCalibrate[n] /

32768)

0...32767

<outStep>

(num)

Volume steps 0 - 4, each defined without Calibrate[n]

< sideTone>

(nun)(^SNFW)

Multiplication factor for the sidetone gain.

Formula to calculate how much of the original microphone signal is added to the earpiece signal:

Sidetone gain in dB = 20 * log (sideTone / 32768).

0...32767

Notes

• The write command works only in audio modes 2 to 6.

• The read and write commands refer to the active audio mode.

• <outCalibrate> specifies the amount of volume of each <outstep> . The range of each <outCalibrate> is up to 65535, but will be suppressed to

32767. A value above <outCalibrate> = 65535 will cause an error.

• The range of <sideTone> is up to 65535, but will be suppressed to 32767. A value above <sideTone> =65535 will cause an error.

• Any change to <outStep> takes effect in audio modes 2 to 6. Nevertheless, the sound quality and the amount of volume are not necessarily the same, since all remaining audio parameters can use different values in either mode.

• Audio mode 1 is fixed to <outstep>=4 . In this mode, any attempt to change

<outStep> or other parameters returns an error.

• The value of <outStep> is stored non-volatile when the ME is powered

down with Table 2.3

or reset with AT+CFUN =x,1

. Any other parameters changed with

AT^SNFO

need to be saved with

AT^SNFW

for use after

restart. See also AT^SNFD for details on restoring factory defaults.

• The values of <outStep> can also be changed with

AT^SNFV

and AT+CLVL .

• CAUTION! When you adjust audio parameters avoid exceeding the maximum allowed level. Bear in mind that exposure to excessive levels of noise can cause physical damage to users!

14.10 AT

^

SNFPT Set progress tones

Syntax

Test Command

AT^SNFPT=?

Read Command

AT^SNFPT?

Write Command

AT^SNFPT= <pt>

Reference(s)

SIEMENS

Response(s)

^

SNFPT

: (list of supported <pt>s )

OK

Response(s)

^SNFPT: <pt>

OK

Response(s)

OK

PIN

○

SERIAL

●


Page 248



The write command controls the Call Progress Tones generated at the beginning of a mobile originated call setup.


<pt>

(num)

0

1

(P)

Disables Call Progress Tones

Enables Call Progress Tones (audible tones shortly heard on the phone when ME starts to set up a call.)

Note

• Please note that the setting is stored volatile, i.e. after restart or reset, the default value 1 will be restored.

14.11 AT

^

SNFV Set loudspeaker volume

Syntax

Test Command

AT^SNFV=?

Read Command

AT^SNFV?

Write Command

AT^SNFV= <outStep>

Response(s)

^SNFV: (list of supported <outstep>s )

OK

Response(s)

^SNFV: <outStep>

OK

Response(s)

OK

ERROR

+CME ERROR


SIEMENS

○ ●


The test command returns the supported values of the parameter <outstep> .

The read command returns the current value of parameter <outstep> .

The write command can be used to set the volume of the loudspeaker to the value <outCalibrate> addressed by <outstep> .


<outStep>

(num)

The actual volume of each step is defined by the parameter <outCal ibrate> , which can be set with

AT^SNFO .

0...4

(p)

Notes

• The read and write commands refer to the active audio mode.

• The write command works only in audio modes 2 to 6!

• Any change to <outStep> takes effect in audio modes 2 to 6. Nevertheless, the actual volume can be quite different, depending on the values of

<outCalibrate> set in each mode. The only exception is audio mode 1 which is fixed to <outstep>=4 .

• <outStep>

is stored non-volatile when the ME is powered down with Table

2.3

or reset with AT+CFUN =1

,1. <outStep>

is not stored by AT^SNFW .


Page 249


• <outStep> can also be changed by

AT^SNFO

(chapter 14.9) and AT+CLVL

(chapter 14.10).

14.12 AT

^

SNFW Write audio setting in non-volatile store

Syntax

Test Command

AT^SNFW=?

Exec Command

AT^SNFW

Response(s)

OK

Response(s)

OK

ERROR

CME ERROR: <err>

OK


SIEMENS

○ ●


TA writes the active audio parameters in non-volatile store related to the active mode.

Notes

• Execute command works only in audio mode 2 to 6.

• TA writes the following audio parameter values in non-volatile store:

AT^SNFi: <inBbcGain>,<inCalibrate>

AT^SNFO : <outBbcGain>,<outCalibrate>[0

to 4],< sideTone>

14.13 AT

^

SRTC Ring tone configuration

Syntax

Test Command

AT^SRTC=?

Read Command

AT^SRTC?

Exec Command

AT^SRTC

Write Command

AT^SRTC=[ <type> ][,< volume> ]

Response(s)

RTC: (list of supported) <type>s, (list of supported) <volume>s

OK

Response(s)

^SRTC: <type>,<volume>,<status>

OK

Response(s)

OK

Response(s)

^SRTC: <type>,<volume>

OK

ERROR


SIEMENS

○ ●


The test command returns the current ring tone and volume.

The read command returns the current <type> and current <volume> . The read command can be used while test playback is off or on. In the latter case, see Execute command for details.


Page 250


During test playback, you can enter the Write command to select another melody and adjust the volume. Also, you can enter the read command to check the type and volume of the current ring tone, and to view the status of playback (on/off). The test ringing signal cannot be activated when an MTC is ringing (ERROR). Selecting <volume>=0 during the test, immediately stops playback. After this, ring tones will be muted until you change <volume> using the write command.

The write command chooses the type and volume of ring tones. The settings can be changed no matter whether or not the ME is ringing. The selected type and volume are saved in the non-volatile Flash memory and, thus, are retained after Power Down. An exception is <type>=0 , that can be entered to quickly mute the tone or melody currently played to indicate an event. <type>=0 only stops immediately the audible ring tone, but does not terminate the URC that indicates the event (for example RING). No permanent settings are changed or saved. Before first using ring tones:

We have chosen to let you decide your own preferences when you start using

ring tones. Therefore, factory setting is AT^SRTC=3,0,0

(ring tones are muted). To activate ring tones for the very first time, first enter the write command and simply change the volume. After applying a firmware update the volume and type selected before the firmware update will be preserved.


<type>

(num)

Type of ring tone. You have a choice of 7 different ring tones and melodies. <type>=0 is only intended for muting.

0 Mutes the currently played tone immediately.

3(D) Sequence 3

<volume>

(num)

Volume of ring tone, varies from low to high

0

(D)

Mute

1 Very

2 Identical 1

3 Low

4 Identical 3

5 Middle

6 Identical 5

7 High

<status>

(num)

Status of test ringing. Indicates whether or not a melody is currently being played back for testing

Notes


Page 251


• The test ringing signal cannot be activated while an MTC is ringing (ERROR).

• If an MTC arrives during test playback, test ringing will be deactivated and

"normal" ringing reactivated (RING).

• If no optional parameter is entered, the old value will be kept.


Page 252


15 HARDWARE RELATED COMMANDS

The AT commands described in this chapter are related to the TANGO55/56's hardware interface. More information regarding this interface is available with the

"TANGO55/56 Hardware Interface Description"[1].

15.1 AT+CALA Set alarm time

Syntax

Test Command

AT+CALA=?

Read Command

AT+CALA?

Write Command

AT+CALA= <time>[,< n>[,<type>[,<text>]] ]

Response(s)

+CALA: (list of supported <n> s), (list of supported <type> s), (list of supported <tlength> s)

OK

ERROR

+CME ERROR: <err>

Response(s)

+ CALA: <time>[,<n>[,<type>[,<text>]]]

OK

ERROR

+CME ERROR: <err>

Response(s)

OK

ERROR

+CME ERROR


GSM 07.07

○ ●


URC 1

+CALA: <text>

Indicates reminder message.

URC 2

^SYSSTART ALARM MODE

+CALA : <text>

Indicates ME wake-up into Alarm mode. If autobauding is active

( AT+IPR =0)

the line "^SYSSTART ALARM MODE" does not appear, but your individual <text> message will be displayed .


Test command returns supported array index values <n> , alarm types <type> , and maximum length of the text <tlength> to be output.

Read command returns the list of current alarm settings in the ME.

The write command sets an alarm time in the ME. When the alarm is timed out and executed the ME returns an Unsolicited Result Code (URC) and the alarm time is reset to "00/01/01,00:00:00".

The alarm can adopt two functions, depending on whether or not you switch the GSM engine off after setting the alarm:

Reminder message: You can use the alarm function to generate reminder messages. For this purpose, set the alarm as described below and do not


Page 253

TANGO55/56 AT COMMAND SET VERSION 1.01 switch off or power down the ME. When executed the message comes as an

Unsolicited Result Code.

Alarm mode: You can use the alarm function to restart the ME when powered down. For this purpose, set the alarm as described below. Then power down

the ME by entering the Table 2.3

command. When the alarm time is reached, the ME will wake up to Alarm mode. To prevent the ME from unintentionally logging into the GSM network, Alarm mode provides restricted operation.

Upon wake-up, the ME indicates an Unsolicited Result Code which reads:

^SYSSTART ALARM MODE. A limited number of AT commands is available during Alarm mode, for details see table "List of AT Commands Available in

Alarm " . The ME remains deregistered from the GSM network.

If you want the ME to return to full operation (normal operating mode) it is necessary to restart the ME by driving the ignition line (IGT pin of application interface) to ground.


<time>

(str)

Format is "yy/MM/dd,hh:mm:ss", where characters indicate year

(two last digits), month, day, hour, minutes. E.g. 6th of May 2004,

22:10:00 hours equals to "04/05/06,22:10:00" (see also

AT+CCLK )

.

Note: if <time> equals current date and time or is set to an earlier date, TA returns +CME ERROR: 21.

<n>

(num)

Integer type value indicating the array index of the alarm.

The ME allows to set only one alarm at a time. Therefore, the list of supported alarm events indicated by the test command

AT+CALA =?

is <n>=0 . If a second alarm time is set, the previous

alarm will be deleted. Therefore, the read command AT+CALA ?

will always return <n>=0 . This is also true if individual settings are made on SERIAL, for details see notes below.

<type>

(num)

Integer type value indicating the type of the alarm.

0 Alarm indication: text message via serial interface

<text>

(str)

String type value indicating the text to be displayed when alarm time is reached; maximum length is <tlength> .

By factory default, < text> is undefined.

Note: <text> will be stored to the non-volatile flash memory when the device enters the Power Down mode via

Table 2.3

. Once saved,

it will be available upon next power-up, until you overwrite it by typing another text. This eliminates the need to enter the full string when setting a fresh alarm.

<text> should not contain characters which are coded differently in

ASCII and GSM (e.g. umlauts), see also

"Supported character sets" and "GSM alphabet tables".

<tlength>

(num)

Integer type value indicating the maximum length of <text>. The maximum length is 16.

Notes


Page 254


• After the alarm was executed the parameter <time> of

AT+CALA

will be reset to "00/01/01,00:00:00", but <text> will be preserved as described above.

• If TANGO55/56 is totally disconnected from power supply the most recently saved configuration of +CALA: <time>[,<n>[,<type>[,<text>]]] will be presented when TANGO55/56 is powered up.

• Each time TANGO55/56 is restarted it takes 2s to re-initialize the RTC and to update the current time. Therefore, it is recommended to wait 2s before

using the commands AT+CCLK

and

AT+CALA

(for example 2s after

^SYSSTART has been output).

• Alarm settings on SERIAL :

-

When the alarm is timed out and executed, the ME sends the

URC only on the interface where the most recent alarm setting was made. The alarm time will be reset to "00/01/01,00:00:00" on all interfaces.

Examples:

EXAMPLE 1

You may want to configure a reminder call for May 31, 2004, at 9.30 h, including the message "Good Morning".

AT+CALA="04/05/31,09:30:00",0,0,"Good Morning"

OK

Do not switch off the GSM engine. When the alarm is executed the

ME returns the following URC:

+CALA: Good Morning

EXAMPLE 2

To set a fresh alarm using the same message as in Example 1, simply enter date and time. <n>,<type>,<text>,<tlength> can be omitted:

AT+CALA="04/05/31,08:50:00" OK

When the alarm is executed the URC comes with the same message:

+CALA: Good Morning

EXAMPLE 3

To configure the alarm mode, e.g. for May 20, 2004, at 8.30 h, enter

AT+CALA ="04/05/2 0,08:30:00"

OK

Next, power down the ME:

AT^SMSO ^SMSO: MS OFF

When the alarm is executed the ME wakes up to Alarm mode and displays a URC. If available, this line is followed by the individual

<text> most recently saved. If no individual message was saved only the first line appears.

^SYSSTART ALARM MODE

+CALA: Good Morning

15.1.1 Summary of AT commands available in Alarm mode

Table 17.1: List of AT commands available in alarm mode AT command function

AT+CALA

Set alarm time.


Page 255


AT+CCLK

AT^SCTM

at^smso

Set date and time of RTC.

Query temperature of GSM engine.

Power down GSM engine.

15.2 AT+CCLK Real Time Clock

Syntax

Test Command

AT+CCLK=?

Read Command

AT+CCLK?

Write Command

AT+CCLK= <time>

Response(s)

OK

Response(s)

+CCLK: <time>

OK

Response(s)

+CME ERROR: <err>

ERROR

OK


GSM 07.05

○ ●


<time>

(str)

Format is "yy/mm/dd,hh:mm:ss", where the characters indicate the two last digits of the year, followed by month, day, hour, minutes, seconds; for example 6 May 2004, 22:10:00 hours equals to "04/05/06,22:10:00"

Factory default is "02/01/01,00:00:00"

Notes

• <time> is retained if the device enters the Power Down mode via

Table 2.3

.

• <time> will be reset to its factory default if power is totally disconnected. In this case, the clock starts with <time> = "02/01/01,00:00:00" upon next power-up.

• Each time TANGO55/56 is restarted it takes 2 s to re-initialize the RTC and to update the current time. Therefore, it is recommended to wait 2 s before

using the commands AT+CCLK

and

AT+CALA

(for example 2 s after

^

SYSSTART has been output).

15.3 AT

^

SCTM Set critical operating temperature

presentation mode or query temperature

Use this command to monitor the temperature range of the module. The write command enables or disables the presentation of URCs to report critical temperature limits.

CAUTION: DURING THE FIRST 15 SECONDS AFTER START-UP, THE MODULE OPERATES IN

AN AUTOMATIC REPORT MODE: URCS CAN BE ALWAYS DISPLAYED

REGARDLESS OF THE SELECTED MODE

<N>.

Syntax

Test Command

AT^SCTM=?

Read Command

AT^SCTM?

Response(s)

^SCTM: (list of supported <n> s)

OK

Response(s)

OK

ERROR


Page 256


Write Command

AT^SCTM= <n>

+CME ERROR: <err>

Response(s)

OK

ERROR

+CME ERROR: <err>


SIEMENS

○ ●


URC 1

URCs will be automatically sent to the TA when the temperature reaches or exceeds the critical level, or when it is back to normal.

URC 2 for module (board) temperature


The read command returns the URC presentation mode and information about the current temperature range of the module.

Select <n> to enable or disable the presentation of the URCs. Please note that the setting will not be stored upon Power Down, i.e. after restart or reset, the default <n> =0 will be restored. To benefit from the URCs <n> =1 needs to be selected every time you reboot the GSM engine.


<n>

(num)

0

(&F)

Presentation of URCs is disabled (except for <m> equal to -2 or +2).

1 Presentation of URCs is enabled.

<m>

(num)

-2

-1

Below lowest temperature limit (causes immediate switch-off)

Below low temperature alert limit

1

2

Above upper temperature alert limit

Above uppermost temperature limit (causes immediate switch-off)

Notes

• Please refer to the "Hardware Interface Description" for specifications on critical temperature ranges.

• To avoid damage the module will shut down once the critical temperature is exceeded. The procedure is equivalent to the power-down initiated with

Table 2.3

.

• URCs indicating the alert level "1" or "-1" are intended to enable the user to take appropriate precautions, such as protect the module from exposure to extreme conditions, or save or back up data etc. The presentation of "1" or "-1" URCs depends on the settings selected with the write command:

• If <n> =0: Presentation is enabled for 15 s time after the module was switched on. After 15 s operation, the presentation will be disabled, i.e. no

URCs will be generated. If <n> = 1: Presentation of "1" or"-1" URCs is always enabled.


Page 257


• Level "2" or "-2" URCs are followed by immediate shutdown. The presentation of these URCs is always enabled, i.e. they will be output even

though the factory setting AT^SCTM =0

was never changed.

• If the temperature limit is exceeded while an emergency call is in progress the engine continues to measure the temperature and to deliver alert messages, but deactivates the shutdown functionality. Once the call is terminated full temperature control will be resumed. If the temperature is still out of range ME switches off immediately.

Examples:

EXAMPLE 1

URCs issued when the operating temperature is out of range:

SCTM_B: 1 Caution: Engine close to overtemperature limit.

SCTM_B: 2 Alert: Engine is above overtemperature limit and switches off.

SCTM_B: -1 Caution: Engine close to undertemperature limit.

SCTM_B: -2 Alert: Engine is below undertemperature limit and switches off.

EXAMPLE 2

URCs issued when the temperature is back to normal (URC is output once):

^sctm_B: 0 Engine back to normal temperature


Page 258


16 MISCELLANEOUS COMMANDS

The AT commands described in this chapter are related to various areas.

16.1 A/Repeat previous command line

Syntax

Exec Command

A/

Reference(s)

Response(s)

PIN SERIAL

V.25ter

○


Repeat previous command line.

●

Notes

• Line does not need to end with terminating character.

• After beginning with the character "a" or "A" a second character "t", "T" or

"/" has to follow. In case of using a wrong second character, it is necessary to start again with character "a" or "A".

• If autobauding is active, the command A/

cannot be used (see AT+IPR ).

16.2 ATS3 Write command line termination character

Syntax

Read Command

ATS3?

Write Command

ATS3= <n>

Reference(s)

Response(s)

<n>

OK

Response(s)

OK

PIN SERIAL

V.25ter

○ ●


This parameter setting determines the character recognized by TA to terminate an incoming command line.


<n>

(num)(&W)(&V) command line termination character

000...13

(&F)

...127

Note

• Using other value than 13 may cause problems when entering commands.

16.3 ATS4 Set response formatting character

Syntax


Page 259


Read Command

ATS4?

Write Command

ATS4= <n>

Reference(s)

Response(s)

<n>

OK

Response(s)

OK

PIN SERIAL

V.25ter

○ ●


This parameter setting determines the character generated by the TA for result code and information text.


<n>

(num)(&W)(&V) response formatting character

000...10

(&F)

...127

16.4 ATS5 Write command line editing character

Syntax

Read Command

ATS 5?

Write Command

ATS5=<n>

Response(s)

< n >

OK

Response(s)

OK


V.25ter


○ ●

This parameter setting determines the character recognized by TA as a request to delete the immediately preceding character from the command line.


<n>

(num)(&W)(&V) command line editing character

000...8

(&F)

...127


Page 260


17 APPENDIX

VERSION 1.01

17.1 Restricted access to SIM data after SIM PIN authentication

The following commands can be used only after data from the SIM have been read successfully for the first time. Reading starts after successful SIM authentication has been performed, and may take up to 30 seconds depending on the SIM used. While the read process is in progress, an attempt to use any of the following commands will result in "+CME Error: 14" (SIM busy).

Ø AT command not available.

○

● returned OK.

AT command fully accessible after SIM PIN authentication has been completed.

AT Command

AT+CMGL

AT^SMGL

AT+CMGR

AT^SMGR

AT+CSCA

AT+CPBR

AT+CPBW

AT+CPBS

AT^SDLD

AT^SPBC

AT^SPBD

AT^SPBG

AT^SPBS

ATD><mem><n

Ø

Ø

Ø

●

Ø

Ø

Ø

●

Ø

Exec

●

●

Ø

Ø

Ø

Test

●

●

●

●

●

●

●

○

○

○

○

○

●

Ø

Ø

Ø

Ø

Ø

Ø

Read

Ø

Ø

Ø

Ø

●

Ø

Ø

●

Ø

●

●

●

●

Ø

Write

●

●

●

●

○

●

●

●

Ø

17.2 List of *# Codes

The following GSM command strings can be sent with the ATD

command and must be terminated with semicolon. Reference: GSM 2.30 [16].

Table 19.1: List of (*#) Codes

Star-Hash Code

Phone Security

*#06#

**04[2]*oldPin*newPin[2]*newPin[2

]#

**05[2]*unblKey* newPin[2]* newPin[2]#

*#0003*MasterPhoneCode#

Functionality

Query IMEI

Change SIM pwd

Change/Unblocking SIM pwd

Unlock "PS" lock with Master Phone

Code

Registration of net password *[*]03*[ZZ]*oldPw*newPw*newPw

#

Phone number presentation

Response, also refer Table 19.3

<IMEI> OK

+CME ERROR: <err> /OK





Page 261


*#30# Check status of CLIP (Calling Line

Identification Presentation)

+CLIP : <n > , <m> OK (see:

AT+CLIP )

*#31#

*31#<Phonenumber>[;]

#31#<Phonenumber>[;]

*#76#

Check status of CLIR (Calling Line

Identification Restriction)

Suppress CLIR

Activate CLIR

Check status of COLP (Connected Line

Identification Presentation)

*#77# Check status of COLR (Connected Line

Identification Restriction)

Call forwarding (See also chapter 0.5.1

)

(choice of *,#,*#,**,##)21*DN*BS# Act/deact/int/reg/eras CFU

+CLIR : <n> , <m> OK (see:

AT+CLIR )

(see

AT+CLIR )

(see

AT+CLIR )

+COLP : 0, <m> OK (where <m> = active or not active)

+COLR : 0,< m> OK (where <m> = active or not active)

(choice of *,#,*#,**,##)67*DN*BS# Act/deact/int/reg/eras CF busy

(choice of*,#,*#,**,##)61

*DN*BS*T#

Act/deact/int/reg/eras CF no reply

(choice of *,#,*#,**,##)62*DN*BS# Act/deact/int/reg/eras CF no reach

Act/deact/int/reg/eras CF all (choice of

*,#,*#,**,##)002*DN*BS*T#

(choice of

*,#,*#,**,##)004*DN*BS*T#

Act/deact/int/reg/eras CF all cond.

Call waiting (See also chapter 0.5.1

)

(choice of *,#,*#)43*BS# Activation/deactivation/int WAIT

^

SCCFC : <reason> ,< status> , <class> [,...] like +CCFC *

)

(see:

AT+CCFC

)

see above see above see above see above see above

+CCWA : <status> ,< class> [,...] like +CCWA

*

)

(see:

AT+CCWA )

Call barring (See also chapter 0.5.1

)

(choice of *,#,*#)33*Pw*BS# Act/deact/int BAOC

(choice of *,#,*#)331*Pw*BS#




#330*Pw*BS#

#333*Pw*BS#

#353*Pw*BS#

Call Hold / Multiparty

C[C] in call

USSD messages

[C]...[C]#

C[C] (excluded 1 [C])

Act/deact/int BAOIC

Act/deact/int BAOIC exc.home

Act/deact/int. BAIC

Act/deact/int BAIC roaming

Deact. All Barring Services Deact.

All Outg.Barring Services Deact.

All Inc.Barring Services

Call hold and multiparty

Send USSD message

Send USSD message

^

SCLCK: <fac> ,< status> ,< class> [, ...] like

+CLCK

*)

(Refer to chapter

AT+CLCK )

see above see above see above see above see above see above

+CME ERROR: <err> / OK



DN

*)

^

SCCFC, +CCWA,

^

SCLCK: The output depends on the affected basic service of the *# code. One line will be output for every tele- or bearer service coded in basic service code BS.

^

SCCFC and

^

SCLCK are modified by giving an additional <reason> or

<fac> in front of the regular output string generated by the standard commands +CCFC and +CLCK.

Abbreviation

ZZ

Meaning

Type of supplementary services:

All services

Barring services

Dialing number

Value

330

Not specified

String of digits 0-9

Abbreviation

BS

Meaning

Basic service equivalent to parameter class:

Voice

FAX

SMS

Value

11

13

16


Page 262


T

PW

C

SMS+FAX

Data circuit asynchron

Data circuit synchron dedicated PAD access dedicated Packet access

Data circuit asynchron+PAD

Data circuit synchron+Packet

Data circuit asynchron+synchron +Packet+PAD

All Services

Time in seconds

Password

Character of TE character set (e.g. asterics, hash or digit in case of USSD, or digits in case of held calls or multiparty calls)

12

25

24

27

26

21

22

20

--

In contrast to AT command AT+CCFC ,

parameter T has no default value. If T is not specified, an operator defined default or the last known value may be used, depending on the network operator.

--

--

Table 19.2: Abbreviations of Codes and Parameters Used in Table "List of *# Codes"

Possible responses

Parameter

<m>

<n>

<status>

<class>

<fac>

<reason>

Meaning

Mode: 0 = not active, 1 = active

Unsolicited result code: 0 = presentation disabled, 1 = presentation enabled

Status: 0 = not active, 1 = active

Represents BS = basic service. See chapters

AT+CCFC ,

AT+CLCK and

0.5.1

.

Facility lock. See chapter

AT+CLCK .

Call forwarding reason

For the exact specification of the format and parameters for *# strings, please refer to GSM 02.30, Annex C, and GSM 02.04, table 3.2 [15].

Star-Hash Code

*

**

*#

#

##

Abbreviations in Table 19.1

act reg int deact eras

Functionality

Activate (except for CLIR, see list above)

Register and activate

Check status (interrogate)

Deactivate (except for CLIR, see list above)

Unregister and deactivate

Table 19.3: Function of *# codes for Supplementary Services

17.3 Available AT Commands and Dependency on SIM PIN

Ø ... command not available

○ ... command does not require PIN1

● ... command requires PIN1

◑ ... command sometimes requires PIN1

AT Command Exec

Configuration Commands

AT&F

AT&V

AT&W

○

○

○

Test

Ø

Ø

Ø

Read

Ø

Ø

Ø

Write

Ø

Ø

Ø


Page 263


ATQ

ATV

ATX

ATZ

AT+CFUN

AT+GCAP

AT+CMEE

AT+CSCS

AT^SCFG

AT^SM20

Ø

Ø

○

○

○

○

Ø

○

Ø

Ø

Ø

Ø

Ø

Ø

○

○

○

○

○

○

Ø

Ø

Ø

Ø

○

Ø

○

○

○

○

Ø

Ø

Ø

Ø

○

Ø

○

○

○

○

Status Control Commands

AT+CMER

AT+CIND

AT^SIND

AT+CEER

ATS18

Ø

Ø

Ø

●

Ø

○

●

Ø

●

○

●

○

○

Ø

Ø

●

○

○

Ø

AT+CPAS

AT+WS46

○

Ø

○

Ø

○

○

○

○ ○

Serial Interface Control Commands

AT\Q

AT&C

AT&D

AT&S

ATE

○

○

○

○

○

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

AT+ILRR

AT+IPR

●

○

●

○

●

○

Security Commands

AT+CPIN

AT+CPIN2

AT^SPIC

AT+CLCK

AT^SLCK

AT+CPWD

AT^SPWD

Ø

Ø

Ø

Ø

○

Ø

Ø

○

●

○

●

●

●

●

○

●

○

Ø

Ø

Ø

Ø

○

●

○

●

●

●

●

Identification Commands

ATI

AT+CGMI

AT+GMI

○

○

○

Ø

○

○

Ø

Ø

Ø

Ø

Ø

Ø


Page 264


AT+CGMM

AT+GMM

AT+CGMR

AT+GMR

AT+CGSN

AT+GSN

AT+CIMI

Call related Commands

ATA

ATD

ATD><mem><n

ATD><n>

ATD><str>

ATDI

ATDL

ATH

AT+CHUP

ATS0

ATS6

ATS7

ATS8

ATS10

ATP

ATO

+++

ATT

AT+CBST

AT+CRLP

AT+CLCC

AT^SLCC

AT+CR

AT+CRC

AT+CSNS

AT^SCNI

AT^SLCD

AT^STCD

Network Service Commands

AT+COPN

AT+COPS

AT+CREG

AT+CSQ

AT^SMONC

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

○

●

●

●

○

○

●

●

●

○

●

Ø

Ø

Ø

●

●

Ø

Ø

Ø

●

●

●

Ø

Ø

○

○

○

○

Ø

Ø

●

●

●

●

◑

●

●

○

●

Ø

Ø

○

○

○

○

○

○

●

●

Ø

Ø

○

●

○

○

○

○

○

○

●

●

○

○

○

●

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

○

○

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

○

○

Ø

Ø


Page 265

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

●

●

○

○

Ø

Ø

Ø

○

○

Ø

○

Ø

Ø

Ø

○

Ø

Ø

○

○

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

●

●

○

○

Ø

Ø

Ø

○

○

Ø

○

Ø

Ø

Ø

○

Ø

Ø

●

○


AT^MONI

AT^MONP

AT^SMONG

AT^SALS

AT^SHOM

AT^SPLM

AT^SPLR

AT^SPLW

Supplementary Service Commands

AT+CACM

AT^SACM

AT+CAMM

AT+CAOC

AT+CCUG

AT+CCFC

AT+CCWA

AT+CHLD

AT+CLIP

AT+CLIR

AT+CPUC

AT+CSSN

AT+CUSD

GPRS Commands

AT+CGACT

AT+CGANS

AT+CGATT

AT+CGAUTO

AT+CGDATA

AT+CGDCONT

AT+CGPADDR

AT+CGQMIN

AT+CGQREQ

AT+CGREG

AT+CGSMS

AT^SGAUTH

AT^SGCONF

ATA

ATD*99#

ATD*98#

ATH

ATS0

FAX Commands

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

●

Ø

Ø

Ø

Ø

Ø

○

●

Ø

Ø

○

○

●

Ø

Ø

●

Ø

●

●

●

●

Ø

●

●

●

●

●

●

●

●

●

●

●

○

○

Ø

Ø

Ø

Ø

Ø

○

●

●

○

●

●

●

●

●

●

●

●

●

○

●

●

●

○

○

●

● ●

Ø

Ø

Ø

Ø

Ø

Ø

Ø

●

Ø

●

Ø

●

Ø

●

Ø

●

○

○

Ø

●

●

●

Ø

Ø

Ø

●

●

●

Ø

●

●

●

○

●

●

●

Ø

○

●

●

●

●

●

●

●

●

●

●

●

○

○

Ø

Ø

Ø

Ø

○

○

●

●

Ø

Ø

●

●

○

●

●

○

●

●

●

●

●

●

●

●

●

●

AT+FBADLIN

AT+FBADMUL

AT+FBOR

AT+FCIG

Ø

Ø

Ø

Ø

Ø

Ø

○

○

○

○

○

○

○

○

○

○


Page 266


AT+CMSS

AT+CNMA

AT+CNMI

AT+CPMS

AT+CSCA

AT+CSCB

AT+CSDH

AT+CSMP

AT+CSMS

AT^SLMS

AT^SMGL

AT^SMGO

AT^SMGR

AT^SSCONF

AT^SSDA

AT+FCLASS

AT+FCQ

AT+FCR

AT+FDCC

AT+FDFFC

AT+FDIS

AT+FDR

AT+FDT

AT+FET

AT+FK

AT+FLID

AT+FMDL

AT+FMFR

AT+FOPT

AT+FPHCTO

AT+FREV

AT+FRH

AT+FRM

AT+FRS

AT+FTH

AT+FTM

AT+FTS

AT+FVRFC

Short Message Service (SMS) Commands

AT+CMGC

AT+CMGD

AT+CMGF

AT+CMGL

AT+CMGR

AT+CMGS

AT+CMGW

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

●

Ø

Ø

●

●

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

○

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

○

○

Ø

○

○

○

Ø

Ø

Ø

Ø

○

○

Ø

○

Ø

Ø

Ø

Ø

Ø

Ø

Ø

○

Ø

Ø

○

Ø

○

●

●

●

●

●

●

●

○

○

●

●

●

●

●

●

●

●

●

●

○

●

●

●

Ø

○

○

●

●

●

●

●

●

●

Ø

Ø

Ø

Ø

Ø

○

○

Ø

Ø

Ø

○

○

○

Ø

○

○

○

Ø

Ø

Ø

Ø

○

○

Ø

○

Ø

Ø

○

Ø

Ø

Ø

Ø

Ø

Ø

○

○

○

○

○

○

Ø

○

○

Ø

○

○

○

○

○

○

○

○

○

Ø

●

●

●

●

●

●

●

Ø

●

●

●

●

●

●

○

●

●

●

●

●

○

○

○

Ø

Ø


Page 267


AT^SSMSS

SIM related Commands

AT+CRSM

AT^SCKS

AT^SCID

AT+CXXCID

AT+CXXCID

Phone book Commands

AT+CPBR

AT+CPBS

AT+CPBW

AT^SPBC

AT^SPBD

AT^SPBG

AT^SPBS

AT^SDLD

Audio Commands

ATL

ATM

AT+CLVL

AT+CMUT

AT+VTD

AT+VTS

AT^SNFD

AT^SNFI

AT^SNFO

AT^SNFPT

AT^SNFV

AT^SNFW

AT^SRTC


AT+CALA

AT+CCLK

AT^SCTM


A/

ATS3

ATS4

ATS5

Ø

Ø

Ø

Ø

Ø

Ø

Ø

○

○

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

Ø

○

○

○

●

Ø

Ø

Ø

○

Ø

Ø

Ø

○

●

●

●

●

●

●

●

●

●

○

○

○

○

Ø

Ø

○

○

○

○

○

○

○

○

○

○

○

○

○

○

Ø

Ø

Ø

Ø

○

Ø

●

Ø

Ø

Ø

Ø

Ø

Ø

○

Ø

Ø

Ø

Ø

Ø

Ø

○

○

○

○

○

Ø

○

○

○

Ø

○

○

○

○

Ø

○

○

○

○

●

○

Ø

Ø

Ø

●

●

●

●

Ø

●

●

●

Ø

Ø

○

○

○

○

○

○

○

Ø

○

○

○

○

Ø

○

Ø

○

○

○

Table 19.4: Available AT Commands and Dependency on SIM PIN

17.4 AT Command Settings storable with AT&W

AT Command


ATQ

ATV

ATX

AT+CMEE

Stored parameters

<n>

<value>

<value>

<n>


Page 268



ATS18


AT\Q

AT&C

AT&D

AT&S

ATE

AT+ILRR

Call Related Commands

ATS0

ATS6

ATS7

ATS8

ATS10

AT+CBST

AT+CRLP

AT^SLCC

AT+CR

AT+CRC


AT+COPS

AT+CREG


AT^SACM

AT+CLIP

GPRS Commands

ATS0

FAX Commands

AT+FCLASS


AT+CMGF

AT+CNMI

AT+CSDH

AT^SMGO


AT^SCKS

Miscellaneous Commands

ATS3

ATS4

ATS5

<n>

<n>

<value>

<value>

<value>

<value>

<value>

<n>

<n>

<n>

<n>

<n>

<speed>,<name>,<ce>

<iws>,<mws>,<T1>,<N2>

<n>

<mode>

<mode>

<format>

<n>

<n>

<n>

<n>

<n>

<mode>

<mode>,<mt>,<bm>,<ds>,<bfr>

<show>

<n>

<mode>

<n>

<n>

<n>

Table 19.5: Settings Stored to User Profile on SERIAL

17.5 Factory Default Settings Restorable with AT&F

Factory Defaults AT Command


ATQ

ATV

ATX

AT+CFUN

AT+CMEE

AT+CSCS

AT^SM20


AT+CMER

ATS18

<n>=0

<value>=1

<value>=4

<fun>=1

<n>=0

<chset >="GSM"

<CallMode>=1,<CmgwMode>=1

<mode>=0,<keyp>=0,<disp>=0,<ind>=0,<bfr>=0

<n>=0


Page 269



AT\Q

AT&C

AT&D

AT&S

ATE

AT+ILRR

Call related Commands

ATD><mem><n

ATS0

ATS6

ATS7

ATS10

AT+CBST

AT+CRLP

AT^SLCC

AT+CR

AT+CRC


AT+COPS

AT+CREG

AT^SALS


AT^SACM

AT+CLIP

AT+CSSN

AT+CUSD

GPRS Commands

ATS0

FAX Commands

AT+FCLASS


AT+CMGF

AT+CNMI

AT+CSDH

AT+CSMP

AT^SMGO

AT^SSCONF

AT^SSDA

AT^SSMSS


AT^SCKS


AT+CPBS

AT^SPBS

Audio Commands

AT+VTD

Hardware related Commands

AT^SCTM

Miscellaneous Commands

ATS3

ATS4

ATS5

<n>=0

<value>=1

<value>=2

<value>=0

<value>=1

<value>=0

<mem> ="SM"

<n>=000

<n>=000

<n>=060

<n>=002

<speed>=7,<name>=0,<ce>=1

<iws>=61,<mws>=61,<T1>=78,<N2>=6

<n>=0

<mode>=0

<mode>=0

<format>=0

<n>=0

<^SALS>=0

<n>=0

<n>=0

<n>=0,<m>=0

<n>=0

<n>=000

<n>=0

<mode>=0

<mode>=0,<mt>=0,<bm>=0,<ds>=0,<bfr>=1

<show>=0

<fo>=17,<vp>=167,<dcs>=0,<pid>=0

<n>=0

<ra>=0

<da>=0

<seq>=0

<mode>=0

<storage> ="SM"

<internal-counter>=0

<duration>=1

<n>=0

<n>=013

<n>=010

<n>=008

Table 19.7: Factory Default Settings Restorable with AT&F

VERSION 1.01


Page 270


17.6 Summary of Unsolicited Result Codes (URC)

AT Command URC


Table 2.3

^SHUTDOWN


AT+CMER

+CIEV: <indDescr>,<indValue>

Call Related Commands

AT^SLCC

if the list of current calls is empty: ^SLCC: if one or more calls are currently in the list: ^SLCC: <idx>,<dir>,<stat>,<mode>,<mpty>,<traffic channel assigned>[,<number>,<type>[,<alpha>] ]

[^SLCC: <idx>,<dir>,<stat>,<mode>,<mpty>,<traffic channel assigned>[,<number>,<type>[,<alpha>] ]]

[…]

^SLCC:

AT+CRC

+CRING: <type>


AT+CREG

+CREG: <stat>

AT+CREG

AT^SALS

+CREG: <stat>[,<lac>,<ci>]

^SALS: <line>


AT^SACM

+CCCM: <ccm>

AT+CCWA

+CCWA: <calling number>,<type of number>,<class>, ,< CLI validity>

AT+CCWA

AT+CLIP

AT+CLIP

AT+CSSN

AT+CSSN

AT+CUSD

^SCWA

+CLIP: <number>,<type>,

+CLIP: <number>,<type>

+CSSI: <code 1>

+CSSU: <code 2>

, , ,<

+CUSD: <m>[<str>[<dcs>]]

CLI validity>

GPRS Commands

AT+CGREG

+CGREG: <stat>


AT+CNMI

AT+CNMI

AT+CNMI

+CMTI: <mem3>,<index>

+CMT: <length><CR><LF><pdu>

+CMT: <oa>,<scts>[,<tooa>,<fo>,<pid>,<dcs>,<sca>,<tosca>,<length>] <CR><LPxdata>

AT+CNMI

AT+CNMI

AT+CNMI

AT+CNMI

AT+CNMI

AT^SMGO

+CBM: <length><CR><LF><pdu>

+CBM: <sn>,<mid>,<dcs>,<page>,<pages><CR><LF><data>

+CDS: <length><CR><LF><pdu>

+CDS: <fo>,<mr>[,< ra> ][,< tora>],<scts>,<dt>,<st>

+CDSI:<mem3>,<index>

^SMGO: <mode>

SIM Related Commands

AT^SCKS

^SCKS: <SimStatus>

Hardware related Commands

AT+CALA

+CALA: <text>

AT^SCTM

^SCTM_A: <m>

AT^SCTM

^SCTM_B: <m>

Table 19.8: Summary of Unsolicited Result Codes (URC)

17.7 Alphabetical List of AT Commands

+++

A/

AT&C

AT&D

AT&F

AT Command

Description

Switch from data mode to command mode

Repeat previous command line

Set circuit Data Carrier Detect (DCD) function mode

Set circuit Data Terminal Ready (DTR) function mode

Set all current parameters to manufacturer defaults

Chapter and Page

chapter 6.18

chapter 16.1

chapter 3.2

chapter 3.3

chapter 1.1


Page 271


AT+CMGD

AT+CMGF

AT+CMGL

AT+CMGR

AT+CMGS

AT+CMGW

AT+CMSS

AT+CMUT

AT+CNMA

AT+CNMI

AT+COPN

AT+COPS

AT+CPAS

AT+CPBR

AT+CHLD

AT+CHUP

AT+CIMI

AT+CIND

AT+CLCC

AT+CLCK

AT+CLIP

AT+CLIR

AT+CLVL

AT+CMEE

AT+CMER

AT+CMGC

AT&S

AT&V

AT&W

AT+CACM

AT+CALA

AT+CAMM

AT+CAOC

AT+CBST

AT+CCFC

AT+CCLK

AT+CCUG

AT+CCWA

AT+CEER

AT+CFUN

AT+CGACT

AT+CGANS

AT+CGATT

AT+CGAUTO

AT+CGDATA

AT+CGDCONT

AT+CGMI

AT+CGMM

AT+CGMR

AT+CGPADDR

AT+CGQMIN

AT+CGQREQ

AT+CGREG

AT+CGSMS

AT+CGSN

Set circuit Data Set Ready (DSR) function mode

Display current configuration

Stores current configuration to user defined profile

Accumulated call meter (ACM) reset or query

Set alarm time

Accumulated call meter maximum (ACMmax) set or query

Advice of Charge information

Select bearer service type

Call forwarding number and conditions control

Real Time Clock

Closed User Group

Call Waiting

Extended error report

Set phone functionality

PDP context activate or deactivate

Manual response to a network request for PDP context activation

GPRS attach or detach

Automatic response to a network request for PDP context activation

Enter data state

Define PDP Context

Request manufacturer identification

Request model identification

Request revision identification of software status

Show PDP address

Quality of Service Profile (Minimum acceptable)

Quality of Service Profile (Requested)

GPRS network registration status

Select service for MO SMS messages

Request product serial number identification (IMEI) identi cal to GSN

Call Hold and Multiparty

Hang up call

Request international mobile subscriber identity

Indicator control

List current calls of ME

Facility lock

Calling line identification presentation

Calling line identification restriction

Loudspeaker volume level

Report mobile equipment error

Mobile Equipment Event Reporting

Send an SMS command

Delete SMS message

Select SMS message format

List SMS messages from preferred store

Read SMS messages

Send SMS message

Write SMS messages to memory

Send SMS messages from storage

Mute control

New SMS message acknowledge to ME/TE, only phase 2+

New SMS message indications

Read operator names

Operator selection

Mobile equipment activity status

Read from Phone book chapter 8.8

chapter 6.10

chapter 5.10

chapter 2.2

chapter 6.22

chapter 4.4

chapter 8.9

chapter 8.10

chapter 15.4

chapter 1.11

chapter 2.1

chapter 11.2

chapter 11.3

chapter 11.4

chapter 11.5

chapter 11.6

chapter 11.7

chapter 11.8

chapter 11.9

chapter 15.5

chapter 11.10 chapter 11.11

chapter 7.1

chapter 7.2

chapter 2.6

chapter 14.2

chapter 1.8

chapter 9.1



chapter 9.6

chapter 5.2

chapter 5.4

chapter 5.6

chapter 9.7

chapter 9.8

chapter 9.9

chapter 9.10

chapter 9.11

chapter 5.8

chapter 3.4

chapter 1.2

chapter 1.3

chapter 8.1

chapter 15.1

chapter 8.3

chapter 8.4

chapter 6.20


chapter 8.5

chapter 8.7

chapter 2.4


Page 272


AT+FCR

AT+FDCC

AT+FDFFC

AT+FDIS

AT+FDR

AT+FDT

AT+FET

AT+FK

AT+FLID

AT+FMDL

AT+FMFR

AT+FOPT

AT+FPHCTO

AT+FREV

AT+FRH

AT+FRM

AT+FRS

AT+FTH

AT+FTM

AT+FTS

AT+FVRFC

AT+GCAP

AT+GMI

AT+GMM

AT+GMR

AT+GSN

AT+CPBS

AT+CPBW

AT+CPIN

AT+CPIN2

AT+CPMS

AT+CPUC

AT+CPWD

AT+CR

AT+CRC

AT+CREG

AT+CRLP

AT+CRSM

AT+CSCA

AT+CSCB

AT+CSCS

AT+CSDH

AT+CSMP

AT+CSMS

AT+CSNS

AT+CSQ

AT+CSSN

AT+CUSD

AT+CXXCID

AT+FBADLIN

AT+FBADMUL

AT+FBOR

AT+FCIG

AT+FCLASS

AT+FCQ

Select phone book memory storage

Write into Phone book

Enter PIN

Enter PIN2

Preferred SMS message storage

Price per unit and currency table

Change Password

Service reporting control

Set Cellular Result Codes for incoming call indication

Network registration

Select radio link protocol param. for orig. non-transparent data call

Restricted SIM Access

SMS service centre address

Select Cell Broadcast Message Indication

Select TE character set

Show SMS text mode parameters

Set SMS text mode parameters

Select Message Service

Single Numbering Scheme

Signal quality

Supplementary service notifications

Supplementary service notifications

Display card ID

Bad Line Threshold

Error Threshold Multiplier

Query data bit order

Query or set the Local Polling ID

Fax: Select, read or test service class

Copy Quality Checking

Capability to receive

Query or set capabilities

Data Compression Format Conversion

Query or set session parameters

Begin or continue phase C data reception

Data Transmission

End a page or document

Kill operation, orderly FAX abort

Query or set the Local Id setting capabilities

Identify Product Model

Request Manufacturer Identification

Set bit order independently

DTE Phase C Response Timeout

Identify Product Revision

Receive Data Using HDLC Framing

Receive Data

Receive Silence

Transmit Data Using HDLC Framing

Transmit Data

Stop Transmission and Wait

Vertical resolution format conversion

Request complete TA capabilities list

Request manufacturer identification

Request TA model identification

Request TA revision identification of software status

Request TA serial number identification (IMEI) chapter 10.8

chapter 10.9

chapter 10.10

chapter 10.11

chapter 10.12

chapter 10.13

chapter 10.14

chapter 10.15

chapter 10.16

chapter 10.17

chapter 10.18

chapter 10.19

chapter 10.20

chapter 10.21

chapter 10.22

chapter 10.23

chapter 10.24

chapter 10.25

chapter 10.26

chapter 10.27

chapter 10.28

chapter 1.10

chapter 5.3

chapter 5.5

chapter 5.7

chapter 5.9

chapter 14.3

chapter 14.4

chapter 4.1

chapter 4.2

chapter 11.12

chapter 8.11

chapter 4.6

chapter 6.24

chapter 6.25

chapter 7.3


chapter 11.13

chapter 11.14

chapter 1.12

chapter 11.15

chapter 11.16

chapter 11.17

chapter 6.26

chapter 7.4

chapter 8.12

chapter 8.13

chapter 12.4

chapter 10.2

chapter 10.3

chapter 10.4

chapter 10.5

chapter 10.6

chapter 10.7


Page 273


AT+ILRR

AT+IPR

AT+VTD

AT+VTS

AT+WS46

AT\Q

AT^MONI

AT^MONP

AT^SACM

AT^SALS

AT^SCFG

AT^SCID

AT^SCKS

AT^SCNI

AT^SCTM

AT^SDLD

AT^SGAUTH

AT^SGCONF

AT^SHOM

AT^SIND

AT^SLCC

AT^SLCD

AT^SLCK

AT^SLMS

AT^SM20

AT^SMGL

AT^SMGO

AT^SMGR

AT^SMONC

AT^SMONG

Table 2.3

AT^SNFD

AT^SNFI

AT^SNFO

AT^SNFPT

AT^SNFV

AT^SNFW

AT^SPBC

AT^SPBD

AT^SPBG

AT^SPBS

AT^SPIC

AT^SPLM

AT^SPLR

AT^SPLW

AT^SPWD

AT^SRTC

AT^SSCONF

AT^SSDA

AT^SSMSS

AT^STCD

ATA

ATA

ATD

Set TE-TA local rate reporting

Set fixed local rate

Tone duration

DTMF and tone generation

Select wireless network

Flow control

Monitor idle mode and dedicated mode

Monitor neighbour cells

Advice of charge and query of ACM and ACMmax

Alternate Line Service

Extended Configuration Setting

Display SIM card identification number

Query SIM and Chip Card Holder Status

List Call Number Information

Set critical operating temperature presentation mode or query temperature

Delete the'last number redial'memory

Set type of authentication for PPP connection

Configuration of GPRS related Parameters

Display Homezone

Extended Indicator Control

Siemens defined command to list the current calls of the ME

Display Last Call Duration

Facility lock

List SMS Memory Storage

Set M20 compatibility mode

List SMS messages from preferred store without setting status to REC

READ

Set or query SMS overflow presentation mode or query SMS overflow

Read SMS message without setting status to REC READ

Cell Monitoring

GPRS Monitor

Switch off mobile station

Set audio parameters to manufacturer default values

Set microphone path parameters

Set audio output (= loudspeaker path) parameter

Set progress tones

Set loudspeaker volume

Write audio setting in non-volatile store

Search the first entry in the sorted telephone book

Purge phone book memory storage

Read current Phone book entries

Step through the selected phone book alphabetically

Display PIN counter

Read the PLMN list

Read entry from the preferred operators list

Write an entry to the preferred operators list

Change Password

Ring tone configuration

SMS Command Configuration

Set SMS Display Availability

Set Short Message Storage Sequence

Display Total Call Duration

Answer a call

Manual response to a network request for PDP context activation

Mobile originated call to dial a number chapter 3.6

chapter 3.7

chapter 15.6

chapter 15.7

chapter 2.7

chapter 3.1

chapter 7.6

chapter 7.7

chapter 8.2

chapter 7.9

chapter 1.13

chapter 12.3

chapter 12.2

chapter 6.27


chapter 9.12

chapter 9.13

chapter 7.10

chapter 2.3


chapter 4.5

chapter 11.18

Chapter 1.14


chapter 4.3

chapter 7.11

chapter 7.12

chapter 7.13

chapter 4.7

chapter 15.19

chapter 11.22

chapter 11.23

chapter 11.24

chapter 6.29

chapter 6.2

chapter 9.14

chapter 6.3


chapter 7.5

chapter 7.8

chapter 1.9

chapter 15.10

chapter 15.11

chapter 15.13

chapter 15.14

chapter 15.17

chapter 15.18

chapter 14.5

chapter 14.6

chapter 14.7


Page 274


ATO

ATP

ATQ

ATS0

ATS0

ATS10

ATS18

ATS3

ATS4

ATS5

ATS6

ATS7

ATS8

ATT

ATV

ATX

ATZ

ATE

ATH

ATH

ATI

ATL

ATM

ATD*98#

ATD*99#

ATD><mem><n

ATD><n

ATD><str

ATDI

ATDL

Request GPRS IP service

Request GPRS service

Originate call to phone number in memory

Originate call to phone number selected from active memory

Originate call to phone number in memory with corre sponding field

Mobile originated call to dialable ISDN number <n>

Redial last telephone number used

Enable command echo

Disconnect existing connection

Manual rejection of a network request for PDP context activation

Display product identification information

Set monitor speaker loudness

Set monitor speaker mode

Switch from command mode to data mode / PPP online mode

Select pulse dialing

Set result code presentation mode

Set number of rings before automatically answering the call

Automatic response to a network request for PDP context activation

Set disconnect delay after indicating the absence of data carrier

Extended call release report

Write command line termination character

Set response formatting character

Write command line editing character

Set pause before blind dialing

Set number of seconds to wait for connection completion

Set number of seconds to wait for comma dialing modifier

Select tone dialing

Set result code format mode

Set CONNECT result code format and call monitoring

Set all current parameters to user defined profile

Table 19.9: Alphabetical List of AT Commands

VERSION 1.01 chapter 6.17

chapter 6.16

chapter 1.4

chapter 6.11

chapter 9.18

chapter 6.15

chapter 2.5

chapter 17.2

chapter 17.3

chapter 17.4

chapter 6.12

chapter 6.13

chapter 6.14

chapter 6.19

chapter 1.5

chapter 1.6

chapter 2.7

chapter 9.16

chapter 9.15

chapter 6.4

chapter 6.5

chapter 6.6

chapter 6.7

chapter 6.8

chapter 3.5

chapter 6.9

chapter 9.17

chapter 5.1

chapter 15.2

chapter 15.3


Page 275