TC65i AT-Commands Set. Manual

Write Command

(Continued)

AT^SIND=<indDescr>, <mode>

Response(s)

ERROR

+CME ERROR: <err>

Write Command

AT^SIND="lsta", <mode>[, <lstaLevel>]

Response(s)

^SIND: "lsta", <mode>[, <lstaLevel>]

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Unsolicited Result Codes

URC 1

Format of the standard indicator:

+CIEV: <indDescr>, <indValue>

Value related to an indicator has changed.

URC 2

Format of the "adnread" indicator issued when accessing the ADN phonebook records stored on the SIM:

+CIEV: <indDescr>, <adnEntry>, <adnNumber>, <adnType>, <adnText>

+CIEV: <indDescr>, "READY"

One URC is issued for every used Abbreviated Dialing Number (ADN) phonebook record. After the last record

of the ADN phonebook was read, a URC with "READY" tag signals end of processing.

URC 3

Format of the Voice Message indicator, if the number of waiting messages is delivered by the network:

+CIEV: <indDescr>, <indValue>, <vmCounter>

If the number of waiting messages is not delivered the standard indicator applies.

URC 4

Format of the "eons" indicator:

+CIEV: <indDescr>, <indValue>, <eonsOperator>, <servProvider>

One URC is issued for each new LAI (Location Area Information) broadcast by the network.

URC 5

Format of the "nitz" indicator:

+CIEV: <indDescr>, <nitzUT>, <nitzTZ>, <nitzDST>

URC 6

Format of the "lsta" indicator:

In case <indValue> equals "0".

+CIEV: <indDescr>, <indValue>, <lstaEdv>, <lstaRssi>

The URC is issued for every radio link error. It provides the error downcounter value corresponding to number

of consecutive errors on downlink and the RSSI of the serving cell.

Error downcounter value of 10 corresponds to first error occurred on downlink, 0 corresponds to last before

cell loss.

URC 7

In case <indValue> equals "1".

+CIEV: <indDescr>, <indValue>, <lstaNo>, <lstaMax>, <lstaMin>, <lstaMean>,

After the error downcounter reaches the value 0 the URC provides some statistic parameters of signal

strength distribution across the band.

Parameter Description

<indDescr>^(str)

String values and their <indValue> ranges.

All indicators supported by AT+CIND are accessible with this command, too. A detailed description of these indi-

cators can be found there.

The following indicators are accessible via AT^SIND only:

“audio“

Activity of the built-in audio unit.

Audio unit not active.

Audio unit is active, for example:

MO voice call: Indicator is output with value 1 when dialing starts.

MT voice call: Indicator is output with value 1 when call is ringing.

“vmwait1“

Voice Message Waiting Indication for line 1

The value 0 notifies that no new voice message is available, and is pro-

vided by the service center to clear the voice message indication after

the subscriber has retrieved all voice messages.

The value 1 notifies the subscriber that the mailbox contains one or

several messages.

"vmwait1" and "vmwait2" indicate the receipt of a special short message with

a Voice Message Waiting Indicator. The service must be provisioned by the

operator.

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

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

further details refer to the AT^SALS command.

The presentation mode of the indicator varies with the operator: If more than

one message are waiting, some operators only indicate the first one, others

deliver the indicator each time a new voice message is put into the mailbox.

After the subscriber has retrieved all voice messages the service center auto-

matically sends another message indication which provides the value 0.

Some operators may also send the number of waiting voice messages along

with the indication. In this case, the number will be displayed by the TC65i as

part of the URC. For example, "+CIEV: vmwait1,1,5" notifies that five new voice

messages are waiting. However, it should be noted that neither the read com-

mand AT^SIND? nor the write command AT^SIND=<mode>,2 display the

number of waiting messages.

The "vmwait" indicators do not apply if a network provider signals new voice

mail(s) via standard SMS. In this case the indicator "message" will be displayed

(see AT+CIND).

“vmwait2“

Voice Message Waiting Indication for line 2

See description of "vmwait1".

“ciphcall“

Ciphering Status Change Indication

Current call or SMS is not ciphered.

Current call or SMS is ciphered.

As stated in GSM specifications 02.07 and 02.09 the ciphering indicator feature

allows the TC65i 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 presentaion will take place.

The following restrictions apply if the same serial channel is used for AT^SIND

"ciphcall" indication and for the action triggering this URC. In general, the rec-

ommended solution is to use a dedicated channel for all status signalling via

URCs.

• If an unciphered mobile originated SMS is performed, AT^SIND "ciphcall"

URCs on the same serial channel will be issued after the related "OK" and

indicate the ciphering state at this time.

• 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.

“adnread“

Abbreviated Dialing Number (ADN) Phonebook Read Indication

Phonebook reading is not finished.

Phonebook reading is finished.

Every time after entering the AT+CPIN the module starts reading the ADN

phonebook. This can be used to enable the TE to output the phonebook

records as URCs. The advantage is that the user does not need to wait until

the phonebook read command AT+CPBR is accessible after entering the SIM

PIN (depending on the SIM card this may take up to 30 seconds).

If <mode>=1 all used ADN phonebook records stored on the SIM will be output

as URCs after SIM PIN authentication has been performed successfully. A

URC with "READY" tag issued at the end of the list indicates that TC65i has

finished reading the phonebook.

Note that the settings of AT^SIND and AT+CMER will be restored to their default

values when restarting the TC65i. Therefore it is recommended that the set-

tings be enabled before entering the SIM PIN. This can be done, for example,

after rebooting the TC65i.

“eons“

Enhanced Operator Name String (EONS) Indication

The Enhanced Operator Name String indicator feature allows the TC65i to out-

put various operator names for different PLMN identities via URC. It also allows

the output of a different operator name based on a subset of the registered net-

work by using a range of Location Area Codes (LACs) or a single LAC.

The presentation of the "eons" indicator is determined by network activity. For

example, the indicator appears every time a location update occurs or a NITZ

information is sent, no matter whether or not the status of the EONS informa-

tion has changed. This means that the same EONS information may be

reported several times.

The EONS tables are stored in the SIM card and will be read at power-up.

Following are the SIM Elementary Files that are affected by the introduction of

EONS feature in the SIM card:

EF_SST (SIM Service Table) - describes which features are active.

EF_OPL (Operator PLMN List) - contains the PLMN identification and location ID

together with the index of the corresponding PNN record

EF_PNN (PLMN Network Name) - contains the full and short form version of the

network name for the registered PLMN

If the Operator Name Source is CPHS Operator Name String long and short

form, refer to <indValue>, the following two SIM Elementary Files will be

used:

EF_ONString (Operator Name String) - contains the name of the PLMN operator

who issued the SIM.

EF_OPShort (Operator Name Short form) - contains a short form of the name of

the PLMN operator who issued the SIM.

“nitz“

Network Identity and Time Zone indication

This indicator shows the time relevant information elements of an MM Informa-

tion (MMI) or GMM Information (GMMI) message received from the network

(see GSM 24.008, ch. 9.2.15a and 9.4.19). The network usually sends a NITZ

indicator when the mobile attaches to the network, when it enters a location

area with different time zone or when a daylight change occurs.

A NITZ indicator may consist of the following parameters: Universal Time (UT),

local Time Zone (TZ), Daylight Saving Time (DST). All information elements of

MMI/GMMI are optional and therefore, the presentation of the parameters

<nitzUT>, <nitzTZ>, <nitzDST> varies with the network. For example, the

network may send all three parameters UT, TZ, DST, or only UT and TZ or only

TZ.

UT is indicated in usual date/time format and represents the current world time

(GMT) at the moment when sent.

TZ is given as a positive (east) or negative (west) offset from UT in units of 15

minutes.

DST shows the number of hours added to the local TZ because of daylight sav-

ing time (summertime) adjustment. Usually DST is 1 hour but it can be also 2

hours in certain locations.

Example for time and time zone with DST:

+CIEV: nitz,"04/07/23,13:39:20",-28,1

In this example TZ is -28, showing a time offset of -7 hours (west) to Universal

Time/GMT (which never changes for DST). DST is 1 which indicates that one

hour was added to TZ because of Daylight Saving Time. If a network does not

send the DST parameter the TZ value would be -32 (8 hours west) as would

be done in winter:

+CIEV: nitz,"04/11/23,13:39:20",-32

Please be aware that despite the last NITZ value can be looked up again via

"AT^SIND=nitz,2" the returned values may be out of date. Especially the UT

value is obsolete because there is no internal NITZ clock and therefore no con-

tinuation of UT.

NITZ values are lost when the module detaches from network. Also when a

manual network selection fails and the module automatically falls back to the

previous network the NITZ values cannot be recalled. Nevertheless an indi-

cated time zone is valid until a new MMI/GMMI will trigger another NITZ indi-

cation.

“simlocal“

SIM availability "+CIEV" URC indicates if the SIM is available.

SIM removed.

SIM inserted.

“simstatus“

SIM Status Indication

The SIM Status Indicator allows to query the status of the SIM (Subscriber

Identity Module).

SIM card removed.

Note: Another way to verify the SIM card connection is the "^SCKS"

URC enabled with AT^SCKS. For use after restart, its presentation

mode can be stored to the user profile with AT&W.

SIM card inserted.

SIM PIN1 not required - SIM card unlocked. TC65i automatically regis-

ters to the GSM network without requesting SIM PIN1.

SIM PIN1 required - SIM card locked. SIM PIN1 must be entered to

enable TC65i to register to the GSM network.

Personalization info ready - CHV (Card Holder Verification) data have

been verified (if required).

SIM initialization completed - ME has finished reading SIM data.

Note: Another way to notify the user when SIM data are accessible is

the "^SSIM READY" URC enabled with AT^SSET. For use after restart,

its presentation mode can be stored to the user profile with AT&W.

“band“

Currently selected frequency band or band combination.

1...15

Identical with <rbc> of AT^SCFG. The value indicates the band(s) cur-

rently available for network selection, depending on the network config-

uration either a single band or a dualband combination. The URC

appears whenever the status of the currently available band(s)

changes, for example after using the AT^SCFG command to change

the "Radio/Band" parameters <rba> or <rbp>. Please see AT^SCFG

for further detail about the feature "Radio/Band" selection.

“lsta“

Link Stability Indication

The Link Stability indicator feature allows the TC65i to output radio link errors

and statistic parameters of signal strength distribution across the band via

URC.

Radio link error.

Radio link signal strength distribution.

The presentation of the "lsta" indicator is determined by the radio link spectrum

shape. For example, each time a radio link error appears the URC indicates an

Error Downcounter value and the RSSI of the serving cell to provide some kind

of warning. Every consecutive error decrements the Error Downcounter value

and successful downlink signal reception resets it to start value of 10. The fac-

tor on which Error Downcounter is decremented depends on network settings.

Error Downcounter value 0 means that the ME has lost the cell and will start

the cell reselection process. In this case the URC is enhanced and includes the

following statistic parameters of signal strength distribution across the band.

These are:

- Number of reported channels,

- Maximal signal strength value,

- Minimal signal strength value,

- Mean value of signal strength across frequency band and

- Variance of signal strength across frequency band.

To avoid that radio link error URCs are output too often, when radio conditions

are bad, you can select a lower warning level with <lstaLevel>.

(num)

Integer type value in the range stated above for the corresponding <indDescr>.

Notes specific to the EONS feature:

If the indicator is "eons", the <indValue> is a type associated to the operator name according to GSM 22.101

[27]. This type depends on the source of the operator name.

Priority of types associated to the operator names is defined as follows (the type listed first has the highest pri-

ority). If a type cannot be indicated the next one will be used.

Not registered.

EF-OPL and EF-PNN (alphanumeric format, can contain up to 24 characters.)

Operator Name String in long and short format according to Common PCN

Handset Specification (CPHS) [28] (alphanumeric format, can contain up to 16

characters).

Name information received by the NITZ service long and short form (alphanu-

meric format, can contain up to 16 characters). The short form will be displayed

only if EF_OPShort from CPHS is available.

Any operator name stored internal to the ME (alphanumeric format, can con-

tain up to 16 characters).

Broadcast MCC-MNC (numeric format which consists of a 3-digit country code

plus a 2- or 3-digit network code).

The name information received by the NITZ service (type 3) is stored non-volatile. It replaces the operator name

of the registered PLMN (type 4) or its numeric form (type 5) stored in the ME. But if the ME, after restart, registers

to another PLMN that is not equal to the saved NITZ name information, the NITZ name information must be

invalidated. If the type is 2, 4 or 5, AT+COPS with the appropriate <mode> displays the same operator name.

<mode>^(num)

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

issued. <mode>=0 is power-up and factory default of indicators defined by

AT^SIND only.

Indicator is registered.

• Indicator event reports are controlled via AT+CMER.

