PDF

Voice Web Application Platform 6.
Deployment Guide
Genesys Telecommunications Laboratories, Inc.
The information contained herein is proprietary and confidential and cannot be disclosed or duplicated
without the prior written consent of Genesys Telecommunications Laboratories, Inc.
Copyright 20032004 Genesys Telecommunications Laboratories, Inc. All rights reserved.
65vw_dep_08-2004_v3.00
About Genesys
Genesys Telecommunications Laboratories, Inc., a subsidiary of Alcatel, is 100% focused on software for call centers.
Genesys recognizes that better interactions drive better business and build company reputations. Customer service
solutions from Genesys deliver on this promise for Global 2000 enterprises, government organizations, and
telecommunications service providers across 80 countries, directing more than 100 million customer interactions every
day. Sophisticated routing and reporting across voice, e-mail, and Web channels ensure that customers are quickly
connected to the best available resourcethe first time. Genesys offers solutions for customer service, help desks,
order desks, collections, outbound telesales and service, and workforce management. Visit www.genesyslab.com for
more information.
Notice
Although reasonable effort is made to ensure that the information in this document is complete and accurate at the
time of release, Genesys Telecommunications Laboratories, Inc., cannot assume responsibility for any existing errors.
Changes and/or corrections to the information contained in this document may be incorporated in future versions.
Your Responsibility for Your Systems Security

You are responsible for the security of your system. Product administration to prevent unauthorized use is your
responsibility. Your system administrator should read all documents provided with this product to fully understand the
features available that reduce your risk of incurring charges for unlicensed use of Genesys products.
Trademarks
Genesys, the Genesys logo, and Voice Web Application Platform are registered trademarks of Genesys
Telecommunications Laboratories, Inc. All other trademarks and trade names referred to in this document are the
property of other companies.
Technical Support from VARs

If you have purchased support from a value-added reseller (VAR), please contact the VAR for technical support.
Technical Support from Genesys

If you have purchased support directly from Genesys, please contact Genesys Technical Support at the following
regional numbers:
Region
Telephone
E-mail
North and Latin America
+888-369-5555 or +506-674-6767
support@genesyslab.com
Europe, Middle East, and Africa
+44 (0) 118 974 7002
support@genesyslab.co.uk
Asia Pacific
+61 7 3368 6868
support@genesyslab.com.au
Japan
+81-3-5649-6821
support@genesyslab.co.jp
Prior to contacting technical support, please refer to the Genesys Technical Support Guide for complete
contact information and procedures.
Ordering Information
For complete information on ordering Genesys products, please see Licensing Genesys Products.
Released by
Genesys Telecommunications Laboratories, Inc.
http://www.genesyslab.com
Contents
Chapter 1
About This Document ............................................................................ 9

Intended Audience..................................................................................... 9
Part Summaries......................................................................................... 9
Conventions............................................................................................. 10
Related Resources .................................................................................. 10
Chapter 2
Prerequisites ......................................................................................... 13
Hardware ................................................................................................. 13
Dialogic Boards................................................................................... 14
Software .................................................................................................. 14
VWAP 6.5 Software ............................................................................ 14
Windows ............................................................................................. 14
Directory Server.................................................................................. 15
Telephony ........................................................................................... 15
Speech Recognition............................................................................ 15
Text-to-Speech.................................................................................... 16
URLScan Filter ................................................................................... 16
EventC/Reporter ................................................................................. 17
Setting Up SQL Server and Clients ......................................................... 17
SQL Server ......................................................................................... 17
Installing SQL Server Client Network Libraries................................... 18
Setting Up Client Connections............................................................ 19
Windows 2000 Server Additional Configuration ...................................... 20
Windows Services .............................................................................. 21
System Settings.................................................................................. 22
Network Interface Card Settings......................................................... 23
Internet Explorer Settings ................................................................... 23
IIS Settings ......................................................................................... 23
System Performance Settings ............................................................ 24
Recommended Third-Party Software ...................................................... 25
Aborted Installations ................................................................................ 25
Deployment Guide
Contents
Part 1
Voice Web Manager and Voice Web Provisioning System .............. 27
Chapter 3
Voice Web Provisioning System Installation and Configuration ..... 29

Installing and Configuring Sun ONE Directory Server ............................. 29
Installing Sun ONE Directory Server................................................... 30
Creating the Root Suffix Using Sun ONE Console ............................. 30
Setting Up Dispenser............................................................................... 31
Installing and Configuring VWPS ............................................................ 35
Installing New VWPS .......................................................................... 35
Setting up VWPS Database................................................................ 36
Configuring VWPS .............................................................................. 36
Chapter 4
Voice Web Manager Installation .......................................................... 41

Introduction.............................................................................................. 41
Installing VWM......................................................................................... 41
Part 2
TDM Set Up ........................................................................................... 43
Chapter 5
VCS Installation and Configuration .................................................... 45

Installing the Dialogic Board .................................................................... 46
Installing Dialogic Software ..................................................................... 46
Installing Intel/Dialogic SR5.1.1 .......................................................... 46
Installing SR 5.1.1 SP1 for Dialogic Software..................................... 47
Installing PTR28779 for Dialogic Software ......................................... 48
Installing PTR31128 for Dialogic Software.......................................... 48
Installing Global Call Protocol Package .............................................. 49
Configuring Dialogic Software ................................................................. 49
Configuring DM/V-A Boards................................................................ 49
Installing VCS .......................................................................................... 56
Configuring VCS...................................................................................... 57
Chapter 6
Nuance 8.0.0 Installation and Configuration for VCS ....................... 61

Required Software................................................................................... 61
Installing and Configuring Nuance 8.0.0 Software .................................. 62
Installing Nuance 8.0.0 Software ........................................................ 62
Installing Nuance Service Pack SP030124......................................... 62
Installing Nuance Audio Provider........................................................ 62
Installing US English Language Pack ................................................. 63
Loading the Default Package on Resource Servers .......................... 63
Installing and Configuring Nuance Watcher........................................ 63
Voice Web Application Platform 6.5
Contents
Configuring VCS to Support ASR Features ........................................ 67

Configuring Nuance................................................................................. 68
Creating ASR Groups ......................................................................... 69
Chapter 7
SpeechWorks OSR Client-Server Installation and Configuration for

VCS .................................................................................................. 71
Installing SpeechWorks OSR .................................................................. 72
Installing OSR Server ......................................................................... 72
Installing OSR Client........................................................................... 72
Configuring OSR Client ...................................................................... 72
Configuring License ............................................................................ 73
Adding a Registry Entry for OSR Server ............................................ 73
Configuring Services on OSR Server ................................................. 74
Configuring Services on VCS ............................................................. 74
Installing ASR Log Manager Agent ......................................................... 75
Configuring SpeechWorks OSR .............................................................. 76
Configuring OSR Server to
ASR Log Manager .............................................................................. 77
Configuring OSR Servers to ASRTeleServers Group ......................... 77
Chapter 8
MRCP Server Configuration for VCS .................................................. 79

Installing the MRCP Server ..................................................................... 79
Configuring MRCP Server ....................................................................... 79
Chapter 9
Text-To-Speech Installation and Configuration for VCS .................. 83

Installing MySQL Components ................................................................ 84
Installing MySQL 3.51.06 or Later Database Software....................... 84
Installing MySQL ODBC Driver........................................................... 84
Installing MDAC 2.7 or Later............................................................... 84
Installing Speechify 2.1.6......................................................................... 84
Setting Maximum Number Of Client Connections .............................. 85
Installing RealSpeak 3.51 SP2 ................................................................ 85
Installing Genesys Text-to-Speech Software ........................................... 85
Configuring Text-to-Speech ..................................................................... 86
Making Test Calls................................................................................ 87
Deployment Guide
Contents
Part 3
IP Communications Server .................................................................. 89
Chapter 10
IPCS Installation and Configuration ................................................... 91

Installing IPCS ......................................................................................... 91
Configuring IPCS..................................................................................... 93
Chapter 11
SpeechWorks OSR Client-Server Installation and Configuration for

IPCS ................................................................................................. 97
Installing SpeechWorks OSR .................................................................. 97
Installing OSR Server ......................................................................... 97
Installing OSR Client........................................................................... 98
Configuring OSR Client ...................................................................... 98
Configuring License ............................................................................ 99
Adding a Registry Entry for OSR Server ............................................ 99
Configuring Services on OSR Server ............................................... 100
Configuring Services on IPCS .......................................................... 100
Installing ASR Log Manager Agent ....................................................... 100
Configuring SpeechWorks OSR ............................................................ 101
Creating ASR Groups ....................................................................... 102
ASR Log Manager ............................................................................ 102
Configuring OSR Servers to ASRTeleServers Group ....................... 102
Chapter 12
Text-to-Speech Installation and Configuration for IPCS ................ 105

Installing MySQL Components .............................................................. 106
Installing MySQL 3.51.06 or Later Database Software..................... 106
Installing MySQL ODBC Driver......................................................... 106
Installing MDAC 2.7 or Later............................................................. 106
Installing Speechify 2.1.6....................................................................... 106
Setting Maximum Number Of Client Connections ............................ 107
Installing RealSpeak 3.51 SP2 .............................................................. 107
Installing Genesys Text-to-Speech Software ......................................... 107
Configuring Text-to-Speech ................................................................... 108
Making Test Calls.............................................................................. 109
Part 4
Voice Web Manager Configuration ................................................... 111
Chapter 13
Voice Web Manager Configuration ................................................... 113

Setting Up VWM Databases.................................................................. 113
Setting Up VWM DatabaseSingle SQL Server.............................. 114
Setting Up VWM DatabaseMultiple SQL Servers ......................... 115
Contents
Setting Up Billing Port ....................................................................... 119

Configuring EventC ............................................................................... 119
Configuring Unified Login Server........................................................... 123
Enabling Cookies .............................................................................. 123
Setting Up Unified Login Admin User ............................................... 124
Configuring Unified Login Server Settings ........................................ 124
Configuring Reporter ............................................................................. 125
Configuring Call Status Monitor ............................................................. 127
Prerequisites ..................................................................................... 127
Configuring CSM Settings ................................................................ 127
Configuring ASR Log Manager.............................................................. 128
Creating DSN for ASR Log Manager ................................................ 129
Configuring ASR Log Server ................................................................. 129
Configuring Outbound Notification......................................................... 131
Creating DSN for Service Access Point............................................ 131
Creating ORL Groups ....................................................................... 132
Configuring Groups on ORL Server.................................................. 132
Configuring PopGateway1 Process on SAP Server ......................... 133
Configuring Genesys Queue Adapter.................................................... 133
Creating the IVR Server.................................................................... 133
Configuring VWCM................................................................................ 134
Setting Up the Database................................................................... 134
Provisioning Media Gateway ............................................................ 135
Configuring Resource Manager ........................................................ 137
Configuring SSM............................................................................... 138
Configuring H.323 Session Manager ................................................ 140
Testing the Installation ........................................................................... 141
Appendix
Miscellaneous Configurations and Troubleshooting ...................... 143

Disabling the F1 Boot ............................................................................ 143
Groundstart Configurations
with Dialogic on VCS ........................................................................ 144
Open Speech Dialog Modules ............................................................... 152
Sun ONE Software ................................................................................ 152
Reinstalling/Repairing an Existing Installation .................................. 152
Upgrading to a New Version ............................................................. 153
Common Tasks ................................................................................. 154
Setting Up Replication ...................................................................... 158
Troubleshooting VWPS Installation ....................................................... 162
Upgrading/Repairing Existing VWPS Installation.............................. 163
Troubleshooting the Dialogic Driver....................................................... 164
Troubleshooting the SQL Server ........................................................... 165
Deployment Guide
Contents
Recommended Solution ................................................................... 165

Troubleshooting VCS............................................................................. 167
Uninstalling Dialogic Software ............................................................... 167
Index .................................................................................................... 169
Chapter
About This Document

Welcome to the Voice Web Application Platform 6.5 Deployment Guide,
which provides detailed installation and configuration instructions for
VWAP 6.5 and associated third-party software. Additional information
about Windows set up and supporting third-party software is also
provided.
This chapter has these sections:
Intended Audience, page 9

Part Summaries, page 9
Conventions, page 10
Related Resources, page 10
Intended Audience
This guide is primarily intended for the system integrators and
administrators who are responsible for the installation and configuration of
the Voice Web Application Platform (VWAP).
Part Summaries
To help you locate information, this Deployment Guide begins with a table
of contents and ends with appendixes and an index. The guide contains the
following Parts, under which are related chapters:
Part 1 Voice Web Manager and Voice Web Provisioning System on

page 27, provides the installation procedure for the Voice Web
Manager.
Deployment Guide
Chapter 1: About This Document
Conventions
Part 2 TDM Set Up on page 43, provides the installation and

configuration procedures for the Voice Communications Server.
Part 3 IP Communications Server on page 89, provides the

installation and configuration procedures for the IP Communications
Server.
Part 4 Voice Web Manager Configuration on page 111, provides

instructions for configuring the Voice Web Manager. These procedures
apply for either a TDM (Voice Communications Server) or VoIP (IP
Communications Serverbased) platform.
Conventions
This guide uses the following document conventions:
A part number appears on the inside cover of the guide. Among other
things, this number identifies the month, year, and version of the guide
you are reading. The part number looks like this:
65vw_dep_08-2004_v2.05
Bold type is generally used for emphasis, values of options, variables,

the names of command objects and fields, and for the first use of a term
being defined in a document.
Italic type is used for document titles and for words, letters, and terms
used as words, letters, and terms.
Related Resources
Consult these additional resources as necessary:
Voice Web Application Platform 6.5 Getting Started Guide, which

provides an overview of the VWAP and introduces the components of
the VWAP product suite.
Voice Web Application Platform 6.5 Network Planning Guide, which

presents recommendations for implementing the VWAP for Network
Service Providers (NSP). It is written for NSP network engineers and
planners who design and plan the architecture of the VWAP structure.
Voice Web Application Platform 6.5 Operations and Provisioning

Guide, which provides instructions for the administration and
provisioning of the VWAP and its components.
10
Related Resources
Voice Web Application Platform 6.5 Genesys Studio Developers

Guide, which provides information on Genesys Studio, a GUI for the
development of applications based on the Voice Extensible Markup
Language (VoiceXML).
Voice Web Application Platform 6.5 VoiceXML 2.0 Reference Manual,

which provides information on developing VoiceXML 2.0 applications
on the VWAP. It presents VoiceXML 2.0 concepts and provides
examples that focus on the VWAP implementation of VoiceXML
(Voice Extensible Markup Language).
Voice Web Application Platform 6.5 Diagnostic and Troubleshooting

Guide, which provides troubleshooting information for the VWAP.
Voice Extensible Markup Language (VoiceXML) Version 2.0 W3C

Candidate Recommendation 20 February 2003, which is a W3C final
release candidate for review by W3C members and other interested
parties for VoiceXML 2.0 The term candidate recommendation means
that this work has received signification review from its immediate
technical community. It is an explicit call to those outside of the related
working groups or the W3C itself for implementation and technical
feedback.
The Genesys Migration Guide, also on the Genesys Documentation

Library CD, which contains a documented migration strategy for each
software release. Please refer to the applicable portion or contact
Genesys Technical Support for additional information.
The Genesys Technical Publications Glossary, which ships on the

Genesys Documentation Library CD and which provides a
comprehensive list of the Genesys and CTI terminology and acronyms
used in this document.
The Release Notes and Release Advisory for this product, which are
available on the Genesys Technical Support website at http://
genesyslab.com/support.
Genesys product documentation is available on the:
Genesys Technical Support website at http://genesyslab.com/support.

Genesys Documentation Library CD, which you can order by e-mail
from Genesys Order Management at orderman@genesyslab.com.
Deployment Guide
11
12
Related Resources
Chapter
Prerequisites
This chapter provides information about the installation prerequisites for
the Voice Web Application Platform (VWAP) when installed with
Windows 2000. It includes information about required software and
recommended hardware and software.
This chapter covers the following topics:
Hardware, page 13
Software, page 14
Setting Up SQL Server and Clients, page 17
Windows 2000 Server Additional Configuration, page 20
Recommended Third-Party Software, page 25
Aborted Installations, page 25
Hardware
Table 1 lists the recommended hardware for a VWAP installation.
Table 1: VWAP Recommended Installation Hardware
Component
Deployment Guide
Value
Model
Dell PowerEdge 2650 2U
ROM (Firmware)
12/26/1999 or later
CPU
Dual Xeon, 2.4 GHz, minimum
Hard Drive
Two 10K RPM 18 GB with RAID 1
Memory
2 GB RAM, minimum
13
Chapter 2: Prerequisites
Software
Dialogic Boards
The VWAP VCS supports the following Dialogic boards:
DM/V480A-2T1
DM/V960A-4T1
DM/V600A-2E1
DM/V1200A-4E1
Software
The following software is required for a VWAP 6.5 installation.
VWAP 6.5 Software

The VWAP 6.5 software is available on CD and includes the following
main components:
Voice Communications Server (VCS)

IP Communications Server (IPCS)
Voice Web Manager (VWM)
Voice Web Provisioning System (VWPS)
Windows
The following Windows components must be on every VWAP server:
Windows 2000 Server with Service Pack 4. You may install critical
updates released after Windows 2000 SP4.
Note: When installing Windows 2000 SP4, you must select USEnglish as the language.
14
Microsoft Data Access Component 2.7

Microsoft Internet Explorer 6.0+
MSXML 4.0 SP2 or later
URLScan Filter for IIS Setup
Windows 2000 Components:
Internet Information Server (IIS) > Common Files
Internet Information Server (IIS) > File Transfer Protocol (FTP)

Server
Software
Internet Information Server (IIS) > Internet Information Server

Snap-In
Internet Information Server (IIS) > World Wide Web Server
Management and Monitoring Tools > Simple Network Management
Protocol
Note: If you change a machine name after registering it with VWPS,

LDAP (Lightweight Directory Access Protocol) can read the configuration
and will operate in Local mode.
Directory Server
RecommendedSun ONE Directory Server version 5.1 SP2
Also SupportedSun ONE Directory Server version 5.1 SP1, 5.1 or
5.0
Note: Sun ONE software is available from the vendor.
Telephony
The following Dialogic telephony software is required:
Dialogic SR 5.1.1 SP1 with PTR28779 and PTR31128

GlobalCall Protocols Package version 4.0
Note: The telephony software is distributed with VWAP, on the VWAP
Third-Party Dialogic CD.
Speech Recognition
The following ASR (Automatic Speech Recognition) software is required if
speech recognition is used:
Nuance 8.0.0 with SP030124, Nuance Dialogic CSP Audio Provider

version 2.0.3, and LanguageModule-EnglishAmerica-v8-0-r2.zip
Note: Nuance is supported on the VCS only. It is not supported on the
IPCS. Nuance software is available from the vendor.
OR
Deployment Guide
15
Software
SpeechWorks Open Speech Recognizer (OSR) Client-Server 1.1.4 with

hot fix HF1-1-4-01 and HF1-1-4-02.
Note: SpeechWorks software is distributed with VWAP, on the ThirdParty SpeechWorks OSR Client-Server 1.1.4 CD.
OR
ASR MRCP vendor software that is certified with VWAP.

Note: MRCP is supported on the VCS only.
Text-to-Speech
VWAP 6.5 supports the following text-to-speech (TTS) software:
ScanSoft RealSpeak Telephony 3.51 SP2

SpeechWorks Speechify 2.1.6
The Speechify or RealSpeak database requires that you establish
connectivity using the following MySQL software, which is available from
http://www.mysql.com:
MySQL 3.51.06 or later

MyODBC 2.50
For database access across a network, the following software is required
and is available from Microsoft.
MDAC 2.7 or later

Note: ScanSoft RealSpeak software is available from the vendor.
SpeechWorks Speechify software is available from the vendor or from
Genesys.
URLScan Filter
To Set Up URLScan Filter for IIS
16
Run the urlscan.exe setup file.
Verify that the installation completed.
Open IIS configuration and right-click on Properties. For example, go

to MyComputer > Manage > Services and Applications > IIS
Configuration, then right click on Properties.
Setting Up SQL Server and Clients
Check the UrlScan entry in IIS > <computer_name> Master

Properties > WWW Service > Edit > ISAPI Filters.
Open the urlscan.ini from C:\WINNT\system32\inetsrv\urlscan.
Change the AllowDotInPath option from 0 (zero) to 1 (one).
Comment out the .asp line from the Deny asp requests section.
EventC/Reporter
EventC/Reporter machines require MDAC 2.7. If the EventC machine has a
higher version of MDAC, the EventC log files or Network Management
GUI might state that a version is not found. If this occurs, then downgrade
MDAC to version 2.7. Refer to Microsoft documentation for instructions
on downgrading MDAC.

SQL Server
An SQL Server 2000 Enterprise Edition SP3 is required and more than one
may be used based upon anticipated network activity and redundancy. The
SQL Server hosts tables for the Voice Web Provisioning System (VWPS),
Voice Web Manager (VWM), Reporter, and the VWM Event Collector and
Processing components.
Install the SQL Server on a computer that meets the hardware and software
requirements outlined in the sections Hardware on page 13 and
Software on page 14. If you are setting up a lab configuration, where the
VWM components are installed on two computers, the SQL Server may
reside on VWM1. Make note of the name and location of the computer for
future use.
Note: When installing the SQL server, you must select US-English as the
language.
Deployment Guide
17
To install the SQL Server:

1
Run the SQL Server installation program.
When prompted for authentication, select Mixed Authentication.
Note the Login Name and password. For example, the Login Name
might be sa with no password.
This completes the SQL Server installation and configuration.
Installing SQL Server Client Network Libraries

You must perform this procedure once for every box that will access the
SQL Server Databases, but that does not have SQL Server installed. This is
required for software such as VWPS, EventC, UnifiedLogin, Call Status
Monitor, and Reporter. For example, if SQL Server is installed on VWM1
box, and VWM components on VWM2 and VWM3 boxes access the
database, perform this procedure on VWM2 and VWM3.
To install connectivity only for SQL Server 2000
18
Insert the Microsoft SQL Server 2000 CD in your CD-ROM drive. If

the CD does not autorun, double-click Autorun.exe in the root directory
of the compact disc.
Select SQL Server 2000 Components.
Select Install Database Server. Setup prepares the SQL Server

Installation Wizard.
At the Welcome screen, click Next.
At the Computer Name screen, note that Local Computer is the default
option, and the local computer name appears in the edit box. Click
Next.
At the Installation Selection screen, click Create a new instance of

SQL Server, or install Client Tools, and then click Next.
Follow the directions on the User Information, Software License

Agreement and related screens.
At the Installation Definition screen, click Connectivity Only, and then

click Next.
At the Start Copying Files screen, click Next to complete the

installation.
Setting Up Client Connections

You must perform this procedure once for every SQL Server box that is
accessed from the Client box. For example, if SQL Server is installed on
VWM1 box, and VWM components on VWM2 and VWM3 boxes access
the database, you must set up client connections to VWM1 box on the
VWM2 and VWM3 (client) boxes.
On the Client box, do the following:
1
In Windows 2000, select Start > Settings > Control Panel >
Administrative Tools > Data Sources.
On the System DSN tab, click Add.
Select SQL Server Driver from the list of drivers and click Finish.
In the Create New Data Source for SQL Server dialog box, enter the
following and click Next when you are through:
Name: a logical name for the Connection, for example, vwm1
Description: a text description, for example, Connection to vwm1

SQL Server
Server: name of the SQL Server, for example, vwm1
In the next dialog box, enter the following:

