Datatek UMI User Manual

Page 26

Advertising

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

Protocol ==> Asynchronous.
NULL after CR Operation ==> Transparent.

A user on the BNS network can now use the dial string “call-ip” to get a connection to the host at
IP address 135.17.59.20 and receive telnet service (TCP port 23).

To illustrate an alternative setup, suppose we had not entered the PDD information as part of the

vport

command. The calling user would have gotten the

UMI Destination> prompt, and could

then enter “135.17.59.20 23” to reach the same destination and service. This would be
preferable if there were many different endpoints in the IP network which BNS network users
need to reach. Rather than require these users to keep track of a multitude of IP addresses,
mnemonic names could instead be used. Each of these could be set up with the following
command:

<UMI>

host 1 name=ip-host1 ipaddr=135.17.59.20 port=23

↵

BNS users could now type “ip-host1” at the

UMI Destination> prompt to reach the same

destination/service.

In addition to a

UMI Predefined Destination within the IP network, and user prompting to reach

same as described above, the

UMI is also capable of Double Dialing. This is an advanced

feature where the

UMI Destination is provided as an argument to the BNS dialstring used to

reach the

UMI virtual port.

An example is “nj/bwdev/ddumi.bender” without the double quotes. The first part of the dialstring
“nj/bwdev/ddumi” is the BNS address to the

UMI virtual ports. The virtual ports are defined as

BNS_to_IP without a PDD. The name “bender” is the IP destination. Since a mnemonic is used in
this example, the name “bender” must exist in the

UMI host table, or a DNS service must be

enabled for resolution. If the name cannot be resolved, the user will be presented with the

UMI

Destination> prompt .

Physical IP address dialing is also supported. The same example could be
“nj/bwdev/ddumi.192.168.1.25” which would not require an entry in the host table or DNS
resolution. If a specific TCP port is needed, it is appended with a space in the same manner as if
the user had entered it manually. eg. “nj/bwdev/ddumi.192.168.7.200 10001”. Please note that
when using the dkcu command from a UNIX host with a specific TCP port, the entire dialstring
must be double quoted for the dkcu command to receive the argument from the UNIX shell
correctly. If the BNS dialstring is entered at a BNS Destination prompt, the double quotes should
not be used.

The

Double Dialing feature requires a release level of at least Build 92 of Datakit Release 6 to

be installed on the Datakit Node controller. It also requires a release level of at least build 23 to
be installed on the

UMI. The module administration is required to be a UMI (as opposed to being

administered as a SAM) on the Datakit/BNS node.

DTK41 I/O module is required for the use of the Double Dialing feature. If a DTK41 is not

present, the user is presented with the

UMI Destination prompt.

4.3.2 IP-to-BNS

Calling

UMI virtual ports designated as

receive, as part of module-based administration, are for the IP-to-

BNS calling direction

. From the node administration perspective, the corresponding SAM ports

are set up as term

service-type ports, since they act like terminals originating calls on the BNS

Advertising