Installation: Websphere Voice Response For Aix With Directtalk Technology

WebSphere Voice Response for AIX with DirectTalk

Technology
Installation
Version 6.1
GC34-7095-01

WebSphere Voice Response for AIX with DirectTalk
Technology
Installation
Version 6.1
GC34-7095-01
Note
Before using this information and the product it supports, read the general information under “Notices” on
page 149.
This edition applies to Version 6, Release 1 of IBM WebSphere Voice Response for AIX with DirectTalk Technology
(program number 5724-I07), and to all subsequent releases and modifications until otherwise indicated in new
editions. Make sure you are using the correct edition for the level of the product.
© Copyright IBM Corporation 1991, 2010.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Figures . . . . . . . . . . . . . vii Chapter 2. Connecting WebSphere Voice
Response to the telephone network . . . 21
About this information . . . . . . . . ix What connects to what? . . . . . . . . 21
Who should use this information . . . . . ix Digital interface cables for WebSphere Voice
How to use this information. . . . . . . ix Response . . . . . . . . . . . . . 25
Following the procedures in this Connecting a DTTA . . . . . . . . . 25
information . . . . . . . . . . . x Connecting an SMDI, SMSI, or VMS exchange
Typographic conventions . . . . . . . . x data link . . . . . . . . . . . . . 26
Accessibility . . . . . . . . . . . . xi Connecting an ACL exchange data link . . . 28
Notes on terminology. . . . . . . . . xii
Where to find more information . . . . . xii Chapter 3. Software installation . . . . . 31
Useful Web sites . . . . . . . . . xii Where to start? . . . . . . . . . . . 31
Making comments on this book . . . . . xiii If you are installing WebSphere Voice
Response for the first time . . . . . . 31
Chapter 1. Preparation . . . . . . . . 1 If you are migrating from a previous
WebSphere Voice Response system components 1 release . . . . . . . . . . . . . 32
Telephony hardware and protocols . . . . 1 Archiving your reports and log files . . . . 32
Voice and data processing . . . . . . . 2 Exporting your application data from the old
Data communications . . . . . . . . 3 system . . . . . . . . . . . . . . 33
What you need for installation . . . . . . 4 Procedure . . . . . . . . . . . . 33
Skills . . . . . . . . . . . . . . 4 Starting the migration process . . . . . . 34
Authority . . . . . . . . . . . . 4 Before starting . . . . . . . . . . 34
Devices . . . . . . . . . . . . . 4 Procedure . . . . . . . . . . . . 34
File systems . . . . . . . . . . . 4 Saving your current data . . . . . . . . 36
User ID . . . . . . . . . . . . . 5 Prerequisites . . . . . . . . . . . 36
Information . . . . . . . . . . . 5 Procedure . . . . . . . . . . . . 36
Preparing for installation . . . . . . . . 6 Preparing to migrate VoiceXML and Java
Migration . . . . . . . . . . . . . 7 applications . . . . . . . . . . . . 38
Planning your migration strategy . . . . 8 Setting up the AIX account (single system
Options for backing-up data prior to image only) . . . . . . . . . . . . 40
migration . . . . . . . . . . . . 8 Setting up the AIX account for a new
Planning the migration of Java and single system image . . . . . . . . 40
VoiceXML applications . . . . . . . . 9 Changing existing AIX accounts for a new
Migrating an existing single system image single system image . . . . . . . . 41
(SSI) . . . . . . . . . . . . . 10 Starting installation of WebSphere Voice
Migrating a system that uses HACMP . . 11 Response . . . . . . . . . . . . . 42
Converting from a standalone system to a Prerequisites . . . . . . . . . . . 42
single system image . . . . . . . . 13 Installing DB2 . . . . . . . . . . 42
Converting from a single system image to If installing WebSphere Voice Response
standalone systems. . . . . . . . . 14 Version 6.1 for the first time. . . . . . 44
Software prerequisites. . . . . . . . . 15 If migrating to Version 6.1 from a previous
The operating system . . . . . . . . 15 level of WebSphere Voice Response . . . 46
Other licensed program products . . . . 17 Setting up the AIX account (standalone
Important notes about using WebSphere Voice system only) . . . . . . . . . . . . 49
Response . . . . . . . . . . . . . 19 Setting your dtuser password . . . . . 49
© Copyright IBM Corp. 1991, 2010 iii

Setting the dtuser file permissions . . . 49 Copying a configuration on to another pSeries
Installing PTFs for WebSphere Voice Response 50 computer . . . . . . . . . . . . . 97
Restarting AIX . . . . . . . . . . . 51 Configuring attached devices . . . . . . 98
Creating the WebSphere Voice Response Changing a device definition . . . . . 98
database . . . . . . . . . . . . . 51 Making sure that what you type is what you
Updating the WebSphere Voice Response see . . . . . . . . . . . . . . . 99
database . . . . . . . . . . . . . 52 About the language environment . . . . 99
Setting ownership of the DTTAs . . . . . 53 About the keyboard map. . . . . . . 99
Running hardware diagnostic procedures . . 55 Setting the language environment . . . . 99
Changing the AIX password on an SSI
Chapter 4. License configuration . . . . 57 database server . . . . . . . . . . 100
Licensing overview . . . . . . . . . 57
The network licensing environment . . . . 58 Chapter 7. Data communications network
WebSphere Voice Response licenses . . . . 59 activities . . . . . . . . . . . . 101
Configuring your system for License Use Connecting to a 3270 mainframe . . . . . 101
Management . . . . . . . . . . . . 60 Communications Server for AIX . . . . 101
How does the other computer recognize
Chapter 5. Starting WebSphere Voice WebSphere Voice Response? . . . . . 106
Response and testing the installation . . 67 Example scenarios . . . . . . . . 108
Starting WebSphere Voice Response . . . . 67 Starting Communications Server and the link
Configuring the WebSphere Voice Response stations manually . . . . . . . . . . 114
telephony . . . . . . . . . . . . . 70 Procedure . . . . . . . . . . . 114
Testing the installation . . . . . . . . 72 Starting Communications Server and the link
Installing extra languages for Java stations automatically . . . . . . . . 114
applications . . . . . . . . . . . . 75 Procedure . . . . . . . . . . . 114
Restoring saved data after migrating . . . . 77 Installing SNMP support . . . . . . . 115
Importing .imp files . . . . . . . . . 80 Prerequisites . . . . . . . . . . 115
Restoring your VoiceXML and Java data . . 84 Procedure . . . . . . . . . . . 115
Rebuilding and reinstalling custom servers. . 85
Migrating 3270 servers . . . . . . . . 86 Chapter 8. Starting, stopping, and
Testing that your applications still work. . . 86 restarting WebSphere Voice Response . . 119
More about starting WebSphere Voice
Chapter 6. Post-installation activities . . . 89 Response. . . . . . . . . . . . . 119
Setting the WebSphere Voice Response Java and VoiceXML environment. . . . 119
environment . . . . . . . . . . . . 89 Display names . . . . . . . . . . 119
Defining an exchange data link to AIX . . . 90 Creating a display name file . . . . . 119
Prerequisites . . . . . . . . . . . 90 Using the status file . . . . . . . . 120
How does AIX recognize the link? . . . 90 Using the status window . . . . . . 120
Verifying the installation of an ACL Starting WebSphere Voice Response from
exchange data link . . . . . . . . . 90 a remote terminal . . . . . . . . . 121
Defining an SMDI, SMSI, or VMS Shutting down WebSphere Voice Response 122
exchange data link to AIX . . . . . . 91 Prerequisites . . . . . . . . . . 122
Checking the tasklist.data file . . . . . 92 Procedure . . . . . . . . . . . 123
Changing the maximum number of user Shutting down WebSphere Voice Response
processes . . . . . . . . . . . . . 94 automatically on AIX shutdown . . . . . 124
How many user processes can run at once? 94 Restarting WebSphere Voice Response . . . 124
How many processes do I need? . . . . 94 Using auto restart. . . . . . . . . 124
Procedure . . . . . . . . . . . . 95 Problems with starting WebSphere Voice
Increasing the amount of page space . . . . 96 Response . . . . . . . . . . . . 126
Procedure . . . . . . . . . . . . 96 The system does not start at all . . . . 126
iv Installation
The system does not display the Welcome Notices . . . . . . . . . . . . . 149
window . . . . . . . . . . . . 127 Trademarks . . . . . . . . . . . . 151
WebSphere Voice Response windows
become active without being selected . . 127 Glossary . . . . . . . . . . . . 153
The system does not behave as expected 129
The WebSphere Voice Response Graphical List of WebSphere Voice Response and
User Interface doesn't start . . . . . . . 129 associated documentation . . . . . . 187
Stopping the WebSphere Voice Response WebSphere Voice Response software . . . 187
windows. . . . . . . . . . . . 129 IBM hardware for use with WebSphere Voice
Stopping the run-time system . . . . . 130 Response . . . . . . . . . . . . 188
If you have trouble starting WebSphere Voice WebSphere Voice Response related products 188
Response . . . . . . . . . . . . 131 WebSphere Voice Server. . . . . . . 188
Unified Messaging for WebSphere Voice
Appendix A. Removing WebSphere Voice Response . . . . . . . . . . . 188
Response . . . . . . . . . . . . 133 AIX and the IBM pSeries computer . . . 188
HACMP . . . . . . . . . . . . 189
Appendix B. WebSphere Voice Response SS7 . . . . . . . . . . . . . 189
commands and utilities . . . . . . . 137 Integrated Services Digital Network. . . 190
dt_setowner command . . . . . . . . 144 Bellcore Specifications for ADSI Telephones 191
Appendix C. WebSphere Voice Response Index . . . . . . . . . . . . . 193

environment variables . . . . . . . 147
Contents v
vi Installation
Figures
1. Exchange data link (direct connection) 24 6. Basic License Tool window . . . . . 64
2. Exchange data link (indirect connection) 24 7. Distribute Licenses window . . . . . 65
3. The configuration tool, "Configure As" 8. Communications network, example A 109
page. . . . . . . . . . . . . 61 9. Communications network, example B 110
4. The configuration tool, "Direct binding" 10. Communications network, example C 111
page. . . . . . . . . . . . . 62 11. Communications network, example D 113
5. The configuration tool, "Start up" page. 63
© Copyright IBM Corp. 1991, 2010 vii

viii Installation
About this information
This book describes how to install the IBM® WebSphere® Voice Response for
AIX® voice processing system. It includes instructions for upgrading the
software and migrating your system and applications from an earlier release,
in addition to instructions for first-time use.
When you start the procedures in this book, the adapters and any other
hardware components must have already been installed in your pSeries®
computers.
When you finish the procedures in this book, you will have a system that can
answer an incoming telephone call using a supplied application.
Who should use this information

To use this book successfully, you should already understand the hardware,
software, communications, and storage prerequisites for installing WebSphere
Voice Response (see the WebSphere Voice Response for AIX: General Information
and Planning book). You should also be familiar with the AIX system
management interface tool (SMIT) which is used to install software, configure
devices, and define the AIX operating environment. In addition, you should
be familiar with using AIX.
As the installer, you also need to understand the data communications

network configuration at your location, including peripheral equipment (such
as display terminals or printers). In addition, you should know how your
organization's telephone network is configured.
If you are unfamiliar with AIX, you may want to consider enrolling on an
IBM training course before you install WebSphere Voice Response. Courses
include information about using the basic AIX commands, the vi editor, and
SMIT. Your IBM service representative can explain how to enroll on an IBM
training course. Alternatively, you can enroll on IBM training courses online at
http://www.ibm.com/services/learning.
How to use this information

The main chapters of this book are made up of a sequence of procedures. This
is how you should use the book:
1. Getting an overview: Read Chapter 1, “Preparation,” on page 1.
© Copyright IBM Corp. 1991, 2010 ix

Use the information in this chapter to plan your installation or migration
process. “Preparing for installation” on page 6 gives you an overview of
the procedures you need to follow when installing WebSphere Voice
Response for the first time or when migrating to the new release.
2. Connecting WebSphere Voice Response to the network: If your system
is not already connected, follow the procedures in Chapter 2, “Connecting
WebSphere Voice Response to the telephone network,” on page 21.
3. Installing the software: Follow the procedures in Chapter 3, “Software
installation,” on page 31. This chapter also describes how to start
WebSphere Voice Response so that the installation can be verified by
making a phone call to a telephone line connected to WebSphere Voice
Response, which runs an application to answer the call.
4. Licensing WebSphere Voice Response: Follow the procedures in
Chapter 4, “License configuration,” on page 57.
5. Configuring the system: After you have completed the installation or
migration, follow the procedures in the following chapters, as necessary:
v Chapter 6, “Post-installation activities,” on page 89
v Chapter 7, “Data communications network activities,” on page 101
The tasks you need to complete depend on your set-up and environment.
6. Starting up and shutting down: Read Chapter 8, “Starting, stopping, and
restarting WebSphere Voice Response,” on page 119.
This chapter contains additional information on startup and shutdown
procedures, for more operational usage of WebSphere Voice Response.
When you have finished the procedures in this book, you have a system on
which you can run the sample applications. You may have to perform further
configuration activities if you intend to use a variety of switch protocols and
facilities. Otherwise, you are ready to start creating applications and installing
them ready for use.
Following the procedures in this information
The procedures assume that you are already familiar with using a mouse and
window environment and that you know how to use the common actions
such as Save to work with information. You'll find information about using
the WebSphere Voice Response windows in the WebSphere Voice Response for
AIX: User Interface Guide book.
Typographic conventions
This book uses the following typographic conventions:

boldface
Identifies an item that is in a WebSphere Voice Response window. The
item might be a keyword, an action, a field label, or a pushbutton.
x Installation
Whenever one of the steps in a procedure includes a word in
boldface, look in the window for an item that is labeled with that
word.
boldface italics
Are used for emphasis. Take extra care wherever you see bold italics.
italics Identify one of the following:
v New terms that describe WebSphere Voice Response components or
concepts. A term that is printed in italics is usually followed by its
definition.
v Parameters for which you supply the actual names or values.
v References to other books.
monospace
Identifies one of the following:
v Text that you type in an AIX window. Because AIX is case sensitive,
ensure that you type the uppercase and lowercase characters exactly
as shown.
v Names of files and directories (path names).
Accessibility
WebSphere Voice Response for AIX is a voice application enabler. The

applications that are developed to run on WebSphere Voice Response provide
telephone access to business data and services. In this way, WebSphere Voice
Response provides accessibility for people who cannot access the data and
services by using regular Web pages or traditional graphic interfaces. These
telephone user interfaces are fully accessible to people who are blind or have
low vision and, if speech recognition is used, to people with mobility
impairments or limited hand use. Speech recognition capability can be
provided by products such as IBM WebSphere Voice Server. In addition,
support for users of Telephony Devices for the Deaf (TDD) is provided as part
of the WebSphere Voice Response product.
With WebSphere Voice Response you can perform many application

development and system administration tasks with a text editor or line
commands—these are accessible if you use a screen reader product to
interface with them. Also, the default settings of the WebSphere Voice
Response graphical user interface can be changed to produce large fonts and
high contrast colors. Details of how to use these accessibility features can be
found in the WebSphere Voice Response for AIX: User Interface Guide book.
Alternatively, application development can be done with Java™ or VoiceXML
development tools that are supplied by IBM and third parties.
About this information xi

You can also use a screen-reader product to access the WebSphere Voice
Response publications in HTML format (for details of their availability see
“List of WebSphere Voice Response and associated documentation” on page
187).
Notes on terminology
v A glossary of commonly-used terms is at the end of this book.
v The full product name of WebSphere Voice Response for AIX with DirectTalk®
Technology is generally abbreviated in this book to WebSphere Voice Response.
v The term pSeries® is generically used in this book to refer both to PCI-based
RS/6000® computers and to appropriate models of the System p5® and
pSeries ranges. (Consult your IBM representative for details of models that
are supported for use with WebSphere Voice Response.) RS/6000 computers
with an MCA bus are not supported.
v The IBM Quad Digital Trunk Telephony PCI Adapter is generally referred to in
this book by its abbreviation DTTA. This adapter is a replacement for the
IBM ARTIC960RxD Quad Digital Trunk PCI Adapter, which is generally
referred to by the abbreviation DTXA. The DTXA is not supported with
WebSphere Voice Response Version 6.1.
v References made to the VoiceXML 2.1 specification are intended to include
VoiceXML 2.0 unless otherwise specified.
Where to find more information
The information provided in the WebSphere Voice Response library will help
you complete WebSphere Voice Response tasks more quickly. A complete list
of the available publications and where you can obtain them is shown in “List
of WebSphere Voice Response and associated documentation” on page 187.
Useful Web sites
The following Web sites are useful sources of information about WebSphere
Voice Response and related products:
WebSphere Voice Response
http://www.ibm.com/software/pervasive/voice_response_aix/
IBM WebSphere developerWorks resources (including WebSphere Voice
products)
http://www.ibm.com/developerworks/websphere/zones/voice/
VoiceXML Version 2.0 and 2.1 specifications
http://www.w3.org/TR/voicexml21/
http://www.w3.org/TR/voicexml20/
xii Installation
CCXML Version 1.0 specification
http://www.w3.org/TR/2007/WD-ccxml-20070119/
Genesys
For more information on Genesys products go to the Genesys Web
site at http://www.genesyslab.com
Making comments on this book
If you especially like or dislike anything about this book, feel free to send us
your comments.
You can comment on what you regard as specific errors or omissions, and on
the accuracy, organization, subject matter, or completeness of this book. Please
limit your comments to the information that is in this book and to the way in
which the information is presented. Speak to your IBM representative if you
have suggestions about the product itself.
When you send us comments, you grant to IBM a nonexclusive right to use or
distribute the information in any way it believes appropriate without
incurring any obligation to you.
You can get your comments to us quickly by sending an e-mail to

idrcf@hursley.ibm.com. Alternatively, you can mail your comments to:
User Technologies,
IBM United Kingdom Laboratories,
Mail Point 095, Hursley Park,
Winchester, Hampshire,
SO21 2JN, United Kingdom
Please ensure that you include the book title, order number, and edition date.
About this information xiii

xiv Installation
Chapter 1. Preparation
Read this chapter before you start to install WebSphere Voice Response for the
first time, or before you upgrade an existing system by installing the new
release.
This chapter includes the following sections:

v “WebSphere Voice Response system components”
v “What you need for installation” on page 4
v “Preparing for installation” on page 6
v “Migration” on page 7
v “Software prerequisites” on page 15
v “Important notes about using WebSphere Voice Response” on page 19
WebSphere Voice Response system components

A WebSphere Voice Response voice processing system brings together your
telephone network and your data communications network. Installing a
WebSphere Voice Response system therefore involves:
v Connecting WebSphere Voice Response to the telephone network
v Installing WebSphere Voice Response and other software on the pSeries
computer
v Configuring WebSphere Voice Response and the other software to work
together
v Connecting WebSphere Voice Response to the data communications
network
This section introduces the hardware and software required for telephony,
voice and data processing, and data communications.
Telephony hardware and protocols
To transmit and receive voice signals to and from the telephone network,
WebSphere Voice Response can use specialized hardware: pSeries computer
digital trunk adapters. Digital trunk adapters are installed in the pSeries
computer system unit. For more information, see “What connects to what?”
on page 21.
WebSphere Voice Response can work with a variety of telephone switches,

using channel-associated signaling or common-channel signaling protocols to
carry the voice traffic and control calls. With some channel-associated
© Copyright IBM Corp. 1991, 2010 1

signaling protocols, an exchange data link may be required to provide functions
such as far-end hang up detection, provision of call information, call transfer,
and message waiting indication.
No hardware adapters are required with BladeCenter or pSeries computers

when using the DTNA software support for Voice over IP networks.
Exchange data link software provided with WebSphere Voice Response

supports:
v Application Control Link (ACL): Siemens Hicom 300
v Simplified Message Desk Interface (SMDI): Nortel
v Simplified Message Service Interface (SMSI): Avaya
v Voice Message Service (VMS): Ericsson
v CallPath Server: Lucent Definity switch
Voice and data processing
WebSphere Voice Response runs on an IBM pSeries computer that has the AIX
operating system and a number of other licensed program products (LPPs)
installed on it. The following types of voice applications are supported:
v CCXML 1.0 with VoiceXML 2.1
v VoiceXML 2.1
v WebSphere Voice Response Java application programming interface
v The WebSphere Voice Response proprietary state table interface
In addition, to extend the system capabilities, you can create custom servers
by using the C or C++ programming languages.
The detailed information in WebSphere Voice Response for AIX: General

Information and Planning should be used to determine which programming
models are best suited for your system. Having made that decision, refer to
“Software prerequisites” on page 15 to determine what other LPPs you need
to install before starting the installation of WebSphere Voice Response.
Speech recognition
Speech recognition can be provided by WebSphere Voice Server (a separately

orderable product). For further information, refer to http://www.ibm.com/
software/pervasive/voice_server/.
WebSphere Voice Response can also be integrated with other MRCP

V1-compliant speech recognition products or TDM-based digital signal
processing. For more information, ask your IBM representative.
2 Installation
Text-to-speech processing
Text-to-speech processing can be provided by WebSphere Voice Server, which
is a separately orderable product. This product is described in detail in the
WebSphere Voice Server infocenter at:
http://publib.boulder.ibm.com/infocenter/pvcvoice/51x/index.jsp
High-quality sound recording and playback
To record high-quality sound or use audio editing software on a separate

personal computer.
Data communications
Remote data access
VoiceXML or Java applications and business data can be resident on a Web

server or application server and accessed using TCP/IP. With state tables and
custom servers, you can access business data either locally on the pSeries
system or remotely using TCP/IP or SNA. You can also access host 3270
applications via TCP/IP or SNA.
Having decided how your system is to access business data, refer to

“Software prerequisites” on page 15 to determine what LPPs you need to
install before installing WebSphere Voice Response.
The network can include:

v X-Windows enabled graphical display terminals, used as remote terminals
for all WebSphere Voice Response functions
v An ASCII terminal for system management functions
v Remote system management by the network operator
Remote system management
If your network is managed by NetView® or another network management

application that uses simple network management protocol (SNMP), one or
more WebSphere Voice Response systems can be managed from a central
point (which can be a separate machine or a pSeries computer on which
WebSphere Voice Response is running). SNMP is used to send WebSphere
Voice Response alarms and other status information to the network
management application.
Using a service such as NetView, the network operator can keep WebSphere
Voice Response running day-to-day. If WebSphere Voice Response stops
Chapter 1. Preparation 3
unexpectedly, the NetView operator can help diagnose the problem, using the
information in the alarm messages. (For more information about alarms, see
the WebSphere Voice Response for AIX: Configuring the System book and the
WebSphere Voice Response for AIX: Problem Determination book.)
The network operator can also obtain up-to-date information about trunks,
channels, CPU usage, and so on, and can reset their status, giving the
operator remote control over the WebSphere Voice Response system.
What you need for installation

Skills
You should know how to use the mksysb command to create a backup image
of the system and how to restore from it.
You can use the AIX System Management Interface Tool (SMIT) utilities to
install software and configure devices. If you haven't used SMIT before, look
through the SMIT overview in the System User's Guide; Operating System and
Devices manual. In this book the instructions tell you to start SMIT using the
smitty command, but you can instead use the smit command if you prefer a
Motif-based interface.
You need some understanding of how AIX handles device definitions, how it
structures file systems and directories, and how it uses processes and page
space. All this information is available in System User's Guide; Operating System
and Devices.
You also need to know how to use a text editor to edit files.
Authority
Some of the steps in the installation and migration process can only be
performed only by a person who is the AIX root user. The root user has
superuser privileges. To complete these activities, you need to know how to
log on as the root user.
Devices
Be aware that it is easiest to install all hardware devices before you start
installing AIX to ensure that the appropriate device drivers are automatically
selected for installation.
File systems
WebSphere Voice Response needs a local /usr file system. It will not run on a
diskless client or on a client in an AIX /usr client-server system configuration.
WebSphere Voice Response also uses a /home file system and a /var file
system.
4 Installation
User ID
All WebSphere Voice Response users (including administrators and
developers) must use the same AIX account. An account named dtuser is
automatically created for this purpose (if it does not already exist) when you
install WebSphere Voice Response. The dtuser ID is created as a basic local
user.
However, you must create the user ID yourself before you install WebSphere
Voice Response if:
v You want to set up a cluster of WebSphere Voice Response systems as a
single system image. For information on how to do this, see “Setting up the
AIX account (single system image only)” on page 40.
v You want to set up your WebSphere Voice Response account differently (for
example, using NIS, AFS, or DFS). For information on how to do this, see
“Setting up the AIX account (standalone system only)” on page 49.
The installation process will insert new text into the .profile file for dtuser.
Changing or deleting that text could affect the running of WebSphere Voice
Response.
Note: Even if you are not using the dtuser AIX account to run WebSphere
Voice Response, you must have a dtuser account in order to install a PTF, so
don't delete it. Use the AIX smit or mkuser command to recreate it if
necessary.
Information
This book contains all the instructions needed to:
v Install WebSphere Voice Response for the first time and configure it to run a
sample application.
v Install the new release of WebSphere Voice Response and migrate an
existing system and applications.
You also need:

v The installation instructions for any other licensed program products you
are going to install (see “Software prerequisites” on page 15).
v General information about other components of your overall system; for
example, the type of switch and protocol you will be using.
If you are migrating from a previous release, you might have to consult other
WebSphere Voice Response books in the from time to time.
Preparing for installation
Read this section before beginning to install, or migrate to, WebSphere Voice
Response Version 6.1; thorough preparation will save you time eventually.
1. If you have not done so already, read the WebSphere Voice Response for AIX:
General Information and Planning book. This includes:
v An introduction to the product, what it can do, and how to use it
v What's new in this release
v Information about planning your system.
2. If you did not complete the planning checklist in the WebSphere Voice
Response for AIX: General Information and Planning book before ordering
WebSphere Voice Response, do so now. Then record the following details
here for reference during the installation process.
Is the communication to be via telephony switch, or

using Voice over IP?
Is the trunk interface E1 or T1?
Is the signaling protocol CAS, ISDN or SS7? (This is

referred to as Signaling Mode.)
If using T1 ISDN with Trunk 1: Trunk 9:

Non–Facility Associated
Signaling (NFAS), what are Trunk 2: Trunk 10:
the trunk identifiers
allocated by the service
Trunk 3: Trunk 11:
provider and which trunk
carries signaling?
Trunk 4: Trunk 12:
Trunk 5: Trunk 13:
Trunk 6: Trunk 14:
Trunk 7: Trunk 15:
Trunk 8: Trunk 16:
To what switch are you

connecting?
6 Installation
If using a CAS signaling
protocol, for which
protocol is the switch
configured?
Are you using an SP

pSeries?
What is the TCP/IP
address of the pSeries
computer?
If you are using a remote
display, what is the
TCP/IP address of the
remote display?
What is the root password
of the pSeries computer?
Which phone number can
you use to dial in to the
sample application?
3. Determine your installation method, either:

v Installing WebSphere Voice Response for the first time.
v Migrating to WebSphere Voice Response Version 6.1 from a previous
release, using the migration utility to replace the previously installed
level.
For more information about the two migration methods, see “Migration.”
When you have completed the installation process described in this book, you
should be able to make a call to WebSphere Voice Response and have it
answer the call. If you are migrating from a previous release, your
applications should still run correctly on the new release.
Keep track of your progress. A progress report is very useful to the IBM
support representative if you find you need any help with the installation.
Migration
If you are migrating from a previous release of DirectTalk or WebSphere Voice
Response , you should read this section which contains information about:
v “Planning your migration strategy” on page 8
v “Planning the migration of Java and VoiceXML applications” on page 9
v “Converting from a standalone system to a single system image” on page
13
v “Converting from a single system image to standalone systems” on page 14
Planning your migration strategy
This section gives an overview of the things you need to consider when
planning your migration strategy. For detailed instructions on migration, see
Chapter 3, “Software installation,” on page 31.
WebSphere Voice Response applications are upwardly compatible from release

to release. WebSphere Voice Response is designed so that you can migrate
your existing applications from previous releases of DirectTalk or WebSphere
Voice Response without difficulty.
Important: If the level of software that you currently have installed is earlier
than WebSphere Voice Response Version 4.2, you should contact your IBM
representative for assistance about moving to WebSphere Voice Response
Version 6.1.
Migration strategies
If you already have applications in production, you need to consider your

migration strategy:
v If you have more than one pSeries computer, and can install the new
release on one system while keeping your applications running on another,
you can follow the instructions for first-time installers, and then migrate
your applications afterwards.
v If you have only one pSeries computer, you need to migrate your system
in-place. Follow the instructions in this book carefully to minimize the
downtime required for migration and installation. If you are migrating
in-place, it is especially important that you prepare thoroughly beforehand.
Make sure you schedule the migration to happen at a time when
applications are least active.
Options for backing-up data prior to migration
The migration process for WebSphere Voice Response Version 6.1 will not
affect your existing system or application data. However, you should always
make a backup of your data prior to starting the migration process, so that
you can recover if any problems are encountered.
Making a backup using mksysb
The safest option is to backup a complete image of your system by using the
mksysb command. Although this can take a long time, it ensures that, if you
do encounter problems during installation, you can easily get back to the
point from which you started. Details of how to use the mksysb command
can be found in the AIX: Installation Guide .
8 Installation
Making a backup using saveDT
An alternative method of backing-up data is to use the WebSphere Voice
Response saveDT utility. However, unlike mksysb, this backs up only the
application data, so if you encounter any problems during installation, you
would need to separately reinstall the level of WebSphere Voice Response that
you had been previously using, and then use the restoreDT utility to recover
the data. In addition, the following types of data are not backed-up by the
saveDT utility:
v Java and VoiceXML applications. See “Planning the migration of Java and
VoiceXML applications”
v AIX_file objects.
v The supplied help text files, which are replaced with a new set during
migration.
v Any changes you may have made to the WebSphere Voice Response
resource files. If, for example, you made color or font changes, you have to
make the same changes again.
v Your values for any system configuration parameters. These may have a
new default value in WebSphere Voice Response Version 6.1, and the new
default value would overwrite the value you have been using.
v Information about Single System Image clusters. If you have a Single
System Image configuration you will need to recreate your cluster after the
save-and-restore process.
v Custom server data that is not in the custom server directory
(ca/custom_server_name) or in ca/bin.
v Current reports and log files. If you want to save your current statistics
data you must archive it first, as described in “Archiving your reports and
log files” on page 32.
For detailed information about backing up data using saveDT, see “Saving
your current data” on page 36.
Planning the migration of Java and VoiceXML applications
You should read this section only if you have existing VoiceXML or Java
applications.
If you are already using VoiceXML 2.0, VoiceXML 2.1, or Java applications,
your application data is not affected during the migration to WebSphere Voice
Response Version 6.1, so you do not need to take any action to run such
applications when migration is complete. Your dtj.ini file is replaced by a
new version, but a copy of your existing file is saved, and renamed to
dtj.ini.V4.2.orig, so any customization that you have made to the file
previously can be restored by copying across the updates.
If you are using VoiceXML 1.0 applications, these are not supported in
WebSphere Voice Response Version 6.1. However, you can convert any
VoiceXML 1.0 applications to comply with the VoiceXML 2.1 specification, by
using the migration facility provided in the WebSphere Voice Toolkit Version
6.0, which can be downloaded free from http://www.ibm.com/software/
pervasive/voice_toolkit. Some editing may also be required and you will need
to make a change to the AppName entry in the configuration file (see
WebSphere Voice Response for AIX: Deploying and Managing VoiceXML and Java
Applications for details). You can then use the Voice Toolkit to test these
migrated applications before starting the migration of WebSphere Voice
Response.
If you are currently using the old Java and VoiceXML Environment (DTBE)
that supported VoiceXML 1.0 applications, you must remove it before you can
start the migration to WebSphere Voice Response Version 6.1. You also need to
save any voice segments and configuration files (.cff) that you use before
installing the new version. These actions are documented in “Preparing to
migrate VoiceXML and Java applications” on page 38.
After installing the new software, you can then restore your data following
the instructions in “Restoring your VoiceXML and Java data” on page 84.
Note: Although Java applications that were developed using JavaBeans can
still run in WebSphere Voice Response Version 6.1, the programming tools
used with this method are no longer supported, and so all new applications
should be developed using the Java API.
Migrating an existing single system image (SSI)
In an SSI system, comprising one or more servers and a number of clients, it
is possible to reduce downtime by first migrating the servers and a limited
number of clients. A reduced capacity system can then be run with the new
WebSphere Voice Response Version 6.1 software, while you migrate the
remaining clients.
Procedure
Before you start, make a backup of all the machines in the SSI cluster.
Upgrade one or more clients:
On the first client machine:

1. Quiesce telephony.
2. Shutdown WebSphere Voice Response.
The client is now isolated and can be migrated while the rest of the SSI
continues to operate.
10 Installation
3. On the isolated client, run the command ssirmclient to remove the SSI
client.
4. Upgrade to WebSphere Voice Response as described in Chapter 3,
“Software installation,” on page 31.
Upgrade the server:
In order to upgrade the server, you must first stop all clients. This means that
the SSI will not be operational while the server is upgraded.
1. On the other SSI clients:
a. Quiesce telephony.
b. Shutdown WebSphere Voice Response.
2. On the SSI server:
a. Run the command ssirmsrv to remove the SSI server.
b. Upgrade WebSphere Voice Response as described in Chapter 3,
c. If the SSI server has telephony, then start telephony.
Restart the reduced system:

1. Start WebSphere Voice Response on the migrated clients.
2. Start Telephony.
Migrate and restart the remaining clients:

1. Upgrade to WebSphere Voice Response Version 6.1.
2. Start WebSphere Voice Response.
3. Start telephony.
Migrating a system that uses HACMP
In an HACMP configuration, you can migrate by creating a partitioned
system, which allows you to migrate some of the clients and one of each
server pair to WebSphere Voice Response Version 6.1, while the remaining
clients and servers remain in a working WebSphere Voice Response Version
4.2 system (although the capacity of this system will be limited).
In this configuration, you can then stop the WebSphere Voice Response
Version 4.2 partition and start the WebSphere Voice Response Version 6.1
partition. In this way, the downtime is reduced to the time it takes to quiesce
the Version 4.2 partition, migrate the database and then bring the WebSphere
Voice Response Version 6.1 clients and servers into the system.
Procedure
Before you start, backup all the machines in the SSI cluster.
In the steps below, server A denotes the SSI server used as the DB2 server and
server B denotes the SSI server used as the NFS server:
Note: Ensure that /home/dtdb23in/sqllib/db2nodes.cfg contains the HA

service name of the DB2 node. If it does not, edit the file and ensure the HA
system works before continuing.
Upgrade one or more clients:
On the first client machine:

1. Quiesce telephony.
2. Shutdown WebSphere Voice Response.
3. Upgrade to WebSphere Voice Response as described in Chapter 3,
4. If you are also migrating to Unified Messaging for WebSphere Voice
Response Version 6.1, install the Unified Messaging base filesets.
Failover to server B and create a partition:
The DB2 and NFS services can be failed over to server B, so that server A can
be upgraded while the system continues working at Version 4.2.
1. On server A, failover all services to server B so that server B assumes the
role of a DB2 server and NFS server.
2. Install the filesets to upgrade to WebSphere Voice Response Version 6.1 on
server A, but do not attempt to migrate the database at this stage.
Failback to the Version 4.2 partition (system down):
The system must now be stopped to allow services to be failed-back to server