a
In the first radio button, select Use SQL Server authentication using
a login ID and password entered by the user.
b In the LoginID field, enter a Login in the SQL Server, for example,
sa. The login ID should have been previously created in SQL Server
and have access privileges to the various databases.
c In the Password field, enter the password for the login.
6
Click Client Configuration in the same dialog box.
Select TCP/IP for Network Libraries.
The Server Alias field represents the alias for the SQL Server. This
can be any name and can be different from the actual machine
name.
Note: The Server Alias is the name used during VWPS configuration.
Deployment Guide
Server Name: enter the name/fully qualified domain name/IP

address of the SQL Server box. If this name is pinged from the
client (current box), it should resolve and communicate
successfully. Genesys recommends using the IP address.
Click OK.
19
Windows 2000 Server Additional Configuration
At the parent window, click Next.
If the parameters are correct, then the next dialog box appears. If the
parameters are incorrect, an error message displays.
10
Click Next > Next.
11
Click Test Data Source. The test should complete with a success
message.
12
Click OK to save the DSN.
Note: If remote clients are unable to connect to the SQL Server, the
default network library for the SQL Server on the client might be set to
Named Pipes instead of TCP/IP. See Appendix, Miscellaneous
Configurations and Troubleshooting on page 143 for more information.
Windows 2000 Server Additional

Configuration
Warning! Do not use the underscore ( _ ) character when naming a
computer even though Windows Setup permits this. Using the underscore
character causes serious problems with several web services that the VWAP
6.5 software uses.
After installing Windows 2000
20
Double-click on the Time icon in the task bar.
Select GMT for the Time Zone, and adjust the date and time
accordingly.
Clear the check box labeled Automatically adjust clock for daylight
saving changes.
Windows Services
Select Start > Programs > Administrative Tools > Services, and set the
Services as shown in Table 2.
Table 2: Windows Services Setup
Deployment Guide
Name
Startup Type
Alerter
Disabled
Application Management
Manual
Clipbook
Manual
Com + Event System
Manual
Computer Browser
Disabled
DHCP Client
Automatic
Directory Replicator
Manual
Event Log
Automatic
FTP Publishing Services
Automatic
IIS Admin Service
Automatic
License Logging
Disabled
Messenger
Disabled
Net Logon
Manual
Network DDE
Manual
NT LM Security Support Provider
Manual
Plug and Play
Automatic
Protect Storage
Automatic
Remote Procedure Call (RPC) Locator
Manual
Remote Procedure Call (RPC) Service
Automatic
Server
Automatic
SNMP
Automatic
SNMP Trap Service
Manual
System Event Notification
Automatic
21
Table 2: Windows Services Setup (Continued)
Name
Startup Type
Task Scheduler
Automatic
TCP/IP NetBIOS Helper
Automatic
Telephony Service
Manual
UPS
Manual
Workstation
Automatic
World Wide Web Publishing Service
Automatic
System Settings
The system settings listed in Table 3 are required on each computer.
Table 3: System Settings
Name
Status
EventLog Viewer maximum log size System Log 1024 Kb
22
EventLog Viewer maximum log size Application

Log
1024 Kb
EventLog Viewer maximum log size exceed

action
Overwrite events as needed
DNS
Appropriate IP addresses
SNMP Trap
As appropriate
Time zone
GMT with Automatic

daylight saving adjustment
OFF
Network Interface Card Settings

The Network Interface Card settings listed in Table 4 are required on each
computer.
Table 4: Network Interface Card Settings
Parameter
Value
NIC1 (Primary)
Appropriate VPN IP address (if used)
NIC2 (Public)
Disabled (by Control Panel) or public IP address (for

computers that need to be dual-homed)
Internet Explorer Settings

The Internet Explorer settings listed in Table 5 are required on each
computer:
Table 5: Internet Explorer Settings
Parameter
Value
IE default document
http://localhost:9810
IIS Settings
This section describes how to configure the IIS settings, which must be
done on each VWM computer.
1
In Windows 2000, select Start > Programs > Administrative Tools >
Internet Services Manager.
Right-click and select Default FTP Site > Properties > Home
Directory tab. Select Read permissions.
Right-click and select Default FTP Site > Properties > Directory
Security tab. Set the default access for all computers to Denied Access.
Right-click and select Default FTP Site > Properties > Security
Accounts tab. Clear the Allow Anonymous connections check box.
Right-click and select Default Web Site > Properties > Home
Directory tab.
a
Click Configuration in the Application Settings section.

b On the App Mappings tab, select and remove all mappings except
.asp and .asa.
Deployment Guide
23
Directory tab.
a
Click Configuration in the Application Settings section.

b On the App Options tab, select Enable session state and set the
session timeout to 30 minutes.
c Select the Enable buffering check box.
7
Directory tab. Set the HTTP security access settings based on
individual requirements.
Right-click and select the Server > Properties > Internet Information
Services tab.
a
b
c
d
e
Click Edit, and select Web Site tab.

Select Enable logging check box.
Click Properties > General properties tab.
Select When file size reaches check box and enter 1 MB in the text
field.
Click Extended properties tab, and select the following options:
Date
Time
Client IP Address
Method
URI Stem
Protocol Status
Right-click and select the Server > Properties > Internet Information
Services tab >Home directory tab > Application Settings section >
Execute Permissions.
10
Select Scripts and Executables.
System Performance Settings

You must configure the following system performance settings on each
VWM computer.
24
In Windows 2000, select Start > Settings > Control Panel > System >
Advanced, click Performance Options.
In the Application Response section, select Optimize performance for

Background services.
Recommended Third-Party Software
Select Start > Settings > Control Panel > System > Advanced, click
Performance Options.
In the Virtual Memory section, click Change, and set Initial size to
640 MB and the Maximum size to 960 MB. If the RAM is 1 GB,
double these values.
Recommended Third-Party Software

Genesys recommends that the VWAP 6.5 components run with the
following third-party network-management software:
PCAnyWhere 10.0
Aborted Installations
Reboot the server after any aborted installation.
Deployment Guide
25
26
Aborted Installations
Part
Voice Web Manager and

Voice Web Provisioning
System
The chapters in Part 1 provide instructions for installing the Voice Web
Manager and Voice Web Provisioning System. These procedures are the
same whether the VWAP 6.5 is installed as a Time Division Multiplex
(TDM) (Voice Communications Serverbased) platform or as a Voice over
Internet Protocol (VoIP) (IP Communications Serverbased) platform.
You can find instructions for configuring VWM in Part 4, and you should
perform them after installing VCS or IPCS.
Part 1 contains the following chapters:
Chapter 3, Voice Web Provisioning System Installation and

Configuration on page 29
Chapter 4, Voice Web Manager Installation on page 41
Deployment Guide
27
Part 1: Voice Web Manager and Voice Web Provisioning System
28
Chapter
Voice Web Provisioning

System Installation and
Configuration
This chapter describes how to install and configure the Sun ONE Directory
Server, the Dispenser, and the Voice Web Provisioning System (VWPS)
software.
Note: Anti-virus software may interfere with the installation process.
Make sure there is no anti-virus software running during installation.
Installing and Configuring Sun ONE Directory Server, page 29

Setting Up Dispenser, page 31
Installing and Configuring VWPS, page 35
Installing and Configuring Sun ONE

Directory Server
Before installing the VWPS, you must first install and configure the Sun
ONE Directory Server. Genesys recommends that you install Sun ONE
Directory Server version 5.1 SP2, however, versions 5.1 SP1, 5.1 and 5.0
are also supported.
Note: Direct access to the local machine is required for installing Sun
ONE. Do not use Microsoft Terminal Services.
Deployment Guide
29
Chapter 3: Voice Web Provisioning System Installation and Configuration
Installing and Configuring Sun ONE
Installing Sun ONE Directory Server

1
From the Sun ONE installation software, double-click setup.exe.
Follow the onscreen instructions and select the default settings

throughout the installation.
When prompted, enter an Administrator ID and password, and enter a

Directory Manager DN and password. Make note of your IDs and
password for future use.
When prompted, reboot the computer.
Creating the Root Suffix Using Sun ONE Console

1
In Windows, select Start > Programs > Sun ONE Server Products >
Sun ONE Console.
Log in with your Directory Manager DN and password.
Expand the Server icon.
Expand the Server Group folder and select Directory Server.
Right-click and select Open. The Directory Server appears.
Click the Configuration tab.
Select the Data icon.
From the Object menu, select New Root Suffix.
In the New Suffix field, enter the name of the suffix, for example,
o=genesys.net.
Note: The suffix name must start with o=. Use the lower case letter o,
not the zero.
30
10
Select the Create associated database automatically check box.
11
Enter the name of the database (for example, genesys), and click OK.
12
Click the Directory tab, and ensure that the Server is selected.
13
From the Object menu, select New Root Object > o=genesys.net.
14
From the Choose New Object list, scroll down and select
Organization and then click OK. The Property Editor dialog box
appears.
15
In this Property Editor dialog box, click OK.
Setting Up Dispenser
Adding a Password to the Root Suffix

Note: This password is also used by VWPS for scheduled tasks.
1
Select the Root Suffix node.
From the Object menu, select Properties.
Click Add Attribute. The Add Attribute dialog box appears.
From the Attribute list, select userpassword and click OK. The
password attribute is added to the list on the left side of the window.
Scroll down to the password field and enter a password (for example,
genesys2003) and make note of it for future reference.
Click OK.
Close all windows.
Note: When installing any Genesys component, the DN (Distinguished

Name) for the root suffix (for example, o=genesys.net) and the password
(for example, genesys2003) created in the sections Creating the Root
Suffix Using Sun ONE Console on page 30 and Adding a Password to
the Root Suffix on page 31 can be used as the UserID and the password.
Installing Sun ONE is now complete.
This section provides instructions for setting up the Dispenser, which is a
web directory.
You must create an FTP site on the Dispenser so that VWPS can update
DID and Application XML files on the Dispenser. The did.xml and
appid.xml files contain configuration and connection information for all
customer applications. These files are generated into the <VWPS
Installation Drive>:\Cn\Web\did_url_mappings directory when an
application is provisioned. The VWPS then FTPs these files to the
Dispenser so that they are available for HTTP requests from the VCS.
You can set up XML Dispensers in VWPS using one of the following three
configuration options:
Deployment Guide
Primary Dispenser only on the VWPS machine (recommended).
Primary Dispenser only on a remote non-VWPS machine.
31
Primary and Backup Dispensers, one of which is on the VWPS

machine.
If high availability of the XML Dispenser is desired, use Option 3. The

three configuration options are described below. Additionally, instructions
to execute common steps are provided, which include:
1
Creating an FTP virtual directory named cnftp and pointing it to a local

folder.
Pointing the default website on port 80 to a local folder.
Primary Dispenser Only, on the VWPS Machine

(Recommended)
In this configuration, only one Dispenser is available to VWAP clients such
as VCS and IPCS. The VWPS machine is also configured to act as a
Dispenser.
1
On the VWPS machine, create a folder

C:\CNDispenser\did_url_mappings.
Set up an FTP virtual directory named cnftp on the VWPS machine.
Point cnftp to the local folder C:\CNDispenser.
Configure the default website on the VWPS machine for port 80 and
point the default website to C:\CN\Web as the home directory.
Set the Dispenser Machine Name parameter in VWPS to the fully

qualified domain name of the VWPS machine.
Restart Watchdog on the VWPS machine.
Primary Dispenser Only, on a Remote Non-VWPS

Machine
In this configuration, only one Dispenser is available to VWAP clients such
as VCS and IPCS. The VWPS machine does not act as a Dispenser.
Instead, you configure another machine to act as a Dispenser. The VWPS
deploys XML files to this Dispenser machine using FTP.
1
On the remote dispenser machine, create a folder

Note: This is not CN\Dispenser.
32
Set up an FTP virtual directory named cnftp on the remote Dispenser

machine.
Point cnftp to the remote machines folder C:\CNDispenser.
Configure the default website on the remote Dispenser machine for port
80 and point the default website to its local C:\CNDispenser\ as the
home directory.

qualified domain name of the remote dispenser machine.
Primary and Backup Dispenser, One of Which is on

the VWPS Machine
In this configuration, two Dispensers are available to VWAP clients such as
VCS and IPCS. The VWPS machine acts as the backup Dispenser. Another
machine is configured to act as the primary Dispenser. The VWPS deploys
XML files to the primary Dispenser using FTP.
To configure the primary Dispenser on a remote machine:
1
On the remote Dispenser machine, create a folder

Set up an FTP virtual directory named cnftp on the remote Dispenser

machine.
Point cnftp to the local folder C:\CNDispenser.
Configure the default website on the remote Dispenser machine for port
80 and point the default website to C:\CNDispenser as the home
directory.
To configure the backup Dispenser on the VWPS machine:
Deployment Guide
Make sure the C:\CN\web\did_url_mappings\ folder exists on the

VWPS machine.
Configure the default website on the VWPS machine for port 80 and
point the default website to the C:\CN\web\ folder on the VWPS
machine.

qualified domain name of the remote dispenser machine.
33
Notes:
The $dispenser$ set in the AppXML fetched from the backup Dispenser
will have the primary Dispenser machine name as its value. This is not an
error.
To change the default (suggested) values relating to Dispensers in VWPS:
If your paths deviate from the paths specified in this procedure, for
example, if the path of the Dispenser is
C:\CNDispenser\did_url_mappings\xmlfiles, then you must modify the
following items:
The cnftp virtual FTP directory continues to point to C:\CNDispenser.

Change the VWPS configuration parameter FTP path on Dispenser
Machine on the VWPS machine to cnftp/did_url_mappings/xmlfiles/.
Modify the VWPS configuration parameter Local DID folder on the

VWPS machine to C:\CN\web\did_url_mappings\xmlfiles\.
Modify the VWPS configuration parameter Dispenser URL on the

VWPS machine to http://$dispenser$/did_url_mappings/xmlfiles/
$appxmlversion$/$appxmlname$
On the VWPS machine, create a folder

C:\CN\web\did_url_mappings\xmlfiles\.
Commonly Used Tasks

To create an FTP virtual directory named cnftp and point it to a local folder:
34
Open Internet Services Manager from Start > Settings > Control
Panel > Administrative Tools > Internet Services Manager.
Expand the machine name node.
Expand Default FTP site.
Right-click Default FTP site and select New > Virtual Directory.
Click Next in the Wizard that appears.
Enter cnftp as the alias. Click Next.
Select the local folder as the path by clicking Browse. Click Next after
specifying the folder (for example, C:\CNDispenser).
In the Access Permissions step, select the Read and Write check boxes.
Click Next.
Click Finish.
Installing and Configuring VWPS
To point the default website on port 80 to a local folder:

1
Open Internet Services Manager from Start > Settings > Control
Panel > Administrative Tools > Internet Services Manager.
Expand the machine name node.
Expand Default Web site.
Right-click Default Web site and choose Properties.
In the TCP Port text box, make sure the value is 80.
Click the Home Directory tab.
In the Local Path text box, specify the local folder by clicking Browse.
Click OK.

This section provides the requirements and the instructions for installing
and configuring the VWPS.
Installing New VWPS

1
Insert the VWAP CD into the computer on which you are installing
VWPS.
Run the setup executable located in solution_specific\VWPS. The

VWPS Install Wizard starts.
If the Wizard prompts you to overwrite any existing files, select Yes to
all. Repeat if necessary.
When you are prompted to select a folder, select (C or D):\CN.

Note: If the LDAP and VWPS are installed on separate computers,
copy the 50Telera.ldif file from the <VWPS Installation Drive>/Cn/
Config folder on the VWPS computer and paste it into the <LDAP
Installation Drive>/Sun ONE/Servers/slapd-<Server Name>/config/
schema folder on the LADP computer.
Restart the LDAP service through the Services Panel, by restarting the
Sun ONE Directory Server.
Deployment Guide
When prompted Is Directory Services Enabled? click Yes.
35
The setup prompts you for the following directory information required
to connect to the directory server:
Directory Server Fully Qualified Domain Name or IP Addressthe

fully qualified name or IP address of the computer on which Sun
directory server is installed.
Directory Services User Namethe username needed to login to

the directory server, for example, cn=Directory Manager.
Passwordpassword for the user account.
Root Domain Namethe root node where all information is

maintained, for example, o=genesys.net.
Note: Use the lowercase letter o, not the number zero.
Click Next.
If the registration is successful, setup displays a success message and
proceeds to the last step.
If there is a problem with registration, setup indicates this and provides
you with another opportunity to register with the directory server.
After the setup finishes, reboot the system.
Setting up VWPS Database

1
On the SQL Server, create a database named VWPS.
Select the VWPS database.
Select the Tools drop-down menu and select SQL Query Analyzer.
Open the VWPS DB NEW 6.5.4SQL file from the <VWPS

Installation Drive>:\CN\Config\DBScripts\ folder located on the
VWPS machine.
Click Run (the green triangle) or press F5. Ignore any

PRIMARY_KEY_CONSTRAINT violations error messages.
Configuring VWPS
36
Open Internet Explorer and enter http://<vwps machine name>:9810/

vwps in the Address bar. The VWPS Login page opens.
Log in with the Directory Manager DN and password.
Click Servers. A tree in the left frame displays.
Click on the + sign next to VWPS to see a list of VWPS servers in the
network.
Expand the server that is being installed. This should have a VWPS
node under it.
Click on VWPS node and select Edit Node from the menu that appears
in the main frame. The Server Configuration page for that node opens.
Ensure that the Show Advanced Fields check box is selected. Supply
values for the parameters listed in Table 6.
Note: Database names are case sensitive.
Table 6: VWPS Parameters
KeyName
KeyValue
Description
Example
Log Levels
Level of detail on how much debugging

information is written to VWPS log files.
SQL DB Machine Name
(Mandatory) Fully qualified name of the SQL

Server machine that hosts the VWPS database
sql.company.com
SQL DB Username
(Mandatory) An existing username for the SQL

Server.
sa
SQL DB Password
Password for the user.
SQL DB Initial Catalog

(Database)
(Mandatory) The database where DID information

is stored. By default, it should be VWPS.
VWPS
Local DID Folder
(Mandatory) Local folder on the VWPS machine

where all the generated XML files are to be kept.
D:\cn\web\did_url_
mappings\
Dispenser Machine Name
(Mandatory) Fully qualified name of the machine

that will act as the XML files Dispenser. Do not
specify localhost.
dispenser.company.c
om
FTP Path on Dispenser

Machine
(Mandatory) Relative FTP path to the folder where

all the XML files are to be deployed using FTP.
This folder will also be available under the
machines web site and server XML pages to
POPServers.
cnftp\did_url_mappi
ngs\
Deployment Guide
37
Table 6: VWPS Parameters (Continued)
KeyName
HTTP Port to use
KeyValue
Description
Example
(Optional) The default is 9810. Change this to a

valid port only if VWPS should use the new port to
notify other servers of their configuration change
and use as a default port for configuration
information.
9810
If you wish to configure VWPS server and UI to

work on a different port, then edit the file
d:\cn\web\vwps\common\server.inc. Open this file
in Notepad and edit the value of the parameter
HTTP_PORT. After changing this value, clear the
Internet Explorer cache and restart IIS admin
service on the VWPS machine.
Populate Adjunct Database
(Mandatory) Select this check box to enable VWPS

to start populating adjunct database with
information from LDAP directory. This is used by
Reporter, EventC.
Selected
Update Frequency in
seconds
(Mandatory) How frequently the data should be

updated. Unless needed do not change the default.
180
Purge Interval (days)
(Mandatory) Number of days after which VWPS

should delete entries from adjunct database that
have been deleted in the directory. When entries
are deleted from the directory, they are kept in the
Adjunct DB for reporting and billing purposes. If
0, entries are deleted immediately. Default is 45.
45
Servers IP Lookup
(Mandatory) Select this check box if VWPS should

lookup IP addresses of servers for report database.
Enable Scheduled Tasks
(Mandatory) Select this check box to enable

scheduled tasks.
Selected
Scheduled Tasks Interval
Value in seconds that specifies how frequently

VWPS looks for pending scheduled tasks and
executes them.
180
VWPS System Account

Password
This is the password for the VWPS system

account. This account is used for scheduled tasks
only.
38
Table 6: VWPS Parameters (Continued)
KeyValue
Description
KeyName
Example
VWPS Operating Mode
Operating mode of VWPS. Options are Standard or

Advanced. If Standard is selected, some advanced
operations are not available. To enable these
operations, select Advanced. In order for this to
take effect, you must log out of VWPS, then log
back in.
Standard
HTTP Safe AppXML
If this check box is selected, VWPS generates

AppXML in URLScan safe folders. For example,
VWPS generates AppXML 2.0 in a 0200 folder
(which does not contain a period in its name) in
addition to the 2.0 folder.
Selected
Click Submit.
Restart WatchDog on the VWPS machine. Once WatchDog comes up,

the VWPS configuration is finished.
10
When WatchDog starts, look for the file vwps.ini.tds under <VWPS
Installation Drive>:\CN\Config folder. This file should not be present.
If it is present, then there is a problem with the new information. Use
watchdog.log to start debugging.
11
Log in to VWPS and click Diagnostics. Make sure that all the
diagnostic tests return success. If not, refer to Troubleshooting VWPS
Installation on page 162.
You are done configuring VWPS.
Deployment Guide
39
40
Chapter
Voice Web Manager

Installation
This chapter describes how to install the Voice Web Manager (VWM)
components.
Note: Antivirus software may interfere with the installation process.
Make sure antivirus software is not running during installation.
This chapter has the following sections:
Introduction, page 41
Installing VWM, page 41
Introduction
You can install the VWM components in either of two ways:
LabAll VWM components are installed on one computer.

NetworkThe VWM components are installed on various, separate
computers.
Installing VWM
Deployment Guide
Insert the VWAP CD into the CD-ROM drive.
From the solution_specific\VWM directory, run the VWM setup

executable. The Install Wizard starts.
41
Chapter 4: Voice Web Manager Installation
Installing VWM
When the Wizard prompts you to select a folder, select (C or D):\CN,

and then click Next.
At the VWM Components Selection screen, select the required VWM

components, then click Next.
A warning screen appears regarding multiple EventC services.

Acknowledge it by clicking OK.
At the second VWM Components Selection screen, select the required

VWM components, then click Next.
At the Voice Web Call Manager Components (VWCM) Selection

screen, select the required VWCM components, then click Next.
If you are prompted to overwrite any existing files, select Yes. Repeat if
necessary.
10

Directory Services User Namethe user name needed to login to


11
Click Next.
42
12
13
Repeat this procedure to install VWM/AIM/VWCM components on

other machines.
Part
TDM Set Up
The chapters in Part 2 provide instructions on installing and configuring a
Time Division Multiplex (TDM) (Voice Communications Serverbased)
platform with Dialogic boards.
Instructions for configuring and installing Voice over Internet Protocol
(VoIP) (IP Communications Serverbased) platform are provided in Part 3.
Chapter 5, VCS Installation and Configuration on page 45

Chapter 6, Nuance 8.0.0 Installation and Configuration for VCS on
page 61
Chapter 7, SpeechWorks OSR Client-Server Installation and

Configuration for VCS on page 71
Chapter 8, MRCP Server Configuration for VCS on page 79

Chapter 9, Text-To-Speech Installation and Configuration for VCS on
page 83
Deployment Guide
43
Part 2: TDM Set Up
44
Chapter
VCS Installation and

Configuration
This chapter describes how to install and configure the Voice
Communications Server (VCS), including the Dialogic software and
hardware.
If you plan on using the SpeechWorks OSR Client-Server ASR software,
you must first install SpeechWorks before installing VCS (see Chapter 7,
SpeechWorks OSR Client-Server Installation and Configuration for VCS
on page 71).
Deployment Guide
Installing the Dialogic Board, page 46

Installing Dialogic Software, page 46
Configuring Dialogic Software, page 49
Installing VCS, page 56
Configuring VCS, page 57
45
Chapter 5: VCS Installation and Configuration
Installing the Dialogic Board
Installing the Dialogic Board

1
Turn off the computer and install the Dialogic board.

