TC65i AT-Commands Set. Manual

Syntax

Test Command

AT^SISS=?

Response(s)

Read Command

AT^SISS?

Response(s)

^SISS: <srvProfileId>, <srvParmTag>, <srvParmValue>

ERROR

+CME ERROR: <err>

Write Command

AT^SISS=<srvProfileId>, <srvParmTag>, <srvParmValue>

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Parameter Description

<srvProfileId>^(num)

Internet service profile identifier.

The <srvProfileId> is used to reference all parameters related to the same service profile. Furthermore,

when using the AT commands AT^SISO, AT^SISR, AT^SISW and AT^SISC the <srvProfileId> is needed

to select a specific service profile.

0...9

Internet service profile parameter.

srvType

Type of Internet service to be configured with consecutive usage of AT^SISS.

For supported values of <srvParmValue> refer to <srvParmValue-srv-

Type>.

alphabet

Selects the character set for input and output of string parameters within a pro-

file.

The selected value is bound to the specific profile. This means that different

profiles may use different alphabets. Unlike other parameters the alphabet can

be changed no matter whether the <srvParmTag> value "srvType" has been

set.

For supported values of

<srvParmValue> refer to

<srvParmValue-

alphabet>.

user

User name string

1. Socket

Not applicable.

2. FTP

Not applicable; set within "address" parameter.

3. HTTP

Length: 2 ... 31

User name for the HTTP authentication mechanism. Currently only HTTP

simple authentication is supported.

4. SMTP

User name to be used for SMTP authentication (string).

Length: 4 ... 64.

If SMTP authentication is disabled, i.e. "smAuth" flag not set, user name

parameter will be ignored.

5. POP3

User name identifying a mailbox, i.e. mailbox name (string).

Length: 1 ... 64.

passwd

Password string

1. Socket

Not applicable.

2. FTP

Not applicable; set within "address" parameter.

3. HTTP

Length: 2 ... 31

Password for the HTTP authentication mechanism. Currently HTTP simple

authentication is supported only.

4. SMTP

Password to be used for SMTP authentication (string).

Length: 4 ... 64.

If SMTP authentication is disabled, i.e. "smAuth" flag not set, password

parameter will be ignored.

5. POP3

Server/mailbox-specific password (string).

Length: 1 ... 64.

Used to perform authentication with a POP3 server.

conId

Internet connection profile to be used, for details refer AT^SICS.

tcpPort

TCP Port Number

1. Socket

Not applicable; set within "address" parameter.

2. FTP

Not applicable; set within "address" parameter.

3. HTTP

Not applicable; set within "address" parameter.

If parameter is omitted the service connects to HTTP default port 80.

4. SMTP

SMTP server TCP port number (numeric)

Length: 0 ... 2¹⁶-1

If this parameter is not set, SMTP default port number 25 is used.

5. POP3

POP3 server TCP port number (numeric)

Length: 0 ... 2¹⁶-1

If this parameter is not set, POP3 default port number 110 is used.

address

String value, depending on the service type either a URL in the case of Socket,

FTP and HTTP or an address in the case of SMTP and POP3:

1. Socket

- Socket type TCP client URL

"socktcp://'host':'remote tcpPort'[;disnagle='0|1'] "

"disnagle" is optional for disabling the TCP Nagle algorithm.

0: Nagle algorithm is enabled (default).

1: Nagle algorithm is disabled.

- Socket type TCP server URL

"socktcp://listener:'local tcpPort' "

- Socket type UDP endpoint URL

"sockudp://:'local udpPort' "

- Socket type UDP client URL

"sockudp://'host':'remote udpPort'[;size='byte'][;port='word']"

Parameter "size" (optional):

0: PDU size is variable (default).

1 ... 1500: Fixed PDU size in bytes.

Parameter "port" (optional):

0: Port number will be assigned from service (default).

1 ... 2¹⁶-1: defines the local port number for the UDP client.

FTP

- FTP client URL (get)

"ftp://'user':'password'@'host':'tcpPort'/'url-path' [;type='a|i|d'] "

Refer to "IETF-RFC 1738".

- FTP client URL (put)

"ftpput://'user':'password'@'host':'tcpPort'/'url-path'/'element

name'

[;type='a|i'][;mode='u|a|d'] "

Used parameters:

"host" is mandatory, all other parameters are optional.

If "password" is set then "user" must be set as well.

If "user" is omitted the string "anonymous" is selected for "user" and "pass-

word".

If "password" is omitted the password request is served by an empty string.

If "tcpPort" is omitted the service connects to the FTP default port 21.

If "url-path" contains only the IP address a directory listing is requested.

If "url-path" contains the IP address and has a slash '/' appended a detailed

directory listing is requested.

"type": [a)scii | i)mage | d)irectory]

"mode": [u)nique | a)ppend | d)elete]

"u)nique" selects the FTP Store Unique command to create a file name

unique to the current directory. If the file name is assigned by the server

then the "^SIS" URC will appear, indicating <urcInfoId> 2100 and the

file name.

"d)elete" clears given 'element name'.

If "mode" is omitted "replace mode" is default setting.

HTTP

HTTP client URL

Length: 6 ... 255

"http://'server'/'path':'tcpPort' "

"server": FQDN or IP-address

"path": path of file or directory

"tcpPort": If parameter is omitted the service connects to HTTP default port

80.

Refer to "IETF-RFC 2616".

SMTP SMTP server address (string).

Length: 4 ... 256.

POP3 POP3 server address (string).

Length: 4 ... 256.

hcContent

Optional parameter for HTTP method "Post".

Length: 0 ... 127

Can be used to transfer a small amount of data. The content of this string will

only be sent if "hcContLen" = 0. The maximum length of "hcContent" is 127

bytes.

To transmit a larger amount of data "hcContLen" must be set to a non-zero

value. In this case the "hcContent" string will be ignored, and data transmission

from the client to the server is done with AT^SISW.

hcContLen

Mandatory parameter for HTTP method "Post".

Length: 0 ... 2³¹-1

The content length shall be set in the header of the HTTP "Post" request before

the data part is transferred.

If "hcContLen" = 0 then the data given in the "hcContent" string will be posted.

If "hcContLen" > 0 then the AT^SISW command will be used to send data from

the client to the server. In this case, "hcContLen" specifies the total amount of

data to be sent. The data can be sent in one or several parts. For each part,

the transmission is triggered by the URC "^SISW: x, 1", then the AT^SISW write

command can be executed. After the exact number of bytes are transferred via

the serial interface, the HTTP client will go from service state "Up" to service

state "Closing" (see parameters <srvState> and <srvState> for detail).

Finally, the URC "^SISW: x, 2" indicates that all data have been transferred and

the service can be closed with AT^SISC.

hcUsrAgent

The user agent string must be set by the application to identify the mobile. Usu-

ally operation system and software version info is set with this browser identi-

fier.

Length: 0 ... 63

hcMethod

HTTP method specification: 0=GET, 1=POST, 2=HEAD.

hcProp

Parameter for several HTTP settings.

Length: 0 ... 127

The general format is 'key': <space> 'value' "\0d\0a".

Multiple settings can be given separated by "\0d\0a" sequences within the

string.

Possible 'key' values are defined at HTTP/1.1 Standard RFC 2616.

hcRedir

This flag controls the redirection mechanism of the TC65i acting as HTTP client

(numeric).

If "hcRedir" = 0: No redirection.

If "hcRedir" = 1: The client automatically sends a new HTTP request if the

server answers with a redirect code (range 30x).

Default is 1.

hcAuth

If set ("hcAuth" = 1) this flag determines that the HTTP client will automatically

answer on authentication requests from the server with the current "passwd"

and "user" parameter settings. If these parameters are not specified the TC65i

will terminate the HTTP connection and send an indication to the TA.

Default is 1.

smFrom

Email sender address, i.e. "MAIL FROM" address (string).

Length: 6 ... 256

A valid address parameter consists of local part and domain name delimited by

a '@' character, e.g. "john.smith@somedomain.de".

smRcpt

Recipient address of the email, i.e. "RCPT TO" address (string).

Length: 6 ... 256

If multiple recipient addresses are to be supplied the comma character is used

as delimiter to separate individual address values, e.g. "john.smith@somedo-

main.de,tom.meier@somedomain.de". Some mail servers do not accept recip-

ient addresses without brackets <>. It is recommended to use the "RCPT TO"

variable with brackets.

smCC

CC recipient address of the email (string).

Length: 6 ... 256

If multiple CC recipient addresses are to be supplied the comma character is

used as delimiter to separate individual address values, e.g.

"john.smith@somedomain.de,tom.meier@somedomain.de".

smSubj

Subject content of the email (string).

Length: 0 ... 256

If no subject is supplied the email will be sent with an empty subject.

smHdr

This parameter, if set, will be appended at the end of the email header section

(string).

Length: 0... 256

Hence, it serves as a generic header field parameter which allows the user to

provide any email header field. It is the user's responsibility to provide correct

header fields!

String of max. 256 characters.

Example for multipart MIME messages:

"Content-Type: multipart/mixed".

smAuth

SMTP authentication control flag (numeric).

If disabled (<srvParmValue> "0" by default), TC65i performs action without

SMTP authentication.

If enabled (<srvParmValue> "1") authentication procedure with the SMTP

server will be performed by means of supported authentication methods, using

values of "user" and "passwd" parameters. If TC65i and SMTP server are not

able to negotiate an authentication mechanism supported by both parties, the

TC65i continues action without authentication.

TC65i supports SMTP authentication.

pCmd

POP3 user command to be executed by the POP3 service (numeric).

For supported values of <srvParmValue> refer to <srvParmValue-pCmd>.

pNumber

Optional message number argument used by the POP3 commands List ("2"),

Retrieve ("3") and Delete ("4"). For POP3 commands see <srvParmTag>

value "pCmd".

Length: 0 ... 2³¹-1

If no specific value is set in the service profile, the value "0" is assumed by

default, i.e. "pNumber" is disabled.

pLength

Maximum message length (string, optional)

Length: 0 ... 2³¹-1

"pLength" can be used to specify the length of the message(s) to be retrieved

from or deleted on the POP3 server. If no specific value is set in the service

profile, the default value "0" is assumed, which means that there is no limit on

the message size.

A warning will be issued inthe following cases:

• If "pNumber" > 0 and a specific message to be retrieved from / deleted on

the server is longer than "pLength".

• If "pNumber" = 0 and all messages to be retrieved from / deleted on the

server are longer than "pLength".

No warning will be issued in the following cases:

• If there are no messages at all on the server.

• If the server has message(s) below and above the "pLength" specified. In

this case, the message(s) within the range of "pLength" can be successfully

retrieved or deleted, but the message(s) above "pLength" remain on the

server without any further notification given to the user.

• Therefore, after retrieving / deleting messages, it is recommended to check

the message status on the server. This can be done by adding a further

POP3 service profile using the POP3 user command List ("2").

pDelFlag

Flag to be used with the POP3 user command Retrieve ("3"). Specifies whether

or not to delete retrieved emails on the server (optional).

For supported values of

<srvParmValue> refer to

<srvParmValue-

pDelFlag>.

tcpMR

Parameter can be used to overwrite the global AT^SCFG parameter "Tcp/

MaxRetransmissions" <tcpMr> for a specific Internet Service connection pro-

file. If the parameter is not specified the value specified with AT^SCFG will be

used.

Supported values <srvParmValue> for this parameter are the same as

described for <tcpMr>.

Setting is not relevant for Internet Service "Socket" with type "UDP".

tcpOT

Parameter can be used to overwrite the global AT^SCFG parameter "Tcp/Over-

allTimeout" <tcpOt> for a specific Internet Service connection profile. If the

parameter is not specified the value specified with AT^SCFG will be used.

Supported values <srvParmValue> for this parameter are the same as

described for <tcpOt>.

Setting is not relevant for Internet Service "Socket" with type "UDP".

<srvParmValue>^(str)

Parameter value; type and supported content depend on related <srvParmTag>.

<srvParmValue-srvType>^(str)

