Cinterion
®
EHS6 AT Command Set
10.6 AT^SISO
EHS6_ATC_V03.001 15/12/3
Confidential / Released
Page 248 of 513
Recently used local IPv4 address in dotted-four-byte format and TCP port separated by colon, e.g.
"192.60.10.10:80".
Remote IPv4 address in dotted-four-byte format and TCP port, separated by colon, e.g. "192.60.10.10:80".
Number of automatically rejected client connect attempts to a Transparent TCP Listener service because the
service is already connected with a client (only relevant for Transparent TCP Listener services with Autoconnect
enabled).
[0] Normal Operation like AT^SISO= <srvProfileId>
1 Show only service parameter of <srvProfileId>
Notes
• If the bearer cannot be established and AT^SISO returns an error there might be a general network problem.
To identify the reason you can take advantage of the AT+CEER command. Using AT+CEER is especially rec-
ommended 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.
• If an FTP connection is no longer available after network loss or server shutdown a 3-minute closing timeout
for each of the two used sockets takes effect, adding up to 6 minutes. The timeout is effective if the AT^SISC
is not sent. Please keep in mind that this time may vary depending on the settings of <tcpMr> and <tcpOt>.
• 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,
AT^SISW or AT^SIST. 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 situa-
tion, but in polling mode the only way to detect the state is using AT^SISI or, alternatively, AT^SISO.
<locAddr>
(str)
<remAddr>
(str)
<rejCounter>
(num)
<optParam>
(num)
To Next Page
Loading...
Need help?
General
