User's Manual

of messages that must be in the queue before processing starts. This value is supported only
for PROXIMUS – SMS and KPN – SMS. This is the only provider that allows the delivery of
more than one message in a single dial-out request, thus potentially reducing communication
costs at the expense of speed. Avaya recommends a value of 1 for most environments,
because processing is usually executed as soon as possible, and any related call setup costs
are therefore less important.
An example of an entry typically found in this field is as follows: 1
eASYNC_Send_time_n
This value specifies (in seconds and in combination with eASYNC_Send_Depth_n) the
moment when actual message delivery is triggered in eASYNC module. When 1 is specified,
immediate processing is triggered when a message request is received from eKERNEL. A
larger value causes the system to wait until the specified number of messages is queued before
processing begins. Note that processing starts due to either Send Depth or Send time,
whichever occurs first. Time can be lost if values larger than 1 are specified.
An example of an entry typically found in this field is as follows: 1
eASYNC_ALA_Prty_DTMF_Confirm_n
This field specifies the priority of the alarm, as defined in ALARM table. Alarms distributed to
eASYNC with priority higher than the defined value are automatically considered
acknowledged, when the provider receives the message. This is usually acceptable; however,
eASYNC typically delivers messages to devices (such as Pagers, GSM, and so on) that cannot
respond with a confirmation. In some circumstances, the message must be active until a
manual confirmation takes place. This can be performed through eASYNC (dial-in and confirm
using CLID).
If the priority of the alarm is lower than or equal to the eASYNC_ALA_Prty_DTMF_Confirm_n
priority, the message reply (<msgrpy>) sent by the eASYNC module to the eKERNEL is treated
as a NACK reply (even if an ACK was sent).
As a result, when alarms that require confirmation are sent using eASYNC and successfully
delivered (status = ACK), they continue to behave as if the status is NACK. The alarm is
repeated every eASYNC_Silence_intv_n seconds until confirmation is received. If the alarm
is not confirmed within DEV_Retry_count_ALT_DEV_id_n (eKERNEL_device) retries, it is sent
to the alternative devices (if configured).
An example of an entry typically found in this field is as follows: 2
eASYNC parameters
DECT Messenger Installation and Commissioning — Book 2 March 2012 191