Specifications

295
The “.CUS” Files
Inbound TNPP Page Mapping
This section addresses the mapping for inbound pages. Both capcode and ID pages are
covered. Inbound page handling is described by entries in the INBOUND section of
network.cus. These entries have three main parts, the network destination description, the
TNPP block type, and the local mapping information. Blanks are used as delimiters
between fields within these sections.
A network destination, shown as “net-id” is a set of TNPP node ID values. Each inbound
page will have its destination ID checked against the destination node ID values in the
inbound section. If the ID is found the page is processed according to the information
associated with that ID. If the page's destination ID is not found then the settings of the
DEFAULT entry are applied to the page. If there is no explicit DEFAULT entry then the
page will be failed, and logged as having an unknown destination.
A network destination is in the form of one of the following formats.
1. A single simple value, such as “0100” or “7”.
2. A range of values, specified as value1-value2. Thus “0020-002F” is a range.
Blanks are not allowed between the values and the “-”.
3. A “wildcard” containing value, using a “?” to indicate a wildcard hexadecimal
digit. Thus “0020-002F” could alternatively be specified as “002?”. The simple
implementation restricts wildcarding to hex format mostly because the code I had
on hand uses bit masking to perform the wildcarding. It could be applied to hex or
decimal radix with a rewrite to compare decimal addresses as text strings.
4. The key word DEFAULT, implying all destinations not explicitly listed. The
DEFAULT entry may appear only once for each class of TNPP block. If not
explicitly given the DEFAULT entry will be to FAIL the page as having an
unknown destination.
TNPP networking gives each capcode page a total of three fields that affect the page's final
destination. The first is the TNPP destination node ID. In the original TNPP specification
it was implied that this was the unique ID of a physical TNPP node. Most implementations
of TNPP have added the concept of “secondary node IDs”, which may be both addresses
in addition to a node's primary ID, and addresses that more than one node may recognize
as causing local pages. The second and third destination fields are the TNPP RF channel
and zone, which are used to determine the local RF channel and zone to use to transmit a
received TNPP page on.
Mappings for TNPP capcode pages are flagged by the key word CAP. The basic format of
a mapping entry for inbound capcode pages is as follows:
INBOUND CAP net-id original-dest prior-lo prior-hi local-destination(s)
INBOUND CAP net-id DEFAULT prior-lo prior-hi local-destination(s)
INBOUND CAP net-id DEFAULT IGNORE
INBOUND CAP net-id DEFAULT FAIL
The “original-destination” is the TNPP channel and zone values within the capcode page
block. Blanks are used as delimiters between fields within a destination, that is original-
dest would be typed similar to “23 42”. Any one or both of these fields may be in the form
of one of the following formats.