User`s guide

304
IP Sockets to Protocol Switch
Configuration - Network > Protocol Switch > IP Sockets to Protocol Switch
This page contains a table that allows you to enter a series of IP Port numbers and X.25 Call
strings as shown below. It is used to configure the unit so that IP data can be switched to
any of the protocols support by the protocol switch includingX.25. For example data that is
received on a TCP connection can be forwarded over SSL, XoT or a UDP stream. The only
columns that must be filled out are “Port” and “Number of Sockets”.
This table is duplicated in the Configuration - Network > Legacy Protocols > X.25 > IP
to X.25 Call section as it can also be used to convert an incoming TCP connection to an
X.25 session to be answered by PAD without using the protocol switch. It is included at this
point in the web user interface as a convenience in case the table is being used in
conjunction with PAD and not the protocol switch.
IP Port
The IP Port field is used to setup the port numbers for those IP ports that will “listen” for
incoming connections that are to be switched over X.25 or other protocol. In the case of
switching to X.25, when such a connection is made the unit will make an X.25 Call to the
address specified in the X.25 Call field. Once this call has been connected, data from the
port will be switched over the X.25 session.
Number of Sockets
The Number of Sockets field is used to select how many IP sockets should simultaneously
listen for data on the specified port. The number of available IP sockets will depend on the
model you are using and how many are already in use (see note below).
X25 Call
The X.25 call field may contain an X.25 NUA or NUI or one of the X.25 Call Macros defined
on the Configuration - Advanced applications > X25 > Macros page.
PID
The PID (Protocol Identifier), field specifies the PID to use when the unit switches an IP
connection to X.25. The PID (protocol ID) field takes the format of four hexadecimal digits
separated by commas, e.g. 1,0,0,0, at the start of the Call User Data field in the X.25 call.
Confirm Mode
When confirm mode is set to “On” then the incoming TCP socket will not be successfully
connected until the corresponding outgoing call has been connected. The incoming TCP
socket will trigger the corresponding outgoing call either to a local PAD instance or to
whatever is configured. The effect of this mode is that the socket will fail if the outbound call