Specifications

Table Of Contents
Chapter 17 TCP App AT Commands
Multi-Tech Systems, Inc. CDMA C1 AT Commands Reference Guide 103
Command
Possible Responses
AT+WIPCREATE=1,<index>,[<local port>]
[,<peer IP>,<peer port>]
OK
+WIPREADY: 1,<index>
AT+WIPCREATE=2,<index>,<peer IP>,
<peer port>
OK
+WIPREADY: 2,<index>
AT+WIPCREATE=3,<server index>,
<local port>,<from idx>,<to idx>
OK
AT+WIPCREATE?
Lists all open sockets.
+WIPCREATE: <protocol>,<index>,<local port>,
<peer IP>,<peer port>
OK
Values: <protocol>
1 UDP
2 TCP client
3 TCP server
<index>
1-8 Socket or session identifier
<local port>
0 65535 Local TCP/UDP port
<peer IP> Peer IP address; a string between quotes indicating an address either in numeric
form (e.g., “85.12.133.10”) or as a DNS entry (e.g., www.multitech.com)
<peer port>
0 65535 Peer TCP/UDP port
<server index>
1-4 TCP server socket index
<from idx>
1-8 Minimum index for spawned TCP client sockets
<to idx>
1-8: Maximum index for spawned TCP client sockets
Notes: Starting a TCP server requires specifying the maximum number of client sockets
that can be spawned. Do with using the <from idx> and <to idx> parameters.
The value set for <to idx> should be equal or more than <from idx>.
It is not possible to create a client socket with AT+WIPCREATE=2, x, y, z when x
is already reserved by a server with AT+WIPCREATE=3,<server idx>,<local
port>,a,b if one of the TCP client sockets indexes between a and b is already
reserved, be it by a client or a sever range.
The <from idx> and <to idx> are reserved for the server socket till the server
socket and the spawned sockets are closed explicitly. So when trying to create a
new TCP server socket, the <from idx> and <to idx> should be different from
what was used earlier. A parameter used as <from idx> can’t be used as <to idx>
anymore for other TCP server socket creation until spawned sockets with
specified <from idx> and <to idx> are closed along with the TCP server socket
explicitly and vice versa.
When there are no available client indexes in the TCP server’s range (or no more
resources to accept incoming connections), any peer trying to connect to the
server will receive an “accept” immediate followed by a shutdown (“peer
close”).