Specifications
297
The “.CUS” Files
A slightly more complex case is when a range of selected IDs maps to a single “to” 
destination. Thus an inbound mapping of: 
 “INBOUND CAP 0100-0105 ALL ALL 1 3  1|1S”
selects TNPP node IDs of 100 through 105, with any channel and zone values, and maps 
them to local RF channel one, zone one. Low priority pages are mapped to a local priority 
of one, while high priority pages map to a local priority of three.
Another example of many to one mapping might be the collapsing of several TNPP 
channel values to a single local RF channel. Thus to map channel values of one through 
twenty five, destination node ID 50, to local RF channel of two:
 “INBOUND CAP 0050 1-25 ALL 1 3  2|*S”
TNPP ID paging does not have the channel and zone settings; these are extracted from the 
subscriber record in the database. The page priority is obtained in the same fashion. The 
function code is sent along with the subscriber ID and the message, if any.
The basic formats of mapping entries for inbound ID pages are as follows:
INBOUND ID net-id original-id-range 
INBOUND ID net-id DEFAULT  PASS 
INBOUND ID net-id DEFAULT  IGNORE 
INBOUND ID net-id DEFAULT  FAIL 
The ID keyword identifies this mapping entry as applying to ID pages. The “original-id-
range” is a pair of values bracketing the range of network ID values to respond to. The 
keyword DEFAULT is for any network ID that does not fall within any specified original 
id range. Only one DEFAULT line for a given net-id range is permitted. The options for 
the DEFAULT mapping are to pass the network ID, to IGNORE this page, or to FAIL this 
page. Pages that are ignored are not logged; pages that are failed will be logged. 
Outbound TNPP Page Mapping
This section addresses the mapping for outbound pages. 
The programming of the mapping outbound TNPP pages depends on the version of 
database that ZPAGE is running on top of. In Version 310, the destination in a subscriber 
record is an eight-character symbolic destination name. This name is mapped to actual 
TNPP and local RF paging by the network.cus entries.
One option beyond destination selection that is needed is a way to choose how outbound 
TNPP pages with voice time are handled. In some cases this is an error, a mistake during 
ZbaseW entry, and should be logged as such. In other cases it is intended, a subscriber 
with a non-display pager has been set up in Insure mode and knows to call his mailbox if 
he does not hear a voice message when he is out of his local coverage area. The following 
commands are used to select which mode is in effect on the terminal.
NETVOICE ALERT 
NETVOICE FAIL 
The ALERT option strips any voice message off outbound pages with voice time, turning 
them into alert only pages or display pages. The voice message information has its 