Supported Internet service type values in <srvParmValue> for <srvParmTag> value "srvType".

Before changing the "srvType" of an existing service profile be sure that the profile is closed. To verify the con-

nection state of the service profile enter the read command AT^SISI. Only when <srvState>=2 is returned

for this specific service profile you can change its service type.

“Socket“

TC65i acting as client or server (listener) for TCP or UDP.

If TC65i is TCP listener at least two service profiles are required. The first

socket profile must be configured as listener. The second service profile will be

dynamically assigned when a socket connection request from a remote client

is incoming. For this purpose, one service profile must be left free (= not con-

figured with AT^SISS). An incoming socket connection request will be indi-

cated by the "^SIS" URC, with the next free <srvProfileId> shown inside

the URC as parameter <urcInfoId>. The connection request can be

accepted or rejected by using the commands AT^SISO or AT^SISC and the ID

retrieved from the "^SIS".

“Ftp“

TC65i acting as FTP client.

“Http“

TC65i acting as HTTP client.

“Smtp“

TC65i acting as SMTP client.

“Pop3“

TC65i acting as POP3 client.

“none“

Reset Internet service profile settings. Operation is not allowed if profile is in

use, i.e. it was activated via AT^SISO.

<srvParmValue-alphabet>^(str)

Supported string parameter character set selections in <srvParmValue> for <srvParmTag> value "alphabet".

[“0“]

Applicable character set is determined by current setting of AT+CSCS.

“1“

International Reference Alphabet (IRA, seven bit ASCII).

<srvParmValue-pCmd>^(num)

Supported POP3 user command values in <srvParmValue> for <srvParmTag> value "pCmd".

Status command.

This command retrieves the "drop listing" of a POP3 server. A "drop listing"

consists of a single line containing the number of messages in the maildrop list

followed by the total size of the maildrop list in bytes. Each drop listing will be

finished by a so-called "dotline", i.e. a new line with just a single dot.

List command.

If <srvParmTag> value "pNumber" is set to a non-zero value the "List" com-

mand returns the "scan listing", consisting of a single line which contains the

message number and the message size in bytes if the specified message

exists in the maildrop list on the POP3 server.

If no such message exists on the server than the POP3 service issues an error

response to the user.

If <srvParmTag> value "pNumber" is zero the "List" command returns a multi-

line "scan listing". For each message on the maildrop list of the server the

POP3 service returns a line containing the message number and its size in

bytes. A final "dotline" will be printed at the end of the "scan listing".

If there are no messages on the maildrop list of the server, the POP3 service

returns a positive response, i.e. it doesn't issue an error response, but the

"scan listing" will be empty.

In either case, each scan listing will be finished by a so-called "dotline", i.e. a

new line with just a single dot.

Retrieve command.

If <srvParmTag> value "pNumber" is set to a non-zero value this command

retrieves the related message from the POP3 server's maildrop list.

If no such message exists on the server the POP3 service issues an error

response to the user.

It depends on the parameter "pDelFlag" if the message will be deleted from the

POP3 server upon successful retrieval.

If <srvParmTag> value "pNumber" is zero the "Retrieve" command returns all

messages pending in the POP3 server's maildrop.

If there are no messages on the maildrop list of the server the POP3 service

returns with a positive response, i.e. it doesn't issue an error response, but the

returned list will be empty.

Each email will be finished by a so-called "dotline", i.e. a new line with just a

single dot.

Delete command

If <srvParmTag> value "pNumber" is set to a non-zero value the command

deletes the related message from the POP3 server's maildrop list. In fact, the

message is marked as deleted on the server and will be deleted permanently

if the POP3 service command executes successfully. In case an error has

occurred, e.g. network loss, the message will not be deleted on the server even

though the POP3 service command has been finished.

If <srvParmTag> value "pNumber" is zero the "Delete" command deletes all

messages from the POP3 server's maildrop list. In fact, the messages are

marked as deleted on the server and will be deleted permanently if the POP3

service command executes successfully. In case an error has occurred, the

messages will not be deleted on the server even though the POP3 service

command has been finished.

(num)

<srvParmValue-pDelFlag>

Supported flag values in <srvParmValue> for <srvParmTag> value "pDelFlag". Only applicable if the profile

contains the POP3 user command Retrieve ("3").

[0]

Messages will not be deleted on the server.

Delete messages on the server which have been retrieved successfully.

Notes

• String parameters are truncated if greater than the maximum length specified above.

• If AT^SISS is used simultaneously on different instances (e.g. Mux channels) only one request can be han-

dled at a time. On the other instance(s) "+CME ERROR: operation temporary not allowed" will be displayed.

If so, repeat the command on this instance.

10.4

AT^SISI Internet Service Information

AT^SISI serves to monitor the status of Internet service profiles defined with AT^SISS.

The AT^SISI read command requests the current status of all defined Internet service profiles.

The AT^SISI write command requests the status of the specified Internet service profile. If the specified service

profile is not defined yet, "+CME ERROR" is returned.

Syntax

Test Command

AT^SISI=?

Response(s)

[^SISI:(list of defined <srvProfileId>s)]

Read Command

AT^SISI?

Response(s)

If response is related to service profile(s) created / opened on this interface:

[^SISI: <srvProfileId>, <srvState>, <rxCount>, <txCount>, <ackData>, <unackData>]

[^SISI: ...]

If response is related to service profile(s) created / opened on other interface(s):

[^SISI: <srvProfileId>, <srvParmTag>value "srvType"]

[^SISI: ...]

ERROR

Write Command

AT^SISI=<srvProfileId>

Response(s)

^SISI: <srvProfileId>, <srvState>, <rxCount>, <txCount>, <ackData>, <unackData>

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Parameter Description

<srvProfileId>^(num)

Internet service profile identifier as defined by AT^SISS (<srvProfileId>).

0...9

<srvState>^(num)

Internet service state (for details see AT^SISO parameter <srvState>).

Allocated

Connecting

Closing

Down

<rxCount>^(num)

Number of bytes received via AT^SISR since last successful AT^SISO write command.

This is the same value as displayed by the AT^SISO read command with the parameter <rxCount>.

<txCount>^(num)

Number of bytes sent via AT^SISW since last successful AT^SISO write command.

This is the same value as displayed by the AT^SISO read command with the parameter <txCount>.

<ackData>^(num)

Number of data bytes already sent and acknowledged at TCP layer. Value 0 indicates that no sent data is

acknowledged yet.

Parameter is not applicable to HTTP, POP3, SMTP and Socket with UDP. For these services the counter is

always set to 0.

<unackData>^(num)

Number of data bytes already sent but not yet acknowledged at TCP layer. A value 0 indicates that all sent data

is already acknowledged.

This is the same value as displayed in the response of the AT^SISW write command with the parameter

<unackData>.

Parameter is not applicable to HTTP, POP3, SMTP and Socket with UDP. For these services the counter is

always set to 0.

Note

• If a service is in state "Down" the responses for <rxCount>, <txCount>, <ackData> and <unackData>

are the last known values for the service in the states "Connecting", "Up" and "Closing".

10.5

AT^SISO Internet Service Open

The AT^SISO write command starts the Internet session configured by the service profile. All further steps

needed to control the session depend on whether you are using URC mode or polling mode. The AT^SISO read

command returns the current status of all services.

URC mode:

If the service opens successfully, the URCs "^SISW" and "^SISR" will trigger the action to follow, either writing

data with AT^SISW or reading data with AT^SISR. To terminate an upload data stream set the <eodFlag>

within the last AT^SISW command. If the URCs notify that a data transfer has been successful ("^SISR: x, 2" or

"^SISW: x, 2"), the service can be closed with AT^SISC. If a special event occurs, e.g. an error or a warning,

after opening or while using a service then the URC type "^SIS" will be delivered.

Polling mode:

After opening the service, all progress information needed to control the session shall be explicitly requested by

the host application. The particular sequence of AT commands varies depending on the service used. The fol-

lowing list summarizes, by way of an example, the steps normally involved in managing an upload or download

job.

•

Upload (Socket, FTP, HTTP, SMTP):

- Enter the AT^SISO command, e.g. AT^SISO=9.

- Enter AT^SISW, specify <reqWriteLength>, e.g. AT^SISW=9,20. Check resulting response for <cnf-

WriteLength>. Optionally, check error with AT^SISE, e.g. AT^SISE=9. If necessary, repeat the

sequence several times.

- Enter last AT^SISW command and enable <eodFlag>, e.g. AT^SISW=9,0,1.

If Socket service: Query available data with AT^SISR, e.g. AT^SISR=9,1430.

- Check service state with AT^SISI, e.g. AT^SISI=9, if necessary several times until <srvState>=6

("Down").

- Check error with AT^SISE, e.g. AT^SISE=9.

- Close service with AT^SISC, e.g. AT^SISC=9.

•

Download (Socket, FTP, HTTP, POP3):

- Enter the AT^SISO command, e.g. AT^SISO=9.

- Enter AT^SISR, specify <reqReadLength>, e.g. AT^SISR=9,1000. Check resulting response for

<cnfReadLength>. If necessary, repeat the sequence several times until <cnfReadLength>= -2 (end

of data) or ERROR.

- Check error with AT^SISE, e.g. AT^SISE=9.

- Close service with AT^SISC, e.g. AT^SISC=9.

•

Socket service (upload and download possible in one session):

- Recommended: Set AT+CMEE=2 to enable extended error text.

- Enter the AT^SISO command, e.g. AT^SISO=9.

- Enter AT^SISR or AT^SISW, specifying

<reqReadLength> or

<reqWriteLength>, e.g.

AT^SISR=9,20 or AT^SISW=9,20. Check resulting response for <cnfReadLength> or <cnfWrite-

Length>. If necessary, repeat the sequence several times.

- Check error with AT^SISE, e.g. AT^SISE=9.

- If write action: Enter last AT^SISW command and enable <eodFlag>, e.g. AT^SISW=9,0,1.

If Socket service: Query available data with AT^SISR, e.g. AT^SISR=9,1430.

- Close service with AT^SISC, e.g. AT^SISC=9.

Syntax

Test Command

AT^SISO=?

Response(s)

Read Command

AT^SISO?

Response(s)

^SISO: <srvProfileId>, <srvParmTag>value "srvType" [, <srvState>, <socketState>,

<rxCount>, <txCount>, <locAddr>, <remAddr>]

[^SISO: ...]

Write Command

AT^SISO=<srvProfileId>

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Parameter Description

<srvProfileId>^(num)

<srvProfileId> 0 ... 9 specified with AT^SISS.

<srvState>^(num)

Internet service state.

Please note, that the state of an Internet service may influence the state of the serial DCD line. For details see

description of value 2 for parameter <value> of command AT&C.

Allocated

Service profile resources are allocated, i.e. at least the service type has been

set (parameter <srvParmTag>, value "srvType" of AT^SISS). The service is

not opened, but ready for configuration.

Connecting

State after opening a service with AT^SISO where the connection is being

established.

If connection setup is successful the service proceeds to the state "4" (Up) and

one of the URCs "^SISW" and "^SISR" may follow. If connection setup is not

successful, the "^SIS" URC may appear and the service enters <srvState>

6 (Down).

In the case of FTP, <srvState>=3 means that the command channel is being

established.

If the service profile is configured as Socket listener, then the listener always

stays at <srvState>=3 and <socketState>=3 (LISTENER), while the

<srvState> and <socketState> of the dynamically assigned service pro-

file may change. See examples in Section 10.5.1.

The service performs its purpose. The data transfer process is the major func-

tion at this state.

FTP: Data channel is up.

SMTP: The SMTP service will not enter <srvState>=4 until the host has writ-

ten the first data packet with AT^SISW.

Closing

Internet Service is closing the network connection.

FTP: Command channel is released.

Down

This state is entered if

- the service has successfully finished its session (see note on Socket),

- the remote peer has reset the connection or

- the IP connection has been closed because of an error (see note below on

service or network errors).

If a service in this state be sure to close it with AT^SISC before reopening it.

