Specifications
Multiport for TNPP and TAP Outdial
140 025-9035AA
• If going out locally, put to what Channel(s) & Zone(s); if going back out to the 
network, put to which node and what address.
• What priority to assign to these incoming pages (like ZbaseW priority). Please note 
that TNPP pages have two priority levels, ordinary and high. You may choose 
which ZbaseW style priorities to assign to the two network priorities.
Using this information, we will set up the configuration for the terminal in the 
“network.cus” file. 
Network CUS Parameter File
network.cus is a configuration file on the paging terminal. It is not needed unless you 
have one of the TNPP Network options. It is used to relate base network destination names 
to actual network addresses, and to select how incoming pages will be transmitted locally. 
One type of entry in the 
network.cus file is the Outbound entry, which is used to map 
from a TNPP destination name to actual network addresses. It is also used to determine 
how to treat the priority level of outgoing pages. This entry may also be used to set the 
TNPP channel and zone of capcode pages, and to attach local RF channel and zone values 
to network destination names. 
Another type of entry is the Inbound record, which is used to determine what to do with 
incoming network pages that the network card passes along to the terminal. It is used to 
select ranges of node addresses to respond to. TNPP channel and zone values, on capcode 
pages, or subscriber ID values, on ID pages, may also serve as selection criteria. Finally 
the Inbound record is used to describe what RF channel and zone information to use with 
pages that match its selection values. 
Refer to the “System Configuration Files” section later in this manual for general 
information on configuration files. 
Configuration - TNPP Addresses
In addition to the information shown for the basic Multiport card, the following is needed: 
• The incoming TNPP address(es) - our ID(s) that the other machine(s) on the 
network will know us by. 
When the other system sends a page, part of the information packet is an address. 
Since there can be multiple paging terminals on a network, we need to know which 
address means us (or which addresses mean us if Multi-Node). Each address is set 
in the oparam.cds file. Therefore, you need to find out the address(es) that the other 
system will be sending to us, and tell us. 
• The outgoing TNPP address(es) - the ID(s) of another machine or machines on the 
network where we will send outgoing network pages. 
This depends on what the other system's address is (or system addresses are if 










