User's Manual

104 Module - eVBVOICE

Outbound calls

An alarm that is linked with a wave file, if the wave file exists, can be sent

to a device with the eVBVOICE module.

Once all the wave files for a specific call are played, you enter a keystroke

to ensure messages are delivered. This functionality is necessary to be

sure the user hears the messages. Answering machines and voice mails

perform in the same manner.

Figure 104

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.

ATTENTION

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

Nortel Communication Server 1000

DECT Messenger Installation and Commissioning — Book 2

NN43120-301 02.01 4 June 2010