A and enable the database to be migrated from DB2 V8.1 to DB2 V9.5.
1. Quiesce telephony on the back-level clients that are taking active calls
(these clients are still on WebSphere Voice Response Version 4.2 and have
not been upgraded yet).
2. Shutdown WebSphere Voice Response on the back-level clients.
3. Edit HAstartDT on server A so that the commands to start DB2 and
WebSphere Voice Response are commented out. That is, comment out the
following lines:
#/usr/bin/su -$DBINSTANCE -c db2start >/dev/console 2>&1
#su dtuser -c "/usr/lpp/dirtalk/tools/vaeinit.nox"
4. Failback all services from server B to server A, so that server A assumes
the role of a DB2 server and NFS server.
At this point, the SSI cluster is down and not taking any calls.
12 Installation
5. On server A, log in as root and run WebSphere Voice Response migration
script by typing:
/usr/lpp/dirtalk/tools/DTdatabase –m
This migrates the DB2 V8.1 instance and database to the DB2 V9.5 level.
Start operating using the partition and migrate the partition:
The Version 6.1 partition can now be started and operation can continue using
this partition while the Version 4.2 partition is migrated.
Converting from a standalone system to a single system image
If you want to convert from an existing WebSphere Voice Response or
DirectTalk system to a single system image, you should consider the
following:
v The data from only one WebSphere Voice Response or DirectTalk system
can be restored into a single system image using the restoreDT command.
This is because most of the database is shared, and would therefore get
overwritten if you attempted to restore on another node in the single
system image.
v If you have multiple systems that have identical application objects (for
example, state tables and voice segments) and voice data, you can use the
saveDT command on any of the systems to save a copy of your data. You
can use the DTlsapobj and DTlsvmobj commands (see the description of
these commands in the WebSphere Voice Response for AIX: Managing and
Monitoring the System book) to display information about application and
voice objects to confirm that all the objects are on all of the existing
systems.
v If you have multiple systems that have different application objects, you
need to plan very carefully before you convert to an SSI environment. You
must check what application objects exist on each system, and resolve any
conflicts. You can use the DTlsapobj and DTlsvmobj commands to list the
application and voice objects on each system.
When you know which objects you want, export them all to one WebSphere
Voice Response or DirectTalk system and run the saveDT command on that
system.
When you have saved a copy of the data that you want, use the restoreDT
utility to restore it to the database server node you set up in the single system
image.
Typically you will want to create a single system image starting from one of
the following points:
You have new pSeries computers
If you have new hardware that you want to configure as a single
system image, you must perform the following steps:
1. Create a new WebSphere Voice Response user ID on every system,
using the AIX smit or mkuser command. The user ID must be
defined identically on every system. This task is described in
“Setting up the AIX account (single system image only)” on page
40.
2. Install WebSphere Voice Response on every system. This task is
described in “Starting installation of WebSphere Voice Response”
on page 42.
3. Configure one of the systems as a server node and the others as
client nodes. This task is described in the WebSphere Voice Response
for AIX: Configuring the System book.
You have existing stand-alone systems
1. Save your existing data.
2. Uninstall WebSphere Voice Response or DirectTalk from each
system.
3. Create an additional user ID on each system (this user ID must be
identical on every system).
Note: If you do not want to create new user IDs, you can change
the existing user ID on each system to make them all identical.
4. Install WebSphere Voice Response on every system.
5. Use vae.setuser to ensure the file systems and ownerships are
correct.
6. Configure every system as an SSI node.
7. Restore your data on to the database server node of your single
system image.
Converting from a single system image to standalone systems
The data on a single system image is stored on the server node. If you want
to copy data from that server node to a standalone WebSphere Voice Response
system, you must:
1. Remove (that is, unconfigure) the clients from the single system image. To
do this, use the ssirmclient command, as described in the WebSphere Voice
Response for AIX: Configuring the System guide.
2. Remove the server from the single system image. To do this, use the
ssirmsvr command, as described in the WebSphere Voice Response for AIX:
Configuring the System guide.
14 Installation
3. Save a copy of the WebSphere Voice Response application data to a file or
tape by running the saveDT command on the system that was the server.
This task is described in “Saving your current data” on page 36.
4. Restore this data to any stand-alone system by using the restoreDT
command. This task is described in “Restoring saved data after migrating”
on page 77.
5. To complete the conversion process, remove the NFS mounts from the
former client nodes, and remove the NFS exports from the former server
node. These tasks are described in the WebSphere Voice Response for AIX:
Configuring the System guide.
Software prerequisites
You need to make sure that the operating system and other licensed program
products are at the required level before beginning to install the WebSphere
Voice Response software.
The operating system
The operating system must be AIX Version 6.1, Technology Level 03, Service
Pack 01, or higher.
The output from the command oslevel -s should look like 6100-03-01-nnnn,
where nnnn is a four-digit date code.
To check whether you have the required level installed, you can list the latest
level of all filesets by typing the following command and pressing Enter:
lslpp -L "bos.*" | more
At least the bos.rte fileset must be at the required level.
If you do not have the required level of AIX installed, you must upgrade the
operating system before installing WebSphere Voice Response or any other
LPPs you require. However, if you are migrating in-place from a previous
release of WebSphere Voice Response or DirectTalk, do not install the new
level of AIX until you have first saved your data (see Chapter 3, “Software
installation,” on page 31 for instructions on how to do this).
When installing or upgrading AIX you do not need to select all the filesets.
Table 1 on page 16 shows the filesets you need to install in addition to the
minimum AIX operating system. All other AIX filesets required by WebSphere
Voice Response are provided on the WebSphere Voice Response installation
CD-ROM and will be installed automatically during the WebSphere Voice
Response installation process.
Table 1. Base operating system filesets required for WebSphere Voice Response
Name Description
Mandatory filesets X11.fnt.coreX at level AIXwindows® x consortium fonts
(in addition to the 6.1.0.0 or higher.
minimum AIX
operating system) X11.samples.lib.Core (at AIXwindows sample x consortium
6.1.1.0 or higher) core libraries binary/source
Binder and loader commands

bos.rte.bind_cmds (at
6.1.3.0 or higher)
devices.artic960.rte (at
6.1.3.0 or higher) IBM ARTIC960 runtime support
X11.vfb (at 6.1.2.0 or Virtual frame buffer software

higher)
bos.adt.base (at 6.1.3.0 or Base application development

higher)
bos.adt.debug (at 6.1.3.0 Base application development

or higher) debugger
bos.adt.prof (at 6.1.2.0 or Base profiling support

higher)
bos.adt.lib (at 6.1.2.0 or Base application development

higher) library
Filesets required for bos.net.tcp.server (at TCP/IP server support

TCP/IP over a 6.1.3.0 or higher)
token-ring network
X11.base.rte (at 6.1.3.0 or X Server terminal software (part
higher) of the AIX server software)
X11.msg.en_US.base.rte Xstation Manager messages in

(at 6.1.0.0 or higher) U.S. English (part of the AIX
Server software)
Filesets required for bos.net.tcp.server TCP/IP server support

TCP/IP over an
Ethernet network
X11.base.rte X Server terminal software (part
of the AIX Server software)
X11.msg.en_US.base.rte Xstation Manager messages in

U.S. English (part of the AIX
Server software)
Filesets required for bos.dlc.token or Token-Ring Data Link Control or

Communications bos.dlc.sdlc SDLC Data Link Control
Server
16 Installation
Table 1. Base operating system filesets required for WebSphere Voice
Response (continued)
Name Description
Filesets required for bos.dlc.token Token-Ring Data Link Control or
3270 servers or bos.dlc.sdlc SDLC Data Link Control
Filesets required for bos.net.tcp.server TCP/IP Server Support

system management
with SNMP
Other licensed program products

Depending on how you want to use WebSphere Voice Response, you might
need to install some other licensed program products before installing
WebSphere Voice Response. Table 2 shows which products you need to install
for using different WebSphere Voice Response functions.
Table 2. Licensed program products required
Function Product Version
License Use Management GUI License Use Runtime 4.6.8.13 - 6.1.0.221
supplied free with AIX
Include the filesets

ifor_ls.base.cli and
ifor_ls.java.gui
This is a mandatory prerequisite

for the dirTalk.DT.rte fileset.
In smitty, the select:

1. ifor_ls.java
2. ifor_ls.msg.en_US or the
appropriate file for the
national language you require
(for example,
ifor_ls.msg.Ja_JP for
Japanese).
Developing custom servers IBM XL C/C++ Enterprise Edition 9.0.0.2
using C++ language for AIX compiler
Must be purchased separately.
Table 2. Licensed program products required (continued)
Function Product Version
Using the 3270 feature Communications Server for AIX -
must be purchased separately. 6.3.1.0
include the filesets:

v sna.rte
v sna.lu0
v sna.msg.en_US.rte
Using VoiceXML or the Java IBM Developer Kit and Runtime 6.0, Service
API for AIX, Java Technology Edition Refresh 7 (SR7)
2
(32-bit)
(also known as IBM 32-bit SDK

for AIX, Java Technology Edition.)
Supplied free with AIX or as a

free download.
1. To download LUM Runtime 4.6.8.13 for AIX:

a. Visit https://www14.software.ibm.com/webapp/iwm/web/reg/
pick.do?lang=en_US&source=lum
b. If not registered, do so to obtain an IBM UserID.
c. Login using your IBM UserID and password.
d. Select Version 4 and click Continue.
e. Find License Use Management Runtime for AIX, 4.6.8 FP13 in the list
displayed.
f. Select all packages for download, including:
v ifor_ls.base_468FP13
v ifor_ls.java_468FP13
v ifor_ls.msg.en_US_468FP13 (if you are using English)
g. Click Download now.
2. To download the base Java 6 SDK (6.0.0.0):
a. Visit http://www.ibm.com/developerworks/java/jdk/aix/
service.html.
b. Select Java 6 32-bit SDK. A DeveloperWorks login ID is required, so
register if necessary.
Note: Unless greater than 4GB address space is required, the 32-bit
Java 6 JVM (32-bit) generally outperforms the 64-bit JVM (64-bit) in
standard configurations.
18 Installation
c. To download SR7 (6.0.0.175) go to Fix Info on the same page. Note that
to install 6.0.0.175, the base SDK 6.0.0.0 must be installed first.
Alternatively, if the AIX 6.1 Expansion Pack CD that you received with
AIX 6.1 is available, and the version of Java 6 on there is 6.0.0.75 or less,
you can install it from the CD, and then apply fixes (downloaded as
described previously) to bring it to 6.0.0.175.
Important notes about using WebSphere Voice Response

When using WebSphere Voice Response, note:
v Look at any readme files in the /usr/lpp/dirTalk/readme directory for the
latest information. This information supersedes what you see in the product
documentation and online help.
There is also some information in the readme files about system prompts
supplied in various languages.
v The setting for umask must be 022 during any installation process, for
example, installation of WebSphere Voice Response, applying PTFs, or
importing WebSphere Voice Response items such as custom servers. If
umask is not set to 022, this can result in failures at runtime.
v Even if you are not using the dtuser AIX account to run WebSphere Voice
Response (see “User ID ” on page 5), you must have a dtuser account
before you can install a PTF. If you do not already have an account of this
name, use smitty or the mkuser command to create it.
v It is recommended that you only stop WebSphere Voice Response by
selecting one of the Shutdown options on the Administration menu of the
Welcome window (see “Shutting down WebSphere Voice Response” on
page 122), or by using the DT_shutdown utility (see “Shutting down
WebSphere Voice Response automatically on AIX shutdown” on page 124).
You should not stop the system, for example, by pressing
Ctrl+Alt+Backspace, without shutting WebSphere Voice Response down
first.
Although Ctrl+Alt+Backspace shuts down AIXwindows, it does not stop
the background processes. In addition, when you log on again, at least one
buffer is lost. If you continue to do this, it is possible to use up the buffer
pool. For these reasons, stopping the X server without shutting down
WebSphere Voice Response first is not recommended.
v For correct operation of various WebSphere Voice Response windows, the
window manager should be set to use the click to focus policy. This is the
default policy for the Common Desktop Environment. If you are using a
different desktop GUI you might need to manually change the focusing
policy.
v On a production system, it is recommended that you run WebSphere Voice
Response from an AIXwindows environment, rather than from the
Common Desktop Environment (CDE).
v On a production system, it is advisable to disable any screen savers
(otherwise known as screen blankers). A screen saver is an application that
is activated after a specified period during which no user interaction with
the mouse or keyboard occurs; the screen saver is deactivated by a mouse
movement. On deactivation, a significant amount of X activity occurs at
very high processor priority, causing major disruption to WebSphere Voice
Response telephony activity. Calls in progress are interrupted because of
trunks and channels temporarily being disabled. Normally these effects
occur only after a long period of screen saving (an hour or more), but it is
sensible to disable any screen savers, such as the standard desktop screen
saver that comes with AIX, on a production system.
As an alternative, if your display has a power-management feature,
configure that to switch off the screen after a period of no user interaction.
20 Installation
Chapter 2. Connecting WebSphere Voice Response to the
telephone network
Voice over IP configurations: As an alternative to using dedicated switched
telephony voice channels to perform your telephony voice communications, as
described below, you can use Voice over IP over a standard Ethernet IP
network by installing a Digital Telephony Ethernet Adapter (DTEA) or the
Digital Telephony No Adapter (DTNA) software implementation of a DTEA
adapter. Details of how to set up these types of configuration are provided in
the WebSphere Voice Response for AIX: Voice over IP using Session Initiation
Protocol book.
This chapter describes how to connect WebSphere Voice Response to the

telephone network. The chapter starts with background information:
v “What connects to what?”
v “Digital interface cables for WebSphere Voice Response” on page 25
This chapter also describes the following tasks:

v “Connecting a DTTA” on page 25
v “Connecting an SMDI, SMSI, or VMS exchange data link” on page 26
v “Connecting an ACL exchange data link” on page 28
Note: For country-specific rules for connecting WebSphere Voice Response to

the telephone network, refer to the README_homologation.xxxx file, where
xxxx is the country/region identifier; for example, UK for the United
Kingdom. The file is located in the /usr/lpp/dirTalk/homologation directory.
What connects to what?

This section introduces the connections you have to make to ensure that
WebSphere Voice Response is connected to the telephone network:
v “Digital trunk connections”
v “H.100 connections” on page 23
v “Exchange data link connections” on page 23
Digital trunk connections
To transmit voice signals to, and receive voice signals from, the telephone
network, one or more digital trunk adapters must be installed in your pSeries
system unit. There is one type of digital trunk adapter:

v The Digital Trunk Telephony Adapter (DTTA): full name IBM Quad Digital
Trunk Telephony PCI Adapter.
Table 3 shows the maximum number of digital trunk adapters you can use in
the currently supported system units.
Table 3. Digital trunk adapters supported by System p5, pSeries and RS/6000 models
used with WebSphere Voice Response
System p5, pSeries, or RS/6000 model Maximum number of
DTTAs
pSeries 615 Models 7029-6C3 and 6E3 Three
pSeries 620 Models 7025-6F0 and 6F1 Not supported
pSeries 630 Models 7028-6C4 and 6E4 Four
pSeries 650 Model 7038-6M2 Four
System p5-520 Model 9111-520 Three
System p5-550 Model 9113-550 Four
System p5-570 Model 9115-570 Not supported, but see
pSeries 7311-D20 I/O
Drawer below
System p6-520 Model 8203-E4A Two
System p6-550 Model 8204-E8A Two
System p6-570 Model 9117-MMA Not supported, but see
next row
pSeries 7311-D20 I/O Drawer on System p6-520, p6-550, Four per i/o drawer
p6-570
pSeries 7311-D20 I/O Drawer on System p5-520, p5-550 or Four per i/o drawer
p5-570
pSeries 7311-D20 I/O Drawer on pSeries 650-6M2 Four per i/o drawer
pSeries 7311-D20 I/O Drawer on pSeries 630-6C4 Four per i/o drawer
pSeries 7311-D10 I/O Drawer on pSeries 650-6M2 Three per i/o drawer
Intellistation 9114 Model 275 One
WebSphere Voice Response Version 6.1 also supports LPAR technology, to a

maximum of two LPARs per pSeries system. With LPARs the total number of
DTTAs supported in a 7311-D20 drawer is increased to 7.
For the most recent information about adapter support, check the following
Web page:
http://www.ibm.com/support/docview.wss?rs=761&uid=swg21253839
22 Installation
Each digital trunk adapter can support up to four trunk connections to the
telephone network. Each trunk can carry 24 (T1) or 30 (E1) calls
simultaneously.
The trunk connections are made in one of the following ways:

v A direct T1 or E1 connection to the switch.
v A T1 or E1 connection to a channel bank connected to a switch.
v A T1 connection to a channel service unit (CSU) connected to the switch.
v A T1 connection to a CSU connected to a channel bank, connected to the
switch.
Any one WebSphere Voice Response system can support either T1 or E1

connections, but not both. The necessary telecommunications cables are
described in more detail in “Digital interface cables for WebSphere Voice
Response” on page 25.
H.100 connections
The DTTA is an H.100 adapter. All H.100 adapters in a pSeries computer must
be connected together using an H.100 top-connector cable. This is to
synchronize the adapters and to support functions such as speech recognition
and channel-to-channel connection (tromboning). H.100 is the industry
standard for PCI systems.
Before you can connect your H.100 adapters together, note the following:
v Adapters should be in adjacent slots in the system unit.
v The termination jumper must be set for the adapter at each end of the
chain. For details see IBM Quad Digital Trunk Telephony PCI Adapter (DTTA):
Installation and User's Guide.
No H.100 cables are supplied with the DTTA; you must order them, as
described in WebSphere Voice Response for AIX: General Information and Planning.
The DTTA has an H.100 connector on the base card (nearest to the front of the
pSeries computer).
Exchange data link connections
When using channel-associated signaling (CAS) to connect to some switches

(including Avaya, Ericsson MD110, Nortel DMS, and Siemens Hicom), an
exchange data link is required to carry signaling information. In all other
cases, including ISDN, the signaling information is carried by the digital trunk
connection and an exchange data link is not required.
Chapter 2. Connecting WebSphere Voice Response to the telephone network 23

The exchange data link is an EIA232 (RS-232) serial connection which can be
either:
v A direct connection (using the appropriate serial cable); see Figure 1.
pSeries
Exchange Data Link
RS232 (V24) cable
WebSphere
Voice
Response
Digital Trunk Connection
Switch
Figure 1. Exchange data link (direct connection)
v An indirect connection (using two modems); see Figure 2.

Use an indirect connection when:
– The distance between the pSeries computer and the switch exceeds the
capabilities of your cable.
– You are connecting the pSeries computer to a central office exchange; in
these circumstances you should obtain advice from your telephone
network provider before following the instructions given in this book.
Exchange Data Link pSeries
Modems
WebSphere
Voice
Digital Trunk Connection Response
Switch
Figure 2. Exchange data link (indirect connection)
Two exchange data link implementations are supplied with WebSphere Voice
Response, providing the following kinds of link:
24 Installation
Bisynchronous link
This implementation supports the Siemens HiCom 300 interface,
Application Connectivity Link (ACL), which requires a bisynchronous
communications link between the switch and the pSeries computer.
Asynchronous link
This implementation supports:
v NORTEL's Simplified Message Desk Interface (SMDI)
v AT&T's Simplified Message Service Interface (SMSI)
v Ericsson's Voice Message Service (VMS)
You can also write your own signaling process to support an exchange data
link (refer to the WebSphere Voice Response for AIX: Programming for the
Signaling Interface book for details).
The WebSphere Voice Response for AIX: General Information and Planning book
contains more information about using the exchange data link. This section
explains how to physically connect the link. The equipment required and
procedures to be followed vary according to the type of exchange data link
(SMDI, SMSI, VMS, or ACL).
For instructions see “Connecting an SMDI, SMSI, or VMS exchange data link”
on page 26 or “Connecting an ACL exchange data link” on page 28.
Digital interface cables for WebSphere Voice Response

WebSphere Voice Response needs a telecommunications cable to connect each
digital trunk adapter to the telephone network. The cables that are available
are described in the WebSphere Voice Response for AIX: General Information and
Planning book.
T1 digital interface cables for WebSphere Voice Response
Connect each DTTA to the telephone network using a standard RJ45 cable.
E1 digital interface cables for WebSphere Voice Response
For channel associated signaling (CAS) and ISDN, connect each DTTA to the
telephone network using a standard RJ45 cable.
Connecting a DTTA
If you are planning to use an exchange data link, go to “Exchange data link
connections” on page 23.

Prerequisites
v Read the background information in “What connects to what?” on page 21.
v Install the DTTA in the system unit.
v Connect the adapters together using H.100 cables (see “H.100 connections”
on page 23).
Procedure
1. Power off the pSeries computer.
2. There are four RJ45 connectors on the back of each DTTA card, numbered
0, 1, 2, and 3. These will correspond to WebSphere Voice Response trunks
numbered:
v On the first adapter: 1, 2, 3, and 4
v On the second adapter: 5, 6, 7, and 8
v On the third adapter: 9, 10, 11, and 12
v On the fourth adapter: 13, 14, 15, 16
To connect each DTTA to the telephony network, plug an RJ45 cable into
the appropriate connector on the back of the card, and then plug the other
end of the cable into the telephony network.
3. When you have connected all DTTAs to the network, power on the pSeries
computer.
If you need to install software, go to Chapter 3, “Software installation,” on

page 31. After this you need to configure the telephony environment, as
described in the WebSphere Voice Response for AIX: Configuring the System book.
Note: On some RS/6000 models that are supported by WebSphere Voice

Response , the logical slot numbers are not the same as the physical slot
numbers. This could cause confusion when trying to identify specific
adapters.
To locate a DTTA, click Configuration --> Pack Configuration, and then

Trunk Interface Parameters for one of the trunks that is on the adapter you
want to test. From the Trunk Interface Parameters window displayed, click
Locate Adapter to cause the LED on the back of the card to flash for five
seconds. See also the section “Running hardware diagnostic procedures” in
the WebSphere Voice Response for AIX: Problem Determination book.
Connecting an SMDI, SMSI, or VMS exchange data link

Connecting the WebSphere Voice Response end
26 Installation
Prerequisites for a direct connection
v An EIA 232 (V.24) null modem cable long enough to connect the pSeries
computer to the switch.
v If your model of pSeries computer has rectangular 10-pin serial port
connectors, a 10-pin to 25-pin 100-millimeter (4-inch) converter cable.
v If necessary, a converter cable for the switch end.
Procedure for a direct connection

1. Locate one of the two serial ports on the back of the pSeries computer.
2. Connect one end of the null modem cable to the port, using a 10-pin to
25-pin converter cable if necessary.
3. Connecting the switch end: Connect the other end of the null modem
cable to the switch, again using a converter cable if necessary. (To locate
the appropriate port on the switch, see the manufacturer's instructions.)
Next step: If you need to install software, go to Chapter 3, “Software

installation,” on page 31. After this you need to define the exchange data link
to AIX, as described in “Defining an exchange data link to AIX” on page 90.
Prerequisites for an indirect connection

v Two compatible modems.
v Cabling as required to connect the two modems (for details, refer to the
modem manufacturer's instructions).
v An EIA 232 (V.24) cable long enough to connect one of the two modems to
the switch.
v An EIA 232 (V.24) cable long enough to connect the other modem to the
pSeries computer.
v If your model of pSeries computer has rectangular 10-pin serial port
connectors, a 10-pin to 25-pin 100-millimeter (4-inch) converter cable.
v If necessary, a converter cable for the switch end.
Procedure for an indirect connection

1. Connecting the WebSphere Voice Response end: Locate one of the two
serial ports on the back of the pSeries computer.
2. Using an EIA 232 (V.24) cable (and, if necessary, a 10-pin to 25-pin
converter cable) connect one of the two modems to the port.
3. Connecting the switch end: Use the other EIA 232 (V.24) cable (plus a
converter cable if necessary) to connect the second modem to the switch.
To locate the appropriate port on the switch, see the manufacturer's
instructions.
4. Linking the two modems: Connect and configure the two modems
according to the manufacturer's instructions.

Connecting an ACL exchange data link

Connecting the WebSphere Voice Response end
Prerequisites for a direct connection

v A conventional EIA 232 (V.24) serial cable long enough to connect the
pSeries computer to the HiCom switch.
v An IBM Multiprotocol Communications Controller (or an equivalent
adapter that supports bisynchronous serial communications).
Procedure for a direct connection

1. Install the communications adapter in a vacant expansion slot in the
pSeries computer. For details of this procedure, see the instructions
supplied with the computer and with the adapter.
2. Connect one end of the serial cable to the adapter's serial port.
3. Connecting the switch end: Connect the other end of the cable to an LCU
card in the HiCom 300 switch. Note that the port needs to be configured
as an ACL port; for details, see the documentation supplied with the
switch.

Prerequisites for an indirect connection

1. Two compatible modems.
2. Cabling as required to connect the two modems (for details, refer to the
modem manufacturer's instructions).
3. Two HiCom modem cables, long enough to connect one of the two
modems to the switch, and the other to the pSeries computer.
4. An IBM Multiprotocol Communications Controller (or an equivalent
adapter that supports bisynchronous serial communications).
Procedure for an indirect connection

1. Connecting the WebSphere Voice Response end: Install the
communications adapter in a vacant expansion slot in the pSeries
computer. For details of this procedure, see the instructions supplied with
the computer and the adapter.
28 Installation
2. Use a HiCom modem cable to connect one of the two modems to the
adapter's serial port.
3. Connecting the switch end : Use the other HiCom modem cable to
connect the second modem to an LCU card in the HiCom 300 switch,
using a converter cable if necessary. Note that the port needs to be
configured as an ACL port; for details, see the documentation supplied
with the switch.
4. Linking the two modems: Connect and configure the two modems
according to the manufacturer's instructions.


30 Installation
Chapter 3. Software installation
This chapter sets out detailed instructions for installing a new release of the
WebSphere Voice Response software, or migrating from a previous release of
the product:
1. “Archiving your reports and log files” on page 32
2. “Exporting your application data from the old system” on page 33
3. “Starting the migration process” on page 34
4. “Saving your current data” on page 36
5. “Preparing to migrate VoiceXML and Java applications” on page 38
6. “Setting up the AIX account (single system image only)” on page 40
7. “Starting installation of WebSphere Voice Response” on page 42
8. “Setting up the AIX account (standalone system only)” on page 49
9. “Installing PTFs for WebSphere Voice Response” on page 50
10. “Restarting AIX” on page 51
11. “Creating the WebSphere Voice Response database” on page 51
12. “Updating the WebSphere Voice Response database” on page 52
13. “Setting ownership of the DTTAs” on page 53
14. “Running hardware diagnostic procedures” on page 55
Where to start?
In this chapter you will either be:
v Installing WebSphere Voice Response for the first time
v Migrating from a previous release
Generally, you should follow the steps in the order they are set out in this
chapter, checking the “Next Step” headings to see where to go next. The
“Prerequisites” headings also provide a reminder of what steps you need to
have performed already.
If you are installing or upgrading to include DTNA or DTEA Voice over IP,
read this chapter in conjunction with the WebSphere Voice Response for AIX:
Voice over IP using Session Initiation Protocol book.
If you are installing WebSphere Voice Response for the first time
v If you are installing WebSphere Voice Response for the first time, you
should start with “Starting installation of WebSphere Voice Response” on
page 42.

v If you are installing WebSphere Voice Response for the first time on a single
system image, you should start with “Setting up the AIX account (single
system image only)” on page 40.
If you are migrating from a previous release
Before starting the migration process, ensure that you first make a backup of
your system data. The different methods for doing this are described in
“Options for backing-up data prior to migration” on page 8.
v To backup your data, begin with “Archiving your reports and log files”
below.
v If you are installing WebSphere Voice Response on a non-production system
before subsequently migrating your applications from your production
WebSphere Voice Response system, go to “Starting installation of
WebSphere Voice Response” on page 42.
Note: The tasklist.data file is overwritten during migration, so you

should make a note of the entries in your file before migration, then update
tasklist.data when migration is complete. Do not back up and restore this
file - new processes might be added during migration for new function. The
tasklist.data file is in the $SYS_DIR directory.
Archiving your reports and log files

When you use saveDT to back up your data, this saves all your archived
reports and log files. If you want to also migrate your current report statistics
and log files, you need to archive them first, before you start the migration
process.
Note that if you archive before the end of the reporting period, the system
overwrites the archive file for the previous period. To safeguard
previously-archived data, make a backup of the archived files before you use
the following procedure.
1. Archiving report statistics: From the Welcome window, select Operations
—> Statistics.
2. Click Object Type —> Report.
3. Press Select in Report Name.
The system displays a list of reports.
4. Select a report, then click OK.
The system archives the report.
5. Repeat steps 2 through 4 for each report you want to archive.
6. Archiving log files: Click Object Type —> Logs.
7. Press Select in Log Name.
The system displays a list of log files.
32 Installation
8. Select a log file, then click OK.
The system archives the log file.
9. Repeat steps 6 on page 32 through 8 for each log file you want to
archive.
10. Close the Statistics window.
Next step: “Starting the migration process” on page 34.
Exporting your application data from the old system

The following types of objects cannot be exported, so you need to use
makesysb or saveDT if you want to backup these objects:
v Voice messages
v Audio names
v User greetings
v Distribution lists
v System parameters
Procedure
If you are unfamiliar with this procedure, you should use mksysb or saveDT
instead (see “Saving your current data” on page 36).
You should do a full export of all your applications and any applications they
require. For instructions on exporting applications, see the WebSphere Voice
Response for AIX: Designing and Managing State Table Applications book.
The export utility uses the AIX tar command to save your application data in
a single file, using the United States Tape Archiver format (USTAR). This
format supports:
v Directory path names with a maximum of 155 characters
v File names with a maximum of 100 characters
You need to ensure that the files you are saving, and the directory you are
saving to, do not exceed these limits.
Next step: “Starting the migration process” on page 34
Chapter 3. Software installation 33

Starting the migration process
This procedure begins the migration process. The migration instructions
provided in this book refer only to migration from WebSphere Voice Response
Version 4.2. If you are upgrading to Version 6.1 from any earlier release,
please contact your IBM representative for advice. WebSphere Voice Response
Version 4.2 must be at fix level 4.2.0.499 prior to migrating to WebSphere
Voice Response Version 6.1.
Follow the procedure described below before you start to install the new
software.
Before starting
You should ensure that:
v You have decided on your migration strategy (see “Migration” on page 7).
v If you have decided to use saveDT for backing up data, you have archived
your reports and logs (see “Archiving your reports and log files” on page
32).
v You have warned your users that you are going to shut down WebSphere
Voice Response.
Procedure
Use the following procedure when you are ready to start the migration.
1. Preparing a regression test to check for successful migration : You can
either use one of your own applications, or one of the sample applications
provided, to record items such as:
v An audio name
v A user greeting
v A voice message
v A voice segment
Ensure that you include the date and time in the items you record. Also,
export or save these items if you are exporting or saving your real data.
(Note that audio names, user greetings, and voice messages cannot be
exported, so you need to record a voice segment if you want to use the
application export–import method.)
You will use these items to test that you can still access your data after the
migration.
Depending on the pSeries model, this can take from 20 minutes to over
2 hours, but it means that you can restore the system if anything goes
wrong. Doing a system backup now could save you a lot of time later.
2. Backing up the AIX system image: Click Operations —> Quiesce
Shutdown.
3. When WebSphere Voice Response has terminated, use the DT_shutdown
command to ensure any long-running tasks are ended.
34 Installation
4. Backup the system image. Use the mksysb command to back up the data
in the root volume group. Use the savevg command to back up other
volume groups. See the AIX: Installation Guide, for further information
about how to use these commands.
5. Configuring custom servers: Restart WebSphere Voice Response.
6. Custom servers supplied with WebSphere Voice Response are ready to run
without any special action. However, if you are migrating from a previous
release of WebSphere Voice Response, or if you are migrating to a later
version of AIX, you must rebuild and reinstall any custom servers that
were not supplied with the product. Therefore, if you have configured a
custom server to start automatically whenever WebSphere Voice Response
is started, you need to change this configuration so that WebSphere Voice
Response will not attempt to start the server before you have had a chance
to rebuild it for use with the current release.
To change the custom server configuration:
a. Click Operations —> Custom Server Manager.
The system displays the Custom Server Manager window.
b. If the IPL Status field for a server shows the value Autoexec, click on
the field, then click Auto-start off from the pop-up menu. Continue
until all servers have the status Installed.
c. Close the window.
7. Changing the operating status: To avoid incurring telephony errors when
you start WebSphere Voice Response, set the value of the Operating Status
parameter for all trunks to Defined.
To change the parameter:
a. Click Configuration —> Pack Configuration, then click Change.
b. Click the Operating Status push button for the first pack.
The system displays the Operating Status window.
c. Click Defined, then click OK.
d. Repeat steps 7b and 7c until all trunks have the Operating Status
Defined.
8. Shutting down : When you are ready to begin the migration process, click
Operations —> Quiesce Shutdown.
Next step:
v If you are going to use saveDT to backup data, go to “Saving your current
data” on page 36.
v Otherwise, go to “Starting installation of WebSphere Voice Response” on
page 42.
Note: WebSphere Voice Response must remain shut down while you install
the new software.

Saving your current data
Use this procedure if you have decided to use saveDT to backup your data
prior to migration (as described in “Options for backing-up data prior to
migration” on page 8).
Prerequisites
When backing up your data, ensure that you are using the level of the
saveDT utility that is compatible with WebSphere Voice Response Version 6.1,
rather than the level provided with the version from which you are migrating.
To obtain the latest version of saveDT before migrating to WebSphere Voice
Response Version 6.1, please update WebSphere Voice Response Version 4.2 to
at least fix level 4.2.0.499 and use the installed version of the saveDT script. In
WebSphere Voice Response Version 6.1, saveDT only supports the tar format.
Before you start the following procedure, note the following prerequisites:
v If you want to save the data from a standalone WebSphere Voice Response
system (that is, a system that is not part of a single system image), ensure
that WebSphere Voice Response is not running.
v If you want to save the data used by a single system image, you must
perform this procedure on the database server node of the single system
image. Before you start this procedure, ensure that WebSphere Voice
Response is not running on any nodes of the single system image, and that
no other processes are connected to DB2.
v If you want to save your current reports and log files you must archive
them first (as described in “Archiving your reports and log files” on page
32), as saveDT does not save current statistics information.
v If you are saving to tape, you need a suitable drive attached to the pSeries
computer.
Procedure
Start
1. Log on to AIX as root.
2. Creating a directory or file system: If you want to save your current data
on the hard disk, create a directory, or even a file system, in which to store
the file. Make sure the location is not within either the /home/dirTalk or
/usr/lpp/dirTalk directories. If you are upgrading the AIX operating
system, make sure you do not save data to any hard disk location that
could be affected by the AIX upgrade.
Use tape if you are uncertain, particularly if you are upgrading the
operating system.
3. Changing to a working directory: Change to an appropriate working
directory, where the utility can put working files. Do not use a directory in
/home/dirTalk or /usr/lpp/dirTalk. For example, use the$HOME directory
for dtuser, or use /tmp:
36 Installation
cd /tmp
4. Setting up the environment : Type the following command and press
Enter:
. /usr/lpp/dirTalk/tools/vae.setenv
Leave a space between the period and the slash before usr.
5. Type the following command and press Enter:
echo $VAE
If the environment is properly set up, the system should display the
following message:
/usr/lpp/dirTalk
6. Checking the current directory: Type the following command and press
Enter:
pwd
The system displays the path for your current directory. Make sure it is
not within the /home/dirTalk or /usr/lpp/dirTalk directories.
7. Saving the data: Type the following command and press Enter:
saveDT
The system displays the Save DirectTalk Data Script menu:
Save DirectTalk Data Script--Backup Device
Total amount of space needed to save DirectTalk: 3393 Kbytes
1) Diskette (Recommended only for Small Amount of Data)
2) Hard Disk file (using tar)
3) Tape (using tar)
4) Quit
Select device type: (type ENTER to list choices) >
8. The menu shows the amount of space you need to save your application
data. Ensure that you have enough space before continuing.
9. Type the number for the option you want to use, then press Enter. The
system prompts you for the device, directory, or file name, as appropriate.
Note: Options 2 and 3 use the AIX tar command to save your application
data in a single file, using the United States Tape Archiver format
(USTAR). This format supports:
v Directory path names with a maximum of 155 characters
v File names with a maximum of 100 characters.
If you select one of these options, you need to ensure that the files you are
saving, and the directory you are saving to, do not exceed these limits.
Next step:
v If you have Java or VoiceXML applications, go to “Preparing to migrate
VoiceXML and Java applications” on page 38.

v If you want to install WebSphere Voice Response on a single system image,
go to “Setting up the AIX account (single system image only)” on page 40.
v Otherwise, go to “Starting installation of WebSphere Voice Response” on
page 42.
Preparing to migrate VoiceXML and Java applications

You should read this section only if you have existing VoiceXML or Java
applications.
As was explained in “Planning the migration of Java and VoiceXML

applications” on page 9, if you are already using any VoiceXML 2.0, you do
not need to make any changes to them before they can be used with
WebSphere Voice Response Version 6.1. Note that if you are still using
VoiceXML 1.0 applications, these are not supported in WebSphere Voice
Response Version 6.1.
However, to continue using the function in VoiceXML 1.0 applications, you

can upgrade them to the VoiceXML 2.0 specification by using the migration
tool that is provided in the WebSphere Voice Toolkit Version 6.0.1, which can
be downloaded free from:
http://www.ibm.com/software/pervasive/voice_toolkit
Some editing may be required and you will have to make a change to the
AppName entry in the configuration file (see WebSphere Voice Response for AIX:
Deploying and Managing VoiceXML and Java Applications for details).
Although Java applications that were developed using JavaBeans can still run,
the programming tools used with this method are no longer supported, so
you should develop any new Java applications using the Java API. If you are
currently using the old Java and VoiceXML Environment (DTBE) that
supported VoiceXML 1.0 applications, you must remove it before you can start
the migration to WebSphere Voice Response Version 6.1. Before doing this,
backup any voice segments and configuration files (.cff) that you use, and
then restore them after migration. The actions are documented in the
following instructions:
Backing-up VoiceXML and Java data

1. Log on as dtuser. Type the following command and press Enter:
cd /var/dirTalk/DTBE/native/aix
2. All users: to prevent the new default.sample.cff from being overwritten
when you restore the old one, type the following command (substituting
newname with a name of your choice) and press Enter:
cp default.sample.cff newname.cff
38 Installation
3. All users: to back up your .cff files, type the following command
(substituting backupfile with a name of your choice) and press Enter:
ls *.cff | grep -v -F default.sample.cff | xargs tar -cvf backupfile.tar
4. Java users only: to add your voice segments to the backupfile.tar file, type
the following command and press Enter:
find /usr/lpp/dirTalk/db/current_dir/voice/ext/%A | xargs tar -uvf backupfile .tar
5. Move the following files to a safe place (for example, on another system,
on a writable CD, or on tape):
v The backupfile you just created.
v If you are going to install a new version of AIX, your applications
programs and application-related data.
Removing the previous Java and VoiceXML environment (DTBE)

1. If WebSphere Voice Response is running, shut it down by entering:
wvrstop -c
2. Log on as root if you are not logged on already.
3. Type smitty remove and press Enter.
4. In the Remove Installed Software panel:
In the SOFTWARE name field, press F4, and from the list select all files
that start with dirTalk.DTBE .
In the REMOVE dependent software? field, select yes.
Press Enter
5. Exit from SMIT
Check level of Java prior to new installation

1. Check that you have the correct version of Java installed by entering:
java -version
If the data that is displayed includes the following (build
pap3260sr7-20091215_02(SR7)), you have Java 6.0 SR7 installed. If you do
not have this level, you must install it now. You can download it from
http://www.ibm.com/developerworks/java/jdk/aix/service.html .
Next step:
v If you want to install WebSphere Voice Response on a single system image,
go to “Setting up the AIX account (single system image only)” on page 40.
v Otherwise go to “Starting installation of WebSphere Voice Response” on
page 42.

