![tell Pager4 3GA.IN4.R2 Installation And User Manual Download Page 41](http://html1.mh-extra.com/html/tell/pager4-3ga-in4-r2/pager4-3ga-in4-r2_installation-and-user-manual_1083867041.webp)
41
- Local arming failed
: this type of event is generated when local arming fails. This basically
occurs when attempting to arm the device locally while an input is activated for which the
“
Force
” option is not enabled.
- Remote arming failed
: this type of event is generated when remote arming fails. This
basically occurs when attempting to arm the device remotely while an input is activated for
which the “
Force
” option is not enabled.
- Periodic test report
: this type of event is generated according to the periodic test report
settings config
ured in the “
General
” settings menu.
- Incoming call from user
: this type of event is generated when the device receives a call
from a user phone number configured in the device. The caller ID (phone number) should
be presented in the call in order to be identified by the device via CLIP service.
- Incoming call from unknown number
: this type of event is generated when the device
receives a call from a phone number which is not configured in the device as a user phone
number, or a call received with hidden caller ID.
-
Output control by APP ID (1…4)
: this type of event is generated when the output of the
device is controlled from one of the mobile devices (1 to 4) through the mobile application.
Activating the output will generate a new event, while deactivating will generate a restore.
- Entry delay started
: this type of event is generated when a delayed input is activated
while the system is armed and entry delay starts.
- Exit delay started
: this type of event is generated upon arming the system, when exit
delay starts.
Type
: the type of the event which can be new or restore. New event will be generated when a
service event occurs, and restore event will be generated when it restores. In the Contact ID
protocol new event is indicated with 1 (or E), while restore is indicated with 3 (or R).
Remote monitoring
:
In this section you can configure the Contact ID event code for reporting to CMS and can select
the preconfigured notification template for the given event. The Contact ID event code should
only be configured if reporting to CMS is used, otherwise select the notification template named
“
EMPTY
”.
Event code
: in this section you can configure the 3
-digit
Contact ID event code
, consisting of
characters 0..9,A,B,C,D,E,F, which
you wish to assign to the given event. The default event
codes are configured according to the standard list of Contact ID event codes.
Partition
: in this section you can configure the partition number you wish to assign to the given
event. The default configuration for partition is 01, except for error events.
Zone
: in this section you can configure the zone number you wish to assign to the given event.
Notification template
: in this section you can select a preconfigured notification template which
you wish to use for the given event. If you wish to use additional notification templates, these
should be added prior to configuring the events. If you do not wish to send a report to CMS on
the given event, select the template named “
EMPTY
”.