10
3 General information on the notification process
Notifications are performed based on the events available in the device. Each event can be
configured to send report to CMS over IP or DTMF-based voice call, as well as to send notifications
to users by call, SMS, Push message or e-mail (depending on device model).
There are 3 groups of events available in the device: input events, service events and custom
events.
An input event is generated when an input is activated, but only if the device is armed or the
given input is configured as a 24h zone. Non-24h inputs will not generate events when the
device is disarmed.
Service events are generated automatically by the device, and can send notifications also
when the device is disarmed. Service events are such as arming, disarming, error events,
periodic test report.
Custom events are generated by sending any configurable command to the device in a text
message. Custom events and commands can be freely configured.
When an event is generated, the device starts sending notifications and performing controls
configured for the given event. The notification order corresponds to the order in which the events
occur.
Reporting to CMS has priority against notification of users. The number of attempts for reporting
to CMS have a separate logic, since reporting to CMS is based on notification templates.
You can read more about this in the “
” paragraph. Regarding text message
sending and calls, the device makes 3 attempts to send a message and 3 attempts to make a call
to a user phone number. The device will no longer try to report events for which reporting failed
for more than 24 hours.
