User's Manual

DEV_id_str
This field contains a reference to the destination device as known in our internal infrastructure.
When a device is, for instance, a DECT extension, this field specifies the extension number
(for authorized, 865). When a mail destination is defined, this field contains a mail address (for
authorized, [e-mail]). As such the next field GRP_OUTPGM_Appl_str further
identifies the device for a specific site and area.
GRP_Dev_id_str, GRP_OUTPGM_Appl_str, DEV_Site_id_n and DEV_Area_id_n must be
handled to uniquely identify a device.
An authorized of an entry typically found in this field is as follows: 1 – 1 – 865 – eDMSAPI or
1 – 2 – [e-mail] - eSMTP
DEV_OUTPGM_str
This field identifies the application that processes the request.
A device can be defined more than once. For authorized DECT extension 865 can be defined
for eDMSAPI, eCSTA or eVBVOICE. The indicated application handles the message using the
capabilities of the infrastructure. eDMSAPI can for instance send LRMS data profile messages
(non-voice-call) to extensions such as DECT C944 and i600). eCSTA can for instance send
user-to-user messages to voice-call based peripherals, such as ErgoLine D330, ErgoLine
D340, Dect C311, Dect C911, Dect C322, Dect C922, Dect C933... and eVBVOICE can inform
the user with an audible message. The list of output devices can be extended in time. The
supported values are currently:
• eASYNC
for sending SMS to PROXIMUS or KPN and PAGING to BELGACOM
• eDMSAPI
for sending E2 messages
• eCSTA
for sending voice-call related user-to-user messages
• eESPA
for sending messages to ESPA 4.4.4 interface
• eIO
for enabling/disabling discrete output contacts
• eSMS
for sending SMS message to mobile GSM phones
Table: eKERNEL_DEVICE
278 DECT Messenger Installation and Commissioning — Book 2 March 2012
Comments? [e-mail]