Proprietary AT Commands

Reference Guide
Revisions

Version Date Description

0.0.1 11-06-2007 Initial Version
1.0.0 12-07-2007 Baselined – no review done since
sections taken from earlier AT
command manual as is
1.0.1 19-12-2007 ME Personalization AT Commands
added
1.1.0 20-12-2007 Updated document baselined
1.2.0 25-01-2008 Added new AT command +SKAOCINV
and modified +SKCCCME
1.3.0 15-02-2008 Updation of +SKAOCINV
1.4.0 11-07-2008 Addition of Proprietary errors
1.5.0 18-07-2008 Addition of new AT commands
+SKDSIMREG and +SKSIMSLT
1.5.1 02-08-2008 Addition of new AT command
+SKSIMMTR
1.6.0 04-08-2008 Document baselined
1.7.0 28-01-2009 Changes made to ME Personalization
AT Commands
1.8.0 16-04-2009 Added changes in +SKENR and other
ME personalization related AT
commands
1.9.0 8-09-2009 Added channel_id for SKCNLI.
2.0.0 20-10-2010 Addition of new AT command
+SKCONDLY.
2.1.0 19-04-2011 Addition of new AT command
+SKEXTREG.
2.1.1 27-04-2011 Added new AT command +SKPINSTAT

2.2.0 04-05-2011 Updated Proprietary Error table

2.2.1 15-07-2011 Updated SKVTS and SKVTD command

2.2.2 07-11-2011 Correction in 4.2 +SKCPBSC

Phonebook update notification
Examples

3.0.0 08-10-2012 Updated SAF specific, GMR+

proprietary AT commands
Trademarks
The Sasken logo is a trademark of Sasken Communication Technologies Limited

World Headquarters

Sasken Communication Technologies Limited

139/25 , Ring Road , Domlur,Bangalore -560071, India
TEL : 9180 25355501
FAX : 9180 25351133
URL : www.sasken.com

Copyright
This publication may not be reproduced, in whole or in part, without prior expressed written
permission from Sasken Communication Technologies Limited. All rights reserved. Copyright ©
2004, by Sasken Communication Technologies Limited. Sasken Communication Technologies
Limited makes no representations or warranties with respect to the contents hereof and
specifically disclaims any implied warranties of merchantability or fitness for any particular
purpose. Furthermore, Sasken Communication Technologies Limited reserves the right to revise
this publication and to make changes from time to time in the content hereof without
obligation of Sasken Communication Technologies Limited to notify any person or organization
of such revisions or changes.

Table of Contents
1 Introduction 8
1.1 Scope........................................................................................................................8
1.2 References..............................................................................................................8
2 Definitions and abbreviations 9
2.1 Definitions...............................................................................................................9
2.2 Abbreviation...........................................................................................................9
3 Call Management 10
3.1 +SKCPWD Proprietary Change Password..........................................................10
3.2 +SKCOLR Connected Line Identification Restriction......................................11
3.3 +SKCSSN Supplementary Service Notifications...............................................11
3.4 +SKSAUTR Set Auto Redial Mode.......................................................................13
3.5 +SKRBLC Redial Black List Control....................................................................16
3.6 +SKCTVE, Individual Call Time Value................................................................17
3.7 +SKCTV Call Timer Value....................................................................................18
3.8 +SKCCS Current Call State Indication...............................................................19
3.9 +SKCPI More Call Progress Information............................................................23
3.10 +SKCONDLY, Set CONNECT delay......................................................................25
3.11 +SKVTS DTMF and Tone Generation.................................................................26
3.12 +SKVTD Tone duration........................................................................................27
4 Mobile Termination Control and Status Commands 28
4.1 +SKMS Current Modem and SIM Status..............................................................28
4.2 +SKCPBSC Phonebook update notification.......................................................30
4.3 +SKCPBS Phonebook storage ready notification.............................................31
4.4 +SKCPIN PIN Remaining Attempts......................................................................32
4.5 +SKECAOC, Extended query CCM using PUCT.................................................33
4.6 +SKECACM, Extended query ACM using PUCT.................................................34
4.7 +SKCCCME, Individual Call Meter and Charges................................................35
4.8 +SKAOCINV, Individual Call AoC Invocation Indications.................................36
4.9 +SKPINSTAT...........................................................................................................37
5 Network Management and Modem Information 38
5.1 +SKCNL Network Location Information............................................................38
5.2 +SKECOPS Asynchronous Version of COPS AT command...............................40
5.3 +SKSBP Set Band Priority....................................................................................42
5.4 +SKCATT CS Attach or Detach............................................................................43
5.5 +SKCCATT CS and PS Attach or Detach............................................................44
5.6 +SKEXTREG Extended Network Registration Status.......................................45
6 Short Messaging Service (SMS) support 46
6.1 +SKCPMS Extended Preferred Message Storage..............................................46
6.2 +SKSMMA More Memory Available.....................................................................47
6.3 +SKSMMF Memory Full........................................................................................49
6.4 +SKCMGU Update SMS message..........................................................................50
6.5 +SKCMGB Get occupied SMS storage Bitmap....................................................51
6.6 +SKCMGR Read SMS message without changing status...................................51
6.7 +SKCSM SMS State indications............................................................................53
6.8 +SKCMGT Change SMS Message Status..............................................................54
7 SIM Application Tool(SAT) in APDU format 55
7.1 +SKSATPD Profile Download Command............................................................56
7.2 +SKSATC Configuration of SIM Application Tool Kit........................................60
7.3 +SKSATE Send Envelope Command...................................................................62
7.4 +SKSATR Send Terminal Response....................................................................63
7.5 +SKSATA SAT call accept....................................................................................65
7.6 +SKSATH SAT call reject.....................................................................................66
8 ME Personalization 67
8.1 +SKMEPERS Activate/Deactivate Personalization...........................................67
8.2 +SKPERSSTAT Query Personalization Status....................................................69
8.3 +SKPERSDIS Disable Personalization.................................................................70
8.4 +SKPERSUBLK Unblock Personalization............................................................71
8.5 +SKPERSVER Personalization Verification Status............................................72
8.6 +SKPERSCPWD Personalization Password Change..........................................73
9 Dual-SIM Related AT Commands 74
9.1 +SKSIMSLT Select SIM for Channel.....................................................................74
 9.2 +SKDSIMREG Dual-SIM Network Registration Status.......................................75
9.3 +SKSIMMTR Set Master SIM..................................................................................77
10 Miscellaneous AT Commands 78
10.1 +SKABORT Abortion of the AT Commands.......................................................78
10.2 +SKICCID Read ICCID from SIM...........................................................................79
10.3 +SKENR Enable for Engineering Mode Information.........................................80
10.4 +SKRSTENR Reset for Engineering Mode Information....................................89
10.5 +SKERRLOG Read Error Log from NVM..............................................................90
11 Setting of Preferred message storage 91
11.1 Listing of ME stored messages............................................................................91
11.2 Reading a Specific ME stored message.............................................................91
11.3 Deleting a Specific ME stored message.............................................................91
12 SMS related AT commands 92
12.1 SKCMGS – Send message (PDU mode, asynchronous).........................................92
13 Sasken Proprietary Errors 93
14 SAF Specific AT Commands 94
14.1 +CGMI (or +GMI)....................................................................................................94
14.2 +CGMM (or +GMM)................................................................................................95
14.3 +CGMR (or +GMR).................................................................................................95
14.4 +_IGPS....................................................................................................................96
14.5 +SKCKPD................................................................................................................98
14.6 +SKENKPD..............................................................................................................99
14.7 +SKVOLLVL............................................................................................................99
14.8 +SKLSAVAIL.........................................................................................................100
14.9 +SKEXTDEVICE....................................................................................................100
14.10 +SKMODEL...........................................................................................................101
14.11 +SKCTIME.............................................................................................................103
14.12 +SKAUDDEV.........................................................................................................104
14.13 +SKALRMIND........................................................................................................105
14.14 +SKBATIND...........................................................................................................106
14.15 +SKPALERT..........................................................................................................107
14.16 +SKRGPSPOS........................................................................................................108
15 Control of SAT/GSM modes 109
15.1 +SKSTKMD............................................................................................................109
15.2 +SKGPSPLCY........................................................................................................110
15.3 +SKGPSPOS..........................................................................................................111
15.4 +SKRBSRCH..........................................................................................................112
15.6 +SKCPWC.............................................................................................................113
15.7 +SKGPSINFO?.......................................................................................................114
16 Audio AT commands 116
16.1 +AUDCOMP..........................................................................................................116
16.2 +AUDLPBK............................................................................................................117
16.3 +AUDLOG.............................................................................................................118
16.5 +AUDPARST.........................................................................................................120
16.6 +AUDPAREQ.........................................................................................................121
16.7 +AUDPARCMP......................................................................................................123
16.8 +AUDREG.............................................................................................................125
16.9 +AUDVAMCFG......................................................................................................126
16.11 +AUDLDSIM..........................................................................................................128
16.12 +AUDERR..............................................................................................................129
17 Traceability 129
 1 Introduction

1.1 Scope

This document is a proprietary of 3GPP 27.007 standards. It specifies the profile of SASKEN
proprietary AT commands and usage of the same.

SAF Specific AT commands defined exclusively for the Satellite mode of operation and also
the switch between GSM mode and the Satellite mode working of the handset.

The commands always begin with AT (which means Attention) and end with the character <CR>
(Carriage Return).

These commands are parsed handled and acted upon internally by SAF.

1.2 References

Standard Version Release Comments

3GPP TS 11.14 8.5.0 Rel99 Specification of the SIM Application
Toolkit for the subscriber Identity
Module
3GPP TS 11.11 8.6.0 Rel99 Specification of the subscriber identity
module
3GPP TS 22.022 3.2.1 Rel99 Personalization of Mobile Equipment
3GPP TS 27.007 AT command set for User Equipment
(UE)
 2 Definitions and abbreviations
2.1 Definitions
Refer section 1.3 in 3GPP 27.007
2.2 Abbreviation

Abbreviation / Term Expansion / Defined

ATPP AT Pre-processor
SAT SIM Application Toolkit

SAF Sasken Application Framework

MNC Mobile Network Code
ME Mobile Equipment
SM SIM
MCC Mobile Country Code
 3 Call Management
3.1 +SKCPWD Proprietary Change Password
+SKCPWD Proprietary Change Password

This action command sets a new password for the facility lock function defined by
command Facility Lock +CLCK. The difference between this command and CPWD is
that the new password has to be reentered. The test command returns a list of pairs
which present the available facilities and the maximum length of their password

Syntax Description

AT+SKCPWD=<fac>,<oldpwd>,<newpw +CME ERROR: <err>

d>,<reenter newpwd>
AT+SKCPWD=? +SKCPWD: list of supported ( <fac>,
<pwdlength>)s
+CME ERROR: <err>

Parameters

<fac>
"P2" SIM PIN2
Refer +CLCK AT
command for
rest of the <fac>
values
<oldpwd> String type; shall be the same as password
specified for the facility from the MT user
interface or with command Change
Password +CPWD
<newpwd>,<reent String type; is the new password; maximum
er newpwd> length of password can be determined with
<pwdlength>
<pwdlength> Integer type maximum length of the
password for the facility
Limitations
This command is supported for the following <facs>:
“AB”, “AG”,”AI”, “IR”, “OI”,”OX”,“PC”,”PN”,”PP”, ”SP”,
”PU”, ”SC” and ”P2”

Examples

Commands Possible Responses Description

AT+SKCPWD=? +CPWD: (“AB”,4), TA responding with the supportable

(“PC”,16),(“PN”,16), values for test command
(“PP”,16),(“PU”,16),
(“SC”,8),(“P2”,8) ,
(“SP”,16)
OK
AT+SKCPWD=”AB”, OK Password has been changed
”0000”,”1234”,”1 successfully.
234”
AT+SKCPWD=”AB”, +CME ERROR: invalid
”1234”,”99” characters in text err
string
AT+SKCPWD=”AB”, +CME ERROR: incorrect TA responds with error response
”8888”,”1234”,”3 password when new password and re-entered
456” new password are not the same.

3.2 +SKCOLR Connected Line Identification Restriction

+ SKCOLR Connected Line Identification Restriction

This command is used to obtain the status of the Connected Line Identification
Restriction as subscribed with the network.

Syntax Description

AT+SKCOLR +SKCOLR: <n>

AT+SKCOLR=?

Parameters

<n>
0 COLR is not provisioned
1 COLR is provisioned
Limitations
None

Examples

Commands Possible Responses Description

AT+SKCOLR +SKCOLR: 0 COLR not provisioned

OK

3.3 +SKCSSN Supplementary Service Notifications

+SKCSSN Extended version SS notification
This command refers to supplementary service related network initiated
notifications. The set command enables/disables the presentation of notification
result codes from TA to TE. When <n>=1 and a supplementary service notification is
received after a mobile originated call setup, intermediate result code +SKCSSI :
<call_id>,<code1>[, <index>] is sent to TE before any other MO call setup result
codes presented in the present document or in V.25ter. When several different
<code1>s are received from the network, each of them shall have its own +SKCSSI
result code. When <m>=1 and a supplementary service notification is received
during a mobile terminated call setup or during a call, or when a forward check
supplementary service notification is receive, unsolicited result code +SKCSSU:
<call_id>,<code2>[,<index>[<number>, <type> [,<subaddr> ,<satype>]]] is sent to
TE. In case of MT call setup, result code is sent after every +CLIP result code and
when several different <code2>s are received from the network, each of them shall
have its own +CSSU result code.
The read command returns the current status of <n> and <m>.
The test command returns values supported by the TA as compound value.

Syntax Description

+SKCSSN=[<n>[,<m>]] OK
+CME ERROR: <err>
+SKCSSN? +SKCSSN: <n>,<m>
+SKCSSN=? +SKCSSN: (list of supported <n>s),
(list of supported <m>s)

Parameters

<n> Parameter sets/shows the +SKCSSI result code presentation

status in the TA
0 disable
1 enable
<m> Parameter sets/shows the +SKCSSU result code presentation
status in the TA
0 disable
1 enable
<call_id> Call id. Same index as in +CLCC, +SKCLCC, +SKCCSI, +SKCPI,
etc…
<code-1> Notifications for mobile originated call setup
0 unconditional call forwarding is active
1 some of the conditional call forwardings are active
2 call has been forwarded
3 call is waiting
4 this is a CUG call
5 outgoing calls are barred
6 incoming calls are barred
7 CLIR suppression rejected call has been deflected
8 call has been deflected

<index> refer "Closed user group +CCUG"

<code-2> 0 this is a forwarded call (MT call setup)
1 this is a CUG call
2 call has been put on hold (during a voice call)
3 call has been retrieved (during a voice call)
4 multiparty call entered (during a voice call)
5 call on hold has been released (during a voice call)
6 forward check SS message received
7 call is being connected with the remote party in
alerting state in explicit call transfer operation (during a voice
call)
8 call has been connected with the other remote party in
explicit call transfer operation
this is a deflected call (MT call setup)
additional incoming call forwarded

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

<type> type of address octet in integer format
<subaddr> string type sub address of format specified by <satype>
<satype> type of subaddress octet in integer format

Examples

Commands Possible Responses Description

AT+SKCSSN=? +SKCSSN: (0,1), (0,1) Query the supported +SKCSSN value
OK
AT+SKCSSN? +SKCSSN: 0,0 Query current +SKCSSN parameters
OK
AT+SKCSSN=1,1 OK Set the +SKCSSN parameters to n=1
and m=1