For details on how to install the Dialogic board, refer to the vendor
documentation included with the board, or check the Dialogic website.
Make note of the board identification number; you might need it later.
To find the identification number, review the installation card supplied
with the board; a switch on the board usually specifies the identification
number.
If you are installing multiple boards:
Each board must have a separate device number. Note the dial
number on each board and the slot in which the board is installed.
After installing the boards in the chassis, cable the boards together.
Note: Although the cable connectors are keyed, their design still
permits improper insertion. Make sure that the connector mates well
with the board and is aligned properly.
Installing Dialogic Software

Before installing the VCS software, you must install and configure the
Intel/Dialogic System Release (SR) 5.1.1 software.
Note: Genesys recommends that you install the Dialogic software on the
local administrator account.
Installing Intel/Dialogic SR5.1.1
46
Insert the VWAP Third-Party Dialogic CD into the CD-ROM drive.
From the Intel\Dialogic\Dialogic_SR_5_1_1 directory, run the setup

executable. The Install Wizard starts, and the Setup Options screen
appears.
Click Custom, then click Next. The program prompts for the
installation of component options.
Select the following options:
Dialogic Drivers, Firmware, and Configuration files
Dialogic Development SDK
Sample programs
Online Documentation
Performance Counters for Win NT performance monitor
ISDN Package
Global Call API Package
Antares
DM3
Continuous Speech Processing (CSP)
Click Next. The ISDN Protocol Selection screen appears.
If you are using the ISDN protocol, click Select All. If you are not
using the ISDN protocol, do not make a selection.
Click Next. The DM3 Component Selection screen appears.
If you are using the DM3 components, click Select All and click Next.
The Online Documentation Access Location screen appears.
Select Install Documentation Locally and click Next. The Destination

Location screen appears.
10
Select the default installation directory and click Next. The Program
Group screen appears.
11
Select the default program group and click Next. The setup copies all of
the program files and creates program groups.
12
At the prompt to run DCM, do not select any of the options.
13
Click Next.
14
Reboot the computer.
Note: If a Found New Hardware dialog box appears upon reboot, refer to
Troubleshooting VWPS Installation on page 162 for more information.
Installing SR 5.1.1 SP1 for Dialogic Software
Deployment Guide
From the VWAP Third-Party Dialogic CD, Intel\Dialogic\

SR5_1_1_patches\Dialogic511sp1 directory, run the setup executable.
Reboot the system after the service pack installation is complete.
47
Installing PTR28779 for Dialogic Software

1
From the VWAP Third-Party Dialogic CD,

Intel\Dialogic\SR5_1_1_patches\PTR28779\ directory, run the setup
executable.
The following files will be overwritten in the data subdirectories.
03/20/2003 11:22a 4,645,111 qs_isdn_4ess.mlm
03/20/2003 11:27a 4,645,809 qs_isdn_5ess.mlm
Reboot the system after the point release installation is complete.
Installing PTR31128 for Dialogic Software

Note: Nuance 8.0 can not be deployed with Dialogic PTR31128. If you
are using Nuance for Automatic Speech Recognition, do not install
PTR31128. Install PTR27390 and PTR28779 instead.
1
From the VWAP Third-Party Dialogic CD,

Intel\Dialogic\SR5_1_1_patches\PTR31128\ directory, run the setup
executable.
The following files will be overwritten in the subdirectories:
bin:
07/22/2003 12:11 PM 53,248 cheetah_cfg.exe

inc:
05/29/2002 05:44 PM 2,851 dm3cc_parm.h
07/04/2001 05:33 PM 3,009 GcVoip.h

lib:
48
09/16/2003 12:21 PM 286,720 cheetah.dll

09/16/2003 12:26 PM 86,016 libcspdm3.dll
09/16/2003 12:31 PM 446,464 libdm3cc.dll
09/16/2003 12:33 PM 204,800 libdm3fax.dll
09/16/2003 12:27 PM 86,016 libdtidm3.dll
09/16/2003 12:25 PM 409,600 libdxxdm3.dll
09/16/2003 12:32 PM 77,824 libipm_nettsc.dll
09/16/2003 12:32 PM 7,536 libipm_nettsc.lib
Reboot the system after the point release installation is complete.
Configuring Dialogic Software
Installing Global Call Protocol Package

1
From the VWAP Third-Party Dialogic CD, Intel\Dialogic\

GlobalCallProtocolPkg40 directory, run the setup executable.
When prompted, select Complete Installation.
The installation checks for PTR fixes, and if needed, installs them.
Accept the defaults. Typically PTR fixes are not required on Dialogic
SR5.1.1.
The Install Wizard reboots the computer.

You must configure the Dialogic software for the appropriate signaling
T1/E1 ISDN or Robbed-Bit.
Note: Using Terminal Services might cause a failure to detect Dialogic
boards after a reboot. If this failure occurs, log off Terminal Services and
log back in. If the board remains undetectable, contact Dialogic technical
support.
Configuring DM/V-A Boards

The DM/V-A boards require SR5.1.1. Regardless of signaling protocols,
you must complete the following workaround if you are using DM/V-A
boards.
Dialogic Service hangs when it is set to autostart mode in Windows
Service, and this setting will also be a problem when another application,
such as WatchDog, is set to autostart and depends on the Dialogic Service.
A workaround for Dialogic PTR 25513 is to change the Dialogic
dependencies.
1
Select Start > Run regedt32.
From the window HKEY_LOCAL_MACHINE, go to

\Sytem\CurrentControlSet\Services\Dialogic\.
In the right side window, double-click DependOnService.
Add dlgcmcd to the top of the list, so it looks like this:

dlgcmcd
Dlgcsram
Deployment Guide
49
Click OK.
Exit regedt32.
Configuring DM/V-A Boards for T1/E1 ISDN

If using ISDN call control signaling, the following configuration is
required:
1
Navigate to the directory where Dialogic\Data is installed (typically

C:\Program Files\Dialogic\Data).
In a text editor, open the appropriate configuration file for your installed
board:
ml2_dsa_<xxx>.configfor DM/V480A-2T1 or DM/V600A-2E1
ml2_qsa_<xxx>.configfor DM/V960A-4T1 or DM/V1200A-4E1

Where <xxx> is the ISDN protocol being used by the trunk, for
example, 4ESS, 5ESS, DMS, or net5.
In section [CHP] of each file, change Setparm=0x1311,2 to

Setparm=0x1311,1
This action sets the default port startup mode to InService.
Save and close the files.
Open an MS-DOS command prompt and change the current directory to

the <Dialogic>\Data directory (typically c:\program files\dialogic\data).
Run the following commands:
For DM/V480A-2T1 or DM/V600A-2E1:

..\bin\fcdgen ml2_dsa_<xxx>.config
The following line should return:
Building ml2_dsa_<xxx>.fcd from ml2_dsa_<xxx>.config

For DM/V960A-4T1 or DM/V1200A-4E1:
..\bin\fcdgen ml2_qsa_<xxx>.config
Building ml2_qsa_<xxx>.fcd from ml2_qsa_<xxx>.config
50
Close the command prompt.
Start Dialogic Configuration Manager (DCM) by going to Start >

Programs > Intel > Dialogic System Software > Configuration
Manager.
The first time you start DCM, the prompt shown in Figure 1 appears.
Figure 1: Computer NameDialogic Configuration Manager Dialog Box
Deployment Guide
51
Select Local and click Connect. Dialogic autodetects all the boards and
prompts for the correct firmware file, as shown in Figure 2.
Figure 2: Dialogic Configuration ManagerAssign Firmware File Dialog Box

10
Select the firmware file from the Available Firmware list.
For a DM/V480A-2T1 or DM/V600A-2E1 board, select

ml2_dsa_<xxx>.pcd
For a DM/V960A-4T1 or DM/V1200A-4E1 board, select

ml2_qsa_<xxx>.pcd
11
Click OK.
12
For DM/V600A-2E1 and DM/V1200A-4E1 boards only, check the

Media Type parameter.
a
Select DCM > TDM Bus configuration tab.

b Set the Media Type to Alaw.
Configuring the DM/V boards is now complete.
13
52
Start the Dialogic Service by clicking the green button on the DCM
toolbar.
Configuring DM/V-A Boards for T1 Robbed-Bit

For T1 Robbed-Bit call signaling, the following configuration is required:
1
Navigate to the directory where Dialogic\Data is installed (typically

C:\Program Files\Dialogic\Data).
In a text editor, open the appropriate configuration file for your installed
board:
ml2_dsa_t1.config (used for DM/V480A-2T1)
ml2_qsa_t1.config (used for DM/V960A-4T1)
In each [CHP] section, change Setparm=0x1311 to Setparm=0x1311,1

This action sets the default port startup mode to InService.
In each [CHP] section, change the first instance of Protocol Type to one
of the following:
1 for E&M
2 for Loop Start
3 for Ground Start

This action sets the ProtocolType to either E&M, Loop Start, or Ground
Start.
In each [CHP] section, change the first instance of AnswerTimeout to

180000. This action sets AnswerTimeout to answer timeout for
outbound calls.
In each [CHP] section, set the first instance of DNIS to y if DNIS is to

be collected for inbound calls. Set DNIS to n if DNIS will not be
collected.
Note: Setting DNIS to y when DNIS is not being transmitted causes
delays in processing inbound calls.
In each [CHP] section, change Blind Transfer to 0 (Off). This turns off
BlindTransfer.
Set LineType to either D4 or ESF.

Each trunk has a [lineAdmin.x] section, where x is the physical
trunk ID.
In the ml2_dsa_t1.config file (used by the DM/V480A-2T1 boards),
you will have [lineadmin.1] and [lineAdmin.2].
In the ml2_qsa_t1.config file (used by the DM/V960A-4T1), you will
have [lineAdmin.1], [lineAdmin.2], [lineAdmin.3], and [lineAdmin.4].
Deployment Guide
53
In each of the [lineAdmin.x] sections, change Setparm=0x1601 to

Setparm=0x1601,0 for D4, or Setparm=0x1601,1 for ESF.
9
Set Coding to either B8ZS or EMI.

In each of the [lineAdmin.x] sections, change Setparm=0x1603 to
Setparm=0x1603,7 for B8ZS, or Setparm=0x1601,8 for AMI.
10
Save and close the files.
11
Open an MS-DOS command prompt and change the current directory to

the <Dialogic>\Data directory (typically c:\program files\dialogic\data).
12
Run the following commands:

a
For DM/V480A-2T1 run

..\bin\fcdgen ml2_dsa_t1.config
Building ml2_dsa_t1.fcd from ml2_dsa_t1.config
For DM/V960A-4T1 run

..\bin\fcdgen ml2_qsa_t1.config
Building ml2_qsa_t1.fcd from ml2_qsa_t1.config
13
54
Start Dialogic Configuration Manager. The first time you start DCM,
the prompt shown in Figure 3, on page 55 appears.
Figure 3: Computer NameDialogic Configuration Manager Dialog Box

14
Deployment Guide
Select Local and click Connect. Dialogic autodetects all the cards and
prompts for the correct firmware file, as shown in Figure 4, on page 56.
55
Installing VCS
Figure 4: Assign Firmware File Dialog Box

15
Select the firmware file from the Available Firmware list.
For a DM/V480A-2T1 board, select ml2_dsa_t1.pcd
For a DM/V960A-4T1 board, select ml2_qsa_t1.pcd
16
Click OK. Configuring the DM/V-A board is now complete.
17
Start the Dialogic Service by clicking on the green button on the DCM
toolbar.
Installing VCS
56
Insert the VWAP CD into the CD-ROM drive.
From the solution_specific\VWCO\VCS directory, run the VCS setup

executable. The Install Wizard starts.
Select (C or D):\CN as the destination folder.
Click Next.
If prompted to use Dialogic, click Yes.
Configuring VCS
When prompted Are Directory Services enabled? click Yes.
Enter the Fully Qualified Name of the Directory Server, Directory User
Name, Password, and Root Domain Name.

Click Yes to restart the computer, then click Finish.

Note: If a dialog box appears asking to run the Found New Hardware
Wizard, it means that the Windows 2000 software does not support
Plug and Play. Refer to Troubleshooting VWPS Installation on page
162 for more information.
10
Open Internet Explorer and enter the URL http://localhost:9810.

The VCS Network Management page opens. If an error occurs where
Network Management or WatchDog is not starting, proceed to
Configuring VCS on page 57. Configuring the VCS might resolve the
error.
Note: For information on the Network Management GUI, refer to the

Voice Web Application Platform 6.5 Operations and Provisioning Guide.
Configuring VCS
To configure basic VCS parameters:
For each machine on which VCS is installed, modify the VCS settings as
follows.
Deployment Guide
Log in to VWPS, then click Servers.
Expand the nodes VCS > <VCSComputerName>, then click

PopGateway.
Click Edit Node. The Server Configuration page for that node opens.
57
Configuring VCS
Supply values for the parameters listed in Table 7.

Table 7: VCS Parameters
Parameter
Description
Example
Primary DID
Mapper
<Fully Qualified Name of

Dispenser Computer>/
did_url_mappings/$did$.xml
http://dispenser/
did_url_mappings/
$did$.xml
Backup DID
Mapper

http://dispenser2/
did_url_mappings/
$did$.xml
Primary
Outbound DID

did_url_mappings/$resellername$_$customername$_$applicationname$_OutboundDID.xml
http://dispenser/
did_url_mappings/
$resellername$_$customername$_$applicationname$_OutboundDID.
xml
Backup
Outbound DID

Secondary Dispenser Computer>/
http://dispenser/
did_url_mappings/
$resellername$_$customername$_$applicationname$_OutboundDID.
xml
telephonydll
Name of Dialogic version dll file
DialogicMgrSR51.dll
For Nuance, use

DialogicMgrSR51.dll, and for
SpeechWorks OSR, use
DialogicGOSAPI.dll
Billing Server
URL
58
<Fully Qualified Name of Billing

Computer>:9811/billing/
events.asp
http://Billing:9811/
billing/events.asp
Click Submit.
Determine the number of inbound and outbound ports that are required.
Expand the PopGateway node and click Route1.
Select the route type, inbound or outbound, from the pull-down list.
Configuring VCS
Change the Channels field to designate the ports for this route. In the
Channels field, the numbers 123 represent T1 line #1:ports 123. For
example, 1:1-5 designates 5 outbound ports.
Note: Genesys recommends limiting a popgateway to 60 channels.
10
Copy the Route1 node to create a Route2 node.
11
Configure the Route2 node based on the number of inbound or

outbound ports desired.
12
If Robbed-Bit is used, for each Route under each PopGateway enter the
following value for the T1rb Protocol File parameter:
For DMV boards, enter DMV
To configure Page Collector:
For each machine on which VCS is installed, modify the Page Collector
setting as follows.
1
Expand the nodes VCS > <VCSComputerName>, then click Page

Collector.
Configure the parameter listed in Table 8.

Table 8: Page Collector Parameters
Parameter
host cache list
Description
Comma separated list of host

names from which all static
responses are cached at Page
Collector. Cached files are used
only if the network fetch fails.
Example
dispenser.genesys.com
Note: Make sure that you configure the host cache list parameter for each
VCS. This list indicates, among many things, the servers where the did.xml
and the app.xml files reside, such that when the VCS fetches these pages,
the VCS will cache them locally on the server.
Deployment Guide
59
Configuring VCS
Configuring VWPS for T1 Robbed-Bit

If Robbed-Bit is used, perform this procedure:
1
Expand the nodes VCS > <VCSComputerName> >PopGateway1,

then click Route1.
Click Edit Node.
Set the value of T1rbProtocolFile to DMV.
Expand the node PopGateway1, then click Route2.
Click Edit Node.
Set the value of T1rbProtocolFile:
For outbound trunks, set to DMV.

For DTMF on outbound trunks, set to DMV.
Note: Be sure to set the value with only the file name, not the
extension; that is, do not add .cdp to the value.
60
For both Route 1 and Route 2 set the following values:
Signaling type
ChannelsFor example 1:1-24, 2:1-24
Network Type1
T1 Robbed-Bit ANI/DNIS order(depends on trunk carrier)
Stop Dialogic Service.
10
Restart WatchDog.
Chapter
Nuance 8.0.0 Installation

and Configuration for VCS
This chapter describes how to install and configure Nuance 8.0.0 software
on the Voice Web Communication and Resource Servers.
Required Software, page 61

Installing and Configuring Nuance 8.0.0 Software, page 62
Configuring Nuance, page 68
Required Software
The following third-party software is required to install Nuance:
Deployment Guide
Nuance version 8.0.0 (Available from Nuance)

Nuance Service Pack SP030124 (Available from Nuance)
Nuance Dialogic DM3 Audio Provider version 2.0.3 (DMV boards)
LanguageModule-EnglishAmerica-v8-0-r2.zip
61
Chapter 6: Nuance 8.0.0 Installation and Configuration for VCS
Installing and Configuring Nuance 8.0.0 Software
Installing and Configuring Nuance 8.0.0

Software
The following Nuance naming conventions are used:
Nuance Recognition ServerRecServer

Nuance Resource ManagerRM
Nuance Compilation ServerCompServer
Nuance License ManagerNLM
Nuance Recognition ClientRecClient
Nuance must be installed on all VCS machines that act as Nuance ASR
recognition clients. Additional components may be turned on depending on
the architecture. Nuance must also be installed on all non-VCS Resource
Servers (RecServers, Resource Managers, License Managers, and
Compilation Servers). Additional components may be turned on depending
on the architecture. Procedures to turn on additional components are
described in Installing and Configuring Nuance Watcher on page 63.
Installing Nuance 8.0.0 Software

1
Log on as administrator.
From the Nuance Installation CD, run the Nuance 8.0.0 setup.exe.
Follow the onscreen instructions.
When prompted for the installation type, select Typical, then click
Next.
At the end of the installation clear the check box labeled Install
Watcher as a Windows2000 Service.
When prompted, reboot the computer.
Installing Nuance Service Pack SP030124
Install Nuance Service Pack SP030124 by extracting the zipped file into
<Nuance Installation Drive:>\Nuance\v8.0.0.
Installing Nuance Audio Provider
62
Stop all Nuance processes.
DM/V boardsunzip the Nuance Dialogic DM3 Audio Provider

(version 2.0.3) software to the <Nuance Installation
Drive:>\Nuance\v8.0.0.
Installing US English Language Pack
Install LanguageModule-EnglishAmerica-v8-0-r2.zip by extracting the

zipped file into <Nuance Installation Drive:>\Nuance\v8.0.0.
Loading the Default Package on Resource Servers

1
On each of the non-VCS CompServers and RecServers, create the

directory Cn\ASR\Packages\Nuance\Telera.
From the VWAP CD, solution_specific\VWCO\ASRDefault Packages\

Nuance directory, copy the default package,
TELERA_DEFAULT_DYNA folder.
Paste the default package TELERA_DEFAULT_DYNA folder into the

Telera folder created in Step 1.
Installing and Configuring Nuance Watcher

Installing watcher-daemon.startup
1
From the VWAP CD, VWCO\ASRConfig\Nuance directory, copy the

watcher-daemon.startup file.
On each VCS and Resource Server (RecServer, RM, CompServer,

NLM), paste the file into the following directory:
<Nuance Installation Drive>:\Nuance\v8.0.0\data
Open the watcher-daemon.startup file in Notepad.
In the file on the VCS computers, in the Start 8.0 section, uncomment,
by removing the # character, the lines for the processes that run on that
particular VCS.
For example, if only one PopGateway runs on the VCS, in the
following section, at the bottom of the file:
#recclient config.RecClientPort=9200
client.Behaviors=calllog \
#config.LogFileRootDir=%NUANCE%\logs \
#config.LogFileNamePrefix=9200 \
#watcher.RestartOnFailure=TRUE
Deployment Guide
63
Uncomment the lines so that the sections appears like this:

recclient config.RecClientPort=9200
config.LogFileRootDir=%NUANCE%\logs \
config.LogFileNamePrefix=9200 \
watcher.RestartOnFailure=TRUE
5
If there are two PopGateways:

#recclient config.RecClientPort=9201
#config.LogFileRootDir=%NUANCE%\logs \
#config.LogFileNamePrefix=9201 \
Uncomment the other processes that run on the VCS such as RecServer
and/or NLM. For example, if only the NLM and RecServer run on the
machine, then the original file looks similar to this:
#nlm %nuance%\data\license-702.txt \
#config.LogFileRootDir=%nuance%\logs \
#resource-manager \
#recserver \
#watcher.RestartOnFailure=TRUE \
#-package
"%CN_ROOT%\ASR\packages\nuance\Telera\TELERA_DEFAULT_D
YNA"
#compilation-server \
#-package
%CN_ROOT%\asr\packages\nuance\telera\TELERA_DEFAULT_D
YNA
64
Uncomment to:
nlm %nuance%\data\license-702.txt \
config.LogFileRootDir=%nuance%\logs \
#resource-manager \
recserver \
config.LogFileRootDir=%nuance%\logs \
watcher.RestartOnFailure=TRUE \
-package
%CN_ROOT%\ASR\packages\nuance\Telera\TELERA_DEFAULT_D
YNA
#-package
%CN_ROOT%\asr\packages\nuance\telera\TELERA_DEFAULT_D
YNA
7
Save and close the file.
For Resource Servers (RecServer, RM, CompServer, NLM)

uncomment the process(es) that the particular Resource Server
performs.
For example, if the Resource Server acts only as a CompServer, the
lines might look like this:
#### run compilation server
-package
%CN_ROOT%\asr\packages\nuance\Telera\TELERA_DEFAULT_DY
NA \
#config.LogfileRoot=%nuance%\logs\cs \
#config.LogfileNum=50 \
Uncomment to:
#### run compilation server
compilation-server \
Deployment Guide
65
-package
%CN_ROOT%\asr\packages\nuance\Telera\TELERA_DEFAULT_DY
NA \
config.LogfileRoot=%nuance%\logs\cs \
config.LogfileNum=50 \
9
If the Resource Server performs multiple processes, uncomment each

corresponding entry as shown in Step 6.
10
Installing Nuance License

1
Obtain a license file, license.txt, from Nuance.
From the <Nuance Installation Directory>\data directory, open the

watcher-daemon.startup file.
In the first few lines, locate an entry that specifies the NLM location.
For example, the entry appears similar to this:
#### run nlm if license manager needed
nlm %NUANCE%\data\license-800.txt \
Place the license.txt file in the NLM location specified in the entry.
Note: The actual name of your file might be different, such as license80.txt. Make sure the entry has the correct file name.
Configuring Nuance Watcher as a Service
66
From the VWAP CD, solution_specific\VWCO\ASRConfig\Nuance

directory, copy the watcher-service-install.bat file.
Paste the file directly under the C: drive on the VCS and each Resource
Server.
Select Start > Run.
Enter cmd and click OK.
At the C:/> prompt, type watcher-service-install.bat and press Enter.

Running the watcher-daemon-nt-service-init records values in the
registry, which are then used by default each time the service starts.
You can change these default values by running watcher-daemon-ntservice-init again with new values.
Note: If you need to uninstall Nuance watcher, run this command:
watcher-daemon-win32-service-init -u
Configuring VCS to Support ASR Features

The VCS computer must be configured to function as an ASR-enabled
VCS. The VCS should already be properly installed for Intel/Dialogic
SR 5.1.
Editing Nuance Configuration File

1
From the VWAP CD, solution_specific\VWCO\ASR\ASRConfig\

Nuance directory, copy the nuance-resources.site file.
Paste the file into the <Nuance Installation Directory>\data directory on

each VCS and Resource Server.
Right-click the file and select Properties > General tab.
Clear the Read-only check box in the Attributes section.
Open the file in a text editor.
In the start for common (VCS, IPCS, RS) section of the file,
uncomment all of the lines.
Note: Uncomment the lines by deleting the semicolon (;) character.
Do not uncomment double semicolon lines.
On the VCS, in the start VCS and start DM3 T1 board (VCS)
sections, uncomment all of the lines as appropriate for VCS and
DMV/A board support.
On the following first two lines:

;lm.Addresses= Fullq Qualified Name of machine running
license manager
;rm.Addresses= Fullq Qualified Name of machine running
resource manager
Deployment Guide
67
Configuring Nuance
Enter the actual fully qualified name of the license manager and
resource manager.
9
On the VCS, in the start RobBit T1 and start E1 alaw sections,

uncomment all of the lines as appropriate for Robbed-Bit and/or alaw
support.
10
11
Select Start > Programs > Administrative Tools > Services.
12
Start the Nuance Watcher Daemon and WatchDog services.
13
In Internet Explorer, open http://localhost:7080. The Nuance Watcher

HTTP page opens, which is used to administer Nuance services on the
computer.
14
Configuring Nuance
68
Expand the nodes VCS > <ComputerName> > PopGateway1.
Select DialogicMgrSR511.dll from the Telephony DLL drop-down

menu.
Click Submit.
Expand the nodes VCS > <ComputerName> > PopGateway1, then

click ASR.
Click Edit Node.
Select Nuance80 from the ASR Platform drop-down menu.
Click Submit.
Select the Nuance node under each ASR node and click Edit Node.
10
Enter 9200 in the Rec Clients Ports field.
11
Select the Dynamic Grammar check box.
12
Ensure that Share CSP Resource check box is selected.
13
Click Submit.
Configuring Nuance
14
(If applicable) Expand the nodes VCS > <ComputerName> >

PopGateway2. Repeat Steps 313, except enter 9201 in the RecClients
Ports field.
15
Restart WatchDog on each ASR-enabled VCS.
Creating ASR Groups

1
Log in to VWPS, then click Groups.
If the ASRTeleServers Group is not present:

a
Click the Click to add a Group link.

b Create a group with the name ASRTeleServers.
Note: Do not use spaces in the name.
Deployment Guide
Click the ASRTeleServers Group, then click Edit Group.
Add all of the VCS ASR servers to the group.
Click Submit.
69
70
Configuring Nuance
Chapter
SpeechWorks OSR ClientServer Installation and

Configuration for VCS
This chapter describes how to install and configure SpeechWorks Open
Speech Recognizer (OSR) software.
Note: If you plan on using the SpeechWorks OSR Client-Server ASR
software, you must first install SpeechWorks before installing VCS.
Antivirus software may interfere with the installation process. Make sure
antivirus software is not running during installation.
Deployment Guide
Installing SpeechWorks OSR, page 72

Installing ASR Log Manager Agent, page 75
Configuring SpeechWorks OSR, page 76
Configuring OSR Server to ASR Log Manager, page 77
71
Chapter 7: SpeechWorks OSR Client-Server Installation and Configuration for VCS
Installing SpeechWorks OSR

Installing OSR Server
Install the OSR Server software on the OSR Server machine, which is
recommended not to be co-resident with the VCS machine.
1
From the Third Party SpeechWorks OSR Client-Server 1.1.4 CD,

OSR_ClientServer1.1.4_GA directory, run the installation software.
Follow the onscreen instructions, and install the following components:
OpenSpeechRecognizer Server 1.1
3rd Party Licensing Components
Installing Patch HF1-1-4-01

Install the patch on the OSR Server machine.
From the Third-Party SpeechWorks OSR Client-Server 1.1.4 CD,

OSR_ClientServer1.1.4_Patches/HF1-1-4-01 directory, run the
HFInstaller.exe.


HFInstaller.exe.
Installing OSR Client

Install the OSR Client software on the OSR Client, which is co-resident
with the VCS machine.
1

Follow the onscreen instructions, and install the following component:
OpenSpeech Recognizer Client 1.1
Configuring OSR Client

The OSR client needs to know the location of the OSR Server it will be
using:
72
Run the OSR Client Configuration utility by selecting Start >

Programs > Speechworks > OpenSpeech Recognizer Client-Server
> OSR Client Configuration Tool.
Click Select Servers.
Enter the server name, IP address, and port (4901) for the OSR Server
machine(s) you will be using.
Select the Enabled check box, and then click Apply and Done.
Configuring License
OSR Server Machine
Use the OSR Server machine as the license server. To obtain and configure
the OSR license, refer to the SpeechWorks OSR Licensing Handbook.
OSR Client (VCS) Machine

1
Set the location of the license server. Make the following changes to the
registry entry:
HKEY_LOCAL_MACHINE\SOFTWARE\SpeechWorks
International\OpenSpeech Recognizer\1.1
Set the value of the key SWILicenseServerList to 27000@<OSR server

name> where OSR server name is the name of the OSR server machine,
for example, 27000@OSR-SRVR.
Open the file C:\Program Files\Speechworks\OpenSpeech

Recognizer\Config\baseline.xml.
Edit the swirec_licensing_mode and swiep_licensing_mode

parameters to explicit as shown in this example:
<param name="swirec_licensing_mode">
<value>explicit</value>
</param>
<param name="swiep_licensing_mode">
</param>
Adding a Registry Entry for OSR Server
Deployment Guide
Set the OSR Server process to start automatically on the OSR Server
machine.
Add the following registry entry:
73
3
Add the following new string value:

SWIsvcMonAutoStart
Set the value to yes.
Configuring Services on OSR Server

On the OSR Server machine, set the OSR Server processes to start
automatically.
1
Select Start > Settings > Control > Panel > Administrative Tools >
Services.
Set the following startup services as follows:
OSR Licensing ServiceAutomatic
SpeechWorks OSR ServerAutomatic
Configuring Services on VCS

1
On the VCS machine, select Start > Settings > Control Panel >
Administrative Tools > Services.
Set the following startup services as follows:
Remote Access Connection ManagerDisabled
TelephonyDisabled
Windows Management Instrumentation Driver Extensions

Automatic
Configuring License Parameters for Both Client and

Server Machines
Perform this procedure if you have installed the OSR Client and the OSR
Server on separate machines.
74
Go to the registry entry HKEY_LOCAL_MACHINE\SOFTWARE

\SpeechWorks International\OpenSpeech Recognizer\1.1.

name>, where OSR server name is the name of the OSR License Server
machine (for example, 27000@OSR-SRVR).
Chapter 7: SpeechWorks OSR Client-Server Installation and Configuration for VCSInstalling ASR Log Manager Agent


</param>
</param>
Installing ASR Log Manager Agent

If the OSR Server machine is not co-resident with VCS, after installing the
OSR Server software, the ASR Log Manager Agent must be installed on
the OSR Server machine.
Note: In this situation, the TTS server and the OSR server cannot coexist.
The ASR Log Manager Agent will respond to the VWM ASR Log
Manager commands to transfer captured utterance files.
Note: Only install the ASR Log Manager Agent on OSR Server machines
that are not co-resident with VCS.
Install the ASR Log Manager Agent on each OSR Server not co-resident
with VCS machine:
1
From the VWAP CD, solution_specific\VWLMA directory, run the

ASR Log Manager Agent setup executable
(ASRLMAgtSetupRelease.exe).

Deployment Guide
75
Configuring SpeechWorks OSR
After installation of the ASR Log Manager Agent, an entry in VWPS

under the Server section labeled ASR Log Manager Agent should
appear.
Expand the ASR Log Manager Agent and an entry for each OSR Server
with ASR Log Manager Agent installed should appear.

After installing the SpeechWorks OSR software, you have to perform
additional configuration to allow all necessary Voice Communications
Server (VCS) machines to recognize and utilize the SpeechWorks OSR
software for ASR.
You must first install VCS (refer to Chapter 5, VCS Installation and
Configuration on page 45), then for each VCS that is to recognize the
SpeechWorks OSR Server, perform the following steps in VWPS:
1
Expand the nodes Voice Communication Server >

<VCSComputerName> > PopGateway1, then click ASR.
Click Edit Node.
From the ASR Platform drop-down menu, select

SpeechWorksOSR11.
Click Submit.

<VCSComputerName> > PopGateway1 > ASR, then click
SpeechWorksOSR.
Click Edit Node.
Enter the value for the field labeled Max number of simultaneous
channels doing wave captures.
Click Submit.
Perform the above steps for each PopGateway on each VCS machine that
has OSR Client installed and will be using SpeechWorks OSR for ASR.
Creating ASR Groups
76
Configuring OSR Server to ASR

3
Click Submit.

ASR Log Manager
After installing the SpeechWorks OSR software, additional configuration in
VWPS is required to allow the ASR Log Manager on VWM to recognize
all necessary SpeechWorks OSR Servers.
Configuring OSR Servers to ASRTeleServers Group

After the ASRTeleServers Group has been created, all of the OSR Server
machines must be added to the group. Use one of the following two
methods to add the OSR Server machines to the ASRTeleServers Group
depending on whether the OSR Server is co-resident or not co-resident with
the VCS machine.
OSR Server Not Co-resident With VCS
Deployment Guide
Click ASRTeleServers, then click Edit Group.
In the Available Servers scroll down list, find the entries under heading
ASRLMAGT.
Select all machines under the heading ASRLMAGT.
Click Add. The selected ASRLMAGT machines now appear in the

Selected Servers scroll down window.
Click Submit.
77
Configuring OSR Server to ASR
OSR Server Co-resident with VCS
78
VCS.
Select all VCS machines that have the OSR Server installed on them.
Click Add. The selected VCS machines now appear in the Selected
Servers scroll down window.
Click Submit.
Chapter
MRCP Server Configuration

for VCS
This chapter describes how to configure an MRCP Automatic Speech
Recognition (ASR) server for VCS.
Installing the MRCP Server, page 79

Configuring MRCP Server, page 79
Installing the MRCP Server

Install the MRCP Server software on the MRCP Server machine, using the
instructions provided by the MRCP Server vendor.
Genesys recommends that the MRCP Server machine not be coresident
with the VCS machine.
Configuring MRCP Server

After installing the MRCP Server software, you must complete additional
configuration tasks that enable all necessary Voice Communications Server
(MRCP clients) machines to recognize and utilize the MRCP Server
software (MRCP Server) for ASR.
Deployment Guide
79
Chapter 8: MRCP Server Configuration for VCS
For each VCS that is to recognize the MRCP Server, perform the following
steps in VWPS:
1

<VCSComputerName> then click PopGateway1.
Click Edit Node.
From the Telephony DLL drop-down menu, select

DialogicMgrGOSAPI.dll.
Click Submit.

<VCSComputerName> > PopGateway1, then click ASR.
Click Edit Node.
From the ASR Platform drop-down menu, select MRCP.
Click Submit.
10

<VCSComputerName> > PopGateway1 > ASR, then click MRCP.
11
Click Edit Node.
12
Supply the value for the parameter listed in Table 9. Be sure to enter
your RTP port range for each PopGateway (do not enter the example
value shown).
Table 9: MRCP Parameters
80
Parameter
Description
Example Value
RTP Port Range
Realtime Transport Protocol

port range.
5000051000
13

<VCSComputerName> > PopGateway1 > ASR > MRCP, then click
MRCPServer1.
14
Click Edit Node.
15
Supply values for the parameters listed in Table 10 on page 81.
Table 10: MRCP Server 1 Parameters
Parameter
Description
Example Value
MRCP Server URL
The URL to the MRCP

Server machine.
rtsp://machine/media/
speechrecognizer
MRCP Server Port
MRCP server port.
port number
16
Click Submit.
Configuring Multiple MRCP Servers

If you have installed more than one MRCP Server, follow these
instructions.
1

<VCSComputerName> > PopGateway1 > ASR, then click MRCP.
Select Copy Node.
Click Copy Node, name the new node, then click Copy.
Refresh the window to display and access the newly deployed MRCP
node.
Creating ASR Groups

1

a

Deployment Guide
Select the Group Type from the drop-down list.
Click Submit.
81
82
Chapter
Text-To-Speech Installation
and Configuration for VCS
This chapter describes how to install and configure Speechify 2.1.6 or
RealSpeak 3.5 and Genesys text-to-speech (TTS) software. You must
install Genesys software and the vendor TTS software on the same
computer.
Note: If deploying SpeechWorks OSR on a separate server from VCS, the
ASR Log Manager Agent component is required on the OSR server. In this
situation, the TTS server and OSR server cannot co-exist.
Also, antivirus software may interfere with the installation process. Make
sure antivirus software is not running during installation.
Deployment Guide
Installing MySQL Components, page 84

Installing Speechify 2.1.6, page 84
Installing RealSpeak 3.51 SP2, page 85
Installing Genesys Text-to-Speech Software, page 85
Configuring Text-to-Speech, page 86
83
Chapter 9: Text-To-Speech Installation and Configuration for VCS
Installing MySQL Components

Before installing vendor software, set up database connectivity with
MySQL. Download the following files from http://www.mysql.com:
MySQL 3.51.06 or later Database Software

MyODBC 2.50 Driver
Installing MySQL 3.51.06 or Later Database Software

1
Run the setup for MySQL 3.51.06 or later database software.
Select the folder in which to install the software.
Select Typical installation.
Installing MySQL ODBC Driver

1
Run the setup for MyODBC 2.50 ODBC driver software.
In the Microsoft ODBC Setup dialog box, click Continue.
Select MySQL from the Available ODBC Drivers list and click OK.
In the Data Sources dialog box, click Close.
Click OK.
Installing MDAC 2.7 or Later

Note: You must stop SQL before installing MDAC.
Run MDAC_Typ.exe for version 2.7 or later.
Installing Speechify 2.1.6
84
From the SpeechWorks Speechify CD, run the setup.exe.
Select Typical installation, and click Install.
Run the setup for the voice fonts Mara and Tom or any other voice
fonts you have for Speechify.
Installing RealSpeak 3.51 SP2
Setting Maximum Number Of Client Connections

By default, Speechify sets the maximum number of client connection per
voice to 18. You can modify this parameter (Maximum Number of Clients)
from the Speechify Server Management application (Start > Programs >
Speechify > Speechify Server Management). For details, refer to the
Speechify User Guide.

1
From the ScanSoft RealSpeak CD, run the setup.exe for the appropriate
voice fonts (typically Jennifer and David).
Note: The vendor language, such as American English, is specified
and controlled by the vendor. Refer to the vendor documentation for
details.
Follow the onscreen instructions and accept all default values. This
installs the voice fonts and the RealSpeak TTS engine.
Installing Genesys Text-to-Speech

Software
1
For a new installation, go to Step 4.

For an upgrade, uninstall the previous version of TTS software from
Start > Settings > Control Panel >Add Remove Programs >Text-toSpeech Server.
Restart the computer.
When the server reboots, delete the folder (C or D):\cn\bin.
From the VWAP CD, solution_specific\TTS\<TTS Vendor> directory,

run the TtsSetupRelease.exe.
Note: Make sure you choose the appropriate TTS vendor directory.
Deployment Guide
Accept the License Agreement.
At the Select MySQL Base Folder screen, enter the location of MySQL,
then click Next.
85
Configuring Text-to-Speech
When prompted for an installation directory, select (C or D):\Cn, then

click Next.
At the Select Components screen, select the appropriate TTS vendor,

then click Next.
10
Enter the Fully Qualified Name of the Directory Server, the Directory
User Name, the password, and the Root Domain Name, and then click
Next.
11

12
When prompted, enter the MySQL password (if any) for the MySQL
root account.
13
When the installation finishes, reboot the computer.
14
Open Internet Explorer and enter the URL http://localhost:9810. The

TTS Network Management page opens.
Note: For information on the TTS Network Management GUI, refer to

the Voice Web Application Platform 6.5 Operations and Provisioning
Guide.
Perform the following procedure on each VCS. At least one VCS must be
installed and configured before performing the following steps.
86
Create a group with a descriptive name for the TTS servers that VCS
will use, for example, TTSforVCS (no spaces).
Select TTS from the Group Type drop-down list.
Add all of the TTS servers that VCS will use to the group.
Click Submit.
Click Servers.
Expand the nodes VCS > <ComputerName>, then click

PopGateway1.
Click Edit Node.
10
Select the Primary TTS Server Group created in Step 3 and click Add.
11
Click Submit.
12
Repeat Steps 111 for each VCS.

Note: Different VCSs may access different groups of TTS server.
Create, name, and assign the groups to each VCS accordingly.
13
Click Servers.
14
Expand the nodes TTS > <ComputerName>> <TTS_Vendor>.
15
Select the voices that were chosen during installation and click Edit
Node.
16
Ensure that the Language pull-down list is set to your locale, and edit
the other values as needed.
17
Click Submit.
To set the voice format

18
Click the <TTS_Vendor> node.
19
Click Edit Node.
20
Set the value for the Default Voice Format parameter as follows:
VOX_MULAW_8KHZUse this value for North America.
VOX_ALAW_8KHZUse this value for Europe.
21
Click Submit.
22
Restart WatchDog on the TTS machine for the changes to take effect.
Making Test Calls

The Speechify or RealSpeak Engine normally loads the voice fonts in
memory when the first TTS request is made. Loading the voice fonts takes
time and might result in the TTS request from the POP to time out.
Subsequent requests to the TTS Server should get processed within the
specified time out duration. Genesys recommends that you make at least
three calls to test the newly installed TTS Server.
Deployment Guide
87
88
Part
IP Communications Server
The chapters in Part 3 provide instructions for installing and configuring
the Internet Protocol Communications Server (IPCS). These procedures are
for a VoIP (IPCS-based) platform.
Chapter 10, IPCS Installation and Configuration on page 91

Configuration for IPCS on page 97
Chapter 12, Text-to-Speech Installation and Configuration for IPCS

on page 105
Deployment Guide
89
Part 3: IP Communications Server
90
Chapter
10
IPCS Installation and

Configuration
This chapter describes how to install and configure the Internet Protocol
Communications Server (IPCS).
Note: If you plan on using the SpeechWorks OSR Client-Server ASR
software, you must first install SpeechWorks before installing IPCS (see
Configuration for IPCS on page 97).
Antivirus software may interfere with the installation process. Make sure
antivirus software is not running during installation.
This chapter has the following topics:
Installing IPCS, page 91

Configuring IPCS, page 93
Installing IPCS
Before installing the IPCS software, make sure youve already installed the
following software:
MSXML 4.0 SP2 or later, which is available from the Microsoft web
site in the download section.
If you plan to use automatic speech recognition (ASR), install

SpeechWorks software. Refer to Chapter 11, SpeechWorks OSR
Client-Server Installation and Configuration for IPCS on page 97 for
instructions.
Deployment Guide
91
Chapter 10: IPCS Installation and Configuration
Installing IPCS
If you plan to use IPCS in DTMF-only mode, you do not need to install
the SpeechWorks software.
To install IPCS:
1
From the VWAP CD, solution_specific\VWCO\IPCS directory, run the

setup executable.
When the Install Wizard prompts to select a folder, select (C or D):\CN.

Note: The default drive is D.
If you are prompted to overwrite any existing files, select Yes. Repeat if
necessary.



Click Next.
92
Open Programs > Administrative Tools > Internet Services

Manager.
Expand the Server icon and select the 9810 listener web site.
10
Right-click and select Properties > Home Directory tab and ensure the
Local Path field is set to <IPCS Installation Drive>\Cn\web.
11
Configuring IPCS

IPCS Network Management page opens. If an error occurs where
Network Management or WatchDog is not starting, proceed to
Configuring IPCS on page 93. Configuring the IPCS might resolve
the error.
Note: For information on the IPCS Network Management GUI, refer to

the Voice Web Application Platform Operations and Provisioning Guide.
Configuring IPCS
To configure basic IPCS parameters:
For each machine on which IPCS is installed, modify the IPCS settings as
follows.
1
Expand the IPCS <Server Name> node, then click PopGateway.
Configure the mandatory parameters listed in Table 11. Enter the

optional parameters as needed.
Table 11: PopGateway Parameters
Parameter
Description
Example
Primary DID Mapper
<Fully Qualified Name of Dispenser

Computer>/did_url_mappings/$did$.xml
http://dispenser.company.com/
Primary Outbound
DID Mapper
<Fully Qualified Name of Dispenser

Computer>/did_url_mappings/$resellername$_$customer-name$_$applicationname$_OutboundDID.xml
http://dispenser.company.com/
did_url_mappings/$resellername$_$customername$_$applicationname$_OutboundDID.xml
Billing Server URL
Billing URL to post billing record to.

http://<Fully Qualified Name of Billing
computer>:9811/Billing/events.asp
http://
billing.company.com:9811/
Billing/events.asp
Local Tone
Rendering
Drop-down list:
Digitized Inband RTP
RTP using RFC-2833
SIP INFO Msg.
The default is RTP using RFC-2833.
RTP using RFC-2833
Deployment Guide
93
Configuring IPCS
Table 11: PopGateway Parameters (Continued)
Parameter
Description
Example
Media Server IP
The media server IP address; typically a local

IP address.
10.10.15.38
Media Server Port
The port for the media server.
9810
Sip1xxResponses
A comma separated list of SIP provisional

responses that the IPCS sends during inbound
call setup. Currently only 100 and 180 are
supported.
100, 180 (Default value)
(Optional) To change the appropriate SIP call reject response, click

Add New Parameter, then add the parameter and value shown in Table
12.
Table 12: PopGateway Parameters
Parameter
Description
Example
HangupCause_Fetch
Error
This hang-up cause value will be used if any

503 (Default value)
VoiceXML file download fails any time
during call setup. Possible values are 400-699.
6
Click Submit.
Select Route under PopGateway, and click Edit Node. The Server
Configuration page for that node opens.
Configure the parameters listed in Table 13, then click Submit.

Table 13: Route Parameters
94
Parameter
Description
Example
Call Direction
The direction of the call. Drop-down list:

In
Out
InOut
InOut
Max Channels
The number of channels the route can use. 100
Signaling Type
Call Signaling Type (always set this to

SIP).
SIP
Configuring IPCS
To configure Page Collector:
For each machine on which IPCS is installed, modify the Page Collector
settings as follows.
1
Expand the IPCS node and then click Page Collector.
Configure the parameter listed in Table 14, then click Submit.

Table 14: Page Collector Parameter
Parameter
host cache list
Description
Comma separated list of host

names from which all static
responses are cached at Page
Collector. Cached files are used
only if the network fetch fails.
Example
dispenser.genesys.com
Note: Make sure that you configure the host cache list parameter for each
IPCS. This list indicates, among many things, the servers where the did.xml
and the app.xml files reside, such that when the IPCS fetches these pages,
the IPCS will cache them locally on the server.
The IPCS configuration, without ASR, is complete. To configure IPCS
with ASR, refer to Chapter 11, SpeechWorks OSR Client-Server
Installation and Configuration for IPCS on page 97.
Deployment Guide
95
96
Configuring IPCS
Chapter
11
SpeechWorks OSR ClientServer Installation and

Configuration for IPCS
This chapter describes how to install and configure SpeechWorks Open
Speech Recognizer (OSR) software on the IP Communications Server.
Installing SpeechWorks OSR, page 97

Installing ASR Log Manager Agent, page 100
Configuring SpeechWorks OSR, page 101
Configuring OSR Server to ASR Log Manager, page 102

Installing OSR Server
Install the OSR Server software on the OSR Server machine, which is
recommended not to be co-resident with the IPCS machine.
1
Deployment Guide

97
Chapter 11: SpeechWorks OSR Client-Server Installation and Configuration for IPCS
Follow the onscreen instructions, and install the following components:
OpenSpeechRecognizer Server 1.1
3rd Party Licensing Components


HFInstaller.exe.

3

HFInstaller.exe.
Installing OSR Client

Install the OSR Client software on the OSR Client, which is co-resident
with the IPCS machine.
1

Follow the onscreen instructions, and install the following component:
OpenSpeech Recognizer Client 1.1
Configuring OSR Client

