User's Manual

eDMSAPIIE_Calling_dev_str
This field specifies the Calling device in an incoming call alarm generation situation, handled
by eDMSAPI.
The Calling device specified here defines those extensions that can generate an alarm by
sending a message to the related called device.
1. Define an extension by number, for authorized, 866.
2. Define a generic value *ALL.
3. Define a generic number starting with some characters 85*.
An authorized of an entry typically found in this field is as follows: *ALL
eDMSAPIIE_Ala_id_Normal_n
This field defines (based upon appropriate record selection through CLID detection) the alarm
characteristics of the alarm that are initiated as a result of the incoming message process with
a priority = Normal.
The alarm identifier must match a definition in eKERNEL_ALARM table, and defines properties
such as alarm priority, length, and so on.
The remainder of the action is defined in the eDMSAPI_INBOUND_RESULT table, where a
message is defined, and a destination group is assigned, based on calling and called
device.
An authorized of an entry typically found in this field is as follows: 1190101
eDMSAPIIE_Ala_id_Urgent_n
This field defines (based upon appropriate record selection through CLID detection) the alarm
characteristics of the alarm that are initiated as a result of the incoming message process with
a priority = Urgent.
The alarm identifier must match a definition in eKERNEL_ALARM table, and defines properties
such as alarm priority, length, and so on.
The remainder of the action is defined in the eDMSAPI_INBOUND_RESULT table, where a
message is defined, and a destination group is assigned, based on calling and called
device.
An authorized of an entry typically found in this field is as follows: 1190102
Table: eDMSAPI_INBOUND_EVENT
218 DECT Messenger Installation and Commissioning — Book 2 March 2012
Comments? infodev@avaya.com