User's Manual

• ALARM id
This shows the ALARM id that was used for the outgoing message, on which the device
generated the response.
• ALARM Prty
This shows the ALARM priority that was used for the outgoing message, on which the
device generated the response.
• ALARM Description
This shows the ALARM Description that was used for the outgoing message, on which
the device generated the response.
• REMOVE AFTER
An Input Program provides the Remove After parameter. It indicates whether the alarm
request stays active until a reset is received from the input program or not.
• CONFIRM ACTION
This shows the setting of the Alarm Confirm Action parameter in the Alarm id. However,
this function is not used anymore. Confirm action is specified in the Group Delivery.
• GROUP DELIVERY
This shows the setting of the Group Delivery parameter in the Alarm id. Values can be
*NONE, *ALL or *ANY. In case of *NONE the parameter is ignored and the alarms remain
on the device until an incoming Confirmation is received for the device with a PIN code.
In case of *ALL, each individual recipient handles messages on individual basis. In case
of *ANY, the message must be distributed to at least one group member. After the first
user confirms, the message is considered delivered and it removes the message for all
group members.
• SILENCE Interval
This shows the setting of the Silence Interval parameter in the Alarm id. This field defines
the number of seconds between repeating the alarm on a device if the device does not
respond.
• STATUS
This is the status of the response. It can be an ACK^, NACK^ or ACK^NACK^.
- ACK^
The device has sent an acknowledgement to confirm that the alarm was received
by the device. Some devices send such an acknowledgement on receiving the
message. Some devices only send an acknowledgement after the message is read
by the receiving person.
- NACK^
The device has sent a negative-acknowledgement to indicate that the device is
unreachable.
- ACK^NACK^
The device has sent an acknowledge to confirm that it received the alarm. However,
DECT Messenger was waiting for a manual acknowledgement from the device user
eLOG
DECT Messenger Fundamentals March 2012 153