ATD0223708999; OK Make a MO voice call (call # 1)

+SKCSSI: 1,2 Indicate this call has been
forwarded
Call has been established

3.4 +SKSAUTR Set Auto Redial Mode

+SKSAUTR Set Auto Redial Mode
The set command enables/disables the automatic redial mode, as well as the
presentation of unsolicited result codes that show various automatic redialing
events: +SKRDLI: <call_id>,<event>,<number>, <type> [, <redial-time-duration>]
The redial feature supports multiple calls that are at the same time in the redialing
phase. Details can be found in TS 22.001.
The read command shows the current settings.
The test command returns the lists of supported values.

Syntax Description

+SKSAUTR=<mode> +CME ERROR: <err>

+SKSAUTR? +SKSAUTR: <mode>

+SKSAUTR =? +SKSAUTR: (list of supported mode)

Parameters

<mode> 0 Disable Auto Redial

1 Enable Auto Redial

<event> 1 call failed, redialing timer is
started with duration <timer or
cause>
2 redial timer expired for the given
call, call is being
3 Number has been put in blacklist
<call Id> Call id of the redialing call
<number> String parameter; called party
number of the call to which this
event pertains
<type> Numeric parameter; type of
 number of <number>
<redial-attempt- Numeric parameter is used in case
time> of <event> == 1 to give the timer
duration (in number of seconds);
MMI could use this parameter to
e.g. show a count-down timer

Examples

Commands Possible Responses Description

AT+SKSAUTR=1 OK Enable automatic redial

AT+SKCCS=1 OK
ATD1234; OK
+SKCCSI: 1, 0, 2, 0, 0, , Outgoing call URC
”1234”, 129

+SKCCSI: 1, 0, 7, 0, 0, 1, In case of redial it will give instead

”1234”, 129 of 7(call failed and redial will be
initiated).

+SKRDLI: 1, 1, “1234”, Redialing is indicated with a timer

129, 5 of 5 seconds
+SKRDLI: 1, 2, “1234”, Event indicating expiration of
129 redial timer
+SKCCSI: 1, 0, 2, 0, 0, , URC to indicate outgoing call
”1234”, 129

+SKCCSI: 1, 0, 6, 0, 0, 1, Call failed and no redial will be

”1234”, “” initiated
NO CARRIER
This number has been put in black
+SKRDLI: 1, 3, “1234”, list
129
ATD1234; OK Trying to make a call to the no
which is present in blacklist.
+SKCCSI: 0, 0, 6, 0, 0,227 Call Failed with cause 227.
, ”1234”, 129

ATD2234; OK
+SKCCSI: 1, 0, 2, 0, 0, , Outgoing call URC
”2234”, 129

+SKCCSI: 1, 0, 7, 0, 0, In case of redial it will give instead

17, ”2234”, 129 of 7(call failed and redial will be
initiated).

+SKRDLI: 1, 1, “2234”, Redialing is indicated with a timer

129, 5 of 5 seconds

+SKRDLI: 1, 2, “2234”, Event indicating expiration of

129 redial timer

+SKCCSI: 1, 0, 2, 0, 0, , URC to indicate outgoing call

”2234”, 129
 +SKCCSI: 1, 0, 7, 0, 0, In case of redial it will give instead
17, ”2234”, 129 of 7(call failed and redial will be
initiated).

+SKRDLI: 1, 1, “2234”, Redialing is indicated with a timer

129, 60 of 60 seconds

ATD9876; OK
+SKCCSI: 0, 0, 6, 0, 0, Second call is cleared
230, ”9876”, “”
NO CARRIER

+SKRDLI: 1, 2, “2234”, Event indicating expiration of

129 redial timer
+SKCCSI: 1, 0, 2, 0, 0, , Re-dialing call is initiated
”2234”, 129

ATH +SKCCSI: 1, 0, 6, 0,c Call cleared by the user

0, 16, ”2234”, “”
OK
ATD1244; OK
+SKCCSI: 1, 0, 2, 0, 0, , Outgoing call URC
”1244”, 129

+SKCCSI: 1, 0, 7, 0, 0, In case of redial it will give instead

17, ”1244”, 129 of 7(call failed and redial will be
initiated).

+SKRDLI: 1, 1, “1244”, Redialing is indicated with a timer

129, 5 of 5 seconds

+SKCCSI: 1, 0, 6, 0, 0, Re-dialing is cleared

229, ”1244”, “”
NO CARRIER

Incoming call
+SKCCSI: 1, 0, 4, 0, 0, ,
”4444”, 129
RING
3.5 +SKRBLC Redial Black List Control
+SKRBLC Redial Black List Control
This command provides additional control over the black listed numbers of
automatic redialing feature. Set command clears the total black list.
The read command returns the black list status. If the black list is full then it
returns +SKRBLC: 1, otherwise it will return +SKRBLC: 0

Syntax Description

+SKRBLC OK
ERROR
+SKRBLC? +SKRBLC: <Black list status>
OK

Parameters

<black list status> 0 Black list is not full

1 Black list is full

Examples

Commands Possible Responses Description

AT+SKSAUTR=1 OK Enable automatic redialing and

AT+SKCCS=1 OK URCs
ATD1234; OK
+SKCCSI: 1, 0, 2, 0, 0, , Outgoing call URC
”1234”, 129

+SKCCSI: 1, 0, 7, 0, 0, In case of redial it will give instead

17, ”1234”, 129 of 7(call failed and redial will be
initiated).

+SKRDLI: 1, 1, “1234”, Redialing is indicated with a timer

129, 5 of 5 seconds

+SKRDLI: 1,2, “1234”, Event indicating expiration of

129 redial timer
+SKCCSI: 1, 0, 2, 0, 0, , URC to indicate outgoing call
”1234”, 129
+SKCCSI: 1, 0, 7, 0, 0, Call failed and redial will be
17, ”1234”, 129 initiated

+SKRDLI: 1, 1, “1234”, Redialing is indicated with a timer

129, 60 of 60 seconds

+SKRDLI: 1,2, “1234”, Event indicating expiration of

129 redial timer
+SKCCSI: 1, 0, 2, 0, 0, , URC to indicate outgoing call
”1234”, 129
Redial attempts for 10 times.
 +SKCCSI: 1, 0, 6, 0, 0,
17, ”1234”, “” Call failed and no redial will be
initiated
+SKRDLI: 1,3,“1234”, 129
This number has been put in black
list
AT+SKRBLC? +SKRBLC: 1 Black list is full
OK
AT+SKRBLC OK Black list is cleared.
AT+SKRBLC? +SKRBLC: 0 Black list is not full
OK
AT+SKRBLC OK Black list clearing command will be
accepted at any point of time

3.6 +SKCTVE, Individual Call Time Value

+SKCTVE, Individual Call Timer Value
The set command controls the presentation of an unsolicited result code +SKCTVI:
<id>, <dur> when a call is cleared. Read Command returns the current setting value
of +SKCTVE command. The test command returns values supported by the ME as a
compound value.

Syntax Description

+SKCTVE=<n> +CME ERROR: <err>

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

Parameters

<n> integer type; indicates whether this URC is enabled

0 disable +SKCTVI URC
1 enable +SKCTVI URC

<id> integer type; denote the call ID ID (see GSM 02.30 [19] Sub
clause 4.5.5.1)

<dur> integer type; represents the duration of the call

Indexed by <id> in unit of seconds

Examples

Commands Possible Responses Description

ATD112; OK Make an emergency call
AT+SKCTVE=1 OK
ATH +SKCTVI: 1,19 Hang up the call. Call lasted for
OK 19s.
3.7 +SKCTV Call Timer Value
+SKCTV Call Time Value
This command returns the value of the last call duration in seconds.

Syntax Description

+SKCTV +SKCTV: <dur>

+CME ERROR: <err>
+SKCTV=? OK

Parameters

<dur> It is an integer type; represents the duration of the last call in

unit of seconds

Examples

Commands Possible Responses Description

ATD112; OK Make an emergency call
ATH OK Hang up the call
AT+SKCTV +SKCTV: 19 Query the value of <dur>
OK Last call lasted 19 seconds
3.8 +SKCCS Current Call State Indication
+SKCCS Current call State Indication
The set command controls the presentation of an unsolicited result code:
+SKCCSI:<id>,<dir>,<stat>,<mode>,<mpty>,[disc_cause][,<number>, <type>[,
[<alpha>][,<line_num]]] in case of a change of any parameter of current calls. The
read command returns the current command setting. The test command returns
supported values as a compound value.

Syntax Description

+SKCCS=<act> OK
+SKCCS? +SKCCS: <act>
+SKCCS=? +SKCCS: (list of supported values)
Parameters

<act> 0 – Disable +SKCCSI event

1 – Enable +SKCCSI event

<id> integer type; call identification number as described in GSM

02.30 [19] Sub clause 4.5.5.1; this number can be used in
+CHLD command operations
<dir> 0 – mobile originated (MO) call
1 – mobile terminated (MT) call
2 – SAT call (SETUP CALL)

<stat> Call states (see +CLCC for most call states)

0 – Active
1 – Held
2 – Dialing (MO call)
3 – Alerting (MO call)
4 – Incoming (MT call)
5 – Waiting (MT call)
6 – Terminated: any call indicated in another state will get this
as the last state; if the same call id later on is reported again,
then it is a new call. (If redialing for the call should happen,
then the call will first be indicated with state terminated and
then with state redialing.)
7 – Redialing call (MO call): call is scheduled for redialing
which will start at timer expiration
<mode> (bearer/teleservice):
0 – Voice
1 – Data
2 – Fax
3 – Voice followed by data, voice mode
4 – Alternating voice/data, voice mode
5 – Alternating voice/fax, voice mode
6 – Voice followed by data, data mode
7 – Alternating voice/data, data mode
8 – Alternating voice/fax, fax mode
9 – Unknown

<mpty> It is not valid for call terminates state (6).

0 – Call is not one of multiparty (conference) call parties
1 – Call is one of multiparty (conference) call parties
<number> string type phone number in format specified by <type>; this
number is updated when information is received about COLP,
ECT, CD, …
<type> type of address octet in integer format (Refer to GSM 04.08 [8]
Sub clause 10.5.4.7)
<alpha> string type alphanumeric representation of <number>
corresponding to the entry found in phonebook; used character
set should be the one selected with command "Select TE
Character Set +CSCS"

<line_number> 1 – Call associated with Line 1

2 – Call associated with Line 2

<disc_cause> integer type and it is valid only for disconnect state (6)
1 - unassigned number
3 - no route to destination
6 - channel unacceptable
8 - operator determined barring
16 - normal call clearing
17 - user busy
18 - no user responding
19 - user alerting, no answer
21 - call rejected
22 - number changed
26 - non selected user clearing
27 - destination out of order
28 - invalid number format
29 - facility rejected
30 - response to status enquiry
31 - normal, unspecified
34 - no channel available
38 - network out of order
41 - temporary failure
42 - switching equipment congestion
43 - access information discarded
44 - requested channel unavailable
47 - resources unavailable
49 - quality of service unavailable
50 - requested facility unsubscribed
55 - incoming calls barred within CUG
57 - bearer capability not authorized
58 - bearer capability not available
63 - service not available
65 - bearer service not implemented
68 - ACM reached ACM maximum
69 - facility not implemented
70 - only restricted bearer cap. avail.
79 - service not implemented
81 - invalid TI
87 - no member of CUG
88 - incompatible destination
91 - invalid transit network selection
95 - incorrect message
96 - invalid mandatory information
 97 - message type not implemented
98 - message type incompatible
99 - info element not implemented
100 - conditional info element error
101 - message incompatible
102 - recovery on time expiry
111 - protocol error
127 - interworking error
133 - Service area prohibited
134 - GPS not available
200 - bearer service not available
201 - no TI available
202 - timer 303 expiry
203 - establishment failure
210 - no error
207 – Number black listed
210 – Call is rejected by SIM (Because of call control fail)
211 – Call is rejected by MS, because other redial is in progress
220 – system under arbitration
221 – higher priority request present
222 – fdn check failed
223 – duplicate transmission not allowed
224 – call rejected by sat
225 – ps call is already accepted by application
226 - cs call is already accepted by application
227 – number present in redial blacklist
228 – active cs call exists
229 – redial call cleared
230 - operation not allowed

Examples

Commands Possible Responses Description

AT+SKCCS=1 OK Enable +SKCCSI URC
ATD9880635407; OK Making a call
+SKCCSI:1,0,2,0,0,, Dialing MO call A (Alpha and line
”9880635407”,129 numbers are not available and hence it
is not displayed)
+SKCCSI:1,0,3,0,0,, Called party is altered (e.g. call
”9880635407”, 129 forwarding)
+SKCCSI:1,0,0,0,0,, Call A active
”9880635407”, 129
AT+CHLD=2 OK Call A has been put on hold
+SKCCSI:1,0,1,0,0,,
”9880635407”, 129
ATD9849169113; OK Make an other MO call B
+SKCCSI:2,0,2,0,0,, Dialing MO call B (Alpha and line
” 9849169113”,129 numbers are not available and hence it
is not displayed)
+SKCCSI:2,0,0,0,0,, Call B is active
”9849169113”, 129
AT+CHLD=3 OK Add call A and B in MPTY
+SKCCSI:1,0,0,0,1,, Call A status
”9880635407”, 129
 +SKCCSI:2,0,0,0,1,, Call B status
”9849169113”, 129
AT+CHLD=11 +SKCCSI:1,0,6,0,,1 Call A has been terminated
6
NO CARRIER
ATH +SKCCSI:2,0,6,0,,1 Call B has been terminated
6
NO CARRIER
3.9 +SKCPI More Call Progress Information
+SKCPI More Call Progress Information
Execution Command:
This command refers to call progress information, which is indicated by the network
during call establishment. The set command enable/disables the presentation of
unsolicited notification result codes from TA to TE. When <n>=1 and a call progress
information is received during a call establishment, result code +SKCPI:
<cId>,<msgType>, <ibt>,<tch>[,<location>,<progress_description>] is sent to TE.
<cId> identifies the call in the call table. The value of <msgType> describes the
layer 3-message type that was used to transfer the call progress information. The
state of TCH assignment and the use of in-band tones for that call can be monitored
by the values of <ibt> and <tch>.
Test Command returns values supported by the TA as compound value
Syntax Description

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

Parameters

<n> Parameter sets/shows the result code presentation

status in the MS
0 disable
1 enable
<cId> It is an integer type; call identification number
<msgType> layer 3 message type
0 setup message (Both MO and MT)
1 release complete
2 alert message
3 call proceed message
4 synchronization message
5 call progress message
6 call connected
7 disconnect (Network initiated)
<ibt> Status of the usage of in-band tones
0 no in-band tones
1 in-bands tones
<tch> TCH assignment
0 TCH not assigned
1 TCH assigned
<Location> 0 User
1 Private network serving the local user
2 Public network serving the local user
4 Public network serving the remote user
5 Private network serving the remote user
10 Network beyond inter-working point
<progress_description> 1: Call is not end-to-end PLMN/ISDN, further call
progress information may be available in-band
2: Destination address in non-PLMN/ISDN
3: Origination address in non-PLMN/ISDN
4: Call has returned to the PLMN/ISDN
8: In-band information or appropriate pattern now
available
 32: Call is end-to-end PLMN/ISDN
64: Queuing

Examples

Commands Possible Responses Description

AT+SKCPI OK Enable call progress URC

ATD0223708666; OK Make an normal call
+SKCPI: 1,0,0,0 Setup request send to NW
+SKCPI: 1,3,0,0,0,32 Call proceeding message received
+SKCPI: 1,5,1,0,0,32 Call progress message received
with in-band tones
+SKCPI: 1,4,1,1 Channel synchronization is done
(rab is allocated)
+SKCPI: 1,6,1,1,0,32 Call connected
AT+SKCPI=? +SKCPI: (0, 1) Query the supported +SKCPI
OK parameter <n>
3.10 +SKCONDLY, Set CONNECT delay
+SKCONDLY, Set CONNECT delay
Execution Command:
This command gives control over the delay that has to be set after which
CONNECT will be sent to TE in case of CSD calls.

Syntax Description

+SKCONDLY=<mo_delay>,<mt_delay> OK
+SKCONDLY? +SKCONDLY:<mo_delay>,<mt_delay>
+SKCONDLY=? +SKCONDLY:(list of supported values)

Parameters

<mo_delay> Parameter defines the delay that is required before

sending CONNECT to TE in case of MO CSD call.

<mt_delay> Parameter defines the delay that is required before

sending CONNECT to TE in case of MT CSD call.

Examples

Commands Possible Responses Description

AT+SKCONDLY=10, OK Sets the <mo_delay> & <mt_delay>

15 with 10 & 15 respectively.

AT+SKCONDLY? +SKCONDLY: 10, 15 Read the current <mo_delay> &

<mt_delay> values in TA.
OK

AT+ SKCONDLY=? +SKCONDLY:(0-255), Query the supported + SKCONDLY

(0-255) parameters <mo_delay> &
<mt_delay>.
OK
3.11 +SKVTS DTMF and Tone Generation
+SKVTS DTMF and Tone Generation

This command allows the playing of locally generated DTMF tones. The command is
write only. In this profile of commands, this command does not operate in data or
fax modes of operation (+FCLASS=0,1,2-7). It applies only during Voice call.

Syntax Description

AT+SKVTS=<n>,<digit> OK
AT+SKVTS=? (list of supported <n>),(list of
supported digits)

Parameters

<digit> A single ASCII character in the set 0-9,#,*,A-D. This is

interpreted as a single ACSII character.
<n> Parameter to indicate the start/stop of DTMF tone.
0 Stop DTMF tone.
1 Start DTMF tone.
Examples

Commands Possible Responses Description

AT+SKVTS=1,”5” OK TA will play the DTMF tone to the

NW if it is on an active voice call.
AT+SKVTS=0,”5” OK TA will stop the DTMF tone if DTMF
tone is being played.
AT+SKVTS=0,”7” +CME ERROR: 3 TA sending error response if DTMF
tone has not been started earlier.
AT+SKVTS=1,”5” +CME ERROR: 4 TA sending error response while
executing command on a non-voice
call.
AT+SKVTS=? +SKVTS:(0-1),(0- TA returning the range of values of
9,A,B,C,D,#,*) test response.
OK
3.12 +SKVTD Tone duration
+SKVTD Tone duration

This command refers to an integer <n> that defines the minimum duration of tones
to be played as a result of +SKVTS command.

Syntax Description

+SKVTD=<n> OK

+SKVTD? +SKVTD :<n>

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

Parameters
<n> Integer type; can take values from 4-255.
NOTE: Each unit corresponds to 20ms. The minimum duration of the tone played
should be 80ms.

Examples

Commands Possible Responses Description

AT+SKVTD=5 OK The minimum duration of the tone
to be played is set to 100ms
(5*20ms).
AT+SKVTD? +SKVTD: 5 Read response
OK
AT+SKVTD=? +SKVTD: (4-255) Test response
OK
 4 Mobile Termination Control and Status Commands
4.1 +SKMS Current Modem and SIM Status
+SKMS Current Modem and SIM Status
Protocol stack should export all the relevant state changes to the application. This
command has been added to export the miscellaneous stack state changes, which
are not given through the standard AT commands such as +CGREG, +CREG and +CPIN
and etc.
The set command controls the presentation of an unsolicited result code +SKMSI:
<sim_status>, <modem_status>in case of a change in the modem or SIM status.
The read command returns the current command setting and modem and SIM status.
Test command returns supported values as a compound value.

Syntax Description

+SKMS=<act> +CME ERROR: <err>

+SKMS? +SKMS: <act>, <sim_status>,
<modem_status>
+SKMS=? +SKMS: (list of supported <act>)

Parameters
<act> 0 – Disable unsolicited event
1 – Enable unsolicited event

<sim_status> 0 – SIM present and SIM is

personalized
1 – SIM Present and SIM is not
personalized
2 – SIM removed
3 – SIM absent
4 – SIM refreshed "Refresh mode =
SIM Initialization
5 - SIM refreshed "Refresh mode =
File Change Notification
6 - SIM refreshed "Refresh mode =
SIM Initialization and File
Change Notification
7 - SIM refreshed "Refresh mode =
SIM Initialization and Full File
Change Notification
8 - SIM refreshed "Refresh mode =
SIM Reset.
<modem_status> 0 – Modem not ready (+CFUN is not
given)
1 – Modem is in limited service
mode (Only emergency calls
and SIM and NVM access is
allowed)
2 – Modem is in full mode (All
services are allowed)
3 - PS Connection suspended
4 – PS Connection resumed
5 – Out of coverage
 Note: 3 and 4 values are not valid
in read mode

Examples

Commands Possible Responses Description

AT+SKMS=1 OK Enable to mode status unsolicited
events
+SKMSI: 2,1 SIM is removed and modem is in
limited service mode
+SKMSI: 4,1 SIM got refreshed and modem is in
limited service modes
+SKMSI: 1,2 Modem is in full mode
AT+SKMS? +SKMS: 1,1,2 Read the current SIM and Modem
status
4.2 +SKCPBSC Phonebook update notification
+SKCPBSC Phonebook update notification

This command controls the presentation of the update status URC +SKCPBSCI:
<storage>, <index>, <operation> when the storage status is changed, because of the
updating a new record or deleting an existing record.

Syntax Description

+SKCPBSC=<mode> OK
+SKCPBSC? +SKCPBSC:<mode>
+SKCPBSC=? +SKCPBSC: (list of supported values for
<mode>)

Parameters

<Mode> 0 Disable +SKCPBSCI URC

1 Enable +SKCPBSCI URC
<Storage> "SM" SIM phonebook
"FD" FDN EF
"EN" Emergency numbers
"ON" Own number
"SD" Service Dialing number
<operation> 0 Added/updated
1 Deleted
2 Deleted all records

Limitation

Delete all record operation is not supported

Examples

Commands Possible Responses Description

AT+CFUN=1 OK Protocol stack is activated

AT+SKCPBSC=1 OK Enable the URC
AT+SKCPMS=”SM” OK Set the storage type
AT+CPBW=1 +SKCPBSCI: 1st record is deleted
"SM",1,1
OK
4.3 +SKCPBS Phonebook storage ready notification
+SKCPBS Phonebook Storage Ready Notification

This command controls the presentation of the storage ready URC +SKCPBSI:
<storage>, <used record>,<total records> when the storage is ready to read.

Syntax Description

+SKCPBS=<mode> OK
+SKCPBS? +SKCPBS:<mode>
+SKCPBS=? +SKCPBS: (list of supported values for
<mode>)

Parameters

<Mode> 0 Disable +SKCPBSI URC

1 Enable +SKCPBSI URC
<Storage> "SM" SIM phonebook
"FD" FDN EF
"EN" Emergency numbers
"ON" Own number
"SD" Service Dialing number

Assumption

By default this URC is enabled in modem.

Examples

Commands Possible Responses Description

AT+SKCPBS=1 OK Enable the SKCPBSI URC

+SKCPBSI: “ADN” is ready and it has 10 used
“SM”,10,250 records out of 250 total records.
+SKCPBSI:”ON”,1,5 “ON” is ready and it has 1-used records
out of 5 records.
AT+CFUN=1 OK Protocol stack is activated

4.4 +SKCPIN PIN Remaining Attempts

+SKCPIN PIN Remaining Attempts
This command returns the remaining number of attempt for each PIN code: PIN1,
PIN2, PUK1 and PUK2. If reading fails (SIM not inserted/SIM failure), an +CME
ERROR:<err> will be returned.

Syntax Description

+SKCPIN +SKCPINC=<pin1>,<pin2>,<puk1>,<puk2>
OK
+CME ERROR: <err>

Parameters

<pin1> integer type; indicates the remaining attempt times of PIN1

Define values 0-3 and 0 means SIM is PIN1 blocked
<pin2> integer type; indicates the remaining attempt times of PIN2
Define values 0-3 and 0 means SIM is PIN2 blocked
<puk1> integer type; indicates the remaining attempt times of PUK1
Defined values 0 – 10 and 0 means SIM is invalidated by PUK1
<puk2> integer type; indicates the remaining attempt times of PUK2
Defined values 0 – 10 and 0 means SIM is invalidated by PUK2

Assumption
None
Examples

Commands Possible Responses Description

<SIM card not +CME ERROR: “SIM Read PIN counter and return ERROR
present> is not inserted” because SIM is not inserted
AT+SKCPIN

AT+CFUN=2 +CME ERROR: “SIM Detect the SIM, PIN is needed

PIN required”
AT+SKCPIN +SKCPIN: 3,3,10,10 Read the remaining PIN attempts
OK
AT+CPIN=”1234” +CME ERROR: PIN1 is not correct and it is giving as an
“incorrect error
password”
AT+SKCPIN +SKCPIN: 2,3,10,10 Read the remaining PIN attempts
OK

AT+CPIN=”1234” +CME ERROR: PIN1 is not correct and it is giving as an

incorrect password error
AT+SKCPIN +SKCPIN: 1,3,10,10 Read the remaining PIN attempts

AT+CPIN=”1234” +CME ERROR: Read the remaining PIN attempts

incorrect password
AT+SKCPIN +SKCPIN: 0,3,10,10 PIN1 is blocked and need to provide the
PUK1
4.5 +SKECAOC, Extended query CCM using PUCT
+SKECAOC, Extended query CCM using PUCT
Execution Command
Return the current value of the current call meter, calculated with the values given
by the price per unit and currency table stored in SIM
Syntax Description

+SKECAOC +SKECAOC: <cur>,<price>

+CME ERROR: <err>
+SKECAOC=? OK

Parameters

<cur> string type; up to three characters currency code (e.g.

“GBP”,”DEM”); character set as specified by command Select
TE character set +CSCS
<price> string type; calculated price value of accumulated call meter;
dot is used as a decimal separator

Examples

Commands Possible Responses Description

AT+CSCS=”IRA” OK Select character set
AT+SKECAOC +SKECAOC: “NT”,”1.50” Query current call meter using
OK PUCT

4.6 +SKECACM, Extended query ACM using PUCT

+SKECACM, Extended query ACM using PUCT

Returns the current value of the accumulated call meter, calculated with the values
given by the price per unit and currency table stored in SIM.

Syntax Description

+SKECACM +SKECACM: <cur>,<price>

+CME ERROR: <err>
+SKECACM=? OK

Parameters

<cur> string type; up to three characters currency code (e.g.

“GBP”,”DEM”); character set as specified by command Select
TE character set +CSCS
<price> string type; calculated price value of accumulated call meter;
dot is used as a decimal separator

Examples

Commands Possible Responses Description

AT+CSCS=”IRA” OK Select character set

AT+SKECACM +SKECACM: “NT”,”2.66” Query current accumulated call
OK meter using PUCT

4.7 +SKCCCME, Individual Call Meter and Charges

+SKCCCME, Individual Call Meter and Charges
The set command controls the presentation of an unsolicited result code +SKCCCM:
<id>,<cm>,<cur>,<price>. In fact, this is the unsolicited version of +SKECAOC, which
also supports multiple calls. The difference is that +SKECAOC command returns the
total call meter of all calls the MS is involved in and SKCCME, if enabled, returns call
meter and price information of each individual call. Read Command returns currently
setting of +SKCCCME. The test command returns values supported by the ME as a
compound value.

Syntax Description
+SKCCCME=<n> +CME ERROR: <err>
+SKCCCME? +SKCCCME: <n>
+CME ERROR: <err>
+SKCCCME=? +SKCCCME: (list of supported <n>s)

Parameters

<n> integer type; indicates whether this URC is enabled

0 disable +SKCCCM URC
1 +SKCCCM URC will be given only after call
termination
2 +SKCCCM URC will be given during the call and also after
call termination
<id> integer type; denote the call ID (see GSM 02.30 [19] Sub
clause 4.5.5.1)
<cm> string type; three byte of the specific call <id> meter
value in hexadecimal format (e.g. “00001E” indicates
decimal value 30); value is in home units
<cur> string type; up to three characters currency code (e.g.
“GBP”,”DEM”); character set as specified by command
Select TE character set +CSCS
<price> string type; current calculated price of the call <id>;
dot is used as a decimal separator

Examples

Commands Possible Responses Description

AT+SKCCCME=2 OK URC is sent to user whenever CCM
is updated during the call and also
after call termination.
AT+SKCCCME? Reading the value
+SKCCCME: 1
OK
AT+SKCCCME=? +SKCCCME: (0-2) Giving the possible values
OK

4.8 +SKAOCINV, Individual Call AoC Invocation Indications

+SKAOCINV, Individual Call AoC Invocation Indications

The set command controls the presentation of an unsolicited result code +SKAOCINV:
<id>,<inv stat>. Read Command returns currently setting of +SKAOCINV. The test
command returns values supported by the ME as a compound value.
Syntax Description
+SKAOCINV=<n> +CME ERROR: <err>
+SKAOCINV? +SKAOCINV: <n>
+CME ERROR: <err>
+SKAOCINV =? +SKAOCINV: (list of supported <n>s)
Parameters

<n> integer type; indicates whether this URC is enabled

0 disable +SKAOCINVI URC
1 enable +SKAOCINVI URC
<id> integer type; denote the call ID (see GSM 02.30 [19] Sub clause
4.5.5.1)
<inv stat> Integer type: indicates the status of invocation of AoC
for a call
0 – Initial invocation of AoC
1 – Updation of AoC parameters during call
2 - Updation of AoC parameters disabled
Examples

Commands Possible Responses Description

AT+SKAOCINV=1 OK URC is sent to user whenever AoC
parameters are updated.
AT+SKCCCME=2 OK

ATD1234; OK MO call establishment

+SKAOCINVI: 0 Initial invoke of AoC

+SKCCCM: Application notified when the call

1,”000001”,”INR”,”2.0” meter is updated for the call
+SKCCCM:
1,”000002”,”INR”,”4.0”

+SKAOCINVI: 1 Change of AoC parameters during

the call
+SKCCCM: Application notified when the call
1,”000003”,”INR”,”6.0” meter is updated for the call

+SKCCCM: Application notified when the call

1,”000005”,”INR”,”10.0” meter is updated for the call
NO CARRIER during call disconnect
AT+SKAOCINV? +SKAOCINV: 1 Reading the value
OK
AT+SKAOCINV=? +SKAOCINV: (0-1) Giving the possible values
OK

4.9 +SKPINSTAT

+SKPINSTAT SIM PIN status change indication

The set command enables/disables the presentation of an unsolicited result code:

+SKPINSTATI: <stat> in case of a change in the current PIN1/PUK1 required status for SIM. The
read command returns the current command setting. The test command returns supported
values as a compound value.

Syntax Description

+SKPINSTAT=<act> OK
+SKPINSTAT? +SKPINSTAT: <act>
+SKPINSTAT=? +SKPINSTAT: (list of supported values)

Parameters

<act> 0 – Disable +SKPINSTATI event

1 – Enable +SKPINSTATI event

<stat> Current SIM PIN1-required status

0 – Ready
1 – PIN1 required
2 – PUK1 required
3 – SIM locked (Maximum PUK1 attempts exceeded)

Examples

Commands Possible Responses Description

AT+SKPINSTAT=1 OK Enable +SKPINSTATI unsolicited

AT+CFUN=2 +CME ERROR: PIN required In case of PIN-locked SIM, on SIM

+SKPINSTATI: 1 activation, PIN1 is required and
corresponding URC is sent.

AT+CPIN=”8888” OK On entering correct PIN, SIM is in Ready state

+SKPINSTATI: 0 and corresponding URC is sent.

On exceeding maximum attempts for wrong

AT+CPIN=”1234” +CME ERROR: PUK PIN, PUK is required to unblock the SIM and
required corresponding URC is sent.
+SKPINSTATI: 2
URC is enabled
AT+SKPINSTAT?
+SKPINSTAT: 1
Test command response
AT+SKPINSTAT=?
+SKPINSTAT: (0-1)
 5 Network Management and Modem Information

5.1 +SKCNL Network Location Information

+SKCNL Network Location Information
The set command controls the presentation of an unsolicited result code +SKCNLI:
<long_name>,<short_name>,[<ucs2_name>],<id>[,<lac>,<ci>],channel_id in case of
a change in the MT's registered network + Cell location or when new information
becomes available (e.g. NITZ).
The read command returns the current command setting and the network + cell
location status. Test command returns supported values as a compound value.

Syntax Description

+SKCNL=<act> OK
+SKCNL? +SKCNL:
<act>,<long_name>,<short_name>
,[<ucs2_name>] ,<id>
[,<lac>,<ci>],channel_id
+SKCNL=? +SKCNL: (list of supported values)

Parameters

<act> 0 – Disable +SKCNLI event

1 – Enable +SKCNLI event without cell information
(<lac>, <ci>)
2 – Enable +SKCNLI event including cell information
(<lac>, <ci>)

<long_name> GSM operator full name

<short_name> GSM operator short name (8 chars)

<ucs2_name> UCS2 (Unicode) GSM operator name if available through NITZ
event. Hex encoded
<id> GSM operator numeric id (6 chars)
<lac> Local area code in hexadecimal (4 chars)
<ci> Cell Id in hexadecimal (4 chars)
<channel_id> arfcn
Assumptions

Modem would search the operator’s name in the following order:

1. Search in NITZ information
2. Search in SIM if the registered network is Home PLMN
3. Search in Static operator name table
4. Search to get the country name with MCC codes
Note: SIM doesn’t have operator name EF as per the rel-99 and hence modem will
not support search in SIM.

Examples

Commands Possible Responses Description

AT+SKCNL? +SKCNL: 1,”AITEL Get the current network

 IL”,”AIRTEL”,,”42501”,” information
2DEF”,”80AB”,65
OK
AT+SKCNL=1 OK Enable network location
information unsolicited event.
+SKCNLI:”AITEL MS sends this information
IL”,”AIRTEL”,“42501“,65 whenever it gets NITZ information
from network

AT+SKCNL=2 OK Enable network location

information unsolicited event with
cell information.
+SKCNLI:”AITELIL”,”AIRT MS sends this information
EL”,“42501“,”2DEF”,“80 whenever it gets NITZ information
AB“,65 from network

5.2 +SKECOPS Asynchronous Version of COPS AT command

+SKECOPS Asynchronous version of COPS AT command

This is an asynchronous version of the standard +COPS AT command. It returns OK
immediately while PLMN search (+SKECOPS=?) or network registration
(+SKECOPS=1,..) goes on in background. The result of the operation will be
presented as an unsolicited result code. Refer the section 7.3 of 3GPP 27.07 for
more details about regular behavior of this command.
Please, note that the unsolicited response containing the list of PLMNs can also be
received after stack activation, if the modem is in manual PLMN selection mode and
the last PLMN could not be found.

Syntax Description
+SKECOPS=[<mode +CME ERROR: <err>
>[,<format>[,<ope
r>]]]
+SKECOPS? +SKECOPS: <mode>[,<format>,<oper>]
+CME ERROR: <err>
+SKECOPS=? +SKECOPS: [list of supported (<stat>,long alphanumeric
<oper>,short alphanumeric <oper>,numeric <oper>)s]
[,,(list of supported <mode>s),(list of supported <format>s)]
+CME ERROR: <err>

Parameters

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

manual (<oper> field shall be present)
1 deregister from network
set only <format> (for read command +SKECOPS?),
2 do not attempt registration/deregistration (<oper>
field is ignored); this value is not applicable in
3 read command response
4 manual/automatic (<oper> field shall be present);
if manual selection fails, automatic mode
(<mode>=0) is entered

<Format> 0 long format alphanumeric <oper>

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

Examples
Commands Possible Responses Description

AT+CREG=2 OK Enable the registration status

unsolicited event.

AT+SKECOPS=0 OK Initiate automatic mode PLMN

selection; MS is searching for
PLMNs in background.
+CREG: 2 Registered to home network
AT+SKECOPS=? OK Immediate OK, while MS scans in
+SKECOPS: (1,””,””, background and later presents the
“40414”), PLMN list to TE
(1,””,””,”40415”),,(0-4),
(0-2)
AT+SKECOPS? +SKECOPS: 1,2,”40414” Read the current registered PLMN
OK and registration mode.

5.3 +SKSBP Set Band Priority

+SKSBP Set Band Priority

This command would be used to set the priority of the bands in NVM and new band
information will come to effective immediately after writing this into NVM.

Syntax Description
+SKSBP=<List of bands> +CME ERROR:<err_id>
+SKSBP? +SKSBP:<user selected bands>
+SKSBP=? +SKSBP:<<System supported bands>

Parameters

<List of bands> 1 900 Band

3 1800 Band
4 1900 Band
7 850 Band

Examples

Commands Possible Responses Description

AT+SKSBP=”4,7” OK Band info is valid and

updated in NVM
AT+SKSBP=? +SKSBP: ”1,4,7” Read the system supported
OK bands
AT+SKSBP? +SKSBP: “4,7” Read user selected band info
OK
AT+SKSBP=”1,3” +CME ERROR: operation not System doesn’t support band
allowed 3 and hence this operation is
not allowed.
5.4 +SKCATT CS Attach or Detach
+SKCATT CS Attach or Detach

This execution command is used to attach the MT to, or detach the MT from, the
Circuit Switch service. After the command has completed, the MT remains in
V.25ter command state. If the MT is already in the requested state, the command
is ignored and the OK response is returned. If the requested state cannot be
achieved, an ERROR or +CME ERROR response is returned.
The read command returns the current Circuit Switch service state.
The test command is used for requesting information on the supported Circuit
Switch service states.

Syntax Description

+SKCATT= [<state>] OK
ERROR
+SKCATT? +SKCATT: <state>
+SKCATT=? +SKCATT: (list of supported
<state>s)

Parameters

<state> Indicates the state of CS

attachment
0 Detached
1 Attached

Examples

Commands Possible Responses Description

AT+SKCATT=1 OK Initiating CS attach

AT+SKCATT? +SKCATT: 1 CS attached
OK
AT+SKCATT=0 OK Initiating CS detach
AT+SKCATT? +SKCATT: 0 CS detached
OK
AT+SKCATT=? +SKCATT: (0-1) Test mode
OK
5.5 +SKCCATT CS and PS Attach or Detach
+SKCCATT CS and PS Attach or Detach

This execution command is used to attach the MT to, or detach the MT from, the
Circuit Switch and Packet Domain service. After the command has completed, the
MT remains in V.25ter command state. If the MT is already in the requested state,
the command is ignored and the OK response is returned. If the requested state
cannot be achieved, an ERROR or +CME ERROR response is returned.
The read command returns the current Circuit Switch and Packet Domain service
state.
The test command is used for requesting information on the supported service
states.

Syntax Description

+SKCCATT= [<state>] OK
ERROR
+SKCCATT? +SKCCATT: <state>
+SKCCATT=? +SKCCATT: (list of supported
<state>s)

Parameters

<state> Indicates the state of CS and PS

attachment
0 Detached
1 Attached

Examples

Commands Possible Responses Description

AT+SKCCATT=1 OK Initiating CS and PS attach

AT+SKCCATT? +SKCCATT: 1 CS and PS attached
OK
AT+SKCCATT=0 OK Initiating CS and PS detach
AT+SKCCATT? +SKCCATT: 0 CS and PS detached
OK
AT+SKCCATT=? +SKCCATT: (0-1) Test mode
OK
5.6 +SKEXTREG Extended Network Registration Status
+SKEXTREG Extended Network Registration Status

The set command controls the presentation of an unsolicited result code

+SKEXTREG: <stat> when <n>=1 and there is an internal event modifying the current
network registration status, which are not covered by standard +CREG event. Read
command returns the status of result code presentation.

Syntax Description

AT+SKEXTREG=<n> OK
CME ERROR: <err>
AT+SKEXTREG =? +SKEXTREG: (list of supported <n>s)

Parameters

<n> 0 Disables unsolicited result code

1 Enables unsolicited result code

<stat> 0 Registration denied as Cell Barred.

1 UT is starting registration on selected PLMN.
2 UT is starting acquisition of new GPS fix.
3 Registration denied as illegal ME.
4 Registration denied as SIM is not provisioned (regn
denied cause = IMSI unknown in HLR)
5 Registration denied as SIM is not recognized by
network. (regn denied cause = authentication
failure or IMSI unknown in VLR)
6 Notification of completion of GPS acquisition
procedure (for closing GPS Wizard in application)
 6 Short Messaging Service (SMS) support

6.1 +SKCPMS Extended Preferred Message Storage

+SKCPMS Preferred Message Storage

This command selects memory storages <mem1>, <mem2> and <mem3> to be used
for reading, writing, etc. If chosen storage is not appropriate for the ME (but is
supported by the TA), final result code +CMS ERROR: <err> shall be returned. Test
command returns lists of memory storages supported by the TA.

Syntax Description

+SKCPMS=<mem1>[,<mem2>[,<mem3>]] +SKCPMS: <total1>,<total2>,<total3>

+CMS ERROR: <err>
+SKCPMS? +SKCPMS:
(mem1>,<total1>,<mem2>,<total2>,
<mem3>,<total3>
+CMS ERROR: <err>
+SKCPMS=? +SKCPMS: (list of supported
<mem1>s), (list of supported
<mem2>s),(list of supported
<mem3>s)

Parameters
Refer sec 9.1 for definition of parameters

Limitation

Mem1, Only SM storage is supported

mem2,
mem3

Examples

Commands Possible Responses Description

AT+SKCPMS=? +SKCPMS: ("SM"),("SM"), The different memory options

("SM") for reading, writing, etc.
OK

AT+SKCPMS="ME", +CMS ERROR: “operation not ME memory is not supported

"ME","ME" allowed”
AT+SKCPMS=”SM”, +SKCPMS: Set memory type as SM for
”SM”,”SM” “SM”,100,”SM”,200,”SM”,10 mem1, mem2, and mem3.
OK
6.2 +SKSMMA More Memory Available
+SKSMMA More Memory Available

If SMS storage in SIM is in control of stack then this AT command is used to indicate
that ME memory is available.Else if SMS storage in SIM is in control of MMI then this
AT command act as follows.
Execution Command sends RP-SMMA message to the SMSC to indicate to the network
that the MS again has memory available for SMS reception. This command needs to
be sent if previously the TE with +CNMA sent an RP-ERROR with cause D6 (memory
exceeded). If now, the user deletes some messages and the TE needs to inform the
stack and the SMSC that now the MS has memory available again.

Syntax Description

+SKSMMA +CMS ERROR: <err>

Parameters
Refer section 9.1 for detail description of these parameters

Examples

Commands Possible Responses Description

AT+CNMA=? +CNMA: (0-2)

List supported value(s)
OK
AT+CMGF=0 OK Select PDU mode
AT+CNMI=2,2,0,0, OK Set MS behavior for MT SMS
0 Select Phase 2+ service
+CSMS: 1,1,1
AT+CSMS=1 OK
AT+SKSMMF OK Indicating memory is full.

+CMT: 33 A MT SMS arrives; +CMT unsolicited

0791889683434822040C9 result code is issued
188965293787200001080
12915115020FD3B29B0E3
2CBDF6D50900D478701
AT+CNMA=2,3
>00D600<ctrl-Z> Acknowledge the network when a
OK SM is received with RP-ERROR
cause D6 (Memory capacity
exceeded)

AT+SKSMMA
OK Indicate to SMSC that more
memory is available

+CMT: 33 SMSC sends previous message again

0791889683434822040C9
188965293787200001080
12915115020FD3B29B0E3
2CBDF6D50900D478701
SMS storage in SIM is in control of
 MMI
AT+CNMA=? +CNMA: (0-2)
List supported value(s)
OK
AT+CMGF=0 OK Select PDU mode
AT+CNMI=2,2,0,0, OK Set MS behavior for MT SMS
0 Select Phase 2+ service
+CSMS: 1,1,1
AT+CSMS=1 OK
AT+SKSMMF OK Indicating memory is full.

+CMT: 33 A MT SMS arrives; +CMT unsolicited

0791889683434822040C9 result code is issued
188965293787200001080
12915115020FD3B29B0E3
2CBDF6D50900D478701

AT+CNMA=2,3 Acknowledge the network when a

>00D600<ctrl-Z> OK SM is received with RP-ERROR
cause D6 (Memory capacity
exceeded)

User deleted SMS entry 1

Indicate to SMSC that more
AT+CMGD=1 OK memory is available

AT+SKSMMA OK SMSC sends previous message again

+CMT: 33
0791889683434822040C9
188965293787200001080
12915115020FD3B29B0E3
2CBDF6D50900D478701
6.3 +SKSMMF Memory Full.
+SKSMMF Memory Full

This AT command is to acknowledge modem that ME memory is full.

Syntax Description

+SKSMMF OK
+SKSMMF? +SKSMMF:<status>
Parameters

<status> 0 Memory status unavailable

1 Memory Full
2 Memory Available
Examples

Commands Possible Responses Description

AT+CNMA=? +CNMA: (0-2)

List supported value(s)
OK
AT+CMGF=0 OK Select PDU mode

AT+CNMI=2,2,0,0, OK Set MS behavior for MT SMS

0 Select Phase 2+ service

AT+CSMS=1 +CSMS: 1,1,1

OK
AT+SKSMMF OK Acknowledge modem that ME
memory is full.

+CMT: 33 A MT SMS arrives; +CMT unsolicited

0791889683434822040C9 result code is issued
188965293787200001080
12915115020FD3B29B0E3
2CBDF6D50900D478701

AT+CNMA=2,3 OK Acknowledge the network when a

>00D600<ctrl-Z> SM is received with RP-ERROR
cause D6 (Memory capacity
exceeded)
6.4 +SKCMGU Update SMS message
+SKCMGU Update SMS message

Execution Command updates a message to memory storage <mem2> in memory

location <index>. By default message status will be set to 'stored unsent', but
parameter <stat> allows also other status values to be given. (ME/TA manufacturer
may choose to use different default <stat> values for different message types.)
The entering of PDU is done similarly as specified in +CMGS. If writing fails, final
result code +CMS ERROR: <err> is returned.

Syntax Description

+SKCMGU=<index>,<length>[,<stat>]<CR> +CMS ERROR: <err>

PDU is given<ctrl-Z/ESC>
+SKCMGU=?

Parameters

Refer section 9.1 for detail description of these parameters

Examples

Commands Possible Responses Description

AT+SKCMGU=? OK
AT+SKCMGU=3,19 >
Write an SM to <mem2> index 3
>0001FF0A8190033
coded by GSM default coding
00387000008C332 OK
scheme
9B5D6787E5
AT+SKCMGU=4,16 >
>0001FF0A8190033 Write an SM to <mem2> index 4
00387000804624B6 OK coded by UCS2 coding scheme
A5F
AT+SKCMGU=5,16, >
3 Write an “STO SENT” SM to
>0001FF0A8190033 OK <mem2> index 5 coded by UCS2
00387000804624B6 coding scheme
A5F
AT+SKCMGU=6,27, >
0
> OK
0791889683434822 Write a “REC UNREAD” SMS-MT
040C91889652937 with content “MT by MMI”
8720000303062417
38323094D2A489C
07359B49
AT+SKCMGU=7,27, >
1
> OK
0791889683434822 Write a “REC READ” SMS-MT with
040C91889652937 content “MT by MMI”
8720000303062417
38323094D2A489C
07359B49
6.5 +SKCMGB Get occupied SMS storage Bitmap
+SKCMGB Get occupied SMS storage Bitmap

Read Command returns a bitmap <entries_bitmap> of all entries in SMS storage

<mem1>. Each occupied entry is marked by 1 and empty entries are marked by 0.

Syntax Description

+SKCMGB? +SKCMGB: <entries_bitmap>

Parameters

<entries_bitmap> String value; Hex encoded

representation of the bitmap

Examples

Commands Possible Responses Description

AT+SKCMGB? +SKCMGB: "FFF10000"

Entries 1 to 13 are occupied
OK

6.6 +SKCMGR Read SMS message without changing status

+SKCMGR Read SMS message without changing status

Execution Command returns message with location value <index> from preferred
message storage <mem1> to the TE. Status of the message and entire message data
unit <pdu> is returned. If status of the message is “REC UNREAD”, status in the
storage is retained. If reading fails, final result code +CMS ERROR: <err> is returned.

Syntax Description

+SKCMGR=<index> When command is successful:

+SKCMGR: <stat>,
[<alpha>],<length><CR><LF><pdu>
otherwise:
+CMS ERROR: <err>
+SKCMGR=?

Parameters

<stat> Integer type

0 RECEIVED UNREAD
1 RECEIVED READ
2 STORED UNSENT
3 STORED SENT
8 RECEIVED NEW
9 DELETED
<alpha> string type alphanumeric
representation of <da> or <oa>
corresponding to the entry found in
 MT phonebook; used character set
should be the one selected with
command Select TE Character Set
+CSCS
<length> integer type value indicating in the
text mode (+CMGF=1) the length of
the message body <data> > (or
<cdata>) in characters; or in PDU
mode (+CMGF=0), the length of the
actual TP data unit in octets (i.e.
the RP layer SMSC address octets
are not counted in the length)
<pdu> In the case of SMS: 3G TS 24.011
[6] SC address followed by 3G TS
23.040 [3] TPDU in hexadecimal
format: ME/TA converts each octet
of TP data unit into two IRA
character long hexadecimal
number (e.g. octet with integer
value 42 is presented to TE as two
characters 2A (IRA 50 and 65))

Examples

Commands Possible Responses Description

AT+CMGF=0 OK Switch to PDU mode
AT+SKCMGR=8 +SKCMGR: 0,,27 Read SM from index 8; it is coded
079188968343482204 in GSM default. The status is
0C9188967232337000 retained without any change.
003050329054402309
67B87C0E82CBCB66
OK
6.7 +SKCSM SMS State indications
+SKCSM SMS State indications

Use this command to receive notifications whenever SMS storage or message state
has changed.
The set command controls the representation of an unsolicited result code:
+SKCSMI: <storage>, <storage-state>[,<index>,<stat>] in case of a change in the
state of the message in location <index> in storage <storage>.
Read returns the current command setting.

Syntax Description

+SKCSM=<act> +CMS ERROR: <err>(when fail)

+SKCSM? +SKCSM: <act>,<storage>,<storage-
state>

Parameters

<act> Integer type

0 Disable +SKCSMI event
1 Enable +SKCSMI event
<storage> String type; storage name
(Currently, only “SM” is supported)
<index> Integer type; location of message
in storage
<storage-state> Integer type
0 Not ready
1 Ready
2 Full
3 Free memory available in SIM
storage
4 Storage overflow (This will be sent
when modem gets the class-2
message and SIM storage is full)
<stat> Integer type
0 RECEIVED UNREAD
1 RECEIVED READ
2 STORED UNSENT
3 STORED SENT
8 RECEIVED NEW
9 DELETED

Examples

Commands Possible Responses Description

AT+SKCSM=1 OK Enable +SKCSMI indications

AT+SKCSM? +SKCSM: 1,"SM",0 Query current storage state: Not
OK ready
…
+SKCSMI: "SM",1 SMS storage become ready
…
 +SKCSMI: "SM",1,7,9 SMS entry 7 was deleted

6.8 +SKCMGT Change SMS Message Status

+SKCMGT Change SMS Message Status

Execution command changes the state of the message with location value <index>.
Result code +CMS ERROR: <err> is returned if the state is illegal or the message does
not exist.

Syntax Description

+SKCMGT=<index>,<stat> +CMS ERROR: <err>(when fail)

Parameters

<stat> Integer type; message state. See in

+SKCSM, +SKCSMI Defined Values
Section.
Note: <stat>=9 (deleted) is not
applicable. Currently only <stat>
0,1,8 are supported

Examples

Commands Possible Responses Description

AT+SKCMGT=1,1 OK Change state of message 1 to

+SKCSMI: "SM",1,1,1 “RECEIVED READ” state.
 7 SIM Application Tool(SAT) in APDU format
All SAT proactive commands are classified into following two categories based on which module
is responsible for handling the proactive command. Reception of these two different command
categories is also indicated with different AT responses as defined in the following sections.
The modem does not support class a or e Sim Toolkit Functionality. If support for these classes
were needed, then the TE would have to provide such support itself.

1 Proactive command which are implemented in the modem (MT):

These proactive
commands are indicated with the SATN unsolicited response.
 MORE TIME
 POLL INTERVAL
 SEND SHORT MESSAGE
 SEND SS
 SEND USSD
 SETUP CALL
 REFRESH
 POLLING OFF
 PROVIDE LOCAL INFORMATION
1. Location information
2. IMEI of ME
3. Network measurement results
4. Timing Advance
 SETUP EVENT LIST
1. MT call
2. Call connected
3. Call disconnected
4. Location status
 TIMER MANAGEMENT
 RUN AT Command
 SENT DTMF
Note: RUN AT command is not supported

2 Proactive command which need to be implemented in TE, if they are supported:

These proactive commands are indicated with the SATI unsolicited response.
 DISPLAY TEXT
 GET INKEY
 INPUT KEY
 PLAY TONES
 SETUP MENU
 SELECT ITEM
 PROVIDE LOCAL INFORMATION
1. Date, time and time zone
2. Language setting

 SETUP EVENT LIST

1. User activity
2. Idle screen available
3. Card reader status
4. Language selection
5. Browser termination
6. Data available
 7. Channel status
 PERFORM CARD APDU
 POWER OFF CARD
 POWER ON CARD
 GET READER STATUS
 SETUP IDLE MODE
 CHANNEL NOTIFICATION
 LANGUAGE NOTIFICATION
 LAUNCH BROWSER
 OPEN CHANNEL
 CLOSE CHANNEL
 RECEIVE DATA CHANNEL
 SEND DATA
 GET CHANNLEL STATUS

Setup Event List Proactive command handling

Setup Event List can have the following three different combinations of events:

 Events which are handled by Modem only:

The modem is responsible for sending the response containing a success or failure
indication depending on whether it supports all events requested or not.

 Events which are handled by MMI only:

In this case modem would send this proactive command as it is to MMI by using +SKSATI
notification and it is MMI’s responsibility to send the terminal response back to modem.

 Events which are handled by both MMI and Modem:

If modem does not handle any of the events it is responsible for then modem will form
the Terminal Response containing a failure code and send it to SIM. If modem handles
all its relevant events, then setup event list command will be passed to the MMI using
SATI. MMI is expected to send terminal response through SKSATR depending on whether
it supports all the events or not.

7.1 +SKSATPD Profile Download Command

+SKSATPD Profile Download Command
This command gives the modem the necessary information to send the TERMINAL
PROFILE into SIM. This command needs to be sent before the SIM activation so
that the profile download can be performed.

The command contains an 18 byte HEX byte stream. TE would fill the MMI
relevant bytes/bits and all other modem relevant bits would be set to 0s. Modem
will then set its relevant bits/bytes as per the modem capabilities. Refer to the
section 5.2 from 3GPP 11.14 for details about the TERMINAL PROFILE structure.

Out of 18 bytes, modem is responsible for setting the following bits:

Byte number

Responsible bit position

1st
2nd
3rd
5th
6th
7th
8th

2nd

1st
2nd
3rd
4th

3rd

4th
6th
7th
8th

4th

2nd
3rd
4th
5th
7th
8th

5th
1st
2nd
3rd
4th
5th

8th

1st
2nd
6th
8th

9th

2nd
3rd
5th

13th

1st
2nd
6 – 8 bits

MMI is responsible to set the remaining bits/bytes in terminal profile.

Syntax Description

+SKSATPD=<terminal profile> OK
+SKSATPD: <terminal profile>
+SKSATPD?
OK
+SKSATPD=? OK

Parameters

<Terminal profile> String type; It is 18 bytes terminal profile (hexadecimal

format; refer +CSCS) in SIM expected format

Examples

Commands Possible Responses Description

AT+SKSATC=1,1 OK Set SAT URCs

AT+SKSATPD=”09FB9 OK Modem will combine the given MMI

73D61000058010000 profile with Modem profile and
00” resultant profile would be
downloaded into SIM when SIM
requests for Profile download at
SIM initialization.
AT+CFUN=2 OK SIM activation/detection; SIM is not
PIN protected.
AT+CFUN=1 OK Protocol stack is activated

7.2 +SKSATC Configuration of SIM Application Tool Kit

+SKSATC Configuration of SIM Application Tool Kit
This command is used to enable/disable the presentation of different unsolicited
notification result codes from TA to TE.

When <n>=1 and one of the following conditions have occurred, the respective
unsolicited result is sent to TE.

A command received from the SIM that is not handled by modem is

indicated to TE by +SKSATI: <satCmd>. The TE needs to answer such an
indication with +SKSATR.

If SIM application tries to set up a call using the Set Up Call feature
described in GSM 11.14, Modem sends the +SKSATA notification and MMI
should check all call related conditions and it is MMI’s responsibility to
accept or reject the SETUP call. Refer +SKSATA and +SKSATH AT command
for more details.

Modem handled proactive command and terminal response would be

notified using the +SKSATN: <satNtfy> URC.

When <m>=1 and one of the following conditions have occurred, the respective
unsolicited result is sent to TE:

The URC +SKSATV: [<status word>][,<envelop_cmd/response>] is sent to TE

as notification of the pair of envelope command and its response (if it was
triggered by the stack/L4 and not by the MMI). <Status word> must not be
present in case of envelope command.

The URC +SKSATS: <SIM response>,<MS status> is also sent as notification of

SIM's response to a call control or SMS control envelope. This URC informs
the TE of the outcome of the verification by the SIM (not allowed, allowed
with modification, allowed without modification).

A TE that wants to operate the SAT interfaces in APDU mode needs to at least set
<n> to 1. With this setting it will get all the information it needs. <m> settings is
not necessary and gives the TE just additional detailed information about the
message exchange between the modem and the SIM Application Toolkit.

Syntax Description

+SKSATC=<n>, <m> OK if the setting is successful; otherwise

+CME ERROR: <err> will be sent to TE
+SKSATC? + SKSATC: <n>, <m>
+SKSATC =? + SKSATC: (list of supported <n>s), (list of
supported <m>s)

Parameters

<n> parameter sets/shows the result code presentation status in

the MT for +SKSATN, +SKSATI and +SKSATA
0 Disable
1 Enable
<m> parameter sets/shows the result code presentation status in
the MT for +SKSATV and +SKSATS
0 Disable +SKSATV and +SKSATS URCs
1 Enable +SKSATV and +SKSATS
<satCmd> String type; Received SIM application proactive command
which is not handled by the MT; (hexadecimal format; refer
+CSCS) in APDU format as defined in 3GPP 11.14
<satRsp> String type; SIM envelope response in APDU format
(hexadecimal format; refer +CSCS) which is coming from SIM
<satNtfy> String type; commands or responses sent by ME to SIM or
command handled by ME (hexadecimal format; refer +CSCS) in
APDU format
<Status word> String type; It is two bytes value coded in HEX format.
<envelop_cmd/res String type; the content of envelope command and its response
ponse>: (hexadecimal format; refer +CSCS) in APDU format
<SIM response> 0 Allow without modification
1 Not allow
2 Allow with modification
<MS status> 0 MS will not continue previous
procedure (make call...etc)
1 MS will continue previous
procedure (make call...etc)

Examples

Commands Possible Responses Description

AT+SATC=1,1 OK SAT URCs are enabled

AT+SKSATPD=”09FB9 OK MMI SAT profile information given

73D61000058010000 to modem before SIM activation.
00”
AT+CFUN=2 OK SIM detect/SIM activation
AT+CFUN=1 OK Protocol stack is activated
Atd0800080090; OK
+SKSATV: , Call control envelop. It is an
“D40C820282 envelope commands hence status
818606818000800009” word is not present in this URC.
+SKSATV: “9000” Call control envelope response. It
is a response for the envelope
command but there is no response
string except the status and hence
it doesn’t show the envelope
response string in this URC.
 +SKSATS: 0,1 Call is allowed without any
modification
ATH OK Call got terminated by user

7.3 +SKSATE Send Envelope Command

+SKSATE Send Envelope Command
This command provides the possibility to send a command to the SIM, using the
envelope mechanism of SIM application toolkit as described in GSM 11.14. The
<satCmd> is given format expected by SIM and no modification is done in the
modem. As soon as a response from the SIM is received, the content is sent to ME
using the result +SKSATE: <status word> [,<satRsp> ]

Syntax Description

+SKSATE: <status word>

+SKSATE=<satCmd> [,<satRsp> ]
OK
+SKSATE=? OK

Parameters

<satCmd> String type; SIM application toolkit command (hexadecimal

format; refer +CSCS) in SIM expected format
<satRsp> String type; SIM application toolkit response (hexadecimal
format; refer +CSCS)
<Status word> String type; It is two byte word and coded in HEX format

Examples

Commands Possible Responses Description

AT+SKSATC=1, 1 OK Enabled SAT URCs

AT+SKSATE=”D607 +SKSATE: “9000” Mmi sends idle screen event to SIM.
19010582020281” OK
7.4 +SKSATR Send Terminal Response
+SKSATR Send Terminal Response Command
This command provides the response to a previous received SAT command, which
was passed to the TE with +SKSATI: <satCmd>. The coding of the response is the
responsibility of the TE. As soon as a response from the SIM is received for terminal
response, the status word would be sent to ME using the result +SKSATR: <status
word>

Syntax Description

+SKSATR: <status word>

OK
+SKSATR=<satRsp> +CME ERROR: <err_id> (If the
modem is received the +SKSATR
when it is in unexpected state )
+SKSATR=? OK

Parameters

<satRsp> String type; SIM application toolkit response (hexadecimal

format; refer +CSCS) starting with the first byte of response
data.
<Status word> String type; It is two byte word and coded in HEX format

Examples

Commands Possible Responses Description

AT+SKSATC=1, 1 OK Enable SAT URC

AT+SKCCS=1 OK Enable URC for current call status
+SKSATI: Setup Menu proactive command
“D0818481030125008202
8182850D80884C52D552A
0503C670D52D98F0E0180
0038003500304FDD8B776
0A88F0C0280751F6D3B5B
8560254FBF8F0A0380884
C52D55B5751788F0C0480
767C96FB5B5090F54EF68
F0C0580807D80A1796888
4C60C58F0C0680770B80A
17968884C60C58F0A0780
8A9E97F34FE17BB18F0A0
 8805BA2670D5C087DDA”
AT+SKSATR=”8103 +SKSATR: “9000” MMI is sending terminal response to
0125008202828183 OK SIM
0100”
AT+SKSATE=”D307 +SKSATE: “9000” User triggers menu selection; SIM
82028281900101” OK accepts envelope.

+SKSATN: Setup call proactive command

“D0178103011000820281 notification (calling number 2143
838507804FDD8B7760A88 and type address 81)
603811234”
+SKSATV: , Modem is sending the call control
“D40C8202828186 envelope to SIM
03811234”
+SKSATV: “9000” Call is allowed without any
modification
+SKSATS: 0,1
+SKSATA Alerting user to accept the call
AT+SKSATA +SKCCSI:1,2,2,0,0,,”2143 User accepts, dialing setup call
”,81
+SKCCSI:1,2,3,0,0,,”2143 Called party is altered
”, 81
+SKCCSI:1,2,0,0,0,,”2143 Call got connected
”, 81
+SKSATN: Terminal response was sent to SIM
“8131101228281310” after call got connected
+SKCCSI: Call is disconnected by called party
1,2,6,0,0,16,”2143”,81
NO CARRIER
7.5 +SKSATA SAT call accept
+SKSATA SAT call Accept
If SIM Application attempts to establish a call, it will send a Set Up Call proactive
command. After Modem receives this command, the Modem indicates that a call
is waiting to be established using “+SKSATA:”. The +SKSATA AT command is
issued when the user accepts establishment of this SAT call.

Syntax Description

+SKSATA OK

Parameters
None

Examples

Commands Possible Responses Description

AT+SKCCS=1 OK Enable URCs to get the current call

status events
AT+SKSATC=1,1 OK Enable all SAT URCs
+SKSATN: Setup call proactive command
“D0178103011000820281 notification (calling number 2143
838507804FDD8B7760A88 and type address 81)
603811234”
+SKSATV: , Modem is sending the call control
“D40C8202828186038112 envelope to SIM
34”
+SKSATV: “9000” Call is allowed without any
modification
+SKSATS: 0,1
+SKSATA Alerting user to accept the call
AT+SKSATA MMI is accepted that call
+SKCCSI:1,2,2,0,0,,”2143 Dialing setup call
”,81
+SKCCSI:1,2,3,0,0,,”2143 Called party is altered
”, 81
+SKCCSI:1,2,0,0,0,,”2143 Call got connected
”, 81
+SKSATN: Terminal response was sent to SIM
“8131101228281310” after call got connected
OK
+SKCCSI: Call is disconnected by called party
1,2,6,0,0,16,”2143”,81
NO CARRIER
7.6 +SKSATH SAT call reject
+SKSATH SAT call reject
If SIM Application attempts to establish a call, it will send a Set Up Call proactive
command. After Modem receive this command, the Modem indicates that a call
is waiting to be established using “+SKSATA”. The +SKSATH AT command is used
to reject this SAT call with a cause value determined by the MMI (e.g. user
rejected, call not possible because call already active, …).

Syntax Description

+SKSATH=<cause> OK

Parameters

<cause> String type; Refer the section 12.12 from 3GPP 11.14 for these
cause values
Examples

Commands Possible Responses Description

AT+SKCCS=1 OK Enable URCs to get the current call

status events
AT+SKSATC=1,1 OK Enable all SAT URCs
+SKSATN: Setup call proactive command
“D017810301100082028 notification (calling number 2143 and
1838507804FDD8B7760 type address 81)
A88603811234”
+SKSATV: ,“D40C82028 Modem is sending the call control
281860 3811234” envelope to SIM
+SKSATV: “9000” Call is allowed without any
modification
+SKSATS: 0,1
+SKSATA Alerting user to accept the call
AT+SKSATH=”22” +SKSATN: Call is rejected by user; indication of
“8103011012028281830 terminal response sent to SIM
122”
OK
 8 ME Personalization
8.1 +SKMEPERS Activate/Deactivate Personalization

+SKMEPERS Activate/Deactivate Personalization

This AT command is used to activate and deactivate the ME personalisation for
given category. Command supports set read and test modes.

Syntax Description

+SKMEPERS=<mode>, <pers_type>, Error

<pers_key>[, <code_entry_mode>[,
<code_group(s)>]]
+SKMEPERS? +SKMEPERS<pers_types activated>
+SKMEPERS=? +SKMEPERS:<modes supported>,
<pers_types supported>, <pers_key
lengths>, <code_entry_modes
supported>, <code_group lengths>

Parameters

Mode 0 – deactivate ME personalisation

1 - activate ME personalisation
Pers_type 0 - Network personalisation
1 - Network subset personalisation
2 - Service Provider personalisation
3 - Corporate personalisation
4 - (U) SIM personalisation
5 – Market personalisation
Pers_key 16 digits length (Minimum 6 digits for (U) SIM personalisation
and 8 digits for other personalisations and maximum is 16
digits)
Code_entry_mode 0 - CODE_FROM_APP
1 – CODE_FROM_SIM
2 - CODE_FROM_SIM_CNL
Code_group MCC + MNC – for Network personalisation
MCC+MNC + 6&7 digits of IMSI –
For Network Subset personalisation
MCC+MNC+SP code in GID1 –
For Service Provider personalisation
MCC+MNC+SP code in GID1+Corporate code in GID2 –
For Corporate personalisation
IMSI – for (U)SIM personalisation
Market code in GID3 – For Market personalisation
Examples

Commands Possible Responses Description

AT+SKMEPERS=1,0 OK NW personalization through

,”12345678”, application is activated for code
0,”123456,342367 groups 123456 and 342367 giving the
” personalization key 12345678 (
Each Time you Personalize ensure
that personalization for that
category is off)
Error If the personalization indicator is
already on, (or) the key that you
have entered should be unique (i.e.
each category should have unique
key).
Error If any other personalization
category with lower priority (such as
NW Subset or SP or CP or SIM ) is
already activated then the NW
personalization cannot be activated.
AT+SKMEPERS=0,0 OK NW personalization through
,”12345678” application is deactivated for all
code groups giving the
personalization key 12345678.
(If the Personalization Key does not
match and the category is already
personalized, it checks for
maximum 3 times and then goes to
blocked state).

Error When the key does not match with

the key you have given

AT+SKMEPERS? +SKMEPERS: 4 Decimal value. SP personalization

OK type is only activated and the rest
are not activated.
8.2 +SKPERSSTAT Query Personalization Status
+SKPERSSTAT Query Personalization Status
This AT command is used to enquire the status of ME personalisation for a given
category.

Syntax Description

AT+SKPERSSTAT=<pers_type>,<pers_key> +SKPERSSTAT=<pers_type>,<no_of_co
de_groups>,<code_group(s)>
AT+SKPERSSTAT=? +SKPERSSTAT=<pers_types
supported>, <pers_key lengths>

Parameters

Pers_type 0 - Network personalisation

1 - Network subset personalisation
2 - Service Provider personalisation
3 - Corporate personalisation
4 - (U) SIM personalisation
5- Market Personalisation
Pers_key 16 digits length (Minimum 6 digits for (U) SIM personalisation
and 8 digits for other personalisations and maximum is 16
digits)
No_of_code_group Number of code group present for that particular Pers_type.
s
Code_group MCC + MNC – for Network personalisation
MCC+MNC + 6&7 digits of IMSI –
For Network Subset personalisation
MCC+MNC+SP code in GID1 –
For Service Provider personalisation
MCC+MNC+SP code in GID1+Corporate code in GID2 –
For Corporate personalisation
IMSI – for (U) SIM personalisation
Market code in GID3 - for market personalisation

Examples

Commands Possible Responses Description

AT+SKPERSSTAT=0 This command retrieves the values of

,”12345678” +SKPERSSTAT: 0,2, the category u have given, if it is
(123456, 342367) personalized it displays with all the
code groups to which it have been
personalized
+CMEERROR: If the category you are querying is
Personalization not personalized
deactivated
Error When it is personalized and incorrect
key is issued to query
(It checks for maximum 3 times and
then goes to blocked state)
AT+SKMEPERS=1,0, OK If we are trying to activate using the
”12345678”,0,”12 same code group repetitively then
345,12345” the code group is stored only once.
This can be verified by giving the
AT+SKPERSSTAT=0 +SKPERSSTAT: 0,1, status query as shown in the
,”12345678” (12345) example.
AT+SKMEPERS=1,5, OK Market personalization through
”12345678”, application is activated for code
0,”1234,3423” groups 1234 and 3423 giving the
personalization key 12345678 (
Each Time you Personalize ensure
that personalization for that
category is off, or subset is
personalized)

8.3 +SKPERSDIS Disable Personalization

+SKPERSDIS Disable Personalization

This AT command is used to disable ME personalisation for given category.
Command supports set, read and test modes.

Syntax Description

+SKPERSDIS=<mode>[,<pers_type>] Error
+SKPERSDIS? +SKPERSDIS: <value >

+SKPERSDIS=? +SKPERSDIS: <list of modes>, < list of

supported personalization types>

Parameters

Mode 0 – Disable anyone

1- Disable ALL
value decimal. Represents the bitmap of disabled personalizations. If
the bit is set to zero then the relevant personalization is
disabled.
Bit 0 - Network personalisation
Bit 1 - Network subset personalisation
Bit 2 - Service Provider personalisation
Bit 3 - Corporate personalisation
Bit 4 - (U) SIM personalisation
Bit 5 - Market personalisation
Pers_type 0 - Network personalisation
1 - Network subset personalisation
2 - Service Provider personalisation
3 - Corporate personalisation
4 - (U) SIM personalisation
5 – Market Personalisation
Examples

Commands Possible Responses Description

AT+SKPERSDIS=1 OK Disable all personalization’s, if they
are not personalized
Error Disabling when at least one of the
category is activated

AT+SKPERSDIS=0,0 OK Disable NW category if it is not

personalized
Error Disabling NW category when the
category is activated

AT+SKPERSDIS? +SKPERDIS: 1 NW subset personalization type is

OK only enabled and the rest are
disabled.

AT+SKPERSDIS=? +SKPERDIS: (0-1), (0-5) Range of values it supports

OK

8.4 +SKPERSUBLK Unblock Personalization

+SKPERSUBLK Unblock Personalization
This AT command is used to unblock ME personalisation for given category.
Command supports set and test modes.

Syntax Description

+SKPERSUBLK=<pers_type>, <pers_ublk_key> Error

+SKPERSUBLK=? +SKPERSUBLK: <pers_types
supported>, <pers_ublk_key lengths>

Parameters

Pers_type 0 - Network personalisation

1 - Network subset personalisation
2 - Service Provider personalisation
3 - Corporate personalisation
4 - (U)SIM personalisation
5 – Market Personalisation
Pers_ublk_key 16 digits length. This is super user key for the given
personalisation category.
Examples

Commands Possible Responses Description

AT+SKPERSUBLK=0 OK If Unblocking is successful or if the
,”12345678912345 category is not blocked
67”
Error If Unblocking is unsuccessful due to
incorrect super user key
8.5 +SKPERSVER Personalization Verification Status
+SKPERSVER (URC)
This command is used for enabling a URC to display the information to the
application that verification of ME personalisation has failed or ME has blocked for
particular personalisation category. URC is of format +SKPERSVERI: < Pers_type >, <
Cause >.

Syntax Description

+ SKPERSVER =<State> Error

+SKPERSVER? +SKPERSVER: <state>

+SKPERSVER=? +SKPERSVER: <supported states>

Parameters

State 0- Disable
1- Enable
Pers_type 0 - Network personalisation
1 - Network subset personalisation
2 - Service Provider personalisation
3 - Corporate personalisation
4 - (U) SIM personalisation
5 – Market Personalisation
Cause 0 – personalisation verification failed
1- ME blocked
Examples

Commands Possible Responses Description

AT+SKPERSVER=1 OK To enable the URC command

AT+CFUN=2 OK During SIM INSERT time

+SKPERSVERI:0, 0 personalization verification is done.
URC is given if the mcc + mnc of the
IMSI does not match with values that
are already personalized NW
personalization. Since
personalization has failed SIM
operations may not be permitted.

+SKPERSVERI:0, 1 When the check for personalization

key during querying,
depersonalization or overriding fails
for maximum attempts, URC is given
that the personalization category has
entered into blocked state
8.6 +SKPERSCPWD Personalization Password Change

+ SKPERSCPWD Personalization Password Change

This command is used to modify the password currently set for a particular category.

Syntax Description

+SKPERSCPWD=<pass_type>, <old-passwd>, +OK

<new-passwd > +CME ERROR
+SKPERSCPWD=? +SKPERSUBLK: <pers_types supported>, <pers passwd
length>, <pers passwd length>

Parameters

Pass_type “NP” - Network personalisation password

“NSP” - Network subset personalisation password
”SP” - Service Provider personalisation password
”CP” - Corporate personalisation password
”MP” – Market Personalisation password
“SU” – Superuser password

old-passwd Old password to be modified.

New-passwd New password to be set.

Examples

Commands Possible Responses Description

AT+SKPERSCPWD=" OK To modify Network personalisation

NP","abcd1234EFG password.
H1234","1z3456788
7654321"

AT+SKPERSCPWD=" +CME ERROR: incorrect Error in case of old password

NP","wxyz9999wxy password mismatch.
z1234","103456788
7654321"
 9 Dual-SIM Related AT Commands
9.1 +SKSIMSLT Select SIM for Channel

+SKSIMSLT Select SIM for Channel

This action command reserves a particular AT channel for the specified SIM Id.
Command supports set, read and test modes.

Syntax Description

AT+SKSIMSLT=<SIM Id> +CME ERROR: <err>

AT+SKSIMSLT? +SKSIMSLT: <SIM Id>
+CME ERROR: <err>
AT+SKSIMSLT=? +SKSIMSLT: list of supported (<SIM
Id>)s
+CME ERROR: <err>

Parameters

SIM Id 0 – Select SIM 0 (Default)

1 – Select SIM 1

Examples

Commands Possible Responses Description

AT+SKSIMSLT=? +SKSIMSLT: (0-1) TA responding with the supportable

OK values for test command
AT+SKSIMSLT=1 OK Current ATPP channel reserved for
SIM Id 1 (second SIM).
AT+SKSIMSLT=0 OK Current ATPP channel reserved for
SIM Id 0 (first SIM).
AT+SKSIMSLT? +SKSIMSLT: 0 Displays the SIM id for which the
OK current channel is reserved
9.2 +SKDSIMREG Dual-SIM Network Registration Status

+SKDSIMREG Dual-SIM Network Registration Status

This set command controls the presentation of an unsolicited result code

+SKDSIMREGI: <stat> [,<failure_type>] when enabled for a particular SIM. On
successful network registration, <stat> is displayed, while on failure, the
<failure_type> is displayed along with <stat>. Read command returns the status of
result code presentation. Test command returns the supported values.

Syntax Description

AT+SKDSIMREG=<n> CME ERROR: <err>

AT+SKDSIMREG? +SKDSIMREG: <n>

+CME ERROR: <err>
AT+SKDSIMREG=? +SKDSIMREG: (list of supported
<n>s)

Parameters

<n> Indicates the status of presentation

of the unsolicited result code for
Network Registration Status
0 Disabled
1 Enabled
<stat> Indicates the status of Network
Registration
Not registered, MT is not currently
0 searching a new operator to
register to
1 Registered, home network
<failure_type> Indicates the type of registration
failure
0 Temporary failure*
1 Permanent failure*

Limitation
This command is only supported in case of Dual SIM Master-Slave
feature support
Examples

Commands Possible Responses Description

OK Disables network registration
AT+SKDSIMREG=0

AT+CFUN=1 OK Protocol stack activated

AT+SKDSIMREG=1 OK Enables network registration

AT+CFUN=2 OK Master SIM activated
 +SKDSIMREGI: 1 Registration successful
AT+CFUN=2
OK Slave SIM activated

+SKDSIMREGI: 0, 1 Registration failed with

failure_type "permanent failure"

AT+SKDSIMREG? +SKDSIMREG: 1 Presentation of network

registration status enabled
OK

AT+SKDSIMREG=? +SKDSIMREG: (0-1) List of supported values

OK

* If the registration fails with LAU reject cause

1. IMSI_UNKNOWN_IN_HLR
2. ILLEGAL_MS
3. ILLEGAL_ME
Modem will indicate a permanent failure.
Modem will indicate temporary failure for all other causes including lower layer
failures.
9.3 +SKSIMMTR Set Master SIM

+SKSIMMTR Set Master SIM

This action command sets which of the 2 SIMs in a Dual SIM case is the Master SIM

Syntax Description

AT+SKSIMMTR=<SIM Id> +CME ERROR: <err>

AT+SKSIMMTR? +SKSIMMTR: <sim_id>
+CME ERROR: <err>
AT+SKSIMMTR=? +SKSIMMTR: list of supported ( <SIM
Id>)s
+CME ERROR: <err>

Parameters

SIM Id 0 – Select SIM 0 (Default)

1 – Select SIM 1

Limitation
This command is only supported in case of Dual SIM Master-
Slave feature support
Examples

Commands Possible Responses Description

AT+SKSIMMTR=? +SKSIMMTR: (0-1) TA responding with the supportable

OK values for test command
AT+SKSIMMTR=0 OK Set SIM Id 0 (first SIM) as Master
SIM.
 10 Miscellaneous AT Commands
10.1 +SKABORT Abortion of the AT Commands
+SKABORT Abortion of the AT Commands
It is used to abort any AT command, which is in execution mode. It returns +CME
ERROR: “at command aborted” and modem will ignore all subsequent responses,
which are coming for the command that was aborted. If modem gets the +SKABORT
when it is in unexpected state then it will send +CME ERROR: “Operation not
allowed”.
Abort is supported for the following AT commands:
Command Mode
+COPS All modes
+CLCK Set mode and only for call barring
related services
+CLIP Read mode
+COLP Read mode
+CCFC Set mode
+CCWA Set mode
+CHLD Set mode
+CMGS Set mode
+CMGC Set mode
+CMSS Set mode

Syntax Description

+SKABORT +CME ERROR: <err>

+SKABORT=? OK

Parameters

Examples

Commands Possible Responses Description

AT+CFUN=1 OK Protocol stack is activated

AT+COPS=? MS will start to scan and present
the PLMN list to TE
AT+SKABORT +CME ERROR: “at PLMN search is aborted and Modem
command aborted” will not present any list to ME
10.2 +SKICCID Read ICCID from SIM
+SKICCID Read ICCID from SIM

This is used to read the ICCID from SIM. It returns the 20 digit number

Syntax Description

+SKICCID +SKICCID: <20 digit number>

OK
+CME ERROR: <err> (if there is an
error)
+SKICCID=? OK

Parameters

Examples

Commands Possible Responses Description

AT+CFUN=1 OK Protocol stack is activated

AT+SKICCID +SKICCID:
“12345678901234567890
”
OK
10.3 +SKENR Enable for Engineering Mode Information

+SKENR Enable for engineering mode information

The execution command is used by TE to request automatic (periodic) engineering
information reports from MS through the +SKENRI:<task>,<msg_id>, <msg details>
unsolicited event. When set command is executed successfully, the engineering mode
information of the specified tasks is enabled and will be returned periodically (currently 5
seconds).
The read command returns the current command setting.
Test command returns supported values as a compound value.

Syntax Description

+SKENR =<task>[,<msg_id>[,flag]] OK
+CME ERROR: <err>
+SKENR? +SKENR: (<task_id1>,<msg_id> )[,
(<task_id2>,<msg_id> )
+SKENR: (<task_id1>,<list of supported
+SKENR=? msg_id> )[, (<task_id1>,< list of
supported msg_id> )

Parameters

<task> Sum of task_id as specified below:

0 Disable statistics for all tasks
1 RR
2 MM
3 GRR
4 GMM
5 LAPDm
6 LLC
7 SNDCP
8 CSD
9 SMS
10 SIM
11 CC
12 TICL
13 ATPP
14 GMR2P_RR
15 GMR2P_MM
16 GMR2P_LAPDM
17 GMR2P_CSD
18 GMR2P_SMS
19 GMR2P_CC
20 KAL
<msg_id> Integer represents the specific type of information. These messages ID are
unique within that task. It gives the flexibility to enable combination of
message within the same task by sending single AT command.

0 it will be used to disable all message for specified task

RR task:
1 Serving cell system information (RR)
2 Neighbor cell system information (RR)
4 Serving cell reselection system information (RR)
8 Channel Status information (RR)
16 Idle channel information (RR)
32 CBCH status information (RR)
64 Dedicated channel information (RR)
128 Serving cell radio information (RR)
256 Neighbor cell radio information (RR)
512 Reselection counter information (RR)
1024 Handover counter information (RR)

GRR task:
1 GPRS system information (GRR)
2 GPRS packet channel system information (GRR)
4 GPRS serving cell reselection system information (GRR)
8 GPRS neighbor cell reselection system information (GRR)
16 TBF information (GRR)
32 BF establishment information (GRR)
64 RLC information (GRR)

LAPDm task:
1 LAPDm information (LAPDm)

MM taks:
1 Location information (MM)
2 State information (MM)
4 Counter information (MM)

GMM task:
1 Location information (GMM)
2 State information (GMM)
4 Counter information (GMM)

CC task:
1 Status information (CC)

LLC task:
1 Status information (LLC)
2 SAPI information (LLC)

SNDCP task:
1 PDP state information (SNDCP)
2 NSAPI information (SNDCP)

CSD task:
1 Status information (CSD)

SIM task:
1 Status information (SIM)

SMS task:
1 Status information (SMS)

1 Port Information (TICL)

1 PPP Information (TICL)
 ATPP Task:
1 ATPP channel status information(ATPP)

GMR2P_RR task:
1 Serving spotbeam system information(GMR2P_RR)
2 Neighbor spotbeam system information (GMR2P_RR)
4 GMR2P_RR status information(GMR2P_RR)
8 GPS information (GMR2P_RR)
16 Dedicated channel information (GMR2P_RR)
32 Serving spotbeam radio information(GMR2P_RR)
64 Neighboring spotbeam radio information (GMR2P_RR)
128 Serving spotbeam reselect counter information (GMR2P_RR)
256 Serving spotbeam network information (GMR2P_RR)
512 RBCCH list information (GMR2P_RR)
1024 CSRR status information(GMR2P_RR)

GMR2P_MM task:
1 Location information(GMR2P_MM)
2 MM state information (GMR2P_MM)
4 MM counter(GMR2P_MM)
8 PH status information(GMR2P_MM)

GMR2P_LAPDM task:
1 LAPDM status information(GMR2P_LAPDM)

GMR2P_CSDtask:
1 CSD status information(GMR2P_CSD)

GMR2P_SMS task:
1 SMS status information(GMR2P_SMS)

GMR2P_CC task:
1 CC status information(GMR2P_CC)

1 Task Information (KAL)

2 Queue Information (KAL)
4 Semaphore Information (KAL)
8 Buffer Status Information (KAL)
Flag Enable or disable reports for a specific msg_id
Disable
Enable (default)
serving cell <serv_cell_bcch_arfcn>,<serv_cell_ci>,<serv_cell_lac>,<serv_sys_info_cell_
system priority>,<serv_sys_info_max_retx>,<serv_sys_info_reest>,<serv_sys_info_
information max_txpwr>,<serv_sys_info_rxlev_min>,<serv_sys_info_page_mode>,<serv_
(RR) cell_gprs_supp>,<serv_cell_mcc_mnc>,<serv_cell_rac>,<serv_sys_info_pg_
mode>
neighbor
<num_cells>[,<id_1>,<neigh_1_arfcn>,<neigh_1_lac>,<neigh_1_cell_prio>,<
cell system
neigh_1_max_txpwr>,<neigh_1_rxlev_min>,<neigh_1_gprs_supp>,<neigh_1
information
_ra_color>[,
(RR)
Serving cell <serv_sys_info_resel_offset>,<serv_sys_info_temp_offset>,<serv_sys_info_
reselection penalty_tmr>,<serv_sys_info_cell_priority>,<serv_sys_info_ecsc>,<serv_sys
system _info_si_7_8>,<serv_sys_info_si_2ter>,<serv__sys_info_multiband_rep>,<se
information rv_sys_info_emer_call_supp>,<serv_sys_info_pag_pd>,<serv_sys_info_dtx_i
(RR) nd>,<serv_sys_info_t3212_timeout>,<serv_cell_cbch_supp>,<serv_cell_imsi
_att>,<serv_cell_mscr>,<serv_cell_sgsnr>
Channel
Status
<gprs_curr_chan_monitored>,<gprs_mob_info_gprs_att_pdp>
information
(RR)
Idle channel
information <chan_num>, <tn>,<dsc>,<ccch_conf>
(RR)
CBCH status
<CBCH_stat>,<ch_type>,<tn>,<tsc>,<hopping>,{<arfcn>(hopping=0)}/
information
{<maio>,<hsn>,<ma_num>,] (hopping=1)}
(RR)
Dedicated <ch_type>,<tn>,<tsc>,<serv_cell_ch_hopp>,
channel {<serv_cell_ch_curr_carrier>(serv_cell_ch_hopp=0)}/
information {<serv_cell_maio>,<serv_cell_ch_hsn>,
(RR) (serv_cell_ch_hopp=1)},<serv_cell_ch_power>,<serv_cell_ch_dtx>,<serv_ce
ll_ch_tav>,<serv_cell_pwrc>,<serv_cell_ch_mode>,<serv_cell_ch_rxlev_f>,
<serv_cell_ch_rxlev_s>,<serv_cell_ch_rxqual>,<serv_cell_rxqual_s>,<serv_c
ell_ch_radio_link_tmout>,<serv_cell_ch_ciph>

Note that <serv_cell_ch_hopp> is used to determine whether

[,<serv_cell_ch_maio>,<serv_cell_ch_hsn>,…..] or
<serv_cell_ch_curr_carrier> exits
Serving cell <serv_cell_bcch_arfcn>,<serv_cell_band>,<serv_cell_c1>,<serv_cell_c2>,<s
radio erv_cell_rxlev>,<serv_cell_bsic>,<serv_cell_ci>,<serv_cell_lac>,<serv_cell_
information mcc_mnc>,<serv_cell_dsc>,<serv_cell_c31><serv_cell_c32>,
(RR) <serv_cell_num_sync_fail>
Neighbor
<num_cells>[,<id_1>,<neigh_1_arfcn>,<neigh_1_curr_band>,<neigh_1_c1>,
cell radio
<neigh_1_c2>,<neigh_1_rxlev>,<neigh_1_bsic>,<neigh_1_lac>,<neigh_1_mc
information
c_mnc>,<neigh_1_c31>,<neigh_1_c32>, <neigh_1_num_sync_fail>
(RR)
Reselection <num_cell_sel_attempts>,<num_cell_sel_fail_900>,<num_cell_sel_fail_180
counter 0>,<num_cell_resel>,<num_cell_resel_900_900>,<num_cell_resel_900_1800
information >,<num_cell_resel_1800_1800>,<num_cell_resel_1800_900>,<num_cell_sel
(RR) _sync_900_attempts>,<num_cell_sel_sync_1800_attempts>
Handover <num_gsm_gsm_inter_succ_900_900>,<num_gsm_gsm_inter_ho_succ_900_
counter 1800>,<num_gsm_gsm_inter_ho_succ_1800_900>,<num_gsm_gsm_inter_ho
information _succ_1800_1800>,<num_gsm_gsm_inter_ho_fail_900_900>,<num_gsm_gsm
(RR) _inter_ho_fail_900_1800>,<num_gsm_gsm_inter_ho_fail_1800_900>,<num_
gsm_gsm_inter_ho_fail_1800_1800>,<num_gsm_gsm_inter_ho_succ_prev_9
00_900>,<num_gsm_gsm_inter_ho_succ_prev_900_1800>,<num_gsm_gsm_i
nter_ho_succ_prev_1800_900>,<num_gsm_gsm_inter_ho_succ_prev_1800_1
800>,<num_gsm_gsm_intra_ho_succ_900_900>,<num_gsm_gsm_intra_ho_su
cc_900_1800>,<num_gsm_gsm_intra_ho_succ_1800_900>,<num_gsm_gsm_i
ntra_ho_succ_1800_1800>,<num_gsm_gsm_intra_ho_fail_900_900>,<num_g
sm_gsm_intra_ho_fail_900_1800>,<num_gsm_gsm_intra_ho_fail_1800_900>
,<num_gsm_gsm_intra_ho_fail_1800_1800>,<num_gsm_gsm_intra_ho_succ_
prev_900_900>,<num_gsm_gsm_intra_ho_succ_prev_900_1800>,<num_gsm
_gsm_intra_ho_succ_prev_1800_900>,<
num_gsm_gsm_intra_ho_succ_prev_1800_1800>
GPRS system <gprs_sys_info_ctrl_ack_type>,<gprs_sys_info_acc_burst_type>,<gprs_sys_i
information nfo_drx_tmr_max>,<gprs_sys_info_pg_mode>,<gprs_sys_info_nco>,<gprs_s
(GRR) ys_info_nmo>,<
gprs_sys_info_spgc_supp>,<gprs_sys_info_si13_pos>,<gprs_sys_info_t3168>,
<gprs_sys_info_t3192>,<gprs_sys_info_bs_cv_max>,<gprs_sys_info_pan_ma
 x>,<gprs_sys_info_pan_inc>,<gprs_sys_info_pan_dec>
GPRS packet <gprs_pbcch_blks>,<gprs_psi1_rpt_pd>,<gprs_prach_blks_res>,<gprs_pag_b
channel lks_res>,<gprs_prach_max_retx>,<gprs_pcc_rel>,<gprs_count_hr>,<gprs_co
system unt_lr>,<gprs_psi_ind>,<gprs_psi5_avail>,<gprs_pbcch_hopp>,
information {gprs_pbcch_carrier(gprs_pbcch_hopp=0)/
(GRR) (pbcch_hopp=1)},<gprs_pccch_hopp>,
{gprs_pccch_carrier(gprs_pccch_hopp=0)/ (gprs_pccch_hopp=1)}

Note that gprs_pbcch_carrier is present only when gprs_pbcch_hopp is 0,

gprs_pccch_carrier is present only when gprs_pccch_hopp is 0
GPRS
serving cell
<gprs_sys_info_rxlev_min>,<gprs_sys_info_txpwr_max>,<gprs_sys_info_cell
reselection
_resel_hyst>,<gprs_sys_info_ra_hyst>,<gprs_sys_info_c31_hyst>,<gprs_sys_i
system
nfo_c32_qual>,<gprs_sys_info_t_resel>
information
(GRR)
GPRS
neighbor
cell <num_cells>[,<id_1>,<gprs_neigh_1_same_ra_as_serv_cell>,<gprs_neigh_1_
reselection cba2>,<gprs_neigh_1_exc_acc>[,<id_2>,<gprs_neigh_2_same_ra_as_serv_c
system ell>,<gprs_neigh_2_cba2>,<gprs_neigh_2_exc_acc> […]]]
information
(GRR)
TBF <gprs_tbf_hopp>,{<gprs_tbf_carrier>(gprs_tbf_hopp=0)}/
information { (gprs_tbf_hopp=1)},<gprs_tbf_dl_slots>,<gprs_tbf_ul_slots>,<gprs_tbf_dl_
(GRR) cs>,<gprs_tbf_ul_cs>,<gprs_tbf_direction>,<gprs_tbf_timing_adv>,<gprs_tb
f_tai>,<gprs_tbf_dl_tfi>,<gprs_tbf_ul_tfi>,<gprs_tbf_mac_mode>,<gprs_tbf
_usf_1>,<gprs_tbf_usf_2>,<gprs_tbf_usf_3>,<gprs_tbf_usf_4>,<gprs_tbf_dl_
start_fn>,<gprs_tbf_ul_start_fn>,<gprs_tbf_dl_end_fn>,<gprs_tbf_ul_end_f
n>
TBF
establishme <gprs_tbf_est_cause>,<gprs_tbf_est_rach_type>,<gprs_tbf_est_res>,<gprs_
nt tbf_est_phase_used_by_nw>,<gprs_tbf_est_radio_priority>,<gprs_tbf_est_r
information lc_octets>, <gprs_tbf_est_rach_type> , <gprs_tbf_est_num_rach_fail>
(GRR)
RLC <gprs_rlc_mode>,<gprs_rlc_n3102>,<gprs_rlc_tbf_mode>,<gprs_rlc_num_bl
information ks_sent>,<gprs_rlc_num_blks_rcvd>,<gprs_rlc_num_blks_missed>,<gprs_rlc
(GRR) _num_blks_retx>,<gprs_rlc_ul_thpt>,<gprs_rlc_dl_thpt>
LAPDm
<num_lapdm_t200_timeout_900>,<num_lapdm_t200_timeout_1800>,<num
information
_lapdm_t200_rcvd_retx_900>,<num_lapdm_t200_rcvd_retx_1800_1900>
(LAPDm)
Location
information <serv_cell_mcc_mnc>,<serv_cell_lac>,<reg_mcc_mnc>,<reg_lac>
(MM)
State <mm_state>,<mm_reg_state>,<gprs_cm_est_state>,<reg_type>,<update_st
information atus>,<lu_type>,<idle_substate>,<rej_cause>,<prev_rej_cause>,<limited_c
(MM) ause>,<is_cm_req_pending >
Counter
<loc_up_fail_cause>,<loc_up_num_attempts>,<loc_up_succ_attempts>,<im
information
si_att_fail_cause>,<imsi_att_num_attempts>,<imsi_att_succ_attempts>
(MM)
Location <serv_cell_mcc_mnc>,<serv_cell_lac>,<serv_cell_rac>,<gprs_sys_info_nmo
information >,<gmm_cell_changed>,<gmm_plmn_forbidden>,<gmm_la_forbidden>,<gm
(GMM) m_old_cell_mcc_mnc>,<gmm_old_cell_lac>,<gmm_old_cell_rac>,<gmm_ol
d_cell_nmo>,<gmm_old_cell_changed>,<gmm_old_cell_plmn_forbidden>,<
gmm_old_cell_la_forbidden>,<gmm_reg_mcc_mnc>,<gmm_reg_lac>,<gmm
 _reg_rac>
State <gmm_state>,<gmm_plmn_sel_mode>,<gmm_ms_class>,<gmm_attach_typ
information e>,<gmm_update_status>,<gmm_attach_attempt_count>,<combine_attach
(GMM) ed>,<gmm_ciph_algo>,<gmm_cksn>,<sim_gprs_invalid>,<llgmm_resume_se
nt>,<gmm_recov_from_non_gprs_cell>,<gmm_spgc_code>,<gmm_non_drx_
tmr>,<gmm_sms_priority>,<gmm_ready_timeout_val>,<ready_timer_status
>,<gmm_rau_tmr>,<gmm_ptmsi>
Counter <ra_up_fail_cause>,<ra_up_num_attempts>,<ra_up_succ_attempts>,<gprs_
information att_fail_cause>,<gprs_att_num_attempts>,<gprsatt_num_succ_attempts>,<
(GMM) comb_att_num_attempts>,<comb_att_num_succ_attempts>,<comb_att_nu
m_attempts>,<comb_att_num_succ_attempts>,<comb_ra_up_num_attemp
ts>,<comb_ra_up_num_succ_attempts>,<cell_update_num_attempts>
Status <call_rel_cause>,<call_rel_direc>,<call_num_mo_attempts>,<call_num_mo
information _succ_attempts>,<call_num_mt_attempts>,<call_num_mt_succ_attempts>,
(CC) <ss_num_attempts>,<ss_num_succ_attempts>,<ss_result_code>,<cc_call_cl
ear_cause>,<mm_call_clear_cause>,<rr_call_clear_cause>
Status <gprs_llc_num_sig_pdus_sent>,<gprs_llc_num_sig_pdus_rcvd>,<gprs_llc_gp
information rs_kc1>,<gprs_llc_gprs_kc2>,<gprs_llc_iov_ui>,<gprs_llc_num_reset_rcvd>,
(LLC) <gprs_llc_ciphering_on_off>
SAPI <num_sapis>[,<gprs_llc_sapi_id_1>,<gprs_llc_sapi_1_num_ui_pdus_sent>,<
information gprs_llc_sapi_1_num_ui_pdus_rcvd>,<gprs_llc_sapi_1_num_I_pdu_sent>,<g
(LLC) prs_llc_sapi_1_num_I_pdu_rcvd>,<gprs_llc_sapi_1_num_I_pdu_retx>,<gprs_
llc_sapi_1_pdu_rcvd_in_err>,<gprs_llc_sapi_1_oc_count_for_I_ul>,<gprs_llc
_sapi_1_oc_count_for_i_dl_0>,<gprs_llc_sapi_1_oc_count_for_ui_ul>,<gprs
_llc_sapi_1_oc_count_for_ui_dl>,<gprs_llc_sapi_1_n201_I>,<gprs_llc_sapi_1
_n201_u>,<gprs_llc_sapi_1_t200>,<gprs_llc_sapi_1_n200>,<gprs_llc_sapi_1
_kd>,<gprs_llc_sapi_1_ku>,<gprs_llc_sapi_1_md>,<gprs_llc_sapi_1_mu>[,<g
prs_llc_sapi_id_2>,<gprs_llc_sapi_2_num_ui_pdus_sent>,<gprs_llc_sapi_2_n
um_ui_pdus_rcvd>,<gprs_llc_sapi_2_num_I_pdu_sent>,<gprs_llc_sapi_2_nu
m_I_pdu_rcvd>,<gprs_llc_sapi_2_num_I_pdu_retx>,<gprs_llc_sapi_2_pdu_r
cvd_in_err>,<gprs_llc_sapi_2_oc_count_for_I_ul>,<gprs_llc_sapi_2_oc_coun
t_for_i_dl_0>,<gprs_llc_sapi_2_oc_count_for_ui_ul>,<gprs_llc_sapi_2_oc_c
ount_for_ui_dl>,<gprs_llc_sapi_2_n201_I>,<gprs_llc_sapi_2_n201_u>,<gprs_
llc_sapi_2_t200>,<gprs_llc_sapi_2_n200>,<gprs_llc_sapi_2_kd>,<gprs_llc_sa
pi_2_ku>,<gprs_llc_sapi_2_md>,<gprs_llc_sapi_2_mu> [,…]]
PDP state <num_pdps>[,<id_1>,<gprs_pdp_cntxt_1_nsapi>,<gprs_pdp_cntxt_1_sapi>,
information <gprs_pdp_cntxt_1_rel_class>,<gprs_pdp_cntxt_1_prec_class>,<gprs_pdp_c
(SNDCP) ntxt_1_del_class>,<gprs_pdp_cntxt_1_pk_thrpt>,<gprs_pdp_cntxt_1_mn_th
rpt>,<gprs_pdp_cntxt_1_rad_prio>,<gprs_pdp_cntxt_1_pdp_addr>,<gprs_p
dp_cntxt_1_act_direc>[,<id_2>,<gprs_pdp_cntxt_2_nsapi>,<gprs_pdp_cntxt
_2_sapi>,<gprs_pdp_cntxt_2_rel_class>,<gprs_pdp_cntxt_2_prec_class>,<g
prs_pdp_cntxt_2_del_class>,<gprs_pdp_cntxt_2_pk_thrpt>,<gprs_pdp_cntx
t_2_mn_thrpt>,<gprs_pdp_cntxt_2_rad_prio>,<gprs_pdp_cntxt_2_pdp_addr
>,<gprs_pdp_cntxt_2_act_direc>[,…]]]
NSAPI <num_nsapis>,
information [<id_1>,<gprs_sndcp_nsapi_1_num_npdus_sent>,<gprs_sndcp_nsapi_1_num
(SNDCP) _npdus_rcvd>,<gprs_sndcp_nsapi_1_num_npdus_retx>,<gprs_sndcp_nsapi_1
_num_npdus_discard>,<gprs_sndcp_nsapi_1_pcomp>,<gprs_sndcp_nsapi_1_
dcomp>[,<id_2>,<gprs_sndcp_nsapi_2_num_npdus_sent>,<gprs_sndcp_nsap
i_2_num_npdus_rcvd>,<gprs_sndcp_nsapi_2_num_npdus_retx>,<gprs_sndcp
_nsapi_2_num_npdus_discard>,<gprs_sndcp_nsapi_2_pcomp>,<gprs_sndcp_
nsapi_2_dcomp>[,…]]]
Status
<num_fa_calls>,<num_t_calls>,<num_nt_calls>,<version_num>,<uplink_wsi
information
ze>,<downlink_wsize>,<ack_tmr>,<retrans_attempts>,<is_ch_up_allowed>
(CSD)
Status <mo_sms_fail_cause>,<mo_sms_attempts>,<mo_sms_succ_attempts>,<mt_
information sms_fail_cause>,<mt_sms_attempts>,<mt_sms_succ_attempts>,<smscb_sch
(SMS) d_msg_rcvd>,<num_tc1m_timeout>,<num_tc2m_timeout>,<num_tr1m_tim
eout>,<num_tr2m_timeout>,<num_tram_timeout>,<num_smscb_schd_time
out>
Status <sim_pin_1_num_ver_attempts_left>,<sim_pin_1_num_unblk_atttempts_le
information ft>,<sim_pin_2_num_ver_attempts_left>,<sim_pin_2_num_unblk_attempts
(SIM) _left>,<sim_sst_1>,<sim_sst_2>,<sim_sst_3>
Port <num_ports>[,<port_id_1>,<chan_state_1>,<call_type_1>,<tx_bytes_1>,<rx
Information _bytes
(TICL) _1>[,<port_id_2>,<chan_state_2>,<call_type_2>,<tx_bytes_2>,<rx_bytes_2
> [,…]]]
PPP <num_ppp_inst>[,<port_id_1>,<lcp_state_1>,<ipcp_state_1>,<async_map_1
Information >,<auth_proto>,<comp_params_1>,<mru_1>,<ul_bytes>,<dl_bytes>[,<port_
(TICL) id_2>,<lcp_state_1>,<ipcp_state_1>,<async_map_1>,<auth_proto>,<comp_
params_1>,<mru_1>,<ul_bytes>,<dl_bytes> [,…]]]
ATPP
channel [[<is_channel_active>,<atpp_channel_1_state>,<atpp_
status channel_1_substate>,< channel_1_is_cmd_present>,<
information( channel_1_cmd_code>,< channel_1_cmd_mode>]…],<stack_mode>
ATPP)
Serving
<page_mode>,<max_rach_retx>,<rxlev_min>,<max_txpwr>,<resel_offset>,
spotbeam
<temp_offset>,<penalty_tmr>,<spotbeam_priority>,<emer_call_supp>,<dtx
system
_ind>,<t3212_timeout>,<gps_reqd>,<gps_mmi_cntrl>,<gps_upd_tmr>,<is_n
information(
cc_permited>,<acc_cntl_class_n>
GMR2P_RR)
Neighbor <no_of_nbr_spotbeams>,
spotbeam [[<nbr_1_spotbeam_mcc_mnc>,<nbr_1_spotbeam_priority>,<nbr_1_spotbe
system am_lac>,<nbr_1_spotbeam_max_txpwr>,<nbr_1_spotbeam_rxlev_min>,<nb
information r_1_spotbeam_resel_offset>,<nbr_1_spotbeam_temp_offset>,<nbr_1_spotb
(GMR2P_RR) eam_penalty_timer>]
[<nbr_2_spotbeam_mcc_mnc>,<nbr_2_spotbeam_priority>,<nbr_2_spotbea
m_lac>,<nbr_2_spotbeam_max_txpwr>,<nbr_2_spotbeam_rxlev_min>,<nbr
_2_spotbeam_resel_offset>,<nbr_2_spotbeam_temp_offset>,<nbr_2_spotb
eam_penalty_timer>]…]
GMR2P_RR <rmc_state>,<rrm_state>,<csrr_state>,<is_background_proc_going_on>,<gp
status s_state>,<is_t3122_emr_timr_running>,<is_cell_test_mode>,<is_30sec_tmr
information _running>,<sim_nvm_sync_flag>
Dedicated
<curr_carrier>,<ch_mode>,<ch_type>,<ch_fwd_timeslot>,,<ch_retn_timesl
channel
ot>,<ch_dtx>,<ch_fed>,<ch_radio_link_timeout>,<ch_rx_equal>,<ch_ciph>,
information
<ch_rxlev>,<ch_power>,<ch_pwrc>,<ch_tav>,<ch_rxequal>
(GMR2P_RR)
Serving
spotbeam <bcch_larfcn>,<rxlev>,<sbic>,<c1>,<c2>,<dlc>,<num_sync_fail>,<spotbeam
radio _type>,<freq_offset_ncch_type>,<channel_offset>,<fsg>,<extended_carrier
information( _arfcn>,<extended_carrier_fo>,<gps_pos_valid>
GMR2P_RR)
Neighboring
spotbeam <no_of_nbr_spotbeams>,[[<nbr_1_larfcn>,< nbr_1_freq_offset>,<
radio nbr_1_co>,< nbr_1_ fsg>,< nbr_1_sbic>,< nbr_1_rxlev>,< nbr_1_c1>,<
information nbr_1_c2>,<num_sync_fail>]….]
(GMR2P_RR)
Serving <sel_attempts_rb>,<sel_fail_rb>,<sel_attempts_nb>,<sel_fail_nb>,<resel_n
spotbeam b>,<no_of_cell_sel_req>,<cause_for_last_cell_sel_req>,<no_of_la_not_allo
reselect wed_cells>,<no_of_roaming_not_allowed_cells>,
counter
information [<la_not_allowed_plmn_id>,<roaming_not_allowed_plmn_id>…]
(GMR2P_RR)
Serving
spotbeam
network <mcc_mnc>,<lac>,<sbi>,<mscr>
information
(GMR2P_RR)
RBCCH list <is_si2_read_from_sim>,<num_of_stored_rbcch_info_vaild>,
information [[<rbcch_version_id>,<rbcch_plmn_id>,<rbcch_index>,<rbcch_index1>,<ru
(GMR2P_RR) m_rbcch_freq_store>,
[[<rbcch_freq_list_store_arfcn>,<rbcch_freq_list_store_fo_ext>…]]]….]
CSRR status <csrr_state>,<call_est_cause>,<cipher_mode>,<cipher_algo>,<cipher_key>,
information( <channel_release”_cause>,<channel_rel_t3122a_value>,<channel_rel_dista
GMR2P_RR) nce>,<dedicated_mode_command>,<assignment_cmd_ch_type>,<assignme
nt_cmd_ch_mode>
Location
information( <mm_reg_mcc_mnc>,<mm_reg_lac>
GMR2P_MM)
MM state <mm_state>,<mm_reg_state>,<mm_update_status>,<mm_lu_type>,<mm_r
information ej_cause>,<mm_prev_rej_cause>,<mm_limited_cause>,<mm_is_cm_req_pe
(GMR2P_MM) nding>,<sim_acc_cntrl_class>
MM
<loc_up_fail_cause>,<loc_up_num_attempts>,<loc_up_num_succ_attempts
counter(GM
>,<num_lr_req_failed_la_not_allowed>
R2P_MM)
PH status
<num_hplm_search_done>,<num_plmn_not_allowed>,<num_change_in_pl
information(
mn>
GMR2P_MM)
LAPDM
status
information( <t200_timeout>,<t200_rcvd_retx>,<rlc_count_val>,<l2_conn_fail_cause>
GMR2P_LAP
DM)
CSD status
<tdt_state>,<async_flag>,<input_data_rate>,<data_size_for_480ms>,<activ
information(
ation_type>,<fa_state>
GMR2P_CSD)
SMS status <mo_sms_fail_cause>,<mo_sms_num_attempts>,<mo_sms_succ_sttempts>,
information( <mt_sms_fail_cause>,<mt_sms_num_attempts>,<mt_sms_succ_attempts>,
GMR2P_SMS) <num_TC1_attempts>,<num_TR1_attempts>,<num_TR2_attempts>,<num_T
RAM_attempts>
CC status <call_rel_dir>,<call_num_mo_attempts>,< call_num_mo_succ_attempts
information( >,<call_num_mt_attempts>,<call_num_mt_succ_attempts>,<ss_num_attem
GMR2P_CC) pts>,<ss_num_succ_attempts>,<ss_result_code>,<cc_call_clear_cause>,<m
m_call_clear_cause>,<rr_call_clear_cause>
Task <num_tasks>[,<task_id_1>,<task_state_1>,<task_priority_1>,<task_stack_m
Information ax_used_1>[,<task_id_2>,<task_state_2>,<task_priority_2>,<task_stack_ma
(KAL) x_used_2>[,…]]]
Queue
<num_qus>[,<q_id_1>,<max_msgs_q_1>,<num_msgs_q_1>[,<q_id_2>,<max_
Information
msgs_q_2>,<num_msgs_q_2>[,…]]]
(KAL)
Semaphore
Information <num_sems>[,<sem_id_1>,<val_sem_1>[,<sem_id_2>,<val_sem_2>[,…]]]
(KAL)
Buffer <num_pools>[,<pool_id_1>,<buff_size_1>,<max_buffs_1>,<num_avail_buffs
Status _1>[,<pool_id_2>,<buff_size_2>,<max_buffs_2>,<num_avail_buffs_2>[,…]]]
Information
(KAL)

Examples

Commands Possible Responses Description

AT+CFUN=1 OK Activate protocol stack

AT+SKENR=1,5,1 OK Enable message 1 and 4 for task 1
AT+SKENR=1,10,1 OK Enable message 2 and 8 for task 1
AT+SKENR=1,3,0 OK Disable message 1 and 2 for task 1

10.4 +SKRSTENR Reset for Engineering Mode Information

+SKRSTENR Reset for engineering mode information
The execution command is used by TE to request reset of engineering information in
the MS. When set command is executed successfully, the engineering mode
information of the specified tasks is reset.
The test command returns supported values as a compound value.

Syntax Description
+SKRSTENR =<task>[,<msg_id>] OK
+CME ERROR: <err>
+SKRSTENR: (<task_id1>,< list of
supported msg_id> )[,
+SKRSTENR=?
(<task_id1>,< list of supported
msg_id> )]

Parameters

<task> Sum of task_id as specified below:

0 Reset statistics for all tasks
1 RR
2 MM
3 GRR
4 GMM
5 LAPDm
6 LLC
7 SNDCP
8 CSD
9 SMS
10 SIM
11 CC
12 TICL
13 ATPP
14 GMR2P_RR
15 GMR2P_MM
16 GMR2P_LAPDM
17 GMR2P_CSD
18 GMR2P_SMS
19 GMR2P_CC
20 KAL
<msg_id> Refer comamnd +SKENR

Examples

Commands Possible Responses Description

AT+CFUN=1 OK Activate protocol stack

AT+SKRSTENR=1 OK Reset task RR information

10.5 +SKERRLOG Read Error Log from NVM

+SKERRLOG Read Error Log from NVM

This set mode is used to reset error logs in NVM and read will be used to display all
error logs which are stored in NVM.

Syntax Description

+SKERRLOG +CME ERROR: <err>

+SKERRLOG? [+SKERRLOG: <err_log_1><CR><LF>
+SKERRLOG: <err_log_2><CR><LF>
…
+SKERRLOG: <err_log_n><CR><LF>]
OK

Parameters

<err_log> Error log string

Examples

Commands Possible Responses Description

AT+CFUN=1 OK Protocol stack is activated

AT+SKERRLOG? +SKERRLOG:
“PROTO_ERR_LOG 1 3 6 8”
OK
AT+SKERRLOG OK Clear logs in NVM
AT+SKERRLOG? OK No error logs in NVM

11 Setting of Preferred message storage

For setting preferred message storage to ME or SM

Command Response
AT+SKCPMS= “ME”, “SM”,
OK
“SM”
AT+SKCPMS = “SM”, “SM”, “SM” OK

11.1 Listing of ME stored messages

Command Response
AT+CMGL = 4 +CMGL: 218104296,1,,33
0791889683434822040C9
188965293787200001080
12915115020FD3B29B0E3
2CBDF6D50900D478701
+CMGL: 218104298,0,,33
0791889683434822040C9
188965293787200001080
12915115020FD3B29B0E3
 2CBDF6D50900D478701
OK

OR
CMS ERROR: <err>

11.2 Reading a Specific ME stored message

AT+CMGR =<message id>.

Command Response
+CMGR: 1,,33
0791889683434822040C9
188965293787200001080
12915115020FD3B29B0E3
AT+CMGR = 218104296 2CBDF6D50900D478701
OK

OR
CMS ERROR: <err>

11.3 Deleting a Specific ME stored message

AT+CMGD =<message id>.

Command Response
OK
AT+CMGD = 218104296
OR
CMS ERROR: <err>

12 SMS related AT commands

12.1 SKCMGS – Send message (PDU mode, asynchronous)

+SKCMGS – Send message (PDU mode, asynchronous)

Execution Command send message from a TE to the network (SMS-SUBMIT). This command is an
asynchronous version of CMGS command, so that the AT channel is not blocked during
execution of this command. Unsolicited response +SKCMGS:1,<mr> is returned on successful
delivery and +SKCMGS:0,,<err> is returned on failure. Message reference value <mr> is
returned to the TE on successful message delivery. Please refer to CMGS command for a list of
<err> values.

Note. This command is for internal use by application framework only. This is not supported
through hyper terminal.

Syntax Description

AT+SKCMGS=<length><CR> OK
>PDU is given<ctrl-Z/ESC>
sending successful:
 +SKCMGS: 1,<mr>
if sending fails:
+SKCMGS:0,,<err>
Parameters

Refer section 9.1 for ‘AT Command Reference Guide [3]’ detail description of these parameters

Examples

Commands Possible Responses Description

AT+SKCMGS=19 OK Send short message. OK is returned

>0001FF0A8190033 +SKCMGS:1,2 immediately. On successful delivery,
00387000008C332 +SKCMGS URC is returned.
9B5D6787E5<CTRL
-Z>

AT+SKCMGS=19 OK Send short message. OK is returned

>0001FF0A8190033 +SKCMGS:0,,17 immediately. Message sending fails
00387000008C332 due to temporary network failure
9B5D6787E5<CTRL and +SKCMGS URC is returned.
-Z>
 13 Sasken Proprietary Errors

Numeric Text

600 AT command aborted

601 SS control failed

602 USSD control failed

603 Number of password attempts reached

604 FDN check failed

605 Abort attempt unsuccessful

606 Personalization disabled

607 Personalization deactivated

608 Personalization verification failed

609 Invalid personalization code group

610 Personalization blocked

611 MUX not enabled

612 No Coverage

613 No Coverage limited service

614 PLMN not allowed

615 GPS not available

616 Invalid power class

617 Market Personalization PUK required

618 Market Personalization PIN required

619 Already Depersonalized

620 Operation not allowed during search

 14 SAF Specific AT Commands

14.1 +CGMI (or +GMI)

+CGMI (or +GMI): Request Manufacturer Identification

Execution command causes the TA to return one or more lines of information text
<sn>, determined by the manufacturer, which is intended to permit the user to
identify the manufacturer. Typically, the text will consist of a single line containing
the name of the manufacturer, but manufacturers can choose to provide more
information if desired (for example, address or telephone number or customer
service).

Syntax Description

+GMI <sn>
+CME ERROR: <err>
+GMI=? OK

Parameters

<sn> The total number of characters, including line terminators, in

the information text shall not exceed 2048 characters.

Examples

Commands Possible Responses Description

AT+GMI “XXX Mobile Phones” Returns the manufacturer’s

OK identification
14.2 +CGMM (or +GMM)

+CGMM (or +GMM) Request Model Identification

Execution command causes the TA to return one or more lines of information text
<sn>, determined by the manufacturer, which is intended to permit the user to
identify the manufacturer. Typically, the text will consist of a single line containing
the name of the product, but manufacturers can choose to provide any information
if desired.
Syntax Description

+GMM <sn>
+CME ERROR: <err>
+GMM=? OK
Parameters

<sn> The total number of characters, including line terminators, in

the information text shall not exceed 2048 characters.
Examples

Commands Possible Responses Description

AT+GMM “Model Information”
OK

14.3 +CGMR (or +GMR)

+CGMR (or +GMR) Request Revision Identification

Execution command causes the TA to return one or more lines of information text
<sn>, determined by the manufacturer, which is intended to permit the user to
identify the manufacturer. Typically, the text will consist of a single line containing
the version of the product, but manufacturers can choose to provide any
information if desired.

Syntax Description

+GMR <sn>
+CME ERROR: <err>
+GMR =? OK
Parameters

<sn> The total number of characters, including line terminators, in

the information text shall not exceed 2048 characters.
Examples

Commands Possible Responses Description

AT+GMR “ Version 1.0.0 “ Product version
OK
14.4 +_IGPS

+_IGPS Request GPS Information

On execution the _IGPS command gives the GPS information. The ability for the UT
to display the GPS location information is controlled by the regulation in some
countries – whether the UT is allowed to release the GPS location information to the
MMI is determined by the network and communicated to the UT during the
registration process (as a part of a broadcast policy in the global beam ? )

Syntax Description

+_IGPS=<lat>, <lon> OK
+CME ERROR: <err>
+_IGPS? +_IGPS:
<lat>, <lon>, <type>, <status>,
<time>
+CME ERROR: <err>
OK
+_IGPS =?
ERROR
Parameters

<lat> Latitude in decimal degrees (minute & seconds converted to

the decimal degrees )
Positive values for North and negative values for South
<lon> Longitude also in decimal
Positive values for East and negative value for West
<type> 0 - “2D”, the GPS receiver has a 2D fix (and the GPS receiver is
ON)

1 - “3D”, the GPS receiver has a 3D fix (and the GPS receiver is
ON)

2 - “Stored” the GPS receiver is turned off – Lat & Lon values
are stored values (or zero if the <status> is undetermined or
barred), time is the time of that fix

3 - “Acquiring” the GPS receiver is turned on and it is

attempting to acquire a fix, the Lat & Lon values are stored
values (or zero if the <status> is undetermined or barred), time
is the time of that fix

<status> 0 - “allowed” – the UT is allowed to display the GPS location

1 - “barred” – GPS Operation barred in this location (Lat & Lon

will be returned as Zero)

2 - “undetermined” – the UT has not received a network policy

on GPS Display at the moment (Lat & Lon will be returned as
Zero)
<time> The current time held in the GPS receiver if the receiver is
active and has determined a time

The time the GPS fix was taken if <type> = “stored” or

“acquiring”

blank if no data is available

Examples
The format of <date & time> is specified using a default format is
"yy/MM/dd,hh:mm:ss±zz", where characters indicate year (two last digits), month,
day, hour, minutes, seconds and time zone (indicates the difference, expressed in
quarters of an hour, between the local time and GMT; range -47...+48).

E.g. 6th of May 1994, 22:10:00 GMT+2 hours equals to "94/05/06,22:10:00+08

NOTE: If UT does not support time zone information then the three last characters
of <time> are not returned
Commands Possible Responses Description
AT+_IGPS=15, -30 OK Sets the latitude and longitude
values
AT+_IGPS? +_IGPS:15, -30, 0, Returns the supported values
2,
AT+_IGPS=15 CME ERROR : 25 Invalid text or data string
14.5 +SKCKPD

+SKCKPD Key control

Execution command enables or disables the MT keypad by giving each keystroke as a character in a string <keys
<press> indicates the action performed on the key.. If emulating fails in an MT error, +CME ERROR: <err> is returned
Syntax Description

+SKCKPD =<key>, <press> OK

+CME ERROR: <err>
+SKCKPD=? OK
Parameters

<key> Character representing key as listed in the following table:

# : hash or enter
* : star sign
0…9 : number keys
< : left arrow button in the menu
> : right arrow button in the menu
C or c : clear display or CLR button
D or d : volume down or left arrow button
E or e : connection end or No button
S or s : connection start or Yes button
U or u : volume up or right arrow button
[ : Left soft key
]: Right soft key
M/m : Menu or OK key
^ : Up arrow
V/v : Down Arrow
<press> Indicates whether a key is pressed (1) or released (0)
Examples

Commands Possible Responses Description

AT+SKCKPD=”#”,1 OK Indicated key press for #
AT+SKCKPD=”#”,0 OK Indicated key release for #
14.6 +SKENKPD

+SKENKPD Key control

Execution command enables/disables the MT keypad control (UTE local keypad, and
the integrated handset keypad). If execution fails an MT error, +CME ERROR: <err> is
returned
Syntax Description

+SKENKPD=<status> OK
+CME ERROR: <err>
+SKENKPD=? OK
Parameters

<status> 0 – Disables the MT keypads’ control

1 – Enables the MT keypads’ control

Examples

Commands Possible Responses Description

AT+SKENKPD=1 OK Enables the MT keypads’ control
AT+SKENKPD=0 OK Disables the MT keypads’ control

14.7 +SKVOLLVL

+SKVOLLVL : Volume Level Setting

This execution command is used to set the volume level of the DUT. If the value is
set successfully, the OK response is returned. If the setting of level is failed, +CME
ERROR response is returned.

Syntax Description

AT+SKVOLLVL= [<value>] OK
ERROR
AT+SKVOLLVL? Current <value>
AT+SKVOLLVL= ? {0,10,20,30,40,50,60,70,80,90,100}
ERROR

Parameters

<value> Indicates the volume level to be

set
0 to 100 in steps of 10

Examples

Commands Possible Responses Description

AT+SKVOLLVL=100 OK Set the volume level to 100 %

AT+SKVOLLVL? 20 Current volume level
AT+SKVOLLVL= ? {0,10,20,30,40,50,60,70,80,90, Display list of supported
 100} values
OK
AT+SKVOLLVL= 200 +CME ERROR: 25 Invalid value

14.8 +SKLSAVAIL

+SKLSAVAIL Loud Speaker Available

The command controls the presentation of Loud Speaker(LS) option on call.

Syntax Description

+SKLSAVAIL=<value> OK
ERROR
Parameters

<value> 0 – Disable LS option

1 – Enable LS option

Examples

Commands Possible Responses Description

AT+SKLSAVAIL=1 OK Enable LS option on call
AT+SKLSAVAIL=0 OK Disable LS option on call
AT+SKLSAVAIL=2 +CME ERROR: 25 Invalid value

14.9 +SKEXTDEVICE

+SKEXTDEVICE External Device Connected

The command indicates the external device has been connected to DUT.
<type> denotes the type of external device. Maximum 10 external devices can be
connected.
<param> provides the extra information regarding external device
Irrespective of <param>, if <type> is ‘0’ in AT command, then device will be in
detatch state.

Important Note

If <type> is 1, then GPS Refresh rate of the UT will be changed to 10 minutes, i.e UT
will try to obtain GPS fix for every 10 minutes.

GPS Refresh Rate of the UT for <type> other than 1 will remains same , i.e 1hour.

Syntax Description

+SKEXTDEVICE=<type>, <param> OK
ERROR
Parameters

<type> 0 – Default device

1 – Docking Station, refer the important note above.
2 , 3… 10 - For Future use to connect other external
device other than Docking station.
<param> 0 – Refer table A
1 – Refer table A

Examples

Commands Possible Responses Description

AT+SKEXTDEVICE=1,0 OK Refer table A
AT+SKEXTDEVIC OK Refer table A
E=1,1
AT+SKEXTDEVICE= OK For Future use to connect
3,0 other external device other
than Docking station
OK For Future use to connect
AT+SKEXTDEVICE= other external device other
3,1 than Docking station
+CME ERROR: 25
OK
AT+SKEXTDEVICE= OK
3,2 +CME ERROR: 25
AT+SKEXTDEVICE=
10,0
AT+SKEXTDEVICE=
10,1
AT+SKEXTDEVICE=
10,2

AT+SKEXTDEVICE= +CME ERROR: 25 Not defined

11,0

Table A
<param> Headset Icon USB Icon Wallpaper Display
1 Removed Shown ‘Handset Docked’ and
‘Ready for service’
0 Removed Removed ‘Ready for service’

14.10 +SKMODEL

+SKMODEL
This AT command is used to set the Model Name and Handset Mode in UT. The AT
command takes two strings as parameters <param1>,<param2>.
<param1> – Model Name - to be displayed in About Screen.
<param2>– Handset Mode - to be displayed on AHS.

If the Input string exceeds the limit, +CME ERROR:<err> is returned.

Syntax Description

+SKMODEL=<param1>,<param2> OK
+CME ERROR: <err>

+SKMODEL? +SKMODEL:<param1>,<param2>

Parameters

<param1> – Model Name - Maximum length is 13 characters

<param2> – Handset Mode - Maximum length is 10 characters

Examples

Commands Possible Responses Description

AT+SKMODEL=”Isat OK Successfully set the model name
phone and handset mode in UT.
pro”,”Isatphone”

AT+SKMODEL=”Isat +CME ERROR:25 Invalid argument since, model

phoneprosasken”,”I name exceeds the maximum
satphone” length.

AT+SKMODEL=”Isat +CME ERROR:25 Invalid argument since, handset

Phone”,”Isatphone mode Exceeds the maximum
pro” length.

AT+SKMODEL? +SKMODEL:”Isat Reads the current Model Name

phone and Handset Mode from UT.
Pro”,”Isatphone
”
OK

14.11 +SKCTIME

+SKCTIME
On execution of +SKCTIME command will return the current time. The returned fields
will be UTC time, date, GMT offset and DST offset.

Syntax Description

+SKCTIME +SKCTIME: <param1>, <param2>, <

param3>, <param4>

+CME ERROR: <err>

Parameters

<param1> – Date - YYYY/MM/DD

<param2> – Time - HH:MM:SS
<param3> – GMT offset - + or – GMT offset in HH:MM
<param4> – DST offset - 1 or 0 depending on DST settings

Examples

Commands Possible Responses Description

AT+SKCTIME +SKCTIME: 2011/05/21, Successfully presents the current
21:47:17, +05:30, 0 time.

AT+SKTIME +SKCTIME: 2011/05/21, Successfully presents the current

(If GMT offset is 21:47:17, +05:30, 1 time.
less than GMT value
and DST is set in
device)

AT+SKCTIME +SKCTIME: 2011/05/25, Successfully presents the current

(whose local time = 21:47:17, +00:00, 0 time.
GMT )

14.12 +SKAUDDEV

+SKAUDDEV
+SKAUDDEV command indicates audio input and output device to which audio is
routed during ongoing call and when call gets connected (MO or MT call).

Syntax Description

+SKAUDDEV + SKAUDDEV: <Audio input device>,

<Audio output device>

+CME ERROR: <err>

Parameters

< Audio input device > Audio input device notification

1 – Handset MIC
2 – Wired headset MIC
4 – Bluetooth headset MIC

< Audio output device > Audio output device notification

1 – Handset speaker
2 – Wired headset speaker
4 – Bluetooth headset speaker
8 – Loudspeaker
Examples
Commands Possible Responses Description
+SKAUDDEV + SKAUDDEV: 1,1 Input is Handset MIC, output is
Handset speaker

+ SKAUDDEV: 2,2 Input is Wired headset MIC and

output is Wired headset speaker

+ SKAUDDEV: 4,4 Input is Bluetooth headset MIC and

output is Bluetooth headset
speaker

+ SKAUDDEV: 1,8 Input is handset MIC and output is

Loudspeaker

14.13 +SKALRMIND

+SKALRMIND
+SKALRMIND command indicates alarm status, alarm ON and alarm OFF.
When the programmable alarm triggers OR stopped OR snoozed, an unsolicited
notification out the AT port shall be sent.

Syntax Description

+SKALRMIND +SKALRMIND: <Alarm indication>

Parameters

< Alarm indication > 1 – ALARM_IND_ON

2 – ALARM_IND_OFF

Examples

Commands Possible Responses Description

+SKALRMIND +SKALRMIND: 1 Alarm start indication.

+SKALRMIND: 2 Alarm stopped OR snoozed

indication.

14.14 +SKBATIND

+SKBATIND
On execution of +SKBATIND command, the battery status icon and battery charging
related pop-up’s (‘Enable charging') will be enabled.
The battery status icon and battery charging related pop-up’s will be disabled by
default when terminal power class does not equal to 5.

Syntax Description

AT+SKBATIND OK
+CME ERROR: <err>

+SKBATIND:<Enable>

Parameters
<Enable > 1 – Enable battery icon and ‘Enable charging' popup
0 – Error

Examples

Commands Possible Responses Description

AT+SKBATIND = 1 OK Enables battery status icon and
battery changing related pop-ups

AT+SKBATIND = 0 CME ERROR: 25 Not supported

14.15 +SKPALERT

+SKPALERT
On execution of +SKPALERT command, the personal alert feature can be enabled or
disabled by specifying the parameter <Enable/Disable>.
The Personal alert feature will be disabled by default when terminal power class
does not equal to 5.

Syntax Description

AT+SKPALERT OK
+CME ERROR: <err>

+SKPALERT:<Enable/Disable>

Parameters
<Enable > 1 – Enable Personal alert feature

<Disable> 0 – Disable Personal alert feature

Examples

Commands Possible Responses Description

AT+SKPALERT = 1 OK Enables Personal alert feature

AT+SKPALERT = 0 OK Disables Personal alert feature

AT+SKPALERT = 3 +CME ERROR: 3 Error will displayed other than 0 and 1

14.16 +SKRGPSPOS

+SKRGPSPOS
On execution of +SKRGPSPOS command, the handset/CM is forced to refresh its GPS position and
returns new GPS position.
On executing this AT command, the AT cmd will return with OK immediately make AT channel free.
This AT cmd will execute max for 45 seconds to get the fresh fix. If new fix is not acquired within this
time (45 sec) then handset will return status as error.
Syntax Description

AT+SKRGPSPOS=? +SKRGPSPOS :<status>

<lat>, <lon>, <alt>, <date >,< time >

+SKRGPSPOS: 0
<error>

Parameters
<status> 1- New GPS fix acquired and output will be with GPS position
0-error (GPS TIME OUT).
<lat> Latitude in decimal degrees (minute & seconds converted to the deci-
mal degrees )Positive values for North and negative values for South
<lon> Longitude also in decimal
Positive values for East and negative value for West
<alt> altitude in meter
<date> YYYY:MM:DD
<time> HH:MM:SS (UTC time)

Examples

Commands Possible Responses Description

AT+SKRGPSPOS=? OK

+SKRGPSPOS:1 Return the GPS value

+12.925554,+77.6861
10,873,2012/06/12,0
8:12:03

+SKRGPSPOS: 0 <error>
GPS TIME OUT
 15 Control of SAT/GSM modes

15.1 +SKSTKMD
+SKSTKMD: Stack Mode Setting

This execution command is used to set the product to either behave like a GMR2P stack or a
GSM Stack. After the command has completed, the MT remains in V.25ter command state. If
the MT is already in the requested state, the command is ignored and the OK response is
returned. If the requested state cannot be achieved, an ERROR or +CME ERROR response is
returned. The read command returns the current product set for the protocol stack.
The test command is used for requesting information on the current product set for the
protocol stack.

Syntax Description

AT+SKSTKMD= [<mode>] OK
ERROR
AT+SKSTKMD? + SKSTKMD: <mode>
AT+ SKSTKMD =? +SKSTKMD: (list of supported <mode>)

Parameters

<mode> Indicates the current product set

0 GSM
1 GMR

Examples

Commands Possible Responses Description

AT+SKSTKMD=1 OK Set the current product to GMR

AT+SKSTKMD? +SKSTKMD: 1
OK Current Product set to GMR

AT+ SKSTKMD =0 OK Set the current product to GSM

AT+ SKSTKMD? + SKSTKMD: 0

OK Current Product set to GSM

AT+ SKSTKMD =? + SKSTKMD: (0-1)

OK Test mode
15.2 +SKGPSPLCY
+SKGPSPLCY GPS Policy Indication

The set command controls the presentation of an unsolicited result code:

+SKGPSPLCYI :<gps_reqd>,<mmi_ctrl_flag>
The read command returns the current command setting. The test command returns supported
values
as a compound value.

Syntax Description

+SKGPSPLCY=<act> OK
+SKGPSPLCY? +SKGPSPLCY: <act>
+SKGPSPLCY=? +SKGPSPLCY: (list of supported <act>)

Parameters

<act> 0 – Disable +SKGPSPLCYI event

1 – Enable SKGPSPLCYI event

Examples

Commands Possible Responses Description

AT+SKGPSPLCY=1 OK Enable +SKGPSPLCYI URC

+ SKGPSPLCYI: 0, 0 GPS Not required, MMI_ctrl_flag_disabled
+ SKGPSPLCYI: 0, 1 GPS Not required, MMI_ctrl_flag_Enabled
+ SKGPSPLCYI: 1, 0 GPS Required, MMI_ctrl_flag_disabled
+ SKGPSPLCYI: 1, 1 GPS Required, MMI_ctrl_flag_Enabled
15.3 +SKGPSPOS
+SKGPSPOS GPS Position Indication

The set command controls the presentation of an unsolicited result code:

+SKGPSPOSI :<gps_validity>
The read command returns the current command setting. The test command returns supported
values as a compound value.

Syntax Description

+SKGPSPOS=<act> OK
+SKGPSPOS? +SKGPSPOS: <act>
+SKGPSPOS =? +SKGPSPOS: (list of supported act>)

Parameters

<act> 0 – Disable SKGPSPOSI event

1 – Enable SKGPSPOSI event

Examples

Commands Possible Responses Description

AT+SKGPSPOS=1 OK Enable +SKGPSPOSI URC

+ SKGPSPOSI: 0 GPS Position Invalid
+ SKGPSPOSI: 1 GPS Position Valid
15.4 +SKRBSRCH
+SKRBSRCH to search the RBCCH

The set command controls the registration of UT.

The read command returns the list of PLMNs.

Syntax Description

+SKRBSRCH=<n> <arfcn> <plmn_id> OK

+SKRBSRCH? +SKRBSRCH: <list of PLMNs >

Parameters

<n> 0 – Stored search

1 – Extensive search
2 – Get the list of RBCCH on a given plmn.

<arfcn> optional field (RBCCH ARFCN from user).

<plmn_id> plmn_id

Examples

Commands Possible Responses Description

AT+SKRBSRCH=1 OK UT will start extensive search.

AT+SKRBSRCH=0 OK UT will start stored search.

AT+SKRBSRCH=0, 8,123456 OK UT will start search on a specific RBCCH ARFCN.

AT+SKRBSRCH=2,, 123456 +SKRBSRCH:“93”,”94”,”95

OK Returns the RBCCH list on the given PLMN

AT+SKRBSRCH? +SKRBSRCH: "123456","213562",

"563423","468356","138934" Returns the PLMN list
15.5 +SKSELABORT

+SKSELABORT to abort search the RBCCH

This command aborts SKRBSRCH set command and CFUN=1 command

Syntax Description

+SKSELABORT OK

Examples

Commands Possible Responses Description

AT+SKRBSRCH=0, 8 OK UT will start search on a specific RBCCH ARFCN.

AT+SKSELABORT OK Aborts SKRBSRCH

AT+CFUN =1 OK Starts protocol stack activation

AT+SKSELABORT OK Aborts protocol stack activation

15.6 +SKCPWC
+SKCPWC Set UT Power Class

The set command sets the power class in common context structure. The read command reads
the power class from this structure. The test command displays the list of supported power
classes

Note: The application (in the full phone solution) does not allow the ‘power class set
command’ to be set from external clients like VAM host or other terminals. The application
rejects this command with +CME ERROR. However the read and test commands are supported.

Syntax Description

+SKCPWC=<pow_class> OK
+CME ERROR
+SKCPWC? +SKCPWC: <curr_class>
+SKCPWC=? +SKCPWC: list of supported (list of <class>s)

Parameters

<pow_class> 2- PC2 (GPIO 36 (1), GPIO 37 (0))

3- PC3 (GPIO 36 (0), GPIO 37 (1))
5- PC5 (GPIO 36 (0), GPIO 37 (0))

Examples
Commands Possible Responses Description

AT+SKCPWC=2 OK Sets power class as 2 in common context structure

gmr2p_ms_classmark
AT+SKCPWC? +SKCPWC: 2 Reads the power class set in the common context structure

AT+SKCPWC=? +SKCPWC: (2, 3, 5) Lists the supported power classes

AT+SKCPWC=4 +CME ERROR:

INVALID_POWER_CLASS_ERR
When invalid power class is entered, displays CME
ERROR

15.7 +SKGPSINFO?
+SKGPSINFO? Read GPS information from NVM

The read command reads the GPS information stored in parameter

NVM_PARAM_TYPE_GPS_SAF_INFO in NVM.

Syntax Description

+SKGPSINFO? +SKGPSINFO: :
<is_pos_valid>,<<lat_degree,lat_minute,lat_second,lat_dir>,<long_degr
ee,long_minute,long_second,long_dir>,<alt_type,alt_dec,alt_frac>,<H_
error,V_error>,<<gps_time_status>,<time>>

+OK

Parameters

< is_pos_valid > 0 – Gps position invalid

1 – Gps position valid

< lat_degree > Latitude in degrees

< lat_minute> Latitude in minutes

<lat_second> Latitude in seconds

< lat_dir > 0 – East

1 – West

<long degree > Longitude in degrees

< long_minute> Longitude in minutes

<long_second> Longitude in seconds

< long_dir > 0 – East

1 – West

<alt_type>
 0 – Height
1 – Depth

<alt_dec> Altitude in decimal

<alt_frac> Altitude in fraction

<H_error> Horizontal error

<V_error> Vertical error

<gps_time_status> 0 – Time_UTC
1 – Time_GPS

<time> Time is in string format “yy/MM/dd,hh:mm:ss:ms”

yy - year
MM – month
dd – date
hh – hour
mm – minute
ss – second
ms - millisecond
Examples
Examples

Commands Possible Responses Description

AT+SKGPSINFO? +SKGPSINFO: 1, 0, 5
,52,1,5,20,35,1,23,56,34,245,0
,"2005/04/03, 00:01:02:00"
OK Reads GPS information stored in NVM
 16 Audio AT commands

16.1 +AUDCOMP

+AUDCOMP Enables/disables Audio component for a given audio mode.

+AUDCOMP Enables/disables Audio component for a given audio mode.
This command enables/disables the given component in audio processing path for a given audio
mode.
It is available in either debug mode or in VAM mode.
It is available in normal mode only if <comp_id> is selected as 3 (“UL Compressor”).

Syntax Description

+AUDCOMP=<audio_mode>,<comp_id>[,<enable_disable>]
+AUDCOMP=<audio_mode>,<comp_id>,<enable_disable> OK if successful
+CME ERROR: <err> if error
+AUDCOMP=<audio_mode>,<comp_id> +AUDCOMP:
<audio_mode>,<comp_id>,<enable_disable>
+AUDCOMP=? +AUDCOMP: (list of <audio_mode>),(list of supported
<comp_id>),(list of supported <enable_disable>)

Parameters

<audio_mode> Integer (0..3)

0 – Handset
1 – Loud Speaker
2 – HEADSET
3 – Bluetooth

<comp_id> Integer (0..8)

0 - Side Tone
1 - Echo Canceller
2 - UL Equalizer
3 - DL Equalizer
4 - UL Compressor
5 - DL Compressor
6 - MCU Compressor
7 – UL Noise Suppressor
8 – DL Noise Suppressor

<enable_disable> Integer (0..1)

0 - Disable
1 – Enable

Examples

Commands Possible Responses Description

AT+AUDCOMP=0,1, OK Enables Echo Canceller in speech

1 processing path for handset mode
AT+AUDCOMP=0,5 +AUDCOMP: 0,5, 0 Gives current status
 OK (enabled/disabled) of audio
component for handset mode
AT+AUDCOMP=? +AUDCOMP: (0..3),(0..6), TA responding with the
(1,0) supportable values for test
OK command
AT+AUDCOMP=0,1, OK Unsolicited error event when
1 +SKAUDERR: “+AUDCOMP operation is not allowed.
0,0,1 is not allowed
during call”

16.2 +AUDLPBK

+AUDLPBK Enables/disables Audio loopback

This command enables/disables the given loopback in audio processing path.

It is available in debug mode only.
Syntax Description
+AUDLPBK=<lpbk_id>[,<enable_disable>]
+AUDLPBK=<lpbk_id>,<enable_disable> OK if successful
+CME ERROR: <err> if error
+AUDLPBK=<lpbk_id> +AUDLPBK: <lpbk_id>,<enable_disable>
+AUDLPBK=? +AUDLPBK: (list of supported <lpbk_id>),(list of supported
<enable_disable>)
Parameters
<lpbk_id> Integer(0)
0 – ABB loopback from Speaker to MIC.

<enable_disable> Integer(0..1)
0 - Disable
1 – Enable
Examples

Commands Possible Responses Description

AT+AUDLPBK=0,1 OK Enables Speaker to MIC ABB

loopback in DL speech processing
path
AT+AUDLPBK=0 +AUDLPBK: 0, 1 Gives current status
OK (enabled/disabled) of loopback id
AT+AUDLPBK=? +AUDLPBK: (0),(1,0) TA responding with the
OK supportable values for test
command
AT+AUDLPBK=0,0 OK Unsolicited error event when
+SKAUDERR: “+AUDLPBK operation is not allowed.
0,0 is not allowed during
call”
16.3 +AUDLOG

AUDLOG Enables/disables Logging of audio samples

This command enables/disables logging of audio samples at the given location in audio
processing path.
It is available in debug mode only.

Syntax Description

+AUDLOG=<loc_id>[,<enable_disable>]
+AUDLOG=<loc_id>,<enable_disable> OK if successful
+CME ERROR: <err> if error
+AUDLOG=<loc_id> +AUDLOG: <loc_id>,<enable_disable>
+AUDLOG=? +AUDLOG: (list of supported <loc_id>),(list of supported
<enable_disable>)
Parameters

<loc_id> Integer(0)
0 – Echo Canceller Input

<enable_disable> Integer(0..1)
0 - Disable
1 – Enable
Examples

Commands Possible Responses Description

AT+AUDLOG=0,1 OK Enables Logging at Echo Canceller

Input in speech processing path
AT+AUDLOG=0 +AUDLOG: 0, 0 Gives current status
OK (enabled/disabled) of Logging at
given location
AT+AUDLOG=? +AUDLOG: (0),(1,0) TA responding with the
OK supportable values for test
command
16.4 +AUDPAREC

+AUDPAREC Controls parameters of Echo Canceller for a given audio mode.

This command controls parameters of Echo Canceller for a given audio mode.
It is available in either debug mode or in VAM mode.
Syntax Description

+AUDPAREC=<audio_mode>,<tailLength>,<enable_aggressive_mode>,<enable_ec_sup
pressor>,<min_suppressor_value>,<lec_delay_length>,<nlp_control>
+AUDPAREC=<audio_mode>,<tailLength>,<enab OK if successful
le_aggressive_mode>,<enable_ec_suppressor>, +CME ERROR: <err> if error
<min_suppressor_value>,<lec_delay_length>,<
nlp_control>
+AUDPAREC=<audio_mode> +AUDPAREC:
<audio_mode>,<tailLength>,<enabl
e_aggressive_mode>,<enable_ec_s
uppressor>,<min_suppressor_value
>

+AUDPAREC=? +AUDPAREC: (list of supported

<audio_mode>),(list of supported
<tailLength>),(list of supported
<enable_aggressive_mode>),(list of
supported <enable_ec_suppressor>),
(list of supported
<min_suppressor_value>),(list of
supported lec_delay_length),(list of
supported nlp_control)

Parameters
<audio_mode> Integer(0..3)
0 – Handset
1 – Loud Speaker
2 – HEADSET
3 – Bluetooth

<tailLength> Integer(1..256) - This parameter is used to control the tail

length of Echo Canceller, and it is in units of 8 kHz samples
(refer to /4/). If tail length is changed dynamically, then it will
reset EC, which may create data loss and stabilization time.

<enable_aggressiv Integer(0,1). This parameter adjusts the internal floors and

e_mode> thresholds to improve NLP and clamping performance in
extremely harsh acoustic environments with very large echo.
0 – Disable
1 – Enable
Note: This parameter should only be enabled if performance is
poor in environment, and if enabling the parameter serves to
improve the signal quality in real tests.

<enable_ec_suppr Integer(0,1). This parameter is used to enable the built-in

essor> audio suppressor logic in the receive and transmit legs of the
EC.
0 – Disable
 1- Enable
Note: The suppressor must be disabled to comply with G.168
testing, and should only be used in very poor acoustic
environments where selective attenuation is acceptable.

<min_suppressor_ Integer(15-bit).The maximum attenuation that is allowed to be

value> injected into the echo path.
Refer to /4/ for details of parameter values.

<lec_delay_length Integer(0..256). This parameter specifies the EC delay length

> to be used.

<nlp_control> Integer(0..2). This parameter controls NLP (Non Linear

Processing) and CNG (Comfort Noise Generation). When set to
0, both the NLP and CNG are disabled.  When set to 1, the CNG
is disabled and the NLP is enabled.  When set to 2, both the
NLP and CNG are enabled.

Examples

Commands Possible Responses Description

AT+AUDPAREC=1,3 OK Configures EC parameters for loud-

2,1,1,1FFF,1,0 speaker mode. If the command is
issued when speech processing
path is active, then it will trigger
reset of EC before taking new
value.
AT+AUDPAREC=1 +AUDPAREC: Gives current status of EC
1,32,1,1,1FFF,1,0 parameters for queried audio
OK mode.

AT+AUDPAREC=? +AUDPAREC: (0-3),(1- TA responding with the

256),(0-1),(0-1),HEX15, supportable values for test
(0-256),(0-2) command
OK

16.5 +AUDPARST

+AUDPARST Controls parameters of Side Tone for a given audio mode.

This command controls parameters of Side Tone.
It is available in either debug mode or in VAM mode.
Syntax Description

+AUDPARST=<audio_mode>,<volume>,<attenuation>
+AUDPARST=<audio_mode>,<volume>,<attenu OK if successful
ation> +CME ERROR: <err> if error
+AUDPARST=<audio_mode> +AUDPARST: <audio_mode>,<attenuation>
+AUDPARST=? +AUDPARST: (list of supported <audio_mode>),(list of
supported <volume>),(list of supported <attenuation>)
Parameters
<audio_mode> Integer(0..3)
0 – Handset
1 – Loud Speaker
 2 – HEADSET
3 – Bluetooth

<volume> Integer(0..31) – Volume level

Note: Current volume level can be set by setting
AT+AUDREG=<device>,4,<register-value>.

<attenuation> Integer(15-bit) - This parameter contains the attenuation in

linear scale which needs to be applied to microphone data
(side tone) before mixing it with speaker data. (refer to /4/).
Actual attenuation = attenuation/2^15.

Rsvd1 Integer - Reserved

Rsvd2 Integer - Reserved

Rsvd3 Integer - Reserved

Examples

Commands Possible Responses Description

AT+AUDREG=2,4,3 OK Configures AudOut12Register for

39 Aout1Gain=25, Aout2Gain=25 (according to
AD6855 data-sheet) for HEADSET mode
AT+AUDPARST=2, OK Configures attenuation of Side Tone for
25,6553 HEADSET mode for a given volume-level.
Gives current status of Side Tone
AT+AUDPARST=3 +AUDPARST: 3,(15- parameters for queried audio mode.
bit,0,0,0)[For all volume-
levels]
OK
AT+AUDPARST=? +AUDPARST: (0..3), TA responding with the supportable values
(0..31),(15- for test command
bit),RSVD1,RSVD2,RSVD3
OK

16.6 +AUDPAREQ

+AUDPAREQ Controls parameters of DSP Uplink/Downlink Equalizer for a given audio mode.

This command controls parameters of DSP Uplink/Downlink Equalizer for a given audio mode.
It is available in either debug mode or in VAM mode.
Syntax Description

+AUDPAREQ=<audio_mode>,<dir>[,<bulk_gain>,<band1_param>,<band2_param>,<ba
nd3_param>]
+AUDPAREQ=<audio_mode>,<dir>,<bulk_gain>, OK if successful
<band1_param>,<band2_param>,<band3_para +CME ERROR: <err> if error
m>
+AUDPAREQ=<audio_mode>,< +AUDPAREQ:
dir> <audio_mode>,<dir>,<bulk_gain>,<band1_param>,<band2_pa
ram>,<band3_param>
+AUDPAREQ=? +AUDPAREQ: (list of supported <audio_mode>),(list of <dir>),
 (list of supported bulk_gain),(list of supported
<band1_param>),(list of supported <band2_param>),(list of
supported <band3_param>)

Parameters

<audio_mode> Integer(0..3)
0 – Handset
1 – Loud Speaker
2 – HEADSET
3 – Bluetooth

<dir> Integer(0..1)
0 – Uplink
1 - Downlink

<bulk_gain> Integer(-600..600) millibels – EQ overall gain

<band_param> (freq+filter_type+q+bandlevel)

freq - Integer(31..8000) Hz
Center frequency of EQ band

filter_type - Integer(0..4)
Filter type of band
0 – LOW_SHELF1
1 – LOW_SHELF2
2 – PEAKING
3 – HIGH_SHELF1
4 – HIGH_SHELF2

q - Integer(10..1000) -
Resonance Q of band.
Actual value = q/100

bandlevel - Integer(-1800..1800) millibels

Amplitude of each band.

Notes: 1. Refer to /5/ for details of parameters.

2. Freq has to be in increasing order in successive bands
3. Actual dB value = millibels/100

Examples

Commands Possible Responses Description

AT+AUDPAREQ= OK Configures parameters of specified

2,0,300, Equalizer for HEADSET mode.
(1000,1,100,-400),
(4000,2,350,0),
(7000,4,800,400)
AT+AUDPAREQ=2,0 +AUDPAREQ: 0,0, Gives current status of specified
2,0,300, (1000,1,100,- Equalizer parameters for queried
400), (4000,2,350,0), audio mode.
 (7000,4,800,400)
OK
AT+AUDPAREQ=? +AUDPAREQ: (0..3), TA responding with the
(0..1), supportable values for test
((31..8000,0..4,10..1000, command
-1800..1800)[3])
OK

16.7 +AUDPARCMP

+AUDPARCMP Controls parameters of DSP Uplink/Downlink or MCU Compressor for a given

audio mode.

This command controls parameters of DSP Uplink/Downlink or MCU Compressor for a given
audio mode.
It is available in either debug mode or in VAM mode.

Syntax Description

+AUDPARCMP=<audio_mode>,<dir>[,<band1_param>],[,<band2_param>],
[,<band3_param>],[,<freq_list>]
+AUDPARCMP=<audio_mode>,<dir>[,<band1_p OK if successful
aram>],[,<band2_param>],[,<band3_param>], +CME ERROR: <err> if error
[,<freq_list>]
+AUDPARCMP= <audio_mode>,<dir> +AUDPARCMP:
<audio_mode>,<dir>,<band1_para
m>,[,<band2_param>],
[,<band3_param>],[,<freq_list>]
+AUDPARCMP=? +AUDPARCMP: (list of supported
<audio_mode>),(list of <dir>),(list
of supported <band_param>), list
of supported <freq_list>)

Parameters

<audio_mode> Integer(0..4)
0 – Handset
1 – Loud Speaker
2 – HEADSET
3 – Bluetooth
4- None

<dir> Integer(0..2)
0 – Uplink
1 – Downlink
2- MCU

<band_param> <band2_param>, <band3_param> and <freq-list> is not

required if <dir> is not set to MCU.

(softknee_delta+output_gain+attack_time+release_time+
num_points+input_level_array+output_level_array)
 Softknee_delta - Integer(50..300) millibels
Delta of input for implementing soft knee at change of
region

Output_gain – Integer(-9600..2400) millibels

Overall output gain of compressor

Attack_time – Integer(0..100) milliseconds

Attack time for compressor

Release_time – Integer(any positive value) milliseconds

Release_time for compressor

num_points - Integer(1..4)
Number of points in compression profile (refer to /6/)

Input_level_array[1..4] – num_point entries of Integer(-

9600..0) millibels
Value has to be in increasing order

<freq_list> output_level_array[1..4] – num_point entries of Integer(-

9600..0) millibels

freq1,freq2,freq3,freq4 – Defines frequencies for different

band regions; this parameter is applicable only for multi-band
compressor in MCU.

Notes: Freq – Integer(1 to 48000) Hz

1. Refer to /6/ for details of parameters.

2. Freq has to be in increasing order in successive bands
3. Only one band exists for DSP
4. Actual dB value = millibels/100

Examples

Commands Possible Responses Description

AT+AUDPARCMP=2 OK Configures parameters of specified

,2, Compressor for loud-speaker
(100,400,50,500,3 mode.
,-4800,-2400,-
1200,-4800,
-3600,-3200)
AT+AUDPARCMP=1 +AUDPARCMP: 1,0, Gives current status of specified
,0 (100,300,50,400), (2,- Compressor parameters for queried
4800,-1200,-4800,-3000) audio mode.
OK
AT+AUDPARCMP=? +AUDPARCMP: (0..4), TA responding with the
(0..2),(50..300,-9600.. supportable values for test
2400,0..100,UINT,1..4,- command
9600..0[1..4],-
9600..0[1..4] ),
( 1..48000[4] )
 OK

16.8 +AUDREG
+AUDREG Reads/Writes Audio registers for a given audio mode.

This command allows read/write access to Audio registers for a given audio mode.
It is available in debug mode only.

Syntax Description

+AUDREG=<audio_mode>,<reg_id>[,<val>]
+AUDREG=<audio_mode>,<reg_id>,<val> OK if successful
+CME ERROR: <err> if error
+AUDREG=<audio_mode>,<reg_id> +AUDREG:
<audio_mode>,<reg_id>,<val>
+AUDREG=? +AUDREG: (list of supported
<audio_mode>),(list of supported
<reg_id>),(list of supported <val>)

<audio_mode> Integer(0..3)
0 – Handset
1 – Loud Speaker
2 – HEADSET
3 – Bluetooth

<reg_id> Integer(0..11)
0 - AudioControl1
1 - AudioControl2
2 - AudioControl3
3 - AudioControl4
4 - AudioOut12Control
5 - AudioOutLRContro
6 - AudioOut3Control l
7 - AudioMic1Control
8 - AudioMic2Control
9 - AudioInControl
10 - AudioMuteControl
11 - DetectorControl

<val> Integer(16-bit) – If value is absent, the command will read

register, otherwise write the register with given value.
Value is represented by a hexadecimal number without “0x”,
e.g. 3C.

Examples

Commands Possible Responses Description

AT+AUDREG=3,0, 4 OK Writes AudControl1 register with

value 0x4 for blue-tooth mode.
AT+AUDREG=3,9 +AUDREG: 3,9, 3 Gives current value of given Audio
 OK register for queried audio mode.
AT+AUDREG=? +AUDREG: (0..3),(0..11), TA responding with the
(16-bit hex <value>) supportable values for test
command

16.9 +AUDVAMCFG

+ AUDVAMCFG Reads/Writes Audio registers for VAM audio configurations.

This command allows read/write access to Audio Register configurations for VAM audio
configurations.
It is available in VAM mode only.

Syntax Description

+AUDVAMCFG=<param>[,<val>]
+AUDVAMCFG=<param>,<val> OK if successful
+CME ERROR: <err> if error
+AUDVAMCFG=<param> +AUDVAMCFG: <param>,<val>
+AUDVAMCFG=? +AUDVAMCFG: (list of supported
<param>),(list of supported <val>)

Parameters

<param> Integer(0..9)
0 - "OUT1_GAIN": AOUT1 PGA gain
1 - "OUT2_GAIN": AOUT2 PGA gain
2 - "OUT3_GAIN": AOUT3 PGA gain
3 - "OUT3L_GAIN": AOUT3L PGA gain
4 - "OUT3R_GAIN": AOUT3R PGA gain
5 - "IN1_GAIN": AIN1 PGA gain
6 - "IN2_GAIN": AIN2 PGA gain
7 - "MIC_PREAMP_GAIN": MIC pre-amplifier gain
8 - "MIC1_BIAS_GAIN": MIC1 bias current and voltage gain
9 - "MIC2_BIAS_GAIN": MIC2 bias current and voltage gain

<val> Integer(-48..45) – If value is absent, the command will read

parameter, otherwise write the parameter with given value.
The number maps to different values/ranges for different
parameters as below:
“OUT1_GAIN” : -48..12…2 dB
“OUT2_GAIN” : -42..18…2 dB
“OUT3_GAIN” : -48..12…2 dB
“OUT3L_GAIN” : -48..12…2 dB
“OUT3R_GAIN” : -48..12…2 dB
“IN1_GAIN” : 0..45, Actual value = val/2 dB
“IN2_GAIN” : 0..45, Actual value = val/2 dB
“MIC_PREAMP_GAIN” : (20,29) dB
“MIC1_BIAS_GAIN” : 0..3, Actual value = (500_10.5,303_6.4,
183.6_3.96,111.25_2.46)
“MIC2_BIAS_GAIN” : 0..3, Actual value = (500_10.5,303_6.4,
 183.6_3.96,111.25_2.46)

Examples

Commands Possible Responses Description

AT+AUDVAMCFG=1 OK Updates Gain for AOUT2 to -12 dB

,-12 in AudioOut12Control register.
AT+AUDVAMCFG=5 +AUDVAMCFG: 5,28 Gives current value of given Audio
OK parameter from associated audio
control register.
AT+AUDVAMCFG=? +AUDVAMCFG: (0..9),(- TA responding with the
48..45) supportable values for test
command

16.10 +AUDUPDNVM

+AUDUPDNVM Updates current settings in NVM default settings.

This command allows update current settings in NVM default settings, such that the updates
settings will be used in subsequent power-on. Note that, current settings can be altered using
audio AT commands in appropriate modes.
It is available in all modes (normal, debug and VAM). Note that, in normal mode only “UL
Compressor” can be enabled or disabled.
Syntax Description

+AUDUPDNVM=<audio_mode>
+AUDUPDNVM=<audio_mode> OK if successful
+CME ERROR: <err> if error
+AUDUPDNVM? Not Available
+AUDUPDNVM=? +AUDUPDNVM: (list of supported <audio_mode>)
Parameters

<audio_mode> Integer(0..4)
0 – Handset
1 – Loud Speaker
2 – HEADSET
3 – Bluetooth
4- All

Examples

Commands Possible Responses Description

AT+AUDUPDNVM=4 OK Updates NVM default settings for

given audio mode
AT+AUDUPDNVM=? +AUDUPDNVM: (0..4) TA responding with the
supportable values for test
command

16.11 +AUDLDSIM
+AUDLDSIM Simulates load of DSP Audio components even if they are disabled.

This command enables/disables load simulation of audio components in audio processing path
on DSP.
It is available in debug mode.

Syntax Description

+ AUDLDSIM=<enable_disable>
+AUDLDSIM=<enable_disable> OK if successful
+CME ERROR: <err> if error
+AUDLDSIM? +AUDLDSIM: <enable_disable>
+AUDLDSIM=? +AUDLDSIM: (list of supported <enable_disable>)

Parameters

<enable_disable> Integer(0..1)
0 - Disable
1 – Enable
Examples

Commands Possible Responses Description

AT+AUDLDSIM=1 OK Enables load simulation for DSP

audio components even if they are
disabled.
AT+AUDLDSIM? +AUDLDSIM: 1 Gives current status
OK (enabled/disabled) of load
simulation
AT+AUDLDSIM=? +AUDLDSIM: (1,0) TA responding with the
OK supportable values for test
command
AT+AUDLDSIM=0 OK Unsolicited error event when
+SKAUDERR: “+AUDLDSIM operation is not allowed.
0 is not allowed during
call”
16.12 +AUDERR

+AUDERR Unsolicited error sent by TA for a previously given command.

Unsolicited error sent by TA for a previously given command.

Syntax Description

Parameters

<err> String indicating error message

Examples

Commands Possible Responses Description

AT+AUDREG=0,0x4 OK Unsolicited error event when

+SKAUDERR: “+AUDREG operation is not allowed.
0,0x4 is not allowed
during call”

17 Traceability

[1] GSPS Requirements specification.