User's Manual

Figure 108: eVBVOICE Outbound calls
Note:
The keystroke you enter to ensure messages are delivered does not confirm an alarm. If
you want to confirm an alarm, you must call the eVBVOICE application and enter your
pincode to confirm the active alarms.
Important:
It is very important that you link all possible alarms with a wave file in the
eKernel_Message_format table. If there is an alarm which must be sent to a eVBVOICE
device, a wave file related to this alarm id must be defined in the eKernel_Message_Format
table. If you do not define the wave file, the alarm is not processed.
If the wave file defined in the eKernel_message_format table does not exist, the eVBVOICE
application always returns a ‘NACK^NOWAV’ return code to the eKernel application. A
‘NACK^NOWAV’ return code means that the end user never receives the alarm or alarms.
After x retries (see DEV_Retry_count_ALT_DEV_id_n field in the eKernel_device table), the
alarm is reset or set for an alternative device (only if DEV_Retry_count_ALT_DEV_id_n >
0).
Note: Remark : in the current release you cannot configure alternative devices with an
outputpgm (ALT_Alt_OUTPGM_Appl_str in eKErnel_device _alt) for eVBVOICE devices
(ALT_OUTPGM_Appl_str = eVBVOICE), because the alternative device otherwise receives
the name of the wave file specified in the eKernel_Message_format table, instead of the
original message.
VBV4.INI.File Settings
The vbv4.ini file is by default located in the c:\winnt directory.
Note:
Ini Settings use both upper and lower case for readability. However the entry in the file is
not case-sensitive.
Introduction
DECT Messenger Installation and Commissioning — Book 2 March 2012 105