• All indicators can be registered or deregistered via AT^SIND, but different

default settings apply: Power-up and factory default of the indicators sup-

ported by AT+CIND is <mode>=1, while, as stated above, indicators defined

by AT^SIND only are set to <mode>=0.

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

<adnEntry>^(num)

ADN phonebook record number on the SIM.

<adnNumber>^(str)

Phone number, for further details see AT+CPBR.

<adnType>^(num)

Address type, for further details see AT+CPBR.

145

Dialing string <adnNumber> includes international access code character '+'.

209

Dialing string <adnNumber> contains printable non-alphabetic non-digit char-

acters saved with the number string.

129

otherwise

<adnText>^(str)

Text assigned to a phone number. For further details see AT+CPBR.

If delivered by the network: Number of new voice messages sent as part of the Voice Message Waiting Indicator.

Refer to <indDescr>.

Operator in format which depends on the type associated to the operator name. Refer to <indValue>.

<servProvider>^(str)

Service Provider Name according to the status settings (SIM Service No. 17) in the SIM Service Table (SST) of

the SIM.

Universal Time delivered as part of the "nitz" Indicator. Refer to <indDescr>.

Time Zone delivered as part of the "nitz" Indicator. Refer to <indDescr>.

Adjustment for Daylight Saving Time as part of the "nitz" Indicator. Refer to <indDescr>.

<lstaLevel>^(num)

Warning Level (0-10)

User value to limit the indication of radio link errors. Refer to <indDescr>.

<lstaEdv>^(num)

EDV (0-10)

Error Downcounter value. Refer to <indDescr>.

<lstaRssi>^(num)

(value-110) dBm

Received signal strength indication value. Refer to <indDescr>.

<lstaNo>^(num)

Number of reported channels. Refer to <indDescr>.

<lstaMax>^(num)

(value-110) dBm

Maximal received signal strength value. Refer to <indDescr>.

<lstaMin>^(num)

(value-110) dBm

Minimal received signal strength value. Refer to <indDescr>.

<lstaMean>^(num)

(value-110) dBm

Mean value of received signal strength across frequency. Refer to <indDescr>.

<lstaVar>^(num)

Variance of signal strength across frequency. Refer to <indDescr>.

Example

Activation and use of indicator "audio":

AT^SIND="audio",1

You register the indicator "audio".

^SIND: audio,1,0

AT+CMER=2,,,2

You activate the Indicator Event Report with AT+CMER.

A set of all registered URCs is presented. (Please note that the example

includes the indicators registered due to the power-up default settings

of AT+CIND.)

+CIEV: battchg,5

+CIEV: signal,0

+CIEV: service,1

+CIEV: sounder,0

+CIEV: message,1

+CIEV: call,0

+CIEV: roam,0

+CIEV: smsfull,0

+CIEV: rssi,4

+CIEV: audio,0

3.4

AT+CEER Extended Error Report

AT+CEER returns an extended error report regarding the reason of the last

• call release

• failure to set up a call (both mobile originated or terminated)

• failure to modify a call by using Supplementary Services

• failed attempt to activate, register, query, deactivate or deregister a Supplementary Service

• unsuccessful GPRS attach or unsuccessful PDP context activation

• GPRS detach or PDP context deactivation

The release cause report is presented in numeric format. Default output in case of a none-error-situation is

+CEER: 0,0,0. A description associated with each number can be found in the tables given in the following sub-

clauses and the relevant GSM specifications.

The first parameter <locationID> serves to locate the other two parameters. Depending on the failure or

release cause either <reason> or <ssRelease> are applicable, i.e. if <reason> ≠ 0, then <ssRelease> = 0.

Vice versa, if <reason> = 0, then <ssRelease> may be ≠ 0.

In addition to AT+CEER, the command ATS18 can be used to check especially the status of fax and data calls.

Syntax

Test Command

AT+CEER=?

Response(s)

ERROR

+CME ERROR: <err>

Exec Command

AT+CEER

Response(s)

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

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

GSM 07.07

Parameter Description

<locationID>^(num)

Location ID as number code. Location IDs are listed in Section 3.4.1, Cause Location ID for the extended error

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

<reason>^(num)

Reason for last call release as number code. The number codes are listed in several tables, sorted by different

categories in the following subclauses. The tables can be found proceeding from the Location ID given in Sec-

tion 3.4.1, Cause Location ID for the extended error report.

<ssRelease>^(num)

Release cause for last Supplementary Service call (listed in Section 3.4.9, GSM Release cause for Supplemen-

tary Service Call)

Examples

EXAMPLE 1

ATD"01751223344";

A mobile originated call is rejected by the remote party.

NO CARRIER

Call setup is terminated with NO CARRIER.

AT+CEER

To check the cause, the caller enters AT+CEER.

+CEER: 8,21,0

The Location ID 8 in Section 3.4.1 points to Section 3.4.7, where 21 =

"call rejected". 0 = "no error" refers to parameter <ssRelease> that is

not applicable.

EXAMPLE 2

The user attempts to activate call barring, but uses a wrong password.

AT+clck=oi,1,"0000",3

+CME ERROR: incorrect password

AT+CEER

+CEER: 35,0,38

The Location ID 35 in Section 3.4.1 points to Section 3.4.9, where 38 =

"negative PW check" may mean that a wrong password was tried for the

first time. 0 = "no error" refers to parameter <reason> that is not appli-

cable.

3.4.1

Cause Location ID for the extended error report

Description

no error (default)

Proprietary L2 cause

GSM cause for L3 radio resource sublayer (GSM 04.08 annex F)

Proprietary cause for L3 radio resource sublayer

GSM cause for L3 mobility management (GSM 04.08 annex G)

Proprietary cause for L3 mobility management

GSM cause for L3 mobility management via MMR-SAP (GSM 04.08 annex G)

GSM cause for L3 call control (GSM 04.08 10.5.4.11 and annex H)

Proprietary cause for L3 call control

GSM cause for L3 SMS CP entity

Proprietary cause for L3 SMS CP entity

GSM cause for L3 SMS RL entity

GSM cause for L3 SMS TL entity

Proprietary cause for L3 SMS TL entity

GSM cause for L3 call-related supplementary services

Proprietary cause for L3 call-related supplementary services

Proprietary 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)

Proprietary cause for GPRS mobility management

GSM cause for session management (GSM 04.08 annex I)

127

Proprietary cause for protocol module or other local cause

128

supplementary services general problem (GSM 04.80 3.6.7)

Description

129

supplementary services invoke problem (GSM 04.80 3.6.7)

130

supplementary services result problem (GSM 04.80 3.6.7)

131

supplementary services error problem (GSM 04.80 3.6.7)

241

Proprietary cause for GPRS API

243

Proprietary cause for PPP/IP-stack

3.4.2

Proprietary L2 cause

Number

Description

242

L2 decoding error

243

L2 decoding error

244

L2 decoding error

245

L2 decoding error

246

L2 decoding error

247

L2 decodingerror

248

L2 decoding error

249

no network response received, e.g. due to low signal quality

250

L2 decoding error

251

L2 decoding error

252

L2 decoding error

253

L2 decoding error

3.4.3

GSM release cause for L3 Radio Resource (RR)

Number

Description

normal event

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

invalid mandatory information

message type non-existent or not implemented

message type not compatible with protocol state

100

conditional information element error

Number

Description

101

no cell allocation available

111

protocol error unspecified

3.4.4

Proprietary release cause for L3 Radio Resource (RR)

Number

Description

RACCHs not answered

RACCHs rejected

access class of the SIM is barred by the network provider

SABM failure

radio link counter expiry or perform abnormal release

confirm ABORT of the MM

respond to DEACT REQ

loss of coverage

reestablishment not possible

T3122 still running

cell selection in progress

responding to paging

location area code has changed

circuit switched not available

3.4.5

GSM release cause for Mobility Management (MM) or Session

Management (SM)

Number

Description

causes related to MS identification

IMSI unknown in HLR

illegal MS

IMSI unknown in VLR

IMEI not accepted

illegal ME

cause related to subscription options

PLMN not allowed

location area not allowed

roaming not allowed in this location area

causes related to PLMN specific network failures and congestion

network failure

congestion

causes related to nature of request

PDP context is deactivated because of a LLC or SNDCP failure

Number

Description

service option not supported

requested service option not subscribed

service option temporary out of order

call cannot be identified

causes related to invalid messages

semantically incorrect message

invalid mandatory information

message type non-existent or not implemented

message not compatible with protocol state

information element non-existent or not implemented

100

conditional information element error

101

messages not compatible with protocol state

111

protocol error, unspecified

causes related to 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 temporary unreachable

3.4.6

Proprietary release cause for L3 Mobility Management (MM)

Number

Description

no SIM available

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

the maximum numbers of CM connections is exceeded

the MM is not registered

the MM state is incompatible

3.4.7

GSM release cause for L3 Call Control (CC)

Number

Description

normal class

unassigned (unallocated) number

no route to destination

channel unacceptable

operator determined barring

normal call clearing

user busy

no user responding

user alerting, no answer

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

no circuit/channel available

network out of order

temporary failure

switching equipment congestion

access information discarded

requested circuit/channel not available

resource unavailable, unspecified

service or option not available class

quality of service unavailable

requested facility not subscribed

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

bearer service not implemented

ACM equal or greater than ACM max

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

Number

Description

invalid transaction identifier value

user not member of CUG

incompatible destination

invalid transit network selection

semantically incorrect message

protocol error (e.g. unknown message) class

invalid mandatory information

message type non-existant or not implemented

message type not comaptible with protocol state

information element non-existent or not implemented

100

conditional information element error

101

message not compatible with protocol

102

recovery on timer expiry

111

protocol error, unspecified

interworking class

127

interworking, unspecified

3.4.8

Proprietary release cause for L3 Call Control (CC)

Number

Description

service not available

hold procedure not available

temporary no service, previous procedure not yet finished

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

number not included in FDN list

notifications

300

called party barred incoming call

3.4.9

GSM Release cause for Supplementary Service Call

Number

Description

no error (default)

unknown subscriber

illegal subscriber

bearer service not provisioned

teleservice not provisioned

illegal equipment

call barred

CUG reject

illegal SS operation

Number

Description

SS error status

SS not available

SS subscription violation

SS incompatibility

facility not supported

absent subscriber

short term denial

long term denial

system failure

data missing

unexpected data value

PW registration failure

negative PW check

number of PW attempts violation

unknown alphabet

USSD busy

126

max nums of MPTY calls exceeded

127

resources not available

general problem codes

300

unrecognized component

301

mistyped component

302

badly structured component

invoke problem codes

303

duplicate invoke ID

304

unrecognized operation

305

mistyped parameter

306

resource limitation

307

initiating release

308

unrecognized linked ID

309

linked response unexpected

310

unexpected linked operation

return result problem codes

311

unrecognize invoke ID

312

return result unexpected

313

mistyped parameter

return error problem codes

314

unrecognized invoke ID

315

return error unexpected

316

unrecognized error

317

unexpected error

318

mistyped parameter

3.5

ATS18

Extended call release report

ATS18 controls the presentation of extended call release reports for circuit switched fax and data calls. Extended

call release reports related to voice calls are controlled via AT+CEER.

The call release report is presented in numeric format and shows as follows:

+CAUSE: <locationID>:<reason>

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

Syntax

Read Command

ATS18?

Response(s)

<n>

Write Command

ATS18=<n>

Response(s)

ERROR

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

V.250

Parameter Description

<n>^{(num)(&W)(&V)}

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

feature.

0^(&F)...255

<locationID>^(num)

Location ID as number code, see also <locationID> of AT+CEER.

Location IDs are listed in Section 3.4.1, Cause Location ID for the extended error report. Each ID is related to

another table that contains a list of <reason>s.

<reason>^(num)

Reason for last call release as number code (see also <reason> of AT+CEER).

<reason> numbers and the associated descriptions are listed in several tables, sorted by different categories

at AT+CEER. The tables can be found proceeding from the Location IDs listed in Section 3.4.1, Cause Location

ID for the extended error report.

4.2

AT&C Set Data Carrier Detect (DCD) Line mode

The AT&C command determines how the state of the DCD line (circuit 109) reflects the TC65i's internal activity.

Syntax

Exec Command

AT&C[<value>]

