User's Manual

eKERNEL immediately upon arrival and these alarms are processed within DECT
Messenger.
In some environments, the remote peripherals cannot indicate that pending alarms are reset,
and therefore the eKERNEL must handle the alarms. Use this field to configure
eKERNEL_ALARM table to correctly handle the alarm requests and refrain from endless-loop
conditions. As such alarms are typically *set with the option remove after sent. The
eESPA_Remove_after_str are then set to *SENT.
In some environments, the attached peripherals are capable of sending a reset to clear all
pending alarms. In such case, alarms must be set using the remove after *RESET value,
indicating all pending alarms remain in the eKERNEL database unless the reset condition is
met.
This parameter refers to all alarms, so that means that every alarm must receive a reset (a
reset occurs if data identifier 4 (call type) is equal to value 1).
If the value *CALC is specified, some alarms receive a reset, and other alarms not. Therefore
the eKERNEL application checks to determine if the alarm description with remove after *SENT
exists. If so, this alarm type is processed, otherwise the alarm is processed as if remove after
*RESET is specified.
If the alarm description is not configured in the eKERNEL_ALARM table, the alarm is not
processed.
An authorized of an entry typically found in this field is as follows: *SENT
eESPA_NAK_retry_cnt_n
This field specifies the number of retries to re-transmit a message after receiving a NAK.
A device that has control of the communication line can transfer data to the other devices.
When unable to accept the message, the receiving device sends a negative acknowledge with
a (1 or 2 or 3) NAK sequence, and the sending device can then retransmit the block. If, after
eESPA_NAK_retry_cnt_n attempts, the transmission still fails, and the sending device
terminates transmission with the EOT character.
An authorized of an entry typically found in this field is as follows: 2
eESPA_Timeout_n
This values specifies in seconds how long the station waits, if no valid transactions are detect
on the communication line, before sending a EOT and terminate the communication and regain
control.
An authorized of an entry typically found in this field is as follows: 10
Table: eESPA
234 DECT Messenger Installation and Commissioning — Book 2 March 2012
Comments? infodev@avaya.com