Setting up the AIX account (single system image only)
If you are installing WebSphere Voice Response on a standalone system, this
section does not apply. Instead, go direct to “Starting installation of
If you are installing in an SSI, you need to follow this procedure whether you
are installing WebSphere Voice Response for the first time, or migrating from
a previous release.
Setting up the AIX account for a new single system image
If you are creating a new single system image using pSeries computers that
do not yet have WebSphere Voice Response installed, you need to create a
new AIX account for all the nodes of your single system image to use. When
you create the accounts you need to make sure that the following are identical
on every system (this ensures proper operation of DB2 and NFS on all
systems of the single system image):
v User name
v User ID
v Group name
v Group ID
Procedure
1. Log on to AIX as root, if you are not logged on already.
cat /etc/passwd | awk -F":" ’{print $3 " " $1}’ | sort -n
The system will display a list of all user names and IDs on this machine.
3. Repeat steps 2 and 3 on each machine in your single system image and
choose a number which is not currently used as a user ID on any of your
machines.
4. On each machine, type the following command and press Enter:
mkuser id=userID dtuser
Where userID is the number you chose in step 4.

This command will create an AIX account called dtuser in the group staff.
If you want to choose a different name for your AIX account, you must
ensure that the name of your account contains lowercase characters only.
You should not change the group. Throughout this book, the WebSphere
Voice Response account is referred to as dtuser.
40 Installation
Changing existing AIX accounts for a new single system image
If you are creating a new single system image from pSeries computers that
already have WebSphere Voice Response installed, you do not need to create a
new AIX account on all the nodes. In this case, you must change the existing
accounts so that they are all the same.
You must ensure that the following are identical on every system:
v User name
v User ID
v Group name
v Group ID
The way you do this will depend on how your system is configured for
products other than WebSphere Voice Response, but here is an example of
how to change the numeric account identifier:
1. Edit the file /etc/passwd and find the line that contains the numeric
identifier. For example:
dtuser:!:16001:1:Jones:/home/dtuser:/usr/bin/ksh
In this line, the fields are separated by colons (:). In this example, the
fields are:
dtuser The user name
! Encrypted password
16001 Numeric identifier of the user
1 Primary group
Jones Description of the user
/home/dtuser
Name of the home directory
/usr/bin/ksh
The user's shell
Change the numeric identifier (in this example it is 16001) to match that of
the other nodes on the single system image.
2. Change the ownership of all the files owned by this user ID.
One way to change the ownership of files from user ID 16001 to 16000 is
with this command:
find / -user 16001 -fstype jfs -print | xargs -n50 chown 16000
3. If you were running any other applications from user 16001, you may
have to make changes in those applications.

Next step: Go to “Starting installation of WebSphere Voice Response.”
Starting installation of WebSphere Voice Response

This section explains how to begin installing the WebSphere Voice Response
software.
You should use this procedure whether you are installing WebSphere Voice
Response for the first time or whether you are migrating from a previous
release.
Prerequisites
v The CD-ROMs on which the WebSphere Voice Response software was
delivered.
v A suitable CD-ROM drive in the pSeries computer.
v AIX Version 6.1 successfully installed on the pSeries computer (see
“Software prerequisites” on page 15).
v Any other LPPs you require successfully installed on the pSeries computer
(see “Software prerequisites” on page 15).
v A /usr file system on the pSeries computer. (WebSphere Voice Response
cannot run on a diskless client or on a client in an AIX /usr client–server
system configuration.)
v A /home file system on the pSeries computer.
v AIX root user (superuser) privilege.
v If you are installing the software on a pSeries computer on which you have
been running a previous version of WebSphere Voice Response or
DirectTalk, ensure that you have saved or exported your applications and
system data (see “Saving your current data” on page 36 or “Exporting your
application data from the old system” on page 33), and if necessary,
backed-up your Java and VoiceXML data (see “Preparing to migrate
VoiceXML and Java applications” on page 38).
v Make sure that WebSphere Voice Response is not running.
These instructions tell you how to install the software using SMIT with the
smitty command. If you prefer, you can use Easy Install, Install and Update
Software Manager, or the smit command (which runs the Motif-based version
of SMIT).
Installing DB2
Use this procedure to install DB2 for use with WebSphere Voice Response. You
must install DB2 if you are installing WebSphere Voice Response for the first
time or if you are migrating from WebSphere Voice Response Version 4.2.
42 Installation
If a problem occurs during installation, use the information and instructions
in the AIX documentation. Informational and warning messages displayed by
WebSphere Voice Response are explained in the WebSphere Voice Response for
AIX: Problem Determination book.
If you are installing or migrating, do not log in as sudo root.
2. Run the ./usr/local/bin/db2ls command (as root). If the correct version
of DB2 is already installed, this command should return 9.5.0.4 or
higher.
3. Check that you have the correct operating system level (see “The
operating system” on page 15).
4. Making an AIX system backup: If you have made any changes since the
last backup, make a backup copy of the system now. Use the mksysb
command to back up the data in the root volume group. Use the savevg
command to back up other volume groups. See the AIX: Installation
Guide, for further information. If something goes wrong during the
software installation, you can then restore the system.
5. Creating a CD file system: If you already have a CD file system, you can
skip to step 11. Otherwise, type the following command and press Enter:
smitty crcdrfs
6. Press F4 in the DEVICE name entry field to display a list of file systems.
7. Select cd0.
8. In the MOUNT POINT entry field type /cdrom .
9. For Mount Automatically at System Restart select no.
10. Press Enter.
The system creates the CD file system. Review the output when it has
finished.
11. Insert WebSphere Voice Response installation CD labelled “IBM DB2 -
limited use, Version 9.5” into the drive.
12. Mounting a CD: Type the following command and press Enter:
smitty mountfs
13. Press F4 in the NAME of file system to unmount entry field to display a
list of file systems.
14. Select the CD-ROM file system (for example /dev/cd0).
15. Press Enter.
The system mounts the CD. Review the output when it has finished.
16. Press F10 to exit from SMIT.
17. Install the DB2 files from the DB2 CD: Type the following command
and press Enter:
cd /cdrom

./db2_install -p wse -f NOTSAMP -n -b /opt/IBM/db2/V9.5
The installation of DB2 can take between 10 to 30 minutes to complete.

19. When the installation has completed, press F10 to exit from SMIT
20. Type: cd /
21. Type: umount /cdrom
22. Remove the DB2 CD from the drive.
23. Run the ./usr/local/bin/db2ls command (as root) again. If the correct
version of DB2 is correctly installed, this command should return 9.5.0.4
or higher.
If installing WebSphere Voice Response Version 6.1 for the first time
Use this procedure to install the WebSphere Voice Response software when
you have not been using a previous level of the product. You can install all
the mandatory and optional items together, or you can install just the
mandatory items, then install one or more optional items later.
Note: Before continuing, you must have installed DB2 as described in

“Starting installation of WebSphere Voice Response” on page 42.
1. Insert the WebSphere Voice Response installation CD into the drive.
2. Mount the CD by repeating steps 12 on page 43 to 16 on page 43 under
the heading “Mounting a CD”.
cd /cdrom
4. To check for any additional advice or instructions, you should read the
README file in the root directory of the CD-ROM. You can also check
the WebSphere Voice Response support website for the most recent
information. Use your Web browser to visit the support page at
http://www.ibm.com/pvc/products/voice/direct_talk_support.shtml
smitty install_latest
6. In the INPUT device/directory for software field enter . (period) to
indicate your current directory and press Enter.
7. Selecting the filesets: Press F4 in the SOFTWARE to install entry field
to list the filesets in the root directory on the CD-ROM.
The system displays the SOFTWARE to Install menu.
8. Select the following mandatory packages:
v devices.dirTalk.artic960
v devices.iop_rpq
v dirTalk.DT
44 Installation
In addition, select any of the following optional packages.
v devices.dirTalk.BrooktroutFax: Fax device driver.
v devices.iop_rpq.rte: DTEA device driver.
v dirTalk.3270: to support 3270 servers.
v dirTalk.ADSI: to support analog display services interface (ADSI)
phones.
v dirTalk.BrooktroutFax: to support Fax machines.
v dirTalk.VRBE_XML: to support VoiceXML 2.1 and Java API
applications.
v dirTalk.GEOTEL: to support Cisco Intelligent Contact Management
software.
v dirTalk.ISDN.com: to support all ISDN protocols.
v dirTalk.ISDN.ATT: to support AT&T 5ESS and Lucent Definity G3i
switches.
v dirTalk.ISDN.DMS100: to support Nortel DMS-100 and DMS 250
switches.
v dirTalk.ISDN.EuroISDN: to support EuroISDN and E1 QSIG.
v dirTalk.ISDN.INS1500: to support Japan's INS Net Service 1500.
v dirTalk.SP: to support languages other than US English. Not required
for VoiceXML and Java.
v dirTalk.TDD: to support telecommunications devices for the deaf.
v dirTalk.VOIP_SIP: to support Voice over IP (using DTNA or DTEA).
Do not select any other packages. Any other required filesets are installed
automatically.
9. When you have selected the filesets to install, press Enter, and then press
Enter again to actually start the installation process.
The system installs the software. This could take from 10 minutes to 30
minutes, depending on which options you install and the model of
pSeries computer you are using. When the process is complete, OK
appears at the top of the screen. Check the messages at the bottom of the
screen to confirm the successful installation of each selected package.
10. Review the output. It may contain information about changes that were
made during the installation.
If any filesets failed to install due to missing prerequisite AIX filesets,
install the missing filesets from the AIX installation CDs or apply AIX
PTFs to upgrade the filesets to the correct level. Repeat the WebSphere
Voice Response installation.
12. Unmounting the CD:.

a. Move to the root directory by typing the following command and
pressing Enter:
cd /
b. Type the following command and press Enter:
smitty umountfs
c. Press F4 in the NAME of file system to unmount entry field to
display a list of file systems.
d. Select the CD-ROM file system (for example /dev/cd0).
e. Press Enter.
f. Manually eject the CD
13. If you require SS7 D7 enablement: Insert the WebSphere Voice Response
installation CD into the drive, and repeat the actions described in steps 2
on page 44 to 12 on page 45, selecting the fileset:
v dirTalk.SS7_D7
Note: SS7 D7 support is provided through the separately-orderable

PRPQ (7J0465) IBM SS7 Support for WebSphere Voice Response. For details
of installation see SS7 Support for WebSphere Voice Response: SS7 User's
Guide book, GC34-7090.
14. If you require the WebSphere Voice Server (MRCP) Connector: Insert
the WebSphere Voice Response installation CD into the drive, and repeat
the actions described in steps 2 on page 44 to 12 on page 45, selecting the
fileset:
v dirTalk.SpeechClient
For details of how to configure and use the WebSphere Voice Server
Connector, refer to the WebSphere Voice Response for AIX: Deploying and
Managing VoiceXML and Java Applications book.
Next step: Go to “Setting up the AIX account (standalone system only)” on

page 49.
If migrating to Version 6.1 from a previous level of WebSphere Voice
Response
Note: Before continuing, you must have installed DB2 as described in

“Starting installation of WebSphere Voice Response” on page 42.
Use this procedure to migrate from WebSphere Voice Response Version 4.2.
1. Insert the WebSphere Voice Response installation CD into the drive.
2. Mount the CD by repeating steps 12 on page 43 to 16 on page 43 under
the heading “Mounting a CD”.
cd /cdrom
46 Installation
4. To check for any additional advice or instructions, you should read the
README file in the root directory of the CD-ROM. You can also check
the WebSphere Voice Response support website for the most recent
information. Use your Web browser to visit the support page at
http://www.ibm.com/pvc/products/voice/direct_talk_support.shtml
smitty update_all
6. In the INPUT device/directory for software field enter . (period) to
7. The migration utility updates instances of the existing files that it finds in
your current installation. Once this is complete, you can then add any
new product features that you want as follows:
a. Type the following command and press Enter
smitty install
b. In the INPUT device/directory for software field enter . (period) to
c. Selecting the filesets : Press F4 in the SOFTWARE to install entry
field to list the filesets in the root directory on the CD-ROM.
The system displays the SOFTWARE to Install menu.
d. Select any of the following optional packages.
v devices.dirTalk.BrooktroutFax: Fax device driver.
v devices.iop_rpq.rte: DTEA device driver.
v dirTalk.3270: to support 3270 servers.
v dirTalk.ADSI: to support analog display services interface (ADSI)
phones.
v dirTalk.BrooktroutFax: to support Fax machines.
v dirTalk.VRBE_XML: to support VoiceXML 2.1 and Java API
applications. If you previously had the dirTalk.DTBE package
installed (to support VoiceXML 1.0 and JavaBeans applications)
ensure that you have removed it, as described in “Preparing to
migrate VoiceXML and Java applications” on page 38.
v dirTalk.GEOTEL: to support Cisco Intelligent Contact Management
software.
v dirTalk.ISDN.com: to support all ISDN protocols.
v dirTalk.ISDN.ATT: to support AT&T 5ESS and Lucent Definity G3i
switches.
v dirTalk.ISDN.DMS100: to support Nortel DMS-100 and DMS 250
switches.
v dirTalk.ISDN.EuroISDN: to support EuroISDN and E1 QSIG.
v dirTalk.ISDN.INS1500: to support Japan's INS Net Service 1500.

v dirTalk.SP: to support languages other than US English. Not
required for VoiceXML and Java.
v dirTalk.SpeechClient: to support speech recognition and text to
speech
v dirTalk.SS7_D7: to support SS7
v dirTalk.TDD: to support telecommunications devices for the deaf.
v dirTalk.VOIP_SIP: to support Voice over IP (using DTNA or
DTEA).
Do not select any other packages. Any other required filesets have
been installed automatically as part of the migration process.
e. When you have selected the filesets to install, press Enter.
The system installs the software. This could take from 10 minutes to
30 minutes, depending on which options you install and the model of
pSeries computer you are using. When the process is complete, OK
appears at the top of the screen. Check the messages at the bottom of
the screen to confirm the successful installation of each selected
package.
8. Review the output. It may contain information about changes that were
made during the migration.
If any filesets failed to install due to missing prerequisite AIX filesets,
install the missing filesets from the AIX installation CDs or apply AIX
PTFs to upgrade the filesets to the correct level. Repeat the WebSphere
Voice Response installation.
10. Unmount the CD as described in step 12 on page 45.
11. If you require SS7 D7 enablement:: Insert the WebSphere Voice
Response installation CD into the drive, and repeat the actions described
in steps 2 on page 44 to 12 on page 45, selecting the fileset:
v dirTalk.SS7_D7
Note: SS7 D7 support is provided through the separately-orderable PRPQ

(7J0465) IBM SS7 Support for WebSphere Voice Response. For details of
installation refer to the SS7 Support for WebSphere Voice Response: SS7
User's Guide book, GC34-7090.
12. If you require the WebSphere Voice Server Connector:: Insert the
WebSphere Voice Response installation CD into the drive, and repeat the
actions described in steps 2 on page 44 to 12 on page 45, selecting the
fileset:
v dirTalk.SpeechClient
For details of how to configure and use the WebSphere Voice Server
Connector, refer to the WebSphere Voice Response for AIX: Deploying and
Managing VoiceXML and Java Applications book.
48 Installation
Setting up the AIX account (standalone system only)
Use this procedure whether you have just installed a standalone WebSphere
Voice Response system for the first time, or have migrated from a previous
release.
Setting your dtuser password
If it does not already exist, an account named dtuser is created automatically
during the installation of WebSphere Voice Response. Before you log on to this
account, you need to set the password.
To do this:
smitty users
3. Select Change a User's Password.
4. Type in dtuser as the user ID, and press Enter.
5. Follow the on-screen prompts.
Setting the dtuser file permissions
You need to use the vae.setuser command to ensure that the file permissions
and ownerships are correct. You need to run this whether you are using the
dtuser account provided by the WebSphere Voice Response installation
process or you have set up your own AIX account.
Attention: $VAE must either not be set or be set to /usr/lpp/dirTalk at this

point.
To do this:
/usr/lpp/dirTalk/tools/vae.setuser
You can ignore any messages about DB2. These might be generated if you
have not yet created the WebSphere Voice Response database.
3. The following prompt is displayed: Enter user ID for running WebSphere
Voice Response (must begin with an alpha character):.
Enter dtuser (unless you have set up an AIX account with a different
name).
4. The prompt Process All filesystems? ([y]/n/?) : is displayed.
Enter y to set ownership and permissions across all relevant mounted
filesystems (this is the default).

Enter n to restrict ownership and permissions to the current path. With
this option, you have to manually set permissions for other filesystems if
you subsequently want to include them. The n option is likely to be used
in configurations where a large number of voice segments, voice messages,
or audio names or greetings are mounted on a separate filesystem, but
already have the correct ownership and permissions. In this situation,
entering y could cause vae.setuser to execute very slowly, possibly taking
hours to complete.
Next step:
v If you have any PTFs to install, such as those provided on the CD labelled
"Service Update", you should install them now, using the instructions
provided below in “Installing PTFs for WebSphere Voice Response.”
v Otherwise, go to “Restarting AIX” on page 51.
Installing PTFs for WebSphere Voice Response

To install PTFs:
2. If you are installing PTFs from a CD, insert the CD in the drive and
mount it.
3. Type smitty update_all and press Enter .
4. Overtype the INPUT device / directory for software field with the name
of the mount point (for example, /cdrom) and press Enter.
5. Leave the value in the SOFTWARE to install field as _update_all. You can
leave all the other options as default values, or set them as you normally
would.
Note: Some of the options may need to be altered if there is not enough
free disk space available for the install.
Finally, ensure that the media is loaded correctly, and press enter to install.
6. When the installation process is complete, exit SMIT and run vae.setuser
to refresh file ownership. Enter the following command:
7. The prompt Enter user ID for running WebSphere Voice Response (must
begin with an alpha character): is displayed.
Enter dtuser (unless you have set up an AIX account with a different
name).
8. The prompt Process All filesystems? ([y]/n/?) : is displayed.
Enter y to set ownership and permissions across all relevant mounted
filesystems (this is the default).
50 Installation
Enter n to restrict ownership and permissions to the current path. With
this option, you have to manually set permissions for other filesystems if
you subsequently want to include them. The n option is likely to be used
in configurations where a large number of voice segments, voice messages,
or audio names or greetings are mounted on a separate filesystem, but
already have the correct ownership and permissions. In this situation,
entering y could cause vae.setuser to execute very slowly, possibly taking
hours to complete.
Next step: Go to “Restarting AIX.”
Restarting AIX
AIX shuts down and restarts to make all changes take effect.
1. Shut down any processes that require a clean shutdown, for example SNA.
2. Make sure you are not in the CD-ROM file system (check all your terminal
sessions).
3. Login as dtdb23in (su - dtdb23in) and type the following commands,
pressing Enter after each one:
a. db2 force applications all
b. db2 terminate
c. db2stop
Wait until all DB2 processes have stopped (you can check this using the
ps –ef | grep db2 command). The db2fmcd process will continue to run,
but this does not cause any problems. If DB2 does fail to stop, use the
command db2stop force.
4. Login as root, type the following command, and press Enter:
shutdown -Fr
Next step:
v If you have installed WebSphere Voice Response for the first time, go to
“Creating the WebSphere Voice Response database.”
v If you migrated to WebSphere Voice Response Version 6.1 from a previous
release, go to “Updating the WebSphere Voice Response database” on page
52.
Creating the WebSphere Voice Response database

This procedure is used when you have installed WebSphere Voice Response
for the first time. It creates the WebSphere Voice Response database tables,
and loads the base application objects, such as state tables, system prompts
and voice directories.

Start
2. Setting up the environment: You are currently logged on as root, but you
need to have the environment set as it would be if you were logged on as
dtuser. To set the environment, type the following command and press
Enter:
Make sure you leave a space between the period and the slash before usr.
There is no visible feedback when you have entered this command.
echo $VAE
following message:
/usr/lpp/dirTalk
4. Creating the database: Check that you have at least 250 MB (256000
1024–byte blocks) of disk space available in the /home file system and at
least 120 MB (122880 1024–byte blocks) available in the /tmp file system by
using the following commands:
df -k /home
df -k /tmp
If you do not have enough space, increase the size available for these file
systems before you proceed.
5. Type the following command, then press Enter:
/usr/lpp/dirTalk/tools/DTdatabase -r
6. The prompt Restore supplied sample database and voice data? (y/n) is
displayed.
Typically you should respond by entering y, at which point the system
creates the database, displaying status messages as it does so. This may
take a few minutes.
Next step: Go to “Setting ownership of the DTTAs” on page 53
Updating the WebSphere Voice Response database

If you migrated to WebSphere Voice Response Version 6.1 from WebSphere
Voice Response Version 4.2 you need to copy (migrate) the WebSphere Voice
Response data from the old DB2 Version 8.1 database to the new DB2 Version
9.5 format as follows:
Start
1. Log on to the DB2 server as dtdb23in.
52 Installation
2. Type the following command to invoke the editor and press Enter:
vi /home/dtdb23in/sqllib/db2nodes.cfg
v If the file already contains data, ensure that the hostname used is the
DB2 machine service IP label.
v If the file has no content, or is new, add the following text:
0 <DB2 service IP label> 0
To save the db2nodes.cfg file you may have to use the:w! command
instead of simply :w.
3. Type the following commands, pressing Enter after each one:
a. chmod 444 /home/dtdb23in/sqllib/db2nodes.cfg
b. db2 force applications all
c. db2 terminate
d. db2stop
Wait until all DB2 processes have stopped (you can check this using the ps
–ef | grep db2 command). The db2fmcd process will continue to run, but
this does not cause any problems. If DB2 does fail to stop, use the
command db2stop force.
4. Log on as root.
/usr/lpp/dirTalk/tools/DTdatabase –m
If an error message is generated, take the following action:

1. Retry the command
/usr/lpp/dirTalk/tools/DTdatabase -m
This should now complete without any errors.

2. Enter the following commands, pressing Enter after each one:
a. su - dtdb23in
b. db2set DB2COMM=TCPIP
c. db2 "update dbm cfg using DIAGLEVEL 3"
d. exit
Next step: Go to “Setting ownership of the DTTAs.”
Setting ownership of the DTTAs

If you are using Digital Telephony Trunk Adapters (DTTAs), you need to set
WebSphere Voice Response as the owner of these adapters, as detailed below.
2. Type the following command and press ENTER:

Make sure that you leave a space between the . (period) and /usr.
lsdev -C | grep rpq
A list of all the devices installed in the system unit will be displayed, for
example:
rpqio0 Available 1H-08 Quad Digital Trunk Telephony PCI Adapter
rpqio1 Available 1V-08 Quad Digital Trunk Telephony PCI Adapter
rpqio2 Available 1Z-08 Quad Digital Trunk Telephony PCI Adapter
rpqio3 Available 1D-08 Quad Digital Trunk Telephony PCI Adapter
ddrpqio0 Available 1H-08-00 Digital Telephony Device Driver
ddrpqio1 Available 1V-08-00 Digital Telephony Device Driver
ddrpqio2 Available 1Z-08-00 Digital Telephony Device Driver
ddrpqio3 Available 1D-08-00 Digital Telephony Device Driver
4. Each line of the output identifies a device. The identifier is on the left, and
the description is on the right. You need to register WebSphere Voice
Response as the owner of each device described as a Quad Digital Trunk
PCI Telephony Adapter.
The last digit of the identifier is the adapter_number which is input to the
dt_setowner command. For a DTTA, you need to supply two other pieces
of information to the dt_setowner command: the adapter type (-x) and the
trunk type (-t).
The dt_setowner command is in the format:
dt_setowner -x -s adapter_number -t T1 | E1
where adapter_number is the last digit of the identifier. For example, to

register WebSphere Voice Response as the owner of the DTTA whose
identifier is rpqio1, type one of the following commands and press Enter:
dt_setowner -x -s1 -t T1
or
dt_setowner -x -s1 -t E1
For more information on using dt_setowner, see “dt_setowner command” on

page 144
Next step: Go to “Running hardware diagnostic procedures” on page 55
54 Installation
Running hardware diagnostic procedures
Diagnosing unrecognized DTTAs
If the lsdev -C | grep rpq command lists any adapters as Defined, or it does
not list an installed adapter, this adapter is not recognized by your system. In
this situation, do the following:
1. Turn off the computer.
2. Remove the unrecognized adapter.
3. Check for any obvious change. Check that the base and daughter cards are
firmly plugged together.
4. Reinstall the adapter into the same card slot that it was removed from.
5. Turn on the computer.
6. Login as the root (or obtain superuser privileges) if you have not already
done so.
7. View the installed adapters (using lsdev -C | grep rpq).
8. If it is still not recognized as Available, replace the adapter.
9. Repeat Steps 1 through 5 of this procedure for any other adapters your
system does not recognize.
Running diagnostics on the DTTA
Ensure WebSphere Voice Response has been shut down before running
hardware diagnostics (otherwise WebSphere Voice Response will experience
unexpected failures).
To run DTTA hardware diagnostics, do the following:

1. Login as the root (or obtain superuser privileges) if you have not already
done so.
2. To set up the diagnostic test environment, type the following command,
then press Enter:
export RPQPATH=/usr/lpp/devices.iop_rpq
then type the following command, and press Enter:

export PATH=$PATH:/usr/lpp/devices.iop_rpq/bin
3. To test an adapter once, type the following command, and press Enter:
rpqtest adapter_number 99 -I
Where adapter_number is the card number corresponding to

rpqioadapter_number. You will be asked to confirm the PCI Mezzanine
Connector (PMC) ID (this should be 0xa1331). rpqtest will proceed
through the testing. If the diagnostics do not find any problems with the
adapter, they will end with the message Test completed.

4. To test a single adapter continuously until it has stopped, add the -C
option to the previous command, as follows:
rpqtest adapter_number 99 -I -C
where adapter_number is the card number corresponding to

rpqioadapter_number. This is a good reliability test.
Note: rpqtest does not require wrap plugs to be installed on the

telephony (RJ45) interface.
5. You should repeat rpqtest for each adapter in the system to make sure
that the hardware is working.
6. If any test fails, the most likely cause is a faulty adapter which should be
replaced.
Note: For the DTTA, the Field Replaceable Unit (FRU) is the entire adapter.
56 Installation
Chapter 4. License configuration
This chapter provides a guide to the requirements for setting up licensing for
WebSphere Voice Response software and to the administration of the
WebSphere Voice Response licensing policy. The chapter is divided into the
following topics:
v “Licensing overview”
v “The network licensing environment” on page 58
v “Configuring your system for License Use Management” on page 60
Some of these topics relate specifically to WebSphere Voice Response, but

most of the information in this chapter is explained in more detail in the
Using License Use Management Runtime book. You can find the document on
any AIX system that has IBM License Use Management product Version 6.1 or
above installed, in the file /usr/opt/ifor/ls/os/aix/doc/lumusg.htm.
Licensing overview
WebSphere Voice Response is license-enabled software. Your licenses should
be enrolled and managed using the IBM License Use Management product.
You need to ensure that License Use Runtime Version 6.1.0 or above is
installed and correctly configured on your system before running WebSphere
Voice Response.
Concurrent network license model
WebSphere Voice Response uses concurrent licenses. These are held by a

network license server and temporarily granted to a WebSphere Voice
Response system to allow it to run. While WebSphere Voice Response is still
running on that system, the license remains unavailable to other networked
machines. When WebSphere Voice Response stops running, the license is
returned to the network license server, where it becomes available to other
license client machines.
If your WebSphere Voice Response machines are not networked or you have a
single standalone system, each machine can be configured to act as its own
license server.
Customer-managed use
WebSphere Voice Response licenses are customer-managed, which means it is

your responsibility to monitor the use of existing licenses and to purchase

new licenses when necessary. License Use Runtime will provide you with all
the information necessary to monitor license use on your system and the
facility to enroll and distribute the licenses you purchase.
With customer-managed use you can choose a soft stop or hard stop policy.
If a license is requested under the soft stop policy and all licenses are already
allocated, a temporary license will be allocated and WebSphere Voice
Response will start without error. Where this occurs, you are expected and
trusted to order more licenses from IBM without delay. License Use
Management keeps a record of the maximum number of temporary licenses
issued at any one time as a high-water mark. You can use the License Use
Management Basic License Tool to monitor the high-water mark and determine
whether you need to purchase more licenses.
Technically, if all the licenses are already in use and a further license is
allocated, this is a license violation. However, choosing this option allows you
time to purchase and distribute extra licenses without disruption to your
business activities. If you have already purchased additional licenses but not
yet enrolled and distributed them, you should do so at this time.
Hard stop policy still allows WebSphere Voice Response to start but
WebSphere Voice Response will issue a red alarm and log an error.
WebSphere Voice Response uses soft stop as the default option. You can use
the Basic License Tool to change the policy to hard stop and back again at any
time.
The network licensing environment

There are three major components to the network licensing environment for
WebSphere Voice Response:
v Network license clients.
v Network license servers.
v Central registry license server.
These components can be set up on separate physical pSeries computers or
with some or all components on the same machine. Each pSeries computer
must have License Use Runtime installed and configured (this is normally
done as part of the installation of the AIX operating system)..
Network license clients
In License Use Management, a network license client is any node configured

to make use of licenses by requesting them from a network license server. In
this case, a network license client will be any machine that has WebSphere
58 Installation
Voice Response installed. A network license client is configured for License
Use Management in the same way regardless of whether it is a WebSphere
Voice Response server or client.
Each network license client must be connected to a network license server.
Network license servers
A network license server is a node in the network on which network licenses

are stored for use by multiple network license clients. You must have at least
one network license server in your network and it is possible to have more.
When the user at a client starts a licensed program, License Use Runtime at
the network license server determines whether a license is available.
Central registry license server
The central registry is a database that contains information about the

enrollment and distribution of licenses. It also holds information related to
those licenses, such as hard or soft stop policy. The central registry license
server is used to track soft stop licenses and record the high-water mark. All
customer-managed use controlled products, including WebSphere Voice
Response, require you to identify one central registry for each network.
WebSphere Voice Response licenses

When you install WebSphere Voice Response for AIX, a set of license files are
provided. The license files are used to create your licenses and enroll them on
your system. The license files provided for WebSphere Voice Response for AIX
are listed here.
All license files have extension .lic and can be found in the
/usr/lpp/dirTalk/db/license directory.
Table 4. The license filenames for each of the WebSphere Voice Response
components.
WebSphere Voice License Filename Number of licenses required
Response component
Channels dtaixchan.lic 1 per channel in use
Chapter 4. License configuration 59

Configuring your system for License Use Management
To configure your system for License Use Management you need to:
v Configure your pSeries computers to act as either license clients or servers.
v Enroll your WebSphere Voice Response licenses.
v Distribute your WebSphere Voice Response licenses.
Setting up the .profile file
Log in with root authority and check that there is a .profile file. If a
.profile file does not already exist you will need to create one.
Add the following paths to the .profile file:

PATH=/usr/opt/ifor/ls/os/aix/bin:$PATH
PATH=/usr/java6/bin:$PATH
If you are using a later version of Java, include the appropriate installation
directory in the path statement instead of java6.
Configuring your networked systems
This section describes how to set up your WebSphere Voice Response systems
as either network license clients or servers. You should decide now which
machine or machines will act as network license servers and where your
central registry will be held.
On each pSeries computer in your network license environment:

2. Type i4cfg -stop to stop the LUM runtime.
3. Type i4cfg to start the configuration tool. (Make sure the $DISPLAY
variable is set correctly.)
4. Select the Configure As page.
60 Installation
Figure 3. The configuration tool, "Configure As" page.
5. Check the boxes as follows:

v Network License Client: must be checked for all systems.
v Nodelocked License Server (NodLS): should not be checked, unless
you have already configured License Use Runtime with this option
checked for use with another product.
v Network License Server (NetworkLS): check only if this system is to
be a license server.
v Central Registry License Server (CrLS): check only if this system is to
be a central registry license server.
Generally you do not need to check the remaining boxes although,
depending on your network configuration, you may need to check
Namespace binding support. See the Using License Use Management
Runtime book for details.
6. Select the Direct binding page.

Figure 4. The configuration tool, "Direct binding" page.
7. Review the entries in the Servers field. If they show the configuration
you want to use, you can proceed to step 11, otherwise select any
incorrect entries, and click Remove
8. Enter the short name of a machine that will act as a license server for this
client. If the machine you are configuring is also to be the server, enter
the machine's own name.
9. If the machine is to act as network license server (Network LS), central
registry license server (Central Registry LS), or both, check the
appropriate boxes beneath the name field.
10. Click Add.
The information you have entered will appear in the Servers field.
11. If you specified that this machine is to be a network license server or a
central registry license server, select the Start up page. If it is to be a
client only, go to step 13 on page 63.
62 Installation
Figure 5. The configuration tool, "Start up" page.
12. Check the Start services at system start up box.

13. Close the Configuration Tool window.
14. On the popup panel, click Yes to save changes.
15. Click OK to confirm.
16. Type i4cfg -start to start the LUM runtime.
Enrolling your licenses
WebSphere Voice Response for AIX requires a license for each configured
channel available to the system. Your company should already have
purchased sufficient channel licenses for your needs. Contact your purchasing
department if you are unsure how many channel licenses have been
purchased and take care to only enroll this number.
To enroll the licenses:

1. Log in as root, if you are not logged on already.
2. Type i4blt to start the Basic License Tool.
3. Click Products –> Enroll –> Single Product.
4. Click Import..., and then in the selection box, navigate to the
/usr/lpp/dirTalk/db/license/ directory.
5. Select dtaixchan.lic.
6. Click Open

7. The Enroll Product window shows the details of the license. Click OK to
confirm.
8. In the Enroll Licenses window, enter your details in the Administrator
Information fields.
9. In the Enrolled Licenses field, enter the number of licenses, using Table 4
on page 59 to help you.
10. Click OK.
Distributing your licenses
Once the licenses have been enrolled, they need to be distributed to make
them available to the network license server.
To distribute the licenses:

1. Log in as root, if you are not logged on already.
2. Type i4blt to start the Basic License Tool, if it is not already running.
The Basic License Tool window will show details of all your enrolled
licenses.
Figure 6. Basic License Tool window
3. Right-click on the license type you want to distribute.

4. Select Distribute licenses from the drop down menu.
A Distribute Licenses window will appear for the license type you are
distributing. This will provide a list of all the servers available.
64 Installation
5. Right-click on the appropriate server for your client machine.
6. Select Selected —> Set number of licenses from the popup menu.
7. Enter the number of licenses you want to distribute to this server. This
should be the number of licenses you enrolled.
8. Click OK.
Figure 7. Distribute Licenses window
9. In the Distribute Licenses window, click Licenses —> Distribute.

11. Repeat steps 3 on page 64 to 10 for each license type you want to
distribute.
You have now configured your system for License Use Management. You can
close any Basic License Tool windows that are still open and proceed to
Chapter 5, “Starting WebSphere Voice Response and testing the installation,”
on page 67.
If you find that licenses are not being granted, see WebSphere Voice Response for
AIX: Problem Determination for instructions on finding the licenses that have
not been correctly enrolled and distributed.

66 Installation
Chapter 5. Starting WebSphere Voice Response and
testing the installation
This chapter covers the following topics:
1. “Starting WebSphere Voice Response”
2. “Configuring the WebSphere Voice Response telephony” on page 70
3. “Restoring saved data after migrating” on page 77
4. “Importing .imp files” on page 80
5. “Rebuilding and reinstalling custom servers” on page 85
6. “Migrating 3270 servers” on page 86
7. “Testing that your applications still work” on page 86
Starting WebSphere Voice Response

This procedure tells you how to start WebSphere Voice Response using a
graphical terminal.
Prerequisites
Before you start WebSphere Voice Response, make sure you do the following:
v You must know the name of your display. This is normally stored in the
$DISPLAY variable. To find the value of the variable, type the following
command on an AIX command line and press Enter:
echo $DISPLAY
If this variable has not been set, contact your system administrator.
v You must know the name of the AIX account set up for WebSphere Voice
Response. The default account name is dtuser.
v If you have newly installed one or more DTTAs in your pSeries computer,
you must register WebSphere Voice Response as the owner of each one. See
“Setting ownership of the DTTAs” on page 53 for instructions.
v If you have newly installed one or more DTNAs or DTEAs, you must
register WebSphere Voice Response as the owner of each one. Refer to the
WebSphere Voice Response for AIX: Voice over IP using Session Initiation Protocol
book for instructions.

Procedure
1. If you have not already used the vae.setuser utility, or you have installed
any WebSphere Voice Response software since it was last used, you must
run it now. See “Setting the dtuser file permissions” on page 49 for
instructions.
2. Log on to the AIX user account that is set up for WebSphere Voice
Response (normally dtuser).
3. If necessary, start a terminal session.
4. If the system displays the Login menu:
WebSphere Voice Response User Login
1) Start WebSphere Voice Response Processes
2) Do Not Start WebSphere Voice Response
Enter choice (or <ENTER> for option list)
Type 1.
Otherwise, type the following command on the AIX command line, then
press Enter:
vaeinit
Type 1 when the system displays the Login menu.

5. If $DISPLAY has not been set, you are prompted for your display name.
If you are prompted, type your display name using the following format:
name:number
where name is the host name, and number is the session number
(normally 0); for example, magpie:0. Then press Enter.
The system displays the Status window; most of the time, you can keep
this window minimized.
6. If you have just installed WebSphere Voice Response for the first time, the
system displays the license acceptance window. You must accept the terms
of the license agreement before WebSphere Voice Response will allow you
to log on.
7. The system displays the Welcome window and the Logon window:
68 Installation
Type admin in the Administrator Profile Name field. The field is
case-sensitive.
8. Type admin in the Password field. This field also is case-sensitive.
Attention: It is strongly recommended that you change this password
immediately; see the WebSphere Voice Response for AIX: Configuring the
System book for details.
9. Click Logon, or press Enter.
The system activates all menus on the Welcome window menu bar:
Next step: You are logged on and ready to start using WebSphere Voice
Response. Now go to “Configuring the WebSphere Voice Response telephony”
on page 70.
Chapter 5. Starting WebSphere Voice Response and testing the installation 69

Configuring the WebSphere Voice Response telephony
This section tells you how to configure your system so that you can run a
simple installation test. If you have migrated from an existing WebSphere
Voice Response or DirectTalk system you may prefer to skip the test and
proceed to “Restoring saved data after migrating” on page 77 then test the
installation with one of your own applications.
The information in this section is an abbreviated form of the information in

