User's Manual

The value must be the extension number of the device where the message is sent. In most
situations each device defined in eDMSAPI_INBOUND table as *IA has at least one record in
this table.
An authorized of an entry typically found in this field is as follows: 999
eDMSAPIIR_Calling_dev_str
This field specified a descriptor of the calling device. As described in eDMSAPI documentation
section, incoming E2 messages are notified within eDMSAPI through calling device and called
device. When an incoming message (to a device that is defined in eDMSAPI_INBOUND table
as type *IA – incoming call alarm generation) is detected by eDMSAPI, the result action
depends on the Called and Calling device.
The value must be the extension number to which the message was sent.
Possible values are:
Define an extension by number, for authorized, 866.
Define a generic value *ALL.
Define a generic number starting with some characters 85.
An authorized of an entry typically found in this field is as follows: *ALL
eDMSAPIIR_GRP_Name_str
This field specifies the group of users that is notified as a result of the *IA (incoming alarm
generation) process through eDMSAPI. The group must be defined in eKERNEL_GROUP and
eKERNEL_GROUP_MEMBER. A message is created for that group, with alarm identification
(and attributes) specified in eDMSAPI_INBOUND_EVENT table. The corresponding attributes
are defined in eKERNEL_ALARM table.
An authorized of an entry typically found in this field is as follows: REA
eDMSAPIIR_Msg_str
This field specifies the message that is sent as a result of the *IA (incoming alarm generation)
process through eDMSAPI. The group receives a message defined in this field, with alarm
attributes specified in eDMSAPI_INBOUND_EVENT table and
eDMSAPI_INBOUND_RESULT table.
Table: eDMSAPI_INBOUND_RESULT
222 DECT Messenger Installation and Commissioning — Book 2 March 2012
Comments? [e-mail]