Response(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

V.250

Parameter Description

<value>^{(num)(&W)(&V)}

[0]

DCD line shall always be on.

1^(&F)

DCD line shall be on only when data carrier signal is present.

DCD line shall be on when one or more Internet services defined on the related

serial channel are in state "Connecting" or "Up" as described below. For details

on the various service states refer to AT^SISI, parameter <srvState> or

AT^SISO, parameter <srvState>.

• SOCKET, HTTP, SMTP, POP3: DCD shall be on when

<srvState>="Connnecting" or "Up"

• FTP: DCD shall be on when data channel is connected, i.e.

<srvState>="Up"

4.5

AT\Q Flow control

Syntax

Exec Command

AT\Q[<n>]

Response(s)

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

ERROR

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Parameter Description

<n>^{(num)(&W)(&V)}

[0]^(&F)

Disable flow control

XON/XOFF software flow control

Only CTS by DCE (TA)

RTS/CTS hardware flow control

Recommended for the following procedures: incoming or outgoing data calls,

fax calls, MUX mode.

Often, the initialization routine of Fax programs includes enabling RTS/CTS

handshake, eliminating the need to issue AT\Q3 once again.

Notes

• When using XON/XOFF flow control (AT\Q1) in online mode, +++ should not be used while the data trans-

mission is paused with XOFF. Before entering the command mode with +++ the paused transmission should

be resumed using the XON character.

• For compatibility reasons, the AT\Q command can be used in Multiplex mode, though the settings will not

take effect. However, be aware that whenever you use the AT\Q write command in Multiplex mode and then

save the current configuration to the user profile with AT&W, the changed AT\Q setting will become active after

restart.

• AT\Q is ignored if used by Java; responses will be invalid or erroneous. Also refer "TC65i Java User's Guide"

[3], Section "Configuration of Serial Interface".

• AT+IFC configures flow control separately for each data direction, while AT\Q applies to both directions.

Both commands influence each other, i.e. settings made with AT\Q apply to AT+IFC and, vice versa, AT+IFC

changes the AT\Q setting.

4.6

AT+IFC Flow Control

AT+IFC controls the flow control mode used by the TC65i separately for each data direction (send and receive).

In contrast to this, flow control settings made with AT\Q are identical for both directions.

AT+IFC and AT\Q are designed to configure the TA (i.e. TC65i). The TE must, of course, also be configured.

When programming the TE bear in mind that the flow control mode set on the TA must be compliant with the flow

control method set on the TE. Please refer notes below.

Syntax

Test Command

AT+IFC=?

Response(s)

+IFC: (list of supported <TEflowcontrol>s), (list of supported <TAflowcontrol>s)

Read Command

AT+IFC?

Response(s)

+IFC: <TEflowcontrol>, <TAflowcontrol>

Write Command

AT+IFC=<TEflowcontrol>, <TAflowcontrol>

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

V.250

Parameter Description

<TEflowcontrol>^(num)(&W)

Specifies the method used by the TA when sending data to the TE.

[0]^(&F)

none

XON/XOFF

Local setting on the TA. Terminates flow control in the TA and thus, causes the

TA to stop sending data to the remote TA.

RTS line

Local setting on the TA.

XON/XOFF

Used to evaluate flow control in the TA. If the data flow from the TA requires

that the transmission be stopped, the TE inserts the XON/OFF control charac-

ters into the data stream to be sent, over the air, to the opposite TE. It is the

responsibility of the receiving TE to recognize and filter out from the data

stream the XON/OFF control characters. So, both TEs must have XON/OFF

flow control enabled.

Also, the receiving TA must be configured to use software flow control. This

means, that if the sending TA is configured for AT+IFC=3,x the receiving TA

must be set to AT+IFC=y,1. In addition, XON/OFF flow control must be

enabled on either TE.

If the TAs and TEs on both sides are properly configured, the transmission of

the XON/OFF control characters will instantly stop the data flow. So, value "3"

has an immediate effect on the over-the-air connection between both TEs.

<TAflowcontrol>^(num)(&W)

Specifies the method used by the TA when receiving data from the TE.

[0]^(&F)

none

XON/XOFF

CTS line

Notes

• If using XON/XOFF flow control (AT+IFC=1,x or AT+IFC=3,x) in data mode, +++ should not be used while

the data transmission is paused with XOFF. Before entering the command mode with +++ the paused trans-

mission should be resumed using the XON character.

• For compatibility reasons, the AT+IFC command can be used in Multiplex mode, though the settings will not

take effect. However, be aware that whenever you use the AT+IFC write command in Multiplex mode and

then save the current configuration to the user profile with AT&W, the changed AT+IFC setting will become

active after restart if autobaud mode is disabled (for details refer AT+IPR).

• AT+IFC and AT\Q usage influence each other, i.e. settings made with AT\Q apply to AT+IFC and, vice versa,

AT+IFC changes the AT\Q setting.

• Bear in mind that when you set a flow control method for one direction on the TA (with AT+IFC) the TE must

also be configured accordingly.

• The values "1" and "2" have only local effect for the connection between TA and TE. Value "3" has an imme-

diate effect on the over-the-air connection.

• XON/OFF flow control is not recommended for transferring binary files or using the GSM character set (refer

AT+CSCS). In this case the data stream might contain characters equal to the values typically used as XON/

OFF control characters, i.e. values 11 (hex) resp. 17 (dec) and 13 (hex) resp. 19 (dec).

4.7

AT+ICF Character Framing

AT+ICF controls character framing and parity format used for receiving and transmitting data via TC65i's asyn-

chronous serial interfaces (UART).

Following settings are supported:

•

7 bits, even parity, 1 stop bit (AT+ICF=5,1)

•

7 bits, odd parity, 1 stop bit (AT+ICF=5,0)

•

8 bits, even parity, 1 stop bit (AT+ICF=2,1)

•

8 bits, no parity, 1 stop bit (AT+ICF=3)

•

8 bits, odd parity, 1 stop bit (AT+ICF=2,0)

•

8 bits, no parity, 2 stop bits (AT+ICF=1)

The selected setting is stored in the user defined profile with next AT&W. It will only be used on next start of the

TC65i if configured to use a fixed bit rate, i.e. without autobaud usage. The autobaud feature (refer AT+IPR)

detects bit rate and character framing currently used by a connected TE. However, this detection suffers some

limitations described at Section 4.9.1, Autobauding.

AT+ICF read command will always show the setting stored in the user defined profile, not a currently detected

character framing.

For compatibility reason AT+ICF can be used in Multiplex mode (refer AT+CMUX), though setting will not take

effect. However, note that settings made on multiplex channel 1 are stored in the user defined profile with next

AT&W.

If the current <format> setting uses no parity (e.g. <format>=3) and AT+ICF is used to switch to a format with

parity (e.g. <format>=2), it is necessary to explicitly set parameter <parity>, e.g. AT+ICF=2,1. If not done

correctly TC65i will respond with "+CME ERROR: invalid index". This is because for <format>=3, the parameter

<parity> is set to the internal value 'no parity' which is not supported by <format>=2. Please remember that

if an optional parameter is omitted for which no default is stated in this document, the value of the parameter

remains unchanged.

If AT+ICF modes 7E1 or 7O1 are set, the parity bit will by default not be transmitted over the air. If the remote

party expects the parity bit to be transmitted, additional settings are required via AT^STPB.

Syntax

Test Command

AT+ICF=?

Response(s)

+ICF: (list of supported <format>s), (list of supported <parity>s)

Read Command

AT+ICF?

Response(s)

+ICF: <format>[, <parity>]

Write Command

AT+ICF=[<format>[, <parity>]]

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

V.250

4.8

AT+ILRR Set TE-TA local rate reporting

The command AT+ILRR controls whether or not the intermediate result code "+ILRR" is transmitted from the TA

to the TE while a connection is being set up. The result code indicates the local rate. It is issued before the final

result code of the connection, e.g. CONNECT, is transmitted to the TE.

Syntax

Test Command

AT+ILRR=?

Response(s)

+ILRR: (list of supported <value>s)

Read Command

AT+ILRR?

Response(s)

+ILRR: <value>

Write Command

AT+ILRR=<value>

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3

Charge

Last

Reference(s)

V.250

Intermediate Result Code

+ILRR: <rate>

Indicates local port rate setting upon connection setup.

Parameter Description

<value>^{(num)(&W)(&V)}

0^(&F)

Disables reporting of local port rate

Enables reporting of local port rate

<rate>^(num)

Port rate setting upon connection setup (bps)

Autobauding (see Section 4.9.1, Autobauding). Not supported on ASC1. Not

usable with Java.

300

600

1200

2400

4800

9600

4.9

AT+IPR Bit Rate

AT+IPR allows to query and set the bit rate of the TC65i's asynchronous serial interfaces (UART).

The test command returns the values of supported automatically detectable bit rates and the values of the sup-

ported fixed bit rates.

The read command returns the the currently set <rate> value.

The write command specifies the bit rate to be used for the interface. Delivery bit rate value (<rate>) is

115200bps on ASC0 and 115200bps on ASC1. This setting will not be restored with AT&F.

If using a fixed bit rate, make sure that both TC65i and TA are configured to the same rate. A selected fixed bit

rate takes effect after the write command returns OK and is stored in non-volatile memory. It is not recommended

to set bit rates lower than 9600 bps in order to avoid timing problems (see Section 1.5, Communication between

Customer Application and TC65i for details about timing).

In case of autobauding mode (AT+IPR=0) the detected TA bit rate will not be saved and, therefore, needs to be

resynchronized after any restart of the ME (for details refer Section 4.9.1, Autobauding). If autobauding is acti-

vated, the TA will automatically recognize bit rate, character framing and parity format (refer AT+ICF) currently

used by the TE.

In Multiplex mode the write command will not change the bit rate currently used, but the new bit rate will be stored

and becomes active, when the module is restarted.

If Java is running, the firmware will ignore any settings made with AT+IPR. Responses to the read, write or test

command will be invalid or deliver "ERROR". Also refer "TC65i Java User's Guide" [3], Section "Configuring

serial interface".

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.

Syntax

Test Command

AT+IPR=?

Response(s)

+IPR: (list of supported auto-detectable <rate>s) , (list of supported fixed-only <rate>s)

Read Command

AT+IPR?

Response(s)

+IPR: <rate>

Write Command

AT+IPR=<rate>

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1

MUX2 MUX3 Charge

Last

Reference(s)

V.250

Parameter Description

<rate>^(num)(&V)

bit rate per second (bps)

Activates autobauding. Not supported on ASC1. Not usable with Java. See

Section 4.9.1, Autobauding for further details.

300

600

1200

2400

4800

9600

14400

19200

28800

38400

57600

115200

230400

460800

921600

Note

• Generally, AT+IPR should be used as a standalone command as specified in Section 1.4.2, Concatenating

AT Commands. If nevertheless combinations with other commands on the same command line cannot be

avoided, there are several constraints to be considered:

- Avoid combinations with the AT commands listed in Section 1.4.2, Concatenating AT Commands.

- Keep in mind that there shall be a minimum pause between two AT commands as specified in Section 1.5,

Communication between Customer Application and TC65i.

- If local echo is active (ATE1) and AT+IPR=x is entered with other commands you may encounter the fol-

lowing 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.

4.9.1

Autobauding

To take advantage of autobaud mode specific attention must be paid to the following requirements:

• Synchronization between TE and TA:

Ensure that TE and TA are correctly synchronized and the bit rate used by the TE is detected by the TA. To

allow the bit rate to be synchronized simply use an "AT" or "at" string. This is necessary when you start up

the ME 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.

• Restrictions on autobauding operation:

- If autobaud mode is enabled, then autobauding does not take effect immediately after the write command

AT+IPR=0 ends. Instead the old bit rate remains active. The autobaud mode is activated with the next

restart of the TA. This is indicated by any following AT+IPR read command which still returns the old bit

rate until the next restart.

Before you activate autobauding switch on the local echo with ATE1. To verify if autobauding has become

effective after restart first send only the characters "AT" or "at" and check that they are echoed within

100ms. In some cases you may need to repeat this several times, until both characters are properly ech-

oed within 100ms.

Please note that after the successful synchronization between TE and TA the autobauding mechanism of

the TA is deactivated until next restart. So, while autobauding is enabled you will need to restart the TA

each time after changing the bit rate of the TE.

- The TA cannot distinguish between 1 and 2 stop bits. Therefore, 1 stop bit will be used by the TA.

- The command A/ cannot be used.

- Only the first "AT" or "at" after restart of the module can be detected (neither "At" nor "aT"). This means

that all the AT commands have to use the same bit rate and frame type.

- The second serial interface ASC1 does not support autobauding.

- Autobauding cannot be used if the ME operates with Java.

- 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 115200 bps.

• Autobauding and bit rate after restart:

Unless the bit rate is determined, the following constraints apply:

- An incoming CSD call or a network initiated GPRS request cannot be accepted. This must be taken into

account when autobauding and autoanswer mode (ATS0 ≠ 0) are enabled at the same time, escpecially

if SIM PIN 1 authentication is done automatically and the setting ATS0 ≠ 0 is stored to the user profile with

AT&W.

- Until the bit rate is found, URCs generated after restart will be output at 115200 bps. This applies only to

user defined URCs, such as "+CREG", "CCWA", "^SCKS" etc. The URCs "^SYSSTART", "^SYSSTART

CHARGE-ONLY MODE" and "^SYSSTART AIRPLANE MODE" will not be indicated when autobauding is

enabled.

Note: To avoid any problems caused by undetermined bit rates in the direction from TA to TE we strongly

recommend to configure a fixed bit rate rather than autobauding.

• Autobauding and multiplex mode:

If autobauding is active you cannot switch to multiplex mode (see AT+CMUX).

4.10

AT+CMUX Multiplex Mode

Multiplex mode enables the use of three (virtual) channels over one serial interface [6] [7]. Every channel is used

as an independent serial link taking advantage of up to three simultaneous AT command or data sessions.

For example, the first channel can be used to send or receive data, while two channels are still available to control

the module with AT commands or to establish a dedicated channel to receive Unsolicited Result Codes (URC),

e.g. "+CIEV:" or ""RING".

TC65i incorporates an internal multiplexer and thus integrates all the functions needed to implement full-featured

multiplex solutions. For the application on top, customers have the flexibility to create their own multiplex pro-

grams conforming to the multiplexer protocol. To help system integrators save the time and expense of designing

multiplexer applications, Cinterion Wireless Modules GmbH offers WinMUX, a ready-to-use multiplex driver for

Windows XP and Windows Vista. Another approach is to develop customized solutions based on the sources of

the WinMUX driver.

Refer to [6] which provides a detailed description of the multiplex architecture and step-by-step instructions of

how to install and configure the multiplex mode. The WinMUX driver and its source files can be supplied on

request. Please contact your local distributor to obtain the latest installation software and user's guide.

All information provided in this section applies to the ASC0 interface only. The second interface ASC1 has no

support of Multiplex mode.

Multiplex mode requires character framing to be set to 8 data, no parity and 1 stop bit. This setting can be made

using (AT+ICF=3).

AT+CMUX write command is used to enter Multiplex mode. Setup of the logical channels is initiated by the TE,

i.e. the TE acts as initiator. This means that the TE shall ensure that logical channels are established before any

further actions on the channels can be started. There is a timeout of five seconds, if the multiplexer protocol is

enabled but no multiplexer control channel is established. Afterwards TC65i returns to AT command mode.

The parameter maximum frame size (N1) according to GSM 07.10 is implemented as 98 bytes by default. All

other parameters are not available. Refer to [6] for further details regarding frame size.

Multiplex mode is not usable by Java applications. The mode cannot be started if the ME is Java controlled.

If Java autostart is enabled with AT^SCFG, it is not possible to activate Multiplex mode on ASC0 or USB.

Syntax

Test Command

AT+CMUX=?

Response(s)

+CMUX: (list of supported<mode>s)

Read Command

AT+CMUX?

Response(s)

+CMUX: <mode>

ERROR

+CME ERROR: <err>

Write Command

AT+CMUX=<mode>

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

GSM 07.07, GSM 07.10, 3GPP TS 27.010

Parameter Description

<mode>^(num)

Multiplexer transparency mechanism

Basic option

<subset>^(num)

Subparameters defined in GSM07.07 are adjusted for control and logical channels as follows

UIH frames used only (control channel)

4.10.1

Restrictions on Multiplex mode

In multiplex mode, data and fax calls can only be set up on logical channel 1. Due to this restriction, AT com-

mands have a different behavior on channels 2+3 compared to channel 1. Several commands are not available,

others return different responses. This section summarizes the concerned commands. For general rules and

restrictions to be considered in Multiplex mode please refer to [6].

Table 4.1: Availability of AT Commands on Virtual Channels

Command

Behavior on channel 1

Behavior on channel 2+3

+++

not usable, but see note ²⁾

AT+CBST

as described

not usable

AT+CRLP

as described

not usable

AT+CG... (GPRS commands)

as described

see note ³⁾

AT+F... (Fax commands)

as described

not usable

AT&S

as described

not usable

ATA

as described

no Data Calls

ATD

as described

no Data Calls

ATDI

as described

not usable

ATL

as described

not usable

ATM

as described

not usable

ATO

as described

not usable

ATS6 ¹⁾

as described

not usable

ATS7 ¹⁾

as described

not usable

ATS8 ¹⁾

as described

not usable

ATS10 ¹⁾

as described

not usable

ATS18 ¹⁾

as described

not usable

1) The ME supports the registers S0 - S29. You can change S0,S3,S4,S5,S6,S7,S8,S10 and S18 using the related ATSn