<socketState>^(num)

Socket state identifier.

Same as value "1", but applicable only if service profile is POP3.

Socket not assigned, i.e. no TCP/UDP connection active.

Socket assigned as CLIENT.

Socket assigned as LISTENER.

Socket assigned as SERVER.

<rxCount>^(num)

Number of bytes received via AT^SISR since last successful AT^SISO write command.

<txCount>^(num)

Number of bytes sent via AT^SISW since last successful AT^SISO write command.

<locAddr>^(str)

Recently used local IP address in dotted-four-byte format and TCP port, separated by colon,

e.g.

"192.60.10.10:80".

<remAddr>^(str)

Remote IP address in dotted-four-byte format and TCP port, separated by colon, e.g. "192.60.10.10:80".

Notes

• If the bearer cannot be established and AT^SISO returns an error there might be a general GSM/GPRS prob-

lem. To identify the reason you can take advantage of the AT+CEER command. Using AT+CEER is especially

recommended when the <infoID> parameter of the AT^SISE command equals 0.

• If a service or network error occurs during an IP session and the "^SIS" URC or the AT^SISE command dis-

play an error message, the service enters <srvState>=5 and then 6, i.e. the IP connection is closed. In this

case, the service still allows reading the data stored in the buffer, but writing data is denied. After reading,

close the service and open it again.

• As in polling mode no error URCs are available you are advised to integrate the commands AT^SISI and

AT^SISE into the command sequences for upload and download jobs. So, the AT^SISO command may be

followed by AT^SISI to check that the service has entered the <srvState>=4 before sending AT^SISR or

AT^SISW. This helps you to detect errors even though the "^SIS" URCs are disabled. A typical example is

that the service fails to be opened because the service profile contains a wrong destination address. In such

a case, after opening with AT^SISO and OK response, the service quickly enters the states <srvState>=2,

4 and 6, with an error being returned no earlier than after sending the first AT^SISR or AT^SISW command.

In URC mode, an error URC, such as "Host not found" would be received in this situation, but in polling mode

the only way to detect the state is using AT^SISI or, alternatively, AT^SISO.

• If the user rapidly closes and opens TCP/IP connections based on the embedded TCP/IP stack the service

may display the error "No buffer space available", meaning that all TCP/IP socket resources are exhausted.

In the worst case, opening further TCP/IP connections is locked for up to 60 seconds.

10.5.1

Example: Accepting / Rejecting Socket Connection Request

from Remote Client

Host 1 configured as Socket listener with IP address 10.10.0.187 at port 65534 is receiving a connection request

from the remote client 10.10.0.185 (at port 1024). The example assumes that connection and service profiles

have been created as stated earlier.

Start the Socket service in listener mode, then query the IP address dynamically assigned to the Socket listener:

at^siso=4

Host 1 opens the Socket service.

at^siso?

Query the current status of all services. All service

^SISO: 0, ""

profiles are unused, except for service profile

^SISO: 1, ""

which is running in listener mode, where

<srvState>=3 (listening) and <socketState>=3

^SISO: 2, ""

(LISTENER). The response also indicates the IP

^SISO: 3, ""

address dynamically assigned to the listener. The lis-

tener's access data (IP address and TCP port num-

ber) shall be passed on to the client.

^SISO: 4, "Socket","3","3","0","0","10.10.0.187:65534","0.0.0.0:0"

^SISO: 6, ""

^SISO: 7, ""

^SISO: 8, ""

^SISO: 9, ""

Indication of incoming Socket connection request:

^SIS: 4, 1, 0

The URC indicates that the listener configured on

service profile 4 is receiving a Socket connection

request (<urcCause>=1) from the remote client.

The last URC parameter <urcInfoId> represents

the ID of the dynamically assigned service profile,

here 0.

at^siso?

Query the current status of services.

^SISO: 0, "Socket","2","4","0","0",

Indication on host 1 that the connection request from

"10.10.0.187:0","10.10.0.185:1024"

the remote client has been dynamically assigned to

^SISO: 1, ""

service profile

0 which is set to Server mode

^SISO: 2, ""

(<socketState>=4).

^SISO: 3, ""

^SISO: 4, "Socket","3","3","0","0", "10.10.0.187:65534","0.0.0.0:0"

^SISO: 6, ""

^SISO: 7, ""

^SISO: 8, ""

^SISO: 9, ""

Host 1 accepts the Socket connection request:

at^siso=0

Host 1 accepts the connection request, where 0 is

the ID of the dynamically assigned service profile.

^SISW: 0, 1

The URC indicates that data transmission to the

remote client is possible. If the remote client has

already sent some data the additional URC ^SISR:

0,1 is displayed.

at^siso?

Query the current status of services.

^SISO: 0, "Socket","4","4","0","0",

The socket connection between host 1 and remote

"10.10.0.187:65534","10.10.0.185:1024"

client is successfully established.

^SISO: 1, ""

^SISO: 2, ""

^SISO: 3, ""

^SISO: 4, "Socket","3","3","0","0","10.10.0.187:65534","0.0.0.0:0"

10.6

AT^SISC Internet Service Close

The AT^SISC write command closes the TCP/IP connection to the remote peer which was opened with

AT^SISO. All resources are released, all status information parameters, e.g. <srvState>, <unackData>,

<ackData>, <rxCount> and <txCount> counters, are reset. Only the initial configuration settings are pre-

served. The service can be restarted any time, using the same configuration or a new one.

Syntax

Test Command

AT^SISC=?

Response(s)

Write Command

AT^SISC=<srvProfileId>

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Parameter Description

<srvProfileId>^(num)

0...9

<srvProfileId> specified with AT^SISS.

10.7

AT^SISR Internet Service Read Data

The AT^SISR command either triggers a read operation (download) or queries the number of bytes in the internal

buffer.

The AT^SISR write command may return the following errors:

• "+CME ERROR: operation failed" if there is a problem on application, socket, PPP or GPRS/GSM level. The

AT^SISE command and the "^SIS" URC offer additional error information.

• "+CME ERROR: operation temporary not allowed" e.g. if the service has not network resources allocated.

• "+CME ERROR: operation not allowed" e.g. if the service is not configured.

Syntax

Test Command

AT^SISR=?

Response(s)

Write Command

AT^SISR=<srvProfileId>, <reqReadLength>

Response(s)

^SISR: <srvProfileId>, <cnfReadLength>[, <remainUdpPacketLength>[, <optServParm>]]

Number of data bytes are sent as specified by <cnfReadLength>. If peek operator was used no data bytes

are sent.

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Unsolicited Result Code

^SISR: <srvProfileId>, <urcCauseId>

Data availability status of the Internet service configured with AT^SISS has changed. The URC is issued when:

• data is available after opening an Internet service or

• less data was confirmed (in <cnfReadLength>) than requested (with <reqReadLength>) during the last

"Read Data" operation and new data is available.

The URC is disabled in polling mode. See AT^SCFG, parameter "Tcp/WithURCs", <tcpWithUrc>.

Parameter Description

<srvProfileId>^(num)

<srvProfileId> 0 ... 9 specified with AT^SISS.

<reqReadLength>^(num)

Peek Operator: Query number of received bytes within internal buffers.

The behaviour of the peek operator depends on the selected Internet service,

i.e. it may not be supported by all IP Services.

For "Socket" service configured for UDP the size of the next available UDP

packet is returned.

1...1500

Requested number of data bytes to be read via the Internet service specified

in <srvProfileId>.

<cnfReadLength>^(num)

-2

Indicates end of data. Data transfer has been finished (all data have been read)

and the service can be closed with AT^SISC.

-1

Applies only to HTTP: Querying number of available bytes is not supported by

the HTTP service.

Indicates that no further data is available at the moment.

Number of available data bytes. The range is determined by

<reqReadLength>:

If <reqReadLength> was greater than 0, then <cnfReadLength> may be

less or equal to the value requested with <reqReadLength>.

<reqReadLength> equals 0 (peek operator) the value indicated by

<cnfReadLength> may be greater than 1500.

<urcCauseId>^(num)

Indicates whether or not data is available for reading with AT^SISR.

Data is available and can be read by sending the AT^SISR command. The

URC appears when less data was confirmed (in <cnfReadLength>) than

requested (with <reqReadLength>) during the last "Read Data" operation

and new data is available.

End of data. Data transfer has completed (all data read). The service can be

closed with AT^SISC.

<remainUdpPacketLength>^(num)

Optional third parameter of the AT^SISR write command response displayed only if the Socket service uses the

UDP protocol.

The reception of each datagram must be completed before the next datagram can be received. This may be a

problem if the buffer of the host application is limited and not designed to handle the maximum packet size of

1500 bytes. To compensate this, the host is advised to request, via <reqReadLength>, an amount less or

equal its maxmimum buffer capacity and wait for the resulting AT^SISR write command response with param-

eter <remainUdpPacketLength>. The benefit of this approach is that the host may properly receive all parts

of a UDP datagram, as after each received data part the number of remaining bytes is synchronized, until read-

ing the datagram is finished.

If the currently read datagram is smaller than the number of bytes requested by the host the <remainUdpPack-

etLength> parameter is omitted.

Further write attempts with AT^SISR are denied as long as the <remainUdpPacketLength> is unequal 0 or

is not omitted. In this case the service returns "+CME ERROR: operation of service temporary not allowed".

Indicates that all bytes of the current UDP datagram are read.

1...(max. data size)-1

Indicates that the currently read UDP datagram is not yet complete. The dis-

played value is the remaining number of bytes.

<remainUdpPacketLength> is unequal 0 until reading all parts of the cur-

rent datagram is finished.

<optServParm>^(str)

Service specific parameter of the AT^SISR write command response. If the Socket service is configured as UDP

endpoint this parameter returns the IP address and the UDP port of the remote host that has sent the current

UDP data.

10.7.1

Example: Socket Host Reads Small Amounts of UDP Data Pack-

ets (URC Mode)

This section applies only to the Socket service using the UDP protocol. The example shows how to read UDP

packets if the buffer of the host application can handle only a few bytes. There are two datagrams available for

reading.

Buffer size: 6 bytes

Datagram A = 18 bytes (content "THIS_IS_DATAGRAM_A")

Datagram B =

3 bytes (content "NEW")

^SISR: 0,1

Service profile 0 is configured for Socket service and UDP. The URC

notifies host that data is available for reading.

at^sisr=0,6

The host requests to read 6 bytes.

^SISR: 0,6,12

The first 6 bytes of datagram A are confirmed and transmitted. Another

THIS_I

12 bytes are still available.

at^sisr=0,6

The host requests to read the next part of 6 bytes.

^SISR: 0,6,6

The next 6 bytes of datagram A are confirmed and transmitted. Another

S_DATA

6 bytes are still available.

at^sisr=0,6

The host requests to read the next part of 6 bytes.

^SISR: 0,6,0

Last part of datagram A was received, no remainder is left.

GRAM_A

at^sisr=0,6

Again, the host requests to read 6 bytes. This time, the request refers to

datagram B which has only 3 bytes. As the read datagram is smaller

than the size requested by the host, the response does not include the

<remainUdpPacketLength>.

^SISR: 0,3

3 bytes are confirmed and transmitted. Datagram B was properly

NEW

received.

10.8

AT^SISW Internet Service Write Data

The AT^SISW command triggers a write operation (upload) and queries the amount of data already sent, but not

acknowledged at the TCP layer. The write operation may be run in binary mode, or in interactive text mode.

The AT^SISW write command may return the following errors:

• "+CME ERROR: operation failed" if there is a problem on application, socket, PPP or GPRS/GSM level. The

AT^SISE command and the "^SIS" URC offer additional error information.

• "+CME ERROR: operation temporary not allowed" e.g. if the service has not network resources allocated.

• "+CME ERROR: operation not allowed" e.g. if the service is not configured.

Syntax

Test Command

AT^SISW=?

Response(s)

Write Command

AT^SISW=<srvProfileId>, <reqWriteLength>[, <eodFlag>[, <mode>[, <optServParam>]]]

