Specifications

System Configuration Files
298 025-9035AA
reference count decremented properly. The FAIL setting results in the page failing, being
logged as an improper mode. The default setting is to FAIL.
V310 On A V310 Database
The Network destination in the subscriber record provides a character string that is a
symbolic destination. This string will be searched for in a table defined by the
OUTBOUND section of network.cus. If the string is not found then the page does not have
a known destination, it will be logged as such and fail. This look-up is done before we
answer the telephone, and works similar to the valid RF channel check.
The string has a companion list of destinations, which are TNPP node IDs along with the
TNPP channel and zone setting to use. For each TNPP destination triplet a network page
gets sent to the specified destination. Each TNPP destination is checked against the
INBOUND mapping, in order to determine if any local RF pages should be generated. If
the node ID is found in the INBOUND table any RF destinations needed are created and
added to the ticket.
The format for describing the destinations is:
OUTBOUND symbol name priority channel|zoneS (more dest)
OUTBOUND symbol name priority node IDN (more dest)
OUTBOUND symbol name priority node ID,TNPP channel,TNPP zoneN (more dest)
OUTBOUND node IDN priority
OUTBOUND node ID,TNPP channel,TNPP zoneN priority (more dest)
OUTBOUND symbol name priority TAP##D channel|zoneS (more dest); TAP outdial
The symbol name is a string of normal printable characters, no more than eight characters
long. Alternatively the destination may be specified by a TNPP node ID, or a node ID plus
TNPP channel and zone values. The format of TNPP node ID, channel, and zone values is
described later. The node ID format is less flexible than the symbolic name format.
Generally, its use should be restricted to test purposes, or secondary node IDs that
functionally are similar to symbolic destinations.
The priority of the outbound TNPP pages is determined by the subscriber's priority. If the
subscriber’s priority is greater than or equal to “4” then the TNPP page will be sent with
its high priority flag set, otherwise it will be a low (or ordinary) priority page.
Valid values are “4” and *:
4 - Normal TNPP subscriber priorities 1, 2, and 3 are sent with TNPP low
priority. Subscriber priorities 4, N, and B are sent with TNPP high
priority.
* - Subscriber priority affects node ID. The subscriber's priority is added to
the node ID to cause the page to be sent to different nodes based on
priority. For priority 1, the node ID is used. For priority 2, the node ID + 1
is used. For priority 3, the node ID + 2 is used, and for priority 4 node ID
+ 3 is used. For a priority of N or B the value node ID + 4 is used.
The actual destinations for the page follow the priority field. Both TNPP destinations and
local RF destinations may be specified. In general when the parameter following the