Specifications

Multiport for TNPP and TAP Outdial
142 025-9035AA
In addition, the older versions of ZPAGE and TNPP do not serve as a node that can pass a
page along to another terminal if it is not intended for us. In other words, we must be at the
“end” of the network connections, not somewhere in the middle.
TNPP provides for channel/zone information to be provided along with a page. Right now,
we ignore this information on incoming pages, and set it to a particular default value for
outgoing pages.
These limitations in the single-node software can be overcome by upgrading to the multi-
node TNPP software discussed above - contact Zetron.
Format of TNPP Related Log File Postings
This section covers the format of a TNPP posting in Version 310 log files.
The source and destination units for network related pages is “
p,iiiiN”, this corresponds
to the “
ccuL” of trunks and “c|zzS”of station cards. The “p” is the port number relating
to the posting, for outgoing pages this will be a zero as the interface between the network
card and the main terminal is referred to as port zero. For inbound pages and network
status reporting the port number is the port number or serial channel on the card. The
“
iiii” following the comma is the node ID (node address), in hexadecimal notation. The
“
N” stands for NIU, or Network Interface Unit.
When a network address is in the “source” field, it is the address of the node that originally
sent the page. A network address in the “destination” field then it is the address this
terminal is sending the page to, similar to the transmitter channel and zone values for a RF
page.
Inbound capcode pages and most network status reports do not have a subscriber ID.
Rather than leading off with a subscriber ID, they start with “
NETiiii”, where “iiii” is
the destination node ID.
NET0002 port link up 12:09:40p 1 1,0000N
This terminal sent a link test to the other node, connected to port one, and received the
proper response. This terminal can now send pages to the other node.
NET0002 port Reset sent 12:09:41p 1 1,0000N
This terminal sent a link reset packet to the other node, connected to port one. This is done
when first connecting to the other nodes, after a reboot.
NET0002 port Reset seen 12:09:43p 1 2,0105N
This terminal received a link reset packet from the other node, connected to port two.
? 0009 page bad dest 12:09:57p 1 7AL 1,0111N
The page was to be sent to node “0111”, and the terminal has not been programmed to
know anything about node “
0111”