the WebSphere Voice Response for AIX: Configuring the System book. You should
use that book when you have completed the instructions in this book and are
ready to configure your system for running production applications.
Prerequisites
v You need some of the information you noted in “Preparing for installation”
on page 6.
v You should be familiar with the Motif style of user interface. The WebSphere
Voice Response for AIX: User Interface Guide book includes some hints and
tips about using the WebSphere Voice Response user interface.
v To use ISDN, you need to import the appropriate ISDN signaling process,
as described in “Importing .imp files” on page 80.
Procedure
Use this procedure to set up channels on one trunk so that you can test that
the installation has worked.
1. Start: From the Welcome window, select Configuration —> Pack
Configuration —> Change to display the Pack Configuration window:
2. Setting the correct country/region: Click the country/region button and

then select your country/region from the list displayed. If your country
or region is not displayed, click Other T1 or Other E1 (see the notes you
made on “Preparing for installation” on page 6).
3. Click OK.
70 Installation
The system displays a dialog box. As the dialog box says, setting the
country/region incorrectly could have serious effects on the operation of
the system, so make sure you have chosen the correct country/region.
The system displays the country/region name and activates other buttons
in the window. To test that the installation has worked, you need only set
the details for the first pack listed under Physical Interface.
Voice over IP: If to run Voice over IP, you are using DTEA cards in your
pSeries computer, or the DTNA software simulation of a DTEA card on
your BladeCenter® or System p5 computer, you should read the
WebSphere Voice Response for AIX: Voice over IP using Session Initiation
Protocol book for details of how to configure them.
In the Pack Configuration windows, DTTA trunks are labeled TPACK E1 or
TPACK T1.
5. Configuring the DTTA: Set the details for the first pack.
Click the Trunk Parameters button and select the signaling mode from
the cascade push-button.
If you select ISDN and are using a T1 interface, you can select
Non Facility Associated Signaling Support, by checking the box. In this
case, you need to fill in the Trunk ID (allocated by your service provider)
and click Primary from the cascade push-button next to Signaling
Channel.
6. Click OK.
7. Click the Switch Type button, then select the switch type from the list
displayed. If your switch is not on the list, click Default.
8. Click OK.
9. Make sure the Operating Status is Available.
10. Click the Line Signaling button. If the protocol you require is not listed:
a. Click Cancel.
b. Click Switch Type again.
c. Click Default.
d. Click OK.
e. Click Line Signaling again. If the protocol you require is still not
listed, this means that the protocol is not normally used in the
country/region you have selected; you will have to use the
information in the WebSphere Voice Response for AIX: Configuring the
System book to configure your telephony environment using system
parameters. When you have done this, you should be able to perform
the installation test.
11. Select the type of line signaling from the list displayed.

