Siemens TC65 Terminal. Manual (Version: 02.000)

11.7 AT+CGEQMIN

<Maximum SDU size>^(num)

This parameter indicates the maximum allowed SDU size in octets.

[0]

subscribed value

10...1520

(value needs to be divisible by 10 without remainder)

1502

<SDU error ratio>^(str)

This parameter indicates the target value for the fraction of SDUs lost or detected as erroneous. SDU error ratio

is defined only for conforming traffic. The value is specified as "mEe". As an example a target SDU error ratio

of 5*10^-3 would be specified as "5E3" (e.g. AT+CGEQMIN=...,"5E3",...).

["0E0"]

subscribed value

"1E2"

"7E3"

"1E3"

"1E4"

"1E5"

"1E6"

"1E1"

<Residual bit error ratio>^(str)

This parameter indicates the target value for the undetected bit error ratio in the delivered SDUs. If no error

detection is requested, Residual bit error ratio indicates the bit error ratio in the delivered SDUs. The value is

specified as "mEe". As an example a target residual bit error ratio of 5*10^-3 would be specified as "5E3" (e.g.

AT+CGEQMIN=...,"5E3",...).

["0E0"]

subscribed value

"5E2"

"1E2"

"5E3"

"4E3"

"1E3"

"1E4"

"1E5"

"1E6"

"6E8"

<Delivery of erroneous SDUs>^(num)

This parameter indicates whether SDUs detected as erroneous shall be delivered or not.

yes

no detect

[3]

subscribed value

Page 320 of 567

11.7 AT+CGEQMIN

<Transfer delay>^(num)

This parameter indicates the targeted time between request to transfer an SDU at one SAP to its delivery at the

other SAP, in milliseconds.

[0]

subscribed value

10...150

(value needs to be divisible by 10 without remainder)

200...950

(value needs to be divisible by 50 without remainder)

1000...4000

(value needs to be divisible by 100 without remainder)

<Traffic handling priority>^(num)

This parameter specifies the relative importance for handling of all SDUs belonging to the UMTS bearer com-

pared to the SDUs of the other bearers.

[0]

subscribed

<PDP_type>^(str)

Packet Data Protocol Type

"IP"

Notes

• If parameters are not defined, the parameter default values depend on the HLR-stored subscribed default val-

ues.

• Definitions of parameters can be found in 3GPP TS 23.107

Page 321 of 567

11.8 AT+CGEQREQ

11.8

AT+CGEQREQ 3G Quality of Service Profile (Requested)

Syntax

Test Command

AT+CGEQREQ=?

Response(s)

+CGEQREQ: <PDP_type>, (list of supported <Traffic class>s), (list of supported <Maximum bitrate

UL>s), (list of supported <Maximum bitrate DL>s), (list of supported <Guaranteed bitrate UL>s),

(list of supported <Guaranteed bitrate DL>s), (list of supported <Delivery order>s), (list of

supported <Maximum SDU size>s), (list of supported <SDU error ratio>s), (list of supported

<Residual bit error ratio>s), (list of supported <Delivery of erroneous SDUs>s), (list of

supported <Transfer delay>s), (list of supported <Traffic handling priority>s)

Read Command

AT+CGEQREQ?

Response(s)

[+CGEQREQ: <cid>, <Traffic class>, <Maximum bitrate UL>, <Maximum bitrate DL>,

<Guaranteed bitrate UL>, <Guaranteed bitrate DL>, <Delivery order>, <Maximum SDU

size>, <SDU error ratio>, <Residual bit error ratio>, <Delivery of erroneous SDUs>,

<Transfer delay>, <Traffic handling priority>]

[+CGEQREQ: ...]

Write Command

AT+CGEQREQ=[<cid>[, <Traffic class>[, <Maximum bitrate UL>[, <Maximum bitrate DL>[,

<Guaranteed bitrate UL>[, <Guaranteed bitrate DL>[, <Delivery order>[, <Maximum SDU

size>[, <SDU error ratio>[, <Residual bit error ratio>[, <Delivery of erroneous

SDUs>[, <Transfer delay>[, <Traffic handling priority>]]]]]]]]]]]]]

Response(s)

ERROR

+CME ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

3GPP TS 27.007

Command Description

The test command returns values supported as a compound value.

The read command returns the current settings for each defined context.

The write command allows the TE to specify a Quality of Service Profile for the context identified by the (local)

context identification parameter <cid> which is used when the MT sends an Activate PDP Context Request

message to the network.

A special form of the write command, AT+CGEQREQ=<cid> causes the requested profile for context number

<cid> to become undefined.

AT&F and ATZ will undefine the QoS profiles of every context which is not active or not online.

Parameter Description

<cid>^(num)

Parameter specifies a particular PDP context definition. The parameter is local to the TE-MT interface and is

used in other PDP context-related commands.

1...2

Page 322 of 567

11.8 AT+CGEQREQ

<Traffic class>^(num)

conversational

streaming

interactive

background

[4]

subscribed value

<Maximum bitrate UL>^(num)

This parameter indicates the maximum number of kbits/s delivered to UMTS (up-link traffic) at a SAP. As an

example a bitrate of 32kbit/s would be specified as 32 (e.g. AT+CGEQREQ=...,32,...).

[0]

subscribed value

1...63

64...128

(value needs to be divisible by 8 without remainder)

256

512

<Maximum bitrate DL>^(num)

This parameter indicates the maximum number of kbits/s delivered by UMTS (down-link traffic) at a SAP. As an

example a bitrate of 32kbit/s would be specified as 32 (e.g. AT+CGEQREQ=...,32,...).

[0]

subscribed value

1...63

64...256

(value needs to be divisible by 8 without remainder)

512

<Guaranteed bitrate UL>^(num)

This parameter indicates the guaranteed number of kbits/s delivered to UMTS (up-link traffic) at a SAP (provided

that there is data to deliver). As an example a bitrate of

32kbit/s would be specified as

32 (e.g.

AT+CGEQREQ=...,32,...).

[0]

subscribed value

1...63

64...128

(value needs to be divisible by 8 without remainder)

<Guaranteed bitrate DL>^(num)