commands (see starting from ATS0). The other registers are read-only and for internal use only!

2) The applicability of the +++ escape sequence depends on the customer's external application based on the Mulitplexer

Protocol. Recommendations for implementing an appropriate modem status command (MSC) are provided in [6], Section

"Escape Sequence".

3) PDP contexts can be defined on any channel, but are visible and usable only on the channel on which they are defined

(thus it is not possible to define a context on channel 2 and activate it on channel 3). GPRS connections can be estab-

lished on two channels at a time.

Table 4.2: Summary of AT commands with Different Behavior in Multiplex Mode

Command

Description

AT\Q

It is recommended to use hardware flow control (AT\Q3). XON/XOFF flow control

(AT\Q1) is not supported in Multiplex mode.

See note regarding AT\Qn settings stored with AT&W if Multiplex mode is active.

AT&V

Different default configurations on channels 1, 2 and 3.

AT&W

Different user profiles can be stored on each channel.

AT+IPR

In Multiplex mode, the write command AT+IPR=<rate> will not change the bit rate

currently used, but the new bit rate will be stored and becomes active, when the

module is restarted.

AT+IPR=0

Multiplex mode cannot be activated while autobauding is enabled.

AT+CALA

On each channel an individual <text> message can be stored. but only one time

setting applies to all channels. This means an alarm <time> set on one of the

channels overwrites the time setting on all remaining channels. Therefore, the total

number of alarm events returned by the read command AT+CALA? will always be

<n>=0, no matter whether individual text messages are stored.

When the alarm is timed out and executed the ME sends the URC only on the

channel where the most recent alarm setting was made. The alarm time will be

reset to "00/01/01,00:00:00" on all channels.

AT+CMEE

Presentation mode can be separately configured for each channel.

AT+CNMA

If Multiplex mode is activated the +CNMI parameter will be set to zero on all chan-

nels, if one channel fails to acknowledge an incoming message within the required

time.

AT+CNMI

Phase 2+ parameters can only be used on one channel. The parameter for <mt>

and <ds> on the other channels have to be set to zero. If either a SM or a Status

Report is not acknowledged, all +CNMI parameter will be set to zero on all chan-

nels.

AT+CFUN

If the ME is in Multiplexer mode, it is not recommended to activate SLEEP mode

with AT+CFUN=<fun>. The best approach to properly control SLEEP mode in this

case is to issue the PSC messages described in [6], Section "Power saving control

(PSC)".

AT+CPMS

Parameter <mem3> will be the same on all instances, but the settings of <mem1>

and <mem2> may vary on each instance.

AT^SSDA

If one instance is set to <da>=1 and <mt>=1, then all other instances must be con-

figured for <mt>=0.

4.11

AT^STPB Transmit Parity Bit (for 7E1 and 7O1 only)

This command is intended only for use with 7E1 and 7O1. In addition to the 7E1 or 7O1 settings made with

AT+ICF the command AT^STPB specifies whether or not to transmit the parity bit over the air.

Syntax

Test Command

AT^STPB=?

Response(s)

^STPB: (list of supported <n>s)

Read Command

AT^STPB?

Response(s)

^STPB: <n>

Write Command

AT^STPB=<n>

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Command Description

The test command returns the supported values of the parameter <n>.

The read command returns the current value of the parameter <n>.

The write command can be used to control the handling of the parity bit. If command fails, "+CME ERROR:

unknown" will be returned.

Parameter Description

<n>^(num)(&W)

0^(&F)

The parity bit will not be transmitted over the air and will be replaced with 0.

This mode is the default setting if 7E1 or 7O1 is activated with AT+ICF.

In a data connection 8 bits will be transmitted, including the parity bit, i.e. the

parity bit will be properly transmitted over the air. The setting shall be used if

problems are encountered when TC65i is running in the default 7E1 or 7O1

mode enabled with AT+ICF. In this case, AT^STPB=1 shall be set in addition

to the 7E1 or 7O1 settings selected with AT+ICF.

Note

• Command is usable if multiplexer is enabled but setting is ignored.

Security Commands

The AT Commands described in this chapter allow the external application to determine various security related

settings.

5.1

AT+CPIN PIN Authentication

The AT+CPIN write command can be used to enter one of the passwords listed below. The read command can

be used to check whether or not the ME is waiting for a password, or which type of password is required.

This may be for example the SIM PIN1 to register to the GSM network, or the SIM PUK1 to replace a disabled

SIM PIN1 with a new one, or the PH-SIM PIN if the client has taken precautions for preventing damage in the

event of loss or theft etc. If requested by the ME AT+CPIN may also be used for the SIM PIN2 or SIM PUK2.

If no PIN1 request is pending (for example if PIN1 authentication has been done and the same PIN1 is entered

again) TC65i responds "+CME ERROR: operation not allowed"; no further action is required.

Each time a password is entered with AT+CPIN the module starts reading data from the SIM. The duration of

reading varies with the SIM card. This may cause a delay of several seconds before all commands which need

access to SIM data are effective. See Section 23.1, Restricted access to SIM data after SIM PIN authentication

for further detail.

Syntax

Test Command

AT+CPIN=?

Response(s)

Read Command

AT+CPIN?

Response(s)

+CPIN: <code>

ERROR

+CME ERROR: <err>

Write Command

AT+CPIN=<pin>[, <new pin>]

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2

MUX3

Charge

Last

Reference(s)

GSM 07.07

Parameter Description

<pin>^(str)

Password (string type), usually SIM PIN1.

If the requested password was a PUK, such as SIM PUK1 or PH-FSIM PUK or another password, then <pin>

must be followed by <new pin>.

<new pin>^(text)

If the requested code was a PUK: specify a new password or restore the former disabled password. See Section

5.1.1, What to do if PIN or password authentication fails? for more information about when you may need to

enter the PUK.

<code>^(text)

SIM PIN authentication

READY

PIN has already been entered. No further entry needed.

SIM PIN

ME is waiting for SIM PIN1.

SIM PUK

ME is waiting for SIM PUK1 if PIN1 was disabled after three failed attempts to

enter PIN1.

SIM PIN2

ME is waiting for PIN2. This is only applicable when an attempt to access a

