
TC63 AT Command Set
5.8 AT^SCSL
s
TC63_ATC_V00.490
Page 131 of 501
5/24/05
Confidential / Draft - Do not copy
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 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 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
• 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?
.
<password>
(str)
<PUK>
(str)
<data>
(str)