This parameter indicates the guaranteed number of kbits/s delivered by UMTS (down-link traffic) at a SAP (pro-

vided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as 32 (e.g.

AT+CGEQREQ=...,32,...).

[0]

subscribed value

1...63

64...256

(value needs to be divisible by 8 without remainder)

<Delivery order>^(num)

This parameter indicates whether the UMTS bearer shall provide in-sequence SDU delivery or not.

yes

[2]

subscribed value

Page 323 of 567

11.8 AT+CGEQREQ

<Maximum SDU size>^(num)

This parameter indicates the maximum allowed SDU size in octets.

[0]

subscribed value

10...1520

(value needs to be divisible by 10 without remainder)

1502

<SDU error ratio>^(str)

This parameter indicates the target value for the fraction of SDUs lost or detected as erroneous. SDU error ratio

is defined only for conforming traffic. The value is specified as "mEe". As an example a target SDU error ratio

of 5*10^-3 would be specified as "5E3" (e.g. AT+CGEQREQ=...,"5E3",...).

["0E0"]

subscribed value

"1E2"

"7E3"

"1E3"

"1E4"

"1E5"

"1E6"

"1E1"

<Residual bit error ratio>^(str)

This parameter indicates the target value for the undetected bit error ratio in the delivered SDUs. If no error

detection is requested, Residual bit error ratio indicates the bit error ratio in the delivered SDUs. The value is

specified as "mEe". As an example a target residual bit error ratio of 5*10^-3 would be specified as "5E3" (e.g.

AT+CGEQREQ=...,"5E3",...).

["0E0"]

subscribed value

"5E2"

"1E2"

"5E3"

"4E3"

"1E3"

"1E4"

"1E5"

"1E6"

"6E8"

<Delivery of erroneous SDUs>^(num)

This parameter indicates whether SDUs detected as erroneous shall be delivered or not.

yes

no detect

[3]

subscribed value

Page 324 of 567

11.8 AT+CGEQREQ

<Transfer delay>^(num)

This parameter indicates the targeted time between request to transfer an SDU at one SAP to its delivery at the

other SAP, in milliseconds.

[0]

subscribed value

10...150

(value needs to be divisible by 10 without remainder)

200...950

(value needs to be divisible by 50 without remainder)

1000...4000

(value needs to be divisible by 100 without remainder)

<Traffic handling priority>^(num)

This parameter specifies the relative importance for handling of all SDUs belonging to the UMTS bearer com-

pared to the SDUs of the other bearers.

[0]

subscribed

<PDP_type>^(str)

Packet Data Protocol Type

"IP"

Notes

• If parameters are not defined, the parameter default values depend on the HLR-stored subscribed default val-

ues.

• Definitions of parameters can be found in 3GPP TS 23.107

Page 325 of 567

11.9 AT+CGPADDR

11.9

AT+CGPADDR Show PDP address

Syntax

Test Command

AT+CGPADDR=?

Response(s)

[+CGPADDR: (list of defined <cid>s)]

Write Command

AT+CGPADDR=[<cid>[,<cid>]]

Response(s)

[+CGPADDR: <cid>, <PDP_address>]

ERROR

+CME ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

GSM 07.07

Command Description

The test command returns a list of defined <cid>s.

The write command returns a list of PDP addresses for the specified context identifiers. If no <cid> is specified,

the addresses for all defined contexts are returned.

Parameter Description

<cid>^(num)

A numeric parameter which specifies a particular PDP context definition (see AT+CGDCONT command).

<PDP_address>^(str)

A string that identifies the MT in the address space applicable to the PDP. The address may be static or dynamic.

Note

• If no <cid> is specified, the write command will return a list of all defined contexts.

Page 326 of 567

11.10 AT+CGQMIN

11.10

AT+CGQMIN Quality of Service Profile (Minimum acceptable)

Syntax

Test Command

AT+CGQMIN=?

Response(s)

+CGQMIN: <PDP_type>, (list of supported <precedence>s), (list of supported <delay>s), (list of

supported <reliability>s), (list of supported <peak>s), (list of supported <mean>s)

ERROR

+CME ERROR

Read Command

AT+CGQMIN?

Response(s)

[+CGQMIN: <cid>, <precedence>, <delay>, <reliability>, <peak>, <mean>]

[+CGQMIN: ...]

ERROR

+CME ERROR

Write Command

AT+CGQMIN=[<cid>[, <precedence>[, <delay>[, <reliability>[, <peak>[, <mean>]]]]]]

Response(s)

ERROR

+CME ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

GSM 07.07

Command Description

The test command returns values supported as a compound value. If the MT supports several PDP types, the

parameter value ranges for each PDP type are returned on a separate line.

The read command returns the current settings for each defined context.

This command allows the TE to specify a minimum acceptable profile which is checked by the MT against the

negotiated profile returned in the Activate PDP Context Accept message.

The set command specifies a profile for the context identified by the (local) context identification parameter,

<cid>.

A special form of the set command, AT+CGQMIN= <cid> causes the minimum acceptable profile for context

number <cid> to become undefined. In this case no check is made against the negotiated profile.

AT&F and ATZ will undefine the minimum QoS profiles of every context which is not active or not online.

Parameter Description

<cid>^(num)

Parameter specifies a particular PDP context definition. The parameter is local to the TE-MT interface and is

used in other PDP context-related commands.

1...2

Page 327 of 567

11.10 AT+CGQMIN

<precedence>^(num)

Precedence class

[0]

network subscribed value

High Priority

Service commitments shall be maintained ahead of precedence classes 2 and

Normal priority

Service commitments shall be maintained ahead of precedence class 3

Low priority

Service commitments shall be maintained

<delay>^(num)

Delay class

The delay parameter defines the end-to-end transfer delay incurred in the transmission of SDUs through the

GPRS network(s).

[0]

network subscribed value

1..4

SDU size: 128 octets:

Delay Class

Mean Transfer Delay

95 percentile

1 (Predictive)

<0.5

<1.5

2 (Predictive)

<25

3 (Predictive)

<50

<250

4 (Best Effort)

Unspecified

SDU size: 1024 octets:

Delay Class

Mean Transfer Delay

95 percentile

1 (Predictive)

<0.5

<1.5

2 (Predictive)

<25

3 (Predictive)

<50

<250

4 (Best Effort)

Unspecified

<reliability>^(num)

Reliability class

[0]

network subscribed value

Non real-time traffic, error-sensitive application that cannot cope with data loss

Non real-time traffic, error-sensitive application that can cope with infrequent

data loss

Non real-time traffic, error-sensitive application that can cope with data loss,

GMM/SM, and SMS

Real-time traffic, error-sensitive application that can cope with data loss

Real-time traffic, error non-sensitive application that can cope with data loss

<peak>^(num)

Peak throughput class (in octets per second).

[0]

network subscribed value

Page 328 of 567

11.10 AT+CGQMIN

Up to 1 000 (8 kbit/s).

Up to 2 000 (16 kbit/s).

Up to 4 000 (32 kbit/s).

Up to 8 000 (64 kbit/s).

Up to 16 000 (128 kbit/s).

Up to 32 000 (256 kbit/s).

Up to 64 000 (512 kbit/s).

Up to 128 000 (1024 kbit/s).

Up to 256 000 (2048 kbit/s).

<mean>^(num)

Mean throughput class(in octets per hour).

[0]

network subscribed value

100 (~0.22 bit/s)

200 (~0.44 bit/s)

500 (~1.11 bit/s)

1 000 (~2.2 bit/s)

2 000 (~4.4 bit/s)

5 000 (~11.1 bit/s)

10 000 (~22 bit/s)

20 000 (~44 bit/s)

50 000 (~111 bit/s)

100 000 (~0.22 kbit/s)

200 000(~0.44 kbit/s)

500 000(~1.11 kbit/s)

1 000 000 (~2.2 kbit/s)

2 000 000 (~4.4 kbit/s)

5 000 000 (~11.1 kbit/s)

10 000 000 (~22 kbit/s)

20 000 000 (~44 kbit/s)

50 000 000 (~111 kbit/s)

best effort

<PDP_type>^(str)

Packet Data Protocol Type

"IP"

Notes

• If parameters are not defined, the parameter default values depend on the HLR-stored subscribed default val-

ues.

• Definitions of parameters in GSM 02.60 and GSM 03.60 paragraph 15.2 "Quality of Service Profile".

Page 329 of 567

11.11 AT+CGQREQ

11.11

AT+CGQREQ Quality of Service Profile (Requested)

Syntax

Test Command

AT+CGQREQ=?

Response(s)

+CGQREQ: <PDP_type>, (list of supported <precedence>s), (list of supported <delay>s), (list of

supported <reliability>s), (list of supported <peak>s), (list of supported <mean>s)

Read Command

AT+CGQREQ?

Response(s)

[+CGQREQ: <cid>, <precedence>, <delay>, <reliability>, <peak>, <mean>]

[+CGQREQ: ...]

Write Command

AT+CGQREQ=[<cid>[, <precedence>[, <delay>[, <reliability>[, <peak>[, <mean>]]]]]]

Response(s)

ERROR

+CME ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

GSM 07.07

Command Description

The test command returns values supported as a compound value. If the MT supports several PDP types, the

parameter value ranges for each PDP type are returned on a separate line.

The read command returns the current settings for each defined context.

This command allows the TE to specify a Quality of Service Profile that is used when the MT sends an Activate

PDP Context Request message to the network.

The set command specifies a profile for the context identified by the (local) context identification parameter,

<cid>.

A special form of the set command, +CGQREQ=<cid> causes the requested profile for context number <cid>

to become undefined.

AT&F and ATZ will undefine the QoS profiles of every context which is not active or not online.

Parameter Description

<cid>^(num)

Parameter specifies a particular PDP context definition. The parameter is local to the TE-MT interface and is

used in other PDP context-related commands.

1...2

<precedence>^(num)

Precedence class

[0]

network subscribed value

High Priority

Service commitments shall be maintained ahead of precedence classes 2 and

Page 331 of 567

11.11 AT+CGQREQ

Normal priority

Service commitments shall be maintained ahead of precedence class 3

Low priority

Service commitments shall be maintained

<delay>^(num)

Delay class

This parameter defines the end-to-end transfer delay incurred in the transmission of SDUs through the GPRS

network(s).

[0]

network subscribed value

1..4

with SDU size = 128 octets:

Delay Class

Mean Transfer Delay

95 percentile

1 (Predictive)

<0.5

<1.5

2 (Predictive)

<25

3 (Predictive)

<50

<250

4 (Best Effort)

Unspecified

with SDU size = 1024 octets:

Delay Class

Mean Transfer Delay

95 percentile

1 (Predictive)

<0.5

<1.5

2 (Predictive)

<25

3 (Predictive)

<50

<250

4 (Best Effort)

Unspecified

<reliability>^(num)

Reliability class

[0]

network subscribed value

Non real-time traffic, error-sensitive application that cannot cope with data loss

Non real-time traffic, error-sensitive application that can cope with infrequent

data loss

Non real-time traffic, error-sensitive application that can cope with data loss,

GMM/SM, and SMS

Real-time traffic, error-sensitive application that can cope with data loss

Real-time traffic, error non-sensitive application that can cope with data loss

<peak>^(num)

Peak throughput class

in octets per second

[0]

network subscribed value

Up to 1 000 (8 kbit/s)

Up to 2 000 (16 kbit/s)

Up to 4 000 (32 kbit/s)

Up to 8 000 (64 kbit/s)

Up to 16 000 (128 kbit/s)

Page 332 of 567

11.11 AT+CGQREQ

Up to 32 000 (256 kbit/s)

Up to 64 000 (512 kbit/s)

Up to 128 000 (1024 kbit/s)

Up to 256 000 (2048 kbit/s)

<mean>^(num)

Mean throughput class

in octets per hour

[0]

network subscribed value

100 (~0.22 bit/s)

200 (~0.44 bit/s)

500 (~1.11 bit/s)

1 000 (~2.2 bit/s)

2 000 (~4.4 bit/s)

5 000 (~11.1 bit/s)

10 000 (~22 bit/s)

20 000 (~44 bit/s)

50 000 (~111 bit/s)

100 000 (~0.22 kbit/s)

200 000(~0.44 kbit/s)

500 000(~1.11 kbit/s)

1 000 000 (~2.2 kbit/s)

2 000 000 (~4.4 kbit/s)

5 000 000 (~11.1 kbit/s)

10 000 000 (~22 kbit/s)

20 000 000 (~44 kbit/s)

50 000 000 (~111 kbit/s)

best effort

<PDP_type>^(str)

Packet Data Protocol type

"IP"

Notes

• If parameters are not defined, the parameter default values depend on the HLR-stored subscribed default val-

ues.

• Definitions of parameters in GSM 02.60 and GSM 03.60 paragraph 15.2 "Quality of Service Profile".

Example

If some of the QoS parameters are omitted,they will keep their current value (or the default value if not specified

so far), e.g.:

AT+CGDCONT=1,"IP"

AT+CGQREQ=

Page 333 of 567

11.12 AT+CGREG

11.12

AT+CGREG GPRS Network Registration Status

AT+CGREG write command enables presentation of URC "+CGREG: <stat>" when <n>=1 and ME's GPRS net-

work registration status changes, or URC "+CGREG: <stat>, <lac>, <ci>" when <n>=2 and the current net-

work cell changes.

AT+CGREG read command queries the current URC presentation status and <stat> which shows whether the

network has currently indicated the registration of the ME. Location information elements <lac> and <ci> are

returned only if <n>=2 and ME is registered to the network.

Syntax

Test Command

AT+CGREG=?

Response(s)

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

Read Command

AT+CGREG?

Response(s)

+CGREG: <n>, <stat>[, <lac>, <ci>]

Write Command

AT+CGREG=[<n>]

Response(s)

ERROR

+CME ERROR

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

GSM 07.07

Unsolicited Result Codes

URC 1

+CGREG: <stat>

Indicates a change in the ME's GPRS network registration status.

URC 2

+CGREG: <stat>, <lac>, <ci>

Indicates a change in the ME's GPRS network registration status or a change of the network cell including

location information.

Parameter Description

<n>^(num)

0^(&F)(P)

Disable network registration unsolicited result code

Enable network registration URC "+CGREG: <stat>"

Enable network registration URC "+CGREG: <stat>, <lac>, <ci>"

Page 335 of 567

11.12 AT+CGREG

<stat>^(num)

Not registered, ME is not currently searching an operator to register to. The ME

is in GMM state GMM-NULL or GMM-DEREGISTERED-INITIATED.

GPRS service is disabled, the ME is allowed to attach to GPRS if requested by

the user.

Registered, home network. The ME is in GMM state GMM-REGISTERED or

GMM-ROUTING-AREA-UPDATING-INITIATED INITIATED on the home

PLMN

Not registered, but ME is currently trying to attach or searching an operator to

TERED-INITIATED. The GPRS service is enabled, but an allowable PLMN is

currently not available. The ME will start a GPRS attach as soon as an allow-

able PLMN is available.

Registration denied. The ME is in GMM state GMM-NULL. The GPRS service

is disabled, the ME is not allowed to attach to GPRS if requested by the user.

Unknown

Registered, roaming. The ME is in GMM state GMM-REGISTERED or GMM-

ROUTING-AREA-UPDATING-INITIATED on a visited PLMN.

<lac>^(str)

Two byte location area code in hexadecimal format.

<ci>^(str)

Two byte cell ID in hexadecimal format.

Note

• When the module is GPRS attached and a PLMN reselection occurs to a non-GPRS network or to a network

where the SIM is not subscribed to for using GPRS, the resulting GMM (GPRS mobility management) state

according to GSM 24.008 is REGISTERED/NO CELL, meaning that the read command will still show

<stat>=1 or <stat>=5.

Page 336 of 567

11.13 AT+CGSMS

11.13

AT+CGSMS Select service for MO SMS messages

Syntax

Test Command

AT+CGSMS=?

Response(s)

+CGSMS: (list of supported <service>s)

Read Command

AT+CGSMS?

Response(s)

+CGSMS: <service>

Write Command

AT+CGSMS=[<service>]

Response(s)

ERROR

+CME ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3

Charge

Last

GSM 07.07

Command Description

The test command is used for requesting information on which services and service preferences can be set by

using the AT+CGSMS write command

The read command returns the currently selected service or service preference.

The write command is used to specify the service or service preference that the MT will use to send MO SMS

messages. If parameter <service> is not given, the current value remains unchanged.

Parameter Description

<service>^(num)

A numeric parameter which indicates the service or service preference to be used. Parameter is global for all

interfaces and volatile.

GPRS

Circuit switched

GPRS preferred (use circuit switched SMS transfer if GPRS SMS transfer is

not possible, for example when the mobile is not GPRS attached or the network

does not support SMS over GPRS)

3^(&F)(P)

Circuit switched preferred (use GPRS if circuit switched is not available)

Note

• Sending SMS via GPRS is only possible when mobile is attached using AT+CGATT.

Page 337 of 567

11.14 AT^SGACT

11.14

AT^SGACT Query all PDP context activations

Syntax

Test Command

AT^SGACT=?

Response(s)

^SGACT: (range of supported <ifc>s) , (range of supported <state>s)

Read Command

AT^SGACT?

Response(s)

[^SGACT: <ifc>, <cid>, <state>]

[^SGACT: ...]

Exec Command

AT^SGACT

Response(s)

^SGACT: <sum>

Reference(s)

PIN ASC0 ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Command Description

The test command returns supported interfaces and states.

The read command lists the activation states for all activated PDP contexts of the ME. Contexts, which are cre-

ated internally by the GPRS modem compatibility commands, will displayed only, if they are activated. The Out-

put of this command is unsorted.

The exec command returns the sum of all activated PDP contexts of the ME.

Parameter Description

<ifc>^(num)

Interface

Indicates the interface on which a particular PDP context was defined. Every PDP context defined with the com-

mand AT+CGDCONT or internally by the GPRS modem compatibility commands is identified one-to-one by its

(local) context identifier and the interface on which it was defined. The range of supported interfaces is returned

by the test command.

ASC0 or Multiplex channel 1

ASC1 or Multiplex channel 2

USB or Multiplex channel 3

<cid>^(num)

PDP context identifier

The interface local identifier which was used to define a PDP context using the command AT+CGDCONT or which

was created internally by using the GPRS modem compatibility commands ATD*98# or ATD*99#. The range

of supported values is returned by the AT+CGDCONT test command. Values 3 and 4 will be used by the GPRS

modem compatibility commands ATD*98# or ATD*99# if no context identifier was specified as the command

was invoked.

Page 338 of 567

11.15 AT^SGAUTH

11.15

AT^SGAUTH Set type of authentication for PPP connection

Syntax

Test Command

AT^SGAUTH=?

Response(s)

^SGAUTH: (list of supported <auth>s)

ERROR

+CME ERROR

Read Command

AT^SGAUTH?

Response(s)

^SGAUTH: <auth>

ERROR

+CME ERROR

Write Command

AT^SGAUTH=<auth>

Response(s)

ERROR

+CME ERROR

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<auth>^(num)

Indicates types of supported authentication.

none

PAP

CHAP

3^(&F)(P)

MS-CHAP-V1, CHAP and PAP

Page 340 of 567

11.16 AT^SGCONF

11.16

AT^SGCONF Configuration of GPRS related Parameters

Syntax

Test Command

AT^SGCONF=?

Response(s)

^SGCONF: (list of supported <llc_pdu_length_U>s), (list of supported <llc_pdu_length_I>s), (list of

supported <GPRS msclass>es)

Read Command

AT^SGCONF?

Response(s)

^SGCONF: <llc_pdu_length_U>, <llc_pdu_length_I>, <GPRS msclass>

Write Command

AT^SGCONF=[<llc_pdu_length_U>][, [<llc_pdu_length_I>][, [<GPRS msclass>]]]

Response(s)

ERROR

+CME ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

Parameter Description

<llc_pdu_length_U>^(num)

The maximum number of octets in an information field of Unnumbered (U) frames. Parameter is non-volatile.

No negotiation with network (500 will be used).

140...500^(D)...1520

Lower values diminish performance.

<llc_pdu_length_I>^(num)

The maximum number of octets in an information field of Combined Information (I) frames. Parameter is non-

volatile.

No negotiation with network (500 will be used).

140...500^(D)...1520

Lower values diminish performance.

<GPRS msclass>^(num)

GPRS Multislot Class. The value can be one of the classes indicated with the Test command. The value set is

volatile and powerup value is the maximum allowed.

Notes

•

+CME ERROR: invalid index: Parameter is out of range

•

+CME ERROR: operation temporary not allowed: The command is blocked as long as GPRS is already in

use (as long as mobile is GPRS attached).

• Writing to user profile with AT&W and restoring with AT&F are not supported.

Page 341 of 567

11.17 ATA

11.17

ATA Manual response to a network request for PDP context acti-

vation

The V.250 ATA command may be used to accept a network request for a PDP context activation announced by

the unsolicited result codes "RING" or "+CRING: GPRS". The MT responds with CONNECT, enters V.250 online

data state and follows the same procedure as it would after having received a AT+CGANS=1 with no <L2P> or

<cid> values specified.

If you try to answer a request which is no longer present or which is already answered by another instance, NO

CARRIER is returned.

Syntax

Exec Command

ATA

Response(s)

CONNECT

NO CARRIER

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

GSM 07.07

Page 342 of 567

11.18 ATD*99#

11.18

ATD*99# Request GPRS service

This command causes the MT to perform whatever actions are necessary to establish a communication between

the TE and the external PDN.

The V.250 'D' (Dial) command causes the MT to enter the V.250 online data state and, with the TE, to start the

specified layer 2 protocol. No further commands may follow on the AT command line. GPRS attachment and

PDP context activation procedures may take place prior to or during the PDP startup if they have not already

been performed using the AT+CGATT and AT+CGACT commands.

Examples on how to use this command are provided in "Section 11.22, Using GPRS AT commands (Examples)".

To confirm acceptance of the command before entering the V.250 online data state command will respond with

CONNECT.

When the layer 2 protocol has terminated, either as a result of an orderly shut down of the PDP or an error, the

MT enters V.250 command state and returns NO CARRIER (for details refer to Section 11.5.1, Automatic deac-

tivation of PDP context during dial-up PPP).

Syntax

Exec Command

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

Response(s)

CONNECT

NO CARRIER

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

GSM 07.07

Parameter Description

<called_address>^(str)

This parameter is currently not used and needs not to be specified.

<L2P>^(str)

Layer 2 protocol to be used between the TE and MT.

"PPP"

layer 2 protocol PPP

"1"

layer 2 protocol PPP

<cid>^(num)

Parameter specifies a particular PDP context definition (see AT+CGDCONT command). If no context is specified,

an internal context with default properties is used (see AT+CGDCONT, AT+CGQREQ and AT+CGQMIN).

1...2

Notes

• If TC65 is in dedicated mode, command returns the result code BUSY.

• ATD is used as a standard V.250 AT command, too.

Page 343 of 567

11.19 ATD*98#

11.19

ATD*98# Request GPRS IP service

This command causes the MT to perform whatever actions are necessary to establish a communication between

the TE and the external PDN.

The V.250 'D' (Dial) command causes the MT to enter the V.250 online data state and, with the TE, to start the

layer 2 protocol.

GPRS attachment and PDP context activation procedures may take place prior to or during the PDP startup if

they have not already been performed using the AT+CGATT and AT+CGACT commands.

To confirm acceptance of the command before entering the V.250 online data state command will respond with

CONNECT.

When the layer 2 protocol has terminated, either as a result of an orderly shut down of the PDP or an error, the

MT enters V.250 command state and returns NO CARRIER (for details refer to Section 11.5.1, Automatic deac-

tivation of PDP context during dial-up PPP).

Syntax

Exec Command

ATD*98[* <cid>]#

Response(s)

CONNECT

NO CARRIER

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

GSM 07.07

Parameter Description

<cid>^(num)

Parameter specifies a particular PDP context definition (see AT+CGDCONT command). If no context is specified,

an internal context with default properties is used (see AT+CGDCONT, AT+CGQREQ and AT+CGQMIN).

1...2

Notes

• If TC65 is in dedicated mode, command returns the result code BUSY.

• ATD is used as a standard V.250 AT command, too.

Page 344 of 567

11.20 ATH

11.20

ATH Manual rejection of a network request for PDP context acti-

vation

The V.250 ATH command may be used to deactivate all PDP contexts which are active or online on the same

interface. This command should not be used to deactivate PDP contexts during the implicit PDP context deacti-

vation procedure which is started automatically after LCP termination or by dropping the DTR line (if AT&D2 is

configured). For details refer to Section 11.5.1, Automatic deactivation of PDP context during dial-up PPP.

The ATH command may also be used to reject a network request for PDP context activation announced by the

unsolicited result codes "RING: GPRS" or "+CRING: GPRS".

Syntax

Exec Command

ATH

Response(s)

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

GSM 07.07

Notes

• In contrast to GSM 07.07 it is possible to cancel a connection with ATH after a break. This is done for com-

patibility reasons due to the "dial-up network" drivers of Microsoft Windows.

• ATH is used as a standard V.250 AT command, too.

• If ATH is used to reject a network request for PDP context activation, then other PDP contexts on the same

interface which are active or online will not be deactivated.

Page 345 of 567

11.21 ATS0

11.21

ATS0

Automatic response to a network request for PDP context

activation

The V.250 ATS0=<n> (Automatic answer) command may be used to turn off (n=0) and on (n>0) the automatic

response to a network request for a PDP context activation. See also "3GPP TS 27.007 (GSM 07.07): AT com-

mand set for User Equipment (UE)".

When the ATS0=<n> (<n> > 0) command is received, the MT will attempt to perform a GPRS attach if not yet

attached and if configured to do so (see AT^SCFG, parameter <gs0aa>). Subsequently, the MT will announce

a network request for PDP context activation by issuing the URC RING or CRING to the TE, followed by the inter-

mediate result code CONNECT. The MT then enters V.250 online data state and follows the same procedure as

it would after receiving a AT+CGANS=1 command with no <L2P> or <cid> values specified.

ATS0=0 does not perform an automatic GPRS detach.

Syntax

Read Command

ATS0?

Response(s)

<n>

Write Command

ATS0=<n>

Response(s)

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

GSM 07.07

Parameter Description

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

000^(&F)

Disables automatic answer mode.

001-255

Enables automatic answering after specified number of rings.

Notes

• If different settings are used on each interface, and a request for PDP context activation is received, the inter-

face 'wins' which is idle and uses the smallest ATS0 value.

• When a network request for PDP context activation is answered automatically and another AT command is

issued at the same time on the same interface then this AT command will not be executed. Any response

relates to the automatic context activation procedure. If the AT command which caused the collision was a

CS data call, the CONNECT response does not pertain to this data call but to GPRS. This can be detected if

ATX is not set to 0. The CS data call will issue CONNECT <text>, GPRS will issue CONNECT only.

• A network request for PDP context activation has a maximum duration of approximately 40 seconds (for

details see GSM 04.08). A RING/CRING URC is issued every 5 seconds, so setting parameter <n> to values

greater than 7 will not allow a successful context activation and is not recommended.

• Automatic GPRS attach will not be performed on recalling a stored user profile with ATZ or on power-up, even

though a value <n> greater than 0 was stored in the user profile with AT&W.

• If AT^SCFG="GPRS/ATS0/withAttach","on" is selected, but the automatic GPRS attach attempt fails (e.g. the

network rejects the attach request), the ATS0 write command ends up with "ERROR" or "+CME ERROR:

unknown" after approx. 5 minutes, though the new <n> value takes effect. This is necessary because ATS0

is used for circuit switched calls too.

• ATS0 write command is PIN protected.

Page 346 of 567

11.22 Using GPRS AT commands (Examples)

11.22

Using GPRS AT commands (Examples)

Examples

EXAMPLE 1

Defining and using a Context Definition ID (CID):

Every time a CID is used as a parameter for a GPRS command the CID has to be defined before by using

the AT+CGDCONT command. To get the parameter of a CID use the AT+CGDCONT read option. If the response

of 'AT+CGDCONT?' is OK only, there is no CID defined.

AT+CGDCONT?

There is no CID defined

All parameters of the CID are initiated by NULL or not present values, and the CID itself is set to be undefined.

To define a CID use the AT+CGDCONT command with at least one CID parameter. At the moment the mobile

supports CID 1 and CID 2 by using the AT+CGDCONT command.

Define CID 1 and set the PDP type to IP, access point name and IP address are not set:

AT+CGDCONT=1,"IP"

Define CID 2 and sets PDP type, APN and IP addr:

AT+CGDCONT=2,"IP", "internet.t-d1.gprs", 111.222.123.234

A following read command will respond:

AT+CGDCONT?

+CGDCONT:1,"IP","","",0,0

+CGDCONT:2,"IP","internet.t-d1.gprs",111.222.123.234

Set the CID 1 to be undefined:

AT+CGDCONT=1

A following read command will respond:

AT+CGDCONT?

+CGDCONT:2,"IP","internet.t-d1.gprs",111.222.123.234

Page 347 of 567

11.22 Using GPRS AT commands (Examples)

EXAMPLE 2

Quality of Service (QoS) is a special parameter of a CID which consists of several parameters itself.

The QoS consists of

- the precedence class

- the delay class

- the reliability class

- the peak throughput class

- the mean throughput class

and is divided in "requested QoS" and "minimum acceptable QoS".

All parameters of the QoS are initiated by default to the "network subscribed value (= 0)" but the QoS itself is

set to be undefined. To define a QoS use the AT+CGQREQ or AT+CGQMIN command.

Overwrite the precedence class of QoS of CID 1 and set the QoS of CID 1 to be present:

AT+CGQREQ=1,2

A following read command will respond:

AT+CGQREQ?

+CGQREQ: 1,2,0,0,0,0

All QoS values of CID 1 are set to network subscribed now, except precedence class which is set to 2. Now

set the QoS of CID 1 to not present:

AT+CGQREQ=1

Once defined, the CID it can be activated. To activate CID 2 use:

AT+CGACT=1,2

If the CID is already active, the mobile responds OK at once.

If no CID and no STATE is given, all defined CIDs will be activated by:

AT+CGACT=

If no CID is defined the mobile responds +CME ERROR: invalid index

Remark: If the mobile is NOT attached by AT+CGATT=1 before activating, the attach is automatically done by

the AT+CGACT command.

After defining and activating a CID it may be used to get online by:

AT+CGDATA="PPP",1

CONNECT

The mobile is connected using the parameters of CID 1.

AT+CGDATA=

CONNECT

The mobile is connected using default parameters (<L2P>="PPP" and

<cid> as described for command AT+CGDATA).

The mobile supports Layer 2 Protocol (L2P) PPP only.

Remark: If the mobile is NOT attached by AT+CGATT=1 and the CID is NOT activated before connecting,

attaching and activating is automatically done by the AT+CGDATA command.

Some providers (e.g. Vodafone or E-Plus) require to use an APN to establish a GPRS connection. So if you

use the Microsoft Windows Dial-Up Network and ATD*9... to connect to GPRS you must provide the context

definition as part of the modem definition (Modem properties/Connection/Advanced.../Extra settings). As an

alternative, you can define and activate the context in a terminal program (e.g. Microsoft Hyperterminal) and

then use the Dial-Up Network to send only the ATD command.

Page 348 of 567

11.23 Using the GPRS dial command ATD

11.23

Using the GPRS dial command ATD

Example

In addition to the GPRS AT commands you can use the "D" command to dial into to the GPRS network.

There are two GPRS Service Codes for the ATD command: Values 98 and 99.

Examples:

ATD*99#

CONNECT

Establish a connection by service code 99.

ATD*99*123.124.125.126*PPP*1#

CONNECT

Establish a connection by service code

99, IP

address 123 and L2P = PPP and using CID 1.

The CID has to be defined by AT+CGDCONT.

ATD*99**PPP#

CONNECT

Establish a connection by service code 99 and L2P

= PPP.

ATD*99***1#

CONNECT

Establish a connection by service code 99 and using

CID 1.

ATD*99**PPP*1#

CONNECT

Establish a connection by service code 99 and L2P

= PPP and using CID 1. The CID has to be defined

by AT+CGDCONT.

ATD*98#

CONNECT

Establish a connection by service code 98.

ATD*98*1#

CONNECT

Establish an IP connection by service code 98 using

CID 1. The CID has to be defined by AT+CGDCONT.

Page 349 of 567

12. FAX Commands

12.

FAX Commands

This chapter describes the AT commands used for fax communications. Please note that fax related commands

are not supported by Java.

If the ME is acting as a fax modem for a PC based fax application (e.g. "WinFax") it is necessary to select the

proper Service Class (Fax Class) provided by the ME. The ME reports its Service Class capabilities, i.e. the cur-

rent setting and the range of services available. This is provided by the AT+FCLASS command.

Service Classes supported by the ME:

AT+FCLASS Parameter

Service class

Reference, Standard

Data modem

e.g. TIA/EIA-602 or ITU V.250

Service Class 1

EIA/TIA-578-A

During an active fax connection the AT parser functionality on the used channel is limited to the AT commands

which according to the ITU V.250 and T.31 specifications are mandatory for fax communications. The functions

of these AT commands are usually supported by commonly used fax applications.

12.1

FAX parameters

This section describes the parameter <mod> used by some of the fax-specific AT commands. To find out the

value(s) actually supported by the <mod> parameter use the test commands either in on-hook or off-hook mode.

Parameter Description

<mod>^(num)

Modulation scheme

V21 Ch2 - 300 bps

V.27ter - 2400 bps

V.27ter - 7200 bps

V.29 - 7200 bps

V.29 - 9600 bps

Note

• For AT+FRH and AT+FTH, parameter <mod> can take value 3 only, while AT+FRM and AT+FTM never support

<mod>=3.

12.1.1

Fax Result Codes

Table 12.1: Fax Result Codes

Result Code

Meaning

+FCERROR

This facsimile error message notifies the DTE that the DCE has

received a different signal (tone or carrier) than expected. This

allows the DTE to recover by requesting the DCE to look for an

alternative tone or carrier signal.

Page 350 of 567

12.2 AT+FCLASS

12.2

AT+FCLASS Fax: Select, read or test service class

AT+FCLASS sets the ME to a particular mode of operation (data, fax). This allows the ME to process information

in a manner suitable for that type of information.

Syntax

Test Command

AT+FCLASS=?

Response(s)

(list of supported <n>s)

Read Command

AT+FCLASS?

Response(s)

<n>

Write Command

AT+FCLASS=<n>

Response(s)

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

EIA/TIA-592-A

Parameter Description

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

0^(&F)

Data (e.g. EIA/TIA-602 or ITU V.250)

Fax class 1 (EIA/TIA-578-A, Service Class 1)

Notes

• Using Error Correcting Mode (ECM) when sending FAXes over GSM should be avoided.

• If <n> is set to 1, all incoming calls will be answered as fax calls when ATA is issued on multiplexer channel

1 resp. ASC0. For calls explicitly signaled as voice or data calls, this procedure will fail with result code "NO

CARRIER", but the incoming call will continue to ring.

It is possible to change the setting of <n> to 0 while the call is ringing, and accept the call afterwards with ATA.

Page 351 of 567

12.3 AT+FRH

12.3

AT+FRH Receive Data Using HDLC Framing

The AT+FRH command enables the TA to receive frames using the HDLC protocol and the modulation scheme

<mod>=3.

An ERROR response code results if the write command is issued while the modem is on-hook. The test com-

mand can be used either in on-hook or off-hook mode to check the value supported by the <mod> parameter.

Syntax

Test Command

AT+FRH=?

Response(s)

+FRH:(list of <mod>s)

Write Command

AT+FRH=<mod>

Response(s)

CONNECT

If error is related to ME functionality

ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

TIA/EIA-578

Note

• TC65 supports only <mod>=3.

Page 352 of 567

12.4 AT+FRM

12.4

AT+FRM Receive Data

The AT+FRM command causes the TA to enter the receive mode, using one of the modulation schemes defined

in Section 12.1, FAX parameters.

An ERROR response code results if the write command is issued while the modem is on-hook. The test com-

mand can be used in on-hook or off-hook mode to check the modulation schemes supported by TC65.

Syntax

Test Command

AT+FRM=?

Response(s)

(list of <mod>s)

Write Command

AT+FRM=<mod>

Response(s)

CONNECT

If error is related to ME functionality:

ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

TIA/EIA-578

Note

•

<mod>= 3 is not possible.

Page 353 of 567

12.5 AT+FRS

12.5

AT+FRS Receive Silence

<time>=n causes the TA to report an OK result code to the TE after the specified period of silence was detected

on the line.

The command is aborted if any character is received by the TE. The modem discards the aborting character and

issues an OK result code. An ERROR response code results if this command is issued while the mode is on-

hook.

Syntax

Write Command

AT+FRS=<time>

Response(s)

If error is related to ME functionality:

ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

TIA/EIA-578

Parameter Description

<time>^(num)

Number of 10 millisecond intervals

0...255

Page 354 of 567

12.6 AT+FTH

12.6

AT+FTH Transmit Data Using HDLC Framing

The AT+FTH command causes the TA to transmit data using the HDLC protocol and the modulation scheme

<mod>=3.

An ERROR response code results if the write command is issued while the modem is on-hook. The test com-

mand can be used either in on-hook or off-hook mode to check the value supported by the <mod> parameter.

Syntax

Test Command

AT+FTH=?

Response(s)

+FTH:(list of <mod>s)

Write Command

AT+FTH=<mod>

Response(s)

CONNECT

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

TIA/EIA-578

Note

• TC65 supports only <mod>=3.

Page 355 of 567

12.7 AT+FTM

12.7

AT+FTM Transmit Data

The AT+FTM command causes the TA to transmit data, using one of the modulation schemes defined in Section

12.1, FAX parameters.

An ERROR response code results if the write command is issued while the modem is on-hook. The test com-

mand can be used in on-hook or off-hook mode to check the modulation schemes supported by TC65.

Syntax

Test Command

AT+FTM=?

Response(s)

(list of <mod>s)

Write Command

AT+FTM=<mod>

Response(s)

CONNECT

If error is related to ME functionality:

ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

TIA/EIA-578

Note

•

<mod>= 3 is not possible

Page 356 of 567

13. Short Message Service (SMS) Commands

13.

Short Message Service (SMS) Commands

The AT Commands described in this chapter allow an external application to use the Short Message Service with

the TC65.

13.1

SMS parameters

Parameter Description

<ackpdu>^(num)

Format is same for <pdu> in case of SMS, but without GSM 24.11 SC address field and parameter shall be

bounded by double quote characters like a normal string type rarameter

<alpha>^(str)(+CSCS)

String type alphanumeric representation of <da> or <oa> corresponding to the entry found in phonebook; imple-

mentation of this feature is manufacturer specific

<cdata>^(num)

Command Data

GSM 03.40 TP-Command-Data in text mode responses; ME/TA converts each 8-bit octet into two IRA character

long hexadecimal numbers (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50

and 65))

