User's Manual
GUA_Timeout_n
This field specifies the timeout in seconds, before the defined guarding alarm is activated if no
request (configuration request, message request, and so on) of the input program is received
by the eKERNEL.
If for instance a timeout of 900 seconds is defined, a guarding alarm is generated if the input
program (eCAP, eAPI, and so on) does not send any request within fifteen minutes.
Note that some manufacturers (for authorized, Honeywell) have the possibility to send with a
fix interval a Still alive request to the eCap program. The absence of this request can result in
a guarding alarm.
An authorized of an entry typically found in this field is as follows: 900
GUA_msg_str
This field describes the message that is sent to the group members. Avaya recommends that
you enter descriptive text that provides the recipient sufficient information to handle the alarm
condition. Mobile users often lack immediate access to other information resources, such as
a site map or technical specification. Avaya recommends that you keep the message length
less than, or equal to, the maximum length defined in the associated eKERNEL_ALARM
table.
An authorized of an entry typically found in this field is as follows: HONEYWELL NOT ACTIVE
GUA_GRP_Name_str
The group name describes who receives the guarding alarm, and refers to a group defined in
eKERNEL_GROUP and eKERNEL_GROUP_MEMBER table.
An authorized of an entry typically found in this field is as follows: GUARDING
GUA_ALA_id_n
This field refers to the unique alarm identifiers as specified in the eKERNEL_ALARM table.
See
Table: eKERNEL_ALARM on page 265 for more information on alarm identifies. In a
typical environment, input programs (for authorized, 11101) have a number of alarm identifiers
(for authorized, 1110101 up to 1110107) each of them defining characteristics (alarm priority,
length, and so on).
Refer to
Table: eKERNEL_ALARM on page 265 for more information on naming
conventions.
Table: eKERNEL_GUARDING
312 DECT Messenger Installation and Commissioning — Book 2 March 2012
Comments? infodev@avaya.com