User's Manual

With the fields eESPAO_ALA_Prty_from_n and eESPAO_ALA_Prty_to_n you can specify a
range of alarm priorities and set a relationship to the beepcode record type and the priority
record type of the espa datablock.
The Data identifier for the beepcode record type is 3.
The Data identifier for the priority record type is 6.
Table 18: Example eESPAO_ALA_Prty_from/to_n values
Site Area Alarm from Alarm to Beepcode Priority
1 1 0 2 1 2
1 1 3 5 3 1
1 1 6 999 9 3
When a <msgrqs> is sent to the eESPA with an alarm priority equal to 2 for pager 4567, a
datablock is created with a beepcode 1 (data identifier 3) and a priority 2 (High) (data identifier
6). Therefore, all alarms with a priority between 0 and 2 have these specifications.
Example datablock:
(RS: record separator, US: Unit separator
* Alarm priority equal to or between 0 and 2
1US4567RS2USExampleRS3US1RS6US2
* Alarm priority equal to or between 3 and 5
1US4567RS2USExampleRS3US3RS6US1
* Alarm priority equal to or between 6 and 999 (highest possible value)
1US4567RS2USExampleRS3US9RS6US3
An authorized of an entry typically found in this field is as follows: 0
eESPAO_ALA_Prty_to_n
See eESPAO_ALA_Prty_from_n on page 239.
An authorized of an entry typically found in this field is as follows: 999
Table: eESPA_OUTBOUND_CFG
240 DECT Messenger Installation and Commissioning — Book 2 March 2012
Comments? [e-mail]