Response(s)

^SISW: <srvProfileId>, <cnfWriteLength>, <unackData>

Number of data bytes as specified by <cnfWriteLength>.

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Unsolicited Result Code

^SISW: <srvProfileId>, <urcCauseId>

Data availability status of the Internet service configured with AT^SISS has changed. The URC is issued when

the service is ready to accept new user data.

The URC is disabled in polling mode. See AT^SCFG, parameter "Tcp/WithURCs", <tcpWithUrc>.

Parameter Description

<srvProfileId>^(num)

<srvProfileId> 0 ... 9 specified with AT^SISS.

<reqWriteLength>^(num)

0...1500

Specifies the number of bytes to be sent with AT^SISW or, if set to 0, requests the amount of data already sent

with AT^SISW but not yet acknowledged:

• Parameter <reqWriteLength> may be 1...1500 bytes to specify the amount of data to be sent with

AT^SISW.

• If parameter <reqWriteLength> equals 0, AT^SISW does not expect any data, but a normal query is per-

fomed. This allows the application to explictly request, in particular at the end of an upload job, the amount of

unacknowledged data at the TCP layer indicated by <unackData>.

• In interactive text mode, <reqWriteLength> must be set to any value greater than 0 (but not necessarily

the precise number of bytes). If set to 0 in interactive text mode, <reqWriteLength> would be interpreted

as query for unacknowledged data and, thus, prevent data transfer.

• If Socket service is selected with UDP protocol

<reqWriteLength>=0 can be used to send an empty UDP packet;

- it is recommended that the size of each data packet be limited to 1472 bytes. Otherwise, it is possible that

the following URC occurs: "^SIS: <id>, 0, 9, The supplied buffer was too small / large".

<eodFlag>^(num)

End of data indication flag.

Parameter is ignored for HTTP, POP3, FTP download, Socket with UDP protocol.

[0]

No end of data. Other data may follow to be transmitted via the Internet service.

End of data is signalled to the Internet Service. Further AT^SISW write com-

mands return an error response. However, reading data may be possible. The

<eodFlag> is effective only if the <reqWriteLength> equals <cnfWrite-

Length>, in particular if the <reqWriteLength> equals 0.

If <mode> equals 1 the <eodFlag> is effective only if the write operation has

been finished with CTRL-Z.

<mode>^(num)

Control how the application provides the data bytes to be sent.

[0]

Binary mode

This mode allows sending a number of bytes defined with parameter

<reqWriteLength>.

Interactive text mode

This mode allows the user to type and send 8-bit ASCII characters while the

service is open. Ctrl-Z terminates data input and causes the data to be trans-

ferred.

Interactive text mode requires that the <reqWriteLength> is set to any value

greater than 0 (though it is not necessary to specify the precise number of

bytes). In this case the <cnfWriteLength> parameter indicates the maxi-

mum length of the data stream without control character CTRL-Z.

In interactive text mode, the following characters are predefined as control

codes:

• BACKSPACE ("\x08") deletes the last given character,

• CTRL-Z ("\x1a") terminates the input,

• ESC ("\x1b") aborts the command. An <eodFlag> is ignored in this case.

The V.25 command ATE also controls the echo mode of the interactive text

mode. If echo is enabled (ATE1) all characters are echoed until <cnfWrite-

Length> is reached. Any attempt to input further data ends up with the warn-

ing message 4001 indicated after the data stream has been completed with

CTRL-Z, nevertheless all data within the range of <cnfWriteLength> will be

sent. See also Section 10.13, Internet Service URC "^SIS". ATE0 disables the

echo mode generally.

<optServParam>^(str)

Service specific parameter of the AT^SISW write command. If the Socket service is configured as UDP endpoint

this parameter is mandatory and specifies the IP address (in dotted format) and the UDP port of the remote host.

For each write request another IP address and UDP port may be given.

<cnfWriteLength>^(num)

0...1500

Confirmed number of data bytes which can be transmitted via the Internet ser-

vice configured in <srvProfileId>. In binary mode (see <mode>) this num-

ber may be less or equal to the value requested with <reqWriteLength>.

The application has to deliver exactly the number of bytes indicated by <cnf-

WriteLength>. A 0 value means that no data can be written at this time, i.e.

it serves as a flow control mechanism.

In interactive text mode, <cnfWriteLength> indicates the maximum number

of bytes it can process. Characters above the indicated number are ignored.

<unackData>^(num)

Number of data bytes already sent but not yet acknowledged at the TCP layer.

The value is constantly changing until the entire upload job has completed. If the value equals 0 all data sent so

far is acknowledged.

In binary mode, <unackData> includes the <cnfWriteLength> value of the pending write operation. There-

fore, the very first write operation of an upload job returns identical values for <cnfWriteLength> and

<unackData>.

This mechanism allows the host application to easily verify whether or not the remote host has successfully

received the data.

Parameter is not applicable to HTTP, POP3, SMTP and Socket with UDP protocol. For these services the

counter is always set to 0.

<urcCauseId>^(num)

The service is ready to accept new user data.

Data transfer has been finished successfully and Internet service may be

closed without loss of data.

Notes

• The AT^SISW write command must be terminated only with the ASCII character set with ATS3. The factory

default for S3 is #13 (Carriage Return). Do not send any further characters after the S3 end-of-line identifier,

until the response "^SISW" is received. This is necessary to avoid that any characters related to the AT com-

mand can be interpreted as being part of the data stream to be transferred. Also refer to Section 1.4, AT Com-

mand Syntax.

• If the Socket service is configured for use as UDP client and fixed size and the interactive text mode is active,

the PDU length always equals the specified fixed length. If the input characters exceed the specified fixed

length, then all surplus characters will be ignored. If the input characters are less than the specified fixed

length, then the remaining range will be filled with "\0" bytes.

10.8.1

Usage of parameter <eodFlag>

Service type

Socket

After the service accepts the end-of-data flag the service state changes to "Closing". No fur-

ther user data is accepted.

After releasing the TCP link the service remains in state "Down".

Parameter is not applicable to Socket with UDP protocol, i.e. value is ignored.

FTP

Parameter only applicable for FTP upload session.

After accepting the end-of-data flag the service state changes to "Closing" and starts to end

the running FTP session.

No further user data is accepted.

After the FTP session is completed on FTP protocol level the service state switches to "Down".

In case of successful completion the URC "^SISW: x,2" is generated.

10.9

AT^SICO Internet Connection Open

The AT^SICO write command opens a connection profile (also referred to as bearer). Unlike the AT^SISO com-

mand which starts a connection profile and the service profile bound to it, AT^SICO activates only the selected

connection profile. Another difference over AT^SISO is that AT^SICO disables the inactivity timeout of the

selected connection profile and, therefore, sets the "inactTO" value to -1 (see also AT^SICS). To release the

connection use the close command AT^SICC. Closing the bearer restores the previously set "inactTO" value of

the concerned connection profile.

The AT^SICO command may be used, for example, to keep a bearer open while no service is active (i.e. while

no service has been opened with AT^SISO). Also, the AT^SICO command is necessary for running the Ping

command AT^SISX when no service has been opened with AT^SISO.

A connection opened with AT^SICO remains open until closed with AT^SICC or, in case of inactivity, discon-

nected by the network after 25 hours usually. The network initiated disconnection can be avoided by sending

AT^SISX at regular intervals (Ping). The Round Trip Time (RTT) of the AT^SISX command strongly depends

on the data traffic of the IP services or DUN connections used at the same time.

Please note that after sending the AT^SICO write command the AT channel is blocked until the connection is

established. The command may be aborted when receiving any character during execution, e.g. "AT" or "at".

The AT^SICO read command requests the current settings of all Internet connection profiles set with AT^SISC.

The output is identical with the read command response of AT^SISC. One line is issued for every possible

parameter of a given <conParmTag> value.

Syntax

Test Command

AT^SICO=?

Response(s)

[^SICO:(list of defined <conProfileId>s)]

Read Command

AT^SICO?

Response(s)

[^SICO: <conProfileId>, <conParmTag>, <conParmValue>]

[^SICO: ...]

Write Command

AT^SICO=<conProfileId>

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Parameter Description

<conProfileId>^(num)

0...5

Internet connection profile identifier defined with parameter <conProfileId>

of AT^SICS.

10.10

AT^SICC Internet Connection Close

The AT^SICC write command releases a connection opened with AT^SICO and restores the previously set inac-

tivity timeout "inactTO" of the selected connection profile.

The command returns an error if any services are bound to this profile. Before using the AT^SICC write com-

mand be sure that all services were closed with AT^SISC.

Syntax

Test Command

AT^SICC=?

Response(s)

[^SICC:(list of defined <conProfileId>s)]

Write Command

AT^SICC=<conProfileId>

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Parameter Description

<conProfileId>^(num)

0...5

Internet connection profile identifier defined with parameter <conProfileId>

of AT^SICS.

Note

• Be sure not to mix up the start and close commands connection profiles and service profiles. It is allowed to

use only the combinations AT^SICO / AT^SICC or AT^SISO / AT^SISC.

10.11

AT^SISX Internet Service Execution

The AT^SISX command sends ICMP (Internet Control Message Protocol) Echo Requests to a target IP address

or host name (also referred to as Ping command).

The AT^SISX command can be used any time while a connection profile, i.e. a bearer, is active. The bearer may

have been started either with AT^SICO, or if a service is in use, with AT^SISO. If issued although no bearer is

active or no connection profile created at all, AT^SISX returns ERROR.

The AT^SISX write command starts the available service type <service>, i.e. the ping command. The com-

mand returns one row for every ICMP Echo Request (max. 30 lines, see parameter <request>). The last Ping

response line is followed by an empty line, then another two lines appear to report a statistic calculated from the

Echo Request responses. To stop the periodic ping type any character, e.g. "AT" or "at". After calling the ping

command the AT channel is blocked until all ICMP requests are executed.

Sending the Ping command does not restart the inactivity timeout "inactTO" of the used connection profile (see

AT^SICS), i.e. if the bearer was opened with AT^SICO the "inactTO" value remains "-1" (= inactivity timeout dis-

abled), and if the bearer was opened with AT^SISO the "inactTO" value set with AT^SICS remains applicable.

The Ping command can only be used to prevent that a network initiated inactivity timeout closes the bearer (see

also description of AT^SICO).

Syntax

Test Command

AT^SISX=?

Response(s)

^SISX:<service>, (list of supported <conProfileId>s), <address>, (range of <request>), (range of

<timelimit>)

Write Command

AT^SISX=<service>, <conProfileId>, <address>[, <request>, <timelimit>]

Response(s)

In case of <pingInfoType>= 1: ICMP Echo Requests (1 - 30 rows)

^SISX:<service>, <pingInfoType>, <conProfileId>, <address>, <roundTripTime>

[...]

In case of <pingInfoType>= 2: Packet statistic (1 row)

^SISX:<service>, <pingInfoType>, <conProfileId>, <sent>, <received>, <lost>,

In case of <pingInfoType>= 3: Time statistic (1 row)

^SISX:<service>, <pingInfoType>, <conProfileId>, <minRTT>, <maxRTT>, <meanRTT>

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Parameter Description

<service>^(str)

“Ping“

Service type.

<conProfileId>^(num)

0...5

Internet connection profile identifier defined with parameter <conProfileId>

of AT^SICS.

<address>^(str)

Target host name or IP address for pinging (i.e. 192.168.1.3).

<request>^(num)

[1]...30

Number of ping requests (ICMP Echo Requests).

<timelimit>^(num)

200...[5000]...10000

Amount of time, in milliseconds, to wait for an Echo Response message related

to a sent Echo Request message.

<pingInfoType>^(num)

Marks the type and format of the information given in the command responses (see syntax of the AT^SISX write

command above).

Ping response(s) received for the ICMP Echo Request(s). Depending on

parameter <request> 1 - 30 rows. Address and Round Trip Time are returned

for each request.

1-row packet statistic calculated from the ping response(s) received for

<pingInfoType>=1.

1-row time statistics calculated from the ping response(s) received for <ping-

