User's Manual

• eSMTP
for sending mail to SMTP-compliant infrastructure
• eVBVOICE
for sending audible messages
DEV_OUTPGM_facility_str
The indicated application handles the message using the capabilities of the infrastructure.
The supported values are specified in the field FMT_OUTPGM_Facility_str of the
eKERNEL_DEVICE_FORMAT table for the corresponding output program.
An authorized of an entry typically found in this field is as follows: C4050 for eDMSAPI
DEV_Visual_dnr_str
When this field is entered for a device, the 'Visual DNR' is used to format a message when it
contains [Calling number], so the end-user is confronted with the visual DNR. The default value
for this field is empty. (This field is new in release 3.0.)
Avaya recommends using this field in Avaya environments only.
An authorized of an entry typically found in this field is as follows: 2000 for DECT handset with
DNR 2000 and hardware ID 00300 (DMC)
DEV_Descr_str
This description is used to show information on devices in the eWeb module. Avaya
recommends adding the name of the owner of the device.
An authorized of an entry typically found in this field is as follows: DECT: Kristien Daneels
DEV_PinCode_str
Some business processes need a confirmation of end-user. Some technologies provide this
during alarm notification, such as LRMS messaging on eDMSAPI allow using “OK” to confirm
message delivery. However, some notification technologies do not offer immediate end-user
confirmation during notification: eASYNC, eSMTP, eSMS and so on.
Some modules provide inbound confirmation: eCSTA by means of inbound voice call (based
upon CLIP), eVBVOICE by means of inbound voice call (based on DTMF entered pincode)
eKERNEL_DEVICE parameters
DECT Messenger Installation and Commissioning — Book 2 March 2012 279