User's Manual
Figure 5: Alarm processing structure on page 17 shows the relation among the modules and
how messages are processed.
Figure 5: Alarm processing structure
Alarms originate at an input program (input module). An incoming alarm carries an alarm
identifier and a group identifier. The alarm identifier must match an identifier in the Alarm
Properties functional block, which specifies how the alarm is processed (priority, time intervals,
and so on). The group identifier determines the final destination. The incoming group identifier
must match a group identifier in the Groups functional block, which contains one or more output
destinations (that is, the group members). The group members are the devices assigned to a
Group.
Figure 6: eCONFIG on page 17 shows the main window of eCONFIG with an example of an
input module (the application programming interface [eAPI]). The eAPI input module is found
in eCONFIG in the Modules > eAPI menu. Select the instance of the module as it appears on
your screen (in this example, the menu selection is Modules > eAPI > API - area Area 1).
Each input module displays different properties.
Figure 6: eCONFIG
The following explanations relate to the blocks in Maintaining DECT Messenger using
eCONFIG on page 19:
• Input Module
The Alarm carries two different identifiers from the input module to the actual Kernel: the
alarm identifier and the group identifier. The identifier provides the message for the output
device.
Avaya DECT Messenger overview
DECT Messenger Fundamentals March 2012 17