InfoType>=1.

<roundTripTime>^(num)

Round Trip Time in milliseconds. If the Echo Response message is not received within the time specified by

<timelimit> the value -1 is returned (e.g. when the bearer shuts down during command execution).

<sent>^(num)

Number of sent packets.

<received>^(num)

Number of received packets.

<lost>^(num)

Number of lost packets.

<lostPercent>^(num)

Lost packets in percent.

<minRTT>^(num)

Minimum Round Trip Time in milliseconds.

10.12

AT^SISE Internet Service Error Report

The AT^SISE write command returns the current error status of the specified Internet service profile. If the ser-

vice profile is not defined or the value is invalid "+CME ERROR" response is returned.

The error status is identical to the content of the "^SIS" URC last issued.

If a service fails the commands AT^SISR or AT^SISW will return an error response. However, if the AT^SISE

command returns <infoID>=0 it is recommended to use the AT+CEER command because a general GSM/

GPRS problem might be the reason.

Syntax

Test Command

AT^SISE=?

Response(s)

Write Command

AT^SISE=<srvProfileId>

Response(s)

^SISE: <srvProfileId>, <infoID>[, <info>]

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Parameter Description

<srvProfileId>^(num)

Internet service profile identifier as defined by AT^SISS <srvProfileId>.

0...9

<infoID>^(num)

Reason for Internet service error. This is a subset of the <urcInfoId>s which can be found in Section 10.13,

Internet Service URC "^SIS".

The value 0 indicates there is no special Internet service error. In this case the application may use AT+CEER

to check for general GSM/GPRS problems.

<info>^(str)

Information text related to <infoID>. This is a subset of the <urcInfoText>s which can be found in Section

10.13, Internet Service URC "^SIS".

Note

• In particular cases, the AT^SISE command may deliver information and warnings. This applies the following

services:

FTP: Information 2100

POP3: Warnings

SMTP: Warnings

If an error occurs the information and warning messages are overwritten by error messages.

10.13

Internet Service URC "^SIS"

This section first describes the syntax and the parameters of the "^SIS" URC. The second part consists of tables

listing the information elements delivered within the "^SIS" URC and the command response of AT^SISE.

The presentation of the "^SIS" URC containing the parameter <urcCause>=0 can be disabled or enabled

depending on whether polling mode or URC mode is preferred. To do so, use the AT^SCFG command, parameter

"Tcp/WithURCs" (refer to <tcpWithUrc>). However, if related to <urcCause>=1 or 2, the "^SIS" URC will

always be delivered regardless of the setting made with AT^SCFG.

Unsolicited Result Code

Indicates an event, an error or an information element. The same information can be obtained via AT^SISE.

^SIS: <srvProfileId>, <urcCause>[, [<urcInfoId>][, <urcInfoText>]]

The URC may appear if an event or an error occurs, for example after opening an Internet service with AT^SISO

or any time during operation. The URC also indicates a request for a mobile terminated Internet service client

connection, or a failure if a mobile terminated request is rejected. Furthermore, the URC may deliver an informa-

tion element resulting from a specific command given in the service profile.

A list of possible causes can be found in the tables below. The tables contain the <urcInfoId> and, if applica-

ble, a specific <urcInfoText>. If marked with *) the precise text related to a <urcInfoId> varies greatly

depending on the scenario and the implementation of the remote server. In these cases, only a brief explanation

of the scenario can be found in the table column "Description".

Parameter Description

<urcCause>^(num)

URC cause identifier.

An event has occurred after opening or while using an Internet service.

The event number is presented via <urcInfoId> and may be an error, a

warning, an information element or a note. Optionally additional information

may be supplied via <urcInfoText>.

Indicates that an opened Socket listener service is receiving a connection

request from a remote client.

The incoming socket connection is dynamically assigned to the next free Inter-

net service profile. In this case, the parameter <urcInfoId> inside the "^SIS"

URC equals the <srvProfileId> of the dynamically assigned service pro-

file. This ID shall be used to accept the connection request with AT^SISO or to

reject it with AT^SISC.

The connection status may be requested by using the AT^SISI read or write

command or the AT^SISO read command. Among other details, the response

indicates the IP address of the remote client (parameter <remAddr>). This

may be helpful to decide whether to accept or reject the request.

Incoming Socket service client connection has failed. The client request was

rejected automatically because no free Internet service profile was available.

<urcInfoId>^(num)

Information identifier related to <urcCause>. See tables below for further detail. The <urcInfoId> number

ranges indicate the type of information element:

0: Service is working properly.

1 - 2000: Error, service is aborted and enters <srvState>=6 (Down).

2001 - 4000: Information related to progress of service.

4001 - 6000: Warning, but no service abort.

6001 - 8000: Notes

Additional information for Socket service: As stated above, if a Socket connection request from a remote client

is received (see <urcCause>=1) the <urcInfoId> equals the <srvProfileId> of the dynamically assigned

free service profile.

<urcInfoText>^(str)

Information text related to <urcCause>. See tables below for further detail.

10.13.1

Information Elements Related to the Service Application

The following table lists the informatiomation elements which may be returned by all supported services within

the "^SIS" URC and the command response of AT^SISE. It should be noted that TCP/IP socket problems may

occur in all Internet service connections (Socket, FTP, HTTP, POP3 or SMTP).

Description

Information Elements Returned by the TCP/IP socket

Invalid socket descriptor

Socket error

Bad address specified

Socket error

Invalid operation

Socket error

No free socket descriptors

Socket error

The operation would block

Socket error

A previous attempt at this operation is still ongoing

Socket error

Socket is not bound

Socket error

The supplied buffer is too small / large

Socket error

Flags not supported

Socket error

Operation not supported

Socket error

The address is already in use

Socket error

The network is unavailable

Socket error

An established connection was aborted (transmission

Socket error

time-out or protocol error)

Remote host has reset the connection

Socket error

No buffer space available

Socket error

The socket is already connected

Socket error

For TCP/IP sockets, the socket is not connected

Socket error

Socket has been shut down

Socket error

Connection timed out

Socket error

Remote host has rejected the connection

Socket error

Remote host is unreachable

Socket error

An unexpected error occurred

Socket error

Host not found

DNS error

An error occurred that may be transient; a further attempt

DNS error

may succeed.

An unrecoverable error occurred

DNS error

General Information Elements

Fatal: The service has detected an unknown error

Indicates that the remote ser-

vice has closed the connection.

The host shall close the service.

Description

Remote peer has closed the connection

Remote peer has closed the

connection unexpectedly, and

no data are available. The host

shall close the service.

Note that the "^SIS" URC only

indicates the <urcInfoId>,

but the AT^SISE command

indicates both the <urcIn-

foId> and the <urcInfo-

Text>.

Fatal: No memory is available for service action

Fatal: Service has detected an internal error

Connection profile not defined.

PPP LCP FAILED

PPP error

PAP Authentication failed

PPP error

CHAP Authentication failed

PPP error

IPCP failed

PPP error

Warnings

4001

Applies only to interactive text

mode: Indicates that number of

input characters is greater than

<cnfWriteLength>.

General Information Elements

6001

General progress information

for connection setup.

10.13.2

Information Elements Related to FTP Service

Description

100

FTP Server rejects session.

101

FTP Server rejects USER command.

102

FTP Server rejects PASS command.

103

FTP Server rejects PASV command or client can't detect

remote IP address.

104

FTP Server rejects requested client action.

105

The given path segment is wrong.

106

The FTP client requests the file

size from the server before

starting the download. During

transmission phase the client

adds the bytes which are sent

via serial line. After transmis-

sion is done the client com-

pares the amount of bytes

transferred via serial line and

socket.

2100

FILE: <filename>

File name assigned by FTP

server if mode=u is used.

10.13.3

Information Elements Related to HTTP Service

Description

Error URCs

200

HTTP-ERR: Not connected - cannot send request

HTTP-ERR: failed on sending request

201

Client error

202

Server error

HTTP-ERR: Service unavailable

203

HTTP-ERR: Redirect failed - too many redirects

Max. number of allowed redi-

HTTP-ERR: Redirect failed - not allowed

rects: 6

HTTP-ERR: Redirect failed - location missing

204

HTTP-ERR: auth failed - user name or password missing

HTTP-ERR: auth failed - user name or password wrong

HTTP-ERR: Authority required for this URL

HTTP-ERR: No access to this URL allowed

Info URCs

2200

HTTP Redirect to: <Host>:<Port> <Path>

2201

HTTP Response <Response code>

Example: ^SIS: 2,3,2201, "HTTP Response: HTTP/1.1

200 OK"

10.13.4

Information Elements Related to POP3 Service

Description

Errors

300

Indicates that the POP3 User Command could

not be executed successfully.

Warnings

4300

POP3 specific warning

10.13.5

Information Elements Related to SMTP Service

Description

Errors

400

Indicates that the SMTP service could not be

executed successfully.

Warnings

4400

SMTP specific warning

^*) Text varies depending on scenario.

10.14

Examples of how to Configure and Use Internet Service Profiles

Below you can find selective examples of how to configure and use Internet service profiles. To visualize the dif-

ference between URC mode and polling mode the operation of services (after opening with AT^SISO) is

explained in separate examples for either mode.

10.14.1

Selecting URC Mode or Polling Mode

To enable or disable the presentation of URCs for the Internet services use the AT^SCFG command, type "TcpIp/

WithURCs" and select "on" or "off" for parameter <tcpWithUrc>.

at^scfg=tcp/withurcs

Query the current setting.

^SCFG: "Tcp/WithURCs","on"

URC mode is enabled (delivery detault).

at^scfg=tcp/withurcs,off

Select polling mode (by switching off URC mode).

^SCFG: "Tcp/WithURCs","off"

Polling mode is accepted.

10.14.2

Configuring Socket Listener

The example assumes that a connection profile has been created as explained in Section 10.1.1 or Section

10.1.2. Keep in mind that if the host is configured as listener another service profile must be left free to be dynam-

ically assigned as Server when the listener receives a connection request from a remote client.

Configure the service profile 4 for use as Socket listener:

at^siss=4,srvType,socket

Select service type Socket.

at^siss=4,conId,0

Select connection profile 0.

at^siss=4,address,"socktcp://lis-

The host specifies its local port 65534 to be used for

tener:65534"

the Socket listener service. The local IP address will

be dynamically assigned when the service is opened

with AT^SISO.

Open the Socket service and query the IP address dynamically assigned to the Socket listener:

at^siso=4

Open the Socket service.

at^siso?

Query the current status of services. All service pro-

^SISO: 0, ""

files are unused, except for service profile 4 which is

^SISO: 1, ""

running in listener mode, where <srvState>=3 (lis-

tening) and <socketState>=3 (LISTENER). The

response also indicates the IP address dynamically

assigned to the listener.

^SISO: 2, ""

^SISO: 3, ""

^SISO: 4, "Socket","3","3","0","0","10.10.0.187:65534","0.0.0.0:0"

^SISO: 6, ""

^SISO: 7, ""

^SISO: 8, ""

^SISO: 9, ""

10.14.3

Configuring Socket Client for Calling a Socket Listener on

Another Host

The example assumes that a connection profile has been created as explained in Section 10.1.1 or Section

10.1.2.

Configure the client's service profile 1 for calling a Socket listener on another host:

at^siss=1,srvType,socket

Select service type Socket.

at^siss=1,conId,0

Select connection profile 0.

at^siss=1,address,"socktcp://

The service profile of the client contains the IP

10.10.0.187:65534"

address and the TCP port of the remote host.

10.14.4

Socket Client Sends Data via TCP Connection (Polling Mode)

The example uses service profile 0 configured for Socket service and TCP.

AT^SISO=0

The host opens service profile 0.

Note: URC ^SISW:0, 1 does not appear! The host

must poll the service state by means of AT^SISI until

the service is in <srvState> "Up".

AT^SISI=0

^SISI: 0,3,0,0,0,0

The service is still in <srvState> "Connecting".

AT^SISI=0