PIN2 related feature was acknowledged with +CME ERROR: 17 ("SIM PIN2

required"), for example when the client attempts to edit the FD phonebook). In

this case the read command AT+CPIN? also prompts for SIM PIN2. Normally,

the AT+CPIN2 command is intended for SIM PIN2.

SIM PUK2

ME is waiting for PUK2 to unblock a disabled PIN2. As above, this is only nec-

essary when the preceding command was acknowledged with +CME ERROR:

18 ("SIM PUK2 required") and only if the read command AT+CPIN? also

prompts for SIM PUK2. Normally, the AT+CPIN2 command is intended for SIM

PUK2.

Phone security locks set by client or factory

PH-SIM PIN

ME is waiting for phone-to-SIM card password if "PS" lock is active and the cli-

ent inserts other SIM card than the one used for the lock. ("PS" lock is also

referred to as phone or antitheft lock).

PH-SIM PUK

ME is waiting for Master Phone Code, if the above "PS" lock password was

incorrectly entered three times.

PH-FSIM PIN

ME is waiting for phone-to-very-first-SIM card. Necessary when "PF" lock was

set. When powered up the first time, ME locks itself to the first SIM card put into

the card holder. As a result, operation of the mobile is restricted to this one SIM

card (unless the PH-FSIM PUK is used as described below).

PH-FSIM PUK

ME is waiting for phone-to-very-first-SIM card unblocking password to be

given. Necessary when "PF" lock is active and other than first SIM card is

inserted.

PH-NET PUK

ME is waiting for network personalisation unblocking password

PH-NS PIN

ME is waiting for network subset personalisation password

PH-NS PUK

ME is waiting for network subset unblocking password

PH-SP PIN

ME is waiting for service provider personalisation password

PH-SP PUK

ME is waiting for service provider personalisation unblocking password

PH-C PIN

ME is waiting for corporate personalisation password

PH-C PUK

ME is waiting for corprorate personalisation un-blocking password

Notes

• Successful PIN authentication only confirms that the entered PIN was recognized and correct. The output of

the result code OK does not necessarily imply that the mobile isregistered to the desired network.

Typical example: PIN was entered and accepted with OK, but the ME fails to register to the network. This may

be due to missing network coverage, denied network access with currently used SIM card, no valid roaming

agreement between home network and currently available operators etc.

TC65i 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 acti-

vate an unsolicited result code which appears whenever the status of the network registration changes (e.g.

when the ME is powered up, or when the network cell changes).

•

<pin> and <new pin> can also be entered in quotation marks (e.g. "1234").

• To check the number of remaining attempts to enter the passwords use the AT^SPIC command.

• See AT+CPWD and AT^SPWD for information on passwords.

• See AT+CLCK and AT^SLCK for information on lock types.

5.1.1

What to do if PIN or password authentication fails?

PIN1 / PUK1:

After three failures to enter PIN 1, the SIM card is blocked (except for emergency calls). +CME ERROR: 12 will

prompt the client to unblock the SIM card by entering the associated PUK (= PIN Unblocking Key / Personal

Unblocking Key). After ten failed attempts to enter the PUK, the SIM card will be invalidated and no longer oper-

able (the device will respond with: +CME ERROR: 770, which stands for: SIM invalid - network reject). 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 pro-

vider. 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 per-

manently block the additional features subject to PIN2 authentification, but usually has no effect on PIN1. PIN2

consists of 4 digits, PUK2 is an 8-digit code only.

To unblock a disabled PIN2 you have two options:

• You can enter AT+CPIN2=PUK2,new PIN2.

• You can use the ATD command followed by the GSM code **052*PUK2*newPIN2*newPIN2#;.

Phone lock:

If the mobile was locked to a specific SIM card (= "PS" lock or phone lock), the PUK that came with the SIM card

cannot be used to remove the lock. After three failed attempts to enter the correct password, ME returns +CPIN:

PH-SIM PUK (= response to read command AT+CPIN?), i.e. it is now waiting for the Master Phone Code. This

is an 8-digit device code associated to the IMEI number of the mobile which can only by obtained from the man-

ufacturer or provider. When needed, contact Cinterion Wireless Modules GmbH and request the Master Phone

Code of the specific module.

There are two ways to enter the Master Phone code:

• You can enter AT+CPIN=Master Phone Code

• You can use the ATD command followed by the GSM code *#0003*Master Phone Code#;.

Usually, the Master Phone Code will be supplied by mail or e-mail. If the received number is enclosed in the *#

codes typically used for the ATD option, it is important to crop the preceding *#0003* characters and the

appended #.

Example: You may be given the string *#0003*12345678#. When prompted for the PH-SIM PUK simply enter

12345678.

If incorrectly input, the Master Phone Code is governed by a specific timing algorithm: (n-1)*256 seconds (see

table below). The timing should be considered by system integrators when designing an individual MMI.

Number of failed attempts

Time to wait before next input is allowed

1st failed attempt

No time to wait

2nd failed attempt

4 seconds

3rd failed attempt

3 * 256 seconds

4th failed attempt

4 * 256 seconds

5th failed attempt

5 * 256 seconds

6th failed attempt and so forth

6 * 256 seconds and so forth

SIM locks:

These are factory set locks, such as "PF", "PN", "PU", "PP", "PC". An 8-digit unlocking code is required to operate

the mobile with a different SIM card, or to lift the lock. The code can only be obtained from the provider.

Failure to enter the password is subject to the same timing algorithm as the Master Phone Code (see Table

above).

Call barring:

Supported modes are "AO", "OI", "OX", "AI", "IR", "AB", "AG", "AC". If the call barring password is entered incor-

rectly three times, the client will need to contact the service provider to obtain a new one.

Related sections:

"+CME ERROR: <err>" values are specified at Section 2.12.1, CME/CMS Error Code Overview. For further

instructions and examples see AT+CLCK, AT^SLCK, AT+CPWD and AT^SPWD.

For a complete list of Star-Hash codes please refer Section 23.2, Star-Hash (*#) Network Commands.

5.2

AT+CPIN2

PIN2 Authentication

AT+CPIN2 controls network authentication of the TC65i.

The read command returns an alphanumeric string indicating whether or not network authentication is required.

The write command allows the TC65i to store the entered password. This may be for example the SIM PIN2 to

benefit from the features listed below, or the SIM PUK2 to replace a disabled PIN2 with a new one. Note that

PIN2 can only be entered if PIN1 authentication was done.

If the TC65i is requesting SIM PUK2, use <pin> to enter the PUK2, followed by <new pin> to specify the new

PIN2.

Syntax

Test Command

AT+CPIN2=?

Response(s)

Read Command

AT+CPIN2?

Response(s)

+CPIN2: <code>

ERROR

+CME ERROR: <err>

Write Command

AT+CPIN2=<pin>[, <new pin>]

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2

MUX3

Charge

Last

Reference(s)

GSM 07.07

Parameter Description

<pin>^(str)

Password (string type), usually SIM PIN2 or, if requested, SIM PUK2.

<new pin>^(str)

If the requested code was SIM PUK2: new password (PIN2).

See Section 5.1.1, What to do if PIN or password authentication fails? for more information about when you may

need to enter the PUK.

<code>^(text)

READY

ME is not pending for any password.

SIM PIN2

ME is waiting for SIM PIN2.

This <code> is returned only when PIN2 authentication has not yet been done

or has failed ("+CME ERROR: 17").

SIM PUK2

ME is waiting for SIM PUK2.

This <code> is returned only when PIN2 authentication has failed and ME is

pending for SIM PUK2 (i.e. "+CME ERROR: 18").

Note

• Functions accessible only after PIN2 authentication:

AT+CACM: Accumulated call meter (ACM) reset or query

AT+CAMM: Accumulated call meter maximum (ACMmax) set or query

AT+CLCK: Facility lock to "FD" (Fixed dialing phonebook)

AT^SLCK: Facility lock to "FD" (Fixed dialing phonebook)

AT+CPWD: Change "P2"password

AT^SPWD: Change "P2"password

AT+CPUC: Price per unit and currency table

AT+CPIN2: Enter SIM PIN2 or SIM PUK2 if requested.

For example, SIM PIN2 will be needed when you attempt to edit the "FD" phonebook and ME returns "+CME

ERROR: 17" or "+CPIN: SIM PIN2".

Once the required <pin> has been entered correctly, PIN2 authentication code changes to READY. After

300s, a repetition of the authentication process is required (PIN2 authentication code changes from READY

to SIM PIN2).

Examples

EXAMPLE 1

Change PIN2

AT+CPWD="P2","0000","8888"

(where "0000" = old PIN2 and "8888" = new PIN2)

EXAMPLE 2

Unblock a disabled PIN2

AT+CPIN2?

+CPIN2: SIM PUK2

PIN2 has been disabled, PUK2 must be entered

to define a new PIN2

AT+CPIN2=12345678,8888

where "12345678" is the PUK2, and "8888" the new

PIN2.

EXAMPLE 3

Write into "FD" phonebook

AT+CPBS="FD"

AT+CPBW=2,"+493012345678",145,"Charly"

+CME ERROR: 17

access denied due to missing PIN2 authentication

AT+CPIN2=8888

AT+CPBW=2,"+493012345678",145,"Charly"

5.3

AT^SPIC Display PIN counter

The AT^SPIC command can be used to find out whether the ME is waiting for a password and, if so, how many

attempts are left to enter the password.

The execute command returns the number of attempts still available for entering the currently required password,

for example the PIN, PUK, PH-SIM PUK etc.

The read command AT^SPIC? indicates which password the number of attempts stated by the execute com-

mand actually refers to. Also, the write command may be used to query the counter for a specific password: It

indicates the number of attempts still available for entering the password identified by <facility>, for example

the PIN, PIN2, PH-SIM PIN etc.

To check whether or not you need to enter a password use the read commands AT+CPIN?, AT+CPIN2? and

AT^SPIC?. If the response to AT+CPIN? is "READY" the counter of the execute command AT^SPIC relates to

PIN2. See last example. If the responses to AT+CPIN? and AT+CPIN2? both read "READY", no password is

currently required, and the referrer of the execute command AT^SPIC is explicitly undefined.

Syntax

Test Command

AT^SPIC=?

Response(s)

Read Command

AT^SPIC?

Response(s)

^SPIC: <code>

Exec Command

AT^SPIC

Response(s)

^SPIC: <counter>

Write Command

AT^SPIC=<facility>

Response(s)

^SPIC: <counter>

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1

MUX2

MUX3

Charge

Last

Parameter Description

<counter>^(num)

Number of attempts left to enter the currently required password. This number will be counted down after each

failure.

<facility>^(str)

Password for which the corresponding PIN counter is to be displayed.

“SC“

SIM PIN or SIM PUK. If the SIM PIN has been deactivated after three failed

attempts, the counter for SIM PUK will be returned instead.

“PS“

"Phone code" or "device code" (cf. AT+CLCK and AT+CPWD). If incorrectly

entered three times, the Master Phone Code is required to lift the lock and the

number of remaining attempts for the master phonecode will be returned.

“P2“

SIM PIN2 or SIM PUK2. If the SIM PIN2 has been deactivated after three failed

attempts, the counter for SIM PUK2 will be returned instead.

“PN“

Network Personalisation

<code>^(text)

Identification of the currently required password.

SIM PIN

ME is waiting for SIM PIN1.

SIM PUK

ME is waiting for SIM PUK1 if PIN1 was disabled after three failed attempts to

enter PIN1.

SIM PIN2

ME is waiting for PIN2, when the attempt to access PIN2 requiring features was

acknowledged with "+CME ERROR: 17" (e.g. if the user attempts to edit the

FD phonebook).

SIM PUK2

ME is waiting for PUK2 to unblock a disabled PIN2. Necessary if preceding

command was acknowledged with "+CME ERROR: 18".

PH-SIM PIN

ME is waiting for phone-to-SIM card password if ''PS'' lock is active and user

inserts other SIM card than the one used for the lock. (''PS'' lock is also referred

to as phone or antitheft lock).

PH-SIM PUK

ME is waiting for Master Phone Code, if the above ''PS'' lock password was

incorrectly entered three times.

PH-NET PUK

ME is waiting for network personalisation unblocking password

Notes

• Whenever the required password changes, <counter> changes to reflect that change. Please refer to the

examples below.

• For passwords associated to the phone lock (''PS'' lock set by user or factory) or other factory set locks, such

as ''PF'', ''PN'', ''PU'', ''PP'', ''PC'' the number of attempts is subject to a timing algorithm explained in

AT+CPIN. If these passwords are incorrectly entered the counter first returns 3, 2 and 1 remaining attempt(s),

but then gives the total number of attempts which amounts to 63 (see example below).

• See also Chapters AT+CLCK, AT+CPIN, AT+CPIN2, AT+CPWD, AT^SLCK for further information on locks and

passwords.

Examples

EXAMPLE 1

The user fails to provide a correct SIM PIN three times. The counter decreases each time. After the counter

reaches zero, the SIM PUK is required. After each failure to enter a correct SIM PUK, the counter decreases.

at+cpin?

+CPIN: SIM PIN

Currently required password is PIN1.

at^spic

^SPIC: 3

3 attempts left.

at+cpin=9999

+CME ERROR: incorrect password

at^spic

^SPIC: 2

2 attempts left.

at+cpin=9999

+CME ERROR: incorrect password

at^spic

^SPIC: 1

1 attempt left.

at+cpin=9999

+CME ERROR: incorrect password

at+cpin?

+CPIN: SIM PUK

Now required password is PUK 1.

at^spic

^SPIC: 10

10 attempts left for PUK 1.

at+cpin=01234567,1234

+CME ERROR: incorrect password

at^spic

^SPIC: 9

9 attempts left for PUK 1.

EXAMPLE 2

Though a mobile is locked to a specific SIM card (phone lock), the user attempts to operate it with another

SIM card. The user correctly enters the SIM PIN of the SIM card currently inserted, but then fails to give the

''PS'' lock password (PH-SIM PUK):

at+cpin=9999

at+cpin?

+CPIN: PH-SIM PIN

ME is waiting for the phone lock password.

at^spic

^SPIC: 3

3 attempts left.

at+cpin=4711

+CME ERROR: incorrect password

at^spic?

^SPIC: 2

2 attempts left.

at+cpin=4712

+CME ERROR: incorrect password

at^spic

^SPIC: 1

1 attempt left.

at^spic?

^SPIC: PH-SIM PIN

Displayed counter refers to phone lock password.

at+cpin=4713

+CME ERROR: incorrect password

at^spic

^SPIC: 63

at^spic?

^SPIC: PH-SIM PUK

Displayed counter refers to master phone code.

at+cpin=4714

+CME ERROR: incorrect password

at^spic

^SPIC: 63

EXAMPLE 3

This example shows that after successful SIM PIN1 authentication the counter of the AT^SPIC execute and

read command refers to SIM PIN2, i.e. it does not reflect the status of SIM PIN1. This may be a problem if

the user enters a wrong PIN1 and is not aware that the number of attempts left to enter SIM PIN1 is counted

down.

+CREG: 0

at+cpin=1234

+CREG: 2

+CREG: 1

The mobile ist properly registered to the network.

at+cpin?

+CPIN: READY

The AT+CPIN? read command confirms that SIM

PIN1 authentication was successful.

at^spic

^SPIC: 3

As SIM PIN1 authentication was successful, the

counter relates to SIM PIN2 and correctly indicates

that the user has 3 attempts to enter SIM PIN2.

AT^SPIC?

Likewise, the read command notifies that the ME is

waiting for SIM PIN2.

^SPIC: SIM PIN2

at+clck="SC",0,456789

First attempt to enter a wrong SIM PIN1.

+CME ERROR: incorrect password

at^spic

^SPIC: 3

SIM PIN1 authentication is still valid, and the counter

relates to SIM PIN2.

at+clck="SC",0,456789

Second attempt to enter a wrong SIM PIN1.

+CME ERROR: incorrect password

at^spic

^SPIC: 3

SIM PIN1 authentication is still valid, and the counter

relates to SIM PIN2.

at+clck="SC",0,456789

Third attempt to enter a wrong SIM PIN1.

+CME ERROR: incorrect password

+CREG: 0

SIM PIN1 authentication is no longer valid.

at^spic

^SPIC: 10

This time, after the SIM PIN1 code has been dis-

abled, the counter indicates the status of SIM PIN1

and notifies that 10 attempts are left to enter the SIM

PUK.

To avoid conflicts we recommend to use the AT^SPIC read and write commands rather than the execute com-

mand only. The read command clearly states the currently required password, and the write command may

be used to get the counter for a specific <facility>, in this case for example "P2".

5.4

AT+CLCK Facility lock

AT+CLCK can be used to lock, unlock or interrogate a network or ME <facility>. The command can be

aborted when network facilities are being set or interrogated.

Syntax

Test Command

AT+CLCK=?

Response(s)

+CLCK:list of supported <facility>s

Write Command

AT+CLCK=<facility>, <mode>[, <password>][, <class>]

Response(s)

if <mode> is not equal 2 and command successful:

if <mode>= 2 and command successful:

+CLCK: <status>[, <class>]

[+CLCK: <status>[, <class>]]

[+CLCK: ...]

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

GSM 07.07, GSM

02.04, GSM

02.88,

GSM 03.88, GSM

04.88

Parameter Description

<facility>^(str)

Phone security locks set by client or factory

Primarily intended for the client to take safety precautions, "SC", "PS" and "FD" can be configured individually.

"PS" may also be factory set.

Parameter <class> is not applicable to security locks.

See examples below for further details.

“SC“

SIM (lock SIM cards). SIM requests password upon ME power-up and when

this lock command is issued.

<password>: SIM PIN1.

“PS“

Phone locked to SIM card. ME requests password when other than current SIM

card is inserted.

"PS" lock is frequently referred to as "phone lock", or "device lock". Accord-

ingly, the password may be called "phone code" or "device code". The "PS"

password is not associated with the PUK of the SIM card. If incorrectly entered

three times, the Master Phone Code is required to lift the lock. This is an 8-digit

device code associated to the IMEI number of the mobile which can only be

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.

“FD“

SIM fixed dialing memory: If the mobile is locked to "FD", only the phone num-

bers stored to the "FD" memory can be dialed. (Capacity of the "FD" phone-

book is 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 the

"FD" phonebook.

Result code for voice, data and fax calls to numbers not stored in the "FD"

phonebook is "+CME ERROR: call barred".

• Access to defined Supplementary Service Call forwarding is possible only

if the exact corresponding public MMI *# code for the desired service is

stored in the "FD" phonebook and used with ATD.

Indication is "+CME ERROR: call barred".

Using Supplementary Services ATD*#code without dialing number is pos-

sible.

• SMS can be sent only to phone numbers which are stored in the "FD"

phonebook.

Also a valid Service Center Address (international format) must be present

in the "FD" phonebook to allow sending SMS at all.

Indication is "+CMS ERROR: operation not allowed".

• GPRS commands can be used only if the "FD" phonebook contains an

entry with phone number ''*99#''. This single entry enables all GPRS com-

mands, including AT commands and modem compatibility commands like

''ATD*99***1#'' or ''ATD*98***1#''.

Indication is "+CME ERROR: call barred".

Factory defined SIM locks:

Typical examples of factory set SIM locks are prepaid phones or network locks, used to restrict the operation of

a mobile to a specific provider or operator. The client should be aware that each of these lock types can only be

unlocked if the associated password is available. For example, a mobile can be locked to accept only SIM cards

from the respective provider, or even one single SIM card. Once a different SIM card is inserted the ME will

prompt the client to enter a specific code. This is not the PUK of the SIM card, but usually an 8-digit code which

needs to be requested from the provider.

The locks can only be set by the manufacturer and need to be agreed upon between the parties concerned, e.g.

provider, operator, distributor etc. on the one side and the manufacturer on the other side. For details contact

your local dealer or Cinterion Wireless Modules GmbH.

Parameter <class> is not applicable to SIM locks.

<password> and instructions for unlocking must be obtained from the network provider.

“PF“

lock Phone to the very First SIM card

“PN“

Network Personalisation

“PU“

Network subset Personalisation

“PP“

Service Provider Personalisation

“PC“

Corporate Personalisation

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 pack-

age.

When you attempt to set a <facility> or <class> which is not provisioned, not yet subscribed to, or not sup-

ported 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: oper-

ation not supported" etc.). To make sure check the extended error response with AT+CEER and the lock status

with <mode>=2.

<password>: Network password supplied from the provider or operator. Usually there is one password which

applies to all call barring options. For details contact your provider.

“AO“

BAOC (Bar All Outgoing Calls)

“OI“

BOIC (Bar Outgoing International Calls)

“OX“

BOIC-exHC (Bar Outgoing International Calls except to Home Country)

“AI“

BAIC (Bar All Incoming Calls)

“IR“

BIC-Roam (Bar Incoming Calls when Roaming outside the home country)

“AB“

All Barring services (applicable only for <mode>=0)

“AG“

All outGoing barring services (applicable only for <mode>=0)

“AC“

All inComing barring services (applicable only for <mode>=0)

<mode>^(num)

unlock

lock

query status

<status>^(num)

lock is inactive

lock is active

<password>^(str)

Password string used to lock and to unlock a <facility>. Length and authority for passwords depend on the

<facility> in question and are therefore listed in the section on parameter <facility>. Passwords can be

modified with AT+CPWD or AT^SPWD.

<class>^(num)

Integer or sum of integers each representing a class of information, i.e. a bearer service, telecommunication ser-

vice or bearer service group as defined in "GSM 02.04".

voice

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 acti-

vate Call Forwarding for all data classes, but deactivate it for data class 64,

"dedicated packet access".

fax

SMS

data circuit sync

data circuit async

dedicated packet access

128

dedicated PAD access

1...[7]...255

combination of some of the above classes.

For example, the default setting 7 represents the sum of the integers 1, 2 and

4 (voice, data and fax).

The value 255 covers all classes.

If parameter "class" is omitted, the default value 7 is used.

Notes

• The AT+CLCK command offers the full range of <class> parameters according to the GSM specifications.

However, when you attempt to use a service option which is not provisioned or not yet subscribed to, the set-

ting will not take effect regardless of the response returned.

The responses in these cases vary with the network (for example "OK", "Operation not allowed", "Operation

not supported" etc.). To make sure check the extended error response with AT+CEER and the lock status with

<mode>=2.

• The command has been implemented with the full set of <class> parameters according to GSM 07.07. For

actual applicability of a desired Call barring service to a specific service or service group (a specific <class>

value) please consult table A.1 of GSM 02.04.

• If an outgoing Fax or Data Call is rejected due to an active ''call barring'' supplementary service, the call will

be terminated with result code NO CARRIER.

Under the same conditions, an outgoing Voice call will be terminated with result code NO DIALTONE.

• If an invalid <password> is entered several times in succession, a delay incremented after each failed

attempt will increase the time to wait before the input of the <password> is accepted. To avoid blocking the

serial interface the running AT+CLCK command is aborted after a short timeout and returns "+CME ERROR:

unknown" (+CME ERROR: 100). If then the AT+CLCK command is issued once again execution is denied

with "+CME ERROR: operation temporary not allowed" (+CME ERROR: 256). For details regarding the delay

see Section 5.1.1, What to do if PIN or password authentication fails?.

• If the user tries to set a lock although it is already active or, the other way round, tries to unlock an inactive

lock, the response will be OK, but the <password> will not be checked or verified.

• In the airplane mode the write command version for the network related <facility> (AO, OI, OX, AI, IR,

AB, AG and AC) is not supported. For remaining facilities the command is fully functional then.

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.

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.

To query the status of the SIM card lock:

AT+CLCK="SC",2

Query the status of SIM card lock.

+CLCK: 1

SIM card is locked. SIM PIN1 must be entered to enable ME to register

to the GSM network.

EXAMPLE 2

Phone lock (<facility>="PS")

AT+CPIN?

Make sure that PIN1 authentication is valid.

To lock the ME to the currently inserted SIM card, first specify a password for <facility> "PS":

AT+CPWD="PS",,"1234"

If "PS" lock has not been set before: enter new password.

Optionally, if "PS" password was defined before, change existing password:

AT+CPWD="PS","1234","3333" To replace existing "PS" password: Enter old and new password.

Then, activate the Phone Lock:

AT+CLCK="PS",1,"3333"

Locks the mobile to the current SIM card.

To operate the mobile with the SIM card for which "PS" lock was activated:

AT+CPIN?

+CPIN: SIM PIN

AT+CPIN="9999"

No additional password is required for operation (SIM recognized by

mobile).

To operate the mobile with other SIM card than the one used for the "PS" lock:

Enter SIM PIN of present card, followed by "PS" lock password.

AT+CPIN?

+CPIN: SIM PIN

AT+CPIN="1111"

PIN authentication accepted.

AT+CPIN?

+CPIN: PH-SIM PIN

"PS" lock password is required.

AT+CPIN="3333"

"PS" Lock password has been accepted. ME is fully operational now.

To deactivate the Phone Lock:

AT+CLCK="PS",0,"3333"

Phone Lock password has to be provided again.

Now the mobile can be used with any SIM card, without the need of the

phone lock password.

5.5

AT^SLCK Facility lock

AT^SLCK provides the "Facility lock" function as defined for the GSM 07.07 command AT+CLCK. The command

can be used to lock, unlock or interrogate a network or ME <facility>.

AT^SLCK is, in every respect, identical with AT+CLCK, except that the command syntax and response prefix is

"^SLCK" instead of "+CLCK". For further details please refer to AT+CLCK.

The command can be aborted when network facilities are being set or interrogated.

Syntax

Test Command

AT^SLCK=?

Response(s)

^SLCK:list of supported <facility>s

Write Command

AT^SLCK=<facility>, <mode>[, <password>][, <class>]

Response(s)

if <mode> is not equal 2 and command successful:

if <mode>= 2 and command successful:

^SLCK: <status>, <class>

[^SLCK: <status>, <class>]

[^SLCK: ...]

If error is related to ME functionality

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

GSM 07.07, GSM 02.04, GSM

02.88,

GSM 03.88, GSM 04.88

Note

• In the airplane mode the write command version for the network related <facility> (AO, OI, OX, AI, IR,

AB, AG and AC) is not supported. For remaining facilities the command is fully functional then.

5.6

AT+CPWD Change Password

AT+CPWD allows to define a new password for a password protected <facility> lock function. Each password

is a string of digits, the length of which varies with the associated <facility>. The test command returns a list

of pairs which represent the available facilities and the maximum length of the associated password. See AT

commands AT+CLCK and AT^SLCK for more information on the various lock features.

Specifically the command can be used to

• change PIN1 or PIN2,

• change the password supplied from your provider for the "call barring" supplementary service,

• set individual phone security passwords,

• enter the unblocking key (Master Phone Code) to restore a disabled "PS" password.

To delete a password use the following syntax: at+cpwd=<facility>,<old password>

Syntax

Test Command

AT+CPWD=?

Response(s)

+CPWD:list of supported (<facility>, <password length>)

Write Command

AT+CPWD=<facility>, <old password>[, <new password>]

Response(s)

New password has been registered for the facility lock function.

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: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

GSM 07.07

Parameter Description

<facility>^(str)

Phone security locks set by client or factory:

Primarily intended for the client to take safety precautions, passwords "SC" (SIM PIN) and "P2" (SIM PIN2) are

usually predefined, but can be configured individually. The password for lock facility "PS" may also be factory

set.

“SC“

SIM PIN. SIM requests password upon ME power-up and when this lock com-

mand is issued.

If incorrectly entered three times, the SIM PUK is required to perform authen-

tication. Input of the SIM PUK password is possible only with AT command

AT+CPIN or ATD. For further details please refer to Section 5.1.1, What to do

if PIN or password authentication fails?.

<password length>: 4 to 8 digits.

“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". Accord-

ingly, the password may be called "phone code" or "device code". The "PS"

password is not associated with the PUK of the SIM card. It must be defined

before the first use of <facility> "PS" with AT+CLCK.

<password length>: 4 digits.

If incorrectly entered three times, the Master Phone Code is required to lift the

lock. This Unblocking procedure is performed with AT+CPWD using the follow-

ing 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 com-

mand AT+CPWD. If Pin authentication has not been completed, input of the

Master Phone code password is possible only with AT command AT+CPIN or

ATD. For further detail please refer to Section 5.1.1, What to do if PIN or pass-

word authentication fails?.

Once the Master Phone Code has been acctepted, the mobile is operational,

and the "PS" lock is no longer active. If needed it must be set once again with

AT+CLCK.

“P2“

SIM PIN 2, e.g. required for authentication with facility lock "FD" (cf. AT+CLCK).

If incorrectly entered three times, the SIM PUK 2 is required to perform authen-

tication. Input of the SIM PUK 2 password is possible only with AT command

AT+CPIN2 or ATD. For further detail please refer to Section 5.1.1, What to do

if PIN or password authentication fails?.

<password length>: 4 to 8 digits.

Factory defined SIM locks:

Typical examples of factory set SIM locks are prepaid phones or network locks, used to restrict the operation of

a mobile to a specific provider or operator. The client should be aware that each of these lock types can only be

unlocked if the associated password is available. For example, a mobile can be locked to accept only SIM cards

from the respective provider, or even one single SIM card. Once a different SIM card is inserted the ME will

prompt the client to enter a specific code. This is not the PUK of the SIM card, but usually an 8-digit code which

needs to be requested from the provider.

The locks can only be set by the manufacturer and need to be agreed upon between the parties concerned, e.g.

provider, operator, distributor etc. on the one side and the manufacturer on the other side. For details contact

your local dealer or Cinterion Wireless Modules GmbH.

“PF“

Lock Phone to the very First SIM card

“PN“

Network Personalisation

“PU“

Network subset Personalisation

“PP“

Service Provider Personalisation

“PC“

Corporate Personalisation

Supplementary Service Call Barring:

Supplementary Service "Call Barring" allows to specify conditions under which calls will be disallowed by the

network.

The availability of the Supplementary Services varies with the network. To benefit from call barring the client will

need to subscribe them, though a limited number of call barring types may be included in the basic tariff pack-

age.

<password length>: The Network Password needs to be supplied from the network provider or network oper-

ator. Usually there is one 4 digit password which applies to all call barring options. For details contact your pro-

vider.

“AO“

BAOC (Bar All Outgoing Calls)

“OI“

BOIC (Bar Outgoing International Calls)

“OX“

BOIC-exHC (Bar Outgoing International Calls except to Home Country)

“AI“

BAIC (Bar All Incoming Calls)

“IR“

BIC-Roam (Bar Incoming Calls when Roaming outside the home country)

“AB“

All Barring services

“AG“

All outGoing barring services

“AC“

All inComing barring services

<password length>^(num)

4...8

Length of password. The range of permitted length for a password depends on

the associated <facility>. It is available from the test command response,

or in the description of parameter <facility>.

<old password>^(str)

Password specified for the facility.

Parameter <old password> can be ignored if no old password was allocated to the facility.

Take into account that a password may have already been set by factory, or that the service is subject to a pass-

word 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).

Notes

• When changing PIN2 (<facility>="P2") it is recommended to check the new state of PIN2 by using the

AT+CPIN2 command.

• In the airplane mode the write command version for the network related <facility> (AO, OI, OX, AI, IR,

AB, AG and AC) is not supported. For remaining facilities the command is fully functional then.

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"

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.

EXAMPLE 3

Handling of the "PS" lock password

AT+CMEE=2

Enable text output of CME Error information

AT+CPWD="PS","1111","2222"

(where "1111" = old password and "2222" = new

password)

Password for facility "PS" is now "2222"

AT+CPWD="PS","1111","2222"

Repeat command to provoke error "incorrect pass-

word"

+CME ERROR: incorrect password

("1111" is no longer the correct password)

5.7

AT^SPWD Change Password

The AT^SPWD command comprises all functions of the AT+CPWD command. Apart from the different prefixes

"^SPWD" and "+CPWD", the major difference is that the <facility> list of AT^SPWD includes the additional

"CM" password dedicated to the Customer SIM Lock. Set with the command AT^SCSL, this type of lock allows

the application manufacturer to lock a mobile to specific operators.

The Customer SIM Lock feature is designed to be configurable during the production of the mobile application.

Therefore, to program the "CM" password, the AT^SPWD write command can be used no matter whether the SIM

is inserted or PIN authentication has been done. Opposite to that, passwords for all other facilities can only be

edited if the SIM is present and PIN authentication completed.

IMPORTANT: Please note that, even though there is no need for a factory set Customer SIM Lock, you are

strongly advised to specify at least a "CM" password, avoiding that end users ever have a chance to activate this

lock type.

Each password is a string of digits the length of which varies with the associated facility. The test command

returns a list of pairs which represent the available facilities and the maximum length of the associated password.

See also AT commands AT+CLCK and AT^SLCK as well as AT^SCSL for more detail on the various lock features.

Syntax

Test Command

AT^SPWD=?

Response(s)

^SPWD:list of supported ( <facility>, <password length>)

Write Command

AT^SPWD=<facility>[, <old password>][, <new password>]

Response(s)

New password has been registered for the facility lock function.

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: ...

In case of trying to set a "CM" password although another type of factory set SIM lock is already active:

+CME ERROR: operation not supported.

If error is related to ME functionality:

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Parameter Description

<facility>^(str)

“CM“

Password used as Customer Mastercode for Customer SIM Lock.

Defining the "CM" password allows the application manufacturer to set a Cus-

tomer SIM Lock by activating a Network Personalization ("PN") with the

AT^SCSL command. The "CM" password is mandatory for each operation with

AT^SCSL.

<password length> of "CM": 8 digits.

To delete the "CM" password use the following syntax: AT^SPWD=<facil-

ity>,<old password>. Please note that this action will delete all personali-

sation data programmed by the manufacturer with AT^SCSL (including the

operator list).

A description of all other passwords commonly supported by AT+CPWD and AT^SPWD can be found in Section

5.6, AT+CPWD. The "CM" password cannot be edited with AT+CPWD.

Notes

• When changing the PIN2 (<facility>="P2") it is recommended to check the new state of PIN2 using the

AT+CPIN2 command.

• In the airplane mode the write command version for the network related <facility> (AO, OI, OX, AI, IR,

AB, AG and AC) is not supported. For remaining facilities the command is fully functional then.

Examples

EXAMPLE 1

To specify the "CM" password required as Customer Mastercode for the Customer SIM Lock:

AT^SPWD="CM"

Check if the Customer Mastercode was already set.

ERROR

No, it was not.

AT^SPWD="CM", ,"12345678"

Specify a new Customer Mastercode (where <old

password> is omitted and

<new

pass-

word>"12345678" = new Customer Mastercode)

The Customer Mastercode has been set to

"12345678".

AT^SPWD="CM"

Checking again.

Yes, it is active now.

EXAMPLE 2

To change the Customer Mastercode:

AT^SPWD="CM","12345678","44444444"

(where "12345678" = old Customer Mastercode, and

"44444444" = new Customer Mastercode).

The Customer Mastercode has been changed from

"12345678" to "44444444".

EXAMPLE 3

To delete the Customer Mastercode:

AT^SPWD="CM","44444444"

Delete the Customer Mastercode by omitting <new

password> and entering only the <old pass-

word> "44444444".

The Customer Mastercode as well as all personali-

sation data programmed by the manufacturer with

AT^SCSL were deleted.

5.8

AT^SCSL Customer SIM Lock

The AT^SCSL command is designed to manage the Customer SIM Lock feature. This feature allows application

manufacturers to lock a mobile to specific operators by activating a Network Personalization ("PN"). If the lock is

enabled the mobile will accept only SIM cards from the given operators.

The Customer SIM Lock is protected by two different passwords:

•

<password> = Network Personalisation password "CM" defined with AT^SPWD and necessary for program-

ming the Customer SIM Lock with AT^SCSL.

•

<PUK> = Lock/Unlock Code defined with AT^SCSL and used to set the Customer SIM Lock with AT^SCSL.

Also used to deactivate a given lock or activate a new one via AT+CLCK or AT^SLCK. The PUK may be pro-

visioned to the end user.

The AT^SCSL write command serves to configure a Customer SIM Lock and to query the current settings.

Syntax

Test Command

AT^SCSL=?

Response(s)

Write Command

AT^SCSL=<facility>, <action>, <password>[, <PUK>, <data>]

Response(s)

ERROR

+CME ERROR: <err>

If <action>= 2 and command successful:

^SCSL: <data>[:<data>:<data>: ...]

If <action>= 2 and operator list is empty:

^SCSL:

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Parameter Description

<facility>^(str)

“PN“

Network Personalisation (= Customer SIM Lock)

<action>^(num)

Set or remove a Customer SIM Lock, or list the locks currently activated.

Remove the given Customer SIM Lock from ME.

Required parameters: <facility>="PN", <action>=0, <password>.

Removing the Customer SIM Lock deletes both the <PUK> and all <data>, i.e.

the entire list of operators.

Write Customer SIM Lock data to the ME and activate the lock.

Required parameters:

<facility>="PN",

<action>=1,

<password>,

<PUK>, <data>.

Retrieve the list of operators the ME is currently locked to.

Required parameters: <facility>="PN", <action>=2, <password>.

<password>^(str)

Password for programming the Customer SIM Lock.

8-digit "CM" password for the facility "PN" that needs to be created with AT^SPWD (see note below for further

details). This password is mandatory for each operation performed with AT^SCSL.

<PUK>^(str)

PUK created and required when entering the Customer SIM Lock data with AT^SCSL, i.e. if <action>=1. Also

used to deactivate a given "PN" lock or to activate a new "PN" lock for another SIM card via AT+CLCK or

AT^SLCK.

The length of the <PUK> is also 8 digits.

Each time the AT^SCSL write command is issued with parameter <action>=1 you are free to use the same

<PUK> or to set a new one. In any case, a new <PUK> overwrites the previous one.

<data>^(str)

Data of the allowed network operators.

Each operator code consists of the "Mobile Country Code" MCC and the "Mobile Network Code" MNC, both sep-

arated by a dot, e.g. MCC1.MNC1. If more than one operator is entered on the same line, then a colon must be

set between each operator code, e.g. MCC1.MNC1:MCC2.MNC2:MCC3.MNC3. For example, for the three

operators T-Mobile D, Vodafone D2 and E-Plus you would enter the following data: 262.01:262.02:262.03

Note that each time the AT^SCSL write command is executed using the parameter <action>=1 the existing

operator codes will not be overwritten, but all new data will be added to the list. This applies no matter whether

the same operator code is already listed, i.e. entering the same operator again causes double entries.

The maximum number of entries in the operator list is 50.

Notes

•

The use of the Customer SIM lock features may be restricted by existing facility locks. For example it is not

possible to enable Customer SIM lock while the "PS" device lock is in place.

•

All parameters of AT^SCSL as well as the "CM" password of AT^SPWD can be used no matter whether or not

the SIM card is inserted or PIN authentication has been done. This allows the application manufacturer to set

the "CM" password and activate the Customer SIM Lock during the production process.

•

The Customer SIM Lock takes effect after the AT^SCSL write command was successfully executed with

parameter <action>=1. Then, after the reboot, the mobile will accept only SIM cards from the supported

operators.

•

To remove the Customer SIM Lock use the write command AT^SCSL with <action>=0 and <password>:

AT^SCSL="PN",0,password. This will delete both the <PUK> and the list of operators. The mobile will accept

any SIM card.

•

Another way to operate the mobile with other SIM cards is to deactivate the Customer SIM Lock using the

command AT+CLCK="PN",0,PUK. This will delete the list of operators specified with the Customer SIM Lock,

but the <PUK> created for the Customer SIM Lock remains valid. The mobile will accept any SIM card.

•

If the Customer SIM Lock is deactivated and, therefore, operable with any SIM card, the end user may use

the <PUK> to set a new SIM lock. To do so, it is necessary to enter the command AT+CLCK="PN",1,PUK first,

then insert a different SIM card and finally restart the mobile. When restarted, the mobile will read out and

accept the list of operators of the currently inserted SIM card. As a result, a new Customer SIM Lock takes

effect for the operator(s) listed on this SIM card.

•

If the Customer SIM Lock is active, but the end user inserts an unsupported SIM card and enters PIN1 the

mobile returns OK, although access to SIM related commands (such as dialing out, access to phonebooks,

SMS etc.) will be denied. If then the read command AT+CPIN is executed the mobile will request the PH-NET

PUK. In this case, you have two options: Use the AT+CPIN command to enter the correct <PUK> of the Cus-

tomer SIM Lock. After this, the mobile can be operated with the new SIM card. As an alternative, re-insert the

correct SIM card associated with the Customer SIM Lock and deactivate the lock via AT+CLCK="PN",0,PUK.

•

If an invalid <password> or <PUK> is entered several times in succession, a delay incremented after each

failed attempt will increase the time to wait before the next input is accepted. The delay follows the same tim-

ing algorithm specified for the PH-SIM PUK (Master Phone Code). For details regarding the delay see Section

5.1.1, What to do if PIN or password authentication fails?.

Examples

EXAMPLE 1

Prerequisite for using the AT^SCSL command is a valid "CM" password created with AT^SPWD. Therefore,

first check the "CM" password. A more detailed example can be found in Section 5.7, AT^SPWD.

AT^SPWD="CM",,

Check that the "CM" password was already set.

Yes, the "CM" password is valid.

EXAMPLE 2

To check, configure and remove a "PN" lock (= Customer SIM Lock):

AT^SCSL="PN",2,44444444

Check the current status of the Customer SIM Lock.

^SCSL:

44444444 is the "CM" password created with

AT^SPWD.

Operator list is still empty, Customer SIM Lock has

not yet been set.

AT^SCSL="PN",1,44444444,12345678,262.01:2

Set a "PN" Lock, where 44444444 = "CM" password,

62.02

12345678 = PH-NET PUK, 262.01 = MCC/MNC of

German operator T-Mobile D and 262.02 = MCC/

MNC of Vodafone D2.

AT^SCSL="PN",2,44444444

Check again.

^SCSL: 262.01:262.02

The mobile is locked to the two network operators T-

Mobile D and Vodafone D2.

AT^SCSL="PN",1,44444444,12345678,262.03

Add another operator (262.03 = MCC/MNC of Ger-

man network operator E-Plus).

AT^SCSL="PN",1,44444444,11223344,262.04

Add another operator. In this case, a new PH-NET-

PUK was used. Keep in mind that the new password

overwrites the old one.

AT^SCSL="PN",0,44444444

Remove the Customer SIM Lock. Keep in mind that

this action deletes the entire list of network operators

contained in <data>. As a result, the mobile will

accept any SIM card.

EXAMPLE 3

If the Customer SIM Lock is active, but the user inserts a different SIM card not supported by the list of oper-

ators defined in <data> the <PUK> must be at hand:

AT^SCSL="PN",2,44444444

For the purpose of this example, we check the cur-

^SCSL: 262.01:262.02

rent status of the Customer SIM Lock.

The mobile lis locked to the German operators T-

Molile D and Vodafone D2.

AT+CPIN=1111

PIN1 is accepted and the mobile is operable, except

for SIM related AT commands.

AT+CMGF=1

AT command that does not require SIM authentica-

tion.

AT+CPBS?

Attempt to use a phonebook command.

+CME ERROR: network personalisation PUK

Access to phonebook fails because of lack of SIM

required

data.

AT+CPIN?

Check status of PIN authentication.

+CPIN: PH-NET PUK

The mobile is waiting for the PH-NET-PUK.

Identification Commands

The AT Commands described in this chapter allow the external application to obtain various identification infor-

mation related to the TC65i and linked entities.

6.1

ATI Display product identification information

The ATI execute command delivers a product information text.

The 'Revision' information consists of the following parts: Version xx and variant yy of software release.

Syntax

Exec Command

ATI

Response(s)

Cinterion

TC65i

REVISION xx.yy

Exec Command

ATI[<value>]

Response(s)

Exec Command

ATI1

Response(s)

Cinterion

TC65i

REVISION xx.yy

A-REVISION xx[.zzz.cc]

PIN ASC0 ASC1

USB MUX1

MUX2

MUX3

Charge

Last

Reference(s)

V.250

Parameter Description

<value>^(num)

Values are not supported and only return OK.

Notes

• "A-REVISION xx.zzz.cc" information consists of the following parts:

Application Revision Number 'xx' as an assignment to customer application.

Application Revision Version 'zzz' as an assignment to changes in customer application.

'cc' as an additional number, e.g. defined by customer.

• "A-REVISION 01" is returned as an assignment to no customer application.

6.6

AT+CGMR Request revision identification of software status

AT+CGMR delivers a product firmware version identification. Command is identical with AT+GMR.

Syntax

Test Command

AT+CGMR=?

Response(s)

Exec Command

AT+CGMR

Response(s)

REVISION <xx.yy>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

GSM 07.07

Parameter Description

<xx.yy>^(str)

Version xx and variant yy of software release.

6.7

AT+GMR Request revision identification of software status

AT+GMR delivers a product firmware version identification. Command is identical with AT+CGMR.

Syntax

Test Command

AT+GMR=?

Response(s)

Exec Command

AT+GMR

Response(s)

REVISION <xx.yy>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

V.250

Parameter Description

<xx.yy>^(text)

Version xx and variant yy of software release.

6.8

AT+CGSN Request International Mobile Equipment Identity

(IMEI)

AT+CGSN delivers the International Mobile Equipment Identity (IMEI). Command is identical with: AT+GSN.

Syntax

Test Command

AT+CGSN=?

Response(s)

Exec Command

AT+CGSN

Response(s)

<sn>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

GSM 07.07

Parameter Description

<sn>^(str)

International Mobile Equipment Identity (IMEI) used to identify a GSM mobile equipment to the GSM network

6.9

AT+GSN Request International Mobile Equipment Identity (IMEI)

AT+GSN delivers the International Mobile Equipment Identity (IMEI). Command is identical with AT+CGSN

Syntax

Test Command

AT+GSN=?

Response(s)

Exec Command

AT+GSN

Response(s)

<sn>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

V.250

Parameter Description

<sn>^(str)

International Mobile Equipment Identity (IMEI) used to identify a GSM mobile equipment to the GSM network.

Call related Commands

The AT Commands described in this chapter are related to Mobile Originated (MOC, i.e. outgoing) Calls and

Mobile Terminated (MTC, i.e. incoming) Calls.

7.1

Call Status Information

For Circuit switched calls, including voice, fax and data calls, call status information is available with URC

"+CIEV: call" (configurable via AT commands AT+CIND and AT+CMER) or - in more detail - from the list of current

calls. This list can be displayed on request via at commands AT+CLCC and AT^SLCC. It can also be issued by

the ME in the form of an unsolicited result code "^SLCC" if configured with AT^SLCC and AT+CMER.

URC "+CIEV: call" and URC "^SLCC" can be configured using AT command AT^SCFG. An overview of the pos-

sible configurations and their consequences for the availability of call status information will be given here.

Generally speaking, the call status values recognized by the ME are as follows:

• active

• held

• dialing (MOC)

• alerting (MOC)

• incoming (MTC)

• waiting (MTC)

• terminating: The call is not active anymore, but inband information is still available.

• dropped: The call has been suspended by the network, but may be resumed later.

The values "terminating" and "dropped" are not standardized for AT command AT+CLCC, and therefore only

available for command AT^SLCC. A call in any of these two states will not appear in the list of current calls as

displayed with AT+CLCC.

A call that is not recognized by the ME is considered to be in "unknown" state.

Some networks may schedule a traffic channel for a call that is not yet in the "active" state. This is reflected in

parameter <traffic channel assigned> of AT command AT^SLCC and the corresponding URC.

Depending on the value of AT^SCFG setting <succ>, Indicator "+CIEV" will be issued (if configured with

AT+CIND and AT+CMER)

• when a state transition ends in state "active" or in state "unknown"

(if AT^SCFG setting <succ>=''restricted'').

• when any state transition (including transitions beginning or ending in state "unknown") occurs in the list of

active calls, or when a traffic channel is established

(if AT^SCFG setting <succ>=''verbose'').

The indicator value for indicator "+CIEV: call" will be "1" if at least one call is in states "held" or "active", and "0"

otherwise.

Depending on the value of AT^SCFG setting <sucs>, Indicator "^SLCC" will be issued (if configured with write

command AT^SLCC and AT+CMER)

• when a state transition ends in state "active" or in state "unknown" (if AT^SCFG setting <sucs>="restricted")

• when any state transition (including transitions beginning or ending in state "unknown") occurs in the list of

active calls, or when a voice channel is established (if AT^SCFG setting <sucs>="verbose").

Due to compatibility considerations, the powerup default for AT^SCFG setting <succ> is "restricted", offering

compatibility to the standard behaviour of indicator "+CIEV: call", while the default for setting <sucs> is "ver-

bose".

In order to see the URCs, event reporting for both indicators must be explicitly configured with the appropriate

AT commands.

7.2

ATA Answer a call

Syntax

Exec Command

ATA

Response(s)

In case of data call, if successfully connected (TA switches to data mode):

CONNECT <text>

In case of voice call, if successfully connected:

When TA returns to command mode after call release:

If no connection:

NO CARRIER

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

V.250

Command Description

TA causes remote station to go off-hook (e.g. answer call).

Parameter Description

<text>^(str)

Connection status

output only if ATX parameter setting with value greater 0. Connection speed values:

“300“

“1200“

“2400“

“4800“

“9600“

“14400“

Notes

• Any additional commands on the same command line are ignored.

• The command may be aborted generally by receiving a character during execution. It can't be aborted in

some connection setup states, such as handshaking.

• If AT+FCLASS setting is 1 or 2, all incoming calls will be answered as fax calls, when ATA is issued on multi-

plexer channel 1 resp. ASC0. For calls explicitly signalled as voice or data calls, this procedure will fail with

result code "NO CARRIER", but the call in question will continue to ring.

It is possible to change the setting for AT+FCLASS to 0 while the call is ringing, and accept the call normally

afterwards with ATA.

• The ATA command may be used also to accept a network request for a PDP context activation (see ATA).

• See also ATX for <text>.

• If an incoming call is no longer available (already disconnected/hanged up)a "NO CARRIER" result code will

be given.

7.3

ATD Mobile originated call to specified number

Syntax

Exec Command

ATD<n>[<mgsm>][;]

Response(s)

If no dialtone (parameter setting ATX2 or ATX4):

NO DIALTONE

If busy (parameter setting ATX3 or ATX4):

BUSY

If a connection cannot be set up:

NO CARRIER

NO DIALTONE

If successfully connected and non-voice call (TA switches to online data mode):

CONNECT <text>

When TA returns to command mode after call release:

If successfully connected and voice call:

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

V.250

Command Description

This command can be used to set up outgoing voice, data or fax calls. It also serves to control Supplementary

Services. The termination character ";" is mandatory to set up voice calls or to send *# codes for Supplementary

Services. It must not be used for data and fax calls.

Additional notes on the responses returned after dialing with ATD:

• For voice calls, you have the choice of two different response modes that can be selected with AT^SM20:

AT^SM20=1 (factory default) causes the ME to respond once the call setup is completed either successfully

("OK") or unsuccessfully ("NO CARRIER", "NO DIAL TONE", "BUSY").

AT^SM20=0 causes the ME to return "OK" immediately after dialing was completed (i.e. before call setup ter-

minates 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 auto-

matically put on hold. The second call attempt is acknowledged with "OK" immediately after dialing with ATD

has completed, without relation to a successful call setup. In case of failure, the additional result codes "NO

CARRIER", "NO DIAL TONE", "NO CARRIER" will be presented afterwards (see example below).

Parameter Description

<n>^(text)

String of dialing digits and optional V.250 modifiers: 0-9, *, #, +, A, B, C

The following V.250 modifiers are ignored: ,(comma), T, P, !, W ,@

<mgsm>^(str)

String of GSM modifiers:

Activates CLIR (disables presentation of own phone number to called party)

Deactivates CLIR (enables presentation of own phone number to called party)

Activate Closed User Group explicit invocation for this call only.

g Deactivate Closed User Group explicit invocation for this call only.

Notes

•

The command may be aborted generally when receiving a character during execution. It cannot be aborted

in some connection setup states, such as handshaking.

•

Parameter "I" and "i" only if no *#-code is within the dial string.

•

<mgsm> is not supported for data calls.

•

<n> is default for last number that can be dialled by ATDL.

•

TC65i AT-Commands Set. Manual - part 2