<ct>^(num)

Command Type

GSM 03.40 TP-Command-Type in integer format

[0]...255

<da>^(num)(+CSCS)

Destination Address

GSM 03.40 TP- Destination-Address Address-Value field in string format; BCD numbers (or GSM default alpha-

bet characters) are converted into characters; type of address given by <toda>

<data>^(num)(+CSCS)

User Data

In case of SMS: GSM 03.40 TP-User-Data in text mode responses; format:

• If <dcs> indicates that GSM 03.38 default alphabet is used and <fo> indicates that GSM 03.40 TP-User-

Data-Header-Indication is not set: ME/TA converts GSM alphabet into current TE character set according to

rules covered in Annex A.

• If <dcs> indicates that 8-bit or UCS2 data coding scheme is used, or <fo> indicates that GSM 03.40 TP-

User-Data-Header-Indication is set: ME/TA converts each 8-bit octet into hexadecimal numbers con-taining

two IRA characters (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65).

In case of CBS: GSM 03.41 CBM Content of Message in text mode responses; format:

• If <dcs> indicates that GSM 03.38 default alphabet is used: ME/TA converts GSM alphabet into current TE

character set according to rules covered in Annex A.

• If <dcs> indicates that 8-bit or UCS2 data coding scheme is used: ME/TA converts each 8-bit octet into hexa-

