AT Commands Reference Guide
80529ST10815A Rev.2– 2017-09-14
ReproductionforbiddenwithoutTelitCommunicationsS.p.A.writtenauthorization‐AllRightsReserved page173of233
#SSLEN – Enable a SSL socket
#SSLEN: (1),(0,1)
Opens a socket SSL to a remote server - #SSLD
#SSLD – Opens a socket SSL to a remote server
AT#SSLD=<SSId>,<r
Port>,<IPAddress>,<
ClosureType>[,<conn
Mode>[,<Timeout>]]
Execution command opens a remote connection via socket secured through SSL.
Parameters:
<SSId> - Secure Socket Identifier
1 - Until now SSL block manage only one socket
<rPort> - Remote TCP port to contact 1..65535
<IPAddress> - string type, address of SSL server
<ClosureType> - how to close SSL socket
0 – Until now only closure type 0 supported. SSL session id and keys are free.
<connMode> - connection mode
0 – online mode connection.
1 – command mode connection (factory default).
<Timeout> - time-out in 100 ms units. It represents the maximum allowed TCP
inter-packet delay. It means that, when more data is expected during the handshake,
the module awaits <Timeout> * 100 msecs for the next packet. If no more data can
be read, the module gives up the handshake and raises an ERROR response.
Note:
if we set
<connMode>
to
online mode connection
and the command is successful
we enter into
online data mode
and we see the intermediate result code
CONNECT
.
After the
CONNECT
we can suspend the direct interface to the socket connection (the
socket stays open) using the escape sequence (
+++
): the module moves back to
command
mode
and we receive the final result code
OK
after the suspension.
After such a suspension, it is possible to resume it by using the
#SSLO
command with the
corresponding
<connId>
.
Note:
if we set
<connMode>
to
command mode connection
and the command is
successful, the socket is opened and we remain in
command mode
and we see the result
code
OK
.
Note:
<Timeout> is the total handshake timeout or, in other words, it is not the
absolute maximum time between the #SSLD issue and the CONNECT/OK/ERROR
response. Though by changing this parameter you can limit the handshake duration
(for example in case of congested network or busy server), there’s no way to be
sure to get the command response within a certain amount of time, because it
depends on the TCP connection time, the handshake time and the computation time
(which depends on the authentication mode and on the size of keys and
certificates).10..5000 - hundreds of ms (factory default is 100)
Note: If secure socket is not enabled, only test requests can be made
To Next Page
Loading...
Need help?
General
