Installing VoiceGuide v7 for Traditional Telephone Lines (Analog/T1/E1)

Installing Dialogic Drivers

Dialogic Drivers (System Release) for use with VoiceGuide can be downloaded from the VoiceGuide Downloads page.
Please always refer to the Dialogic’s Release Notes and/or Installation Notes to determine what Operating System may be used.

The Dialogic card should be placed in system, and the telephone lines should be attached to the cards before the Dialogic System Release drivers are installed. The Dialogic System Release Drives will detect the cards present in system upon installation.
Please refer to installation and configuration instructions for the board which is used.

Dialogic Drivers install asks user to select options to install. It is best to just select all the options available.

If using a 32-bit version of Windows, the Physical Address Extensions (PAE) need to be disabled. Dialogic install program will display an alert if it detects that PAE is enabled on system.

After instaling the Dialogic System Release the machine needs to be restarted.

After restarting the system open the Dialogic Configuration Manager (DCM) and confirm that the Dialogic service can be started.

If there are problems starting the Dialogic service please ensure that the Windows account used has sufficient priviledges and the install was started using 'Ran as Administrator' option.
If there are still problems then please fully disable the Windows' User Access Control and then reinstall the Dialogic System Release drivers. Windows' User Access Control is disabled in the Windows Registry, by setting the EnableLUA parameter to 0.

To re-install Dialogic System Release you need to first fully uninstall it, selecting 'Do not save configuration', and restart system after uninstall.
After instaling the Dialogic System Release the machine needs to be restarted.

The Dialogic service should be set to start automatically. Use DCM 's Settings -> System/Device autostart -> Start System menu, or by using the Windows' Control Panel -> System and Security -> Administrative tools -> Services

Only after the Dialogic System Release drivers are installed on the system and the the Dialogic service is started can the VoiceGuide installation proceed.


Testing Dialogic Installation

Dialogic drivers install some sample programs that can be used to test correct card/drivers operation.

The sample programs are located in this directory:


The C:\ProgramData\ directory is a hidden directory, and needs to be made visible first.

To make C:\ProgramData\ directory visible click on C:\ drive in Windows Explorer, then click on the "Organize" button in top left corner and select "Folder and Search Options". Click on "View" tab and select "Show hidden files, folders and drives" option.

On the older Windows XP and Windows 2003 systems the sample programs are located in this directory:

C:\Program Files\Dialogic\demos\voice\


One of the sample programs that can be used is ANSRMT.EXE, it is located in the \demos\voice\ANSRMT\ subdirectory.


Installing VoiceGuide

Dialogic System Release drivers must be installed first.

VoiceGuide needs to be installed using the Administrator account. If not logged in as Administrator then right click on install .EXE and select 'Run as administrator'.

When installing VoiceGuide select the "Telephone Lines (Analog, T1/E1 ISDN)" option to install the configuration files which are used with the Dialogic cards.


Configuring VoiceGuide

System configuration is set using the Config.xml file. Config.xml file is located in VoiceGuide's \conf\ subdirectory. Config.xml is used to set the script to be used when answering incoming calls, and a number of other settings.

The default Config.xml file opens the first 4 ports of an analog Dialogic card. If an analog Dialogic card is installed then immediately after installing VoiceGuide you will be able to call into the system on any of the 4 ports and you will hear VoiceGuide answer the call and start a demonstration 'Credit Card Payment' script.

If a card other then a 4 port analog card is used then the Config.xml file in VoiceGuide's \conf\ subdirectory will need to be changed to match the card. Sample Config.xml files are provided in that directory as well, showing how Config.xml should be set if a card other then a 4 port analog card is used.

If not running as Administrator then permission changes may need to be made to allow editing of Config.xml, VG.INI, etc. files.

In Windows Explorer:

- Right click on the VoiceGuide directory,
- Select Properties,
- Go to the Security tab,
- Make the necessary changes

Alterntively, the text editor application used to edit the Config.xml, VG.INI, etc. files would need to be started using the 'Run as administrator' option. Then Windows will not block the saving of new versions of Config.xml, VG.INI, etc. files.


After you hear the demonstration script answer the call you are now ready to start creating your own scripts, make outgoing calls etc.
The Script Designer and other VoiceGuide applications can be started by right-clicking on the IVR tray icon and selecting from the context menu.

If not running as Administrator then you will not be able to stop and start the VoiceGuide service using the VoiceGuide Service Monitor applet from the icon tray.
To stop/start the VoiceGuide IVR service you will need to go to Control Panel -> System and Security -> Administrative tools -> Services


Wav file format

When using VoiceGuide v7.x all sound files should be in format: uLaw or ALaw, 8kHz, 8 bit, Mono.

uLaw or ALaw format is selected at install time.

Systems located in North America and Japan should use the uLaw format.

Systems located in the rest of the world use ALaw format.

These are the two formats used by telephone companies to transmit voice over the traditional analog and digital connections, and using this sound format will result in little or no distortion of the sound file when it is transmitted over the phone line.