The OSR client needs to know the location of the OSR Server it will be
using:
98
Run the OSR Client Configuration utility by selecting Start >

Programs > Speechworks > OpenSpeech Recognizer Client-Server
> OSR Client Configuration Tool.
Click Select Servers.
Enter the server name, IP address, and port (4901) for the OSR Server
machine(s) you will be using.
Select the Enabled checkbox, and then click Apply and Done.
Configuring License
OSR Server Machine
Use the OSR Server machine as the license server. To obtain and configure
the OSR license, refer to the SpeechWorks OSR Licensing Handbook.
OSR Client (IPCS) Machine

1
Set the location of the license server. Make the following changes to the
registry entry:

name> where OSR server name is the name of the OSR server machine,
for example, 27000@OSR-SRVR.


</param>
</param>
Adding a Registry Entry for OSR Server

1
Set the OSR Server process to start automatically on the OSR Server
machine.
Add the following registry entry:

Add the following new string value:

SWIsvcMonAutoStart
Deployment Guide
Set the value to yes.
99
Installing ASR Log Manager
Configuring Services on OSR Server

On the OSR Server machine, set the OSR Server processes to start
automatically.
1
Select Start > Settings > Control > Panel > Administrative Tools >
Services.
Set the following startup services to:
OSR Licensing ServiceAutomatic
SpeechWorks OSR ServerAutomatic
Configuring Services on IPCS

1
On the IPCS machine, select Start > Settings > Control Panel >
Administrative Tools > Services.
Set the following startup services to:
Remote Access Connection ManagerDisabled
TelephonyDisabled
Windows Management Instrumentation Driver Extensions

Automatic
Installing ASR Log Manager Agent

If the OSR Server machine is not co-resident with IPCS, after installing the
OSR Server software, the ASR Log Manager Agent must be installed on
the OSR Server machine.
Note: In this situation, the TTS server and the OSR server cannot coexist.
The ASR Log Manager Agent will respond to the VWM ASR Log
Manager commands to transfer captured utterance files.
Note: Only install the ASR Log Manager Agent on OSR Server machines
that are not co-resident with IPCS.
Install the ASR Log Manager Agent on each OSR Server not co-resident
with IPCS machine:
1
100
From the VWAP CD, solution_specific\VWLMA directory, run the

ASR Log Manager Agent executable (ASRLMAgtSetupRelease.exe).
Chapter 11: SpeechWorks OSR Client-Server Installation and Configuration for IPCS Configuring SpeechWorks OSR

After installation of the ASR Log Manager Agent, an entry in VWPS

under the Server section labeled ASR Log Manager Agent should
appear.
Expand the ASR Log Manager Agent and an entry for each OSR Server
with ASR Log Manager Agent installed should appear.

After installing the SpeechWorks OSR software, you have to perform
additional configuration to allow all necessary IPCS machines to recognize
and utilize the SpeechWorks OSR software for ASR.
You must first install IPCS (refer to Chapter 10, IPCS Installation and
Configuration on page 91), then for each IPCS that is to recognize the
SpeechWorks OSR Server, perform the following steps in VWPS:
1
Expand IPCS > <IPCSComputerName> > McuXml, then click the

ASR link.
Click Edit Node.
From the ASR Platform drop-down menu, select OSRMgr11.
Click Submit.
Expand IPCS > <IPCSComputerName> > McuXml> ASR, then

click OSRMgr11.
Click Edit Node.
Enter the value for the field labeled Maxchannelwavecapture.
Click Submit.
Perform the above steps for each IPCS machine that has OSR Client
installed and will be using SpeechWorks OSR for ASR.
Deployment Guide
101
Chapter 11: SpeechWorks OSR Client-Server Installation and Configuration for IPCS Configuring OSR Server to ASR
Creating ASR Groups

1

a

3
Add all of the IPCS ASR servers to the group.
Click Submit.

ASR Log Manager
After installing the SpeechWorks OSR software, additional configuration in
VWPS is required to allow the ASR Log Manager on VWM to recognize
all necessary SpeechWorks OSR Servers.
Configuring OSR Servers to ASRTeleServers Group

After the ASRTeleServers Group has been created, all of the OSR Server
machines must be added to the group. Use one of the following two
methods to add the OSR Server machines to the ASRTeleServers Group
depending on whether the OSR Server is co-resident or not co-resident with
the IPCS machine.
OSR Server Not Co-resident With IPCS
102
ASRLMAGT.
Select all machines under the heading ASRLMAGT.
Click Add. The selected ASRLMAGT machines now appear in the

Selected Servers scroll down list.
Click Submit.
OSR Server Co-resident With IPCS
Deployment Guide
IPCS.
Select all IPCS machines that have the OSR Server installed on them.
Click Add. The selected IPCS machines now appear in the Selected
Servers scroll down list.
Click Submit.
103
104
Chapter
12
Text-to-Speech Installation
and Configuration for IPCS
This chapter describes how to install and configure Speechify 2.1.6 or
RealSpeak 3.5 and Genesys Text-to-Speech (TTS) software. You must
install Genesys software and the vendor TTS software on the same
computer.
Note: If deploying SpeechWorks OSR on a separate server from IPCS,
the ASR Log Manager Agent component is required on the OSR server. In
this situation, the TTS server and OSR server cannot co-exist.
Also, antivirus software may interfere with the installation process. Make
sure antivirus software is not running during installation.
Deployment Guide
Installing MySQL Components, page 106

Installing Speechify 2.1.6, page 106
Installing RealSpeak 3.51 SP2, page 107
Installing Genesys Text-to-Speech Software, page 107
Configuring Text-to-Speech, page 108
105
Chapter 12: Text-to-Speech Installation and Configuration for IPCS

Before installing vendor software, set up database connectivity with
MySQL. Download the following files from http://www.mysql.com:
MySQL 3.51.06 or later Database Software

MyODBC 2.50 Driver
Installing MySQL 3.51.06 or Later Database Software

1
Run the setup for MySQL 3.51.06 or later database software.
Select the folder in which to install the software.
Select Typical installation.
Installing MySQL ODBC Driver

1
Run the setup for MyODBC 2.50 ODBC driver software.
In the Microsoft ODBC Setup dialog box, click Continue.
Select MySQL from the Available ODBC Drivers list and click OK.
In the Data Sources dialog box, click Close.
Click OK.
Installing MDAC 2.7 or Later

Note: You must stop SQL before installing MDAC.
Run MDAC_Typ.exe for version 2.7 or later.
Installing Speechify 2.1.6
106
From the SpeechWorks Speechify CD, run the setup.exe.
Select Typical installation, and click Install.
Run the setup for the voice fonts Mara and Tom or any other voice
fonts you have for Speechify.
Setting Maximum Number Of Client Connections

By default, Speechify sets the maximum number of client connection per
voice to 18. You can modify this parameter (Maximum Number of Clients)
from the Speechify Server Management application (Start > Programs >
Speechify > Speechify Server Management). For details, refer to the
Speechify User Guide.

1
From the ScanSoft RealSpeak CD, run the setup.exe for the appropriate
voice fonts (typically Jennifer and David).
Note: The vendor language, such as American English, is specified
and controlled by the vendor. Refer to the vendor documentation for
details.
Follow the onscreen instructions and accept all default values. This
installs the voice fonts and the RealSpeak TTS engine.
Installing Genesys Text-to-Speech

Software
1
From the VWAP CD, solution_specific\<TTS vendor> directory, run

the TtsSetupRelease.exe.
Note: Make sure you choose the appropriate TTS vendor directory.
Deployment Guide
Accept the License Agreement.
At the Select MySQL Base Folder screen, enter the location of MySQL,
then click Next.
When prompted for an installation directory, select (C or D):\Cn, then

click Next.
At the Select Components screen, select the appropriate TTS vendor,

then click Next.
When prompted Are Directory Services Enabled? click Yes.
The Setup prompts you for the following directory information required
107


8
Click Next.
When prompted, enter the MySQL password (if any) for the MySQL
root account.
10
When prompted, restart the computer.
11

TTS Network Management page opens.
Note: For information on the TTS Network Management GUI, refer to

the Voice Web Application Platform 6.5 Operations and Provisioning
Guide.
Note: At least one IPCS must be installed and configured before
performing the following steps.
108
Create a group with a descriptive name for the TTS servers that IPCS
will use, for example, TTSforIPCS (no spaces).
Select TTS from the Group Type drop-down list.
Add all of the TTS servers that IPCS will use to the group.
Click Submit.
Click Servers.
Expand the nodes IPCS > <ComputerName >, then click McuXml.
Click Edit Node.
10
Select the Primary TTS Server Group created in Step 3 and click Add.
11
Click Submit.
12
Repeat Steps 111 for each IPCS.

Note: Different IPCSs may access different groups of TTS servers.
Create, name, and assign the groups to each IPCS accordingly.
13
Click Servers.
14
Expand the nodes TTS > <ComputerName> > <TTS_Vendor>.
15
Select the voices that were chosen during installation and click Edit
Node.
16
Ensure that the Language pull-down list is set to your locale, and edit
the other values as needed.
17
Click Submit.
To set the voice format

18
Click the <TTS_Vendor> node.
19
Click Edit Node.
20
Set the value for the Default Voice Format parameter as follows:
VOX_MULAW_8KHZUse this value for North America.
VOX_ALAW_8KHZUse this value for Europe.
21
Click Submit.
22
Restart WatchDog on the TTS machine for the changes to take effect.
Making Test Calls

The Speechify or RealSpeak Engine normally loads the voice fonts in
memory when the first TTS request is made. Loading the voice fonts takes
time and might result in the TTS request from the IPCS to time out.
Subsequent requests to the TTS Server should get processed within the
Deployment Guide
109
specified time out duration. Genesys recommends that you make at least
three calls to test the newly installed TTS Server.
110
Part
Voice Web Manager

Configuration
The chapter in Part 4 provides instructions for configuring the Voice Web
Manager. These procedures apply to either a Time Division Multiplexbased Voice Communications Server (VCS) or VoIP-based IP
Communications Server (IPCS) platform.
Part 4 contains one chapter:
Chapter 13, Voice Web Manager Configuration on page 113
Deployment Guide
111
Part 4: Voice Web Manager Configuration
112
Chapter
13
Voice Web Manager

Configuration
This chapter describes how to configure the VWM (Voice Web Manager)
components.
Setting Up VWM Databases, page 113

Configuring EventC, page 119
Configuring Unified Login Server, page 123
Configuring Reporter, page 125
Configuring Call Status Monitor, page 127
Configuring ASR Log Manager, page 128
Configuring ASR Log Server, page 129
Configuring Outbound Notification, page 131
Configuring Genesys Queue Adapter, page 133
Configuring VWCM, page 134
Testing the Installation, page 141
Setting Up VWM Databases

You can set up EventC databases in two ways depending on the number of
SQL Server machines.
Note: You must be experienced with database administration activities.
Deployment Guide
113
Chapter 13: Voice Web Manager Configuration
Databases on one machine
If this is a new install and all databases reside on the same machine, refer to
Setting Up VWM DatabaseSingle SQL Server on page 114.
Databases on multiple machines
If installing across multiple SQL Servers, refer to Setting Up VWM

DatabaseMultiple SQL Servers on page 115.
When running multiple EventCs in a network, the following configurations
are required:
Each EventC box has to have its own collector database. This database
cannot be shared across EventCs.
Only one EventC box can run Peak Calculator processes. Configuring
more than one EventC with Peak Calculator can cause unpredictable
results.
Only one Reporter and RepDWH database can be in the network.

Setting up a backup EventC is different from setting up other backup
components. You can install and configure a backup EventC, but it
wont run until its enabled. Either the primary or the backup can be
active at any point. You must disable EventC processes from running
by setting their Node Type to 1 in VWPS.
Setting Up VWM DatabaseSingle SQL Server

EventC Database Easy Install creates the databases and tables, and loads
startup information. You can use this procedure even if the databases have
already been created; however, all existing data will be lost.
Perform this setup if the VWAP databases reside on one SQL Server.
Note: For EventC upgrade instructions, refer to the
SQL_readme_6_5_4.txt file located in <Installation Drive>\SQLScripts
directory.
114
On the SQL Server, create a directory on the C drive called Cn.
From any machine that has VWM installed, copy the SQLScripts folder
from the <VWM Installation Drive>\Cn directory and place it in the
C:\Cn directory on the SQL Server machine.
Log onto the SQL Server as administrator.
Select the Master database.
Select Tools > SQL Query Analyzer.
Open the InstallParams_6_5_4.sql script from the

C:\Cn\SQLScripts\DefaultInstall\6.5.4 folder on the SQL Server
machine.
Check the configuration section, which contains the names of the

databases that will be created.
/*CONFIGURE HERE..
Below are the list of customizable parameters. Change
them if you need
Else default values as provided below will be used */
SELECT @ScriptRoot = 'C:\cn\SQLScripts' /*Root
directory where scripts are unpacked */
SELECT @CollectorDB = 'Collector'/*Name of Collector
Database */
SELECT @PeaksDB = 'Peaks'/*Name of Peaks Database */
SELECT @ReporterDB = 'Reporter'/*Name of Reporter
Database */
SELECT @RepDWHDB = 'RepDWH'/*Name of Reporter DWH
database */
SELECT @UnifiedLoginDB = 'UnifiedLogin'/*Name of
Unified Login database */
SELECT @ECVersion = '6.5.4'/*Do not edit this one */
/*CONFIGURE END*/
Make sure that the @ScriptRoot value is equal to the root directory
where the files are extracted.
Run the InstallParams_6_5_4.sql script by pressing F5.

This creates a DefaultInstall.sql file in the
C:\Cn\SQLScripts\DefaultInstall\6.5.4 directory.
10
From the Query Analyzer, open the DefaultInstall_6_5_4.sql file.
11
Run the DefaultInstall_6_5_4.sql script by pressing F5.

Note: Running this script takes a few minutes.
12
Check for database SQL server errors after the script completes.
Setting up the database is now complete. Go to the section Setting Up

Billing Port on page 119.
Setting Up VWM DatabaseMultiple SQL Servers

Perform this setup if the VWAP databases reside on multiple SQL Servers.
Deployment Guide
115
Note: For these setup instructions, VWPS will be used as the name of the
VWPS database.
Step 1On each SQL Server, create the following databases:
RepDWH
UnifiedLogin
Collector
Peaks
Reporter
Create the databases among multiple SQL Servers. Genesys recommends

UnifiedLogin, Reporter, and RepDWH on one database, and Collector and
Peaks on another database.
Step 2Navigate to the <ScriptRoot> directory:
EventC scripts are found under EventC/<Version> directory.

Reporter scripts are found under Reporter/<Version> directory.
UnifiedLogin scripts are found under UnifiedLogin/<Version>
directory.
Note: Run the scripts only for the required databases.
Step 3Run the Collector From Scratch script:
1
On the appropriate SQL Server, select the Collector database.
Open the Collector_from_scratch.sql from the UnifiedLogin directory.
Run the script by pressing F5.
Step 4Run the Peaks From Scratch script:

1
On the appropriate SQL Server, select the Peaks database.
Open the Peaks_from_scratch.sql from the EventC directory.
Step 5Run the UnifiedLogin From Scratch script:

1
116
On the appropriate SQL Server, select the UnifiedLogin database.
Note: The UnifiedLogin database should be on the same machine as

the VWPS database.
2
Open the UnifiedLogin_from_scratch.sql script from the EventC

directory.
Open the SetupAdminLogin.sql and run the script in the same database.
Step 6Run the Reporter From Scratch script:

1
On the appropriate SQL Server, select the Reporter database.
Open the Reporter_from_scratch.sql script from the EventC directory.
Before running the script, change VWPS to the name of the VWPS
database in the script.
Step 7Import data for the Collector database:

1
On the appropriate SQL Server, select the Collector database.
Right-click and select All tasks > Import Data.
Select the data source of the text file from the drop-down list provided.
Select the StateTransitions.csv file from the EventC directory.
Select the Delimited radio button.
Select the check box labeled First row has column names.
When prompted, use the appropriate delimiter (typically a semicolon).
Select the Use SQL Server Authentication radio button.
Enter the user name and password.
10
Complete the wizard and perform the importation.
Step 8Import data for the Reporter database:
Deployment Guide
117
Select the data source of the text file from the drop-down list
provided.
Select the lataareamap.csv file from the EventC directory.
Select Delimited.
Select Use SQL Server Authentication.
10
Step 9Open the RepDWH From Scratch script:

1
On the appropriate SQL Server, select the RepDWH database.
Open the RepDWH_from_scratch.sql script from the EventC directory.
Step 10Import data for the Peaks database:

1
On the appropriate SQL Server, select the Peaks database.
Select the data source of the text file from the drop-down list provided.
Select the peak_control.csv file from the EventC directory.
Select Delimited.
Select Use SQL Server Authentication.
10
Step 11Run the Reporter 6.5.4 script:
118
Open the Reporter_defs_6_5_4.sql script from the Reporter directory.
Configuring EventC
Repeat all of the substeps in Step 8Import data for the Reporter
database for the following files located in SQL Scripts\Reporter\6.5.4:
tlra_reports.csv
tlra_report_sqls.csv
tlra_report_display_table.csv
Setting up the EventC database is now complete.
Setting Up Billing Port

1
On the EventC machine, create directories named current and archives

under the (C or D):\Cn\data directory.
Select Start > Programs > Administrative Tools > Internet Services
Manager.
Right-click and select Server Name > New > Web Site.
In the wizard that appears, set the description to Billing Port, then click
Next.
Leave the IP Address as All Unassigned, and assign TCP/IP to port

9811, then click Next.
In the Path field, enter <VWM Installation Directory>\Cn\web\, then

click Next.
Allow Read and Run Scripts access, then click Next.
Click Finish.
Right-click on Billing Port and select Start to start the website.
Configuring EventC
1
Expand the nodes Event Collector > <ServerName>, then click

ConfigEventC.
Configure the parameters listed in Table 15 on page 120.

Note: SQL database names are case sensitive.
Deployment Guide
119
Configuring EventC
Table 15: EventC Parameters
Parameter
Description
Example Value
Source Directory
The physical directory where the billing

event files are posted by the Billing Port
c:\cn\Data\Current
Archive Directory
The physical directory where the billing

files are moved after they are processed
by the Events Loader
C:\cn\data\archives
Probe Dialer Customer ID
Dummy Customer for test calls
1001
Probe Dialer Application ID Dummy Application for test calls
1001
ReRouted Calls Customer

ID
Dummy Customer for test calls
1001
ReRouted Calls Application

ID
Dummy Application for test calls
1001
DLS Period Start Date

(GMT)
Daylight Savings Time
4/7/2003 8:00:00
DLS Period End Date

(GMT)
Daylight Savings Time
10/28/2003 7:59:59
Collector - Server Name
Fully Qualified Name of SQL Server

that has the Collector database
Sql.company.com
Collector - Database Name
Name of Collector database
Collector
Collector - Password
SQL Password
<blank>
Collector - UserID
SQL UserID
sa
Reporter - Server Name

that has the Reporter database
Sql.company.com
Reporter - Database Name
Name of Reporter database
Reporter
Reporter - Password
SQL Password
<blank>
Reporter - UserID
SQL UserID
sa
DataWareHouse - Server
Name

that has the Data Warehouse database
Sql.company.com
DataWareHouse - Database
Name
Name of the Data Warehouse database
RepDWH
DataWareHouse - Password
SQL Password
<blank>
120
Configuring EventC
Table 15: EventC Parameters (Continued)
Parameter
Description
Example Value
DataWareHouse - UserID
SQL UserID
sa
VWPS Server Name

that has the VWPS database. This is
created by the VWPS install.
Sql.company.com
VWPS - Database Name
Name of VWPS database. This is

created by the VWPS install.
VWPS
VWPS - Password
SQL Password
<blank>
VWPS UserID
SQL UserID
sa
Peaks Server Name

that has the Peaks database
Sql.company.com
Peaks - Database Name
Name of Peaks database
Peaks
Peaks - Password
SQL Password
<blank>
Peaks - UserID
SQL UserID
sa
Peaks Wait Time
Hours to wait before first Peaks process

starts
Peaks Addl Delay
Additional delay for subsequent

processes
15
Peak Execution Sequence
Execution sequence of peaks processes
PeaksNSP,PeaksReporter,Pea
ksAIM
Click Submit.
For each of the following processes, click Edit Node and make sure
that the default values for each process are acceptable. Edit the values
as needed.
a
CallRecsGenerator
Table 16: CallRecsGenerator Parameters
Deployment Guide
Parameter
Description
Example Value
Cycle Interval
The interval, in seconds,

between cycles
180
CRG Wait Time
The maximum time in hours to

wait for call completion
121
Configuring EventC
Table 16: CallRecsGenerator Parameters (Continued)
Parameter
Description
Example Value
Check DB Space
Checks databases for space

availability
Selected
Log Details
Detailed logging for debugging NO
EventsLoader
Table 17: EventsLoader Parameters
Parameter
Description
Example Value
Delimiter in Event
File
The delimiter in the event file
&
Cycle Interval

between cycles
180
Log Details
Detailed logging for debugging

in cycler
NO
EventsValidator
Table 18: EventsValidator Parameters
Parameter
Description
Example Value
Cycle Interval

between cycles
180
Log Details

in cycler
NO
PeaksAIM
Table 19: PeaksAIM Parameters
122
Parameter
Description
Example Value
Cycle Interval

between cycles
180
Log Details

in cycler
NO
Configuring Unified Login Server
PeaksNSP
Table 20: PeaksNSP Parameters
Parameter
Description
Example Value
Cycle Interval

between cycles
180
Log Details

in cycler
NO
PeaksReporter
Table 21: PeaksReporter Parameters
Parameter
Description
Example Value
Cycle Interval

between cycles
180
Log Details

in cycler
NO
Expand the node Events Collector >, click <ServerName>, then click
Notify Server.
Configuring the EventC is now complete.

Note: Once you start the events loader process, the events.asp file is
automatically updated.

Enabling Cookies
Deployment Guide
On the Login Server computer, ensure that cookies are enabled by

starting Internet Explorer, then selecting Tools > Internet Options >
Privacy tab and clicking Advanced.
Select the Override automatic cookie handling check box, and select
the Always allow session cookies check box.
123
Setting Up Unified Login Admin User

1
Open the SQL Query Analyzer, and login to the UnifiedLogin database.
In SQL Query Analyzer, type the following command:

Exec SetAdminUser VWPS
Press execute.
Note: This command is the Stored Procedure SetAdminUser
command. Provide the VWPS database name on the same machine as
the parameter:
The command sets and returns the user name, password, and company
name. Take note of this information because this will be the initial
administrator login for UnifiedLogin Server. You can rerun this
command any number of times to reset the administrator password.
Configuring Unified Login Server Settings

For each machine on which Unified Login Server is installed, the following
modifications are required for the Unified Login Server settings:
1
Expand the nodes Unified Login Server > <ComputerName>, then

click UnifiedLogin.

Table 22: Unified Login Server Parameters
Parameter
Description
Example Value
Login SQL Server Name
SQL Server alias name used to set up

client connections in Setting Up Client
Connections on page 19 for the Login
Server machine
vwm1
Login SQL Database Name
Database for UnifiedLogin in the

LoginSQLsvr
UnifiedLogin
Login SQL User Name
LoginSQLDB database username
sa
Login SQL Password
LoginSQLDB database password
<password>
124
Configuring Reporter
Table 22: Unified Login Server Parameters (Continued)
Parameter
Description
Example Value
VPN Addresses Start With
The starting number for all VPN IP

addresses in the network.
10
Public Domain Name for

Services
Domain under which the Unified Login

server and all its services exist. This is to
enable domain level cookies. This value
should be consistent with the domain
name in UnifiedLoginServer parameter.
This value should be a part of all service
URLs and should include the period
character (.) as the first character in the
sequence.
.domain.com
VPN Domain Name for

