Specifications

301
TNPP and System Startup Events Reporting
Actions Taken
The paging terminal can react to an event occurrence with one or both of the following:
• The FaultRelay action turns on the fault relay for two to three seconds.
• The Page action sends an alphanumeric display page to the specified pager ID
(usually the system operator). The page is sent at the priority level of the subscriber
record.
System Configuration Files
Two different system configuration files control events reporting:
• The events.cus file controls which events (TNPP and/or system startups) are
monitored and what actions are taken when an event occurs (Page and/or
FaultRelay).
• The network.cus file controls the reporting of each event occurrence. Moreover, this
file determines which ports are supervised and which subtypes of events trigger a
message.
Each file must be set separately, however they must work together to create the desired
results. For example, if the events.cus file specifies pages upon TNPP events, then the
network.cus file must indicate the types of TNPP events, and on which ports, that should
trigger those pages.
EVENTS.CUS
The events.cus file has two possible command lines for controlling the events reporting.
Their basic formats are as follows:
StartUp Page<subscriber-id> “<msg>” FaultRelay
TNPP Page<subscriber-id> “<msg>” FaultRelay
StartUp and TNPP refer to the type of event on which to act. Page and FaultRelay refer to
the action(s) to take.
• both keywords are optional
• the order of these two keywords does not matter
• however, the Page action is always performed first
• FaultRelay requires no parameters
• if the keyword is used, the fault relay is turned on
The field <subscriber-id> refers to whom should receive the event page.
• must be an existing subscriber record with status V (valid) or G (group call)
• must have an alphanumeric display pager
The field <msg> refers to any custom display message.
• this field is optional - default values are often sufficient