^SISI: 0,4,0,0,0,0

The service is now in <srvState> "Up" and is

ready to accept data.

AT^SISW=0,10

The host requests to write 10 bytes.

^SISW: 0,10,10

Response that 10 bytes can be sent and are unac-

knowledged.

0123456789

AT^SISW=0,10,1

The host requests to write next 10 bytes and enables

the end-of-data flag.

^SISW: 0,0,10

But the service refuses the request, even the end-of-

data flag remains without effect.

AT^SISW=0,10,1

Next try (polling).

^SISW: 0,10,20

Response that the service accepts 10 bytes and this

data and the previously sent data are unacknowl-

edged.

0123456789

AT^SISW=0,0,0

Polling to request unacknowledged data.

^SISW: 0,0,10

There are 10 bytes still unacknowledged.

AT^SISI=0

Polling for

<srvState> change

("Closing"

"Down").

^SISI: 0,5,0,20,10,10

20 bytes are transfered via serial interface, 10 bytes

are acknowledged by remote peer, 10 bytes are on

the way.

AT^SISI=0

Polling for

<srvState> change

("Closing"

"Down").

^SISI: 0,6,0,20,20,0

The Service is in state "Down" and all data is con-

firmed by the remote peer.

AT^SISC=0

Closing the Socket service.

10.14.5

Socket client sends data via TCP connection with URCs

The example uses service profile 0 configured for Socket service and TCP.

AT^SISO=0

The host opens service profile 0.

^SISW: 0,1

Socket service is ready for upload.

AT^SISW=0,10

The host requests to write 10 bytes.

^SISW: 0,10,10

Response that 10 bytes can be sent and are unac-

knowledged.

0123456789

^SISW: 0,1

The URC indicates that the Socket service is ready

to transfer more data. Data of the last AT^SISW

command are transferred to the remote host.

AT^SISW=0,10,1

The host requests to write next 10 bytes and enables

the end-of-data flag to notify that these are the last

10 bytes of the session.

^SISW: 0,10,20

Response that the service accepts 10 bytes and this

data and the previously sent data are unacknowl-

edged.

0123456789

------

Waiting for URC.

^SISW: 0,2

Data transfer has been finished.

AT^SISC=0

Closing the Socket service.

10.14.6

Socket Scenario with UDP Endpoint

The following example shows a communication between a UDP endpoint (host 1) and a UDP client (host 2).

The first part of the example refers to the UDP endpoint and shows the configuration which allows the UDP end-

point to communicate with any UDP client.

The second part shows the settings of a UDP client.

The third and the fourth part are running in parallel: The third part shows the procedures on the UDP endpoint

side done when communicating with a UDP client. The fourth part shows the equivalent steps done by the UDP

client when communicating with the UDP endpoint.

Part 1 - host 1 is configured for use as UDP endpoint:

AT^SISS=0,srvtype,socket

Select service type Socket.

AT^SISS=0,conid,1

Select connection profile 1.

AT^SISS=0,alphabet,1

Choose ASCII alphabet.

AT^SISS=0,address,"sockudp://:6666"

Specify the local UDP port.

Part 2 - host 2 is configured for use as UDP client:

AT^SISS=0,srvtype,socket

Select service type Socket.

AT^SISS=0,conid,1

Select connection profile 1.

AT^SISS=0,alphabet,1

Choose ASCII alphabet.

AT^SISS=0,address,"sockudp://

Specify the address of host 1.

10.10.0.219:6666"

Part 3 - host 1 opens the service and communicates with host 2:

AT^SISO=0

Open the service.

^SISW: 0, 1

The URC indicates that host 1 is waiting on UDP port

6666 and can send data to any UDP client.

^SISR: 0, 1

The URC indicates that host 2 has opened the con-

nection to host 1 and has sent some data.

AT^SISR=0, 100

Host 1 requests to read 100 bytes.

^SISR: 0, 23, 0, 10.10.0.22:6561

Host 1 is reading the text string received from host 2

Hello, I'm the client!

and gets information about the remote client, i.e. the

address of host 2.

AT^SISW=0,1,0,1,"10.10.0.22:6561"

Host 1 starts sending a text string to host 2.

^SISW: 0, 1500, 0

Host 1 is sending a text string to host 2. As a result,

Hi, I'm the UDP endpoint!

host 2 is receiving the URC "^SISR: 0, 1" shown

below in part 4 of the example.

^SISW: 0, 1

The URC confirms that host 1 can send data again.

AT^SISC=0

Close the service.

Part 4 - host 2 opens the service and communicates with host 1:

AT^SISO=0

Open the service.

^SISW: 0, 1

The URC indicates that theservice is ready.

AT^SISW=0,1,0,1

Host 2 has entered interactive text mode and starts

to write.

^SISW: 0, 1500, 0

Host 2 is writing a text string. As a result, host 1 is

Hello, I'm the client!

receiving the URC "^SISR: 0, 1" shown above in part

3 of this example.

^SISW: 0, 1

The URC confirms that there is no further data avail-

able.

^SISR: 0, 1

The URC indicates that data has been received.

AT^SISR=0,100

Host 1 requests to read 100 bytes.

^SISR: 0, 26

The response indicates that host 2 has received 26

Hi, I'm the UDP endpoint.

characters from host 1.

AT^SISC=0

Close the service.

10.14.7

Configuring and Using FTP Download (URC Mode)

First set up a connection profile as explained in Section 10.1.1 or Section 10.1.2. Enter at least all parameters

which are mandatory for the connection profile.

Configure the service profile 1 for FTP:

at^siss=1,srvType,ftp

Select service type FTP.

at^siss=1,conId,0

Select connection profile 0.

at^siss=1,address,"ftp://

Specify FTP address with user and password anon-

192.168.1.2;type=d"

ymous.

Make an FTP connection:

at^siso=1

Open the service.

Bearer is established, service is getting started.

^SISR: 1, 1

Data is available.

at^sisr=1,1500

Request to read 1500 bytes.

^SISR: 1, 50

50 bytes are now available.

hardware

inttest

software

support

systemtest

^SISR: 1, 2

Data transfer finished. No more data available. The

connection to the FTP server is closed.

at^sisc=1

Close the service.

10.14.8

Configuring and Using FTP Upload (URC Mode)

First set up a connection profile as explained in Section 10.1.1 or Section 10.1.2. Enter at least all parameters

which are mandatory for the connection profile.

Configure the service profile 1 for FTP:

at^siss=1,srvType,ftp

Select service type FTP.

at^siss=1,conId,0

Select connection profile 0.

at^siss=1,address,"ftpput://

Specify FTP address with individual user name and

myname:mypasswd@192.168.1.2/upload/exam-

password. The file "example.bin" shall be created on

ple.bin;type=i"

the FTP server.

Make an FTP connection:

at^siso=1

Open the service.

Bearer is established, service is getting started.

^SISW: 1, 1

FTP service is ready for upload.

at^sisw=1,100

Client requests to send 100 bytes.

^SISW: 1,100,100

The write command response confirms that 100

bytes must be transferred now.

0123456789012345678901234567890123456789012

User data is transferred.

3456789012345678901234567890123456789012345

67890123456789

^SISW: 1, 1

URC indicates that the FTP service is ready to trans-

fer more data. Data of the last AT^SISW command is

transferred to the remote host.

at^sisw=1,0,1

No more data available. The file "example.bin" shall

be closed on the FTP server.

^SISW: 1, 2

Data transfer finished successfully. The connection

to the FTP server is closed.

at^sisc=1

Close the FTP service.

10.14.9

Configuring SMPT Service Profile

First set up a connection profile as explained in Section 10.1.1 or Section 10.1.2. Enter at least all parameters

which are mandatory for a CSD or GPRS profile. The example uses the connection profile ID 1 and the service

profile ID 9.

at^siss=9,srvType,"Smtp"

Select service type SMTP.

at^siss=9,alphabet,"1"

Choose ASCII alphabet.

at^siss=9,conId,"1"

Select connection profile 1.

at^siss=9,address,"192.168.1.2"

Specify SMTP server address.

at^siss=9,user,"subscriber1"

Specify sender's user name required for SMTP

authentication.

at^siss=9,passwd,"subscr1"

Specify password used by the sender for SMTP

authentication.

at^siss=9,smFrom,"subscriber1@testdo-

Sender's email address.

main.com"

at^siss=9,smRcpt,"subscriber2@testdo-

Recipient's email address.

main.com"

at^siss=9,smSubj,"Meeting Request Sunday

Enter text for subject field.

Morning"

at^siss=9,smAuth,"1"

Sender name and password can be used for SMTP

authentication.

at^siss?

To check the profile enter the AT^SISS read com-

^SISS: 0, "srvType", ""

mand. The response includes the values of all 10

^SISS: 1, "srvType", ""

connection profiles. In this example, no values are

set for the profiles 0 through 8. Service profile 9 con-

^SISS: 2, "srvType", ""

tains the values specified above and the values auto-

^SISS: 3, "srvType", ""

matically assumed by default.

^SISS: 4, "srvType", ""

^SISS: 6, "srvType", ""

^SISS: 7, "srvType", ""

^SISS: 8, "srvType", ""

^SISS: 9, "srvType", "Smtp"

^SISS: 9, "conId", "1"

^SISS: 9, "alphabet", "1"

^SISS: 9, "address", "192.168.1.2"

^SISS: 9, "user", "subscriber1"

^SISS: 9, "passwd", "*******"

^SISS: 9, "smFrom", "subscriber1@testdomain.com"

^SISS: 9, "smRcpt", "subscriber2@testdomain.com"

^SISS: 9, "smCC", ""

^SISS: 9, "smSubj", "Meeting Request Sunday Morning"

^SISS: 9, "smHdr", ""

^SISS: 9, "tcPort", "25"

Default: TCP port number commonly used for SMTP.

^SISS: 9, "smAuth", "1"

^SISS: 9, "tcpMR", "10"

Default: Number of retransmission attempts for TCP

packets is 10 (= default of AT^SCFG).

^SISS: 9, "tcpOT", "6000"

Default: Timeout before closing outstanding TCP

connection is 6000 sec (= default of AT^SCFG).

10.14.10

Sending Email (URC Mode)

This example uses the service profile described in Section 10.14.9.

at^siso=9

Open the service, i.e. start to send the email.

^SISW: 9, 1

The "^SISW" URC indicates that email data can be

transferred.

at^sisw=9,87

The email to be sent has 87 bytes.

^SISW: 9,87,87

The write command response confirms that 87 bytes

are available for transmission.

Good Morning everyone, we are delighted to

Write the message text.

announce our next meeting on Sunday morning.

at^sisw=9,0,1

Set the <eodFlag> to mark the end of the email

body.

^SISW: 9,0,0

The <eodFlag> is accepted by the service.

^SISW: 9,2

The "^SISW" URC confirms that all data is sent suc-

cessfully.

at^sisi=9

Check the connection state of the service profile 9.

^SISI: 9,6,0,87,0,0

The command response confirms that the SMTP

service is in state "6" (Down) and that 87 bytes have

been transferred.

at^sisc=9

Close the service.

10.14.11

Sending Email (Polling Mode)

This example uses the service profile described in Section 10.14.9.

at^siso=9

Open the service, i.e. start to send the email.

at^sisw=9,10

Try to write 10 bytes.

^SISW: 9, 10, 0

The service response indicates that 10 bytes can be

written.

Hallo Tom!

Write 10 bytes.

at^sisw=9,10

Try to write 10 bytes.

^SISW: 9, 0, 0

The service response indicates that the service

refuses to accept any data at the moment.

at^sisw0=9,12

Try to write 12 bytes.

^SISW: 9, 12, 0

The service response indicates that 12 bytes can be

written.

Bye Bye Tom!

Write 12 bytes.

at^sisw=9,0,1

Set the <eodFlag> to mark the end of the email

body.

^SISW: 9,0,0

The <eodFlag> is accepted by the service.

at^sisi=9

Check the connection state of service profile 9.

^SISI: 9,5,0,22,0,0

The command response confirms that the SMTP