Services
Same as for Public Domain, but for

VPN.
.vpndomain.com
VWPS Database Name
Name of the VWPS database. This value

should be the same server as
UnifiedLogin database.
VWPS
Service ID for
Administration Utility
The Service ID for the administration

utility. Default is CONFIG1.
CONFIG1
For each machine on which Reporter is installed, modify the Reporter
settings as follows:
Deployment Guide
Expand the nodes Reporter > <ComputerName>, then click

Reporter.
Configure the parameters listed in Table 23 on page 126. Make sure

they are accurate, then click Submit.
125
Table 23: Reporter Database Connection Parameters
Parameter
Description
Example Value
Reporter SQL Server Name
Reporter SQL Server name. Use fully

qualified name.
sql.company.com
Reporter SQL Database

Name
Reporter SQL database name
Reporter
Reporter SQL Server User

Name
Reporter SQL Server user name
sa
Reporter SQL Server

Password
Reporter SQL Server password
<password>
VWPS SQL Server Name
SQL Server name where VWPS

database is installed
sql.company.com
VWPS SQL Database

Name
VWPS database name
VWPS
VWPS SQL Server User

Name
User name to access VWPS database
sa
VWPS SQL Server

Password
Password to access VWPS database
<password>
SSL Enabled on the Web

Server
Select this check box if SSL certificates

are installed and enabled on the web
server.
Name of NSP to show in

Reports
NSP name that appears at the top of the

left side tree for administrators and as
the browser title.
NSPName
Service ID for Reporter
Service ID for Reporter
RPT1
Database Software Used
Database software used for storing data.

Only value allowed is MSSQL. For
future use.
For future use.
126
Configuring Call Status Monitor
Configuring Call Status Monitor

Prerequisites
The following prerequisites are required before configuring Call Status
Monitor (CSM):
At least one real application is properly provisioned in VWPS, other

than the one you created as dummy in EventC prerequisites.
Policy Manager (PM) has been started and is running successfully for at
least one customer/one application.
Configuring CSM Settings

For each machine on which CSM is installed, modify the CSM settings as
follows:
1
Expand the nodes Call Status Monitor > <ComputerName>, then

click Call Status Monitor.
Configure the parameters in Table 24. Make sure they are accurate, then
click Submit.
Table 24: Call Status Monitor Parameters
Parameter
Description
Example Value
VWPS SQL Server Name
VWPS SQL Server name. Use fully

qualified name.
sql.company.com
VWPS SQL Database Name VWPS SQL database name
VWPS
VWPS SQL Server User

Name
VWPS SQL Server user name
sa
VWPS SQL Server

Password
VWPS SQL Server password
<password>
SSL Enabled on the Web

Server
Select this check box if SSL certificates

are installed and enabled on the web
server.
PM Web Server Port
Port on which Policy Manager listens
Deployment Guide
9810
127
Configuring ASR Log Manager
Table 24: Call Status Monitor Parameters (Continued)
Parameter
Description
Example Value
Name of NSP to show in

Reports
NSP name that appears at the top of the

left side tree for administrators and as
the browser title
NSPName
Service ID for Call Status

Monitor
Service ID for CSM
CSM1
Configuring ASR Log Manager

You must have already created the ASRTeleServers group before
configuring the ASR Log Manager. Refer to the applicable ASR vendor
chapter in this guide for instructions on creating ASR groups.
1
Expand the nodes ASR Log Manager >

<ASRLogManagerComputer>, then click LogMgr.

Table 25: ASR Log Manager Parameters
Parameter
Description
Example
Start time for data transfer
The time of day that the ASR Log

Server initiates transfers.
17:00
Duration between
consecutive transfers in sec
How often the ASR Log Server initiates

transfers.
86400
Log Server URL
FTP address of ASR Log Server

computer.
ftp://asrls.company.com
BWM URL
The fully qualified name of the Band

Width Manager computer, which runs
on port 9810. Replace the computer
name only; leave webnotify.asp? and
everything after it as is.
http://
bwm.compnay.com:9810/
webnotify.asp?notifyprocess
=bwm1&customer=ASRLog
Manager
Group List
The name(s) of the group(s) created

above. Separate the group names with a
semicolon.
ASRTeleServers
128
Configuring ASR Log Server
Creating DSN for ASR Log Manager

1
On the VWM computer on which the ASR Log Manager is installed, go

to Settings > Control Panel > Administrative Tools > Data Sources.
Select System DSN.
Click Add.
From the Driver list, select Microsoft Access Driver.
Click Finish.
In the ODBC Microsoft Access Setup Window, set the following:
Data Source Namelogmgr
DescriptionLog Manager Database
Select Select Database.
Select <VWM Installation Drive>:\cn\data\logmgr.mdb.
Click OK to save and exit.

1
Expand the nodes ASR Log Server > <ASRLogServerComputer> >

Scheduler >, then click ASRLogServer.
Click Edit Node.
In the ASRLogServer section, configure the parameters listed in Table

26.
Table 26: ASR Log Server Parameters
Parameter
Description
Example
Task Frequency
How often the ASR Log Server

initiates transfers.
24:00:00
Task Start Time
The time of day that the ASR Log

Server initiates transfers.
17:00
Task Priority
Priority at which this task is run by the

Scheduler.
Low
Deployment Guide
129
Table 26: ASR Log Server Parameters (Continued)
Parameter
Description
Example
Service ID
Service ID of the ASR Log Server.

Using the default value is acceptable.
LOGMGR1
vwpsurl
The fully qualified name of the VWPS

computer. Replace the computer name
only; leave webnotify.asp? and
everything after it as is.
http://vwps.company.com/
webnotify.asp?notifyprocess=vwp
s
Note: In order for all wave files to transfer successfully, Genesys

recommends having a time difference of at least 8-hours between the
ASR Log Manager start time for data transfer and the ASR Log Server
task start time.
5
Click Submit.
Expand the nodes ASR Log Server > <ASRLogServerComputer> >

Scheduler > ASRLogServer, then click SpeechWorksOSR.
Click Edit Node.
Configure the parameters listed in Table 27.

Table 27: Server Parameters
Parameter
Description
Example
Pattern specifying start of

log capture
This pattern specifies the start of ASR log

capture in the ASR log file.
EVNT=SWIclst
Pattern specifying end of

log capture
This pattern specifies the end of ASR log

capture in the ASR log file.
EVNT=SWIclnd

application name
This pattern specifies the start of the

application name for which this ASR capture
belongs.
SVNM=
Delimiter that specifies the

end of application name
This pattern specifies the end of the application

name.

utterance file name
This pattern specifies the start of the log file

name where the utterance was captured.
WVNM=

end of the utterance log file
name
This pattern specifies the end of the utterance

log file name.
130
Configuring Outbound Notification
Table 27: Server Parameters (Continued)
Parameter
Description
Example
Pattern specifying the start

of channel number on which
this capture was done
This pattern specifies the start of channel

number on which this capture was done.
|CHAN=

end of the channel number
This pattern specifies the end of the channel

number.
Click Submit.
10
On the ASR Log Server computer, select Start > Programs >
Administrative Tools > Internet Services Manager.
11
Expand the IIS server, select Default FTP Site, then right-click on it.
12
Select Properties > Home Directory tab.
13
Enter a home directory in the Local Path field.

Note: Genesys recommends that you use c:\inetpub\ftproot for the
home directory.
The ASR Log Server moves everything in this directory to individual
customer folders. Make sure that there are only ASR log files in this
directory.
14
Select the Write check box.
15
Click OK.
You are done configuring ASR Log Server.

Note: The configuration instructions in this section are only required if
you are using Outbound Notification on your VWAP system.
Creating DSN for Service Access Point
Deployment Guide
On the VWM computer on which the ASR Log Server is installed, go to

Settings > Control Panel > Administrative Tools > Data Sources.
Select System DSN.
131
Click Add.
From the Driver list, select Microsoft Access Driver.
Click Finish.
In the ODBC Microsoft Access Setup Window, set the following:
Data Source Namesapdb
DescriptionService Access Point Database
Select Select Database.
Select <VWM Installation

Drive>:\cn\data\NotificationQueueDatabase.mdb.
Click OK to save and exit.
Creating ORL Groups

1
Enter a descriptive name for the ORL Server in the Group Name field.
Select Outbound VCS from the Group Type drop-down list.
Add all of the VCSs that are designated as Outbound Notification

Servers to the group.
Click Submit.
The ORL group has been created.
Configuring Groups on ORL Server
132
Expand the Outbound Resource Locator node.
Expand the link of the Server that you wish to configure.
Click the ORL node.
Click Edit Node.
Select the desired ORL group and click Add.
Click Submit.
Configuring Genesys Queue Adapter
Configuring PopGateway1 Process on SAP Server

1
Expand the Service Access Point node.
Expand the link of the SAP Server that you wish to configure.
Click the PopGateway1 Process link under the SAP Server link.
Click Edit Node.
In the Primary Outbound DID Mapper field, enter the SAP URL as
follows:
<dispenser-machine>/$customername$_$application_name$_OutboundDID.xml
Note: When entering the SAP URL, make sure that the exact URL as
shown above is used. The only variable in the URL is the <dispensermachine>.
Click Submit.
The PopGateway1 process has been configured for that SAP Server.
Configuring Genesys Queue Adapter

The Genesys Queue Adapter (GQA) must have an IVR Server with which
to communicate. The IVR Server must be created as a server in VWPS.
Creating the IVR Server

Adding IVR Server
1
In VWPS, click Servers.
Click IServer in the left frame, then click Add New Server.
Warning! Do not use the name of an existing VWAP machine. Doing
so will overwrite the existing LDAP template.
Deployment Guide
Enter the fully qualified name of the IVR Server.
Click Browse.
133
Configuring VWCM
Select the IServerInstance.csv from the <VWM Installation Drive>/Cn/

config folder.
Click Submit.
Importing IVR Server Template

1
Select the server you just added in Adding IVR Server on page 133.
Click Edit.
In the Server Version field, take note of the version number.
From the VWPS top menu, click Templates.
Click ISVR in the left frame, then click Import Template File.
In the Template Version field, enter the version number noted from
Step 3.
Click Browse.
Select the IServerTemplate.csv file from the <VWM Installation

Drive>/Cn/config folder.
10
Click Submit.
Configuring VWCM
The procedures in this section apply for an IPCS installation.
These are the VWCM components:
Resource Manager
SIP Session Manager (SSM)
H.323 Session Manager
Typically either the SSM or the H.323 Session Manager is installed, but not
both.
Setting Up the Database

Before configuring the Resource Manager, SSM, and H.323 Session
Manager, you must set up a database on the SQL Server. Make sure the
clock on this server is synchronized with the VWCM server.
134
Configuring VWCM
To set up the database for Resource Manager and SSM:

1
On the appropriate SQL Server, select Master database.
From the VWAP CD, solution_specific\VWCM\Database Scripts

directory, open SipSessionMgr.sql.
Run SipSessionMgr.sql script by pressing F5.
Open StoredProcedureSSM.sql and run the script by pressing F5.
Open ResourceMgr.sql and run the script by pressing F5.
Open StoredProcedureRM.sql and run the script by pressing F5.
To set up the database for Resource Manager and H323 Session Manager:
1
On the appropriate SQL Server, select Master database.
From the VWAP CD, solution_specific\VWCM\Database Scripts

directory, open ResourceMgr.sql.
Open StoredProcedureRM.sql and run the script by pressing F5.
Provisioning Media Gateway

Adding Servers
1
Click Media Gateways, then click Add New Server. The Add New
Server page opens.
Warning! Do not use the name of an existing VWAP machine. Doing
so will overwrite the existing LDAP template.
Deployment Guide
In the New Server Name field, enter a fully qualified name for the
server that is configured in the DNS.
Click Browse and from the VWAP CD, solution_specific\VWCM\

MediaGateways CSV directory select MGInstance.csv.
Click Submit.
Repeat Steps 15 for each Media Gateway.
135
Configuring VWCM
Importing Template
You only need to import a template once. If additional Media Gateways are
added later, they will use the existing template.
1
Select the server you just added in Adding Servers on page 135.
Click Edit.
In the Server Version field, take note of the version number.
From the VWPS top menu, click Templates.
Click MG in the left frame, then click Import Template File.
In the Template Version field, enter the version number noted from
Step 3.
Click Browse and from the VWAP CD, solution_specific\VWCM\

MediaGateways CSV directory, select MGTemplate.csv.
Click Submit.
Configuring Media Gateway

1
Expand the nodes Media Gateways > <first server>, then click the
Device node.
Click Edit Node. The Servers Configuration page opens.

Note: Clicking in a parameter field opens a help window that contains
a description of the field, data type, range, and default information.

Table 28: Media Gateway Device Parameters
136
Parameter
Description
Example
Name of
Media
Gateway
A name for the device
MediaGateway1
IP address for
this device
The numeric IP address, not fully qualified

name
10.10.10.10
Configuring VWCM
Table 28: Media Gateway Device Parameters
Parameter
Description
Example
Port for this

device
The TCP/IP port that signalling is provided

on.
SIP default is 5060.
H323 default is 1720.
5060
Number of
Ports
The number of ports the device has

accommodated
100
Port Type
Inbound, Outbound or both
InOut
Provider
The name of the service provider.
ATT
Creating Media Gateway Groups

1
Click the Click to add a group link.
Create a new Group named MediaGateways.
Select MG from the Group Type drop-down list.
From the Available Servers list, select the MediaGateways to be

assigned to the group, and click Add.
Click Submit.
Configuring Resource Manager
Deployment Guide
Expand the nodes Resource Manager > <VWCM Computer>, then

click ResourceManager.
Configure the parameters listed in Table 29 on page 138, then click

Submit.
137
Configuring VWCM

Table 29: Resource Manager Parameters
Parameter
Description
Example
Database User ID
The login ID for the database
sa
Database
Password
The password for the database, if any
<blank>
Primary database
IP address
The IP address, not fully qualified name, of the primary

database server
10.10.10.10
Backup database
IP address
The IP address, not fully qualified name, of the backup

database server, if any
10.10.10.10
Database Name
The name of the Resource Manager database
Resource
Manager
SIP listening IP
address
The IP address that is used to listen for SIP messages
10.10.10.1
SIP listening port
The TCP/IP port number on the Resource Manager that listens

for SIP messages
5070
Media Gateway
Server Group(s)
The name of the group (or groups) of Media Gateways that this
Resource Manager provides services to
MediaGateways
Configuring SSM
138
Expand the nodes SIP Session Manager > <VWCM Computer>, then
click SIPSessionManager.
Configure the parameters listed in Table 30 on page 139, then click

Submit.
Configuring VWCM

Table 30: SSM Parameters
Parameter
Description
Example
Database User
ID
The login ID for the database.
sa
Database
Password
The password for the database, if any.
<blank>
Primary
database IP
address
The IP address, not fully qualified name, of the

primary database server.
10.10.10.10
Backup
database IP
address
The IP address, not fully qualified name, of the

backup database server, if any.
10.10.10.10
Database Name
The name of the SSM database.
SIPSessionManager
SIP listening IP
address
The IP address that is used to listen for SIP

messages.
10.10.10.1
SIP listening
port
The TCP/IP port number that listens for SIP

messages.
5060
Resource
Manager IP
Address and
Port
The IP address and TCP/IP port of the Resource

Manager.
10.10.10.10:5070
Fault Tolerance
A flag to enable/disable fault tolerance.
Selected
Primary DID
URL
The http address of the dispenser.
http://<Dispenser Fully Qualified

Domain Name>/
Backup DID
URL
The http address of the backup dispenser, if any.
http://<Backup Dispenser Fully

Qualified Domain Name>/
Softswitch IP
address and port
SIP IP address and signaling port of the

softswitch.
10.10.10.10:5080
Backup
softswitch SIP
IP address and
port
SIP IP address and port for outbound calls when

the primary softswitch fails
10.10.10.10:5090
Deployment Guide
139
Configuring VWCM
Note: To change the default SIP configuration, update the support and
siplisteneripaddress attributes. If the machine has more than one NIC
interface, specify which interface the SSM should listen to by setting the
siplisteneripaddress attribute.
Configuring H.323 Session Manager

1
Expand the nodes H.323 Session Manager> <VWMComputer>, then

click H.323SessionManager.

Table 31: H.323 Session Manager Parameters
Parameter
Description
Example
SIP Listening IP
Address
IP address that is used to listen to SIP messages.
10.10.10.10
SIP Listening
Port
The network port that is used to listen to SIP

messages.
5060
Resource
Manager IP
Address
IP address and port of the Resource Manager
10.10.10.10:5070
Primary DID
URL
The http address of the dispenser.
http://<hostname>/
Backup DID
URL
The http address of the backup dispenser, if any.
http://<hostname>/
ISDN
Numbering
Type
ISDN numbering type that the PSTN network

supports.
International
Primary
Gatekeeper IP
Address
IP address and port of the primary gatekeeper.
10.10.30.105:1720
140
Testing the Installation
Table 31: H.323 Session Manager Parameters (Continued)
Parameter
Description
Example
Backup
Gatekeeper IP
Address
IP address and port of the backup gatekeeper, if

any.
10.10.30.100:1720
Enable RAS
Messages
Flag to indicate if RAS messages should be used

to communicate with the gatekeeper.
Select this check box if required.
H.323 Listening
IP Address
IP address that is used to listen to H.323

messages.
10.10.10.10
H.323 Listening
Port
The network port that is used to listen to H.323

messages.
1720

To test the installation, it is necessary to create a reseller, customer, and
application.
1
Log in to VWPS.
Click Resellers/Customers/Applications, then click Add Reseller.
Create a reseller with a logical name that represents the Service

Provider. Make sure of the following:
The Reseller is Parent NSP check box is selected.
The GMT offset and additional daylight savings offset is correct.

This will affect Reporter views.
Under this reseller, click New Customer.
Create a customer with a logical name such as NSPAdmin. This is the

name used for the initial administration login in Unified Login, and this
is the customer you use for Test Calls configuration in EventC. Make
sure of the following:
The NSP Customer check box is selected.
Provision this customer. At a minimum, the customer should have a

primary Policy Manager selected.
Note: If VWPS indicates that it failed to notify the server, disregard
this message. The message occurs because WatchDog is not running.
Deployment Guide
Under this customer, click New Application.
141
Create an application for test calls, which may be called Dummy App.
You cannot provision the application until the Policy Manager is
installed.
Take note of the IDs and Names of the reseller, customer, and
applications created. This is required for configuring EventC and
Unified Login.
10
After this creation, check the VWPS database and verify that the
resellers, customers, applications, and servers tables have the
information that was created in VWPS. This is a critical requirement for
EventC and Unified Login to function.
Note: For instructions on how to use VWPS, refer to the Voice Web
Application Platform 6.5 Operations and Provisioning Guide.
142
Appendix
Miscellaneous
Configurations and
Troubleshooting
This appendix contains additional configuring, troubleshooting, and
uninstalling information.
This appendix has these sections:
Disabling the F1 Boot, page 143

Groundstart Configurations with Dialogic on VCS, page 144
Open Speech Dialog Modules, page 152
Sun ONE Software, page 152
Troubleshooting VWPS Installation, page 162
Troubleshooting the SQL Server, page 165
Troubleshooting VCS, page 167
Uninstalling Dialogic Software, page 167
Disabling the F1 Boot

Since operators normally access the VCS remotely, they cannot actually
press any keys. If certain problems occur during startup, it is necessary to
press the F1 key to continue booting the computer. Therefore, you must
disable the F1 boot function so operators can remotely boot the computer.
1
Deployment Guide
Reboot the computer and press F10 to access system configuration

during the reboot.
143
Appendix : Miscellaneous Configurations and Troubleshooting
Groundstart Configurations with Dialogic on VCS
In the Main Menu, access the Advanced Mode.
Select Configure Hardware.
Wait approximately 1015 seconds for hardware detection.
Select Review or Modify Hardware Settings.
Under Advanced Features, select F1 Boot Prompt.
Select Disable - Skip Prompt and press Enter.
Press F10 to save the changes.
Restart the computer.
Groundstart Configurations
with Dialogic on VCS
The following changes should be made on every VCS only if groundstart
protocol is being used on T1 RobbedBit.
The PDK.CFG file on each VCS using groundstart protocol on T1
RobbedBit should appear as below:
PDK.CFG
board 0 fcdfile ml2_dsa_cas.fcd pcdfile ml2_dsa_cas.pcd variant
pdk_us_ls_fxs_io.cdp
The pdk_us_ls_fxs_io.cdp file on each VCS using groundstart protocol on
T1 RobbedBit must be configured with the feature parameters required for
your configuration and environment. VWAP supports the following
features:
DNIS and ANI after start