12. Click OK.
13. Make sure the Direction is Bothway.
You have now set the details you need to receive an incoming call using
one of the trunks. You will probably need to specify more details before
you can use your own applications.
14. Click the Save/*Changed box next to the details you have set.
15. Click File —> Save.
The system displays a dialog box.
17. Click File —> Close.
18. Shutting down : Check that the WebSphere Voice Response startup
process has completed.
19. In the Welcome window, click Operations —> Immediate Shutdown.
The system displays a dialog box.
The system shuts down all windows, cleans up the database, and stops
all foreground and background processes.
21. Do not restart WebSphere Voice Response immediately. Always wait until
you see the message “Node Manager terminating” before you try to
restart WebSphere Voice Response, to allow all processes to terminate
properly. Then you can close the window by pressing Ctrl+C.
22. Restarting: Follow the instructions in “Starting WebSphere Voice
Testing the installation

This test uses a simple application to check that the installation has worked.
You will call in to WebSphere Voice Response and hear the sample application
answer the call.
72 Installation
If you are migrating from a previous release, note the following before you
restore any previous configuration:
v The channel ids are set to 4085551234 but there is no profile associated with
this number.
v The default application profile (0000000000) is set to JavaApplication.
This means that if you call the system at this point (with no other valid
application profiles), the call is passed to the Java and VoiceXML environment.
If, for any reason, the Java and VoiceXML environment is not available, the
call is answered by the Welcome application (a state table). This will work for
all signaling protocols, both those that pass the called number to WebSphere
Voice Response for AIX and those that do not.
Note: If you want to test that a CCXML application can perform the
call-handling on incoming calls, you must first change the Incoming_Call state
table so that it allows calls to pass through without answering them, as
described in Appendix E of the WebSphere Voice Response for AIX: Deploying
and Managing VoiceXML and Java Applications book.
1. Activating the trunk and all channels: From the Welcome window, select
—> Operations —> System Monitor to display the System Monitor
window:

2. To activate the trunk and all channels, click the Trunk Status push button
for the trunk you configured, then click Enable.
The trunk operating status is changed to Inservice.
3. Click the Trunk Status button again and click Channels in Service.
4. Click File —> Close.
5. Making a call to WebSphere Voice Response: Before following these
instructions, make sure you have installed the fileset for the locale you
want to use, as shown in Table 5 on page 75. If you installed the complete
dirTalk.VRBE_XML package, all locale filesets will have been installed.
Start the installation verification application by entering the following
command:
verify_install
Follow the instructions on the screen.
6. Make a call, using a telephone number that routes calls to WebSphere
Voice Response and is not allocated to any of your own applications.
v If you have installed dirTalk.VRBE_XML, the default Java application
answers the call and passes it to a VoiceXML application, which greets
you with the words "Welcome. Websphere Voice Response is now
installed." Then the application hangs up.
74 Installation
v If you have not installed dirTalk.VRBE_XML, the default state table
application answers the call and greets you with "Welcome to the IBM
WebSphere Voice Response for AIX." Then the application hangs up.
You have successfully installed WebSphere Voice Response. If there is any
other outcome, try using the information in WebSphere Voice Response for
AIX: Problem Determination to solve the problem, or contact IBM Support.
Next step:
v If you want to use the Java and VoiceXML environment in a language other
than U.S. English, go to “Installing extra languages for Java applications.”
v If you have installed WebSphere Voice Response for the first time, go to
“Importing .imp files” on page 80. In particular, to use ISDN as your
signaling protocol you must have imported the required ISDN custom
server files.
v If you are have migrated from a previous release of DirectTalk or
WebSphere Voice Response:
– If you have Java and VoiceXML applications, go to “Restoring your
VoiceXML and Java data” on page 84.
– If you use any custom servers or 3270 servers, go to “Rebuilding and
reinstalling custom servers” on page 85, or “Migrating 3270 servers” on
page 86, as required.
– Otherwise, go to “Testing that your applications still work” on page 86.
v If you need to restore data that you backed up from a previous release, go
to “Restoring saved data after migrating” on page 77.
v If you exported data from a previous release, use the instructions in the
WebSphere Voice Response for AIX: Designing and Managing State Table
Applications book to import the application data you exported.
Installing extra languages for Java applications

You only need to follow these instructions if you want to run Java
applications in a language other than U.S. English.
Prerequisites
Table 5. Audio segment filesets for each language.
Language Fileset name without Enhancements
Catalan–Spain dirTalk.DTBE.ca_ES
English–UK dirTalk.DTBE.en_GB
English–US dirTalk.DTBE.en_US
French–Canada dirTalk.DTBE.fr_CA
French–France dirTalk.DTBE.fr_FR

Table 5. Audio segment filesets for each language. (continued)
German–Germany dirTalk.DTBE.de_DE
Italian–Italy dirTalk.DTBE.it_IT
Spanish–Mexico dirTalk.DTBE.es_MX
Spanish–Spain dirTalk.DTBE.es_ES
Portuguese-Brazil
Procedure
1. Log in as dtuser.
2. At the command line, type the following command and press Enter:
cd /var/dirTalk/DTBE/nls/mappers
3. For each language you want to install, type the following command and
press Enter to import the voice segments:
dtjnlsin xx_yy.zip
Where xx_yy is the language identifier for the language you want to use.
The language identifier forms the last five characters of the audio segment
fileset name.
4. Make sure you see the message "The language pack has been installed
successfully".
To set the default locale to a different language, you need to edit the
default.cff file:
1. Setting the default locale to a different language : Type the following
command and press Enter:
cd /var/dirTalk/DTBE/native/aix
2. Edit the default.cff file.
3. Find the line that reads:
NodeDefLocale=en_US
and change the language identifier from en_US to the language identifier
you want.
4. Save your changes.
5. At the command line, type the following command and press Enter:
dtjconf
6. Stop the Java and VoiceXML environment by typing:
dtjstop
7. Restart the Java and VoiceXML environment by typing:
76 Installation
dtjstart
You can now follow the instructions in “Testing the installation” on page 72
again, to make sure that you hear the application in the new language. For
more information about configuring applications in the Java and VoiceXML
environment, see WebSphere Voice Response for AIX: Deploying and Managing
VoiceXML and Java Applications.
Next step:
v If you have successfully installed WebSphere Voice Response for the first
time, go to “Importing .imp files” on page 80.
v If you have migrated from a previous release of DirectTalk or WebSphere
Voice Response:
– If you have Java and VoiceXML applications, go to “Restoring your
VoiceXML and Java data” on page 84.
– If you use any custom servers or 3270 servers, go to “Rebuilding and
– Otherwise, go to “Testing that your applications still work” on page 86.
v If you saved data from a previous release and need to restore it, go to
“Restoring saved data after migrating.”
v If you exported specific data from a previous release, use the instructions in
the WebSphere Voice Response for AIX: Designing and Managing State Table
Applications book to import the application data you exported.
Restoring saved data after migrating

If you have successfully migrated to WebSphere Voice Response Version 6.1,
you do not need to use this procedure to restore data you saved using the
saveDT utility in “Saving your current data” on page 36.
If you saved data from a previous release, you can use that data to either:
v recover from a migration failure
v restore data to a database server when moving from a standalone system to
a single system image (as described in“Converting from a standalone
system to a single system image” on page 13)
v restore data when moving from a single system image to a standalone
system (as described in “Converting from a single system image to
standalone systems” on page 14).
If you wish to restore data in these situations, follow the procedure in this
section.

The restored data is in the same state it was in when you saved it. The
Default and User applications still exist, and the System application contains
the System application profile. However, note that system parameters and
archived statistics are not restored unless you answer the appropriate prompt
when you restore your data.
Prerequisites
Before you start the following procedure, note the following prerequisites:
v Ensure that WebSphere Voice Response is not running on the system to
which you want to restore data.
v If you want to restore data to a single system image, you must perform this
procedure on the database server node of the single system image. You
must ensure that WebSphere Voice Response is not running on any nodes of
the single system image, and that no other processes are connected to DB2.
v To restore the data, you need the same amount of space on the hard disk as
you needed to save the data, plus 2–4 MB for data migration activities. If
there is not enough space available, either use SMIT to increase the size of
the file system, or move the WebSphere Voice Response databases to a file
system with more space; see the WebSphere Voice Response for AIX: Managing
and Monitoring the System book for more information.
v If you are restoring from a tape, you need a suitable drive attached to the
pSeries computer. For example, if you saved your data to a 5 GB tape,
ensure that you have a 5 GB tape drive.
Procedure
Note: The restoreDT process can take some time. If you have many voice
messages or voice segments, it could take several hours.
Start
1. Shut down WebSphere Voice Response, if it is running.
2. Log on to AIX as root. It does not matter which directory you are in.
3. Setting up the environment: Type the following command and press
Enter:
echo $VAE
following message:
/usr/lpp/dirTalk
5. Restoring the data : Type restoreDT and press Enter.
78 Installation
The system displays the Restore Voice Response Data Script menu:
Restore Voice Response Data Script--Restore Device
1) Diskette (Recommended only for Small Amount of Data)
2) Hard Disk file (using tar)
3) Tape (using tar)
4) Quit
Select device type: (press ENTER to list choices) >
6. Type the number for the option you want to use, then press Enter. The
system prompts you for the device, directory, or file name, as
appropriate.
A message is displayed warning you that the WebSphere Voice Response
database will be reset to the condition it was in when you first installed
WebSphere Voice Response. Answer Y to continue past this message:
your data will be restored after restoreDT resets the database.
The system restores the data you saved to the correct directories. The
process takes some time, particularly if you have many voice messages or
voice segments.
7. Checking that the process has worked: Check the messages that have
been written in the restoreDT log file in the current directory. Search for
the word ERROR.
v Error messages: If you find any error messages, do not try to start
WebSphere Voice Response. Refer to the WebSphere Voice Response for
AIX: Problem Determination book for further information, and either try
to fix the errors or contact your IBM representative.
v Warning messages: These messages generally indicate that there are
problems that you can fix after starting WebSphere Voice Response.
8. Ensuring that the file permissions are correct: If you are restoring to a
stand-alone WebSphere Voice Response system (that is, not one
configured as part of a single system image), you must now run
vae.setuser again to make sure that the file permissions and ownerships
are correct.
To do this, type the following command, press Enter, and then follow the
prompts:
9. The save-and-restore migration process does not preserve any changes
you may have made to the WebSphere Voice Response resource files. If,
for example, you made color or font changes, you have to make the same
changes again.
10. Running the regression test: Test that you can still access the items you
recorded Procedure.
Next step: Go to “Importing .imp files” on page 80.

Importing .imp files
WebSphere Voice Response includes application components that need to be
imported into WebSphere Voice Response before they can be used. Two of them
have already been imported automatically because they are essential to system
operation (the base applications and the U.S. English system prompts); these
are provided as import files so that you can restore them easily if they become
corrupted. All the others are optional sample programs and other components
that not all users need. These components and the path names of the import
files are listed here. All the import files end in .imp. All the directories are
within /usr/lpp/dirTalk/sw/.
Use Table 6 to decide which files you need to import and record those you
have imported. For example, if you are planning to use batch voice import,
you need to import sw/samples/BVI.imp. The column headed “AP?” indicates
whether an application profile is required.
Table 6. Components supplied as import files
Component Path Name Relative to /usr/lpp/dirTalk/sw/ AP? U
Admin custom server admin/admin.imp

(required for some
command line utilities)
Batch voice import program samples/BVI.imp
3270 server sample program samples/3270ServerSample.imp Yes
Signaling process that samples/CTI.imp

communicates with CallPath
Server
Custom server sample samples/CustomServerSample.imp Yes

program
Base applications samples/BaseData.imp Yes U

(automatically imported)
Voice application sample samples/RecordAudionameSample.imp Yes

programs
samples/VoiceMessagingSample.imp Yes
80 Installation
Table 6. Components supplied as import files (continued)
Source files of background samples/juke_box.imp Yes

music subsystem, sample
tunes, and sample voice
application with background
music
TDM Trombone Utility samples/IBM_Trombone.imp Yes
Fax sample application fax/FaxSample.imp Yes
ISDN call transfer isdn/call_transfer/ISDN_Call_Xfer.imp

application
Signaling process for 5ESS isdn/sigproc_5ess_5e8/sigproc_5ess_5e8.imp

5E8 ISDN 1
Signaling process for 5ESS isdn/sigproc_5ess_5e9/sigproc_5ess_5e9.imp

5E9 ISDN 1
isdn/sigproc_dms100_bcs34/sigproc_dms100_bcs34.imp
Signaling process for
1
DMS100 BCS34 ISDN
Signaling process for INS isdn/sigproc_ins_isdn/sigproc_ins_isdn.imp

Net Service 1500 ISDN 1
Signaling process for isdn/sigproc_euroisdn/sigproc_euroisdn.imp

EuroISDN 1
1 isdn/sigproc_att_tr41449/sigproc_att_tr41449.imp
Signaling process for AT&T
Signaling process for ISDN isdn/sigproc_t1_nat/sigproc_t1_nat.imp

National 2 and 5ESS 5E12 1
Signaling process for isdn/sigproc_t1_nat/sigproc_dms_nat.imp

DMS-100 National
(NA007/8) 1
Signaling process for isdn/sigproc_dms250/sigproc_dms250.imp

DMS-250 1
Signaling process for QSIG isdn/sigproc_qsig/sigproc_qsig.imp

Table 6. Components supplied as import files (continued)
System prompts in Belgian samples/BelgianDutch.imp

Dutch
System prompts in Brazilian samples/BrazilianPortuguese.imp

Portuguese
System prompts in French samples/French.imp
System prompts in German samples/German.imp
System prompts in Italian samples/Italian.imp
System prompts in U.K. samples/UKEnglish.imp

English
Telecommunications Device samples/TTD.imp

for the Deaf (TDD)
TDD sample custom server samples/TTDSample.imp Yes
ADSI custom server adsi/ADSI.imp
Cisco custom server geotel/GeoTel.imp

samples/VOX_CTI.imp
Avaya Interaction Center
VOX connector
voip/sigproc_sip/sigproc_sip.imp
Voice over IP/SIP
voip/call_transfer/VOIP_Call_Transfer.imp
Voice over IP/SIP Call
Transfer
Note:
1. Before you can use an ISDN configuration you must import the appropriate ISDN signaling
process.
Procedure
Repeat this procedure for each of the import files.
Start
82 Installation
1. From the Welcome window , select Applications —> Applications to
display the Applications window.
2. Selecting the file to import : In the Applications window, click
Applications —> Import —> Replace —> File.
The system displays an Import File dialog box.
3. Type the path name in the Search String field, followed by an asterisk (*).
For example:
/usr/lpp/dirTalk/sw/samples/*
The system displays a list of files in that path.
4. Select the files from the Files list:
5. Click OK.
The system imports the files, then displays the Import Report window,
showing information about the import process.

6. Press Enter to close the window.
If you have imported a custom server, you need to start it before you can use
it. Refer to the WebSphere Voice Response for AIX: Managing and Monitoring the
System book for instructions.
The application is installed and ready for your use. In some cases, you need
to create an application profile for it before it can be used. See the WebSphere
Voice Response for AIX: Designing and Managing State Table Applications book for
information about creating application profiles.
If you are installing WebSphere Voice Response for the first time, you have
now finished the installation process proper and are ready to continue with
configuration. To integrate WebSphere Voice Response with Communications
Server, see Chapter 7, “Data communications network activities,” on page 101.
For details of WebSphere Voice Response configuration, see the WebSphere
Voice Response for AIX: Configuring the System book.
If you are migrating from a previous release of DirectTalk:
Next step:
v If you have Java and VoiceXML applications, go to “Restoring your
VoiceXML and Java data.”
v If you use any custom servers or 3270 servers, go to “Rebuilding and
v Otherwise, go to “Testing that your applications still work” on page 86.
Restoring your VoiceXML and Java data

Follow this procedure if you backed up your Java and VoiceXML data (see
“Preparing to migrate VoiceXML and Java applications” on page 38).
The procedure overwrites configuration files and voice segments of the same
name but does not erase voice segments you have created since making the
backup.
For this procedure to work, you must have started WebSphere Voice Response
at least once.
Procedure
1. Log on as dtuser.
2. To stop the node, run dtjstop. If the node was not running, make sure you
have started it at least once since installing the new software.
84 Installation
3. Move to the directory where you put the backup file you created in
“Preparing to migrate VoiceXML and Java applications” on page 38.
4. To restore the backupfile, type the following command and press Enter:
tar -xpvf backupfile
where backupfile is the pathname of the backup file you created in

“Preparing to migrate VoiceXML and Java applications” on page 38.
5. If you have installed a new version of AIX, you may have to restore
applications programs and application-related data.
6. To use the restored default.cff, run dtjconf .
7. To restart the node, run dtjstart.
Rebuilding and reinstalling custom servers

Any custom servers that were installed under a previous release of AIX may
not work following migration, so you must rebuild and reinstall them before
they can be used. Even though the system might indicate that they have
already been installed, they still may not work correctly.
If your custom servers are running on a single system image, and the nodes
of cluster are running different versions of AIX, you must rebuild and reinstall
your custom servers on the node that has the earliest version of AIX.
If you have written your own signalling processes, you will need to rebuild
them because of the increase in the number of channel groups supported.
Prerequisite
The C ++ compiler must already be installed and licensed.
Procedure
Use this procedure to alter the date-time stamp, ensuring that you alter the
correct files in the correct directory for the server.
Start
1. From the Welcome window , select Applications —> Applications to
display the Applications window.
2. Updating the date-time stamp on the .c files: This ensures that every
source file gets recompiled.
In the Applications window, select the Application to which the custom
server belongs, then click Application —> Open.
The system displays the Application window.
3. Click the Custom Servers icon to open the Custom Servers folder.

4. Click the custom server, then click Object —> Open.
The system displays the Custom Server window.
5. Click Utilities —> Import.
The system displays the Custom Server Import window. (This is an AIX
terminal window.)
6. Type touch *.c in the Custom Server Import window and press Enter.
7. Close the Custom Server Import window and repeat steps 4–6 for each
custom server.
8. Rebuilding and reinstalling the custom servers: Use the instructions in
the WebSphere Voice Response for AIX: Custom Servers book to build and
install the servers.
Next step: Before a voice application can use the server, you will also need to
restart it, as described in the WebSphere Voice Response for AIX: Configuring the
System book.
Now go to “Migrating 3270 servers.”
Migrating 3270 servers

If your voice applications use 3270 servers, you need to redefine the 3270 host
interface. You also need to ensure that your SNA network has been configured
correctly (see “Connecting to a 3270 mainframe” on page 101).
When you move data from one pSeries computer to another, using
save-and-restore, the WebSphere Voice Response 3270 session configuration is
duplicated exactly. If the SNA link station names on the second pSeries
computer differ from the first, the 3270 Session Configuration window
displays Profile_not_found for the name of the link station. To remove the
unusable sessions, select the sessions with LU set to Profile_not_found; then
click File —> Delete Objects. Use the information in the WebSphere Voice
Response for AIX: Configuring the System book to configure the new sessions.
If you did not migrate your system using save-and-restore method, you also
need to reconfigure the 3270 sessions (see the WebSphere Voice Response for
AIX: Configuring the System book).
Next step: “Testing that your applications still work.”
Testing that your applications still work

When you have completed the steps in this chapter, you should test that your
applications still work. After you have done this, make another backup copy
of the AIX system image.
86 Installation
You have now completed the installation procedure. You have a basic, usable
WebSphere Voice Response system, although there are some more tasks you
may have to complete.

88 Installation
Chapter 6. Post-installation activities
You now have a working WebSphere Voice Response system with which you
can develop applications and put them into production.
It is likely, however, that you still need to perform one or more of the tasks
described in this chapter before you can consider your installation to be
complete. For some of these tasks, you log on to the WebSphere Voice
Response system and use the windows. For other tasks, you log on as the root
user and use the AIX command line or other tools. Before logging on as root,
read “Setting the WebSphere Voice Response environment.”
This chapter covers the following tasks:

v “Setting the WebSphere Voice Response environment”
v “Defining an exchange data link to AIX” on page 90
v “Checking the tasklist.data file” on page 92
v “Changing the maximum number of user processes” on page 94
v “Increasing the amount of page space” on page 96
v “Copying a configuration on to another pSeries computer” on page 97
v “Configuring attached devices” on page 98
v “Making sure that what you type is what you see” on page 99
v “Changing the AIX password on an SSI database server” on page 100
Setting the WebSphere Voice Response environment

Use this procedure to reset the environment when you are logged on as root.
It sets the file permissions and environment variables as they are for dtuser,
the WebSphere Voice Response user ID. If you are logged on as dtuser, the
environment is already correct, and you can go to the next step.
1. Running the script: Type the following command, then press Enter:
2. Checking the environment: Type the following command, then press
Enter:
echo $VAE
The system displays:
/usr/lpp/dirTalk

Defining an exchange data link to AIX
For an introduction to the exchange data link, see “Exchange data link
connections” on page 23.
Prerequisites
v The exchange data link needs to be attached to the telephone network. (see
“Exchange data link connections” on page 23).
v The AIX operating system needs to be installed (see “Software
prerequisites” on page 15).
How does AIX recognize the link?
To AIX, the exchange data link is simply another piece of hardware that needs
to be defined as a device, just like a printer or a disk drive. The procedure
depends on the type of link:
ACL link
The Multiprotocol Communications Adapter is defined and
configured automatically, and you need only check that its status is
Available.
SMDI, SMSI, or VMS link
The pSeries hardware configuration needs to be changed to include
the link.
Verifying the installation of an ACL exchange data link
Use this procedure to check that the Multiprotocol Communications Adapter
required for an ACL exchange data link has been installed correctly.
Start
2. Starting SMIT : Type smitty commodev, then press Enter.
The system displays the SMIT Communications menu.
3. Verifying the status of the port: If the Multiprotocol Adapter option is
not displayed, check that the Multiprotocol Communications Adapter is
correctly seated.
4. Select Multiprotocol Adapter, then press Enter.
5. Select Adapter, then press Enter.
6. Select Change/Show Characteristics of a Multiprotocol Port, then press
Enter.
7. Select the port you have used for the link, then press Enter.
8. Check that the status of the port is Available.
If the port status is not Available, the most likely cause is a poor
connection between the adapter and its four-port box.
90 Installation
If you are unable to verify that the required port is Available, shut down
AIX, power off the pSeries computer, and check the exchange data link's
physical connections. Then repeat the verification procedure.
9. When you have finished using SMIT, press F10 to exit.
Next step: When you have verified the link, make sure that the tasklist.data
file includes either an ACL or an SMSI process, as described in “Checking the
tasklist.data file” on page 92.
Defining an SMDI, SMSI, or VMS exchange data link to AIX
This procedure employs SMIT commands to define the exchange data link as
a TTY device.
Start
2. Starting SMIT: Type smitty tty, then press Enter.
The system displays the SMIT TTY menu.
3. Identifying the device: Use the cursor keys to highlight Add a TTY, then
press Enter.
The system displays the TTY Type panel.
4. Use the cursor keys to highlight tty rs232 Asynchronous Terminal, then
press Enter.
The system displays the Parent Adapter panel, which lists the serial ports.
5. Use the cursor keys to highlight one of the ports, then press Enter.
The system displays the Add a TTY panel and highlights the Port number
field.
6. Selecting the correct port : Press F4 to display a list of available ports.
Select the port to which you connected the exchange data link cable, then
press Enter.
The system inserts the port identification in the Port number field.
7. Make sure the value in the Enable LOGIN field is disable.
If the exchange data link port is connected to a modem, make sure the
baud rate, parity, and stop bit settings are as recommended by the modem
manufacturer, and that they match the settings defined at the switch end
of the connection.
8. Press Enter.
The system displays the Command Status panel to confirm that the
exchange data link is configured as a TTY and the device is included in
the hardware configuration.
Chapter 6. Post-installation activities 91

Next step: When you have verified the link, make sure that the tasklist.data
file includes either an ACL or an SMSI process, as described in “Checking the
tasklist.data file.”
Checking the tasklist.data file
The tasklist.data file lists the WebSphere Voice Response component
processes. When the system starts, it starts the processes listed in the file. If
one of the processes is missing from the file, or is commented out (preceded
by a # sign), the system does not start that process. If the entire file is missing,
the system does not start at all.
The tasklist.data file needs to be stored in the directory specified by the

$SYS_DIR variable for the WebSphere Voice Response AIX account.
Attention: Make sure there are no trailing space characters on any of the
entries in the file.
Table 7. Entries in the tasklist.data file
A 20 CODECINIT
A 20 DTSNMPD_START 1
B 20 DBIM
A 20 LRS
A 20 OAM
A 20 DBHEALTH
A 20 SDI 2
A 20 VAGIO
A 20 STATEM
A 20 PROMPTM
A 20 CACHEM
H 20 STPDSERVER
H 20 VAGSERVER
H 20 SGAMSERVER
H 20 UPSERVER
H 20 UDSERVER
A 20 CHPM
H 20 DTBEMGR
A 20 CHP
H 20 SCRSERVER
H 20 SMSERVER
H 20 XREFSERVER
H 20 SLDAEMON 2
H 20 CA_CNTL
H 20 CTRL3270 3
A 20 SMSI 4
A 20 ACL 5
H 20 TSLOT
92 Installation
Table 7. Entries in the tasklist.data file (continued)
H 20 MWISERVER
Note:
1. The entry DTSNMPD_START is inserted when you use the DTsnmpd.cfg script (see
“Installing SNMP support” on page 115). Note that it should be the first entry, so
that the snmp daemon is started before anything else and does not miss any
alarms that may occur.
2. Normally, the tasklist.data file should contain an entry for the SLDAEMON and SDI
processes. If you are running WebSphere Voice Response without a digital trunk
adapter (for instance, to develop applications), you can remove these entries (or
precede them with a #) to avoid messages telling you that you are running without
telephony hardware.
3. The CTRL3270 entry is inserted when you install the 3270 option.
4. The SMSI entry is required for an SMDI, SMSI, or VMS data link.
5. The ACL entry is required for an ACL data link.
Procedure
Use this procedure to review the contents of the tasklist.data file, to make
sure that it lists the required processes. You also need to ensure that there is
only one file and that it is stored in the correct directory.
Start
1. Log on to the WebSphere Voice Response AIX account (normally dtuser)
or, if you are already logged on as root, reset the environment (see
“Setting the WebSphere Voice Response environment” on page 89).
2. Enter the following command and press Enter:
cd $SYS_DIR
3. Reviewing the contents of the file: Edit the tasklist.data file.
4. Check the file to make sure it contains all the entries you require (see
Table 7 on page 92).
5. If an entry is missing, add it to the file.
6. If you have changed the file, make sure you save it with your changes.
7. Removing duplicate files : Now, you need to make sure there is no
tasklist.data file in the WebSphere Voice Response binary directory. Type
cd $VAEBIN
ls
The system displays a list of the files in the binary directory.
9. If there is a file in the list called tasklist.data, delete it.

Next step: “Changing the maximum number of user processes.”
Changing the maximum number of user processes

WebSphere Voice Response is a collection of component programs. When
necessary, the system runs multiple copies of the same component program at
once. Each instance of a running program is called a process.
For example, when a call comes in on one of the telephone channels,

WebSphere Voice Response runs the program that manages telephone calls. If
another call comes in before the first call finishes, WebSphere Voice Response
runs another instance of the same program (creates a new process) so that the
calls can be handled simultaneously. During the course of each call,
WebSphere Voice Response starts other processes to handle a voice
application's requirement for information and other services.
In AIX terms, the processes WebSphere Voice Response runs are user processes.
From the AIX point of view, WebSphere Voice Response is just another user.
In WebSphere Voice Response, the process responsible for each call is called a
channel process.
How many user processes can run at once?
AIX includes a parameter to let you limit the maximum number of user
processes that can run at one time. The parameter is called the maximum
number of user processes.
The default value that AIX defines for the maximum number of user
processes is too low for WebSphere Voice Response. Installing the WebSphere
Voice Response software automatically increases this value to 150, if it is not
higher than that already. You might need to increase this further.
How many processes do I need?
As a guideline, you can determine the minimum number of WebSphere Voice
Response processes by adding together:
v The number of channels
v The number of extra channel processes (defined in the Extra Channel
Process parameter, within the Application Server Interface parameter group,
default=10)
v The number of custom server processes
v Twice the number of 3270 sessions
v 50, for WebSphere Voice Response processes
v 50, for user processes
The number of processes you need depends on the configuration of your

system. For example, if WebSphere Voice Response is processing signals from
94 Installation
more than 60 telephone channels, or if you plan to configure 30 or more 3270
sessions, consider increasing the maximum number of user processes to
between 200 and 250. If the number you select is too high, you can always
decrease it. Similarly, use of custom servers increases the number of processes
required.
Note that even if you configure the maximum number of user processes to be
somewhat larger than required, there is no significant AIX performance or
resource penalty.
Procedure
Use this procedure to increase or decrease the maximum number of user
processes. If you have reset the value to more than 150, use this procedure
when you restore WebSphere Voice Response from an image backup. When
the system is restored from an image backup, the maximum number of user
processes is automatically reset to 150.
Start
2. Checking the current parameter value: Type the following command, then
press Enter:
lsattr -E -l sys0
Where l is a lowercase L (for logical device), not the number 1.
The system displays the current values of device attributes on the system.
The value shown for the maxuproc attribute is the current maximum
number of user processes. For example:
maxuproc 150 Maximum number of PROCESSES
3. Resetting the value: To change the maximum number of user processes,
type the following command, then press Enter:
chdev -l sys0 -a maxuproc=maximum_number_of_processes
Where l is a lowercase L (for logical device), not the number 1. For
example, to reset the maximum number of processes to 400, type the
following command:
chdev -l sys0 -a maxuproc=400
The system changes the upper limit on user processes to the number you
indicate, and stores the changed parameter in the database.
Alternatively, you can use smitty chgsys to display a menu that allows
the number of processes to be changed.

Increasing the amount of page space
Page space is space on the hard disk that AIX uses when moving information
into and out of active memory. Moving data between paging space and active
memory should not happen often, because the real-time performance of
WebSphere Voice Response will become significantly degraded. For that
reason it is essential to provide sufficient RAM in the system to enable normal
operation without any paging taking place.
However AIX may occasionally move infrequently used pages out to disk, so
a small amount of paging space is always necessary. The default of 512MB
will work in most cases, but an increase to 2GB may provide a better
safeguard. Because the page space definition is preserved when you create an
AIX image backup, you need these instructions only when you want to alter
the amount of space that is currently defined.
Attention: If you want to increase the size of page space, do not define the
extra space as primary page space. Then, if it turns out you do not need the
extra space, you can delete it easily. (Deleting primary page space involves a
special procedure not documented here.)
Procedure
You can use SMIT to increase the amount of page space or create a new page
space, or you can use these instructions:
Start
2. Determining the current page space: Type the following command, then
press Enter:
lsps -a
The system displays the number of page spaces defined and the size of
each page space logical volume.
3. Calculating how many logical partitions to add: Note how much page
space is currently defined for the volume that needs a larger amount of
page space.
If you need to increase the page space by 40 MB, and the size of a logical
partition is 2 MB, you need to add 20 logical partitions. If the size of a
logical partition is 4 MB, you need to add 10 logical partitions.
There are two ways of increasing the page space:
v Add logical partitions to the existing page space
v Create a new page space.
4. Adding logical partitions: Type the following command, then press Enter:
chps -s number_of_logical_partitions page_space_name
For example:
96 Installation
chps -s 9 paging00
The system adds nine logical partitions to the paging00 logical volume.
5. Creating new page space: Type the following command, then press Enter:
mkps -s number_of_logical_partitions -n -a volume_group_name physical_volume
where number_of_logical_partitions is the number you need for the new
page space. For example:
mkps -s 10 -n -a rootvg hdisk2
The system creates a new page space containing 10 logical partitions on
the rootvg logical volume, using the physical disk hdisk2.
Copying a configuration on to another pSeries computer

When you have installed and configured WebSphere Voice Response on one
pSeries computer, you might want to copy the whole configuration on to
other pSeries computers. This is known as cloning. To clone a WebSphere
Voice Response configuration, use the mksysb command to back up the data
in the root volume group on the first system and then install it on the second
system. The mksysb command is described in “Backing Up Your System” in
the Installation Guide.
After you have loaded the system image onto another pSeries computer and
changed the hostname, you need to run the fsupdate command. You also
need to update the DB2 configuration file /home/dtdb23in/sqllib/
db2nodes.cfg to ensure that the hostname matches the target machine. The
hostname is referenced as 0 hostname 0 within this file, where hostname
matches the output from the AIX hostname command being run on the target
machine.
However, you need to bear in mind that:

v AIX automatically installs only the minimum software filesets for the
devices and machine detected during the installation process. This gives
you the maximum amount of free disk space for your applications.
However, it also means that when you clone a system to a different model
of pSeries computer or to a system with different devices attached, you
may have to install additional software on the second system.
For example, cloning from a system with no token ring adapter to one with
a token ring adapter won't work if the minimum subset of filesets was
installed on the original system. You will need to install the filesets required
to support the token ring adapter after installing the cloned system.
Ideally, if you are planning to clone many systems, you should specifically
install on the original system all the filesets you are going to require to
support all the devices on the other systems.
v You require a software license for each system on which you intend to use
the C or C ++ compiler.

Configuring attached devices
The WebSphere Voice Response definitions for any attached devices you
intend to use must match the AIX definitions created using SMIT. Otherwise,
WebSphere Voice Response cannot find and use these devices.
Change the definition if you redefine a device within AIX, or if you add a
device and the AIX device definition does not match the WebSphere Voice
Response default definition. WebSphere Voice Response includes default
device definitions for a diskette drive, a tape drive, and a communications
port for an exchange data link connection (previously known as TTY or MPQ
port). It does not include a default printer queue definition so, unless you
define one, you won't be able to print any reports, state tables, or other
information from the WebSphere Voice Response interface.
Changing a device definition
Use this procedure if you need to change any of the device definitions.
Start
1. From the Welcome window, select Configuration —> System
Configuration —> Change
2. Changing the port for an exchange data link: Click Exchange Data Link.
The system displays the parameters in the Exchange Data Link parameter
group.
3. Click EDL Communication Port.
4. Click Help for guidance on how to set this parameter according to the
type of exchange data link you intend to use.
5. When you have typed in the correct value, click OK.
6. Close the Exchange Data Link window, by clicking File —> Close.
7. Click File —>Save. If you aren't defining anything else, go to step 20 on
page 99.
8. Changing the other device definitions: Click General.
The system displays the parameters in the General parameter group:
9. Defining the diskette drive: To redefine the diskette drive, click Default
Diskette Drive.
10. Type in the new device definition for the diskette drive.
11. Click OK.
12. Defining the tape drive : To redefine the tape drive, click Default Tape
Drive.
13. Type in the new device definition for the tape drive.
14. Click OK.
15. Defining the printer : To redefine the printer, click Printer Queue.
98 Installation
16. Type in the identification for the print queue.
17. Click OK.
18. Close the WebSphere Voice Response window, by clicking File —> Close.
19. Click File —> Save.
20. Close the System Configuration window, by clicking File —> Close.
The next time you restart WebSphere Voice Response, the system
configuration will include the new devices.
Making sure that what you type is what you see

This section refers to the WebSphere Voice Response user interface only and
will not affect your applications.
About the language environment
The AIX installation process defines certain characteristics of the environment
in which WebSphere Voice Response operates. These characteristics include a
language environment.
The language environment determines what date–time conventions

WebSphere Voice Response uses by default. The language environment also
determines the code set used by default throughout the system. A code set is
a set of all the letters, numbers, and special characters which can be used in
the system. WebSphere Voice Response is designed to operate with the ISO
8859-1 (ISO Latin 1) code set.
If your system code set is not ISO 8859-1, you may see unexpected characters,
particularly if you are using a national language keyboard.
About the keyboard map
The keyboard map correlates each key on the keyboard to a character in the
code set. That is, when you press one of the keys on the keyboard, the
character that WebSphere Voice Response displays on the panel is the
character that is mapped to that key. Not every character in the code set can
be entered directly from every type of keyboard.
Keyboard maps are predefined within AIX and delivered as part of the
system. The system includes maps for use by graphical display terminals as
well as by the system console. You need to ensure that your terminal or
console is configured with the correct keyboard map and code set.
Setting the language environment
You can use SMIT to select the default language environment for your system.
Start

2. Starting SMIT : Type smitty chlang, then press Enter.
The system displays Change/Show Primary Language Environment
menu.
3. Select Select Set of Cultural Convention, Language, and Keyboard, then
press Enter.
The system displays the Select Set of Cultural Convention, Language,
and Keyboard menu.
4. Selecting a language environment:
5. Press F4 to list the available sets. The system displays the Command
Status menu. Press PF10 to exit SMIT.
Changing the AIX password on an SSI database server

When you configure a cluster of WebSphere Voice Response systems as a
single system image (SSI), you have to specify the AIX login user ID and
password of the system you configure as the database server. Therefore if you
change this password, the WebSphere Voice Response clients will no longer be
able to communicate with the server. For this reason, you must follow this
procedure to change the password:
1. Remove every client from the single system image, using the ssirmclient
command. For more information, see the WebSphere Voice Response for AIX:
Configuring the System book.
2. Change the login password on the server.
3. Use the vae.setuser utility to ensure that the file permissions and
ownerships are correct. Type the following command and press Enter, then
follow the prompts:
4. Reconfigure each system that was a client, using the ssimkclient
command. For more information, see the WebSphere Voice Response for AIX:
100 Installation
Chapter 7. Data communications network activities
This chapter provides instructions for the following tasks:
v “Connecting to a 3270 mainframe”
v “Starting Communications Server and the link stations manually” on page
114
v “Starting Communications Server and the link stations automatically” on
page 114
v “Installing SNMP support” on page 115
Connecting to a 3270 mainframe

WebSphere Voice Response can emulate a 3270 terminal to retrieve
information that is stored on an IBM mainframe such as a System/370™, a
System/390® or an AS/400®. To make use of this functionality, you must
ensure that WebSphere Voice Response and the mainframe are part of the
same data communications network and that Communications Server for AIX
is correctly installed and configured on your pSeries computer.
Communications Server for AIX
IBM Communications Server for AIX enables your pSeries computer to
communicate with System/370, System/390 and AS/400 hosts and other
personal computers. The Communications Server gateway allows applications
to run, unchanged, over both SNA and TCP/IP communication networks.
Every data communications network consists of a number of linked elements,

or nodes. The nodes are connected both physically and logically.
Communications Server for AIX enables nodes that have been attached
physically to recognize each other, and to be linked logically. It keeps track of
the location of each node that is part of the network and implements
communication between them.
A single network node is made up of one or more network accessible units

(NAUs). An NAU can be a physical unit (PU), such as a piece of hardware, or
a logical unit (LU), such as a terminal session. A single node can include
multiple NAUs, both PUs and LUs. A single PU can support multiple LUs.
Communications Server for AIX requires that each NAU is configured. The
configuration specifies:
v Where each node is located
v What NAUs are in each node

v How the nodes connect physically
v How they connect logically
Configuring Communications Server for AIX
You must configure Communications Server for the host connection and for
each of the LUs that will be used for 3270 emulation. If the configuration has
already been done for a host connection, you need configure only the LUs.
Configuring Communications Server consists of defining resource information

in a configuration file. You can do this using any of the following:
v The Motif administration tool, xsnaadmin
v SMIT
v The command snaadmin
If you are installing WebSphere Voice Response for the first time, it is
suggested that you use xsnaadmin to create the initial configuration.
If you are migrating from a DirectTalk system that used Version 6.1 or earlier
of Communications Server for AIX, or SNA Server/6000, or SNA
Services/6000, you can use the exportsna utility before you remove that level
of SNA. The exportsna utility creates an ASCII file of the previous
configuration files so they can be migrated and imported to Communications
Server Version 6 using the snamig utility.
No migration is required if you are upgrading from a DirectTalk system that

used Version 5 of Communications Server for AIX, because Communications
Server for AIX Version 6 can use your existing configuration information
without change.
For more information on this, see the Communications Server for AIX: Migration
Guide.
The configuration tasks you need to perform depends on your network

configuration and whether you are sending 3270 data streams over SNA or
over TCP/IP. Use the information provided in:
v Configuring LU 2 sessions
v Configuring an SDLC RS-232 host l link station
v Configuring a token-ring link station
v Configuring a DLUR link station
to identify the information you need, then use the instructions provided in
either “Defining a link station using SNA” on page 104 or “Defining a link
station using TCP/IP” on page 105 to configure Communications Server.
102 Installation
Configuring LU 2 sessions:
v The local LU address, as specified in the LU 2 configuration, is the LU DAF
address. The address is normally assigned by automatic configuration; if
you need to change it, it should correspond to the LOCADDR field in the
LU configuration record on VTAM. This should be different for each LU
which is defined on the PU, with addresses 0 and 1 reserved for SSCP-PU
sessions.
v The SSCP field is a 12-digit hexadecimal number specifying the SSCP. The
first two digits are always 05. The low-order 10 digits contain the SSCP ID.
The default configuration allows any SSCP ID; if you need to restrict it,
select Advanced from the LU Type 0-3 dialog.
v For VTAM Version 3 and above, the network name and LU name need to
be specified in the LU 2 configuration; these are not generated
automatically during quick configuration. The network name should match
the NETID field in the VTAM ATCSTRnn member. The LU name should
be the name assigned on the LU macro in the VTAM definition.
Configuring an SDLC RS-232 host l link station:

v Depending on the type of modem used for the connection, the network
type can be either switched or non-switched. If the line is connected by a
dedicated leased line, the connection is non-switched. If the connection is
made by a dial-up modem, the connection uses the standard switched
network.
v In the SDLC Link Station dialog, the Poll address field gives the polling
address for the PU. It is specified in the VTAM configuration for the PU in
the ADDR field.
v For switched connections, set the Local Node ID field to the value specified
for the PU in the VTAM configuration. The IDBLK field specifies the first
three digits and the IDNUM field specifies the last five digits. This number
is in hexadecimal format.
Configuring a token-ring link station:

v The remote link address is the address, on the token ring, used by the 3745
or 3174 terminal controller for this link station. This value must match the
controller value, or no communication can take place. The field is a 12-digit
hexadecimal value. For 3745 connections, this is specified in the LOCADD
field of the LINE statement.
v In the Port dialog, the Token Ring Card field identifies the token ring
adapter that will be used. With Communications Server for AIX, the
number of link stations that could be defined on one token ring card was
limited by whether they were calling or listen link stations. This restriction
does not apply to Communications Server; however, if you are using
multiple links per adapter, careful configuration is necessary.
Chapter 7. Data communications network activities 103

v For 3174 connections, the Window Size field in the LLC2 Port Parameters
dialog should be less than the W value specified in 3174 customization
question 941. To see the LLC2 Port Parameters dialog, select Advanced
from the port's Token Ring SAP dialog.
v For 3174 connections, the maximum I-FIELD size should match the F value
specified in 3174 customization question 941. To change it, type the
following command:
snaadmin define_tr_port
Then change the max_rcv_btu_size and max_send_btu_size fields.
v For switched connections, set the Local Node ID field to the value specified
for the PU in the VTAM configuration. The IDBLK field specifies the first
three digits and the IDNUM field specifies the last five digits. This number
is in hexadecimal format.
Configuring a DLUR link station:

v The Enterprise Extender (EEDLC) feature of Communications Server for
AIX is used to send 3270 data streams over an IP network. Enterprise
Extender uses a Dependent Logical Unit Requester (DLUR) to connect to
the host machine via a Dependent Logical Unit Server (DLUS) using an
APPC session. The 3270 dependent control sessions flow over this pipe.
v In the DLUR PU window, the DLUR PU and DLUS PU names are eight
character alphanumeric strings. The DLUS PU name should be preceded by
the APPN network name using the form XXXXXXXX.YYYYYYYY
v The linkstation name is the name of the DLUR connection, not the IP link
station itself.
Defining a link station using SNA
Use the command xsnaadmin to define the link station and LU 2 sessions
required. In the following procedure, a token ring connection is used as an
example.
For more detailed information on configuring Communications Server for

AIX, see the Communications Server for AIX: Administration Guide.
Start
2. Configure the node: Type the following command and press Enter.
xsnaadmin
The system displays the Motif CS/AIX Nodewindow.
3. Click Services —> Configure Node Parameters.
4. In the Node Parameters window, specify the Control Point name, then
click OK.
104 Installation
The node box changes from Unconfigured to Inactive.
5. Define a port: Click New.
6. Click Port Using Token Ring Card, then click OK.
7. Define a link station: Click New.
8. Click Link Station to Port portname, then click OK.
The Token Ring Link Station window appears.
9. In the Token Ring Link Station window, select On Node Startup for
Activation, then specify the Local Node ID (XID) and the MAC address.
10. Define the LUs: Click New.
11. Click LU for 3270 Display to Link Station linkstationname, then click
OK.
The LU Type 0-3 window appears.
12. Specify the LU name and select either single LU or a range of LUs and
specify a range of numbers.
When you have completed the configuration, start Communications Server for
AIX using the procedure in “Starting Communications Server and the link
stations manually” on page 114.
Defining a link station using TCP/IP
Use the command xsnaadmin to define the link station and LU 2 sessions
required.
For more detailed information on configuring Communications Server for

AIX, see the Communications Server for AIX: Administration Guide.
Start
2. Configure the node: Type the following command and press Enter.
xsnaadmin
The system displays the Motif CS/AIX Node window.
3. Click Services —> Configure Node Parameters.
4. In the Node Parameters window, specify the Control Point name, then
click OK.
The node box changes from Unconfigured to Inactive.
5. Define a port: Click New.
6. Click Enterprise Extender (HPR/IP), then click OK.
7. Define a link station: Click New.
8. Click Link Station to Port portname, then click OK.
The IP Link Station window appears.

9. In the IP Link Station window, select On Node Startup for Activation,
then specify the Remote IP hostname.
10. Define the DLUR PU: Click New.
11. Click DLUR PU, then click OK.
The DLUR PU window appears.
12. In the DLUR PU window, specify a name for the DLUR PU and the
name and PU ID for the DLUS.
Optionally, select Initially Active and Retry Contacting DLUS
Indefinitely.
13. Define the LUs: Click New.
14. Click LU for 3270 Display to Link Station linkstationname, then click
OK.
The LU Type 0-3 window appears.
15. Specify the LU name and select either single LU or a range of LUs and
specify a range of numbers.
16. Click Advanced
17. Click LU use and select CS/AIX V4.2 LU1-3.
18. Type the fully qualified partner LU name and click OK.
19. Click OK again.
When you have completed the configuration, start Communications Server for
AIX using the procedure in “Starting Communications Server and the link
stations manually” on page 114.
How does the other computer recognize WebSphere Voice Response?
Communications Server for AIX manages only the pSeries computer. Other
components on the network may require additional information before they
can communicate with WebSphere Voice Response. For example, when the
network connects the pSeries computer to a remote computer through a
communication controller, both the remote computer and the controller need
to be made aware that the pSeries computer is part of the network. When the
connection is to an IBM System/370 processor, the VTAM definition file needs
to include the pSeries computer.
Configuring host communication for WebSphere Voice

Response
You must define to VTAM a physical unit (PU) with at least one logical unit
(LU) for communication to the pSeries computer. Define the PU with a
MAXDATA parameter of at least 256 and PUTYPE=2. All other parameters are
dependent on the connection type to the host. Define at least one LU for 3270
emulation. Define the 3270 emulation LU with the following parameters:
Nonnegotiable bind
106 Installation
FM Profile (FMPROF)=3
TS Profile (TSPROF)=3
FM usage-Primary LU protocols (PRIPROT)=x’11’,x’21’,x’31’,x’91’,x’A1’,
or x’B1’
FM usage-Secondary LU protocols (SECPROT)=x’B0’,x’90’, or x’A0’ for
displays, also x’10’,x’20’,x’30’ for printers.
FM usage-Common LU Protocols (COMPROT)=x’3080’,x’7080’ for LU1 printers.
Pacing=none required
LU type=LU2 (PSERVIC = x’028000000000000000000200’)
or
LU type=LU3 (PSERVIC = x’038000000000648400007E00’)
or
LU type=LU1 (PSERVIC = x’01000000E100000000000000’)
The values specified for the PSERVIC fields are not the only valid values that
can be entered. The PSERVIC field controls the LU type and screen or print
buffer options and sizes. Other valid 3270 settings can be used in this field.
Configuring the mainframe computer for connection over

TCP/IP
Use this procedure to help you configure your mainframe computer to

communicate with WebSphere Voice Response over a TCP/IP network. For
complete instructions see Communications Server for AIX: Administration Guide.
Additional information is provided in the IBM Redbook Migrating Subarea
Networks to an IP Infrastructure Using Enterprise Extender.
1. Configure a VIPA address in the TCP/IP stack that Enterprise Extender
will use.
2. Set up an Enterprise Extender connection. The connections are defined to
VTAM as shown in the following example:
AP24XCAE VBUILD TYPE=XCA
IYCOZXP1 PORT MEDIUM=HPRIP,
IPTOS=(20,40,80,C0)
LIVTIME=10,
SAPADDR=8,
SRQRETRY=3
SRQTIME=15
IYCOZXG1 GROUP DIAL=YES,CALL=INOUT,
DYNPUPFX=IY,
DYNPU=YES,
AUTOGEN=(24,EEL,EEP)
Switched XCA major node
Switched major node configuration
AP24SMNX VBUILD TYPE=SWNET
IYCOR000 PU PUTYPE=2,
CPNAME=NETLEY,
ADDR=01,

ASDP=YES,
NETID=GBIBMIYA,
CPCP=YES,
CONNTYPE=APPN,
TGN=3, USE 3 FOR ENTERPRISE EXTENDER
HPR=YES,
DWACT=NO,
XID=YES,
TGP=TRING16M, USE THIS TG PROFILE IN IBMTGPS
ISTATUS=ACTIVE
*
IYCOP000 PATH IPADDR=0.00.00.00, IP ADDR OF WORK STATION
GRPNM=IYCOZXG1 REFERS TO GROUP NAME IN XCA MAJNODE
3. Configure a DLUR connection. Use the following example as a guide:
AP24SMNY VBUILD TYPE=SWNET
IYCOR00A PU PUTYPE=2,
IDBLK=071,
IDNUM=1111A,
MODETAB=SNATERM#,
LOGTAB=LOGTAB00,
USSTAB=UTCPPTOK,
SSCPFM=USSSCS,
VPACING=0,PACING=0,
ISTATUS=ACTIVE
*
IYCOT042 LU LOCADDR=2,ISTATUS=ACTIVE
etc to
*
* Example of an additional DLUR connection
IYCOR005 PU PUTYPE=2,
IDBLK=071,
IDNUM=11115,
MODETAB=SNATERM#,
LOGTAB=LOGTAB00, INTERPRET TABLE IN SYS2.VTAMLIB
USSTAB=UTM24TOK,
SSCPFM=USSSCS,
VPACING=0,PACING=0,
ISTATUS=ACTIVE
*
Example scenarios
The configuration tasks you need to perform depends on how your network
is configured. There are four example configurations provided here. These
particular physical link stations support the exchange of information between
108 Installation
WebSphere Voice Response and any application running on a System/370,
System/390, or AS/400 processor that communicates through a 3270 data
stream using LU 2 protocols.
If your network is not similar to one of the examples, use the information in
the System Management Guide; Communications and Networks, to determine how
to define it.
Example SNA link station A
In example A (shown in Figure 8), a pSeries computer is connected on a

token-ring LAN, through an IBM 3174 Establishment Controller, to an IBM
System/370, System/390, or AS/400.
Local
Area
WebSphere
Voice Network
Reponse
pSeries
IBM 3174 System/390
Figure 8. Communications network, example A
Connecting the to a System/370 or System/390:
This procedure describes how to connect the pSeries computer to a

System/370 or System/390 in the configuration shown in Figure 8.
1. On the System/370 or System/390: Create an entry in the VTAM definition
file for each downstream physical unit (DSPU): the IBM 3174 and the
pSeries computer.
2. Create a logmode entry.
3. On the pSeries computer: Use xsnaadmin to configure the token-ring link
station (see “Defining a link station using SNA” on page 104).
4. Configure the 3174 to include the address (or alternate address) of the
token-ring adapter in the pSeries computer.
5. Start Communications Server for AIX.
Connecting the to an AS/400:

This procedure describes how to connect the pSeries computer to an AS/400
in the configuration shown in Figure 8 on page 109.
1. On the AS/400: Create a network description object, a controller
description object, and a device description object (one for each terminal).
3. Configure the 3174 to include the address (or alternate address) of the
Example SNA link station B
In example B (shown in Figure 9), two pSeries computers are connected on a

token-ring LAN, through a communication controller, to an IBM System/370
or System/390. You can also attach the pSeries computers on the LAN to an
AS/400. In this case, the communication controller is internal to the AS/400.
Local
Area
WebSphere
Voice Network
Reponse
pSeries
WebSphere
Voice IBM
Reponse
3745 System/390
Communications
pSeries Controller
Figure 9. Communications network, example B

file for each downstream pSeries computer.
2. Create an NCP for the communication controller, or alter any existing NCP
to reflect the additional DSPUs.
110 Installation
4. Reinitialize the communication controller.

1. On the AS/400: Create a connection definition object, a controller
description object, and a device description object (one for each logical
device).
Example SNA link station C
In example C (shown in Figure 10), a pSeries computer is connected, using an

SDLC connection through a communication controller, to an IBM System/370
or System/390. You can also attach the pSeries computer to an AS/400 using
an SDLC connection. In this case, the communication controller is internal to
the AS/400
EIA 232,
V.24 or V.35
WebSphere
Voice
Reponse
Modem Modem
pSeries
IBM
3745
Communications
Controller
System/390
Figure 10. Communications network, example C

System/370 or System/390 in the configuration shown in Figure 10 on page
111.
1. On the System/370 or System/390: Create an NCP for the network
controller, or alter any existing NCP to reflect the additional DSPUs.
4. On the pSeries computer: Use xsnaadmin to configure the SDLC link

1. On the AS/400: Create a connection definition object, a controller
description object, and a device description object (one for each logical
device). Create a logmode entry.
2. On the pSeries computer: Use xsnaadmin to configure the SDLC link
Example SNA link station D
In example D (shown in Figure 11 on page 113) up to four pSeries computers

on a token-ring LAN are connected to an IBM System/370 or System/390,
using an SDLC connection through an IBM 3174 and a communication
controller.
112 Installation
Local
Area
WebSphere
Voice
Network
Reponse
IBM 3174
pSeries
EIA 232
V.24 or V.35
Modem Modem
WebSphere
Voice
Reponse
IBM
pSeries 3745
Communications
Controller
System/390
Figure 11. Communications network, example D
Connecting the s:
This procedure describes how to connect several pSeries computers to a

file for each downstream physical unit: the SDLC link station, the IBM
3174, and the pSeries computers.
2. Create an NCP for the communication controller, or alter any existing NCP
to reflect the additional DSPUs.
6. Configuring the 3174: Configure the 3174 to include the address of the

Starting Communications Server and the link stations manually
Starting Communications Server for AIX establishes the network defined by
the information in the SNA configuration. Starting the link stations activates
the physical link defined by each link station.
You may have to stop a link station or SNA before you change SNA
configuration. If you do, or if AIX stops, you can start Communications Server
for AIX and the link stations manually. You can also edit the resource (.rc) file
for Communications Server for AIX so that both Communications Server for
AIX and the link stations start automatically every time you restart AIX; see
“Starting Communications Server and the link stations automatically.”
Procedure
Use this procedure to start Communications Server for AIX, or a link station,
or both, manually.
Start
2. Starting xsnaadmin: Type xsnaadmin, then press Enter.
The system displays a Motif window, named CS/AIX Node.
3. Starting Communications Server for AIX: Click hostname Inactive.
The system starts Communications Server for AIX.
4. Starting a link station: Click the line that contains the name of the link
station you want to start.
The line is highlighted.
5. Click Start.
The system starts the link station.
Starting Communications Server and the link stations automatically

Use this procedure to make sure that Communications Server for AIX and the
link stations start whenever you restart AIX.
Procedure
Start
2. Starting Communications Server automatically: Type the following
command, then press Enter:
lsitab sna
3. If the sna line is not found, type the following command, then press Enter:
mkitab "sna:2:wait:/etc/rc.sna > /dev/console 2>&1 #start SNA Daemons"
114 Installation
(There is one blank space between rc.sna and >, and one blank space after
>.)
4. Edit the /etc/rc.sna file.
5. Find the line that reads #/usr/bin/snaadmin init_node, and remove the #
(which is a comment indicator).
6. Starting all link stations automatically : Ensure that Activation has been
set to On Node Startup (see “Defining a link station using SNA” on page
104).
Alternatively, add the following line to the file:
/usr/bin/snaadmin start_ls, ls_name=link_station_name
7. Save the file.
8. Shut down the AIX system using the shutdown -Fr command and restart
it to make the changes take effect.
Installing SNMP support

The Simple Network Management Protocol (SNMP) can be used as the basis
of remote system management and monitoring. Follow this procedure to make
WebSphere Voice Response information available to the network operator.
Prerequisites
v AIX SNMP support (the snmpd daemon included with the TCP/IP support
in the base operating system) has been installed.
v You need to know the root password.
Procedure
Start
1. Log on as dtuser.
2. Adding WebSphere Voice Response SNMP definitions: Use the
DTsnmpd.cfg script to:
v Add or upgrade the WebSphere Voice Response information in the
Management Information Base (MIB) definitions file (/etc/mib.defs)
and the snmpd configuration files (/etc/snmpdv3.conf and
/etc/snmpd.peers)
v Add the entry for DTSNMPD_START to the tasklist.data file (shown in
Table 7 on page 92).
Type the following command and press Enter:
/usr/lpp/dirTalk/tools/DTsnmpd.cfg
Enter the root password when requested.
By default, this script removes any existing WebSphere Voice Response
definitions from /etc/mib.defs, /etc/snmpdv3.conf and /etc/snmpd.peers,
and then adds the current WebSphere Voice Response data. The following
message is displayed:

DTsnmpd.cfg is about to add/replace WebSphere Voice Response entries in
/etc/snmpdv3.conf and /etc/snmpd.peers. Existing
versions will be saved as /etc/snmpdv3.conf.save and
/etc/snmpd.peers.save
Note: In AIX 6.1, the default level of snmpd is version 3. The

configuration file for version 3 is /etc/snmpdv3.conf.
Optionally, you can completely rebuild /etc/mib.defs from the MIB
definitions in /usr/samples/snmpd, but only if these samples and the MIB
compiler (mosy) are installed. This should not normally be necessary.
After running DTsnmpd.cfg, the following line of WebSphere Voice
Response data is added to /etc/snmpdv3.conf:
smux 1.3.6.1.4.1.2.6.30 "directTalk6000" # Added by DTsnmpd.cfg
The DTsnmpd.cfg script does not give you the opportunity to change any
other information in the /etc/snmpdv3.conf files, but you can make other
changes by logging on as root and editing the required file directly. Any
changes you make are not overwritten by subsequently
runningDTsnmpd.cfg. If you make any changes after running DTsnmpd.cfg,
refresh the snmpd daemon to activate those changes, by using the
following command when logged on as root:
refresh -s snmpd
If you are using SNMP to control WebSphere Voice Response remotely, as
described in the WebSphere Voice Response for AIX: Managing and Monitoring
the System book and to run any of the snmpinfo set commands, you must
have write access to certain MIB definitions.
To set up the correct writeView for VACM_ACCESS.
a. Verify the version of snmpd in use by entering the command:
ls -l /usr/sbin/snmpd
If the file is linked to snmpdv3ne, version 3 is in use and the correct

configuration file is therefore /etc/snmpdv3.conf.
b. Update the configuration file to grant the write permission for user: In
snmpdv3.conf, the writeView parameter for group1 under VACM_ACCESS
is set by default to - as shown below:
#VACM_ACCESS groupName contextPrefix contextMatch securityLevel securityModel readView writeView notifyView storageType
VACM_ACCESS group1 - - noAuthNoPriv SNMPv1 defaultView - defaultView -
Change the - to defaultView to grant the write permission as shown

below:
#VACM_ACCESS groupName contextPrefix contextMatch securityLevel securityModel readView writeView notifyView storageType
VACM_ACCESS group1 - - noAuthNoPriv SNMPv1 defaultView defaultView defaultView -
c. Recycle snmpd by entering these commands:

stopsrc -s snmpd
startsrc -s snmpd
116 Installation
3. Enabling the WebSphere Voice Response SNMP daemon to be started
automatically : You may want the WebSphere Voice Response SNMP
daemon to start automatically whenever AIX is restarted, even if
WebSphere Voice Response itself is not started. This ensures that the
daemon does not miss any WebSphere Voice Response alarms that might
occur, and allows WebSphere Voice Response to be started remotely via
SNMP.
Use your editor to open the rc.dirTalk file in the /etc directory.
4. Remove the # from the following entries:
#/usr/lpp/dirTalk/tools/vae.setenv
#/usr/lpp/dirTalk/sw/bin/DTSNMPD_START
5. Ensure that the AIX snmpd daemon itself is automatically restarted
whenever AIX is restarted. For more information on the snmpd daemon,
see the Commands Reference.
6. Save the modified rc.dirTalk file.
7. Specifying options when starting the SNMP daemon: You can specify
options when the SNMP daemon is started. To do this, edit the
DTSNMPD_START script. The same options are used whether the daemon is
started independently of WebSphere Voice Response or with WebSphere
Voice Response, because the same script is used for both. For details of the
dtsnmpd options, see the WebSphere Voice Response for AIX: Configuring the
System book.
8. Updating the SNMP system directory: You might need to provide the
WebSphere Voice Response SNMP MIB definition to the application you
are using for SNMP network management. Consult the documentation
accompanying the application for the proper method of doing this. The
MIB definition is supplied in two formats, and both files are located in the
SYSPARM_DIR directory on the system where WebSphere Voice Response is
installed:
dtsnmpd.my file
Transfer this file to the directory where the MIB is located, on the
system where the system-management application is to run.
dtsnmpd.defs file
This file has been compiled using the mosy command and is in
the format used in the /etc/mib.defs file. You can add the
contents of the file to the end of the /etc/mib.defs file on the
system on which the system-management application is to run.
The /etc/mib.defs file is used by SNMP commands, such as
snmpinfo. (The snmpinfo utility is supplied with the AIX Base
Operating System TCP/IP Server, and is located in the /usr/sbin
directory.)
Use the ftp command or Network File System (NFS) to transfer
the dtsnmpd.my file, or write the file to diskette or tape from the

WebSphere Voice Response system and restore it to the
appropriate directory on the system on which the
system-management application is to run.
WebSphere Voice Response's SNMP support is now installed.
118 Installation
Chapter 8. Starting, stopping, and restarting WebSphere
Voice Response
This chapter provides the following information:
v “More about starting WebSphere Voice Response”
v “Shutting down WebSphere Voice Response” on page 122
v “Shutting down WebSphere Voice Response automatically on AIX
shutdown” on page 124
v “Restarting WebSphere Voice Response” on page 124
v “Problems with starting WebSphere Voice Response” on page 126
v “The WebSphere Voice Response Graphical User Interface doesn't start” on
page 129
v “If you have trouble starting WebSphere Voice Response” on page 131
More about starting WebSphere Voice Response

“Starting WebSphere Voice Response” on page 67 describes the standard
procedure for starting WebSphere Voice Response, which you use during
installation. This section gives you some more background on startup
procedures. It tells how you can configure your system to start WebSphere
Voice Response more easily, and describes how to start up WebSphere Voice
Response from a remote terminal.
Java and VoiceXML environment
If the system parameter Start Java and VoiceXML Environment
Automatically is set to yes, then the Java and VoiceXML environment is
started automatically when WebSphere Voice Response starts. Ensure that you
read WebSphere Voice Response for AIX: Deploying and Managing VoiceXML and
Java Applications for detailed information about configuring the Java and
VoiceXML Environment before you attempt to start it.
Display names
If AIXwindows is already running (for example, if you logged on as root,
started AIXwindows, and then opened an aixterm window), you need to
know the name of your display. This is normally stored in the $DISPLAY
variable. If this variable has not been set, contact your system administrator.
Creating a display name file
To avoid entering a display name every time you start WebSphere Voice
Response, you can create a display name file. The display name file must be
stored in the directory defined by the value of $HOME in the profile for the

WebSphere Voice Response user. This means that the WebSphere Voice
Response windows will always start on this display.
Procedure
Start
1. Log on as dtuser. Do not start WebSphere Voice Response.
2. The display name for a terminal is the terminal name, not the name of the
host system from which the terminal is booted. If you are unsure of the
correct display name, type echo $DISPLAY at the command prompt and
press Enter.
The system shows the display name.
3. Create a new file called .display.cfg in the $HOME directory.
4. Add a single line to the file that identifies the display by name.
For example, if your display is called magpie, and you plan to use a single
instance of the X server, add a line that looks like this:
magpie:0
5. Save the file.
The system uses the display name in this file whenever you start WebSphere
Voice Response.
Using the status file
System initialization is recorded in a file called DTstatus.out. If there is a
problem starting WebSphere Voice Response, you may be able to determine
the cause by looking at this file. The information in the file always documents
the most recent attempt to start the system.
DTstatus.out is stored in the $OAM_LOG_PATH database directory. The full path

name is /home/dirTalk/current_dir/oamlog/DTstatus.out.
For more information on DTstatus.out, refer to the WebSphere Voice Response

for AIX: Configuring the System book.
Using the status window
The system displays the information it is writing to the status file in a status
window. The status window is a standard aixterm window, not a WebSphere
Voice Response window. It can remain open, displaying the system status,
while you work with WebSphere Voice Response.
If you do not want to monitor the system's status, close the status window.
Because it is an aixterm window, you can either minimize it or press Ctrl+C
to close it completely.
120 Installation
Starting WebSphere Voice Response from a remote terminal
A remote terminal is one that enables you to access the WebSphere Voice
Response system on the network using the telnet command.
Before a remote terminal can display the WebSphere Voice Response

windows, you need to give the WebSphere Voice Response system permission
to display the windows on the remote terminal. You also need to be running
AIXwindows on the remote terminal. The easiest way is to use SMIT
commands.
Start
1. Log on to the remote terminal.
2. Starting AIXwindows: If AIXwindows does not start automatically, type
startx and press Enter:
The system starts the X server program that starts AIXwindows.
3. Giving the server permission : Type the following command and press
Enter:
xhost +name
where name is the name of your WebSphere Voice Response system.
tn name
where name is the name of your WebSphere Voice Response system.
5. If you have not already used the vae.setuser utility, or you have installed
WebSphere Voice Response software since it was last used, you must run
it before using the vaeinit command. See “Setting the dtuser file
permissions” on page 49 for instructions.
6. Log on to the AIX user account that is set up for WebSphere Voice
Response (normally dtuser). This should start the initialization sequence.
If it does not, type vaeinit and press Enter.
The WebSphere Voice Response User Login menu is displayed:
If the Login menu is not displayed, type the following command on the
AIX command line and press Enter:
vaeinit
7. Type 1 and press Enter.
The system prompts you for your display name.
8. Type your display name, using the following format:
name:number
Chapter 8. Starting, stopping, and restarting WebSphere Voice Response 121

where name is the host name, and number is the session number
(normally 0); for example, magpie:0. Press Enter.
The system displays the Status window; most of the time, you can keep
this window minimized. The system then displays the Welcome window
and the Logon window.
9. If you have not yet created any other administrator profiles, enter admin
in the Administrator Profile Name field; otherwise enter the name of
your administrator profile. Note that the field is case-sensitive, so be
careful about typing uppercase or lowercase characters as appropriate.
10. Type your password in the Password field. This field is also
case-sensitive. The supplied password for admin is also admin.
Attention: It is strongly recommended that you change this password
immediately; see the WebSphere Voice Response for AIX: Configuring the
System book for details.
11. Click Logon, or press Enter.
The system activates all menus on the Welcome window menu bar:
You can now continue to use WebSphere Voice Response on the remote
terminal.
Shutting down WebSphere Voice Response

There are two ways to shut down the system using the WebSphere Voice
Response windows:
Immediate shutdown
Stops everything as quickly as possible. Any telephone calls in
progress are terminated instantly.
Quiesce shutdown
Stops everything more gracefully. All telephone calls in progress are
allowed to complete before the system stops.
In both cases, if the system parameter Start Java and VoiceXML Environment
Automatically is set to yes, the Java and VoiceXML environment will also be
stopped.
In addition, you can use the DT_shutdown command, which shuts down
WebSphere Voice Response immediately, and also ends any long-running
processes, including the DTBE host manager.
Prerequisites
When you are shutting down the system before installing new packs or
adapters, set the trunk status of any affected packs to Defined before shutting
down.
122 Installation
Procedure
Attention: Always shut down WebSphere Voice Response using this
procedure (or use the DT_shutdown command). If you attempt to stop the
system in any other way, processing may not terminate correctly and the
system may not be able to start again.
Start
1. From the Welcome window, select Operations
2. If other people are using WebSphere Voice Response, give them adequate
warning that you are going to shut it down.
3. Shutting down without letting calls terminate first: Click Immediate
Shutdown.
If anyone else is currently using WebSphere Voice Response, it asks you to
confirm that you want to shut down.
4. If you are sure you want to shut down regardless, click OK.
WebSphere Voice Response shuts down all windows, cleans up the
database and stops all foreground and background processes.
If you decide to leave the system running, click Cancel.
5. Shutting down gracefully: Click Quiesce Shutdown.
If anyone else is currently using WebSphere Voice Response, it asks you to
confirm that you want to shut down.
6. If you are sure you want to shut down regardless, click OK.
WebSphere Voice Response shuts down all windows, cleans up the
database and stops all foreground and background processes.
If you decide to leave the system running, click Cancel.
Do not restart WebSphere Voice Response immediately. Always wait until you
see the “Node Manager terminating” message in the WebSphere Voice
Response status window before you try to restart WebSphere Voice Response,
to allow all processes to terminate properly. Proper termination is particularly
important if Communications Server is running with a large number of logical
units.
For details of the DT_shutdown command, refer to WebSphere Voice Response

for AIX: Managing and Monitoring the System.

Shutting down WebSphere Voice Response automatically on AIX shutdown
Use the following procedure to configure WebSphere Voice Response to shut
down automatically when the AIX operating system is shut down.
Start
2. Editing the script: Edit or create the rc.shutdown script in the /etc
directory.
3. Add the following lines to the script:
if [ -x /usr/lpp/dirTalk/tools/DT_shutdown ]
then
/usr/lpp/dirTalk/tools/DT_shutdown
fi
exit 0
5. Activating the script: To make the script executable, type the following
command on the command line, then press Enter:
chmod +x /etc/rc.shutdown
Restarting WebSphere Voice Response

WebSphere Voice Response includes an automatic restart feature. If you are
using WebSphere Voice Response and something happens that causes AIX to
stop running (such as a power failure), AIX automatically restarts WebSphere
Voice Response when it restarts. (If you were not using WebSphere Voice
Response when AIX stopped, AIX starts again, but does not restart WebSphere
Voice Response automatically.)
Always wait several minutes before you try to restart WebSphere Voice
Response. Waiting allows all processes to terminate properly. Proper
termination is particularly important if Communications Server is running
with a large number of logical units.
Using auto restart
When WebSphere Voice Response stops suddenly and abnormally, some
information may be lost. Even with auto restart turned on, WebSphere Voice
Response might not be able to start correctly. If you have trouble restarting
WebSphere Voice Response, use the information in “Problems with starting
The automatic restart capability is enabled by default when the software is

installed. Use the following procedure to disable automatic restart.
124 Installation
Start
1. Turning auto restart off : Log on to AIX as root, if you are not logged on
already.
rmitab "dtauto"
WebSphere Voice Response will not automatically restart if AIX terminates

abnormally.
Use this procedure to enable automatic restart if it has been disabled.
Start
1. Turning auto restart on: Log on to AIX as root, if you are not logged on
already.
lsitab dtauto
3. If the dtauto line is not found, type the following command (all on one
line) and press Enter:
mkitab "dtauto:2:once:/usr/lpp/dirTalk/tools/vaeinit.pre
>/dev/console 2>&1 #Autostart WebSphere Voice Response"
WebSphere Voice Response will automatically restart if AIX terminates

abnormally.
When WebSphere Voice Response restarts automatically, the WebSphere Voice

Response processes start and run. The console displays informational
messages, and the error log contains a message reporting that the system was
restarted automatically. However, the AIXWindows manager is not a
WebSphere Voice Response process. The automatic restart process does not
start AIXwindows or any of the WebSphere Voice Response
AIXwindows-dependent processes.
Start
1. Restarting the WebSphere Voice Response windows: Log on as dtuser
from an aixterm window.
The system displays the following menu:
2. Type 1 and press Enter.
The WebSphere Voice Response Logon window is displayed.

Next step: You can now log on as described in “Starting WebSphere Voice
Problems with starting WebSphere Voice Response

This section provides help for the following situations:
v “The system does not start at all”
v “The system does not display the Welcome window” on page 127
v “WebSphere Voice Response windows become active without being
selected” on page 127
v “The system does not behave as expected” on page 129
The system does not start at all
If the system does not start at all, the WebSphere Voice Response system
parameter files may be corrupted. If you restore the values that were supplied
with WebSphere Voice Response, you will be able to start the system. You can
then change any inappropriate values to suit your requirements.
Alternatively, if you have your own backup version of the system parameters,
you can restore that version.
Restoring the default system parameter values
Use this procedure to restore the default system parameter values for
WebSphere Voice Response.
Start
1. Log on as dtuser or, if you are already logged on as root, reset the
environment (see “Setting the WebSphere Voice Response environment” on
page 89).
2. Restoring parameters to their default values: To restore the default
values, type the following command and press Enter:
cp $SYSPARM_DIR/rd.data.orig $SYSPARM_DIR/rd.data
You have now restored the parameter values that were supplied with
WebSphere Voice Response, and you should be able to start the system. It is
important that dtuser owns the restored files. If it does not, refer to the AIX
documentation for information on changing access permissions.
When you have successfully started WebSphere Voice Response, you can
change any system parameters to suit your requirements.
126 Installation
Restoring a backup version of the system parameters
Use this procedure to restore a backup version of your system parameters.
Start
1. Log on as dtuser or, if you are already logged on as root, reset the
page 89).
2. Restoring parameters to their configured values: To restore a different set
of values, type the following command and press Enter:
cp $SYSPARM_DIR/yourfilename $SYSPARM_DIR/rd.data
Make sure you specify the backup file that contains the correct parameter
values.
You have now restored your parameter values from a backup version. It is
important that dtuser owns the restored files. If it does not, change the access
permissions.
Now try to start the system. If you have any problems, it may be better to
restore the parameter values supplied with this release (see “Restoring the
default system parameter values” on page 126).
The system does not display the Welcome window
If the system starts but does not display the Welcome window, then:
v You might have typed the name of a different display. If you were not
asked to provide a display name, you might already have a $DISPLAY
variable set in your .profile, .display.cfg file or environment. If you
specify a different display name, and the display exists, the system displays
the Welcome window on that display. If you mistyped the name, and it is
not the name of a real display, WebSphere Voice Response does not start.
v You might not have given the WebSphere Voice Response system authority
to display windows on your display (see “Starting WebSphere Voice
Response from a remote terminal” on page 121).
Before you can start WebSphere Voice Response again, you need to stop the
DT process that has started running. See “The WebSphere Voice Response
Graphical User Interface doesn't start” on page 129 for details.
WebSphere Voice Response windows become active without being
selected
If you start WebSphere Voice Response and the windows display correctly but
become active without being explicitly selected, the window manager may be
using the wrong keyboard focus policy.

The window manager focus policy is set in a file called .Xdefaults. The
master .Xdefaults file is included in the AIXwindows software. However,
anyone who uses the system can copy the .Xdefaults file into their own
directory and edit it to suit their preference.
If you are using AIX windows
Use this procedure to change the keyboard focus policy.
Start
1. Log on as dtuser, or if you are already logged on as root, reset the
page 89).
2. To make sure you are in the home directory, type the following command
and press Enter:
cd $HOME
3. To display the contents of the directory, type the following command and
press Enter:
ls -a
4. Look for a file named .Xdefaults. If the file is not there, use the AIX
documentation to find out where else to look.
5. Edit the .Xdefaults file.
6. Find the lines that specify the keyboard focus policy. Make sure they read
as follows:
Mwm*focusAutoRaise:true
Mwm*keyboardFocusPolicy:explicit
xrdb $HOME/.Xdefaults
The keyboard focus policy is now correct.
If you are using the common desktop environment
Use this procedure if you are using the common desktop environment (CDE).
Start
1. Log on as dtuser and start the common desktop environment.
2. Click the Style Manager icon.
3. In the Style Manager, click the window icon.
4. In the Style Manager Window, click Click in Window to Make Active and
Raise Window When Made Active.
128 Installation
5. Click OK.
6. Restart the common desktop environment.
The keyboard focus policy is now correct.

The system does not behave as expected
When you start WebSphere Voice Response as described in “Starting
WebSphere Voice Response” on page 67, the system starts both the
background and foreground processes. If some of the processes do not start
correctly, the Welcome window might be displayed and you might be able to
log on to WebSphere Voice Response, but the system will not behave as
expected.
Check that the tasklist.data file is not corrupted or missing, and that it has
all the entries you need (see “Checking the tasklist.data file” on page 92).
The WebSphere Voice Response Graphical User Interface doesn't start

The WebSphere Voice Response for AIX: Managing and Monitoring the System
book explains how to stop WebSphere Voice Response by shutting down the
system from the Welcome window. If you stop the system without shutting it
down, the background processes may not terminate correctly.
Although Ctrl+Alt+Backspace shuts down AIXwindows, it does not stop the

background processes. In addition, when you log on again, at least one buffer
is lost. If you continue to do this, it is possible to use up the buffer pool. For
these reasons, stopping the X server without shutting down WebSphere Voice
Response first is not recommended. Always stop WebSphere Voice Response
by selecting one of the shutdown options.
There may be a time when the system starts, the Welcome window is
displayed, but you cannot log on from the Welcome window (the cursor still
looks like a wristwatch). This can occur because of timing problems in the
initialization procedure caused by system resource constraints. To rectify this,
interrupt the Welcome window process (the DT process) using the kill
command, and then restart it.
If WebSphere Voice Response starts but does not allow you to log on, you
cannot stop it by selecting a shutdown action. Use the procedure set out in
“Stopping the run-time system” on page 130 to terminate the component
processes and stop WebSphere Voice Response cleanly.
Stopping the WebSphere Voice Response windows
This procedure stops the WebSphere Voice Response windows, but not the
run-time system.

Start
1. Log on as dtuser, or if you are already logged on as root, reset the
page 89).
2. Listing the running processes : Type the following command and press
Enter:
ps -def | grep DT
The system displays the process ID (PID) for the DT process. (Not all PIDs
contain the same number of digits.)
3. Stopping WebSphere Voice Response : Type the following command and
press Enter:
kill -2 DT_process_ID
The system interrupts the DT process. The Welcome window disappears.
To start the WebSphere Voice Response windows again, make sure you are
logged on as dtuser, type the following command, and press Enter:
DT &
Stopping the run-time system

This procedure shuts down the WebSphere Voice Response system.
Start
1. Restarting WebSphere Voice Response: Log on as dtuser or, if you are
already logged on as root, reset the environment (see “Setting the
WebSphere Voice Response environment” on page 89).
2. Stopping WebSphere Voice Response : Type the following command and
press Enter:
DT_shutdown
The system shuts down all WebSphere Voice Response processes and
ensures that all resources are freed.
Note: The DT_shutdown command does not shut down processes that have
been started by custom servers. To shut down these processes, you must
follow the instructions the custom servers provide.
Next step: Now use vaeinit to start up in the usual way, as described in
“Starting WebSphere Voice Response” on page 67.
130 Installation
If you have trouble starting WebSphere Voice Response
If two people try to start WebSphere Voice Response at the same time, one of
them will receive the following message:
WebSphere Voice Response is being started by another user.
Automatic retry will be attempted in 3 minutes...
The startup sequence continues to retry until the first user has completed
startup, or until it times out (after 15 minutes).
If WebSphere Voice Response is abnormally terminated during the startup

sequence, you may receive the same message, even though you are the only
person trying to start WebSphere Voice Response. In this case, the problem is
caused by files that were created during the initialization sequence being left
behind when WebSphere Voice Response was abnormally terminated. You can
clean up these files using the following procedure.
Start
1. Log on as dtuser. If you are already logged on as root, reset the
page 89).
2. Ensuring that no other user is trying to start WebSphere Voice Response
: Search through the process table for a vaeinit process. Type the following
ps -def | grep vaeinit
The system displays a list of all processes with vaeinit in their names.
(This includes the grep vaeinit process itself, which you can ignore.)
3. If there is an entry for vaeinit, search the process table for NODEM. Type
ps -def | grep NODEM
The system displays a list of all processes with NODEM in their names. If
there is a vaeinit entry and a NODEM entry, either WebSphere Voice
Response is already running, or someone else may be trying to start it. Do
not attempt to clean up the files.
4. Cleaning up the files: If there is no entry in the list for the vaeinit process,
or if there is a vaeinit entry but no NODEM, no other user is trying to
start WebSphere Voice Response. Clean up the files. Type the following
/usr/lpp/dirTalk/tools/DTforce.clean
Next step: Now use vaeinit to start up in the usual way, as described in
“Starting WebSphere Voice Response” on page 67.

132 Installation
Appendix A. Removing WebSphere Voice Response
In some circumstances, you may need to remove WebSphere Voice Response
completely from the system. If you do, follow the procedure in this appendix.
Note: If your WebSphere Voice Response system is configured as a single

system image (SSI), you must unconfigure it before you can remove
WebSphere Voice Response. For information on how to remove a client or a
server from a single system image, see the WebSphere Voice Response for AIX:
Start
1. Log on to AIX as root. If you are already logged on as root, reset the
environment by typing the command:
2. Removing the database: Type the following command and press Enter:
cd /usr/lpp/dirTalk/tools
3. Type the following command and press Enter to shutdown WebSphere
Voice Response:
DT_shutdown
4. Type the following command and press Enter to delete the database files:
DTdatabase -d
5. Removing the DB2 instance: Before performing the following steps it is
advisable to create a backup image of your system. You should shutdown
WebSphere Voice Response and use the mksysb command to create the
backup image. See AIX: Installation Guide, for further instructions.
6. Type the following commands, pressing Enter after each one:
su - dtdb23in
db2 force applications all
db2 terminate
db2stop
exit
/opt/IBM/db2/V9.5/instance/db2idrop dtdb23in
leaving a space immediately before dtdb23in.
If DB2 Version 9.5 was installed in a directory other than
/opt/IBM/db2/V9.5, that path should be substituted.
7. Type the following command to remove the dtdb23in user id:
rmuser dtdb23in
8. Type the following command to remove the dtdb23in directory:

rm -rf /home/dtdb23in
9. Removing WebSphere Voice Response: Type the following command
and press Enter:
smitty install_remove
The system displays the Remove Installed Software menu.
10. Press F4 to list the software.
If any of the following filesets are listed, select them:
dirTalk.DT.xxx
devices.iop_rpq.rte
devices.dirTalk.artic960.diag
where xxx represents any characters.
All other WebSphere Voice Response filesets will be automatically
removed.
11. For PREVIEW only? select no.
12. For REMOVE dependent software? select yes.
13. Press Enter.
14. Press Enter again to confirm.
The system removes the software. This can take a few minutes.
15. Review the output.
16. Look for the /home/dirTalk and /var/dirTalk directories. If they contain
any files you want to keep (for example, custom server files or log files),
copy the files to another directory. Remove the dirTalk directories using
the following commands:
cd /home
rm -rf dirTalk
cd /var
rm -rf dirTalk
cd /var/adm/ras
rm -rf dirTalk
17. Removing the DB2 filesets: If you are not using DB2 for any other
products other than WebSphere Voice Response, you should now remove
DB2. If you are using DB2 for other products you must have a licence for
DB2 as the WebSphere Voice Response licence is not valid when the
product has been removed.
To remove DB2, ensure that DB2 is no longer running and if not, type:
/opt/IBM/db2/V9.5/install/db2_deinstall -a
and press Enter. If DB2 version 9.5 was installed in a directory other than
/opt/IBM/db2/V9.5, that path should be substituted.
134 Installation
18. Removing the WebSphere Voice Response AIX account: Make sure that
you do not have any user data that you have created remaining on you
system.
19. Type the following commands and press Enter:
cd /var
find . -user dtuser -type f -exec rm {} \;
find . -user dtuser -type d -exec rm -rf {} \;
cd /tmp
cd /opt
cd /home
rm -rf dtuser
rm -rf dirTalk
If you have set up your own AIX account for WebSphere Voice Response
type your account name in place of dtuser.
20. Type the following commands and press Enter:
rmuser dtuser
rmuser dtdb23in
rm -rf /home/dtdb23in
Next step: Shut down and restart AIX, using the shutdown -Fr command.
Appendix A. Removing WebSphere Voice Response 135

136 Installation
Appendix B. WebSphere Voice Response commands and
utilities
Table 8 lists the commands and utilities you can use to work with WebSphere
Voice Response and the WebSphere Voice Response database. It shows in
which books you can find more information.
Table 8. WebSphere Voice Response commands and utilities
State of Voice More

Response information
Name Purpose Permission system (see Key)
AC Starts the ASCII dtuser running MM

Console (after
prompting for
administrator name
and password)
Debugmon Records voice input dtuser running VP

and output on specific
telephony channels
Drop_DB_Pkgs Removes WebSphere dtuser stopped CF

Voice Response
database packages
from the database
server of a single
system image
dt.log_mgr Merges, condenses, dtuser running MM

groups, and deletes
oamtrace and
errorlog files
dt_setowner Sets and queries the root stopped INS

owner of a DTTA
DT_shutdown Shuts down dtuser running MM

WebSphere Voice
Response

Table 8. WebSphere Voice Response commands and utilities (continued)
State of Voice More

DTalarm Displays or logs a dtuser running MM

WebSphere Voice
Response alarm
message
DTarchives Views or prints dtuser running MM

archived log or report
files
DTcs Adds, lists, or dtuser running MM

removes custom
server
autoexec-override
entries
DTdata Deletes or exports dtuser running MM

data on statistics
database tables
DTdatabase Creates the root stopped INS

WebSphere Voice
Response database
dtexport Exports application dtuser running DMA

objects into
application or partial
export packages
dtimport Imports application or dtuser running DMA

partial export
packages
dtjconf Imports an editable dtuser not applicable DMVJ

configuration file into
the Java and
VoiceXML
configuration
database.
138 Installation
State of Voice More

dtjenv Sets environment dtuser or not applicable DMVJ

variables for Java and root
VoiceXML.
dtjflog Formats Java and dtuser not applicable DMVJ

VoiceXML log files so
they can be read.
dtjplex Performs numerous dtuser running (for DMVJ

utility actions in the most actions)
Java and VoiceXML
environment.
dtjqapps Queries waiting Java dtuser not applicable DMVJ

and VoiceXML
applications.
dtjqhost Queries the local Java dtuser not applicable DMVJ

and VoiceXML host.
dtjqnode Queries the local Java dtuser not applicable DMVJ

and VoiceXML node.
dtjconf script Imports a dtuser not applicable DMVJ

configuration file into
the configuration
database. Whenever
the default.cff file is
modified,
dtjconf script must be
run to make the
changes take effect.
dtjshost Starts (or stops) the dtuser not applicable DMVJ

local Java and
VoiceXML host.
Appendix B. WebSphere Voice Response commands and utilities 139

State of Voice More

dtjstart Starts Node1 in the dtuser running DMVJ

local host and starts
all applications
included in any
groups that are
included in Node1.
dtjstop Quiesces all dtuser running DMVJ

applications and all
nodes on the local
host.
dtjterm Stops immediately all dtuser running DMVJ

applications and all
nodes on the local
host.
dtjver Reports the current dtuser running DMVJ

version of Java and
VoiceXML
environment.
DTlogs Archives, lists, prints, dtuser running MM

or views log files
DTlsapobj Lists information dtuser running MM

about a type of
WebSphere Voice
Response application
object
DTlsvmobj Lists information dtuser running MM

about a type of
WebSphere Voice
Response voice
messaging object
DTmon Displays information dtuser running MM

about system
resources
140 Installation
State of Voice More

DTprompt Imports from, and dtuser running ST

exports to, an AIX file
the ASCII source of a
WebSphere Voice
Response prompt
DTreports Archives, lists, prints, dtuser running MM

or views standard
reports
DTSNMPD_START Starts the WebSphere dtuser running MM

Voice Response SNMP
daemon
DTst Imports from, and dtuser running ST

exports to, an AIX file
the ASCII source of a
WebSphere Voice
Response state table
DTverifydb Verifies the dtuser running MM

WebSphere Voice
Response database
ISDN_MONITOR Displays and decodes dtuser running and PD

frames and messages trunks in
passed between the service
switch and
WebSphere Voice
Response trunks.
print_trace Formats WebSphere dtuser running or PD

Voice Response trace stopped
files
RDSETBUFS Resets the size of the dtuser running or CF

buffer pool stopped

State of Voice More

restoreDT Restores WebSphere root stopped INS

Voice Response data
that was saved using
the saveDT command
run_script Logs on or off a 3270 dtuser running 3270

server
saveDT Saves WebSphere root stopped INS

Voice Response data
ssimkclient Configures a dtuser stopped CF

WebSphere Voice
Response system as a
client node within a
single system image
ssimksvr Configures a dtuser stopped CF

WebSphere Voice
Response system as a
server node within a
single system image
ssirmclient Removes a client node dtuser stopped CF

from a single system
image
ssirmsvr Removes a server dtuser stopped CF

node from a single
system image
ssistatus Displays how the dtuser running or CF

WebSphere Voice stopped
Response system is
configured within a
single system image
vae.setenv Sets WebSphere Voice dtuser or running or INS

Response environment root stopped
variables
142 Installation
State of Voice More

vae.setuser Defines the root stopped INS

WebSphere Voice
Response user ID and
file permissions
vaeinit Starts WebSphere dtuser stopped (but MM

Voice Response if running
already, starts
the graphical
user interface)
vaeinit.nox Starts WebSphere dtuser stopped CF

Voice Response
without XWindows
vxml Allows you to run any user running BE

VoiceXML
applications remotely.
VOIP_MONITOR
Allows you to any user running VP
monitor Voice over
IP/ SIP sequences
wvrapplprof List, add, change, dtuser running. DMA

delete, copy, or view Before you
details of an can use the
application profile. wvrapplprof
command,
you must
import the
admin custom
server and
make sure
that it is
running.

State of Voice More

wvrmailbox List, change, or view dtuser running. DMA

details of mailboxes Before you
associated with an can use the
application profile. wvrmailbox
The application profile command,
must already exist you must
(see wvrapplprof). import the
admin custom
server and
make sure
that it is
running.
wvrstop Stop the WebSphere dtuser running MM

Voice Response
runtime system.
wvrtrunk Enable, disable, or dtuser running MM

query the status of
one or more trunks
and their channels.
Key: DMVJ: Deploying and Managing VoiceXML and Java Applications;CF: Configuring
the System; DMA: Designing and Managing State Table Applications; INS: Installation;
MM: Managing and Monitoring the System; PD: Problem Determination, ST: Application
Development using State Tables; VP: Voice over IP using Session Initiation Protocol
dt_setowner command
Purpose
Registers, removes or queries the owner of a DTTA.
Syntax
For DTTA use either:
dt_setowner -x -s adapter_number -t T1 | E1
or
144 Installation
dt_setowner -x -u adapter_number | -q adapter_number
For DTNA use:
dt_setowner -n -s adapter_number -t T1 | E1
Description
Use the dt_setowner command to register WebSphere Voice Response as the

owner of a DTTA. Other applications can use a DTTA, so if you do not
register WebSphere Voice Response as the owner, WebSphere Voice Response
cannot use that DTTA.
v Before you use the dt_setowner command, you must determine the
identification number of every DTTA you want to use. To do this, see
“Setting ownership of the DTTAs” on page 53.
v Before you can run the dt_setowner command, you must log in as root.
v You must run the dt_setowner command before you start WebSphere Voice
Response for the first time.
v You must run the dt_setowner command for every DTTA you want to use.
Flags
n Specifies the DTNA adapter type.
q Displays the name of the application that has registered ownership of
the DTTA.
s Registers WebSphere Voice Response as the owner of the DTTA.
t Specifies whether the adapter is to be used for E1 or T1 telephony
(DTTA only)
u Unregisters WebSphere Voice Response as the owner of the DTTA.
x Specifies the DTTA adapter type.
adapter_number
The identification number of the adapter. For a DTTA it is the rpqio
number. For more information, see “Setting ownership of the DTTAs”
on page 53. For a DTNA it is the vnaio number. For more information,
refer to the WebSphere Voice Response for AIX: Voice over IP using
Session Initiation Protocol book.
Exit status
0 Successful completion.
>0 An error occurred. Messages show the reason for the error.

146 Installation
Appendix C. WebSphere Voice Response environment
variables
Table 9 describes the WebSphere Voice Response environment variables.
Table 9. WebSphere Voice Response environment variables
Variable Value Description
$CUR_DIR /usr/lpp/dirTalk/db/current_dir Current system data files.
$ARC_DIR /usr/lpp/dirTalk/db/archive_dir This directory contains a copy
of the directories in the
$CUR_DIR directory, and is
used for archiving.
$DEV_DIR /usr/lpp/dirTalk/db/develop_dir This directory contains a copy
$CUR_DIR directory.
$DTJ_DIR /var/dirTalk/DTBE/native/aix This directory contains scripts
and configuration files for the
Java and VoiceXML
environment
$DTJ_HOME /var/dirTalk/DTBE This directory contains all files
relating to Java and VoiceXML
environment.
$DTJ_LOGS /var/dirTalk/DTBE/dtj_logs This directory contains the log
files for the Java and VoiceXML
environment
$TMP_DIR /usr/lpp/dirTalk/db/temporary_dir This directory contains a copy
$CUR_DIR directory, and is
used when exporting and
importing files.
$OAM_LOG_PATH /usr/lpp/dirTalk/db/current_dir/oamlog Error log, statistics, trace.
$VAE /usr/lpp/dirTalk
$VAEBIN /usr/lpp/dirTalk/sw/bin WebSphere Voice Response
binary directory.
$VAETOOLS /usr/lpp/dirTalk/tools This directory contains
utilities, including those
described in Appendix B,
“WebSphere Voice Response
commands and utilities,” on
page 137.
$SYSPARM_DIR /usr/lpp/dirTalk/db/sysparm_dir System parameters. SNMP
files.
$SYS_DIR /usr/lpp/dirTalk/db/sys_dir System directory.

Table 9. WebSphere Voice Response environment variables (continued)
Variable Value Description
CA_THRESHOLD_PERCENTAGE The percentage of the buffer
Range: 20–95 pool that can be used by
custom servers. If this limit is
exceeded, the system returns
CA_ACCESS_NOBUFS. If this
variable is not set, 75 will be
used.
148 Installation
Notices
This information was developed for products and services offered in the
U.S.A.
IBM® may not offer the products, services, or features discussed in this
document in other countries. Consult your local IBM representative for
information on the products and services currently available in your area. Any
reference to an IBM product, program, or service is not intended to state or
imply that only that IBM product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe
any IBM intellectual property right may be used instead. However, it is the
user’s responsibility to evaluate and verify the operation of any non-IBM
product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give
you any license to these patents. You can send license inquiries, in writing, to:
The IBM Director of Licensing, IBM Corporation,

North Castle Drive,
Armonk,
NY 10504-1785,
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the

IBM Intellectual Property Department in your country or send inquiries, in
writing, to:
IBM World Trade Asia Corporation Licensing,

2-31 Roppongi 3-chome Minato-ku,
Tokyo 106,
Japan.
The following paragraph does not apply to the United Kingdom or any
other country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS

PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY

OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow
disclaimer of express or implied warranties in certain transactions, therefore,
this statement may not apply to you.
This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will
be incorporated in new editions of the publication. IBM may make
improvements and/or changes in the product(s) and/or the program(s)
described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those
Web sites. The materials at those Web sites are not part of the materials for
this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the
purpose of enabling: (i) the exchange of information between independently
created programs and other programs (including this one) and (ii) the mutual
use of the information which has been exchanged, should contact: IBM UK
Limited, Department 88013, 4NW, 76/78 Upper Ground, London, SE1 9PZ,
England. Such information may be available, subject to appropriate terms and
conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer
Agreement, IBM International Programming License Agreement, or any
equivalent agreement between us.
Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available
sources. IBM has not tested those products and cannot confirm the accuracy
of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be
addressed to the suppliers of those products.
COPYRIGHT LICENSE: This information contains sample application

programs in source language, which illustrate programming techniques on
various operating platforms. You may copy, modify, and distribute these
sample programs in any form without payment to IBM, for the purposes of
developing, using, marketing or distributing application programs conforming
to the application programming interface for the operating platform for which
the sample programs are written. These examples have not been thoroughly
150 Installation
tested under all conditions. IBM, therefore, cannot guarantee or imply
reliability, serviceability, or function of these programs.
For country-specific notes on the use of WebSphere Voice Response, refer to

the README file located in the directory /usr/lpp/dirTalk/homologation.
The file name is in the format README_homologation.xxxx, where xxxx is
the country/region identifier.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corporation in the United States, other
countries, or both. If these and other IBM trademarked terms are marked on
their first occurrence in this information with a trademark symbol (® or ™),
these symbols indicate U.S. registered or common law trademarks owned by
IBM at the time this information was published. Such trademarks may also be
registered or common law trademarks in other countries. A current list of IBM
trademarks is available on the Web at Copyright and trademark information
(http://www.ibm.com/legal/copytrade.shtml).
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks of Oracle
and/or its affiliates.
Other company, product or service names may be trademarks or service

marks of others.
Notices 151
152 Installation
Glossary
The following terms and abbreviations are defined as they are used in the context of
WebSphere Voice Response. If you do not find the term or abbreviation you are looking for,
see IBM Dictionary of Computing, McGraw-Hill, 1994 or the AIX: Topic Index and Glossary,
SC23–2513.
Special Characters (2) The ISDN protocol that is used

on the 5ESS switch. It provides 23
µ-law The companding algorithm that is
B-channels and a D-channel over a
used primarily in North America
T1 trunk.
and Japan when converting from
analog to digital speech data. 6312 Digital Trunk Telephony Adapter
(Compand is a contraction of (DTTA)
compress and expand.) Contrast See Digital Trunk Telephony Adapter.
with A-law.
6313 Digital Trunk Telephony Adapter
(DTTA) with Blind Swap Cassette (BSC)
Numerics See Digital Trunk Telephony
2 B-channel transfer feature Adapter with Blind Swap Cassette.
See Integrated Services Digital
Network (ISDN) two B-channel A
transfer.
A-law The companding algorithm that is
3270 host application used in Europe, Latin America, and
An application on the IBM other countries when converting
System/370™ System/390®, or from analog to digital speech data.
AS/400® that interacts with (Compand is a contraction of
terminals that support the 3270 data compress and expand.) Contrast
stream. with µ-law.
3270 script language access protocol
See script language. A protocol that is used between an
external subscriber and a switch in a
3270 server
telephone network.
A function of WebSphere Voice
Response that provides a software ACD See automatic call distributor.
interface between WebSphere Voice
ACL See application connectivity link.
Response and IBM System/370,
System/390, or AS/400 architecture action See state table action.
business applications that interact
Action Palette
with terminals that support the 3270
An area that contains folders and
data stream. Contrast with custom
icons that can be selected to create
server.
state table actions.
5ESS (1) A Lucent Technologies switch.

Address Resolution Protocol (ARP) condition), but it is also used to
In HACMP, the Internet refer to green (a red or yellow
communication protocol that message has been cleared) and
dynamically maps Internet white (information) conditions.
addresses to physical (hardware) Contrast with alert.
addresses on local area networks.
alert A message that is sent to a central
Limited to networks that support
monitoring station, as the result of
hardware broadcast.
an alarm. Contrast with alarm.
The usr/sbin/cluster/etc/clinfo.rc
alternate mark inversion (AMI)
script, which is invoked by the
A T1 line coding scheme in which
clinfo daemon whenever a network
binary 1 bits are represented by
or node event occurs, updates the
alternate positive and negative
system ARP cache. This ensures that
pulses and binary 0 bits by spaces
the IP addresses of all cluster nodes
(no pulse). The purpose is to make
are updated after an IP address
the average dc level on the line
takeover. The script can be further
equal to zero.
customized to handle site-specific
needs. AMI See alternate mark inversion.
administrator profile analog
Data that describes a WebSphere Data in the form of continuously
Voice Response user. Information variable signals, such as voice or
that is in an administrator profile light signals.
includes ID, password, language
analog display services interface (ADSI)
preference, and access privileges.
A Bellcore signaling protocol that is
ADSI See analog display services interface. used with existing voice networks.
ADSI supports analog transmission
ADSI telephone
of voice and text-based information
A “smart” telephone that can
between a host or switch, voice mail
interpret and return ADSI data.
system, service bureau, or similar,
advanced intelligent network (AIN) and a subscriber's ADSI-compatible
A telephone network that expands screen telephone. A single
the idea of the intelligent network voice-grade telephony channel is
(IN) to provide special services more shared between voice and data,
efficiently; for example, by giving using a technique by which the
users the ability to program many channel is taken over for the
of the services themselves. transmission of modem-encoded
data.
AIN See advanced intelligent network.
ANI See automatic number identification.
alarm Any condition that WebSphere Voice
Response thinks worthy of annotation
documenting with an error message. In speech recognition, an
Strictly, the term alarm should alphanumeric string that is used to
include only red (immediate mark a grammar when it is defined.
attention) and yellow (problem When the grammar is used in an
154 Installation
application, both the word and the auto-attendant
alphanumeric string are returned to Automated attendant. A voice
the application. application that answers incoming
calls and asks callers which number
announcement-only greeting
or other service they would like.
In voice mail, a greeting that does
not give the caller a chance to leave automatic call distributor (ACD)
a voice message. A telephone system feature that
automatically queues and processes
application
inbound calls according to
A (usually) customer-written
predefined rules. For example, a call
program or set of programs that
might be routed to the agent whose
might consist of one or more state
line has been idle longest.
tables or custom servers that are
running on WebSphere Voice automatic number identification (ANI)
Response, with associated voice A service available in the U.S. that
segments. See voice application. provides the telephone number of
the calling party. It is generated by
application connectivity link (ACL)
the caller's originating central office
A service that transmits out-of-band
switch, sent to a telephone network
information between WebSphere
carrier if required, then sent directly
Voice Response and the Siemens
either to a switch or to a voice
Hicom 300 switch.
processing system.
application profile
autostubbing
Data that describes initial actions
A state table icon view utility that
that are to be performed when the
automatically converts lines into
telephone is answered. Information
stubs when they cross a specified
in an application profile indicates to
number of columns.
the channel process which state
table to load.
B
application server interface (ASI)
B8ZS Bipolar with 8-zero substitution. A
The principal software component
T1 line code that is required for
of WebSphere Voice Response that
64Kb channels such as ISDN.
manages the real-time channel
processing. B-channel
See bearer channel. See also Integrated
application server platform (ASP)
Services Digital Network (ISDN) .
A platform that is used for Web and
voice applications for e-business. background music
Any audio data that is to be played
ASI See application server interface.
on a music channel.
ASP See application server platform.
barge-in
audio name The capability that allows a prompt
The audible name that relates to a to be interrupted by an utterance
specific application profile ID and
mailbox.
Glossary 155
that is then passed to a speech which is used to describe the syntax
recognizer. See also cut-through of a given language and its notation.
channel. In speech recognition, a special
adaptation of grammar
baseforms
representation that is specified by
The set of phonetic pronunciations
Speech Recognition Control Language
that are associated with a grammar.
(SRCL) (pronounced “circle”).
In WebSphere Voice Server, the IBM
dictionary of pronunciations is used. bos Base Operating System.
basic rate interface (BRI) bps bits per second.
The means of ISDN access that is
BRI See basic rate interface.
normally used by private
subscribers. It provides two bridge See DVT bridge.
B-channels of 64 Kb per second and
British Approvals Board for
one D-channel of 16 Kb per second
Telecommunications
for signaling. This is often known as
The British standards organization
2B+D. Contrast with primary rate
that is responsible for approval of
interface (PRI).
equipment that is to be attached to
beans Java beans with which you can the PSTN.
build voice applications to use the
services of WebSphere Voice C
Response on any platform.
cadence
bearer channel The modulated and rhythmic
In an ISDN interface, a duplex recurrence of an audio signal. For
channel for transmitting data or example, a series of beeps or a
digital voice between the terminal series of rings.
and the network. The B-channel
call Telephone call. Often used to mean
operates at 64 Kb per second.
a single run-time instance of a voice
bearer service application.
The type of service that defines how
call center
an ISDN connection will be used.
A central point at which all inbound
Typical bearer services are speech
calls are handled by a group of
telephony, 64 Kb per second data,
individuals in a controlled
and high-quality speech.
sequential way. Call centers are
blind transfer usually a front end to a business
A type of call transfer in which the such as airline ticketing or mail
call is routed to another extension order.
and the original call is ended. No
Call Control eXtensible Markup Language
check is made to determine whether
(CCXML)
the transferred call is answered or if
Language designed to provide
the number is busy. Contrast with
telephony call control support for
screened transfer.
VoiceXML or other dialog systems.
bnf Abbreviation for Backus-Naur Form,
156 Installation
Refer to the CCXML forum web site to another telephone number. See
at http://www.w3.org/TR/ccxml also dual-line call transfer.
call forwarding CAS See channel associated signaling.
The process of sending incoming
cascading resources
calls to a different number.
Resources that can be taken over by
called party more than one node. A takeover
Any person, device, or system that priority is assigned to each
receives a telephone call. Contrast configured cluster resource group in
with caller. a per-node way. In the event of a
takeover, the node with the highest
caller (1) Any person, device, or system
priority gets the resource group. If
that makes a telephone call. (2)
that node is unavailable, the node
Often used to refer to any user of a
with the next-highest priority gets
voice application, although
the resource group, and so on.
WebSphere Voice Response might
have made an outbound call and CAS tone
the user is really the called party. (3) Customer Premise Equipment
In voice mail, any person who Alerting Signal tone. In ADSI, this
makes a telephone call to a tone is sent to the ADSI telephone
subscriber. Contrast with user. to switch the phone to data mode.
calling line identification presentation CBX See computerized branch exchange.
(CLIP) An ISDN supplementary service
CCH See Comité de Coordination de
that advises the called party of the
l'Harmonisation.
caller's number; for example, by
displaying it on a telephone display CCITT
panel. See Comité Consultatif International
Télégraphique et Téléphonique.
CallPath
Software that provides basic CCS See common channel signaling (CCS).
computer-telephony integration
central office (CO)
(CTI) enablement and
A telephone switching system that
comprehensive CTI functionality.
resides in the telephone service
This includes access to, and
provider's network. Different types
management of, inbound and
of central office switches exist,
outbound telecommunications.
depending upon the role of the
call session switch in the telephone network.
The sequence of events that occurs Commonly, a central office switch
from the time a call is started to the connects customer lines to other
time all activities related to customer lines or trunks, and is the
answering and processing the call point at which local subscriber lines
are completed. end for switching to other lines or
trunks.
call transfer
A series of actions that directs a call central registry
A component of the Licence Use
Glossary 157
Management network topology. A WebSphere Voice Response to the
server's database that logs requests switch, channel bank, or channel
for licenses, upgrades for licenses, service unit.
and journals all license activity in a
channel process (CHP)
tamper-proof auditable file.
The AIX process that runs the logic
CEPT See Conference Européenne des of the state table; each active caller
Administrations des Postes et session has one active channel
Télécommunications. process.
CGI See Common Gateway Interface. channel service unit (CSU)
A device that is used to connect a
channel
digital phone line to a multiplexer, a
One of the 24 channels that are on a
channel bank, or directly to another
T1 trunk, or one of the 30 channels
device that generates a digital
that are on an E1 trunk. See also
signal. A CSU performs specific
speech recognition session, music
line-conditioning and equalization
channel.
functions, and responds to loopback
channel-associated signaling (CAS) commands that are sent from the
A method of communicating CO.
telephony supervisory or line
CHP See channel process.
signaling (on-hook and off-hook)
and address signaling on T1 and E1 CIC See circuit identification code.
digital links. The signaling
CICS See customer information control
information for each traffic (voice)
system.
channel is transmitted in a signaling
channel that is permanently circuit identification code (CIC)
associated with the traffic channel. A 12-bit number that identifies a
On T1 links, supervisory signaling trunk and channel on which a call is
is sent in the traffic channel by carried.
using robbed-bit signaling (RBS). On
clear message
E1 links, a separate channel is used
A message that is displayed by
to send signaling. Address signaling
WebSphere Voice Response to tell
can be transmitted either in the
the operator that a red or yellow
signaling channel (out-of-band) or
error message has been cleared.
in the traffic channel (in-band).
Contrast with common channel client node
signaling (CCS). In a single system image (SSI), a
WebSphere Voice Response system
channel bank
that handles interactions with
A device that converts an analog
callers. A client node must have a
line signal to a digital trunk signal.
telephony connection. It does not
channel number store application or voice data; it
The identifying number that is gets data from the server node of
assigned to a licensed channel on the SSI.
the T1 or E1 trunk that connects
158 Installation
CLIP See calling line identification common channel signaling (CCS)
presentation. A method of communicating
telephony information and line
cluster
signaling events (for example, call
Loosely-coupled collection of
setup and call clearing) on a
independent systems (nodes) that
dedicated signaling channel. The
are organized into a network to
signaling channel is either a
share resources and to communicate
predefined channel on an E1 or T1
with each other. HACMP defines
digital link, or a completely separate
relationships among cooperating
link between the switch and
systems where peer cluster nodes
WebSphere Voice Response. For data
provide the services that a cluster
integrity and reliability, the
node offers if that node cannot do
information is usually
so.
communicated using a data link
cluster configuration protocol. The telephone information
User definition of all cluster and line signaling events are sent as
components. Component data packets. SS7 and ISDN are
information is stored in the Object common-channel signaling
Data Manager. Components include protocols. Contrast with channel
cluster name and ID, and associated signaling.
information about member nodes,
Common Gateway Interface (CGI)
adapters, and network modules.
An interface to programs that
CO See central office. provide services on the world wide
Web.
codec Refers to adapters that compress
and decompress video files. The compiled grammar file
letters "codec" represent A grammar in binary format that
"compression/decompression"; in was built by the WebSphere Voice
the past, they represented Server grammar development tools.
"coder/decoder."
compound license
Comité de Coordination de In License Use Management, a type
l'Harmonization of license that allows a system
The CEPT committee responsible for administrator to generate license
standards. passwords for a given number of
licenses. A compound license can
Comitato Elettrotechnico Italiano
generate either nodelocked or
The Italian standards organization
non-nodelocked licenses, but not
responsible for signaling protocols.
both
Comité Consultatif International
computer-telephony integration (CTI)
Télégraphique et Téléphonique (CCITT)
The use of a general-purpose
This organization has been renamed
computer to issue commands to a
and is now known as the
telephone switch to transfer calls
International Telecommunications
and provide other services.
Union - Telecommunication
Typically, CTI is used in call centers.
Standardization Sector (ITU-T).
Glossary 159
computerized branch exchange (CBX) WebSphere Voice Response for
A computer-driven, digital Windows application specifies
communications controller that which context profiles to load into
provides telephone communication the engine it has reserved.
between internal stations and
context type
external networks.
Indicates to the recognition engine
Conférence Européenne des how to interpret the grammar file.
Administrations des Postes et Possible types are: VOCAB_FILE,
Télécommunications (CEPT) GRAMMAR_FILE, TEXT,
European Conference of Postal and MNR_FILE, MNR,
Telecommunications PERSONAL_FILE,
Administrations. PERSONAL_WDS,
BASEFORM_FILE.
configuration file
See parameter file. continuous speech recognition
Recognition of words that are
configuration parameter
spoken in a continuous stream.
A variable that controls the behavior
Unlike isolated or discrete word
of the system or the behavior of all
recognition, users do not have to
applications that are running on the
pause between words.
system. See parameter file, system
parameter. conversation
See speech recognition session.
container window
A window that lists the names of all CPE See customer premises equipment.
existing objects of the same type.
CSU See channel service unit .
context
CTI See computer-telephony integration.
A set of one or more grammars that
is enabled and used during a customer information control system
recognition action. The grammars (CICS)
are specified by a FILELIST file. A licensed program that enables
Parameters that influence the transactions that are entered at
recognition, such as the maximum remote workstations to be processed
initial silence period and the ending concurrently by user-written
silence period, are also defined by application programs. It includes
the context. More than one context facilities for building, using, and
can be enabled for a recognition. maintaining databases.
context name custom server
The name given to a context in a A C language or C++ language
context profile that is used for program that provides data
WebSphere Voice Server. manipulation and local or remote
data stream, database, or other
context profile
services that are additional to those
Describes to the WebSphere Voice
that the state table interface
Server process which contexts
provides. Custom servers provide
should be loaded into an engine. A
an interface between WebSphere
160 Installation
Voice Response and business D-channel backup (DCBU)
applications, functions, or other An ISDN NFAS configuration where
processes to give callers access to two of the T1 facilities have a
business information and voice D-channel, one of which is used for
processing functions such as speech signaling, and the other as a backup
recognition. if the other fails. See also non-facility
associated signaling.
customer premises equipment (CPE)
Telephony equipment that is on the DDI See direct inward dialing.
premises of a business or domestic
DDS See production system.
customer of the telephone company.
An example is a private branch delay start
exchange (PBX). A procedure that is used with some
channel-associated signaling
cut-through channel
protocols to indicate when a switch
A channel of voice data that has
or PABX is ready to accept address
been passed through
signaling. After seizure, the switch
echo-cancellation algorithms. The
sends off-hook until it is ready to
channel provides echo-canceled
accept address signaling, at which
voice data that can then be used by
time it sends on-hook. Contrast with
the engine in a recognition attempt.
immediate start and wink start.
This is similar to barge-in.
delta channel
D In an ISDN interface, the D-channel
or delta channel carries the
daemon
signaling between the terminal and
In the AIX operating system, a
the network. In a basic rate
program that runs unattended to
interface, the D-channel operates at
perform a standard service.
16 Kb per second. In a primary rate
database server node interface, the D-channel operates at
In a single system image (SSI), a 64 Kb per second.
WebSphere Voice Response system
destination point code (DPC)
that contains the WebSphere Voice
A code that identifies the signaling
Response DB2® database. This is
point to which an MTP signal unit
usually the same node as the voice
is to be sent. Unique in a particular
server node.
network.
DBIM The internal database manager of
development system
A WebSphere Voice Response
DBS The database server of WebSphere system that is not used to respond
Voice Response. to, or make, “live” calls; it is used
only to develop and test
DCBU See D-channel backup.
applications. Contrast with
D-channel production system.
See delta channel.
dial To start a telephone call. In
telecommunication, this action is
Glossary 161
performed to make a connection between ISDN subscriber equipment
between a terminal and a and the network. It is carried on the
telecommunication device over a ISDN D-channel. ITU-T
switched line. recommendations Q.920 to Q.940
describe this protocol.
dial by name
To press the keys that are related to Digital Trunk Ethernet Adapter (DTEA)
subscribers' names instead of to A Radysis adapter card that
their telephone numbers or provides the audio streaming (RTP)
extensions. interface between the WebSphere
Voice Response internal H.100 bus
dialed number identification service
and Ethernet for a maximum of 120
(DNIS)
channels using uncompressed
A number that is supplied by the
(G.711) voice, and compressed
public telephone network to identify
G.723.2 and G.729A compressed
a logical called party. For example,
voice.
two toll-free numbers might both be
translated to a single real number. Digital Trunk No Adapter (DTNA)
The DNIS information distinguishes A device driver that supports
which of the two toll-free numbers uncompressed (G.711) voice RTP
was dialed. streaming.
dialog box Digital Trunk Telephony Adapter (DTTA)
A secondary window that presents The IBM Quad Digital Trunk
information or requests data for a Telephony PCI Adapter. In
selected action. WebSphere Voice Response, this
adapter is known as a DTTA. It
dial tone
allows you to connect directly to the
An audible signal (call progress
telephony network from a pSeries
tone) that indicates that a device
computer without the need for an
such as a PABX or central office
external pack.
switch is ready to accept address
information (DTMF or dial pulses). Digital Trunk Telephony Adapter (DTTA)
with Blind Swap Cassette (BSC)
DID See direct inward dialing.
The IBM Quad Digital Trunk
digital signal processing (DSP) Telephony PCI Adapter. In
A set of algorithms and procedures WebSphere Voice Response, this
that processes electronic signals adapter is known as a DTTA. It
after their conversion to digital allows you to connect directly to the
format. Because of the specific telephony network from a pSeries
mathematical models that are computer without the need for an
required to perform this processing, external pack. This DTTA includes a
specialized processors are generally short Blind Swap Cassette (BSC)
used. which is required for installing the
DTTA in machines that use the BSC
Digital Subscriber signaling System
(for example, the pSeries 650–6M2).
Number 1 (DSS1)
A signaling protocol that is used
162 Installation
diphone distribution list
A transitional phase from one sound In voice mail, a list of subscribers to
to the next that is used as a building whom the same message can be
block for speech synthesis. Typically, sent.
between one thousand and two
DMS100
thousand diphones exist in any
(1) A Northern Telecom switch. (2)
national language.
The custom ISDN protocol that is
direct dial in (DDI) run on the DMS100 switch,
See direct inward dialing. providing 23 B-channels and a
D-channel over a T1 trunk.
direct inward dialing (DID)
A service that allows outside parties DNIS See dialed number identification
to call directly to an extension of a service.
PABX. Known in Europe as direct
double-trunking
dial in (DDI).
See trombone.
direct speech recognition
down The condition in which a device is
Identification of words from spoken
unusable as a result of an internal
input that are read directly from the
fault or of an external condition,
telephony channel. Contrast with
such as loss of power.
indirect speech recognition.
downstream physical unit (DSPU)
DirectTalk bean
Any remote physical unit (data link,
One of the beans that is provided
storage, or input/output device)
with WebSphere Voice Response. It
that is attached to a single network
provides access from a voice
host system.
application to simple call control
functions: waiting for a call, making DPC See destination point code.
an outgoing call, handing a call over
drop-in grammar
to another application, and
A set of precompiled grammar rules
returning a call when finished.
that can be used by an
discrete word recognition application-specific grammar to
Identification of spoken words that improve the recognition
are separated by periods of silence, performance.
or input one at a time. Contrast
DSP See digital signal processing.
with continuous speech recognition.
DSPU See downstream physical unit.
disconnect
To hang up or terminate a call. DSS1 See Digital Subscriber signaling
System Number 1.
Distributed Voice Technologies (DVT)
A component of WebSphere Voice DTMF
Response that provides an interface See dual-tone multifrequency.
to allow you to integrate your own
DTEA See Digital Trunk Ethernet Adapter.
voice technology (such as a speech
recognizer) with your WebSphere DTNA
Voice Response system. See Digital Trunk No Adapter.
Glossary 163
DTTA See Digital Trunk Telephony Adapter. DVT service
The combination of a voice
dtuser The name of the AIX account that is
application, a DVT bridge, and a
set up during the installation
voice technology that allows a caller
process for the use of all users of
to interact with your business.
dynamic vocabulary
dual-line call transfer
A vocabulary that is defined while
A call transfer method in which the
an application is running.
primary and secondary lines remain
bridged until a call is completed.
E
(Also known as tromboning: see
trombone). E&M A channel-associated signaling
protocol in which signaling is done
dual-tone multifrequency (DTMF)
using two leads: an M-lead that
The signals are sent when one of the
transmits battery or ground and an
telephone keys is pressed. Each
E-lead that receives open or ground.
signal is composed of two different
tones. E1 A digital trunking facility standard
that is used in Europe and
DVT See Distributed Voice Technologies.
elsewhere. It can transmit and
DVT bridge receive 30 digitized voice or data
The interface between a voice channels. Two additional channels
technology component (such as a are used for synchronization,
speech recognizer) and the DVT framing, and signaling. The
server. A bridge must exist for each transmission rate is 2048 Kb per
technology that you want to second. Contrast with T1.
integrate with DVT.
echo cancelation
DVT_Client2 A filter algorithm that compares a
A WebSphere Voice Response copy of the voice data that is being
custom server that passes sent to a caller, with the voice data
commands and data to DVT_Server. being that is received from the
caller. Any echo of the sent data is
DVT interface
removed before the received data is
sent on, for example, to a speech
programming interface that is used
recognizer.
by a DVT bridge. It enables
integration of voice applications edge See result.
with Distributed Voice Technologies to
EDL See exchange data link.
provide functions such as speech
recognition. emulation
The imitation of all or part of one
DVT_Server
computer system by another, so that
A component of DVT that allocates
the imitating system accepts the
and manages system resources in
same data, runs the same programs,
response to requests from
and gets the same results as the
DVT_Client2.
imitated computer system does.
164 Installation
endpoint standard, agreed in 1993, that
In Voice over Internet Protocol, a place provides a basic range of services
where calls are originated and and supplementary services using
ended. 30 B-channels plus a D-channel over
an E1 trunk.
engine
A speech recognition process that exchange data link
accepts voice data as input and A serial connection that carries
returns the text of what was said as messaging information between
output. It is the process that WebSphere Voice Response and the
performs the recognition. Lucent Technologies 1AESS,
Northern Telecom DMS100, Ericsson
engine type
MD110 switch, or Siemens Hicom
Each engine must be configured
300.
with a specific type. The type is a
textual tag that is associated with a exit A point in a supplied application
specific engine and does not change from which control can be passed to
the operation or functionality of the another custom-written application.
engine. On completion, the custom-written
application passes control back to
error message
the supplied application.
Any message that is displayed by
WebSphere Voice Response in the
F
System Monitor as an alarm and
optionally written to the WebSphere fade in
Voice Response error log, or to the To gradually increase the volume of
AIX error log (as an alert). Strictly, sounds, such as background music.
the term error message should
fade out
include only red (immediate
To gradually decrease the volume of
attention) and yellow (problem
sounds, such as background music.
situation) messages, but it is also
used to refer to green (a red or failover
yellow message has been cleared) A transparent operation that, in the
and white (informational) messages. event of a system failure, switches
responsibility for managing
Ethernet
resources to a redundant or standby
A 10/100 network connection
system. Also known as fallover.
between the VoIP gateway and the
Speech Server that supports VoIP. FDM See Feature Download Management.
ETS European Telecommunications Feature Download Management (FDM)
Standard or European An ADSI protocol that enables
Telecommunication Specification. several alternative key and screen
overlays to be stored in an ADSI
ETSI European Telecommunications
telephone, and to be selected by
Standards Institute.
predetermined events at the
Euro-ISDN telephone.
The common European ISDN
Glossary 165
Federal Communication Commission function
(FCC) The standard body in the United In ADSI, an ADSI instruction or
States that is responsible for group of instructions.
communication.
FXS See Foreign Exchange Subscriber.
field An identifiable area in a window
that is used to enter or display data. G
FILELIST gatekeeper
A WebSphere Voice Server A component of a Voice over Internet
Telephony runtime file that defines Protocol that provides services such
which files to load into a WebSphere as admission to the network and
Voice Server engine. It contains a address translation.
list in the form:
gateway
context type grammar filename A component of Voice over Internet
... ... Protocolthat provides a bridge
between VoIP and circuit-switched
Recursion is not permitted; that is, environments.
no contexts of type FILELIST can be
specified in a FILELIST. When a G.711 Specification for uncompressed
FILELIST is loaded, all the voice for PSTN and Voice over
grammars that are specified in it are Internet Protocol access.
loaded into the engine. From then G.723.1
on, the grammars that are loaded Compressed audio codecs that are
when the FILELIST is specified are used on Voice over Internet Protocol
regarded as a single context. connection for voice.
Foreign Exchange Subscriber (FXS) G.729A
A signaling protocol that links a Compressed audio codecs that are
user's location to a remote exchange used on Voice over Internet Protocol
that would not normally be serving connection for voice.
that user, to provide, for example,
calls to outside the local area at the glare A condition that occurs when both
local rate. ends of a telephone line or trunk are
seized at the same time.
frame A group of data bits that is
surrounded by a beginning grammar
sequence and an ending sequence. A structured collection of words and
phrases that are bound together by
fsg Abbreviation for finite state rules. A grammar defines the set of
grammar. In WebSphere Voice all words, phrases, and sentences
Server, the extension of a file that that might be spoken by a caller
contains grammar specifications in and are recognized by the engine. A
compiled, binary form. It is grammar differs from a vocabulary in
generated from a .bnf file and is that it provides rules that govern
called a .fsg file. the sequence in which words and
phrases can be joined together.
166 Installation
greeting observes the alternate mark inversion
In voice mail, the recording that is (AMI) rule and V represents an AMI
heard by a caller on reaching violation. HDB3 is similar to B8ZS
subscriber's mailbox. See also that is used with T1.
announcement-only greeting. Contrast
HDLC See high-level data link control.
with voice message.
high-level data link control
greeting header
An X.25 protocol.
In voice mail, a recording that is
made by a subscriber and played to homologation
callers either before or instead of a The process of getting a telephony
personal greeting. product approved and certified by a
country's telecommunications
Groupe Special Mobile (GSM)
authority.
A CEPT/CCH standard for mobile
telephony. hook flash
A signal that is sent to a switch to
H request a switch feature (such as call
transfer).
HACMP (High-Availability Cluster
Multi-Processing) for AIX host application
Licensed Program Product (LPP) An application residing on the host
that provides custom software that computer.
recognizes changes in a cluster and
hunt group
coordinates the use of AIX features
A set of telephone lines from which
to create a highly-available
a non-busy line is found to handle,
environment for critical data and
for example, an incoming call.
applications.
HACMP/ES I
Licensed Program Product (LPP)
immediate start
that provides Enhanced Scalability
A procedure that is used with some
to the HACMP for AIX LPP. An
HACMP/ES cluster can include up
protocols, when the address
to 32 nodes.
signaling is sent within 65
hang up milliseconds of going off-hook.
To end a call. See also disconnect. Contrast with delay start and wink
start.
HDB3 High-density bipolar of order 3. An
E1 line coding method in which IN See intelligent network.
each block of four successive zeros
in-band
is replaced by 000V or B00V, so that
In the telephony voice channel,
the number of B pulses between
signals are said to be carried
consecutive V pulses is odd.
in-band. Contrast with out-of-band.
Therefore, successive V pulses are of
alternate polarity so that no dc indirect speech recognition
component is introduced. Note: B Identification of words from spoken
represents an inserted pulse that
Glossary 167
input that are read from a file. specification, and used on Nortel
Contrast with direct speech and Lucent switches.
recognition.
Integrated Services Digital Network user
initialize part (ISUP)
To prepare a system, device, or Part of the SS7 protocol that
program for operation; for example, supports telephony signaling
to initialize a diskette. applications. The ISDN user part is
defined to carry signaling
input parameter
information that relates to digital
Data that is received by a program
telephones, terminals, and PABXs in
such as a prompt, 3270 script,
customer premises.
custom server, or state table from
the program that called it. Contrast intelligent network (IN)
with local variable and system A telephone network that includes
variable. programmable software that is not
resident on the switch. It allows the
integrated messaging
service provider to provide special
A messaging system in which more
services, such as special
than one copy of a single message is
call-handling, that are not
stored, the copies being kept
dependent on the capabilities of the
synchronized by the applications
switch. See also advanced intelligent
that are used to access them.
network.
Contrast with unified messaging.
intelligent peripheral (IP)
Integrated Services Digital Network
A voice processing system (such as
(ISDN)
WebSphere Voice Response) that
A digital end-to-end
provides enhanced services such as
telecommunication network that
voice response, speech recognition,
supports multiple services
text-to-speech, voice messaging, and
including, but not limited to, voice
database access in an advanced
and data.
intelligent network.
interactive voice response (IVR)
(ISDN) call transfer
A computer application that
In WebSphere Voice Response, an
communicates information and
application that allows you to
interacts with the caller via the
transfer calls on Nortel DMS-100
telephone voice channel.
switches using Integrated Services
Digital Network (ISDN) two B-channel International Telecommunications Union –
transfer, and on Nortel DMS-100 and Telecommunication Standardization Sector
DMS-250 switches using Nortel's (ITU-T)
proprietary Release Link Trunk The name of the organization that
(RLT) call transfer protocol. was previously known as the
CCITT.
(ISDN) two B-channel transfer IP See intelligent peripheral.
A call transfer feature that is
defined by Bellcore GR-2865-CORE
168 Installation
ISDN See Integrated Services Digital L
Network (ISDN) .
LAN See local area network.
ISDN two B-channel transfer
language model
See Integrated Services Digital
For speech recognition, a set of
Network (ISDN) two B-channel
acoustic shapes (in binary format)
transfer.
for a given set of words, in which
ISDN-UP word-to-word differences are
See Integrated Services Digital maximized, but speaker-to-speaker
Network user part. differences are minimized. See also
vocabulary.
ISUP See Integrated Services Digital
Network user part. LAPD See link access protocol for the
D-channel.
ITU-T See International Telecommunications
Union – Telecommunication licensed program product (LPP)
Standardization Sector. A separately-priced program and its
associated materials that bear an
IVR See interactive voice response.
IBM copyright and are offered
under the terms and conditions of a
J
licensing agreement.
Java Bean
license server
A reusable Java component. See
A machine on a network that holds
beans.
licenses and distributes them on
jump out request to other machines on the
See call transfer. network.
line error
K
An error on the telephone line that
key (1) One of the pushbuttons on the causes the signal to be impaired.
telephone handset; sometimes
link access protocol for the D-channel
referred to as a DTMF key. (2) A
An HDLC protocol used in ISDN
component of the keyboard that is
that ensures a reliable connection
attached to the computer system.
between the network and the user.
key pad Often used as another name for
The part of the telephone that Q.921.
contains the pushbutton keys.
local area network (LAN)
key pad mapping A network in which computers are
The process of assigning special connected to one another in a
alphanumeric characters to the keys limited geographical area.
that are on a telephone key pad, so WebSphere Voice Response
that the telephone can be used as a communication with WebSphere
computer-terminal keyboard. Voice Server speech recognition,
text-to-speech, and single system
image (SSI) requires a LAN that is
dedicated to that purpose (unless
Glossary 169
both are installed on the same message waiting indicator (MWI)
system). A token-ring network is a A visible or audible indication (such
type of LAN. as a light or a stutter tone) that a
voice message is waiting to be
local variable
retrieved.
A user-defined temporary variable
that can be accessed only by the MFR1 An in-band address signaling
program (state table, prompt, or system that uses six tone
3270 script) for which it is defined. frequencies, two at a time. MFR1 is
Contrast with input parameter, system used principally in North America
variable. and is described in ITU-T
recommendations Q.310 through
M Q.332.
macro See system prompt. MIME See multipurpose Internet mail
extensions.
MAP See mobile application part.
mobile application part (MAP)
MB See megabyte.
Optional layer 7 application for SS7
megabyte that runs on top of TCAP for use
(1) For processor storage and real with mobile network applications.
and virtual memory, 1 048 576
MP See multiprocessor.
bytes. (2) For disk storage capacity
and transmission rates, 1 000 000 MSU See message signal unit.
bytes.
MTP See message transfer part.
Message Center
mu(µ)-law
See Unified Messaging
The companding algorithm that is
message delivery preference used primarily in North America
The subscriber's choice of whether and Japan when converting from
voice mail is stored as voice mail analog to digital speech data.
only, as e-mail only, or as both voice (Compand is a contraction of
mail and e-mail. compress and expand.) Contrast
with A-law.
message delivery type
The format in which a voice multiprocessor (MP)
message is delivered. A computer that includes two or
more processing units that can
message signal unit (MSU)
access a common main storage.
An MTP packet that contains data.
multipurpose Internet mail extensions
message transfer part (MTP)
(MIME)
Part of the SS7 protocol that is
A protocol that is used on Internet
normally used to provide a
for extending e-mail capability and
connectionless service that is
merging it with other forms of
roughly similar to levels one
communication, such as voice mail
through three of the OSI reference
and fax.
model.
170 Installation
mumble Network File System (NFS)
Non speech noise that a user A protocol, developed by Sun
interjects while speaking. Microsystems, Incorporated, that
allows any host in a network to
music channel
gain access to another host or
A channel on which sounds can be
netgroup and their file directories.
broadcast to one or more telephony
In a single system image (SSI), NFS
(voice) channels.
is used to attach the WebSphere
music title Voice Response DB2 database.
The name by which WebSphere
network termination
Voice Response knows a tune.
See NT mode.
MWI See message waiting indicator.
NFAS See non-facility associated signaling.
N NFS See Network File System.
National ISDN node In a single system image (SSI), one
A common ISDN standard that was of the WebSphere Voice Response
developed for use in the U.S. systems that are in the cluster.
NAU See network addressable unit. non-facility associated signaling (NFAS)
An ISDN configuration where
N-Best
several T1 facilities can be
The ability to return more than one
controlled by a single D-channel,
speech recognition result. Typically,
instead of the normal T1
an array of results is available in the
configuration where each T1 facility
application in sequence of
has 23 B-channels and a D-channel
descending probability.
(23B+D). With NFAS, all 24
NCP See network control program. timeslots of the non signaling trunks
are available for voice, whereas only
NET Norme Européenne de
23 channels can be used on the
Télécommunication.
trunk that carries signaling traffic
Net 5 The test specification for (23B+D+n24B).
conformance to the Euro-ISDN
NT mode
standard for primary rate access to
Attachment to the ISDN network is
ISDN.
asymmetric. The network side of the
network addressable unit (NAU) connection operates in network
Any network component that can be termination, or NT, mode. User
addressed separately by other equipment operates in terminal
members of the network. equipment, or TE, mode.
network control program (NCP)
O
Used for requests and responses
that are exchanged between physical ODM See Object Data Manager.
units in a network for data flow
Object Data Manager (ODM)
control.
A data manager intended for the
storage of system data. The ODM is
Glossary 171
used for many system management (ISO) in 1984, it is considered to be
functions. Information that is used the primary architectural model for
in many commands and SMIT intercomputer communications
functions is stored and maintained
originating point code (OPC)
in the ODM as objects with
A code that identifies the signaling
associated characteristics.
Point that originated an MTP signal
off-hook unit. Unique in a particular
A telephone line state, usually network.
induced by lifting a receiver, in
OSI See Open Systems Interconnection.
which the line is ready to make a
call. outgoing mail
In voice mail, messages that are sent
offline
by a subscriber to another
Not attached or known to the
subscriber on the same system, and
existing system configuration, and
have not yet been listened to by the
therefore not in active operation.
addressee.
on-hook
out-of-band
A telephone line state, usually
In the telephony signaling channel,
induced by hanging up a receiver,
as opposed to the voice channel.
in which the line is ready to receive
Signals are said to be carried
a call.
out-of-band. Contrast with in-band.
online In active operation.
P
OPC See originating point code.
PABX See private automatic branch exchange
Open Systems Interconnection (OSI)
.
(1.) The interconnection of open
systems as specified in particular pack Each DTTA contains the equivalent
ISO standards. (2.) The use of of four packs. The pack is a digital
standardized procedures to enable trunk processor built into the digital
the interconnection of data trunk adapter, so there is no need
processing systems. for external hardware. See also
TPACK.
Open Systems Interconnection (OSI)
architecture parameter file
Network architecture that observes An ASCII file that sets configuration
the particular set of ISO standards parameters.
that relate to Open Systems
password
Interconnection.
A unique string of characters that is
Open Systems Interconnection (OSI) known to a computer system and to
Reference Model a user. The user must specify the
A conceptual model composed of character string to gain access to the
seven layers, each specifying system and to the information that
particular network functions. is stored in it.
Developed by the International
PBX See private branch exchange.
Organization for Standardization
172 Installation
PCI See peripheral component interconnect. normally used by large sites. It
provides 30 (E1) or 23 (T1)
PCM See Pulse Code Modulation.
B-channels of 64 Kb per second and
PCM fault condition one D-channel for signaling. This is
A fault, such as power supply often known as 30B+D or 23B+D.
failure, or loss of incoming signal, in Contrast with basic rate interface.
T1 or E1 equipment. (ITU-T G.732
primary rate ISDN (PRI)
and G.733.)
See primary rate interface.
peripheral component interconnect (PCI)
primitive
A computer busing architecture that
A message that is sent from one
defines electrical and physical
process to another.
standards for electronic
interconnection. private automatic branch exchange (PABX)
An automatic private switching
personal greeting
system that services an organization
In voice mail, a greeting that is
and is usually located on a
recorded by a subscriber. Contrast
customer's premises. Often used as
with system greeting.
another name for private branch
phone recognition exchange (PBX) .
Communicating with a computer
private branch exchange (PBX)
using voice via a telephone, over a
A switch inside a private business
telephone line. The computer
that concentrates the number of
application recognizes what was
inside lines into a smaller number
said and takes suitable action.
of outside lines (trunks). Many PBXs
port In time-slot management, one end also provide advanced voice and
of a 64 Kbps unidirectional stream data communication features. Often
that can be attached to the TDM used as another name for private
bus. automatic branch exchange .
port set process a call
In time-slot management, a To answer the telephone and
collection of ports that can be perform the correct tasks.
connected using a single
Process Manager
CA_TDM_Connect() API call to a
In WebSphere Voice Server, the
complementary collection of ports.
process that manages the interaction
PRA Primary rate access (PRA). Used as of all telephony system processes;
another name for primary rate for example, starting and stopping
interface (PRI). text-to-speech or speech recognition
sessions.
PRI See primary rate interface.
production system
primary rate access (PRA)
See primary rate interface.
system that responds to or makes
primary rate interface (PRI) “live” calls. A production system
The means of ISDN access that is can also be used to develop new
Glossary 173
applications. Contrast with pronunciation pool
development system. A WebSphere Voice Server resource
that contains the set of all
program temporary fix (PTF)
pronunciations.
An update to IBM software.
protocol
program data
A set of semantic and syntactic rules
Application-specific data that can be
that determines the behavior of
associated with a call transfer from
functional units when they get
CallPath to WebSphere Voice
communication. Examples of
Response, or in the opposite
direction. This is equivalent to
protocols are FXS, RE, and R2.
CallPath program data, but
WebSphere Voice Response imposes PSTN An ITU-T abbreviation for public
the restriction that the data must be switched telephone network.
a printable ASCII character string,
PTF See program temporary fix.
with a maximum length of 512
bytes. Pulse Code Modulation (PCM)
Variation of a digital signal to
prompt
represent information.
(1) A message that requests input or
provides information. Prompts are pushbutton
seen on the computer display screen (1) A key that is on a telephone key
and heard over the telephone. (2) In pad. (2) A component in a window
WebSphere Voice Response, a that allows the user to start a
program that uses logic to specific action.
determine dynamically the voice
pushbutton telephone
segments that are to be played as a
A type of telephone that has
voice prompt.
pushbuttons. It might or might not
prompt directory send tone signals. If it does, each
A list of all the prompts that are number and symbol on the key pad
used in a particular voice has its own specific tone.
application. Used by the state table
to play the requested voice prompts. Q
pronunciation Q.921 The ITU-T (formerly CCITT)
The possible phonetic recommendation that defines the
representations of a word. A word link layer of the DSS1 protocol.
can have multiple pronunciations; Q.921 defines an HDLC protocol
for example, “the” has at least two that ensures a reliable connection
pronunciations, “thee” and “thuh”. between the network and the user.
Often used as another name for
pronunciation dictionary
LAPD.
A file that contains the phonetic
representation of all of the words, Q.931 The ITU-T recommendation that
phrases, and sentences for an defines the network layer of the
application grammar. DSS1 protocol. This layer carries the
174 Installation
ISDN messages that control the remote alarm indication (RAI)
making and clearing of calls. A remote alarm (also referred to as
a yellow alarm) indicates that the
quiesce
far-end of a T1 connection has lost
To shut down a channel, a trunk
frame synchronization. The Send
line, or the whole system after
RAI system parameter can be set to
allowing normal completion of any
prevent WebSphere Voice Response
active operations. The shutdown is
from sending RAI.
performed channel-by-channel.
Channels that are in an idle state remote extension (RE)
are shut down immediately. An E1 signaling protocol that is
Channels that are processing calls similar to FXS loop start.
are shut down at call completion.
resource element
A component of an Intelligent
R Network. The resource element
RAI See remote alarm indication. contains specialized resources such
as speech recognizers or
RBS See robbed-bit signaling.
text-to-speech converters.
RE See remote extension.
response
Recognition Engine server In speech recognition, the character
In WebSphere Voice Server, the string that is returned by the
software that performs the speech recognizer, through DVT_Client, to
recognition and sends the results to the state table. The string represents
the client. This consists of one ‘Tsm the result of a recognition attempt.
router' and at least one ‘tsmp' and This is the word or words that the
one ‘engine'. recognizer considers to be the best
match with the speech input.
reduced instruction set computer (RISC)
A computer that uses a small, result An indicator of the success or
simplified set of frequently-used failure of a state table action. It is
instructions to improve processing returned by WebSphere Voice
speed. Response to the state table. Also
known as an edge.
referral number
The phone number to which calls result state
are routed, when call forwarding is The state that follows each of the
active. possible results of an action.
rejection return code
The identification of an utterance as A code that indicates the status of
one that is not allowed by a an application action when it
grammar. completes.
release link trunk (RLT) RISC See reduced instruction set computer.
A custom specification from Nortel
RLT See release link trunk.
for ISDN call transfer.
Glossary 175
robbed-bit signaling (RBS) segment ID number
The T1 channel -associated signaling One or more numbers that are used
scheme that uses the least to identify a voice or prompt
significant bit (bit 8) of each segment.
information channel byte for
Server Display Control (SDC)
signaling every sixth frame. This is
An ADSI control mode in which the
known as 7-5/6-bit coding rather
ADSI telephone is controlled
than 8-bit coding. The signaling bit
through a dialog with a voice
in each channel is associated only
response system.
with the channel in which it is
contained. server node
In a single system image (SSI), a
S WebSphere Voice Response system
that contains either the WebSphere
SAP See service access point.
Voice Response DB2 database, or the
SAS A T1 signaling protocol that is voice data, or both.
similar to FXS.
service access point (SAP)
SCbus See Signal Computing bus. An OSI term for the port through
which a service user (layer N+1)
SCCP See signaling connection control part.
accesses the services of a service
SCP See service control point. provider (layer N).
screened transfer service control point (SCP)
A type of call transfer in which the A component of the intelligent
transfer of the held party to the network that provides transactional
third party is completed only if the services, such as translation of
third party answers the call. toll-free numbers to subscriber
Contrast with blind transfer. numbers.
script The logical flow of actions for a service information octet (SIO)
3270 server program. A field that is in an MTP message
signal unit. It identifies a higher
script language
layer user of MTP, and whether the
A high-level, application-specific
message relates to a national or
scripting language, which consists
international network.
of statements that are used to
develop 3270 scripts. These scripts service node
are part of the interface between a An element of an Intelligent
state table and a 3270-based host Network. The service node contains
business application. the service logic that controls an
intelligent network application and
SCSA See Signal Computing System
resources.
Architecture.
service provider
SDC See Server Display Control.
Any company that provides services
SDLC See Synchronous Data Link Control. for a fee to its customers, such as
telecommunication companies,
176 Installation
application service providers, signaling
enterprise IT, and Internet service The exchange of control information
providers. between functional parts of the
system in a telecommunications
service provider equipment (SPE)
network.
The switching equipment that is
owned by the telephone company. signaling connection control part (SCCP)
A layer 3 protocol that observes
session
OSI.
See speech recognition session.
signaling information field (SIF)
Session Initiation Protocol
The user data portion of an MTP
A signaling protocol used for
message signal unit.
internet conferencing, telephony,
presence, events notification and signaling link code (SLC)
instant messaging. A code that identifies a particular
signaling link that connects the
short message service center (SMSC)
destination and originating
A component of the mobile
signaling points. This is used in
telephony network, specified by the
MTP signaling network
GSM group of standards, that
management messages to indicate
provides for exchange of
the signaling link to which the
alphanumeric messages of less than
message relates.
160 bytes. Messages can be
exchanged between different types signaling link selection (SLS)
of system such as mobile telephone, A field that is used to distribute
alphanumeric pager, terminal, MTP signal units across multiple
e-mail, telex, or DTMF telephone. signaling links.
SIF See signaling information field. signaling mode
The type of signaling protocol,
Signal Computing System Architecture
either channel-associated signaling,
(SCSA)
or common-channel signaling.
An architecture that was defined by
Dialogic to support interoperability signaling point
of software and hardware A node in a signaling network that
components that are developed by either originates and receives
different vendors in the computer signaling messages, or transfers
telephony industry. signaling messages from one
signaling link to another, or both.
Signal Computing bus (SCbus)
A time division multiplexed (TDM) signaling process
hardware bus that was originated A WebSphere Voice Response
by Dialogic to interconnect different component that controls signaling
vendors' computer telephony for an exchange data link or
adapters. Specified as part of Signal common-channel signaling protocol.
Computing System Architecture Some signaling processes are
(SCSA).
Glossary 177
supplied with WebSphere Voice network. Each system (known as a
Response, and others can be node) in the cluster is configured as
custom-written. either a client or a server. A single
system image typically consists of
signaling System Number 7 (SS7)
one server node and multiple client
The international high-speed
nodes. The client nodes retrieve
signaling backbone used for the
applications and voice data from the
public-switched telephone network.
server. A second server can be
silence configured for redundancy.
A short pause between utterances.
sink A port that takes voice data from
simple mail transfer protocol (SMTP) the TDM bus. Contrast with source.
An Ethernet protocol that is related
SIO See service information octet.
to TCP/IP.
SIP See Session Initiation Protocol.
simple network management protocol
(SNMP) SLC See signaling link code.
In the Internet suite of protocols, a
SLS See signaling link selection.
network management protocol that
is used to monitor routers and SMDI See Simplified Message Desk Interface.
attached networks. SNMP is an
SMIT See System Management Interface Tool.
application layer protocol.
Information on devices managed is SMP See symmetric multiprocessor.
defined and stored in the
SMSC See short message service center.
application's Management
Information Base (MIB). SNMP SMSI See Simplified Message Service
provides a means of monitoring Interface.
SMTP See simple mail transfer protocol.
resources remotely.
SNA Systems Network Architecture.
Simplified Message Desk Interface
(SMDI) SNMP
A Northern Telecom service that See simple network management
transmits out-of-band information protocol .
between WebSphere Voice Response
source A port that puts voice data on to the
and particular switches.
TDM bus. Contrast with sink.
Simplified Message Service Interface
SPACK
(SMSI)
A logical component that consists of
A Lucent Technologies service that
a base card, which connects to the
transmits out-of-band information
digital trunk adapter in the pSeries
between WebSphere Voice Response
computer, and a trunk interface card
and particular switches.
(TIC), which manages the trunk
single system image (SSI) connection to the switch. Contrast
A cluster of WebSphere Voice with VPACK and TPACK.
Response systems that are
SPE See service provider equipment.
connected together using a local area
178 Installation
speaker-dependent speech recognition SRCL See Speech Recognition Control
Identification of spoken words that Language (SRCL).
is related to knowledge of the
SS7 See signaling System Number 7.
speech characteristics of one
speaker. Contrast with SSI See single system image.
speaker-independent speech recognition.
SSI-compliant custom server
speaker-independent speech recognition A custom server that runs correctly
Identification of spoken words that in a single system image. The
is related to collected knowledge of custom server observes all the
the speech characteristics of a guidelines for the operation of
population of speakers. Contrast custom servers in an SSI
with speaker-dependent speech environment.
recognition.
SSI-tolerant custom server
special character A custom server that runs in a
A character that is not alphabetic, single system image, but with only
numeric, or blank. For example, a some restrictions.
comma (,) or an asterisk (*).
standalone system
speech recognition A WebSphere Voice Response
The process of identifying spoken system that is not part of a single
words. See discrete word recognition, system image (SSI). A standalone
continuous speech recognition, system is not connected to other
speaker-dependent speech recognition, WebSphere Voice Response systems,
speaker-independent speech recognition. so it contains its own application
and voice data.
Speech Recognition Control Language
(SRCL) state One step in the logical sequence of
In WebSphere Voice Server, a actions that makes a WebSphere
structured syntax and notation that Voice Response voice application.
defines speech grammars,
state table
annotations, repetitions, words,
A list of all the actions that are used
phrases, and associated rules.
in a particular voice application. A
speech recognition session component of WebSphere Voice
In WebSphere Voice Server, a Response.
sequence of recognition commands
state table action
that allocate a recognition engine,
One instruction in a set of
and return a unique identifier to
instructions that is in a WebSphere
identify the engine.
Voice Response state table that
speech synthesis controls how WebSphere Voice
The creation of an approximation to Response processes various
human speech by a computer that operations such as playing voice
concatenates basic speech parts prompts or recording voice
together. See also text-to-speech. messages. See also state.
Glossary 179
stub A line in a state table that is only manages the WebSphere Voice
partially displayed. Response system by adding users,
assigning account numbers, and
subscriber
changing authorizations.
In voice mail, any person who owns
a mailbox. system greeting
In voice mail, a default greeting that
subscriber class
is heard by callers to the mailboxes
A named set of variables that
of subscribers who have not
defines a specific level of service
recorded a personal greeting or who
available to telephone subscribers,
have selected the system greeting.
such as maximum number of
Contrast with personal greeting.
messages per mailbox and
maximum number of members per System Management Interface Tool
mailbox distribution list. (SMIT)
A set of utilities that can be used for
subvocabulary
various purposes, such as loading
A vocabulary that is called by
another vocabulary.
software, installing the exchange
supplementary service data link, and configuring SNA.
In Euro-ISDN, a service outside the
Systems Network Architecture (SNA)
minimum service offering that each
An architecture that describes the
signatory is obliged to provide. For
logical structure, formats, protocols,
example, calling line identification
and operational sequences for
presentation (CLIP) and call session.
transmitting information units
switch A generic term that describes a through the networks and also the
telecommunications system that operational sequences for
provides connections between controlling the configuration and
telephone lines and trunks. operation of networks.
symmetric multiprocessor (SMP) system parameter
A system in which A variable that controls some of the
functionally-identical multiple behavior of WebSphere Voice
processors are used in parallel, Response or applications that are
providing simple and efficient running under WebSphere Voice
load-balancing. Response. System parameters are set
through System Configuration or
Synchronous Data Link Control (SDLC)
Pack Configuration options on the
A discipline for managing
Configuration menu. Some system
synchronous, code-transparent,
parameter values are assigned to
serial-by-bit information transfer
system variables when an application
over a link connection. Transmission
is initialized. Contrast with input
exchanges can be duplex or
parameter, local variable, system
half-duplex over switched or
variable.
nonswitched links.
system prompt
system administrator
The symbol that appears at the
The person who controls and
180 Installation
command line of an operating TCAP See transaction capabilities application
system, indicating that the operating part.
system is ready for the user to enter
TCP/IP
a command.
See Transmission Control
system variable Protocol/Internet Protocol.
A permanent global variable that is
TDD See Telecommunications Device for the
defined by WebSphere Voice
Deaf.
Response for use by state tables.
Many system variables are loaded TDM See time-division multiplex bus.
with values when the state table is
technology
initialized. Some values are taken
A program, external to WebSphere
from system parameters. Contrast
Voice Response, that provides
with input parameter, local variable,
processing for functions such as
system parameter.
text-to-speech or speech recognition.
T Telecommunications Device for the Deaf
(TDD) A telephony device that has a
T1 A digital trunking facility standard
QWERTY keyboard and a small
that is used in the United States and
display and, optionally, a printer.
elsewhere. It can transmit and
receive 24 digitized voice or data telephone input field
channels. Signaling can be A field type that contains
imbedded in the voice channel information that is entered by a
transmission when robbed-bit caller who is using pushbutton
signaling is used. The transmission signals. See also field.
rate is 1544 kilobits per second.
terminal
Contrast with E1.
(1) A point in a system or
T1/D3 A framing format that is used in T1 communication network at which
transmission. data can enter or leave. (2) In data
communication, a device, usually
T1/D4 A framing format that is used in T1
equipped with a keyboard and
transmission.
display device, that can send and
tag A text string that is attached to any receive information.
instance of a word in a grammar. A
termination character
tag can be used (1) to distinguish
A character that defines the end of a
two occurrences of the same word
telephone data entry.
in a grammar or (2) to identify more
than one word in a grammar as text-to-speech (TTS)
having the same meaning. The process by which ASCII text
data is converted into synthesized
Tag Image File Format-Fax (TIFF-F)
speech. See also speech synthesis.
A graphic file format that is used to
store and exchange scanned fax TIC See trunk interface card.
images.
time-division multiplex bus (TDM)
A method of transmitting many
Glossary 181
channels of data over a smaller DTTA digital trunk adapter
number of physical connections by provides up to four TPACKs on a
multiplexing the data into timeslots, PCI card.
and demultiplexing at the receiving
transaction
end. In this document, one such
A specific, related set of tasks in an
channel can be considered to be a
application that retrieve information
half-duplex unidirectional stream of
from a file or database. For
64 Kb per second.
example, a request for the account
TIFF-F balance or the available credit limit.
See Tag Image File Format-Fax
transaction capabilities application part
timeslot (TCAP)
The smallest switchable data unit on Part of the SS7 protocol that
a data bus. It consists of eight provides transactions in the
consecutive bits of data. One signaling network. A typical use of
timeslot is similar to a data path TCAP is to verify a card number, for
with a bandwidth of 64 Kb per the credit card calling service.
second.
transaction messaging
token A particular message or bit pattern The ability to associate an item of
that indicates permission or data, such as a transaction identifier,
temporary control to transmit. with a voice message. The voice
message can later be retrieved by
token-ring network
referencing the data value.
A local area network that connects
devices in a ring topology and transfer
allows unidirectional data See call transfer.
transmission between devices by a
Transmission Control Protocol/Internet
token-passing procedure. A device
Protocol (TCP/IP)
must receive a token before it can
A communication subsystem that is
transmit data.
used to create local area and wide
tone An audible signal that is sent across area networks.
a telephone network. Single
trombone
(one-frequency) tones, tritones (three
A connected voice path that enters
sequential tones at different
an IVR from a switch on one circuit,
frequencies), dual tones (two
then returns to the same switch on a
simultaneous tones at different
parallel circuit. Two IVR ports and
frequencies), and dual sequential
two circuits are consumed, but in
tones exist. Each has a different
some circumstances this might be
meaning.
the only way to make a connection
TPACK between two callers if the attached
A digital trunk processor that is switch does not support a Call
implemented using DSP technology Transfer function. Also known as
on the digital trunk adapter without double-trunking.
the need for external hardware. One
trunk A telephone connection between
182 Installation
two central offices or switching Unified Messaging
devices. In WebSphere Voice An IBM product that uses
Response, a trunk refers to 24 or 30 WebSphere Voice Response's voice
channels that are carried on the processing capabilities to provide a
same T1 or E1 digital interface. wide range of voice mail, fax, and
e-mail functions. Previously known
trunk interface card (TIC)
as Message Center.
The component of the pack that
manages the trunk connection to the user Someone who uses WebSphere
switch. Voice Response as a system
administrator, application developer,
Tsm Router
or similar. Contrast with caller.
In WebSphere Voice Server, a
process that controls which engine utterance
processes are in use at any time. A spoken word, phrase, or sentence
Requests for an engine by a that can be preceded and followed
WebSphere Voice Server Client are by silence.
accepted or rejected depending on
whether an engine that meets the V
Tsm Client's requirements is
variable
available.
A system or user-defined element
tsmp In WebSphere Voice Server, a that contains data values that are
process that is running on the used by WebSphere Voice Response
Recognition engine server machine voice applications. See input
that passes messages between an parameter, local variable, system
engine and a Tsm Client. One tsmp parameter, system variable.
exists for every engine.
VMS See Voice Message Service.
TTS See text-to-speech.
vocabulary
tune A piece of music or other audio A list of words with which
data that is intended to be played as WebSphere Voice Response matches
background music. input that is spoken by a caller. See
also language model.
U
voice application
underrun A WebSphere Voice Response
To run out of audio data to play, application that answers or makes
causing voice or music to be calls, plays recorded voice segments
audibly broken up or cut off. to callers, and responds to the
caller's input.
unified messaging
A messaging system in which a voice directory
single copy of a message is stored A list of voice segments that is
and accessed by multiple identified by a group ID. Voice
applications (for example, voice directories can be referenced by
mail and e-mail). Contrast with prompts and state tables. Contrast
integrated messaging. with voice table.
Glossary 183
voice mail voice technology. The library uses
The capability to record, play back, entry points that are provided by
distribute, and route voice DVT.
messages.
Voice Protocol for Internet Messaging
voice mailbox (VPIM)
The notional hard disk space where The standard for digital exchange of
the incoming messages for a voice voice messages between different
mail subscriber are stored. voice mail systems, as defined in
Internet Request For Comments
voice message
(RFC) 1911.
In voice mail, a recording that is
made by a caller for later retrieval voice response unit (VRU)
by a subscriber. A telephony device that uses
prerecorded voice responses to
Voice Message Service (VMS)
provide information in response to
An Ericsson service that transmits
DTMF or voice input from a
information between WebSphere
telephone caller.
Voice Response and particular
switches. voice segment
The spoken words or sounds that
voice messaging
make recorded voice prompts. Each
The capability to record, play back,
segment in an application is
distribute, route, and manage voice
identified by a group ID and a
recordings of telephone calls
segment ID and usually includes
through the use of a processor,
text.
without the intervention of agents
other than the callers and those who voice server node
receive messages. In a single system image (SSI), a
server node that contains the voice
voice model
data. This is usually the same node
A file that contains parameters that
as the database server node.
describe the sounds of the language
that are to be recognized on behalf voice table
of an application. In WebSphere A grouping of voice segments that is
Voice Server, this is a bnf file. See used for organizational purposes.
also grammar. Voice tables can be referenced by
prompts, but not by state tables.
Voice over Internet Protocol (VoIP)
Contrast with voice directory.
The sending of telephony voice over
Internet Protocol (IP) data voice technology
connections instead of over existing See technology.
dedicated voice networks, switching
VoiceXML
and transmission equipment. See
VoiceXtensible Markup Language.
also gatekeeper and gateway.
An XML-based markup language
voice port library for creating distributed voice
A library that manages a socket applications. Refer to the VoiceXML
connection from the client to the forum web site at www.voicexml.org
184 Installation
VoIP See Voice over Internet Protocol. information. Contrast with delay
start and immediate start.
VPACK
A component consisting of a base word spotting
card, which connects to the digital In speech recognition, the ability to
trunk adapter in the pSeries recognize a single word in a stream
computer, and a trunk interface card of words.
(TIC), which manages the trunk
wrap In ADSI, the concatenation of two
connection to the switch. The single
columns of display data to form a
digital trunk processor contains one
single column.
VPACK, and the multiple digital
trunk processor contains slots for up
Y
to five VPACKs. Contrast with
SPACK and TPACK. yellow alarm
See remote alarm indication.
VPIM See Voice Protocol for Internet
Messaging.
Z
VRU See voice response unit.
zero code suppression (ZCS)
A coding method that is used with
W
alternate mark inversion to prevent
World Wide Web Consortium (W3C) sending eight successive zeros. If
An organization that develops eight successive zeros occur, the
interoperable technologies second-least significant bit (bit 7,
(specifications, guidelines, software, with the bits labeled 1 through 8
and tools) to lead the Web to its full from the most significant to the least
potential. W3C is a forum for significant) is changed from a 0 to a
information, commerce, 1. AMI with ZCS does not support
communication, and collective clear channel operation.
understanding. Refer to the web site
at http://www.w3.org
A voice processing system, that
combines telephone and data
communications networks to use,
directly from a telephone,
information that is stored in
databases.
wink start
A procedure that is used with some
protocols to indicate when a switch
or PABX is ready to accept address
signaling. After seizure, the switch
sends a short off-hook signal (wink)
when it is ready to accept address
Glossary 185
186 Installation
List of WebSphere Voice Response and associated
documentation
Here is a list of the documentation for WebSphere Voice Response for AIX and
associated products. PDF and HTML versions of the documentation are
available from the IBM Publications Center at http://www.ibm.com/shop/
publications/order. Hardcopy books, where available, can be ordered through
your IBM representative or at this Web site.
WebSphere Voice Response for AIX documentation can also be found by going
to the IBM Pervasive software Web site at http://www.ibm.com/software/
pervasive, selecting the WebSphere Voice products link, and then selecting
the library link from the WebSphere Voice Response page.
PDF and HTML versions of the WebSphere Voice Response for AIX
publications are available on the CD-ROM supplied with the product. In
addition, WebSphere Voice Response for AIX, WebSphere Voice Response for
Windows, Unified Messaging, and other WebSphere Voice publications are
available together in PDF and HTML formats on a separately-orderable
CD-ROM (order number SK2T-1787).
Note: To read PDF versions of books you need to have the Adobe Acrobat
Reader (it can also be installed as a plug-in to a Web browser). It is available
from Adobe Systems at http://www.adobe.com .
WebSphere Voice Response software

v WebSphere Voice Response for AIX: General Information and Planning,
GC34-7084
v WebSphere Voice Response for AIX: Installation, GC34-7095
v WebSphere Voice Response for AIX: User Interface Guide, SC34-7091
v WebSphere Voice Response for AIX: Configuring the System, SC34-7078
v WebSphere Voice Response for AIX: Managing and Monitoring the System,
SC34-7085
v WebSphere Voice Response for AIX: Designing and Managing State Table
Applications, SC34-7081
v WebSphere Voice Response for AIX: Application Development using State Tables,
SC34-7076
v WebSphere Voice Response for AIX: Developing Java applications, GC34-7082
v WebSphere Voice Response for AIX: Deploying and Managing VoiceXML and Java
Applications, GC34-7080

v WebSphere Voice Response for AIX: Custom Servers, SC34-7079
v WebSphere Voice Response for AIX: 3270 Servers, SC34-7075
v WebSphere Voice Response for AIX: Problem Determination, GC34-7087
v WebSphere Voice Response for AIX: Fax using Brooktrout , GC34-7083
v WebSphere Voice Response for AIX: Cisco ICM Interface User's Guide, SC34-7077
v WebSphere Voice Response for AIX: Programming for the ADSI Feature,
SC34-7088
v WebSphere Voice Response for AIX: Programming for the Signaling Interface,
SC34-7089
v WebSphere Voice Response for AIX: Voice over IP using Session Initiation
Protocol, GC34-7093
v WebSphere Voice Response for AIX: Using the CCXML Browser, SC34-7092
v WebSphere Voice Response for AIX: VoiceXML Programmer's Guide, SC34-7117
IBM hardware for use with WebSphere Voice Response

v IBM Quad Digital Trunk Telephony PCI Adapter (DTTA): Installation and User's
Guide, part number 00P3119 (DTTA card)
WebSphere Voice Response related products

WebSphere Voice Server
The documentation for Version 5.1 of WebSphere Voice Server is provided in

the form of an HTML-based information center, and can be found at:
http://publib.boulder.ibm.com/pvc/wvs/51/en/infocenter/index.html
Unified Messaging for WebSphere Voice Response

v Unified Messaging: General Information and Planning, GC34-6398
v Unified Messaging: Subscriber's Guide (Types 0, 1, 2, 3, 4 and 9), SC34-6403
v Unified Messaging: Subscriber's Guide (Types 5, 6, 7 and 8), SC34-6400
v Unified Messaging: Administrator's Guide, SC34-6399
v Unified Messaging: Voice Interface, GC34-6401
v Unified Messaging: Web Services Voicemail API, SC34-6975
Unified Messaging publications can be found by going to the IBM Pervasive

software Web site at http://www.ibm.com/software/pervasive, selecting the
products link, and then selecting the library link from the Unified Messaging
page.
AIX and the IBM pSeries computer
For information on AIX Version 6.1, refer to the AIX V6.1 infocenter
188 Installation
For information on System p5 and BladeCenter computers, refer to the IBM
Power hardware infocenter
HACMP
v HACMP for AIX: HACMP 5.4 Concepts and Facilities, SC23-4864-09
v HACMP for AIX: HACMP 5.4 Planning Guide, SC23-4861-09
v HACMP for AIX: HACMP 5.4 Installation Guide, SC23-5209-00
v HACMP for AIX: HACMP 5.4 Administration Guide, SC23-4862-09
v HACMP for AIX: HACMP 5.4 Smart Assist for DB2, SC23-5179-03
v HACMP for AIX: HACMP 5.4 Troubleshooting, SC23-5177-03
v HACMP for AIX: Enhanced Scalability Installation and Administration Guide,
Volume 1, SC23-4284
v HACMP for AIX: Enhanced Scalability Installation and Administration Guide,
Volume 2, SC23-4306
For more information on HACMP, refer to the HACMP Library and the AIX
V6.1 infocenter.
SS7
v SS7 Support for WebSphere Voice Response: SS7 User's Guide, GC34-7090
IBM SS7 Support for WebSphere Voice Response observes the applicable parts
of the following specifications for ISUP:
v CCITT Blue book (1988) Q.701 - Q.707
v ITU-T (formerly CCITT) Recommendations Q.700 - Q.716, Volume VI Fascicle
VI.7
v ITU-T White book (1993) Q.711 - Q.714
v ITU-T (formerly CCITT) Recommendations Q.721 - Q.725, Volume VI Fascicle
VI.8
v ITU-T White book (1992) Q.730 group
v ITU-T White book (1992) Q.761 - Q.764
v ITU-T (formerly CCITT) Recommendations Q.771 - Q.775, Q.791, Volume VI
Fascicle VI.9
ADC
v ADC NewNet AccessMANAGER™: Installation and Maintenance
Manual
v ADC NewNet AccessMANAGER™: User Manual
List of WebSphere Voice Response and associated documentation 189

WebSphere Voice Response ISDN support observes the applicable parts of the
following standards for User Side protocol:
Custom ISDN Standards:
v Northern Telecom DMS/250 Primary Rate Interface NIS A211-4 Release
8, July 1995. (IEC05 level)
v Northern Telecom DMS/100 Primary Rate Interface NIS A211-1 Release
7.05, May 1998. (NA007 & RLT)
v AT&T 5ESS Switch. ISDN Primary Rate Interface Specification. 5E7 and
5E8 Software Release AT&T 235-900-332. Issue 2.00 December 1991
v AT&T 5ESS Switch. ISDN Primary Rate Interface Specification. 5E9
Software Release AT&T 235-900-342. Issue 1.00 November 1993
(National ISDN only)
v Lucent 5ESS-2000 Switch ISDN Primary Rate Interface, Interface
Specification, 5E9(2) and Later Software Releases, 235-900-342. Issue
5.00 January 1997 (National ISDN only)
v AT&T ISDN Primary Rate Specification TR41449 July 1989
v AT&T ISDN Primary Rate Specification TR41459 August 1996
Euro-ISDN
The following documents refer to the specifications required for
observing ISDN:
v TBR4-ISDN; Attachment Requirements For Terminal Equipment To
Connect To An ISDN Using ISDN Primary Rate Access, Edition 1, Nov.
95, English
v CTR 4 - European Communities Commission Decision 94/796/EC
published in the Official Journal of the European Communities L
329, 20 December 94 (ISDN PRA)
National ISDN
National ISDN is described in the following publications:
v National ISDN, SR-NWT-002006, Issue 1, August 1991, published by
Bellcore
v National ISDN-1, SR-NWT-001937, Issue 1, February 1991, published
by Bellcore
v National ISDN-2, SR-NWT-002120, Issue 1, May 1992, published by
Bellcore
INS Net Service 1500
INS Net Service is described in the following publications:
190 Installation
v Interface for the INS Net Service Volume 1 (Outline), 7th Edition,
published by Nippon Telegraph and Telephone Corporation
v Interface for the INS Net Service Volume 2 (Layer 1 & 2 Specifications),
4th Edition, published by Nippon Telegraph and Telephone
Corporation
v Interface for the INS Net Service Volume 3 (Layer 3 Circuit Switching),
5th Edition, published by Nippon Telegraph and Telephone
Corporation
Bellcore Specifications for ADSI Telephones
The following Bellcore specification documents contain technical details of the

requirements for ADSI telephones, and the interface to voice response systems
such as WebSphere Voice Response:
v SR-INS-002461: CustomerPremises Equipment Compatibility Considerations for
the Analog Display Services Interface
v TR-NWT-001273: Generic Requirements for an SPCS to Customer Premises
Equipment Data Interface for Analog Display Services
List of WebSphere Voice Response and associated documentation 191

192 Installation
Index
AS/400
Special characters example A 109
/usr file system 4
example B 110
.Xdefaults file 127
example C 111
$ 67
attaching
Numerics attaching
See connecting 27
3174 communications controller 109, 112
attaching pSeries to data communications
3270 host access
network 101
redefining interface after migration 86
automatic restart 124
3270 server
filesets for 17
sample program import file 80
B
background processes
A See processes 1
backing up
accessibility xi
ACL backing up
See Application Connectivity Link (ACL) 25 See also save-and-restore method 36
ADSI custom server before migrating 36
import files 82 system image 34
AIX backing-up
account: setting password for dtuser 49, 89 VoiceXML and Java 38
account: setting password on an SSI database backing-up data before migration 8
server 100
operating environment: setting for dtuser 89
C
C language compiler
operating system: installing 15
licenses for cloned systems 97
operating system: required level 15
required software 2
shutdown, shutting down WebSphere Voice
C++ 2, 17, 85, 97
Response automatically 124
CA_ 148
system parameter : system page space 96
cable
system parameter: maximum number of user
E1 digital interface cable 25
processes 94
T1 digital interface cable 25
AIX account
to connect WebSphere Voice Response to the
See also dtuser account 49
telephone network 25
AIX operating system
CACHEM entry in tasklist.data 92
documentation 4
call control information
AIX system parameter
See exchange data link 1
See also system parameter 1
CallPath Server
AIXwindows
import files 80
.Xdefaults file 127
channel
preferred on production system 19
enabling 73
restarting 125
character set 99
application
CHPM entry in tasklist.data 92
See voice application 1
Cisco custom server
Application Connectivity Link (ACL)
import files 82
ACL entry in tasklist.data 92
cloning a WebSphere Voice Response system 97
connecting 25
CNTL entry in tasklist.data 92
ARC_ 147
CODECINIT entry in tasklist.data 92
archived log file, migration, archiving before 32
commands
archived report file, migration, archiving before 32
DT_ 130

commands (continued) defining (continued)
dt_setowner 144 tape drive 98
Common Desktop Environment (CDE) VMS exchange data link to AIX 90
avoiding on production system 19 DEV_ 147
starting WebSphere Voice Response 68 device definition
communication controller changing 98
example B 110 supplied defaults 98
example C 111 devices
example D 112 installing before software 4
communication port diagnostics
exchange data link 98 DTTA 55
Communications Server hardware 55
description 101 digital trunk adapter
filesets for SDLC connection 16 DTTA 23
filesets for token-ring LAN 16 Digital Trunk Telephony Adapter (DTTA)
introduction 101 running diagnostics 55
required level 18 setting ownership 53
starting manually 114 unrecognized 55
compatibility, application 8 DIR 147
component processes, WebSphere Voice Response 92 disk space
concurrent network license model 57 required for restoring information 77
configuring diskette drive
attached devices 98 defining 98
exchange data link 90 display name 68, 119
connect creating a file for 119
DTTA 26 problems starting WebSphere Voice Response 127
converting to a single system image 13 starting WebSphere Voice Response 67
copying starting WebSphere Voice Response from a remote
cloning WebSphere Voice Response systems 97 terminal 121
CTRL3270 entry in tasklist.data 92 DISPLAY variable
CUR_ 147 display names 119
custom server prerequisites 67
rebuilding after migration 85 Welcome window not displayed 127
customer managed licensing 57 DT_ 130
dt_setowner command 144
D dtauto, restarting WebSphere Voice Response
data communications network automatically 124
defining 101 DTdatabase command 52
hardware 3 DTforce.clean command 131
See also token-ring LAN 1 DTJ_ 147
database DTSNMPD_ 92
creating 52 DTstatus.out file 120
remote database access 3 DTTA 21
DBHEALTH entry in tasklist.data 92 connect
DBIM entry in tasklist.data 92 prerequisites 26
defining procedure 26
3270 host interface 86 dtuser account
asynchronous exchange data link to AIX 90 needed to install PTF 5, 19
data communications network 101 setting AIX environment for 89
diskette drive 98 setting password on an SSI database server 100
exchange data link port 98 setting up 5, 49
exchange data link to AIX 90 starting WebSphere Voice Response 67
printer queue 98 DTXA 21
SMSI exchange data link to AIX 90
SNA configuration 104, 105
194 Installation
hardware
E data communications network 3
EDL Communication Port parameter 98
diagnostics 55
environment variables
high quality voice 3
$ 147, 148
speech recognition 2
setting when logged on as root 89
telephony 21
Ethernet network, filesets for TCP/IP 16
text-to-speech 3
exchange data link
HOME 147
configuring the attachment 90
homologation 21
defining as a TTY device 90, 91
defining the communication port 98
introduction 2
I
immediate shutdown 122
export command import file
file names, restrictions on 33 importing 80
path names, restrictions on 33 import-export method
exporting exporting application data 33
voice applications 33 importing
exportsna utility 102 optional features 80
initializing
F WebSphere Voice Response, problems with 126
fax application, sample application import file 81
installation
file permissions 89
test 70
file system
installing
local /usr 4
AIX and other LPPs 15
filesets
custom servers 85
devices.artic960 44
WebSphere Voice Response software 42
devices.artic960dev 44
ISDN
devices.dirTalk.
signaling process:import files 81
BrooktroutFax 44
devices.dirTalk.artic960 44
dirTalk.3270 44
K
keyboard
dirTalk.ADSI 44 focus policy 127
dirTalk.BrooktroutFax 44 map : introduction 99
dirTalk.DT 44 map : language environment 99
dirTalk.DTBE 44 map : remapping 99
dirTalk.DVT 44
dirTalk.GEOTEL 44 L
dirTalk.ISDN.ATT 44 language compiler
dirTalk.ISDN.com 44 importing custom servers 85
dirTalk.ISDN.DMS100 44 licenses for cloned systems 97
dirTalk.ISDN.EuroISDN 44 required level 17
dirTalk.ISDN.INS1500 44 required software 2, 17
dirTalk.SP 44 language environment, keyboard 99
dirTalk.SS7_D7. license files 59
D7_Enablement 44 licensed program products 17
dirTalk.TDD 44 licensed program products (LPPs)
focus policy levels required 17
keyboard 127 Licensed program products (LPPs) 2
window manager 127 Licenses 57
foreground processes configuring 60
See processes 1 distributing 64
enrolling 63
H management 57
H.100 adapter
networked 57, 58, 59
DTTA 23
overview 57
order 23
Index 195
link station
defining 104, 105
N
NAU (network accessible unit) 101
example B 110
network
example C 111
See data communications network, telephone
example D 112
network, token-ring LAN 1
SDLC RS-232 host, configuring 103
network accessible unit (NAU) 101
starting automatically 114
starting manually 114
token ring, configuring 103
O
OAM entry in tasklist.data 92
local /usr file system 4 OAM_ 147
log file optional feature
archiving before migration 32 import files 80
LOG_ 147
logging on P
problems with 129 pack
to WebSphere Voice Response 67 introduction 21
logical partition 96 page space, system
LOGS 147 increasing 96
LPPs 17 needed for WebSphere Voice Response 96
See licensed program products (LPPs) 1 password
LRS entry in tasklist.data 92 setting on an SSI database server 100
lsattr command 95 WebSphere Voice Response administrator 69, 122
lsitab command PATH 147
starting communications server automatically 114 PERCENTAGE 148
turning auto restart on 125 preinstalled software
lsps command 96 installation method 7
setting the dtuser password 40, 49
M prerequisite software 17
maximum, number of user processes
printer
(maxuproc parameter) 94
defining 98
(maxuproc parameter), procedure 95
processes
message information
changing maxuproc parameter 94
problems with starting 129
migrating from WebSphere Voice Response
required number 94
application compatibility 8
WebSphere Voice Response component 92
exporting application data 33
programming models
introduction 8
JavaBeans (not recommended for new
restoring data 77
applications) 2
saving data 36
The WebSphere Voice Response proprietary state
starting migration 34
table interface 2
migration
VoiceXML 1.0 2
voiceXML and Java applications 9
VoiceXML 2.1 2
mkitab command
WebSphere Voice Response Java application
starting communications server automatically 114
programming interface 2
turning auto restart on 125
PROMPTM entry in tasklist.data 92
mksysb 8
PTF
mksysb command
dtuser required for installing 5, 19
backing up before installation 34
cloning a WebSphere Voice Response system 97 Q
monitoring 120 quiesce shutdown 122
initialization 120
remote, equipment required for 3 R
MWISERVER entry in tasklist.data 93 rc.dirTalk file 117
rcsna
See starting Communications Server 114
196 Installation
regression test 34 setting ownership
remapping the keyboard 99 DTTA 53
remote data access 3 SGAMSERVER entry in tasklist.data 92
remote system management shutdown 130
equipment required 3 shutdown command 130
remote terminal, displaying WebSphere Voice Response shutting down
windows 121 AIX 51
removing WebSphere Voice Response automatically 124
WebSphere Voice Response software 133 WebSphere Voice Response manually 122
report Simple Network Management Protocol (SNMP)
archiving before migration 32 filesets for 17
required files installing 115
AIX operating system 15 introduction 3
licensed program products 17 MIB definitions 115
resource files, changing 79 Simplified Message Desk Interface (SMDI)
restarting connecting 25
AIXwindows 125 entry in tasklist.data 93
auto restart 124 Simplified Message Service Interface (SMSI)
waiting till processes terminate 124 connecting 25
WebSphere Voice Response 125 Simplified Message Service Interface (SMSI) entry in
restoreDT command 79 tasklist.data 92
restoring single system image
application data after migrating 77 changing the server password 100
system parameters 126 converting to 13
VoiceXML and Java data 84 converting to stand-alone systems 14
rmitab command 125 skills required for installation 4
root user SLDAEMON entry in tasklist.data 92
required authority 4 SMDI
setting WebSphere Voice Response environment See Simplified Message Desk Interface (SMDI) 25
for 89 SMSERVER entry in tasklist.data 92
RS/6000 SMSI
attaching to data communications network 101 See Simplified Message Service Interface (SMSI) 25
migrating SNA servers 86 SNA
WebSphere Voice Response hardware 2 communication:starting automatically 114
RS232 connection configuration: requirements for WebSphere Voice
See exchange data link 1 Response 106
SNA link station
S See link station 114
save command SNA Server
file names, restrictions on 37 See Communications Server 101
path names, restrictions on 37 snamig utility 102
saving application data 37 SNMP
save-and-restore method See Simple Network Management Protocol
restoring application data 77 (SNMP) 3
saving application data 36 soft/hard stop licensing policy 57
saveDT 9 software
saveDT command required 17
See save command 37 software prerequisites 15
screen saver speech recognition
disabling on a production system 20 equipment required 2
SCRSERVER entry in tasklist.data 92 SR-INS-002461 Bellcore specification 191
SDI entry in tasklist.data 92 START entry in tasklist.data 92
SDLC connection 112 starting
See Digital Trunk Extended Adapter (DTXA) 21 Communications Server: manually 114
See Digital Trunk Telephony Adapter (DTTA) 21 Communications Server:automatically 114
Index 197
starting (continued)
WebSphere Voice Response during installation 67
T
T1 digital interface cable
WebSphere Voice Response: using DTstatus.out 120
description 25
WebSphere Voice Response:auto restart 124
tape drive
WebSphere Voice Response:problems with 126
defining 98
STATEM entry in tasklist.data 92
tar command
status
export command 33
file 120
save command 37
window 68, 120
tasklist.data file 92, 115
stopping
tasklist.data, during migration 32
WebSphere Voice Response when you can't log
TCP/IP
on 129
See Transmission Control Protocol/Internet Protocol
storage
(TCP/IP) 1
See disk space 1
Telecommunications Device for the Deaf (TDD)
STPDSERVER entry in tasklist.data 92
import files 82
synchronous data link control
telephony equipment 1
See SDLC connection 1
testing installation
SYS_ 147
regression test 34
SYSPARM_ 147
using the test application 70
system components 1
verifying a bisynchronous exchange data link 90
system console, keyboard map 99
verifying an ACL exchange data link 90
system image
text-to-speech
backing up before migration 34
equipment required 3
system management
THRESHOLD_ 148
equipment required 3
TMP_ 147
System Management Interface Tool (SMIT)
token-ring LAN
defining an exchange data link 90
connecting WebSphere Voice Response using:
increasing file system size 78
example A 109
increasing page space 96
connecting WebSphere Voice Response
introduction 4
using:example B 110
removing DirectTalk 134
connecting WebSphere Voice Response
See System Management Interface Tool (SMIT) 1
using:example D 112
starting Communications Server manually 114
filesets for Communications Server 16
starting link stations manually 114, 121
filesets for TCP/IP 16
starting WebSphere Voice Response from a remote
TR-NWT-001273 Bellcore specification 191
terminal 121
Transmission Control Protocol/Internet Protocol
system page space
(TCP/IP)
See page space, system 1
filesets for Ethernet network 16
system parameter
filesets for token-ring LAN 16
See also AIX system parameter 1
trunk
system parameters
enabling 73
restoring 126
TSLOT entry in tasklist.data 92
system prompts
TTY device
import files 82
System/370
example A 109
example B 110
U
UDSERVER entry in tasklist.data 92
example C 111 Ultimedia Audio Adapter for AIX 3
example D 112 uninstalling
System/390 WebSphere Voice Response 133
example A 109 unrecognized
example B 110 DTTA 55
example C 111 UPSERVER entry in tasklist.data 92
example D 112 upward compatibility 8
198 Installation
user ID window manager focus policy 127
See dtuser account 49
user processes X
See processes 1 Xdefaults file 127
utilities xhost command 121
WebSphere Voice Response: commands 137 XREFSERVER entry in tasklist.data 92
Xstation keyboard map 99
V
VAE 147
vae.setenv command
running the script 89
setting up the environment 52, 78
vae.setuser command 49
VAEBIN 147
vaeinit command 68, 121
VAETOOLS 147
VAGIO entry in tasklist.data 92
VAGSERVER entry in tasklist.data 92
validating the installation 70
Virtual Telecommunication Access Method
(VTAM) 106
VMS
See Voice Message Service (VMS) 25
voice application
exporting before migrating 33
restoring after migration 77
sample program import files 80
saving before migrating 36
Voice Message Service (VMS)
connecting 25
Voice Message Service (VMS) entry in tasklist.data 93
voice recognition
See speech recognition 2
VoiceXML 2.1 and Java Enhancements
AIX version 6.1 15
installation 9
migration 9
VoiceXML and Java
backing-up 38
VoiceXML and Java data
restoring 84
VTAM (Virtual Telecommunication Access
Method) 106
W
converting from 13
restoring data 77
saving data 36
starting migration from 34
Welcome window
displayed as normal 129
not displayed as normal 126
window
displaying on a remote terminal 121
Index 199
200 Installation

Program Number: 5724-I07
GC34-7095-01

Installation: Websphere Voice Response For Aix With Directtalk Technology

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Installation: Websphere Voice Response For Aix With Directtalk Technology

Transféré par

Droits d'auteur :

Formats disponibles

WebSphere Voice Response for AIX with DirectTalk

© Copyright IBM Corp. 1991, 2010 iii

Appendix C. WebSphere Voice Response Index . . . . . . . . . . . . . 193

© Copyright IBM Corp. 1991, 2010 vii

Who should use this information

As the installer, you also need to understand the data communications

How to use this information

© Copyright IBM Corp. 1991, 2010 ix

This book uses the following typographic conventions:

WebSphere Voice Response for AIX is a voice application enabler. The

With WebSphere Voice Response you can perform many application

About this information xi

Where to find more information

Making comments on this book

You can get your comments to us quickly by sending an e-mail to

About this information xiii

This chapter includes the following sections:

WebSphere Voice Response system components

WebSphere Voice Response can work with a variety of telephone switches,

© Copyright IBM Corp. 1991, 2010 1

No hardware adapters are required with BladeCenter or pSeries computers

Exchange data link software provided with WebSphere Voice Response

The detailed information in WebSphere Voice Response for AIX: General

Speech recognition can be provided by WebSphere Voice Server (a separately

WebSphere Voice Response can also be integrated with other MRCP

High-quality sound recording and playback

To record high-quality sound or use audio editing software on a separate

VoiceXML or Java applications and business data can be resident on a Web

Having decided how your system is to access business data, refer to

The network can include:

Remote system management

If your network is managed by NetView® or another network management

What you need for installation

You also need:

Is the communication to be via telephony switch, or

Is the trunk interface E1 or T1?

Is the signaling protocol CAS, ISDN or SS7? (This is

If using T1 ISDN with Trunk 1: Trunk 9:

Trunk 5: Trunk 13:

Trunk 6: Trunk 14:

Trunk 7: Trunk 15:

Trunk 8: Trunk 16:

To what switch are you

Are you using an SP

3. Determine your installation method, either:

WebSphere Voice Response applications are upwardly compatible from release

If you already have applications in production, you need to consider your

Making a backup using mksysb

Upgrade one or more clients:

On the first client machine:

Upgrade the server:

Restart the reduced system:

Migrate and restart the remaining clients:

Note: Ensure that /home/dtdb23in/sqllib/db2nodes.cfg contains the HA

Upgrade one or more clients:

On the first client machine:

Failover to server B and create a partition:

Failback to the Version 4.2 partition (system down):

The system must now be stopped to allow services to be failed-back to server

Start operating using the partition and migrate the partition:

At least the bos.rte fileset must be at the required level.

Binder and loader commands