service is in state "5" (Closing) and that 22 bytes

have been written.

at^sisi=9

Check the connection state of service profile 9.

^SISI: 9,6,0,22,0,0

The command response confirms that the SMTP

service is in state "6" (Down) and that 22 bytes have

been written.

at^sise=9

Check error status of service profile 9.

^SISE: 9,0

The command response confirms that no error

occurred.

at^sisc=9

Close the service.

10.14.12

Configuring POP3 Service Profile

First set up a connection profile as explained in Section 10.1.1 or Section 10.1.2. Enter at least all parameters

which are mandatory for a GPRS profile. The example uses the connection profile ID 1 and the service profile

ID 1. The service profile is set up to retrieve a specific email (email number 2).

at^siss=1,srvType,"Pop3"

Select service type POP3.

at^siss=1,conId,"1"

Select connection profile 1.

at^siss=1,address,"192.168.1.2"

Specify POP3 server address.

at^siss=1,user,"subscriber1"

Specify recipient's mailbox name.

at^siss=1,passwd,"subscr1"

Password used by recipient for authentication to

POP3 server.

at^siss=1,pCmd,"3"

Command used to retrieve emails.

at^siss=1,pNumber,"2"

Email message number 2 shall be retrieved.

at^siss?

To check the profile enter the AT^SISS read com-

^SISS: 0, "srvType", ""

mand. The response includes the values of all 10

^SISS: 1, "srvType", "Pop3"

connection profiles. Service profile 1 contains the

values specified above and the values automatically

^SISS: 1, "conId", "1"

assumed by default.

^SISS: 1, "alphabet", "0"

Default: Character set enabled with AT+CSCS shall

be used.

^SISS: 1, "address", "192.168.1.2"

^SISS: 1, "user", "subscriber1"

^SISS: 1, "passwd", "*******"

^SISS: 1, "pCmd", "3"

^SISS: 1, "tcPort", "110"

Default: TCP port number commonly used for POP3.

^SISS: 1, "pNumber", "2"

^SISS: 1, "pLength", "0"

Default: Message size shall not be limited.

10.14.13

Retrieving Email (URC Mode)

This example uses the service profile described in Section 10.14.12.

at^siso=1

Open the service that was created to retrieve email

number 2 from the POP3 server.

^SISR: 1, 1

The "^SISR" indicates that data is available for read-

ing.

at^sisr=1,500

Try to read 500 bytes.

^SISR: 1, 500

Command response indicates that 500 bytes will be

transferred, i.e. there will be no other URC since the

requested length equals the confirmed length.

Return-Path: <subscriber1@testdomain.com>

X-Original-To: subscriber1@testdomain.com

Delivered-To: subscriber2@testdomain.com

Received: from 10.10.0.132 (unknown [10.10.0.132])

by testdomain.com (Postfix) with SMTP id 379321D004

for <subscriber1@testdomain.com>; Tue, 20 Dec 2005 08:00:07 +0100 (CET)

To: subscriber2@testdomain.com

Cc:

From: subscriber1@testdomain.com

Subject: TestMail

Message-Id: <20051220070007.379321D004@testdomain.com >

Date: Tue, 20 Dec 2005 08:00:07 +0100

at^sisr=1,500

Try to read another 500 bytes.

at^sisr=1,78

Command response indicates that only 78 bytes will

transferred.

(CET)

X-UIDL: &lL"!(Z6"!^cl!!1+%"!

Status: RO

Hallo Tom!Bye Bye Tom!

Dot indicates end of mail according to RFC 2821.

^SISR: 1, 2

Parameter <urcCauseId> of the "^SISR" URC

confirms that all data is transferred successfully.

at^sisc=1

Close the service.

10.14.14

Retrieving Email (Polling Mode)

This example uses the service profile described in Section 10.14.12.

at^siso=1

Open the service that was created to retrieve email

number 2 from the POP3 server.

at^sisr=1,1000

Try to read 1000 bytes.

^SISR: 1, 0

Command response indicates that currently no data

is available.

at^sisr=1,1000

Again, try to read 1000 bytes.

^SISR: 1, 0

Command response indicates that currently no data

is available.

at^sisr=1,1000

Again, try to read 1000 bytes.

^SISR: 1, 578

Command response indicates that 578 bytes are

available for reading.

Return-Path: <subscriber1@testdomain.com>

X-Original-To: subscriber1@testdomain.com

Delivered-To: subscriber2@testdomain.com

Received: from 10.10.0.132 (unknown [10.10.0.132])

by testdomain.com (Postfix) with SMTP id 379321D004

for <subscriber1@testdomain.com>; Tue, 20 Dec 2005 08:00:07 +0100 (CET)

To: subscriber2@testdomain.com

Cc:

From: subscriber1@testdomain.com

Subject: TestMail

Message-Id: <20051220070007.379321D004@testdomain.com >

Date: Tue, 20 Dec 2005 08:00:07 +0100 (CET)

X-UIDL: &lL"!(Z6"!^cl!!1+%"!

Status: RO

Hallo Tom!Bye Bye Tom!

Dot indicates end of mail according to RFC 2821.

at^sisr=1,1000

Try to read 1000 bytes once again.

^SISR: 1,-2

No more data available to read, i.e. the service has

finished.

at^sisi=1

Check the connection state of service profile 1.

^SISI: 1,6,578,0,0,0

The command response indicates that the POP3

service is in state "6" (Down) and that 578 bytes have

been retrieved.

at^sise=1

Check error status of service profile 1.

^SISE: 1,0

The command response confirms that no error

occurred.

at^sisc=1

Close the service.

10.14.15

HTTP POST (Polling Mode)

at^siss=1,srvType,"Http"

Select service type HTTP.

at^siss=1,conId,1

Select connection profile 1.

at^siss=1,hcMethod,1

Select "Post" method.

at^siss=1,address,"http://192.168.1.3/datafiles/dummy/dummy.txt"

at^siss=1,hcContLen,180

Try to upload 180 bytes.

at^siso=1

Open the service.

at^sisw=1,100

Send the first 100 bytes.

^SISW: 1, 100, 0

at^sisw=1,100

Try to send again 100 bytes.

^SISW: 1, 80, 0

80 bytes are sent.

at^sisw=1,40

Try to write data once again.

^SISW: 1, 0, 0

No further data available, i.e. the service has fin-

ished.

at^sisi?

^SISI: 1,6,0,180,0,0

The command response indicates that HTTP service

is in state "6" (Down) and that 180 bytes have been

sent.

at^sise=1

Check error status of service profile 1.

^SISE: 1,0

The command response confirms that no error

occurred.

at^sisc=1

Close the service.

10.14.16

HTTP GET (Polling Mode)

at^siss=0,srvType,"Http"

Select service type HTTP.

at^siss=0,conId,1

Select connection profile 1.

at^siss=0,hcMethod,0

at^siss=0,address,http://192.168.1.4/

at^siso=0

at^sisr=0,1500

Start reading data in polling mode.

^SISR: 0, 1264

...DATA...

at^sisr=0,1500

^SISR: 0, 1500

...DATA...

at^sisr=0,1500

^SISR: 0, 602

...DATA...

at^sisr=0,1500

Again, try to read 1500 bytes.

^SISR: 0, -2

Nor more data to read, i.e. the service has finished.

at^sisi?

^SISI: 0,6,0,3366,0,0

The command response indicates that the HTTP

service is in state "6" (Down) and that 3366 bytes

have been read.

at^sise=0

Check error status of service profile 0.

^SISE: 0,0

The command response confirms that no error

occurred.

at^sisc=0

Close the service.

11.

GPRS Commands

This chapter describes AT commands that a TE (Terminal Equipment, e.g. an application running on a controlling

PC) may use to control the TC65i acting as GPRS Mobile Termination (MT). Please use chapter "Using GPRS

AT commands (Examples)" as a first guidance.

11.1

AT+CGACT PDP context activate or deactivate

Syntax

Test Command

AT+CGACT=?

Response(s)

+CGACT: (list of supported <state>s)

Read Command

AT+CGACT?

Response(s)

+CGACT: <cid>, <state>

[+CGACT: <cid>, <state>]

Write Command

AT+CGACT=[<state>[, <cid>[, <cid>[,... ]]]]

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

GSM 07.07

Command Description

The test command is used for requesting information on the supported PDP context activation states.

The read command returns the current activation states for all the defined PDP contexts.

The write command is used to activate or deactivate the specified PDP context(s). After the command has com-

pleted, the MT remains in V.250 command state. If any PDP context is already in the requested state, the state

for that context remains unchanged. If the MT is not GPRS attached when the activation form of the command

is executed, the MT first performs a GPRS attach and them attempts to activate the specified contexts. If no

<cid>s are specified the activation/deactivation form of the command activates/deactivates all defined contexts.

Parameter Description

<state>^(num)

Indicates the state of PDP context activation.

detached

[1]

attached

11.2

AT+CGANS Manual response to a network request for PDP con-

text activation

Syntax

Test Command

AT+CGANS=?

Response(s)

+CGANS: (list of supported <response>s), (list of supported <L2P>s)

Write Command

AT+CGANS=[<response>[, <L2P>[, <cid>]]]

Response(s)

CONNECT

NO CARRIER

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

GSM 07.07

Command Description

The write command requests the MT to respond to a network request for GPRS PDP context activation which

has been signaled to the TE by the RING or CRING unsolicited result code. The <response> parameter allows

the TE to accept or reject the request.

Parameter Description

<response>^(num)

[0]

the request is rejected and the MT returns OK to the TE

accept and request that the PDP context be activated

<L2P>^(str)

a string parameter which indicates the layer 2 protocol to be used (see AT+CGDATA command)

<cid>^(num)

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

Note

• If <response> is 1, the following procedure is followed by the MT:

If the <L2P> parameter value is unacceptable to the MT, the MT will return an "ERROR" or "+CME ERROR:

<err>" response. Otherwise, the MT issues the intermediate result code CONNECT and enters V.250 online

data state.

A <cid> may be specified for use in the context activation request.

During the PDP startup procedure the MT has the PDP type and the PDP address provided by the network

in the Request PDP context activation message. If this is in conflict with the information provided by a spec-

ified <cid>, the command will fail. There will be no conflict, if the PDP type matches exactly and the PDP

address given by the context definition for <cid> is empty or matches exactly with the address specified with

the network PDP context activation message.

The context will be activated using the values for PDP type and address provided by the network, together

with all other information found in the PDP context definition. An APN may or may not be required, depending

on the application.

If no <cid> is given or if there is no matching context definition, the MT will attempt to activate the context

using the values for PDP type and address provided by the network. The other parameters will be set to their

default values (see AT+CGDCONT).

If activation is successful, data transfer may proceed.

After data transfer is complete, and the layer 2 protocol termination procedure has completed successfully,

the V.250 command state is reentered and the MT returns the final result code OK.

In the event of an erroneous termination or a failure to start up, the V.250 command state is re-entered and

the MT returns the final result code NO CARRIER, or if enabled, "+CME ERROR: <err>". Attach, activate and

other errors may be reported. It is also an error to issue the AT+CGANS command when there is no pending

network request.

The command may be used in both normal and modem compatibility modes.

11.3

AT+CGATT GPRS attach or detach

Syntax

Test Command

AT+CGATT=?

Response(s)

+CGATT: (list of supported <state>s)

Read Command

AT+CGATT?

Response(s)

+CGATT: <state>

Write Command

AT+CGATT=[<state>]

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

GSM 07.07

Command Description

The test command is used for requesting information on the supported GPRS service states.

The read command returns the current GPRS service state.

The write command is used to attach the MT to, or detach the MT from the GPRS service. After the command

has completed, the MT remains in V.250 command state. If the MT is already in the requested state, the com-

mand is ignored and the OK response is returned. Any active PDP contexts will be automatically deactivated

when the attachment state changes to detached.

Parameter Description

<state>^(num)

Indicates the state of GPRS attachement.

0^(P)

detached

[1]

attached

Notes

