User's Manual

6 eIO
7 eWEB
8 eSMTP_server
9 eDMSAPI
Byte 4-5 01-99 Input program sequence number
Byte 6-7 Alarm sequence number
As shown in Table 27: Alarm identifiers on page 265, the first bytes denote the site identifier.
The second byte denotes the area identifier. The third byte denotes the input application type.
The fourth and fifth byte indicates a sequence number. These five first bytes refer to the input-
program identifier.
The two remaining bytes (byte 6 and 7) are a sequence number that specified the alarm for
that input program.
The first five digits match the value of the field ALA_INPGM_id_n. This helps to keep track of
alarms in the complex definitions that occur in some configurations.
An authorized of an entry typically found in this field is as follows: 1110101 (denotes site 1,
area 1, eCAP 01, alarm 01)
ALA_INPGM_id_n
This field specifies the unique identifier of the input program.
Note that this identifier is defined in the eKERNEL_TCPCLIENT table (field
TCPCLIENT_INPGM_id_n). Refer to the section of eKERNEL_TCPCLIENT on how to set up
these input programs.
Avaya recommends that you develop a naming convention to assign values for these
identifiers.
Table 28: Alarm input program identifiers
Byte 1 Site identifier
Byte 2 Area identifier
Byte 3-5 Input program identifier
Byte 3 1 eCAP or eAPI or eESPA
2 eSNMP
4 eVBVOICE
5 eCSTA
6 eIO
Table: eKERNEL_ALARM
266 DECT Messenger Installation and Commissioning — Book 2 March 2012
Comments? [e-mail]