decimal numbers containing two IRA characters.

Page 358 of 567

13.1 SMS parameters

<dt>^(num)

Discharge Time

GSM 03.40 TP-Discharge-Time in time-string format: "yy/MM/dd,hh:mm:ss+zz", where characters indicate year

(two last digits), month, day, hour, minutes, seconds and time zone. For example, 6th of May 1994, 22:10:00

GMT+2 hours equals "94/05/06,22:10:00+08"

<ieia>^(num)

IEIa (Information Element Identifier octet) of the concatenated SMS.

Concatenated short messages, 8-bit reference number

Concatenated short messages, 16-bit reference number

<index>^(num)

Integer type; value in the range of location numbers supported by the associated memory

<length>^(num)

Message Length

Integer type value indicating in the text mode (AT+CMGF=1) the length of the message body <data> (or

<cdata>) in characters; or in PDU mode (AT+CMGF=0), the length of the actual TP data unit in octets (i.e. the

RP layer SMSC address octets are not counted in the length) In text mode, the maximum length of an SMS

depends on the used coding scheme: It is 160 characters if the 7 bit GSM coding scheme is used, and 140 char-

acters according to the 8 bit GSM coding scheme.

If the SMS message format is ''text mode'' (AT+CMGF=1) and the character set is set to ''UCS2'' with AT+CSCS

and the SMS is also coded as "UCS2" (see <dcs> of AT+CSMP), then the length is in octets instead of charac-

ters.

For concatenated SMS messages the maximum length will be reduced by the length of the user data header

with respect to <ieia> (6 bytes for <ieia>=8 and 7 bytes for <ieia>=16). In the case of 8-bit data, the max-

imum length of the short message field is: 140 octets - (6 or 7) = 134 or 133. In the case of GSM 7 bit default

alphabet data, the maximum length of the short message is (140 - (6 or 7))*8/7 = 153 or 152 characters. In the

case of 16 bit UC2 data, the maximum length of the short message is: (140 - (6 or 7))/2)= 67 or 66 characters.

<max>^(num)

Maximum number of all segments to be concatenated into one SMS, beginning with 1.

<max>=0 means: ignore the value. This will result in a non-concatenated SMS.

0...255

<mem1>^(str)

Memory to be used when listing, reading and deleting messages:

"SM"

