Specifications
System Configuration Files
300 025-9035AA
but only a few lines in network.cus and oparam.cds. A second advantage of symbolic IDs
is that it can be easier to assign meaning to the destinations. As an example, a system
operator might have symbolic destinations of LOCAL_P5, LOCAL_P6, WIDE_P5, and
WIDE_P6, for local and wide area paging for P5 and P6 pagers. One of those four
destinations would be entered in a subscriber record for the Network destination.
Again the outbound section does not contain any RF information, as that is derived from
the inbound mapping for the node ID. If at some time in the future the single channel gets
too busy and the P5 frequency is split off to a second channel only the INBOUND and
OUTBOUND LOCAL_P5 specifications will need to be changed. All subscribers with
LOCAL_P5 or WIDE_P5 need not be changed.
TNPP and System Startup Events Reporting
A new feature has been added to ZPAGE to report TNPP link status and all system
startups. The events subsystem reports various unexpected and atypical incidents, such as
a TNPP link going down. Generally, events are defined as unwelcome occurrences that
cannot be tested for at will. For instance, a subscriber programming error does not qualify
as an event, but an unknown node destination error does. For a list of all the possible
TNPP events see Table 46.
Types of Events
There are two sets of event types that can be reported:
• TNPP events - report problems within the TNPP subsystem
• System startups - report any terminal reboot
• shows the time that paging operations return to active
OUTBOUND WIDE_P5 2 5090N Pages of priority 2 and above are treated as
network high priority. The destination node ID
used is “5090”.
OUTBOUND M600 * B000N Pages are sent to different TNPP destinations
depending on their priority. The main use for this
feature is to allow a Model 600 to prioritize
incoming TNPP pages based on the originating
subscriber's priority setting or by 2000 Series
priority overrides. (This feature was created for use
with the Model 600.)
INBOUND CAP 5090 Default 1 2 1|8S Incoming capcode pages to ID 5090, any TNPP
channel and zone, are sent to local RF channel 1,
zone 8.
OUTBOUND LOCAL_P5 2 1|8S Local P5 pages are on channel 1, zone 8.