Datatek UMI User Manual
Page 41
U N I V E R S A L M E D I A T I O N I N T E R F A C E ( U M I ) U S E R M A N U A L
04/30/09
41
calls to originating virtual ports without a PDD specification will be presented a user interface for
“dialing” a destination IP address and TCP port.
When a virtual port is a call receiver (listener), it is assigned a default port number value of 23
(TELNET service). If only one class of service is needed for access to the BNS network, this does
not need to be changed. However, when a specific TCP port is specified via the
hport=
Multiple virtual ports may share the same TCP port value, to define a
hunt group of virtual ports.
A connection that is directed to this TCP port value would select the next available virtual port.
The
hport=
The
cug=[+|-]
list of CUGs assigned to the virtual port. The “
+” will add the
is used to delete the
The
prot option allows the specification of the encapsulation method associated with the virtual
port. The
async encapsulation method uses a telnet service without extensions. This is
applicable to asynchronous connections. The
sync encapsulation is basically the same as
asynchronous, but with the extensions needed for synchronous protocols. The
raw option is used
when no encapsulation is desired. It should be noted that the DT-4000 and DT-2020 series
devices are tolerant of synchronous encapsulation for asynchronous connections, so virtual ports
with these protocols may be grouped together for connections exclusively to endpoints on those
devices. The
vpad option selects a virtual pad service. This allows IP resident entities to access
devices on the DK/BNS network with a mediation service similar to the DT-xx8x devices.
The
crfix=< TRANS | NONULL > option accommodates an anomaly in some early variants of
telnet implementation on UNIX systems, which insert a NULL character in the data stream after a
carriage return. Most end devices are not affected by this NULL character. However, some
devices (e.g. the BNS control computer) have erroneous operation if these characters are
received. The value
TRANS indicates transparent operation, where all data received by the UMI,
including a NULL after a carriage return, is forwarded to the end device. The value of
NONULL
removes a NULL character immediately following a carriage return. No other NULL characters
are affected. The default operation is transparent, and the
crfix option may only be specified if
the protocol selected is asynchronous.
The
crlf=< TRANS | LCS60 > option accommodates Microsoft MSDOS (and Windows variants)
of telnet implementations. These implementations insert a LF character in the data stream after a
carriage return. Since both characters are treated equally by some endpoints, the result is a
double line entry where only one was desired. The LCS60 device would always strip the LF
following a CR. However, this would yield problems for some applications where transparency
was desired. The
crlf option allows the selection of either operation. When the crlf=TRANS is
selected, the virtual port is transparent. When the
crlf=LCS60 is selected, the virtual port
performs LCS60 style processing on the LF following a CR. It is stripped from the data stream.
The
data=<7bit | trans> option allows you to "filter" data to 7bit by essentially masking out the
parity bit on each character. This is useful when a TY card connected to a Network Element is
configured as 8 bit and no parity and the Network Element is 7bit and even parity. Datakit takes
care of parity conversion on egress, but Telnet does not. Some telnet clients will display garbage,
and others will work fine. This feature will eliminate the issue altogether.
The
sess=
sessions. The option is available for sessions that originate in the IP infrastructure, and for the
async encapsulation method. The default value is
trans which provides seamless service instead
of session hold. If the BNS port has been configured with an attention character, that attention