SIM message storage

"ME"

Mobile Equipment message storage

"MT"^(D)

Sum of "SM" and "ME" storages

<mem2>^(str)

Memory to be used when writing and sending messages:

"SM"

SIM message storage

"ME"

Mobile Equipment message storage

"MT"^(D)

Sum of "SM" and "ME" storages

Page 359 of 567

13.1 SMS parameters

<mem3>^(str)

Received messages will be placed in this memory storage if routing to TE is not set. See command AT+CNMI

with parameter <mt>=2.

"SM"

SIM message storage

"MT"^(D)

Sum of "SM" and "ME" storages

<mid>^(num)

Message Identifier

GSM 03.41 CBM Message Identifier in integer format

<mn>^(num)

Message Number

GSM 03.40 TP-Message-Number in integer format

<mr>^(num)

Message Reference

GSM 03.40 TP-Message-Reference in integer format

<oa>^(num)(+CSCS)

Originating Address

GSM 03.40 TP-Originating-Address Address-Value field in string format; BCD numbers (or GSM default alpha-

bet characters) are converted into characters; type of address given by <tooa>

<page>^(num)

Page Parameter

GSM 03.41 CBM Page Parameter bits 4-7 in integer format

<pages>^(num)

Page Parameter

GSM 03.41 CBM Page Parameter bits 0-3 in integer format

<pdu>^(num)

In the case of SMS: GSM 04.11 SC address followed by GSM 03.40 TPDU in hexadecimal format: ME/TA con-

verts each octet of TP data unit into hexadecimal numbers containing two IRA characters (e.g. octet with integer

value 42 is presented to TE as two characters 2A (IRA 50 and 65)). In the case of CBS: <ra> GSM 03.40 TP-

Recipient-Address Ad-dress-Value field in string format; BCD numbers (or GSM default alphabet characters)

are converted into characters; type of address given by <tora>

<ra>^(num)(+CSCS)

Recipient Address

GSM 03.40 TP-Recipient-Address Address-Value field in string format; BCD numbers (or GSM default alphabet

characters) are converted to characters of the currently selected TE character set

(refer to command

AT+CSCS.); type of address given by <tora>

Page 360 of 567

13.1 SMS parameters

<ref>^(num)

Reference number to identify all segments of the concatenated SMS (i.e. the number needs to be the same for

each segment). If <ieia>=8 then max=255, otherwise 65535.

0...255

0...65535

<sca>^(num)(+CSCS)

Service Center Address

GSM 04.11 RP SC address Address-Value field in string format; BCD numbers (or GSM default alphabet char-

acters) are converted to characters of the currently selected TE character set (refer to command AT+CSCS); type

of address given by <tosca>

<scts>^(num)

Service Centre Time Stamp

GSM 03.40 TP-Service-Centre-Time-Stamp in time-string format (refer <dt>)

<seq>^(num)

Sequence number of the concatenated SMS beginning with 1. The number must be incremented by one for

each segment of the concatenated short message.

<seq>=0 means: ignore the value. This will result in a non-concatenated SMS.

0...255

<sn>^(num)

Serial Number

GSM 03.41 CBM Serial Number in integer format

<st>^(num)

Status

GSM 03.40 TP-Status in integer format

0...255

<stat>^(str)

Message status

3GPP 27.005 Interface of SMS and CB. Indicates the status of message in memory.

Description

text mode (<mode>=1)

PDU mode (<mode>=0)

Default

Received unread mes-

"REC UNREAD"

for SMS reading com-

sages

mands

Received read messages

"REC READ"

Stored unsent messages

"STO UNSENT"

for SMS writing com-

mands

Stored sent messages

"STO SENT"

All messages

"ALL"

Page 361 of 567

13.1 SMS parameters

<toda>^(num)

Type of Destination Address

GSM 04.11 TP-Destination-Address Type-of-Address octet in integer format (when first character of <da> is +

(IRA 43) default is 145, otherwise default is 129)

0...255

<tooa>^(num)

Type of Originating Address

GSM 04.11 TP-Originating-Address Type-of-Address octet in integer format (default refer <toda>)

<tora>^(num)

Type of Recipient Address

GSM 04.11 TP-Recipient-Address Type-of-Address octet in integer format (default refer <toda>)

<tosca>^(num)

Type of Service Center Address

GSM 04.11 RP SC address Type-of-Address octet in integer format (default refer <toda>)

Page 362 of 567

13.2 AT+CMGC

13.2

AT+CMGC Send an SMS command

Syntax

Test Command

AT+CMGC=?

Response(s)

Write Command

If text mode (see AT+CMGF=1)

AT+CMGC=<fo>, <ct>[, <pid>[, <mn>[, <da>[, <toda>]]]]<CR> Text can be entered <CTRL-Z>/<ESC>

Response(s)

+CMGC: <mr>[, <scts>]

If sending fails

ERROR

+CMS ERROR

Write Command

If PDU mode (see AT+CMGF=0)

AT+CMGC=<length><CR> PDU can be entered <CTRL-Z>/<ESC>

Response(s)

+CMGC: <mr>[, <ackpdu>]

If sending fails

ERROR

+CMS ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

GSM 07.05

Notes

• After invoking the commands AT+CMGW, AT+CMGS or AT+CMGC it is necessary to wait for the prompt ">"

before entering text or PDU. After the prompt a timer will be started to observe the input.

• At baudrates below 19200 it is recommended to use the line termination character only (refer to ATS3, default

<CR>) before entering the text or PDU. Use of the line termination character followed by the response format-