• If the MT is in dedicated mode, write command returns "+CME ERROR: operation temporary not allowed".

• 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

<state>=1.

• Under some network conditions the GPRS attach command fails, if entered immediately after a "+CREG: 1"

URC. This can be avoided by waiting at least 1s before entering the GPRS attach command.

11.4

AT+CGAUTO Automatic response to a network request for PDP

context activation

Syntax

Test Command

AT+CGAUTO=?

Response(s)

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

Read Command

AT+CGAUTO?

Response(s)

+CGAUTO: <n>

Write Command

AT+CGAUTO=[<n>]

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3

Charge

Last

Reference(s)

GSM 07.07

Command Description

The test command returns the values of <n> supported by the MT as a compound value.

The write command disables or enables an automatic positive response (auto-answer) to the receipt of a

Request PDP Context Activation message from the network. It also provides control over the use of the V.250

basic commands ATS0, ATA and ATH for handling network requests for PDP context activation.

Parameter Description

<n>^(num)

Disable automatic response for network requests for GPRS PDP context acti-

vation. GPRS network requests are manually accepted or rejected by the

AT+CGANS command.

Enable automatic response for network requests for GPRS PDP context acti-

vation. GPRS requests are automatically accepted according to the description

below.

3^(&F)(P)

Modem compatibility mode. The automatic acceptance of both GPRS and

incoming CSD calls is controlled by the ATS0 command. Manual control uses

the ATA and ATH commands, respectively, to accept or reject GPRS network

requests or incoming CSD calls.

Notes

• It is allowed to have different AT+CGAUTO settings on different interfaces.

• When the AT+CGAUTO=0 command is received, the MT will not perform a GPRS detach if it is attached. Sub-

sequently, when the MT announces a network request for PDP context activation by issuing the URC RING

or CRING, the TE may manually accept or reject the request by issuing the AT+CGANS command or may sim-

ply ignore the network request.

• When the AT+CGAUTO=1 command is received, the MT will attempt to perform a GPRS attach if it is not yet

attached. Failure will result in ERROR or, if enabled +CME ERROR being returned to the TE. Subsequently,

the MT announces a network request for PDP context activation by issuing the URC RING to the TE, followed

by the intermediate result code CONNECT. The MT then enters V.250 online data state and follows the same

procedure as it would after having received a +CGANS=1 with no <L2P> or <cid> values specified.

• If a GPRS attach will be initiated by this command and the MT is not able to attach for more than 385 seconds

(timer T3310 expired), command returns with "ERROR" or "+CME ERROR: unknown", but MT is still trying

to attach and the requested automatic mode <n> is in use.

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

issued at the same time on the same interface, then this AT command is not executed. Any response belongs

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

switched data call, the CONNECT response does not belong to this data call but to the GPRS. This can be

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

11.5

AT+CGDATA Enter data state

Syntax

Test Command

AT+CGDATA=?

Response(s)

+CGDATA: (list of supported <L2P>s)

Write Command

AT+CGDATA=[<L2P>[, <cid>[, <cid>]]]

Response(s)

CONNECT

NO CARRIER

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

GSM 07.07

Command Description

The test command is used for requesting information on the supported layer 2 protocols to be used between the

TE and MT.

The write command causes the MT to perform all actions which are necessary to establish communication

between the TE and the network using one or more GPRS PDP types. This may include performing a GPRS

attach and one or more PDP context activations. Commands following the AT+CGDATA command in the AT com-

mand line will not be processed by the MT.

If no <cid> is given or if there is no matching context definition, the MT will attempt to activate the context with

PDP type IP and all other context parameters set to their default values (see AT+CGDCONT, AT+CGQREQ,

AT+CGQMIN).

If the <L2P> parameter is omitted, the layer 2 protocol is unspecified and PPP will be used.

If the write command is successful, the MT issues the intermediate result code CONNECT and enters V.250

online data state.

After data transfer is complete, and the layer 2 protocol termination procedure has completed successfully, the

command state is reentered and the MT returns the final result code OK.

If the <L2P> parameter value is unacceptable to the MT, the MT returns ERROR or +CME ERROR.

In the event of erroneous termination or a failure to start up, the command state is reentered and the MT returns

NO CARRIER, or if enabled +CME ERROR.

Parameter Description

<L2P>^(str)

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

[“PPP“]

layer 2 protocol PPP

<cid>^(num)

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

used in other PDP context-related commands.

1...2

Notes

• If the MT is in dedicated mode, write command returns "+CME ERROR: operation temporary not allowed".

• It is possible to leave the GPRS data mode and enter the command mode by using the V.250 command +++.

By using the command AT+CGDATA again, the data mode is reentered. Which context is used to return to

data mode, depends on the supplied parameter <cid>.

If no <cid> is specified, this is equivalent to using the V.250 command ATO, which is usable for GPRS con-

nections too. In this case the first context will be used, which is active and already in data mode since it has

been activated.

It is possible to use AT+CGDATA to enter the data mode for a context, which is not yet in data mode since it

has been activated. With ATO this is not possible.

11.5.1

Automatic deactivation of PDP context during dial-up PPP

When using the AT+CGDATA write command or ATD*99# or ATD*98# the MT issues the intermediate result

code CONNECT and enters V.250ter online data state. In V.250 online data state, first some LCP protocol

exchange between MT and TE is performed to set up the PPP link. After successfully establishing the PPP link,

the MT performs the PDP context activation procedure if the context is not already activated. As a result, the MT

is in a "PDP context activated" state within the PLMN, the PPP link is established on the mobile side and the

mobile is ready for IP data transfer.

If the TE wants to close the LCP link the MT may perform an LCP termination request procedure on PPP level.

After this LCP termination procedure the MT deactivates the PDP context automatically and the MT returns to

V.250 command mode and issues the final result code NO CARRIER.

During the implicit PDP context deactivation procedure after LCP termination the TE may change into V.250

command state (e.g. by using +++ or by toggling DTR if AT&D is set to 1) before the result NO CARRIER occurs.

In this case the application should not try to deactivate the PDP context by using the commands AT+CGACT or

ATH. If DTR is configured to disconnect data connections (AT&D2), then the application should not toggle DTR

during the implicit PDP context deactivation and before "NO CARRIER" is received.

11.6

AT+CGDCONT Define PDP Context

Syntax

Test Command

AT+CGDCONT=?

Response(s)

+CGDCONT: (range of supported<cid>s), <PDP_type>, , , (list of supported <d_comp>s), (list of supported

<h_comp>s)

ERROR

+CME ERROR: <err>

Read Command

AT+CGDCONT?

Response(s)

[+CGDCONT: <cid>, <PDP_type>, <APN>, <PDP_addr>, <d_comp>, <h_comp>]

[+CGDCONT: ...]

ERROR

+CME ERROR: <err>

Write Command

AT+CGDCONT=[<cid>[, <PDP_type>[, <APN>[, <PDP_addr>[, <d_comp>[, <h_comp>]]]]]]

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

GSM 07.07

Command Description

The test command returns supported values as a compound value.

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

The write command specifies the parameters for a PDP context identified by the context identifier <cid>. The

number of contexts that may be in a defined state at the same time is given by the range returned by the test

command. A special form of the write command (AT+CGDCONT=<cid>) causes the values for context <cid> to

become undefined.

Parameter Description

<cid>^(num)

PDP Context Identifier

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

<PDP_type>^(str)

Packet Data Protocol type

Specifies the type of the packet data protocol.

“IP“

Internet Protocol (IETF STD 5)

<APN>^(str)

Access Point Name

The logical name that is used to select the GGSN or the external packet data network. If the value is null or

omitted, then the subscription value will be requested.

<PDP_addr>^(str)

Packet Data Protocol address

Identifies the MT in the address space applicable to PDP (e.g. IP V4 address for PDP type IP). If the value is

null or omitted, then a value may be provided by the TE during the PDP startup procedure or, failing that, a

dynamic address will be requested.

<d_comp>^(num)

Data Compression

Controls the PDP data compression (applicable for Subnetwork Dependent Convergence Protocol (SNDCP)

only) 3GPP TS 44.065

[0]

off

<h_comp>^(num)

Header Compression

Controls the PDP header compression 3GPP TS 44.065, 3GPP TS 25.323

[0]

off

Notes

• The MT supports PDP type IP only.

• All context definitions will be stored non volatile if the ME is configured accordingly (see AT^SCFG parameter

"GPRS/PersistentContexts" (<gpc>)).

• If the non volatile storage of CGDCONT settings is not activated by the AT^SCFG parameter "GPRS/Persis-

tentContexts", then AT&F and ATZ will undefine every context which is not active or not online.

11.7

AT+CGEQMIN Rel. 99 Quality of Service Profile (Minimum accept-

able)

Syntax

Test Command

AT+CGEQMIN=?

Response(s)

+CGEQMIN: <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+CGEQMIN?

Response(s)

[+CGEQMIN: <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>]

[+CGEQMIN: ...]

Write Command

AT+CGEQMIN=[<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: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

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 checked by the MT against the negotiated profile returned in the

Activate/Modify PDP Context Accept message.

A special form of the write command, AT+CGEQMIN=<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

<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+CGEQMIN=...,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+CGEQMIN=...,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+CGEQMIN=...,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+CGEQMIN=...,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

<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

<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

11.8

AT+CGEQREQ Rel. 99 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: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

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

<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

<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

<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

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

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

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.

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

Read Command

AT+CGQMIN?

Response(s)

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

[+CGQMIN: ...]

ERROR

+CME ERROR: <err>

Write Command

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

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

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

Please note, that the parameters of the minimum acceptable profile need to meet the following condition:

((AT+CGQMIN.<delay>= 0) OR (AT+CGQREQ.<delay> ≤ AT+CGQMIN.<delay>)) AND

((AT+CGQMIN.<reliability>= 0) OR

(AT+CGQREQ.<reliability> ≤ AT+CGQMIN.<reliability>)) AND

((AT+CGQMIN.<peak>= 0) OR (AT+CGQREQ.<peak> ≥ AT+CGQMIN.<peak>)) AND

((AT+CGQMIN.<precedence>= 0) OR

(AT+CGQREQ.<precedence> ≤ AT+CGQMIN.<precedence>)) AND

(AT+CGQREQ.<mean> ≥ AT+CGQMIN.<mean>)

If this condition is not fulfilled or the network does not support all of the specified minimum QoS settings, then

the activation of the associated context will fail.

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

<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

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“

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

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

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

Please note, that the parameters of the requested QoS profile need to meet the following condition:

((AT+CGQMIN.<delay>= 0) OR (AT+CGQREQ.<delay> ≤ AT+CGQMIN.<delay>)) AND

((AT+CGQMIN.<reliability>= 0) OR

(AT+CGQREQ.<reliability> ≤ AT+CGQMIN.<reliability>)) AND

((AT+CGQMIN.<peak>= 0) OR (AT+CGQREQ.<peak> ≥ AT+CGQMIN.<peak>)) AND

((AT+CGQMIN.<precedence>= 0) OR

(AT+CGQREQ.<precedence> ≤ AT+CGQMIN.<precedence>)) AND

(AT+CGQREQ.<mean> ≥ AT+CGQMIN.<mean>)

If this condition is not fulfilled or the network does not support all of the requested QoS settings, then the activa-

tion of the associated context will fail.

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

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)

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“

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

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3

Charge

Last

Reference(s)

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

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

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

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

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.

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>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

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.

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

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

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.

Note

• AT^SGCONF will respond with "+CME ERROR: operation temporary not allowed" if the module is already

GPRS attached (see AT+CGATT). The same error response is sent during background protocol stack activity,

e.g. during network registration.

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

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

GSM 07.07

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

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

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 TC65i is in dedicated mode, command returns the result code BUSY.

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

• When using the command on the second serial interface please see also Section 1.9.

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

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

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 TC65i is in dedicated mode, command returns the result code BUSY.

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

• When using the command on the second serial interface please see also Section 1.9.

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)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

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.

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)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

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.

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

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.

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.

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

TC65i AT-Commands Set. Manual - part 4