CPA after answer for Network Announcements
CPA after answer for Group3 Fax
CPA after answer for Busy
CPA after answer for Ring No Answer
CPA after answer for voice
Label Routing
The below file illustrates the use of these various feature parameters, and is
to be used as a reference only. Be sure to use the feature parameters that
apply to your configuration and environment. Consult the Dialogic Product
Manuals for additional information.
pdk_us_ls_fxs_io.cdp
144
/**
%full_filespec: pdk_us_ls_fxs_io.cdp-10:ascii:gc#1 %
******************************************************
FILE : PDK_US_LS_FXS_IO.CDP
USES : PDK_US_LS_FXS_IO.PSI
COUNTRY : T1 FXS
PROTOCOL: Inbound + Outbound
*******************************************************
This is a CDP file is to be used with the US loop-start FXS protocol. It
provides only the voice mail side execution of the protocol. The FXOFXS protocol is asymmetrical, and may only interface with a line
running an FXO (PBX) side of the protocol.
ALL CAS_SIGNAL_TRANS_t CDP_TRANS = ABCD, ABCD,
PreInterval,PostInterval,
PreIntervalNominal,PostIntervalNominal
ALL PATTERN_PULSE CDP_PULSE = OffCode<ABCD>,
OnCode<ABCD>,
PreInterval,PostInterval,
PreIntervalNominal,PostIntervalNominal,
m_PulseIntervalMin,m_PulseIntervalNominal,
m_PulseIntervalMax
*/
/* FXS protocol supports and requires following features:*/
ALL Charstring_t Sys_features = Feature_Inbound,
Feature_Outbound, Feature_Transfer,Feature_Hold,
Feature_Drop_On_Hold
DM3 INTEGER_t SYS_LineTypeT1 = 1
/*
This PSL parameter informs the PDK engine that protocol requires call
progress (pre-connect call analysis).
Possible values:
0 = ALWAYS-OFF (disable)
1 = PREFERRED (always use - protocol requires)
2 = PASS-THROUGH (use if requested by application, i.e., control is
passed-through to application)
*/
R4 INTEGER_t PSL_MakeCall_CallProgress = 1
DM3 INTEGER_t PSL_CACallProgressOverride = 1
Deployment Guide
145
/*
This PSL parameter informs the PDK engine that protocol requires
media detection (post-connect call analysis).
Possible values:
1 = PREFERRED (always use - protocol requires)
2 = PASS-THROUGH (use if requested by application, i.e., control is
passed-through to application)
*/
R4 INTEGER_t PSL_MakeCall_MediaDetect = 2
DM3 INTEGER_t PSL_CAMediaDetectOverride = 2
/*
Set this value to true(1) to have the FXS transition to Accepted state
immediately upon receiving an accept call command and thus ignore
the number of rings parameter. The current default is false (0) to be
consistent with ICAPI, thereby waiting for the specified number of
rings before transitioning to Accepted state.
*/
ALL BOOLEAN_t CDP_IMMEDIATE_ACCEPTSTATE = 0
/*
This parameter controls when the protocol will send up
GCEV_ALERTING/GCEV_CONNECTED event to the application. If
set to 0, GCEV_ALERTING is sent, when ring back is detected, and
GCEV_CONNECTED is sent when the call is connected. If set to 1,
GCEV_ALERTING is sent when
After dialing is completed if CPA is disabled, or
After dialing is initiated if CPA is enabled.

However, if CPA is disabled and CDP_PBXAnswerEnabled is also
disabled, then GCEV_CONNECTED will be sent after dialing instead
of GCEV_ALERTING, for the protocol would not be able to reach the
connected state otherwise.
All BOOLEAN_t CDP_Send_Alerting_Or_Connected_After_Dial
=1
/*
Set this value to true (1) to have the FXS wait for dial tone prior to
dialing.
Note this parameter does NOT apply to supervised transfers
(consultation calls) in which case dial tone is not verified.
*/
ALL BOOLEAN_t CDP_WaitDialToneEnabled = 1
146
/* Set this value to true (1) to have the FXS connect on positive media
detection, i.e., voice, fax, modem, etc. */
ALL BOOLEAN_t CDP_CONNECT_UPON_MEDIA = 1
/* Set this value to true (1) to have the FXS connects on call analysis
result of no ringback (remote collision). */
ALL BOOLEAN_t CDP_ConnectOnNoRingBack = 1
/* Set this value to true (1) to have the FXS connects on call analysis
result of no dialtone (local collision). */
ALL BOOLEAN_t CDP_ConnectOnNoDialTone = 1
/*
Define the dial tone detection for a dual-tone of 440Hz+480Hz on for at
least 1 sec.
Dial tone detection is only active if the prior parameter is enabled.
TONE_t format = Freq 1, Freq 1 Dev, Freq 2, Freq 2 Dev, Amp 1, Amp
2, On Time,
On Time Dev, Off Time, Off Time Dev, Mode (1 for Edge Detection, 0
for Cadence Detection), Repeat Count
*/
ALL TONE_t TONE_DIAL = 350,50,440,50,0,0,0,0,0,0,1,1
/* Define the ring tone detection */
ALL TONE_t TONE_RINGBACK =
440,65,480,65,0,0,1000,100,0,0,1,1
/* Define the dial tone timeout (msec). Used only when
CDP_WaitForDialTone is enabled. */
ALL INTEGER_t CDP_DialToneWaitTime = 5000
/*
Define the intentional delay (msec) for going onhook prior to making a
call before gc_WaitCall is ever called.
*/
ALL INTEGER_t CDP_OnhookDuration = 2000
/*
Define the intentional delay (msec) after the offhook prior to dialing
digits.
This is used primarily in scenarios when CDP_WaitDialToneEnabled is
disabled (zero).
*/
ALL INTEGER_t CDP_PostOffhookDelay = 0
/* Define timeout (msec) to determine whether PBX has hung-up. */
ALL INTEGER_t CDP_MinPBXHangupTime = 6000
Deployment Guide
147
/*
Define the intentional delay (msec) after the blind transfer hookflash
and the start of dialing. Note this should not be necessary assuming the
wait for dialtone parameter, CDP_WaitDialToneEnabled, is enabled.
*/
ALL INTEGER_t CDP_BTPreDialDelay = 1000
/* Define the intentional delay (msec) before hanging up after dialing
on a blind transfer. */
ALL INTEGER_t CDP_BTPostDialDelay = 500
/* This parameter sets the hookswitch state upon opening the device:
0:= ONHOOK, 1:= OFF_HOOK */
ALL BOOLEAN_t CDP_ProtocolStartsOffhook = 1
/* This parameter sets the hookswitch state on protocol completion: 0:=
ONHOOK, 1:= OFF_HOOK */
ALL BOOLEAN_t CDP_ProtocolStopsOffhook = 0
/* This parameter indicates an off-hook (outbound seize) from the
voicemail side (local) on the line. */
ALL CAS_SIGNAL_TRANS_t CAS_OFFHOOK =
xxxx,11xx,50,50,0,80
/* This parameter indicates an on-hook (idle) from the voicemail side
(local) on the line. */
ALL CAS_SIGNAL_TRANS_t CAS_ONHOOK =
xxxx,01xx,50,50,0,80
/* This parameter identifies the CAS pattern that indicates the PBX
applied a ring signal (inbound seize) on the line. */
ALL CAS_SIGNAL_TRANS_t CAS_RING_APPLIED =
01xx,00xx,50,50,80,80
/* This parameter identifies the CAS pattern that indicates the PBX
applied a ring signal (inbound seize) on the line. */
ALL CAS_SIGNAL_TRANS_t CAS_RING_STOPPED =
00xx,01xx,50,50,80,80
/* This parameter identifies the CAS pattern for a hookflash on the line.
*/
ALL CAS_SIGNAL_PULSE_t CAS_HOOKFLASH =
11xx,01xx,50,50,80,80,450,500,550
/*
This parameter permits the remote PBX to initiate transitioning to the
connected state with an answer signal. However, any PBX answer
signal is ignored if call progress is mandated in the make call.
148
*/
ALL BOOLEAN_t CDP_PBXAnswerEnabled = 1
/* This pattern indicates that the remote PBX has answered. */
ALL CAS_SIGNAL_TRANS_t CAS_PBX_ANSWER =
11xx,01xx,50,50,80,80
/* Enabling this parameter permits the remote PBX to initiate
disconnects. */
ALL BOOLEAN_t CDP_PBXDiscEnabled = 1
/* This pattern indicates that the remote PBX has disconnected. */
ALL CAS_SIGNAL_TRANS_t CAS_PBX_DISC =
0xxx,1xxx,50,600,0,80
/*
This parameter permits the protocol to bypass signaling a hookflash
when dropping a consultation call. It should be enabled only in the case
when all consultation calls are assumed to initiate the disconnect. When
enabled, no hookflash CAS signaling is sent and only state changes are
delivered to the application. (Normally this parameter should be
disabled and set to zero.)
*/
ALL BOOLEAN_t CDP_BypassHookflashOnConsultationDrop =
0
/*
This parameter permits the protocol to bypass signaling a hookflash
when initiating either a supervised or unsupervised transfer via
gc_SetupTransfer( ) or gc_BlindTransfer( ) respectively. It is currently
a temporary customized feature and should be normally disabled and set
to zero. When enabled, no hookflash CAS signaling is issued and only
applicable state changes are delivered to the application.
*/
ALL BOOLEAN_t CDP_BypassHookflashOnTransfer = 0
/* These three tone templates define the DTMF tones used for support
of disconnect supervision: */
ALL TONE_t TONE_DISCONNECTDIAL =
350,50,440,50,0,0,1000,-1000,0,0,1,0
ALL TONE_t TONE_DISCONNECTREORDER =
480,50,620,50,0,0,250,50,250,50,1,4
ALL TONE_t TONE_DISCONNECTBUSY =
480,50,620,50,0,0,500,50,500,50,1,4
/*
Following tone templates define the default Call Progress tones used:
Deployment Guide
149
Note: Do not uncomment unless non-US call progress tones are used
by switch (FXO).
R4 TONE_t PSL_TONE_CP_DIAL_LCL =
350,50,440,50,0,0,0,0,0,0,1,0
R4 TONE_t PSL_TONE_CP_RNGBK1 =
440,65,480,65,0,0,1000,100,3000,300,1,0
R4 TONE_t PSL_TONE_CP_BUSY1 =
480,50,620,60,0,0,500,50,500,50,1,4
*/
/*
***********************************************
DM3 Parameters
***********************************************
*/
DM3 INTEGER_t PSL_VariantId = 9
/* PSL_VendorId: (REQUIRED) Identifies the vendor of the protocol,
this Id is assigned by Dialogic to the vendor */
DM3 INTEGER_t PSL_VendorId = 0x10001
/* PSL_ProtocolId: (REQUIRED) Vendor assigned Id, which identifies
a vendors protocol. */
DM3 INTEGER_t PSL_ProtocolId = 0x1001d
/* PSL_Version: (REQUIRED) Identifies version of the protocol.
Maintained by vendor but must be in the standard Dialogic versioning
format.
The combination of VendorId, ProtocolId, and Version uniquely
identifies a protocol.
The following describes the format.
*/
150
/*
---Type: 0=Prod, 1=Beta, 2=Alpha, 3=Exp
| -----Major Number
|| -----Minor Number
|| | -----Beta Number
|| | | -----Alpha Number
|| | | |
vv v v v */
DM3 INTEGER_t PSL_Version = 0x00300000

/*
PSL_CompatibilityMask: A bit mask of the Version value it determines
compatibility between protocol and cdp files. The value used when
building the protocol will determine which cdp variant are considered to
be compatible. The value supplied by the variant will determine which
protocol build is acceptable. The combination of the stored and supplied
masks will determine if a match is found */
/*
---Type: 0=Prod, 1=Beta, 2=Alpha, 3=Exp
| -----Major Number
|| -----Minor Number
|| | -----Beta Number
|| | | -----Alpha Number
|| | | |
vv v v v */
DM3 INTEGER_t PSL_CompatibilityMask = 0xfffff000

/* sys_ProtocolName (REQUIRED) Vendor assigned Id that identifies
auxiliary files. */
DM3 CHARSTRING_t SYS_ProtocolName = pdk_us_ls_fxs_io
/* sys_VariantName (OPTIONAL) Differentiates between variants
using the same base protocol. */
DM3 CHARSTRING_t SYS_VariantName = t1_fx_io
/* sys_i960HotFile (REQUIRED) Protocol object file to use with this
CDP file. */
DM3 CHARSTRING_t sys_i960HotFile = pdk_us_ls_fxs_io.hot
/*
*********************************************************
***********
END OF FILE
*********************************************************
***********
*/
Deployment Guide
151
Open Speech Dialog Modules
Open Speech Dialog Modules

ScanSoft recommends caching to run with Open Speech Dialog Modules
(OSDM).
To use OSDM, currently it is required to have the wininet caching turned
on in Page Collector for better performance.
To use the wininet caching:
1
Log into VWPS, then click the VCS server node that needs to be
modified.
Click Pagecollector.
Add a new attribute/value pair as usecninet to 0.
Add a new attribute/value pair as cachemode to 1.

Note: You can specify either partial caching, which is 2, or full
caching, which is 1.
Click Submit and then restart WatchDog on the VCS.
Sun ONE Software

Reinstalling/Repairing an Existing Installation
The following steps outline the procedure to repair or modify an existing
installation. These instructions do not apply to upgrading to a new version
of Sun ONE Directory Server. The same version of software is installed to
correct/repair an existing installation.
Software Requirements
These instructions apply to the following versions of Sun ONE Directory
Server:
Sun ONE Directory Server 5.1 SP2 (recommended)

Sun ONE Directory Server 5.1 SP1, 5.1 and 5.0
152
Sun ONE Software
Backing Up Existing Directory Server Data and

Configuration
1
Back up the relevant directory root node(s)/root suffix(es). For

example, genesys.net.
Copy the LDIF file to a safe locationnot under the same folder where
Sun ONE is installed.
If there is already a full directory backup or an exported LDIF file, they

can also be used if it is not possible to create a backup in this step. If it
is possible to take a backup at this point, then it should be taken and
usedthis will ensure that all the latest data is preserved.
Installing the Software Again

Reinstall the Sun ONE software on top of the existing software. It should
detect that it is being installed over an existing version. Select all of the
default values and restart the machine once the software is installed.
Restoring Backed Up Data and Configuration

1
Make sure that 50Telera.ldif file is present in the folder C:\Sun

ONE\Servers\slapd-(machinename)\config\schema.
If it is not present, copy the file to this folder and restart the Sun ONE
services as described in Restarting Directory Server Services on page
158.
Login to the directory server as described in Logging In to Sun ONE

Administration Console on page 154. Check for data.
If the data is not present, restore as described in Restoring Data in a
Single Root Suffix on page 157.
Under the root node in the directory, check for the ACI count and
content. This count should be eight (8) and ACIs should match with
Genesys ACI. If there is a discrepancy, reinstall VWPS. Reinstalling
VWPS will make sure that the correct ACL is in place.
Upgrading to a New Version

Instructions for upgrading from different source and target versions are
different. Find the instructions that match your versions and follow them
appropriately.
Deployment Guide
153
Sun ONE Software
Upgrading Version 5.0, 5.0 SP1, 5.0 SP2 to 5.1

This upgrade consists of making an LDIF export, uninstalling the old
version completely, installing the new version, and then restoring data and
configuration completely.
1
Make a complete backup of the directory server as described in

Backing Up/Exporting Data in a Single Root Suffix on page 155, and
keep it in a safe place.
Backup the data of relevant root suffixes as described in Restoring the

Entire Directory Server on page 156. If there are multiple rootsuffixes, backup each suffixs data in a different file. Copy the files to a
safe location.
Completely uninstall the Sun ONE directory server from your machine
as described in Completely Uninstalling Directory Server Software
on page 157.
Install the new version of the directory server according to fresh

installation instructions.
Make sure that 50Telera.ldif file is present in the folder C:\Sun

ONE\Servers\slapd-(machinename)\Config\Schema\.
If it is not present, copy it to this location from the Installation CD and
restart services as described in Restarting Directory Server Services
on page 158.
Restore data backup as described Restoring Data in a Single Root

Suffix on page 157.
Check for ACIs under the root suffix. If they are absent or do not match
what the VWPS installation added, reinstall VWPS. This ensures that
all ACIs are in place and accurate.
Common Tasks
This section outlines some commonly encountered tasks while working
with Sun ONE Directory Server.
Logging In to Sun ONE Administration Console

Sun ONE Administration Console is used to administer the directory
server. It is accessible from only the local machine where it is installed.
1
154
Select Start > Programs > Sun ONE Server Products > Sun ONE
Console.
Sun ONE Software
In the Login dialog box, enter the directory manager user name for
example, cn=Directory Manager. In the password box, enter the
password for directory manager. Click OK.
If the Login dialog states that the administration service is not running,
start the service as described in Restarting Directory Server Services
on page 158.
Sun ONE Console starts.
Expand the <ServerName> node by clicking the + sign next to it.

Expand the Server Group node. Click Directory Server <machine
name>.
Click Open, which appears in the far right section of the screen. This
brings up the Directory Server Administration console.
Backing Up the Entire Directory Server

This procedure captures a comprehensive snapshot of the directory server,
including data and configuration, and is useful for restoring a directory
server to its previous state if the installation gets damaged or if data is lost.
1
Login to the Sun ONE Administration Console as described in

Logging In to Sun ONE Administration Console on page 154.
Click the Tasks tab.
Click Back Up Directory Server. A new dialog box opens.
Accept the default values in the box and click OK.

This creates a backup of the entire directory server in the folder C:\Sun
ONE\Servers\slapd-<machine-name>\bak\<time of backup in
YYYY_MM_DD_HH_MM_SS format>.
Note: Copy this folder to a safe location, preferably on a removable
backup device.
Restart Sun ONE services as described in Restarting Directory Server

Services on page 158.
Backing Up/Exporting Data in a Single Root Suffix

This procedure will backup/export data in a single root suffix/root node.
This is useful when there is no need to backup configuration with data. The
output of this operation is an LDIF file that can be used by many tools to
restore data to the directory server.
Deployment Guide
155
Sun ONE Software
Login to Sun ONE Administration Console as described in Logging In

to Sun ONE Administration Console on page 154.
Click Tasks.
Click Export Databases. A new dialog box opens.
Click Browse and choose a location and name for the export LDIF file.
Select the Subtree radio button. Click Browse to specify the sub-tree to
backup.
In the new window that opens, click the tree to backup, for example,
genesys.net. Click OK.
A warning message box appears. Click OK to start the export.

Steps 57 create an LDIF file that contains data for the branch and its
child nodes. Copy this file to a safe location, preferably on a removable
backup device.
Restart Sun ONE services as described in Restarting Directory Server

Services on page 158.
Restoring the Entire Directory Server

This procedure restores a previously taken backup (as described in
Backing Up the Entire Directory Server on page 155) to a directory
server. It will restore data, configuration, and schema information. Changes
made to the directory since the backup was taken will be lost. During this
process, the directory server will not be available for normal operation.
1

Click Restore Directory Server. A new dialog box opens.
Choose the backup to restore from the Available Backups drop-down

list. If there are no entries in this list, there are no available backups to
restore from. Click OK after choosing the backup.
A new dialog box appears, indicating that the directory server will be
taken offline to restore the backup.
Click Yes to confirm. At this point, the directory server will not be
available for normal operations.
The dialog box informs when the restore process is finished.
156
Sun ONE Software
(Optional) Click Status Logs to see more details about this process.
Click Restart Directory Server to bring up the directory server.

The restore process is now finished.
Restoring Data in a Single Root Suffix

This procedure restores a previously taken export (as described in Backing
Up/Exporting Data in a Single Root Suffix on page 155) to a directory
server. It will restore only data. Configuration and schema information are
not restored. Changes made to the directory since the backup/ export was
taken are preserved. During this process, the directory server will continue
to work normally.
1

Click Import Databases. A new dialog box pops-up.
Click Browse and choose a location and name of the exported LDIF file
to restore from. Click OK to start restoring. Once the restore is finished,
click Close.
Click Restart Directory Server to bring up the directory server.

The restore process is now finished.
Completely Uninstalling Directory Server Software

A normal uninstall does not completely remove all files. The following
additional steps are necessary to completely remove the Sun ONE
Directory Server installation.
1
Select Start > Settings > Control Panel > Add/Remove Programs.
Select the Sun ONE installation to remove.
Click Remove. This removes the Sun ONE files that were installed by
default installation.
Restart the machine.
From Windows Explorer, select the folder C:\Sun ONE. Make sure that
there is no need to copy the data in it. If yes, make a copy of this folder.
Delete the folder and its sub folders.
This completely removes Sun ONE Directory Server from your
machine.
Deployment Guide
157
Sun ONE Software
Restarting Directory Server Services

After any changes in configuration and schema to the directory server, you
must restart the services for the changes to take effect.
1
Select Start > Programs > Administrative Tools > Services.
Restart the following services:
Sun ONE Directory Server 5 (machine name)
Sun ONE Administration Server 5(.x)
Setting Up Replication
Setting Up Single-Master Replication
This section assumes that one directory server is already configured and
contains data that needs to be replicated onto another read-only directory
server.
The original server that will become the master will be referred to as Server
A. The new server that will be the read-only slave will be referred to as
Server B.
On Server B:
1
Install Sun ONE directory server.
Create root node with the same name as the root node that needs to be
replicated from Server A. Follow the instructions in Creating the Root
Suffix Using Sun ONE Console on page 30; however, you do not need
to perform the instructions in the subsection Adding a Password to the
Root Suffix on page 31.
Create a new user for replication. The supplier will provide these
credentials to update the consumer:
a
b
c
d
e
f
Open directory console and select Directory tab > Config.

Right-click and select New > Other.
Select Person, and click OK.
In the new window, select the option Show Attribute Names.
In the values for cn and sn, enter Replication Manager.
Click Add Attribute and select userpassword from the list. Click
OK.
Note: The userpassword should not be longer than seven characters.
158
Sun ONE Software
Enter a password for the attribute userpassword.

h Click Naming Attribute: sn Change. Clear the sn check box and
select the cn check box. Click OK.
i
Click OK to create the user.
4
Set up the tree for replication.

a
b
c
d
e
f
Select the Configuration tab and expand the Replication. Select

the root node to replicate. On the right side:
Select the Enable Replica check box.
In the Replicate Role, select Dedicated Consumer.
Under Common Settings, specify a purge delay of 7 days, and then
scroll down.
In the new supplier DN field enter cn=Replication Manager,
cn=Config, and click Add.
Click Save.
On Server A:
1
Select the Configuration tab in the directory console and highlight the
Replication node.
In the right pane:

a
Select the Enable Changelog check box.

b Click Use Default.
c Set Max Changelog age to 8 weeks.
d Click Save to enable replication on this server.
3
In the Replication tree, highlight the root node to replicate.

a
b
c
d
e
Select the Enable Replica check box.

Select the Single Master radio button.
Under Common Settings, specify a replica id that is not currently in
use by any other server. This has to be unique.
Specify a Purge Delay of 7 days.
Click Save to save replication settings for this database.
Create a replication agreement between Server A and Server B. Server

A will push out data to Server B and needs to provide appropriate
credentials to Server B.
a
Right-click the database to replicate in the Replication tree. Select

New Replication Agreement.
b Enter a name for this agreement, for example <root node> on
<Server B>. Substitute your own values. Enter a description that
clearly states the following:
Deployment Guide
159
Sun ONE Software
The kind of replicationsingle master, multi master.

Click Other and in the new window, enter the fully qualified
name of Server B. Enter the port numberthis should be 389
unless you have configured your Server B directory server to
listen on another port.
In the Connection section, enter the user cn=Replication
Manager, cn=Config in Bind as and the associated password in
Password. Click Next. If Server A is able to bind successfully to
Server B, the screen will go to the next step. If there is an error,
make sure the information is correct and that Server B is
configured and running.
In the next screen, select Always keep directories in sync. Click
Next.
Select Do not initialize consumer. Click Next.
Click Done to finish setting up the replication agreement
between Server A and Server B.
Before replication can start, the consumer (Server B) needs to be

initialized from Server A. This process copies existing data from Server
A to Server B. Right-click the replication agreement, and select
Initialize Consumer. When initialization is complete, replication is
setup and will keep the two subtrees in sync.
Setting Up Multimaster Replication (MMR)

Install Server A and Server B. If one server is installed already then
designate that as Server A and install Server B.
This section assumes that one directory server is already configured and
contains data that needs to be replicated onto another read-write directory
server.
The original server that will become the master will be referred to as Server
A. The new server that will be the read-write replica will be referred to as
Server B.
To prepare Server A for MMR:
1
Open the directory server.
Select Configuration > Supplier settings tab

a
Select Enable changelog, and use the default.

b Specify Max Changelog age as 8 weeks.
c Click Save. This allows this server to be configured for replication.
160
Sun ONE Software
Open replication > genesys.net, then:

a
b
c
d
e
f
g
h
i
j
k
Enable replica.
Multiple Master.
Replica ID = 1.
Enter a new server DN = cn=Replication Manager. Click Add.
Click Save.
Right-click and select new replication agreement.
Enter a name and a description. Click Next.
Click Other. Add Server B and port.
Enter bind DN as cn=Replication Manager and password. Click
Next.
Select Always keep directories in sync. Click Next.
Select Do not initialize consumer. Click Next.
You are done preparing Server A for MMR.

4
Select Directory tab > Config > Right-click > New > Other
a
b
c
d
e
f
Select Person and click OK.

Full name and Last name are both Replication Manager.
Click Add attribute, and select user Password. Enter replication as
the password.
Naming attribute sn. Change.
Clear sn and select cn. Click OK.
Click OK. This creates the replication manager user.
To prepare Server B for MMR:

1
Open the directory server.
Go to Configuration > Supplier settings tab

a
Enable changelog, use default.

b Specify max changelog age as 8 weeks.
c Click Save. This allows this server to be configured for replication.
3
Open replication > genesys.net.

a
b
c
d
e
f
g
Deployment Guide
Enable replica.
Multiple Master.
Replica ID = 1.
Enter a new server DN = cn=Replication Manager. Click Add.
Click Save.
Right-click and new replication agreement.
Enter a name and a description. Click Next.
161
Troubleshooting VWPS Installation
Click Other. Add Server B and port.

i
Enter bind DN as cn=Replication Manager and password. Click
Next.
j
Always keep directories in sync. Click Next.
k Do not initialize consume. Click Next.
You are done.
4
Go to the Directory tab > Config > Right-click > New > Other
a
b
c
d
e
f
Person. Click OK.

Full name and Last name are both Replication Manager.
Add attribute, userPassword. Enter replication as the password.
Naming attribute sn. Change.
Clear sn and select cn. Click OK.
Click OK. This creates the replication manager user.