ting character (refer to ATS4, default <LF> can cause problems

Page 363 of 567

13.3 AT+CMGD

13.3

AT+CMGD Delete short message

The write command deletes a short message from the preferred message storage <mem1> location <index>.

Syntax

Test Command

AT+CMGD=?

Response(s)

Write Command

AT+CMGD=<index>

Response(s)

ERROR

+CMS ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

GSM 07.05

Notes

• If there is no short message stored at the selected index, the response is OK too.

• Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data

may not yet be accessible, resulting in a short delay before the requested AT command response is returned.

See Section 23.1, Restricted access to SIM data after SIM PIN authentication for further detail.

Page 364 of 567

13.5 AT+CMGL

13.5

AT+CMGL List SMS messages from preferred store

The write command returns messages with status value <stat> from message storage <mem1> to the TE. If the

status of the message is 'received unread', the status in the storage changes to 'received read'.

The execute command is the same as the write command with the given default for <stat>.

Syntax

Test Command

AT+CMGL=?

Response(s)

+CMGL: (list of supported <stat>s)

Exec Command

AT+CMGL

Response(s)

+CMGL: (see write command for default of <stat>)

Write Command

AT+CMGL=<stat>

Response(s)

Output if text mode (AT+CMGF=1) and command successful:

For SMS- SUBMITs and/or SMS-DELIVERs

+CMGL: <index>, <stat>, <oa>/<da>, [<alpha>], [<scts>][, <tooa>/<toda>, <length>]

<data>

[... ]

For SMS-STATUS-REPORTs

+CMGL: <index>, <stat>, <fo>, <mr>, [<ra>], [<tora>], <scts>, <dt>, <st>

[... ]

For SMS-Commands

+CMGL: <index>, <stat>, <fo>, <ct>

[... ]

Output if PDU mode AT+CMGF=0 and command successful:

For SMS-SUBMITs and/or SMS-DELIVERs

+CMGL: <index>, <stat>, [<alpha>], <length>

<pdu>

[... ]

If error is related to ME functionality

ERROR

+CMS ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2

MUX3

Charge

Last

GSM 07.05

Page 366 of 567

13.5 AT+CMGL

Notes

• The selected <mem1> can contain different types of SMs (e.g. SMS-DELIVERs, SMS-SUBMITs, SMS-STA-

TUS-REPORTs and SMS-COMMANDs), the response may be a mix of the responses of different SM types.

TE application can recognize the response format by examining the third response parameter.

• The parameters <ra> and <tora> will only be displayed if parameter <ra> of the AT^SSCONF command is

set to 1.

• Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data

may not yet be accessible, resulting in a short delay before the requested AT command response is returned.

See Section 23.1, Restricted access to SIM data after SIM PIN authentication for further detail.

• If the ME is Java controlled, take into account that the AT Command API can handle responses up to a length

of 1024 bytes. To avoid any longer reponses it is recommended not to read the entire range of phonebook

entries at a time.

Page 367 of 567

13.6 AT+CMGR

13.6

AT+CMGR Read SMS messages

The write command returns SMS message with location value <index> from message storage <mem1> to the

TE. If status of the message is 'received unread', status in the storage changes to 'received read'.

Syntax

Test Command

AT+CMGR=?

Response(s)

Write Command

AT+CMGR=<index>

Response(s)

Output if text mode (AT+CMGF=1) and command successful:

For SMS-DELIVER

+CMGR: <stat>, <oa>, [<alpha>], <scts>[, <tooa>, <fo>, <pid>, <dcs>, <sca>, <tosca>,

<length>]

<data>

[... ]

For SMS-SUBMIT

+CMGR: <stat>, <da>, [<alpha>][, <toda>, <fo>, <pid>, <dcs>, [<vp>], <sca>, <tosca>, <length>]

<data>

[... ]

For SMS-STATUS-REPORT

+CMGR: <stat>, <fo>, <mr>, [<ra>], [<tora>], <scts>, <dt>, <st>

<data>

[... ]

For SMS-Commands

+CMGR: <stat>, <fo>, <ct>[, <pid>, [<mn>], [<da>], [<toda>], <length>]

<data>

[... ]

Output if PDU mode (AT+CMGF=0) and command successful:

For SMS-SUBMITs and/or SMS-DELIVERs

+CMGR: <stat>, [<alpha>], <length>

<pdu>

[... ]

ERROR

+CMS ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1

MUX2

MUX3

Charge

Last

GSM 07.05

Page 368 of 567

13.6 AT+CMGR

Notes

• Response if AT+CMGR is used to read an empty record index: +CMGR: 0,,0

• Response if AT+CMGR is used to read a non-existent record index: +CMS ERROR: invalid memory index

• The parameters <ra> and <tora> will only be displayed if parameter <ra> of the AT^SSCONF command is

set to 1.

• Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data

may not yet be accessible, resulting in a short delay before the requested AT command response is returned.

See Section 23.1, Restricted access to SIM data after SIM PIN authentication for further detail.

Page 369 of 567

13.7 AT+CMGS

13.7

AT+CMGS Send Short Message

The write command transmits a short message from TE to network (SMS-SUBMIT).

After invoking the write command wait for the prompt ">" and then start to write the message. To send the mes-

sage simply enter <CTRL-Z>. After the prompt a timer will be started to observe the input.

To abort sending use <ESC>. Abortion is acknowledged with "OK", though the message will not be sent.

The message reference <mr> is returned to the TE on successful message delivery. The value can be used to

identify the message in a delivery status report provided as an unsolicited result code.

Syntax

Test Command

AT+CMGS=?

Response(s)

Write Command

If text mode (see AT+CMGF=1)

AT+CMGS=<da>[, <toda>]<CR> Text can be entered. <CTRL-Z>/<ESC>

Response(s)

+CMGS: <mr>[, <scts>]

If sending fails see notes below.

Write Command

If PDU mode (see AT+CMGF=0)

AT+CMGS=<length><CR> PDU can be entered. <CTRL-Z>/<ESC>

Response(s)

+CMGS: <mr>[, <ackpdu>]

If sending fails see notes below.

Reference(s)

PIN ASC0 ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

GSM 07.05

Notes

• If sending fails, for example, if a message is too long, the result code depends on the current setting of the

AT^SM20 command:

If the AT^SM20 <CmgwMode> equals 1 (factory default) any failure to send a message is responded with "OK".

Users should be aware, that despite the "OK" response, the message will not be sent to the subscriber.

If the AT^SM20 <CmgwMode> equals 0 any failure to send a message is responded with "ERROR".

• If sending fails due to timeout, then

AT^SM20 <CmgwMode>=1 causes "+CMS ERROR: Unknown error" to be returned;

AT^SM20 <CmgwMode>=0 causes "+CMS ERROR: timer expired" to be returned.

• Note that some providers do not recognize an @ symbol used in a short message. A widely used alternative

is typing "*" as defined in GSM 03.40 (GPP TS 23.40).

• All characters entered behind the prompt ">" will be recognized as GSM characters. For example, "Back-

space" (ASCII character 8) does not delete a character, but will be inserted into the short message as an addi-

tional physical character. As a result, the character you wanted to delete still appears in the text, plus the GSM

code equivalent of the Backspace key.

Page 370 of 567

13.7 AT+CMGS

• Message Length in Text Mode

The maximum length of a short message depends on the used coding scheme: It is 160 characters if the 7

bit GSM coding scheme is used, and 140 characters according to the 8 bit GSM coding scheme.

In case UCS2 character set selected it is highly recommended to set Data Coding Scheme (<dcs> of

AT+CSMP) to 16-bit data, otherwise the length of sms user data is restricted to 88 octets. Even better for mes-

sages with UCS2 character set is the PDU Mode.

• At baudrates lower than 19200 it is recommended to use the line termination character only (refer to <n> of

ATS3, default <CR>) before entering text or PDU. Use of the line termination character followed by the

response formatting character (see <n> of ATS4, default <LF>) can cause problems.

Page 371 of 567

13.8 AT+CMGW

13.8

AT+CMGW Write Short Messages to Memory

The execute and write commands transmit a short message (either SMS-DELIVER or SMS-SUBMIT) from TE

to memory storage <mem2>. Memory location <index> of the stored message is returned. Message status will

be set to 'stored unsent' unless otherwise given in parameter <stat>.

After invoking the execute or write command wait for the prompt ">" and then start to write the message. To save

the message simply enter <CTRL-Z>. After the prompt a timer will be started to observe the input.

To abort writing use <ESC>. Abortion is acknowledged with "OK", though the message will not be saved.

Syntax

Test Command

AT+CMGW=?

Response(s)

Exec Command

If text mode (see AT+CMGF=1):

AT+CMGW

Response(s)

<CR> Text can be entered. <CTRL-Z>/<ESC>

+CMGW: <index>

If writing fails

ERROR

+CMS ERROR

Write Command

If text mode (see AT+CMGF=1):

AT+CMGW=<oa>/<da>[, [<tooa>/<toda>][, <stat>]]<CR> Text can be entered. <CTRL-Z>/<ESC>

Response(s)

+CMGW: <index>

If writing fails see notes below.

Write Command

If PDU mode (see AT+CMGF=0):

AT+CMGW=<length>[, <stat>]<CR> PDU can be entered. <CTRL-Z>/<ESC>

Response(s)

+CMGW: <index>

If writing fails see notes below.

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

GSM 07.05

Notes

• If writing fails, for example, if a message is too long, the result code depends on the current setting of the

AT^SM20 command:

If the AT^SM20 <CmgwMode>=1 (factory default) any failure to send a message is responded with "OK". Users

should be aware, that despite the "OK" response, the message will not be written to the selected SMS stor-

age.

If the AT^SM20 <CmgwMode> equals 0 any failure to write a message is responded with "ERROR".

Page 372 of 567

13.8 AT+CMGW

• If writing fails due to timeout, then

AT^SM20 <CmgwMode>=1 causes "+CMS ERROR: Unknown error" to be returned;

AT^SM20 <CmgwMode>=0 causes "+CMS ERROR: timer expired" to be returned.

• Note that some providers do not recognize an @ symbol used in a short message. A widely used alternative

is typing "*" as defined in GSM 03.40 (GPP TS 23.40).

• For baudrates lower than 19200 it is recommended to use the line termination character only (refer to ATS3=

<n>, default <CR>) before entering the text or PDU. Use of the line termination character followed by the

response formating character (see ATS4= <n>, default <LF>) may cause problems.

• SMS-COMMANDs and SMS-STATUS-REPORTs cannot be stored in text mode.

• All characters entered behind the ">" prompt will be recognized as GSM characters. For example, "Back-

space" (ASCII character 8) does not delete a character, but will be inserted into the short message as an addi-

tional physical character. As a result, the character you wanted to delete still appears in the text, plus the GSM

code equivalent of the Backspace key.

• Message Length in Text Mode

The maximum length of a short message depends on the used coding scheme: It is 160 characters if the 7

bit GSM coding scheme is used, and 140 characters according to the 8 bit GSM coding scheme.

In case UCS2 character set selected it is highly recommended to set Data Coding Scheme (<dcs> of

AT+CSMP) to 16-bit data, otherwise the length of sms user data is restricted to 88 octets. Even better for mes-

sages with UCS2 character set is the PDU Mode.

• The length of 8-bit data coded short messages has to be greater than 0.

Page 373 of 567

13.9 AT+CMSS

13.9

AT+CMSS Send short messages from storage

The write command sends message with location value <index> from message storage <mem2> to the network

(SMS-SUBMIT or SMS-COMMAND). If new recipient address <da> is given for SMS-SUBMIT, it shall be used

instead of the one stored with the message. Reference value <mr> is returned to the TE on successful message

delivery. Value can be used to identify message upon unsolicited delivery status report result code.

If the optional parameter <da> is given, the old status of the short message at <index> remains unchanged

(see <stat>).

Syntax

Test Command

AT+CMSS=?

Response(s)

Write Command

If text mode (AT+CMGF=1):

AT+CMSS=<index>[, <da>[, <toda>]]

Response(s)

+CMSS: <mr>[, <scts>]

If sending fails

ERROR

+CMS ERROR

Write Command

If PDU mode (AT+CMGF=0):

AT+CMSS=<index>[, <da>[, <toda>]]

Response(s)

+CMSS: <mr>[, <ackpdu>]

If sending fails

ERROR

+CMS ERROR

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

GSM 07.05

Page 374 of 567

13.10 AT+CNMA

13.10

AT+CNMA New Message Acknowledgement to ME/TE, only

phase 2+

The write / execute command confirms successful receipt of a new message (SMS-DELIVER or SMS-STATUS-

REPORT) routed directly to the TE. TA shall not send another +CMT or +CDS result code to TE until previous

one is acknowledged. If ME does not receive acknowledgement within required time (network time-out), ME

sends RP-ERROR to the network. TA shall automatically disable routing to TE by setting both <mt> and <ds>

values of AT+CNMI to zero.

Syntax

Test Command

AT+CNMA=?

Response(s)

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

Exec Command

AT+CNMA

Response(s)

ERROR

+CMS ERROR

Write Command

AT+CNMA=<n>

Response(s)

ERROR

+CMS ERROR

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

GSM 07.05

Parameter Description

<n>^(num)

Parameter required only for PDU mode.

Command operates similarly as in text mode.

Notes

• The execute / write command shall only be used when AT+CSMS parameter <service> equals 1 (= phase

2+).

• The execute command can be used no matter whether text mode or PDU mode is activated. The write com-

mand is designed for the PDU mode only.

• If multiplex mode is activated (AT+CMUX=0) the AT+CNMI parameter will be set to zero on all channels, if one

channel fails to acknowledge an incoming message within the required time.

Page 375 of 567

13.11 AT+CNMI

13.11

AT+CNMI New short Message Indication

The write command selects the procedure how the receipt of new short messages from the network is indicated

to the TE when TE is active, e.g. DTR signal is ON. If TE is inactive (e.g. DTR signal is OFF), message receiving

should be done as specified in GSM 03.38. If the DTR signal is not available or the state of the signal is ignored

(V.250 command AT&D0, reliable message transfer can be assured by using AT+CNMA acknowledgment proce-

dure. The rules <mt>=2 and <mt>=3 for storing received messages are possible only if phase 2+ compatibility

is activated with AT+CSMS=1. The parameter <ds>=1 is only available in phase 2+

Syntax

Test Command

AT+CNMI=?

Response(s)

+CNMI: (list of supported<mode>s), (list of supported <mt>s), (list of supported <bm>s), (list of supported

<ds>s), (list of supported <bfr>s)

Read Command

AT+CNMI?

Response(s)

+CNMI: <mode>, <mt>, <bm>, <ds>, <bfr>

Write Command

AT+CNMI=[<mode>][, <mt>][, <bm>][, <ds>][, <bfr>]

Response(s)

ERROR

+CMS ERROR

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

GSM 07.05

Unsolicited Result Codes

URC 1

<mt>=1:

+CMTI: <mem3>, <index>

Indicates that new message has been received

URC 2

<mt>=2 (PDU mode enabled):

+CMT: <length><CR><LF><pdu>

Indicates that new message has been received

URC 3

<mt>=2 (text mode enabled):

+CMT: <oa>, <scts>[, <tooa>, <fo>, <pid>, <dcs>, <sca>, <tosca>,

Indicates that new message has been received

Page 376 of 567

13.11 AT+CNMI

URC 4

<bm>=2 (PDU mode enabled):

+CBM: <length><CR><LF><pdu>

Indicates that new cell broadcast message has been received

URC 5

<bm>=2 (text mode enabled):

+CBM: <sn>, <mid>, <dcs>, <page>, <pages><CR><LF><data>

Indicates that new cell broadcast message has been received

URC 6

<ds>=1 (PDU mode enabled):

+CDS: <length><CR><LF><pdu>

Indicates that new SMS status report has been received

URC 7

<ds>=1 (text mode enabled):

+CDS: <fo>, <mr>[, <ra>][, <tora>], <scts>, <dt>, <st>

Indicates that new SMS status report has been received

URC 8

<ds>=2:

+CDSI: <mem3>, <index>

Indicates that new SMS status report has been received

Parameter Description

<mode>^(num)(&W)

[0]^(&F)

Buffer unsolicited result codes in the TA. If TA result code buffer is full, indica-

tions can be buffered in some other place or the oldest indications may be dis-

carded and replaced with the new received indications.

Discard indication and reject new received message unsolicited result codes

when TA-TE link is reserved (e.g. in on-line data mode). Otherwise forward

them directly to the TE.

Buffer unsolicited result codes in the TA when TA-TE link is reserved (e.g. in

online data mode) and flush them to the TE after reservation. Otherwise for-

ward them directly to the TE.

Forward unsolicited result codes directly to the TE. When TA-TE link is

reserved (e.g. in online data mode) the URCs are signaled according to the

AT^SCFG parameters <uri>, <udri> and <urat>

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

Rules for storing received short messages depend on the relevant data coding method (refer to GSM 03.38),

preferred memory storage (AT+CPMS) setting and this value.

Note: If AT command interface is acting as the only display device, the ME must support storage of class 0 mes-

sages and messages in the message waiting indication group (discard message)

[0]^(&F)

No SMS-DELIVER indications are routed to the TE.

If SMS-DELIVER is stored in ME/TA, indication of the memory location is

routed to the TE using unsolicited result code:

Page 377 of 567

13.11 AT+CNMI

SMS-DELIVERs, except class 2 messages and messages in the message

waiting indication group (store message) are routed directly to the TE using

unsolicited result code:

Class 3 SMS-DELIVERs are routed directly to the TE using unsolicited result

codes defined in <mt>=2. Messages of other data coding schemes result in

indication as defined in <mt>=1.

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

Rules for storing received CBMs depend on the relevant data coding method (refer to GSM 03.38), the setting

of Select CBM Types (AT+CSCB) and this value:

[0]^(&F)

No CBM indications are routed to the TE.

New CBMs are routed directly to the TE using unsolicited result code:

Class 3 CBMs are routed directly to TE using unsolicited result codes defined

in <bm>=2.

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

[0]^(&F)

No SMS-STATUS-REPORTs are routed to the TE.

SMS-STATUS-REPORTs are routed to the TE using unsolicited result code:

If SMS-STATUS-REPORT is routed into ME/TA, indication of the memory

location is routed to the TE using unsolicited result code:

<bfr>^(num)(&V)

[1]^(&F)

TA buffer of unsolicited result codes defined within this command is cleared

when <mode> changes from 0 to 1...3.

<index>^(num)

Integer type; value in the range of location numbers supported by the associated memory

Notes

• Parameters <mt>=2,3 and <ds>=1 are only available with GSM phase 2+ (see AT+CSMS=1). Incoming SMs

or Status Reports have to be acknowledged with AT+CNMA=0 when using these phase 2+ parameters.

• Requirements specific to Multiplex mode:

In multiplex mode (AT+CMUX=0) only one channel can use a phase 2+ parameter. The parameter for <mt>

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

all AT+CNMI parameter in all channels will be set to zero.

• If the ME operates on different instances (MUX channels 1, 2, 3 or ASC0/ASC1) avoid different settings for

routing and indicating short messages. For example, if messages shall be routed directly to one instance of

the TE (set with AT+CNMI, AT^SSDA), it is not possible to activate the presentation of URCs with AT+CMER

or AT+CNMI on another instance. Any attempt to activate settings that conflict with existing settings on

another interface, will result in CME ERROR, or accordingly CMS ERROR.

• Handling of Class 0 short messages:

If the host application is provided with a display and AT^SSDA=1 has been set Class 0 short messages can

be displayed immediately.

If the host application does not include a display, ME handles Class 0 short messages as though there was

no message class, i.e. it will ignore bits 0 and 1 in the <dcs> and normal rules for exceeded memory capacity

shall apply. This approach is compliant with GSM 03.38 .

• The parameters <ra> and <tora> will only be displayed if <ra> of the AT^SSCONF command is set to 1.

• If either a SM or a Status Report is not acknowledged, all AT+CNMI parameter in all channels will be set to

zero.

Page 378 of 567

13.12 AT+CPMS

13.12

AT+CPMS Preferred SMS message storage

The write command selects memory storages <mem1>,<mem2>, <mem3> to be used for reading, writing, etc.

Syntax

Test Command

AT+CPMS=?

Response(s)

+CPMS: (list of supported <mem1>s), (list of supported <mem2>s), (list of supported <mem3>s)

Read Command

AT+CPMS?

Response(s)

+CPMS: <mem1>, <used1>, <total1>, <mem2>, <used2>, <total2>, <mem3>, <used3>, <total3>

ERROR

+CMS ERROR

Write Command

AT+CPMS=<mem1>[, <mem2>[, <mem3>]]

Response(s)

+CPMS: <used1>, <total1>, <used2>, <total2>, <used3>, <total3>

ERROR

+CMS ERROR

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

GSM 07.05

Parameter Description

<used1>^(num)

Number of messages currently in <mem1>

<used2>^(num)

Number of messages currently in <mem2>

<used3>^(num)

Number of messages currently in <mem3>

<total1>^(num)

Number of messages storable in <mem1>

<total2>^(num)

Number of messages storable in <mem2>

<total3>^(num)

Number of messages storable in <mem3>

Page 379 of 567

13.12 AT+CPMS

Notes

•

The Mobile Equipment storage ''ME'' offers space for 25 short messages, see <mem1>.

•

''MT'' is the sum of ''ME'' (= 25 locations) and ''SM'' (capacity varies with SIM card). The indices <index> of

the ''MT'' storage are dependent on the order selected with AT^SSMSS

•

The <mem1>, <mem2> and <mem3> parameter will be stored in non-volatile memory.

•

The user should be aware that the setting ''MT'' involves ''ME'' and ''SM'', with ''ME'' being filled up first. If the

''ME'' storage is full, TC65 will proceed with the ''SM'' storage.

Incoming Class 1 short messages (ME specific) will be preferably stored to ''ME'' and may be transferred to

the ''SM'' storage if ''ME'' is used up.

Incoming Class 2 messages (SIM specific) will be stored to the SIM card only, no matter whether or not there

is free ''ME'' space. As a result, the ^SMGO: 2 indication (see AT^SMGO) may be presented without prior indi-

cation of ^SMGO: 1. For more information regarding SIM and ME specific message classes refer to <dcs>

and the following specifications: GSM 03.38 and 3GPP TS23038.

•

Multiplexer: In Multiplex mode or when the two physical serial interfaces are connected, the parameter

<mem3> will be the same on all instances, but the settings of <mem1> and <mem2> may vary on each channel

/ interface. As a result, changes on parameter <mem1> and/or <mem2> befor activating the multiplexer or dif-

ferences values for other instanes can result in not desired behaviours like different outputs for AT+CMGL and

so on.

•

While <mem3> equals ''SM'' and <mem1> equals ''ME'' it is possible that, after deleting short messages from

''ME'', the freed space on ''ME'' is reclaimed for new incoming short messages, when there is no space left on

the ''SM'' storage. As it is often the clients concern to have received short messages stored only to the SIM

card, inconsistent settings should be generally avoided. This can be achieved simply by using the same

parameter for all memory indices.

•

Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data

may not yet be accessible, resulting in a short delay before the requested AT command response is returned.

See Section 23.1, Restricted access to SIM data after SIM PIN authentication for further detail.

•

The indices <index> of the storage are dependent on the order selected with AT^SSMSS.

Page 380 of 567

13.13 AT+CSCA

13.13

AT+CSCA SMS Service Center Address

Write command updates the SMSC address, through which mobile originated SMs are transmitted. In text mode,

setting is used by send and write commands. In PDU mode, setting is used by the same commands, but only

when the length of the SMSC address coded into the <pdu> parameter equals zero.

Syntax

Test Command

AT+CSCA=?

Response(s)

Read Command

AT+CSCA?

Response(s)

+CSCA: <sca>, <tosca>

Write Command

AT+CSCA=<sca>[, <tosca>]

Response(s)

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3

Charge

Last

GSM 07.05

Notes

• In case of using no parameter after AT+CSCA= the content of <sca> will be deleted.

• This command writes the service center address to non-volatile memo.

• The SMS service center address should be entered as specified by the service provider.

Page 381 of 567

13.14 AT+CSCB

13.14

AT+CSCB Select Cell Broadcast Message Indication

The test command returns the supported modes as a compound value.

The write command selects which types of CBMs are to be received by the ME.

Syntax

Test Command

AT+CSCB=?

Response(s)

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

Read Command

AT+CSCB?

Response(s)

+CSCB: <mode>, <mids>, <dcss>

Write Command

AT+CSCB=[<mode>[, <mids>[, <dcss>]]]

Response(s)

Reference(s)

PIN ASC0 ASC1

USB MUX1

MUX2

MUX3

Charge

Last

GSM 07.05

Parameter Description

<mode>^(num)

Message mode

[0]^(&F)

Accept messages that are defined in <mids> and <dcss>

Forbid messages that are defined in <mids> and <dcss>

<mids>^(str)

Cell Broadcast Message ID specification

• For <mode>=0: Six different possible combinations of CBM IDs (e.g. "0,1,5,320-478,922,2000-3000"), default

is empty string.

In certain configurations, e.g. if using SIMs that contain data in Elementary File EF-CBMID (Cell Broadcast

Message Identifier for Data download) less than six combinations may be available.

To access a SIM's Elementary File data refer to command AT+CRSM.

• For <mode>=1: One CBM ID or range of IDs (e.g. "320-478"), default is empty string.

<dcss>^(str)

CBM data coding scheme specification

All different possible combinations of CBM data coding schemes (e.g. "0-3,5"). Using default empty string leads

to get all CBMs independent of their dcss.

A given <dcss> replaces any former value and is used for consecutive requests.

Page 382 of 567

13.15 AT+CSDH

13.15

AT+CSDH Show SMS text mode parameters

The write command sets whether or not detailed header information is shown in text mode result codes.

Syntax

Test Command

AT+CSDH=?

Response(s)

+CSDH: ((list of supported <show>s)

Read Command

AT+CSDH?

Response(s)

+CSDH:<show>

Write Command

AT+CSDH=<show>

Response(s)

+CSDH: <show>

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

GSM 07.05

Parameter Description

<show>^(num)(&W)

[0]^(&F)

Do not show header values defined in commands AT+CSCA and AT+CSMP

(<sca>, <tosca>,<fo>,<vp>, <pid> and <dcs>) nor <length>, <toda> or

<tooa> in "+CMTI", AT+CMGL, AT+CMGR result codes for SMS-DELIVERs and

SMS-SUBMITs in text mode; for SMS-COMMANDs in +CMGR result code, do

not show <pid>,<mn>,<da>, <toda>, <length> or <cdata>

Show the values in result codes

Page 383 of 567

13.16 AT+CSMP

13.16

AT+CSMP Set SMS text Mode Parameters

The write command selects values for additional parameters needed when the short message is sent to the net-

work or placed in a storage when text format message mode is selected.

It is possible to set the validity period starting from the time when the short message is received by the SMSC

(<vp> is in range 0... 255) or define the absolute time of the validity period termination (<vp> is a string). The

format of <vp> is given by <fo>. If TA supports the enhanced validity period format, see GSM 03.40), it shall be

given as a hexadecimal coded string (e.g. <pdu>) with quotes.

Syntax

Test Command

AT+CSMP=?

Response(s)

Read Command

AT+CSMP?

Response(s)

+CSMP:<fo>, <vp>/ <scts>, <pid>, <dcs>

Write Command

AT+CSMP=<fo>[, <vp>/<scts>[, <pid>[, <dcs>]]]

Response(s)

+CSMP: <index>

If sending fails

ERROR

+CMS ERROR

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

GSM 07.05

Parameter Description

<fo>^(num)

First Octet

depending on the command or result code: first octet of GSM 03.40 SMS-DELIVER, SMS-SUBMIT (default 17),

SMS-STATUS-REPORT, or SMS-COMMAND (default 2) in integer format

0...17^(&F)...255

<vp>^(num)

Depending on SMS-SUBMIT <fo> setting: GSM 03.40 TP-Validity-Period either in integer format or in time-

string format (refer <dt>)

0...167^(&F)...255

<dcs>^(num)

Data Coding Scheme

GSM 03.38 SMS Data Coding Scheme, or Cell Broadcast Data Coding Scheme in integer format

0^(&F)...247

Page 384 of 567

13.17 AT+CSMS

13.17

AT+CSMS Select Message Service

Syntax

Test Command

AT+CSMS=?

Response(s)

+CSMS: (list of supported<service>s)

Read Command

AT+CSMS?

Response(s)

+CSMS: <service>, <mt>, <mo>, <bm>

Write Command

AT+CSMS=<service>

Response(s)

+CSMS: <mt>, <mo>, <bm>

ERROR

+CMS ERROR

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

GSM 07.05

Parameter Description

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

0^(&F)

GSM 03.40 and GSM 03.41 (the syntax of SMS AT commands is compatible

with GSM 07.05 Phase 2 version 4.7.0; Phase 2+ features which do not require

new command syntax may be supported, e.g. correct routing of messages with

new Phase 2+ data coding schemes)

GSM 03.40 and GSM 03.41 (the syntax of SMS AT commands is compatible

with GSM 07.05 Phase 2+ version; the requirement of <service> setting 1 is

mentioned under corresponding command descriptions).

<mt>^(num)

Mobile Terminated Messages:

Type not supported

Type supported

<mo>^(num)

Mobile Originated Messages:

Type not supported

Type supported

Page 386 of 567

13.17 AT+CSMS

<bm>^(num)

Broadcast Type Messages:

Type not supported

Type supported

Notes

• If CSMS mode is switched from Phase 2+ to Phase 2 and one or more AT+CNMI Parameter are Phase 2+

specific a '+CMS ERROR: unknown error' will appear. It is recommended to switch the AT+CNMI Parameters

to Phase 2 specific values before entering Phase 2.

• Phase 2+ (<service>=1) must be set before the following features can be used:

- Configuring procedures for indicating received short messages with the AT+CNMI parameters <mt>=2 or

<mt>=3 and <ds>=1.

- Acknowledging incoming short messages with AT+CNMA.

- Receiving Status Reports and acknowledging them with AT+CNMA.

Page 387 of 567

13.18 AT^SCML

13.18

AT^SCML List Concatenated Short Messages from preferred

store

The write command returns messages with status value <stat> from message storage <mem1> to the TE. If the

status of the message is 'received unread', the status in the storage changes to 'received read'. The execute

command is the same as the write command with the given default for <stat>. See notes of AT+CMGL.

Syntax

Test Command

AT^SCML=?

Response(s)

^SCML: (list of supported <stat>s)

Exec Command

AT^SCML

Response(s)

^SCML: (see write command for default of <stat>)

Write Command

AT^SCML=<stat>

Response(s)

Output if text mode (AT+CMGF=1) and command successful:

For SMS-SUBMITs and/or SMS-DELIVERs

^SCML: <index>, <stat>, <oa>/<da>, [<alpha>], [<scts>][, <tooa>/<toda>, <length>][, <seq>,

<max>, <ieia>, <ref>]

<data>

[... ]

For SMS-STATUS-REPORTs

^SCML: <index>, <stat>, <fo>, <mr>, [<ra>], [<tora>], <scts>, <dt>, <st>

[... ]

For SMS-Commands

^SCML: <index>, <stat>, <fo>, <ct>

[... ]

Output if PDU mode (AT+CMGF=0) and command successful:

For SMS- SUBMITs and/or SMS-DELIVERs

^SCML: <index>, <stat>, [<alpha>], <length>

<pdu>

[... ]

If error is related to ME functionality

ERROR

+CMS ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2

MUX3

Charge

Last

SIEMENS

Page 388 of 567

13.19 AT^SCMR

13.19

AT^SCMR Read Concatenated Short Messages

The write command returns the message with location value <index> from message storage <mem1> to the TE.

If the status of the message is 'received unread', the status in the storage changes to 'received read'. See notes

of AT+CMGR.

Syntax

Test Command

AT^SCMR=?

Response(s)

Write Command

AT^SCMR=<index>

Response(s)

Output if text mode (AT+CMGF=1) and command successful:

For SMS-DELIVER

^SCMR: <stat>, <oa>, [<alpha>], <scts>[, <tooa>, <fo>, <pid>, <dcs>, <sca>, <tosca>,

<length>][, <seq>, <max>, <ieia>, <ref>]

<data>

[... ]

For SMS-SUBMIT

^SCMR: <stat>, <da>, [<alpha>][, <toda>, <fo>, <pid>, <dcs>, [<vp>], <sca>, <tosca>,

<length>][, <seq>, <max>, <ieia>, <ref>]

<data>

[... ]

For SMS-STATUS-REPORT

^SCMR: <stat>, <fo>, <mr>, [<ra>], [<tora>], <scts>, <dt>, <st>

<data>

[... ]

For SMS-Commands

^SCMR: <stat>, <fo>, <ct>[, <pid>, [<mn>], [<da>], [<toda>], <length>]

<data>

[... ]

Output if PDU mode (AT+CMGF=0) and command successful:

For SMS-SUBMITs and/or SMS-DELIVERs

^SCMR: <stat>, [<alpha>], <length>

<pdu>

[... ]

ERROR

+CMS ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Page 389 of 567

13.20 AT^SCMS

13.20

AT^SCMS Send Concatenated Short Messages

Sending a concatenated message is similar to sending a "normal" message, except that each segment of the

concatenated message must be identified by the additional parameters <seq>, <ieia> and <ref>. To send all

segments of the message one by one, the AT^SCMS write command must be executed for each segment.

The write command transmits one segment of a concatenated short message from TE to network (SMS-SUB-

MIT).

After invoking the write command wait for the prompt ">" and then start to write the message. To send the mes-

sage simply enter <CTRL-Z>. After the prompt a timer will be started to observe the input.

To abort sending use <ESC>. Abortion is acknowledged with "OK", though the message will not be sent.

The message reference <mr> is returned to the TE on successful message delivery. The value can be used to

identify the message in a delivery status report provided as an unsolicited result code.

Syntax

Test Command

AT^SCMS=?

Response(s)

Write Command

Command syntax for text mode (see AT+CMGF=1):

AT^SCMS=<da>[, <toda>], <seq>, <max>, <ieia>, <ref><CR> Text can be entered <CTRL-Z>/<ESC>

Response(s)

+CMGS: <mr>[, <scts>]

If sending fails

ERROR

+CMS ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

Notes

• See notes provided for AT+CMGS.

• Command is only available if AT+CMGF=1.

Page 390 of 567

13.21 AT^SCMW

13.21

AT^SCMW Write Concatenated Short Messages to Memory

Writing a concatenated message to the memory is similar to writing a "normal" message, except that each seg-

ment of the concatenated message must be identified by the additional parameters <seq>, <ieia> and <ref>.

To store all segments of the message one by one, the AT^SCMW write command must be executed for each seg-

ment.

The write commands transmits one segment of a concatenated SMS (either SMS-DELIVER or SMS-SUBMIT)

from TE to memory storage <mem2>. Memory location <index> of the stored message is returned. Message

status will be set to 'stored unsent' unless otherwise given in parameter <stat>.

Syntax

Test Command

AT^SCMW=?

Response(s)

Write Command

If text mode (see AT+CMGF=1)

AT^SCMW=<oa>/<da>, [<tooa>/<toda>][, <stat>], <seq>, <max>, <ieia>, <ref><CR> Text can be

entered. <CTRL-Z>/<ESC>

Response(s)

^SCMW: <index>

If writing fails

ERROR

+CMS ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

Notes

• Command is only available if AT+CMGF=1.

• To send or delete a concatenated short message please use the known SMS commands, see AT+CMSS for

sending and AT+CMGD for deleting.

• See notes provided for AT+CMGW.

Page 391 of 567

13.22 AT^SLMS

13.22

AT^SLMS List SMS Memory Storage

AT^SLMS indicates the max. capacity of each SMS storage type and the number of locations currently used.

Syntax

Test Command

AT^SLMS=?

Response(s)

Exec Command

AT^SLMS

Response(s)

^SLMS: ''MT'',<total3>, <used3>

^SLMS: ''SM'',<total1>, <used1>

^SLMS: ''ME'',<total2>, <used2>

ERROR

+CMS ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

Parameter Description

<total1>^(num)

Maximum number of messages storable in the SMS memory of the SIM (physical storage "SM")

<total2>^(num)

Maximum number of messages storable in the SMS memory of the Mobile Equipment (physical storage "ME")

<total3>^(num)

Sum of "SM" and "ME", indicated as "MT". Maximum number of all messages storable in the SIM memory and

the Mobile Equipment memory.

<used1>^(num)

Number of messages currently stored in the SMS memory of the SIM (physical storage "SM")

<used2>^(num)

Number of messages currently stored in the SMS memory of the Mobile Equipment (physical storage "ME")

<used3>^(num)

Concatenated logical SMS storages of SIM ("SM") and Mobile Equipment ("ME"). Sum of all messages currently

stored, indicated as "MT".

Note

• Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data

may not yet be accessible, resulting in a short delay before the requested AT command response is returned.

See Section 23.1, Restricted access to SIM data after SIM PIN authentication for further detail.

Page 392 of 567

13.23 AT^SMGL

13.23

AT^SMGL List Short Messages from preferred store without set-

ting status to REC READ

The write command allows to select a status type and lists, from the message storage <mem1>, all messages

that currently have the specified <stat>. The major difference over the standard command AT+CMGL is that the

status of the listed messages remains u n c h a n g e d (unread remains unread).

The execute command is the same as the write command, but uses the given default of <stat>.

Syntax

Test Command

AT^SMGL=?

Response(s)

same as AT+CMGL

Exec Command

AT^SMGL

Response(s)

^SMGL: (For default values of <stat>, see "Section 13.1, SMS parameters.)

Write Command

AT^SMGL=<stat>

Response(s)

same as AT+CMGL

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

Notes

• The selected <mem1> can contain different types of SMs (e.g. SMS-DELIVERs, SMS-SUBMITs, SMS-STA-

TUS-REPORTs and SMS-COMMANDs), the response may be a mix of the responses of different SM types.

TE application can recognize the response format by examining the third response parameter.

• Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data

may not yet be accessible, resulting in a short delay before the requested AT command response is returned.

See Section 23.1, Restricted access to SIM data after SIM PIN authentication for further detail.

• If the ME is Java controlled, take into account that the AT Command API can handle responses up to a length

of 1024 bytes. To avoid any longer re-sponses it is recommended not to read the entire range of short mes-

sage entries at a time.

Page 393 of 567

13.24 AT^SMGO

13.24

AT^SMGO Set or query SMS overflow presentation mode or

query SMS overflow

The write command sets the overflow presentation mode.

The read command returns the overflow presentation mode and the SMS overflow status.

Syntax

Test Command

AT^SMGO=?

Response(s)

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

Read Command

AT^SMGO?

Response(s)

^SMGO: <n>, <mode>

ERROR

+CMS ERROR

Write Command

AT^SMGO=<n>

Response(s)

ERROR

CME ERROR

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Unsolicited Result Code

SMS buffer change:

^SMGO: <mode>

Status of SMS buffer has changed.

Parameter Description

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

SMS overflow presentation mode

[0]^(&F)

Disable

Enable

<mode>^(num)(&V)

SMS overflow status

Space available

SMS buffer full (The buffer for received short messages is <mem3>. See

AT+CPMS.)

Buffer full and new message waiting in SC for delivery to phone

Page 394 of 567

13.25 AT^SMGR

13.25

AT^SMGR Read short message without setting status to REC

READ

The AT^SMGR command is a specific Siemens command which has the same syntax as AT+CMGR. The only func-

tional difference is that the status "REC UNREAD" of a short message is not overwritten to "REC READ".

Syntax

Test Command

AT^SMGR=?

Response(s)

^SMGR:

Write Command

AT^SMGR=<index>

Response(s)

see AT+CMGR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

Note

• Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data

may not yet be accessible, resulting in a short delay before the requested AT command response is returned.

See Section 23.1, Restricted access to SIM data after SIM PIN authentication for further detail.

Page 396 of 567

13.26 AT^SSCONF

13.26

AT^SSCONF SMS Command Configuration

AT^SSCONF controls details of some SMS releated commands. Please note that AT^SSCONF settings are stored

volatile, i.e. after restart or reset the default values will be restored.

Syntax

Test Command

AT^SSCONF=?

Response(s)

^SSCONF:list of supported <ra>s

Read Command

AT^SSCONF?

Response(s)

^SSCONF:<ra>

Write Command

AT^SSCONF=<ra>

Response(s)

PIN ASC0 ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

Parameter Description

<ra>^(num)

Display recipient address

[0]^(&F)

TC65 does not display <ra> and <tora>. These parameters are used with the

result codes of AT+CMGL, AT^SMGL, AT+CMGR, AT^SMGR and the URC "+CDS".

TC65 displays <ra> and <tora>.

Page 397 of 567

13.27 AT^SSDA

13.27

AT^SSDA Set SMS Display Availability

This command allows to notify the TC65 of its controlling application's capability to immediately display incoming

SMS on a display.

If the application is able to display incoming short messages, a class 0 message shall be displayed immediately.

However, if it does not, class 0 messages shall be treated as if no message class is determined (GSM 03.38[21]).

The effect of this command if <da>=1 is to determine the behavior of parameter <mt> of AT+CNMI:

If multiplex mode is enabled (AT+CMUX) and <da>=1 with <mt>=1 is set on any logical channel, all other chan-

nels have to use <mt>=0.

Syntax

Test Command

AT^SSDA=?

Response(s)

^SSDA:list of supported <da>s

Read Command

AT^SSDA?

Response(s)

^SSDA:<da>

Write Command

AT^SSDA=<da>

Response(s)

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<da>^(num)

Display Availability

0^(&F)

Application is not able to display incoming short message

Application is able to display incoming short message

Note

• If the ME operates on different instances (MUX channels 1, 2, 3 or ASC0/ASC1) avoid different settings for

routing and indicating short messages. For example, if messages shall be routed directly to one instance of

the TE (set with AT+CNMI, AT^SSDA), it is not possible to activate the presentation of URCs with AT+CMER

or AT+CNMI on another instance. Any attempt to activate settings that conflict with existing settings on

another interface, will result in CME ERROR, or accordingly CMS ERROR.

Page 398 of 567

13.28 AT^SSMSS

13.28

AT^SSMSS Set Short Message Storage Sequence

The short message storage ''MT'' (see AT+CPMS) is a logical storage. It consists of two physical storages ''ME''

and ''SM''. This command allows to select the sequence of addressing this storage.

Syntax

Test Command

AT^SSMSS=?

Response(s)

^SSMSS: (list of supported) <seq>s

Read Command

AT^SSMSS?

Response(s)

^SSMSS: <seq>

Write Command

AT^SSMSS=<seq>

Response(s)

Reference(s)

PIN ASC0 ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<seq>^(num)

MT sequence

0^(&F)

''MT'' storage is ''ME'' then ''SM

''MT'' storage is ''SM'' then ''ME''

Note

• The <seq> parameter will be stored in non-volatile memory.

Page 399 of 567

Siemens TC65 Terminal. Manual (Version: 02.000) - part 5