VWPS Does Not Show DIDs/DIDGroups Information
1
Using the servers GUI in VWPS, locate VWPS > <VWPS

machine>>VWPS. Right-click this node and select Edit from the menu.
Under this database, parameters will be present.
Select Start > Settings > Control Panel > Administrative Tools > Data
Sources (ODBC).
Click the System DSN tab.
Create a system DSN using the same information as supplied to VWPS.

You can copy this information from the servers UI opened in Step 1.
To create a DSN:
a
Click Add in the System DSN tab.

b From the list that appears, scroll to the bottom and select SQL
Server. Click Finish.
c In the new screen that appears, enter the following values:
Name = vwpstest
If vwpstest is already being used, enter a different name.
Description = testing VWPS connection
Server = Enter the same value as given in dbserver parameter in
servers UI.
162
d
e
f
g
h
i
j
k
l
m
n
o
Click Next.
Select the With SQL Server authentication radio button.
Click Client Configuration.
Select the TCP/IP radio button in the new screen that appears.
Click OK.
Make sure the Connect to SQL Server to obtain check box is
selected.
In the Login ID text box, enter the value of the dbusername
parameter from the servers UI. In the Password text box, enter the
value of the parameter dbpassword.
Click Next.
Select the Change default database to check box.
From the drop-down list, select the database supplied as the value of
the parameter dbinitialcatalog. If this database is not there, the
installation has not completed correctly. Create the database and try
again.
Click Next after selecting the correct database name.
Click Finish in the next screen that appears.
A new screen will appearclick Test Data Source.
ODBC manager will try to connect to the SQL Server. If it reports
back SUCCESS, then the configuration is correct and VWPS should
work. If the configuration is correct, restart WatchDog on VWPS
machine and try again. In case the ODBC manager reports back an
error, the configuration information is incorrect. Review the
information you have supplied for accuracy.
If the test succeeds and VWPS still does not show DIDs information,
make sure you have executed the scripts supplied in the install package.
Upgrading/Repairing Existing VWPS Installation

If VWPS is being reinstalled, repaired, or upgraded, follow these steps:
Deployment Guide
Uninstall VWPS using Control Panel > Add/Remove Programs.
After uninstalling, reboot the machine.
Backup the entire directory server. For details on how to do this, refer to
the VWPS Sun ONE.doc document. Use this backup if you need to
rollback to the pre-upgrade environment.
Perform the steps in Installing New VWPS on page 35.
Create the database structure for VWPS:
163
Troubleshooting the Dialogic Driver
To upgrade the database structure from a previous version:

a
b
c
d
e
f
g
h
Open the SQL Server Query Analyzer and connect to the VWPS
database.
Make sure VWPS database is selected in the drop-down selection
DB.
Open the supplied VWPS DB UPGRADE 6.5.3 to 6.5.4.sql in the
query analyzer from the D:\CN\Config\DBScripts\ folder on the
VWPS machine. A number of SQL statements punctuated by GO
statements should be visible in the Query Analyzer.
Select the first SQL statement and click the Run buttonthe green
triangle.
Ignore any PRIMARY_KEY_CONSTRAINT violations error
messages.
Repeat for every SQL statement. This upgrades the database
structure as required by this version of VWPS.
This script must be executed even if it has been run in a previous
version of VWPS installation.
Restart WatchDog.
Login to VWPS and click Diagnostics. Make sure that all the
diagnostic tests return success.
Perform the steps in Configuring VWPS on page 36.
In case installation is not successful, reinstall previous version of

VWPS.
Troubleshooting the Dialogic Driver

Windows 2000 uses inf files to correlate a device it finds while scanning
the PCI bus with a driver binary file that would be loaded for the scanned
device. Take the following steps for Windows 2000 systems that are
installed with a system release that does not include full Plug and Play
supported drivers.
For such systems, a NULL inf file was created. The purpose of the NULL
inf file is to make the system aware of the name and manufacturer of the
Dialogic board. This is used to track the device in the Device Manager and
to save the user from having to cancel the add hardware wizard that would
appear at every reboot when the system is not supplied with an inf file.
1
164
Click Next on the Found New Hardware Welcome dialog box that
appears after reboot. The Install Hardware Device Drivers dialog box
appears and prompts you to choose where the driver should be located.
Troubleshooting the SQL Server
Selected the radio button labeled Search for a suitable driver for my
device (recommended), and click Next. The Locate Driver files dialog
box appears, which has a series of check boxes.
Select the Specify a location check box, and click Next.
Click the Browse button and point to dialogic\drvr directory under the
installation directory, and click OK. The Driver Files Search Results
dialog box appears.
Verify that the file dlgcdm3_nt4.inf for DM3 boards was found by
Windows as a driver device. The Completing the Found New Hardware
Wizard dialog box appears and displays the name of the dialog board
that it finished installing.
Make sure that the correct name appears.
Click Finish.
To add subsequent supported Dialogic PCI boards, shut down the system,
insert the board and bring the system back up. Upon reboot, the system
scans the new board and automatically locates the inf file and finds the
name of the newly inserted board. You can check this inside the Device
Manager.

If remote clients are unable to connect to the SQL Server even when
connection information is correct, the default network library for SQL
Server on the client is set to Name Pipes instead of TCP/IP. If TCP/IP is
forced through making a system DSN, this problem may still occur.
Recommended Solution
The following solution has to be performed on every client machine that is
accessing a remote SQL Server.
Deployment Guide
From the SQL Server Installation CD, install SQL Server Client
utilities.
Select Start > Programs > SQLServer > Client Network Utility.
From the Server Alias Configuration list, select the SQL Server
machine you wish to access. In the Default Network Library dropdown list, select TCP/IP and click OK.
If the SQLServer machine is not in the list, click Add. In the dialog box
that appears, enter the following information:
165
Server Aliasfully qualified name of the SQLServer

b Network LibraryTCP/IP
c Port Number1433 unless you have configured SQLServer to
listen on a different port
5
Click OK.
Note: Depending on your network configuration, the client may be unable

to connect to the SQLServer when the servers fully qualified name is given
but may connect successfully if only the server name without the domain
name is given.
Alternate Solution If SQLServer CD Is Not Available

An alternate solution is to make DSN on the client machine, provide it
information to connect to the remote SQLServer and choose TCP/IP as the
default Network Library. This solution forces the client to connect to the
specified server using TCP/IP only.
1
Select Start > Settings > Control Panel > Administrative Tools >
Data Sources (ODBC).
Click the System DSN tab and click Add.
From the list that appears, scroll to the end and select SQL Server, then
click Finish.
In the next dialog box that appears, enter the following values:
a
Nametestdsn
If testdsn is already being used, give the DSN a different name.

b Descriptiontesting SQLServer connection
c [Server]fully qualified name of the SQLServer machine
166
Click Next.
In the next dialog box that appears, select the With SQL Server
authentication... check box.
Click Client Configuration, select the TCP/IP radio button, and click
OK
Select the Connect to SQL Server to obtain... check box.
In the Login ID text box, enter the value of the dbusername parameter
from the servers UI. In the password text box, enter the value of the
parameter dbpassword. Click Next.
10
Select the Change default database to check box.
Troubleshooting VCS
11
From the drop-down list, select the database you are trying to access. If
this database is not there, the installation has not completed correctly.
Create the database and try again.
12
Click Next.
13
Click Finish.
14
Click Test Data Source. ODBC Manager will try to connect to the
SQL Server. If it reports back SUCCESS, then the configuration is
correct and the software should work. If it reports back an error, the
configuration information is incorrect. Review the information you
have supplied for accuracy.
15
On success, every connection to the specified SQL Server from this

client machine will use TCP/IP.
Troubleshooting VCS
Bridging Calls
Calls can be bridged within a popgateway; however, bridging between two
popgateways or two VCSs is not supported.
Error Message
The VCS displays the following error when ASR is not configured: Error
found while loading XML : ERROR: ProcessMgtDataByProcName failed.
0x80010105XSL
File : file://C:/CN/Web/vcs/vcs_asr_packages.xsl
Uninstalling Dialogic Software

If you must uninstall the Dialogic software, follow this procedure:
Deployment Guide
On each VCS that the Dialogic software will be uninstalled, make a

copy of that VCSs pop.ini file.
If using DMV boards, on each VCS that the Dialogic software will be
uninstalled, make a copy of that VCSs Dialogic config files.
Uninstall the VCS software using the Add/Remove Programs from

Microsoft.
167
168
Uninstalling Dialogic Software
Uninstall the Dialogic PTRs by going to Start > Programs > Intel
Dialogic System Software > Point Release > Point Release Uninstall.
Uninstall the Global Call Package using the gcunin.exe executable that
is provided with the VWAP Third-Party software CD for Dialogic, in
the CD\GlobalCallProtocolPkg40\WINDOWS\I386 directory.
Uninstall the Dialogic SR5.1.1 SP1 using the uninstall utility provided
in the Servers Start > Programs > Dialogic > System Release 5.1.1
Service Pack 1 Uninstall.
Uninstall the Dialogic SR5.1.1 using the uninstall utility provided in the
Servers Start > Programs > Dialogic > Uninstall.
Reboot each VCS.
Delete the <d:\cn directory> and the <d:\Dialogic> directory (or the
appropriate Dialogic root directory).
Index
A
adding password, Sun ONE . . . . . . . . . 31
ASR groups, creating . . . . . . 69, 76, 81, 102
ASR log manager
configuring. . . . . . . . . . . . . . . . . 128
parameters . . . . . . . . . . . . . . . . 128
ASR Log Manager Agent, installing . . . 75, 100
ASR log server
configuring. . . . . . . . . . . . . . . . . 129
parameters . . . . . . . . . . . . . .129, 130
audience . . . . . . . . . . . . . . . . . . . . 9
audio provider, Nuance. . . . . . . . . . . . 62
B
billing port . . . . . . . . . . . . . . . . . . 119
C
configuring
ASR log manager . . . . . . . . . . . . . 128
ASR log server . . . . . . . . . . . . . . 129
DCM . . . . . . . . . . . . . . . . . . . . . 53
Dialogic software . . . . . . . . . . . . . . 49
EventC. . . . . . . . . . . . . . . . . . . 119
Genesys queue adapter . . . . . . . . . . 133
H.323 session manager . . . . . . . . . . 140
IPCS . . . . . . . . . . . . . . . . . . . . . 93
media gateway . . . . . . . . . . . . . . 136
Nuance . . . . . . . . . . . . . . . . . . . 68
outbound notification . . . . . . . . . . . 131
reporter . . . . . . . . . . . . . . . . . . 125
resource manager . . . . . . . . . . . . . 137
SpeechWorks OSR . . . . . . . . . . 76, 101
SpeechWorks OSR client . . . . . . . . 72, 98
SpeechWorks OSR license . . . . . . . 73, 99
SpeechWorks OSR services on OSR server 74
SpeechWorks OSR services on VCS . 74, 100
SSM . . . . . . . . . . . . . . . . . . . . 138
Deployment Guide
Sun ONE . . . . . . . . . . . . . . . . . . 29
TTS . . . . . . . . . . . . . . . . . . 86, 108
Unified Login Server . . . . . . . . . . . 123
VCS . . . . . . . . . . . . . . . . . . . 57, 67
VWCM . . . . . . . . . . . . . . . . . . 134
VWM . . . . . . . . . . . . . . . . . . . 113
VWPS . . . . . . . . . . . . . . . . . . . . 35
Configuring License Parameters for both Client
and Server Machines . . . . . . . . .74
conventions . . . . . . . . . . . . . . . . . .10
creating
ASR groups . . . . . . . . . . . 69, 76, 81, 102
media gateway groups . . . . . . . . . . 137
root suffix . . . . . . . . . . . . . . . . . . 30
D
database
EventC . . . . . . . . . . . . . . . . . . 115
installing software . . . . . . . . . . . . . . 84
VWCM . . . . . . . . . . . . . . . . . . 134
Dialogic board, installing . . . . . . . . . . . .46
Dialogic driver, troubleshooting . . . . . . . 164
Dialogic software
configuring . . . . . . . . . . . . . . . . . 49
global call protocol, installing . . . . . . . . 49
installing. . . . . . . . . . . . . . . . . . . 46
PTR28779, installing . . . . . . . . . . . . 48
PTR31128, installing . . . . . . . . . . . . 48
SR 5.1.1 SP1, installing . . . . . . . . . . . 47
SR 5.1.1, installing . . . . . . . . . . . . . 46
directory server requirements . . . . . . . . .15
dispenser . . . . . . . . . . . . . . . . . . .31
E
editing
Nuance configuration file . . . . . . . . . . 67
EventC . . . . . . . . . . . . . . . . . . . . .17
billing port . . . . . . . . . . . . . . . . . 119
169
Index
configuring.
database. .
easy install.
parameters
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
119
115
114
120
F
F1 boot, disabling . . . . . . . . . . . . . . 143
G
Genesys queue adapter, configuring. . . . . 133
global call protocol . . . . . . . . . . . . . . 49
groups
creating ASR . . . . . . . . . 69, 76, 81, 102
media gateway . . . . . . . . . . . . . . 137
H
H.323 session manager, configuring . . . . . 140
hardware, recommended. . . . . . . . . . . 13
I
IIS
settings . . . . . . . . . . . . . . . . . . . 23
URLScan filter . . . . . . . . . . . . . . . . 16
installing
ASR Log Manager Agent . . . . . . . 75, 100
Dialogic board . . . . . . . . . . . . . . . . 46
Dialogic software . . . . . . . . . . . . . . 46
IPCS . . . . . . . . . . . . . . . . . . . . . 91
MDAC . . . . . . . . . . . . . . . . . 84, 106
MySQL . . . . . . . . . . . . . . . . 84, 106
Nuance . . . . . . . . . . . . . . . . . . . 62
Nuance license . . . . . . . . . . . . . . . 66
RealSpeak . . . . . . . . . . . . . . . 85, 107
Speechify . . . . . . . . . . . . . . . 84, 106
SpeechWorks OSR . . . . . . . . . . . 72, 97
SpeechWorks OSR client . . . . . . . . . . 72
SQL server . . . . . . . . . . . . . . . . . 17
Sun ONE . . . . . . . . . . . . . . . . 29, 30
TTS . . . . . . . . . . . . . . . . . . . . . 85
US English language pack . . . . . . . . . 63
VCS . . . . . . . . . . . . . . . . . . . . . 56
VWM. . . . . . . . . . . . . . . . . . . . . 41
VWPS . . . . . . . . . . . . . . . . . . . . 35
watcher-daemon.startup. . . . . . . . . . . 63
Internet Explorer settings. . . . . . . . . . . 23
IPCS
configuring. . . . . . . . . . . . . . . . . . 93
installing . . . . . . . . . . . . . . . . . . . 91
parameters . . . . . . . . . . . . . . . 93, 94
route parameters . . . . . . . . . . . . . . 94
170
L
language pack, installing US English . . . . .63
M
MDAC, installing . . . . . . . . . . . . . 84, 106
media gateway. . . . . . . . . . . . . . . . 135
configuring . . . . . . . . . . . . . . . . 136
groups. . . . . . . . . . . . . . . . . . . 137
parameters . . . . . . . . . . . . . . . . 136
MySQL
installing. . . . . . . . . . . . . . . . 84, 106
installing database software . . . . . . . . 84
ODBC driver . . . . . . . . . . . . . 84, 106
N
Nuance
audio provider . . . .
configuration file . .
configuring . . . . .
configuring watcher .
installing. . . . . . .
license . . . . . . .
required software . .
SP030124. . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
62
67
68
66
62
66
61
62
O
ODBC driver . . . . . . . . . . . . . . . . . 106
open speech dialog modules . . . . . . . . 152
outbound notification, configuring . . . . . . 131
P
parameters
ASR log manager . . . . . . . . . . . . . 128
ASR log server . . . . . . . . . . . . 129, 130
EventC . . . . . . . . . . . . . . . . . . 120
IPCS . . . . . . . . . . . . . . . . . . 93, 94
IPCS route . . . . . . . . . . . . . . . . . 94
media gateway . . . . . . . . . . . . . . 136
reporter . . . . . . . . . . . . . . . . . . 126
resource manager . . . . . . . . . . . . 138
Unified Login . . . . . . . . . . . . . . . 124
VCS . . . . . . . . . . . . . . . . . . . . . 58
prerequisites . . . . . . . . . . . . . . . . . .13
provisioning media gateway . . . . . . . . . 135
R
RealSpeak, installing. . . . . . . . . . . 85, 107
Index
Reporter . . . . . . . . . . . . . . . . . . . 17
reporter
configuring. . . . . . . . . . . . . . . . . 125
parameters . . . . . . . . . . . . . . . . 126
resource manager
configuring. . . . . . . . . . . . . . . . . 137
parameters . . . . . . . . . . . . . . . . 138
resources, related . . . . . . . . . . . . . . 10
S
servers, adding . . . . . . . . . . . . . . . . 135
settings
system performance. . . . . . . . . . . . . 24
SIP session manager, see SSM
speech recognition requirements . . . . . . 15
Speechify . . . . . . . . . . . . . . . . . 84, 106
SpeechWorks OSR
configuring. . . . . . . . . . . . . . . . . . 76
configuring client . . . . . . . . . . . . 72, 98
configuring license. . . . . . . . . . . . 73, 99
configuring services on OSR server. . . . . 74
configuring services on VCS . . . . . 74, 100
installing . . . . . . . . . . . . . . . . . 72, 97
installing client . . . . . . . . . . . . . . . . 72
SpeechWorks OSR, configuring . . . . . . . 101
SQL server . . . . . . . . . . . . . . . . . . 17
client network libraries. . . . . . . . . . . . 18
installing . . . . . . . . . . . . . . . . . . . 17
troubleshooting . . . . . . . . . . . . . . 165
SSM, configuring . . . . . . . . . . . . . . . 138
Sun ONE . . . . . . . . . . . . . . . . . . . 152
adding password . . . . . . . . . . . . . . 31
configuring. . . . . . . . . . . . . . . . . . 29
creating root suffix . . . . . . . . . . . . . . 30
installing . . . . . . . . . . . . . . . . . 29, 30
upgrading . . . . . . . . . . . . . . . . . 153
system performance settings. . . . . . . . . 24
T
T1 robbed-bit . . . . . . . . . . . . . . . . . 60
telephony requirements . . . . . . . . . . . 15
templates, importing . . . . . . . . . . . . . 136
test calls . . . . . . . . . . . . . . . . . 87, 109
testing VWPS install . . . . . . . . . . . . . 141
text-to-speech, see TTS
troubleshooting
Dialogic driver . . . . . . . . . . . . . . . 164
SQL server . . . . . . . . . . . . . . . . 165
TTS
configuring. . . . . . . . . . . . . . . 86, 108
installing . . . . . . . . . . . . . . . . . . . 85
Deployment Guide
requirements . . . . . . . . . . . . . . . . 16
U
Unified Login
admin user . . . . . . . . . . . . . . . .
configuring . . . . . . . . . . . . . . . .
parameters . . . . . . . . . . . . . . . .
server settings . . . . . . . . . . . . . .
upgrading
Sun ONE . . . . . . . . . . . . . . . . .
VWPS . . . . . . . . . . . . . . . . . . .
URLScan Filter. . . . . . . . . . . . . . . .
124
123
124
124
153
163
.16
V
VCS
ASR features . . . . . . . . . . . . . . . . 67
configuring . . . . . . . . . . . . . . . . . 57
default package . . . . . . . . . . . . . . . 63
installing. . . . . . . . . . . . . . . . . . . 56
parameters . . . . . . . . . . . . . . . . . 58
Voice Web Manager, see VWM
VWAP CD . . . . . . . . . . . . . . . . . . .14
VWCM
adding servers . . . . . . . . . . . . . . 135
components . . . . . . . . . . . . . . . . 134
configuring . . . . . . . . . . . . . . . . 134
database . . . . . . . . . . . . . . . . . 134
importing templates . . . . . . . . . . . . 135
VWM
configuring . . . . . . . . . . . . . . . . 113
database . . . . . . . . . . . . . . . . . 114
installing. . . . . . . . . . . . . . . . . . . 41
VWPS
configuring . . . . . . . . . . . . . . . . . 35
installing. . . . . . . . . . . . . . . . . . . 35
repairing. . . . . . . . . . . . . . . . . . 163
setting up database . . . . . . . . . . . . . 36
T1 robbed-bit . . . . . . . . . . . . . . . . 60
testing install . . . . . . . . . . . . . . . 141
troubleshooting install . . . . . . . . . . . 162
upgrading . . . . . . . . . . . . . . . . . 163
W
watcher, configuring . . . . . . . . . . . . . .66
watcher-daemon.startup, installing . . . . . .63
Windows
configuring . . . . . . . . . . . . . . . . . 20
requirements . . . . . . . . . . . . . . . . 14
171
Index
172

PDF

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

PDF

Загружено:

Авторское право:

Доступные форматы

Voice Web Application Platform 6.

Genesys Telecommunications Laboratories, Inc.

Your Responsibility for Your Systems Security

Technical Support from VARs

Technical Support from Genesys

North and Latin America

Europe, Middle East, and Africa

+44 (0) 118 974 7002

+61 7 3368 6868

About This Document ............................................................................ 9

Voice Web Manager and Voice Web Provisioning System .............. 27

Voice Web Provisioning System Installation and Configuration ..... 29

Voice Web Manager Installation .......................................................... 41

TDM Set Up ........................................................................................... 43

VCS Installation and Configuration .................................................... 45

Nuance 8.0.0 Installation and Configuration for VCS ....................... 61

Voice Web Application Platform 6.5

Configuring VCS to Support ASR Features ........................................ 67

SpeechWorks OSR Client-Server Installation and Configuration for

MRCP Server Configuration for VCS .................................................. 79

Text-To-Speech Installation and Configuration for VCS .................. 83

IP Communications Server .................................................................. 89

IPCS Installation and Configuration ................................................... 91

SpeechWorks OSR Client-Server Installation and Configuration for

Text-to-Speech Installation and Configuration for IPCS ................ 105

Voice Web Manager Configuration ................................................... 111

Voice Web Manager Configuration ................................................... 113

Voice Web Application Platform 6.5

Setting Up Billing Port ....................................................................... 119

Miscellaneous Configurations and Troubleshooting ...................... 143

Recommended Solution ................................................................... 165

Voice Web Application Platform 6.5

About This Document

Intended Audience, page 9

Part 1 Voice Web Manager and Voice Web Provisioning System on

Chapter 1: About This Document

Part 2 TDM Set Up on page 43, provides the installation and

Part 3 IP Communications Server on page 89, provides the

Part 4 Voice Web Manager Configuration on page 111, provides

Bold type is generally used for emphasis, values of options, variables,

Voice Web Application Platform 6.5 Getting Started Guide, which

Voice Web Application Platform 6.5 Network Planning Guide, which

Voice Web Application Platform 6.5 Operations and Provisioning

Voice Web Application Platform 6.5

Chapter 1: About This Document

Voice Web Application Platform 6.5 Genesys Studio Developers

Voice Web Application Platform 6.5 VoiceXML 2.0 Reference Manual,

Voice Web Application Platform 6.5 Diagnostic and Troubleshooting

Voice Extensible Markup Language (VoiceXML) Version 2.0 W3C

The Genesys Migration Guide, also on the Genesys Documentation

The Genesys Technical Publications Glossary, which ships on the

Genesys Technical Support website at http://genesyslab.com/support.

Chapter 1: About This Document

Voice Web Application Platform 6.5

Dell PowerEdge 2650 2U

Dual Xeon, 2.4 GHz, minimum

Two 10K RPM 18 GB with RAID 1

VWAP 6.5 Software

Voice Communications Server (VCS)

Microsoft Data Access Component 2.7

Internet Information Server (IIS) > Common Files

Internet Information Server (IIS) > File Transfer Protocol (FTP)