WVR61 Problem Determination c3470877

WebSphere Voice Response for AIX with DirectTalk

Technology
Problem Determination
Version 6.1
GC34-7087-07
Note
Before using this information and the product it supports, read the general information under “Notices” on
page 451.
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, 2013.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Figures . . . . . . . . . . . . . vii Documenting your problem . . . . . . 21
Determining problem severity . . . . . 23
Tables . . . . . . . . . . . . . . ix Reporting a problem with a C-language
program . . . . . . . . . . . . 24
About this information . . . . . . . . xi Running hardware diagnostic procedures . . 25
How to use this information. . . . . . . xi Adapter feature codes. . . . . . . . 25
Typographic conventions . . . . . . . xii DTTA device driver . . . . . . . . 25
Accessibility . . . . . . . . . . . . xii Diagnosing unrecognized DTTAs on PCI
Notes on terminology . . . . . . . . xiii systems . . . . . . . . . . . . 27
Where to find more information . . . . . xiii Running diagnostics on the DTTA . . . 27
Useful Web sites . . . . . . . . . xiii Diagnosing telephony line errors . . . . . 28
Making comments on this book . . . . . xiv What causes telephony line errors? . . . 28
Diagnosing telephony line errors on the
Chapter 1. Introducing WebSphere Voice DTTA . . . . . . . . . . . . . 29
Response support . . . . . . . . . . 1 Using debugrec to record input and output 29
Online help . . . . . . . . . . . . 1
IBM Support Assistant (ISA) . . . . . . . 2 Chapter 3. Solving WebSphere Voice
WebSphere Voice Response product Response problems . . . . . . . . . 31
documentation . . . . . . . . . . . 3 How to use this information . . . . . . 31
IBM support resources . . . . . . . . . 3 When nothing works . . . . . . . . . 32
What to expect when you call IBM Support . . 3 Problems found during installation or system
startup . . . . . . . . . . . . . . 33
Chapter 2. Analyzing the problem . . . . 5 WebSphere Voice Response software does
Cataloging the symptoms . . . . . . . . 5 not start to initialize . . . . . . . . 33
Have any system conditions changed? . . 5 Fileset consistency warnings are displayed
Which component is failing? . . . . . . 6 on startup. . . . . . . . . . . . 35
Describing the state of the system . . . . . 6 Welcome window does not display . . . 36
Describing the system by using dtProblem 6 DB2 error SQL6048N is generated when
Collecting Java and VoiceXML environment attempting to start WebSphere Voice
specific information . . . . . . . . . 7 Response . . . . . . . . . . . . 37
Determining how much disk space is free . 8 WebSphere Voice Response reports
Determining the maximum number of user "SQL1042C with SQLSTATE=58004" error . 38
processes the system can start . . . . . 9 The startup of WebSphere Voice Response
Checking how much page space has been takes longer than normal and generates
defined . . . . . . . . . . . . 10 errors . . . . . . . . . . . . . 38
Determining how many buffers are The windows on an Xstation are displayed
defined for system use . . . . . . . 12 in the wrong font . . . . . . . . . 39
Determining what level of software is restoreDT returns with an error from the
installed . . . . . . . . . . . . 13 "tar -xhv -f" command . . . . . . . 39
Reviewing the error log . . . . . . . 13 BrooktroutFax Adapter TR114 failure. . . 39
Copying the error log to tape or diskette 14 Failed to start Voice Response node -
Before you call IBM Support . . . . . . 15 error_id 21004 . . . . . . . . . . 40
Capturing a system-level trace . . . . . 15 The ricdiag utility fails following a mksysb
Capturing binary trace . . . . . . . 18 restore . . . . . . . . . . . . . 40
© Copyright IBM Corp. 1991, 2013 iii

Error occurs when logging onto Exceptions reported when a Java or
WebSphere Voice Response GUI after VoiceXML application is started from a
running mksysb. . . . . . . . . . 41 VRNode . . . . . . . . . . . . 64
DTSNMPD_START fails to start after Dial, MakeCall, or TransferCall actions
upgrading AIX . . . . . . . . . . 41 behave unexpectedly . . . . . . . . 65
Running vae.setenv produces DB2 errors 42 Get actions that use the telephone line do
Database error occurs when trying to not execute . . . . . . . . . . . 67
connect to the WebSphere Voice Response SendData or ReceiveData action does not
database . . . . . . . . . . . . 42 provide expected results . . . . . . . 67
License Enrollment errors during Application fails attempting to play voice 68
WebSphere Voice Response Version 6.1 Common problems with hangup detection 70
migration . . . . . . . . . . . . 42 Common problems with voice interrupt
DB2 errors during WebSphere Voice detection . . . . . . . . . . . . 70
Response Version 6.1 installation . . . . 43 Common problems with background
WebSphere Voice Response Version 6.1 music . . . . . . . . . . . . . 71
migration errors related to DB2 software . 44 Results of running an application are not
Configuring SS7 in a WebSphere Voice as expected . . . . . . . . . . . 74
Response Single System Image . . . . . 44 Mailbox does not play recorded message 75
Network problems . . . . . . . . . . 44 3270 server does not start . . . . . . 75
WebSphere Voice Response does not 3270 server script fails . . . . . . . 76
initiate outbound calls . . . . . . . 45 Custom server does not start . . . . . 77
WebSphere Voice Response does not WebSphere Voice Response does not accept
answer the phone . . . . . . . . . 46 data from the caller's keypad . . . . . 77
WebSphere Voice Response receives no DTMF input is sometimes not recognized
information from the exchange data link . 50 in a state table application . . . . . . 78
WebSphere Voice Response answers the WebSphere Voice Response generates
phone with “technical difficulties” . . . 51 "unsupported language" error when
Telephone channel is hung . . . . . . 52 running VoiceXML Application. . . . . 78
No SNMP traps are being sent . . . . . 53 Exceptions reported when a WebSphere
WebSphere Voice Response cannot access a Voice Response Java/VoiceXML application
remote 3270 host . . . . . . . . . 54 is started from VRNode . . . . . . . 79
3270 session is permanently disabled. . . 55 FileCache error on a WebSphere Voice
3270 emulation does not work . . . . . 55 Response VoiceXML 2.0 system with
Telephony connection does not multiple application Nodes . . . . . . 80
synchronize . . . . . . . . . . . 55 Compression of voice messaging can result
Cannot enable trunk . . . . . . . . 56 in poor quality audio . . . . . . . . 80
DB2 does not start if the machine name is error_id 1 and error_id 25032 caused by an
changed after DB2 is installed . . . . . 58 unsupported application design . . . . 81
Resolving error_id 26001 . . . . . . . 58 Error on recordutterance with Nuance
Problems found while running voice speech server . . . . . . . . . . 82
applications . . . . . . . . . . . . 59 Text-to-speech audio in an application
Voice application does not start . . . . 60 sounds like static . . . . . . . . . 82
Calls do not transfer . . . . . . . . 60 Timeout waiting for response from
FileCache failures when running VoiceXML grammar compiler . . . . . . . . . 82
applications . . . . . . . . . . . 62 Performance and other general problems . . 83
Newly installed voice audio files not A process does not start when you expect
played by VoiceXML application . . . . 63 it to . . . . . . . . . . . . . . 83
VXMLParserPool::Parser created over WebSphere Voice Response windows start
capacity . . . . . . . . . . . . 64 without being selected . . . . . . . 84
The system runs extremely slowly . . . 84
iv Problem Determination
WebSphere Voice Response telephony Appendix A. Messages issued during
activity is unexpectedly disrupted. . . . 87 migration or import . . . . . . . . 169
WebSphere Voice Response cannot access
the printer . . . . . . . . . . . 88 Appendix B. WebSphere Voice Response
WebSphere Voice Response is not messages identified by number . . . . 173
accumulating call detail records . . . . 88 Example Message . . . . . . . . . . 175
Frequent “without sending detach” Session Manager/CHP . . . . . . . . 176
messages . . . . . . . . . . . . 89 DB2 return codes . . . . . . . . . . 191
WebSphere Voice Response does not shut DBSM (database server) return codes . . . 193
down . . . . . . . . . . . . . 89 NODEM (Node Manager) . . . . . . . 211
Screen is blank or frozen while WebSphere STPD (State Table/Prompt Directory) . . . 215
Voice Response is running . . . . . . 89 VAE (General WebSphere Voice Response) 216
Alarm graphic turns yellow or red . . . 90 LUM (License Use Management). . . . . 222
Applications and operations keywords SMSI (Simplified Message Service Interface) 225
turn gray . . . . . . . . . . . . 90 CACHE (Cache Manager) . . . . . . . 229
Channel available indicator turns red DBIM (Internal Database Manager) . . . . 231
independently . . . . . . . . . . 90 VPACK, SPACK and XPACK . . . . . . 232
Telephony problem without an alarm VAD (Voice Application Development) . . . 263
indicator . . . . . . . . . . . . 90 ACL (Application Connectivity Link) . . . 264
Licenses are not granted . . . . . . . 91 CA (Custom Server) . . . . . . . . . 266
The system configuration GUI crashes DTBE (Java and VoiceXML environment) . . 271
when being closed . . . . . . . . . 92 SM_SRVR . . . . . . . . . . . . 272
/dev/systrctl1... message is displayed in CTRL3270 . . . . . . . . . . . . 274
Dtstatus.out . . . . . . . . . . . 93 OAM (Operations and Maintenance) . . . 284
File db2diag.log increases up to the AIX SNMP (Simple Network Management
system limit . . . . . . . . . . . 93 Protocol) . . . . . . . . . . . . . 297
dtjflog fails during logging . . . . . . 94 SDI (Signaling Device Driver Interface) . . 299
WebSphere Voice Response VRBE ISDN services . . . . . . . . . . . 312
OutOfMemory error . . . . . . . . 94 ISDN signaling process and ISDN call
control . . . . . . . . . . . . . 316
Chapter 4. Using the ISDN_Monitor . . . 95 ISDN D Layer 3 . . . . . . . . . . 321
The ISDN_Monitor. . . . . . . . . . 95 ISDN D Layer 2 and Layer 1 . . . . . . 324
Starting the ISDN_Monitor . . . . . . 95 VoIP . . . . . . . . . . . . . . 329
Stopping the ISDN_Monitor. . . . . . 96 SS7 . . . . . . . . . . . . . . 336
Restarting the ISDN_Monitor . . . . . 96 Timeslot Management . . . . . . . . 349
Monitoring a trunk which is then disabled 96 Pack Configuration . . . . . . . . . 352
Logging the ISDN_Monitor trace Signaling Interface . . . . . . . . . 354
information to a file . . . . . . . . 96 SpeechServer custom server . . . . . . 359
Decoding the ISDN_Monitor output . . . 96 CallPath_Sigproc Custom Server . . . . . 368
Other ISDN messages . . . . . . . 106 Java and VoiceXML environment messages 385
ISDN_Call_Transfer custom server . . . . 415
Chapter 5. Introducing the WebSphere Juke_Box custom server. . . . . . . . 422
Voice Response alarm messages. . . . 107 IBM_Trombone_Custom_Server . . . . . 435
Message destinations. . . . . . . . . 107 MRCP messages . . . . . . . . . . 442
Message content . . . . . . . . . . 108 VXML messages . . . . . . . . . . 444
Message categories . . . . . . . . . 111 Messages and explanations . . . . . 447
Message filtering . . . . . . . . . . 112
Messages by severity. . . . . . . . . 113 Notices . . . . . . . . . . . . . 451
Messages affected by filtering . . . . . . 163 Trademarks . . . . . . . . . . . . 453
Contents v
Glossary . . . . . . . . . . . . 455 Unified Messaging for WebSphere Voice
Response . . . . . . . . . . . 490
List of WebSphere Voice Response and AIX and the IBM pSeries computer . . . 491
associated documentation . . . . . . 489 HACMP . . . . . . . . . . . . 491
WebSphere Voice Response software . . . 489 SS7 . . . . . . . . . . . . . 491
IBM hardware for use with WebSphere Voice Integrated Services Digital Network. . . 492
Response . . . . . . . . . . . . 490 Bellcore Specifications for ADSI Telephones 493
WebSphere Voice Response related products 490
WebSphere Voice Server. . . . . . . 490 Index . . . . . . . . . . . . . 495
vi Problem Determination
Figures
1. Trace of a typical startup sequence 97 7. Flow of call related events for an
2. WebSphere Voice Response sending a outbound call from WebSphere Voice
DISC frame to the switch . . . . . . 98 Response . . . . . . . . . . . 103
3. WebSphere Voice Response sending 8. Outbound call fails . . . . . . . 105
SABME frames at one second intervals . 99 9. Trace of a call clearing . . . . . . 106
4. A RESTART message initializing a 10. Message information in the WebSphere
whole trunk . . . . . . . . . . 99 Voice Response error log . . . . . 109
5. The channel ID information element 101
6. Trace showing NFAS on a channel
enabled on a trunk with no signaling . 101
© Copyright IBM Corp. 1991, 2013 vii

viii Problem Determination
Tables
1. AIX system trace event IDs used by 6. WebSphere Voice Response messages
WebSphere Voice Response . . . . . 18 affected by filtering . . . . . . . 163
2. WebSphere Voice Response messages 7. Message numbers generated by each
classified as Red . . . . . . . . 113 software component . . . . . . . 173
3. WebSphere Voice Response messages 8. DB2 return codes . . . . . . . . 191
classified as Yellow . . . . . . . 127 9. WebSphere Voice Response database
4. WebSphere Voice Response messages return codes . . . . . . . . . . 193
classified as Green. . . . . . . . 151 10. Message codes and meanings . . . . 444
5. WebSphere Voice Response messages
classified as White. . . . . . . . 154
© Copyright IBM Corp. 1991, 2013 ix

x Problem Determination
About this information
This book describes how to isolate and diagnose problems that you might
find while using the IBM® WebSphere® Voice Response for AIX® with
DirectTalk® Technology voice processing system.
Throughout this book, the IBM WebSphere Voice Response for AIX voice
processing system is referred to as WebSphere Voice Response.
If you are a newcomer to WebSphere Voice Response, start with Chapter 1,

“Introducing WebSphere Voice Response support,” on page 1, which describes
the manuals and other support available for the product. Then read Chapter 2,
“Analyzing the problem,” on page 5, which describes how to handle any
problems with WebSphere Voice Response, and also explains how to get
additional help from IBM Support.
If you have a problem with WebSphere Voice Response, use the information
provided in Chapter 3, “Solving WebSphere Voice Response problems,” on
page 31 to solve it.
If you get a message when migrating or importing data, look it up in

Appendix A, “Messages issued during migration or import,” on page 169.
If you get a numbered WebSphere Voice Response message in the error.log

on the System Monitor, refer to it in Appendix B, “WebSphere Voice Response
messages identified by number,” on page 173, which is organized by message
number.
How to use this information

This book contains background information, procedures, and reference
information. The procedures explain how to complete the tasks for which you
are responsible.
The background information explains when to use the procedures and

contains prerequisites for using them successfully. Before you use any
procedure for the first time, read through all the relevant background
information.
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
© Copyright IBM Corp. 1991, 2013 xi

such as Save to work with information. If you are new to WebSphere Voice
Response, have a look at the WebSphere Voice Response for AIX: User Interface
Guide book, which tells you how to log on and log off, and use the WebSphere
Voice Response windows efficiently.
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.
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 IBM WebSphere Voice Server, or other MRCP-V1.0-compliant
speech recognition products. In addition, support for users of Telephony
Devices for the Deaf (TDD) is provided as part of the WebSphere Voice
Response product.
xii Problem Determination

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.
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
489).
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 489.
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/
About this information xiii

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/
CCXML Version 1.0 specification
http://www.w3.org/TR/2011/PR-ccxml-20110510/
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.
xiv Problem Determination

Chapter 1. Introducing WebSphere Voice Response
support
WebSphere Voice Response consists of more than just hardware and software
components. When you buy WebSphere Voice Response, you also get access to
system support for the product. Part of this support is the on-line help and
the documentation that comes with the system. The documentation describes
how to use WebSphere Voice Response to meet your business needs. In
addition, WebSphere Voice Response includes a network of support resources,
available up to 24 hours a day, 7 days a week depending on your service
agreement with IBM.
If you have a problem with WebSphere Voice Response, first analyze the
problem, using the guidance provided in Chapter 2, “Analyzing the problem,”
on page 5, and gather all the relevant information that you can. Next, use the
information in the subsequent chapters to try and find a solution to the
problem. If you cannot find sufficient information to help you solve the
problem, call IBM Support.
This chapter provides an overview of the support that you can expect from
IBM. For a detailed description of the support available, look in the IBM
Software Support Handbook, available from the Software Support Web site at
http://ps.software.ibm.com.
Online help
Every window in the WebSphere Voice Response user interface has a help
button or a help menu. The help gives you a brief explanation of the contents
of the window and how to use it.
v Always select help when a pop-up dialog displays an error or warning
message you don't understand. The help provides a little more explanation.
v Select help in the parameter windows in System Configuration, if you need
an explanation of the parameter. (This information is also included in
WebSphere Voice Response for AIX: Configuring the System.)
v Select help, in other windows if you cannot remember what to do. If,
however, you are new to the system, or trying something for the first time,
you will probably find that the more detailed product documentation is
more useful. The product documentation contain a lot of background
information that makes it easier to understand new concepts and
terminology.
© Copyright IBM Corp. 1991, 2013 1

In addition, on-line explanations are available for all the alarms displayed in
the System Monitor Alarms window. To view these explanations, select the
message in the Alarms window (see WebSphere Voice Response for AIX:
Configuring the System for details.) The explanations are also listed in
Appendix B, “WebSphere Voice Response messages identified by number,” on
page 173.
IBM Support Assistant (ISA)

The IBM Support Assistant (ISA) saves you time when searching for product,
support and educational resources. If a problem report needs to be opened,
ISA helps you gather support information, then create and track your
electronic problem report. ISA is a free, standalone application that you can
download and install, together with the corresponding plugin for WebSphere
Voice Response.
ISA provides the following services:

v Improves your ability to locate IBM support, development and educational
information through a federated search interface (one search to multiple
resources).
v Provides quick access to the IBM Education Assistant and key product
education roadmaps.
v Simplifies access to IBM product home pages, product support pages, as
well as product forums or newsgroups, through convenient links.
v Saves time submitting problems to IBM Support by collecting key
information, then electronically creating a Problem Management Report
(PMR)
To obtain ISA, go to the download page at https://www14.software.ibm.com/

webapp/iwm/web/preLogin.do?source=isa, and download the installation
package for any platform on which you will use ISA. You need to login using
your IBM web identity (the same identity as used for sites such as MySupport
and developerWorks). If you do not already have an IBM web identity, you
may complete the free registration process on the web page to obtain one. The
install image that you download includes an HTML Installation and
Troubleshooting Guide.
To obtain the ISA plug-ins specific to the IBM products you are using, such as
WebSphere Voice Response, go to the "Support and downloads" web page at
http://www.ibm.com/support/us/, and enter the search term "support
assistant".
2 Problem Determination
WebSphere Voice Response product documentation
The WebSphere Voice Response product documentation contains all the
information you need to plan, install, configure, and maintain WebSphere
Voice Response.
The purpose of this manual is to help you solve problems. The other manuals
contain additional information that might be helpful when you have a
problem to solve. A complete list of the available books and where you can
obtain them is shown in “List of WebSphere Voice Response and associated
documentation” on page 489
IBM support resources

IBM provides a support center for your IBM software and hardware.
Your IBM software support center can help in situations such as when you
encounter an undocumented error message, or an unexpected result after you
have followed the instructions in the documentation.
IBM Support can access additional product documentation, and files that
document the experiences other companies have had with WebSphere Voice
Response. In addition to the support center, IBM experts and other technical
resources are ready to provide assistance.
What to expect when you call IBM Support

When you call support, you will be talking with someone who assumes that
you have first tried to analyze the problem and solve it yourself, and they will
want to know what happened. The more information you can provide, the
more quickly IBM can help.
Before calling IBM Support, use the guidance given in Chapter 2, “Analyzing
the problem,” on page 5 to analyze the problem, and then use the information
in Chapter 3, “Solving WebSphere Voice Response problems,” on page 31 to
try to solve the problem yourself—this is sometimes the quickest and easiest
method.
Apart from your analysis of the problem, have the following information
ready:
v Your customer number.
v Whether the problem is new.
v A phone number where you can be reached.
Chapter 1. Introducing WebSphere Voice Response support 3

v A feeling for the business impact or severity of the problem you are
reporting. Use the information in “Determining problem severity” on page
23 as a guide.
Chapter 2. Analyzing the problem
To solve any problem you might be having with WebSphere Voice Response,
start by trying to identify the cause. First, catalog the symptoms. Then
determine the state of the system; for example, calculate how much disk space
is available, what levels of software are installed, and how the operating
environment has been defined.
When you have collected all the necessary information, use Chapter 3,
“Solving WebSphere Voice Response problems,” on page 31 to identify and
solve the problem. If you then need to consult an IBM specialist, your analysis
will hopefully provide all the required information. In addition, before you
call support, make sure you have fully documented the problem and assigned
it a severity level.
This chapter is organized as follows:

v “Cataloging the symptoms”
v “Describing the state of the system” on page 6
v “Before you call IBM Support” on page 15
v “Running hardware diagnostic procedures” on page 25
v “Diagnosing telephony line errors” on page 28
Cataloging the symptoms

Different problems have different symptoms. In general, however, you will
usually notice a WebSphere Voice Response problem because of an error
message, because something does not function correctly, or both.
Try to isolate all events that seem to be symptoms of the problem. It is

extremely helpful if you can identify the precise situation in which the
problem occurs, the frequency with which it occurs, and the sequence in
which the symptoms occur. Details of an error from the error log and traces of
system activity can be particularly useful for determining the cause of a
problem, and can speed up its resolution.
Have any system conditions changed?
When WebSphere Voice Response has been running smoothly and suddenly
develops problem, often the reason is because an operating condition has
changed. To determine whether operating conditions have changed at your
location, ask yourself the following:
v Have you recently installed a new release of software?

v Have you recently replaced or added hardware?
v Have you recently changed the telephony configuration on either the
WebSphere Voice Response system or the switch?
v If the problem is with a voice application, is it an application that has
recently been put into production?
v If the problem is with the 3270 host connection, has the network
configuration changed, or have any of the SNA profiles been changed?
Which component is failing?
Some types of problems do not involve a failing component. But for problems
that do, it is important to find out which part of WebSphere Voice Response is
not working correctly.
Because hardware and software problems are handled by different IBM

Support organizations, first determine whether the symptoms seem to indicate
a hardware–related or a software–related problem. Then, try to identify more
precisely where the problem is. If one of the symptoms is an error message,
for example, the number of the error message can help you identify where the
problem originates. Or, if the problem is with a voice application, the
component of the application that is failing can help identify what part of the
software is not processing correctly.
Describing the state of the system

Once you have cataloged the symptoms, check the state of your WebSphere
Voice Response system; sometimes just doing this can reveal what is causing a
problem.
This section contains instructions for the following:

v Describing the system by using dtProblem
v Determining how much disk space is free
v Determining the maximum number of user processes the system can start
v Checking how much page space has been defined for the system to use
v Determining how many buffers are defined for system use
v Determining what levels of software have been installed
v Reviewing the error log
v Copying the error log to tape or diskette
Describing the system by using dtProblem
You can gather information about your system by using dtProblem. IBM
Support can then use that information to debug the problems that you are
experiencing.
It is best to use dtProblem immediately after the problem occurs. It gathers
information about:
v The system configuration
v The level and type of products that are installed
v Users
To run dtProblem, log on to the user ID from which you run WebSphere Voice
Response.
Now type:
dtProblem outputdir
where outputdir is the directory into which you want to put the output file.
(dtProblem usually needs less than 4 MB of space on the output directory.)
On the output directory is a file called dtProblem.tar.Z, ready for

transmission to IBM Support. You can examine the file contents yourself. To
unpack the file, and extract the resulting files into the directory
dtProblem_dir, use the command:
zcat dtProblem.tar.Z | tar -xvf -
Collecting Java and VoiceXML environment specific information

If you have installed the Java and VoiceXML environment, you can gather
information about the Java and VoiceXML environment in your system by
using dtbeProblem. IBM Support can then use that information to debug the
problems that you are experiencing.
If the problem can be easily re-created, collect a trace. To do this:

1. Stop the Java and VoiceXML environment environment by running the
dtjstop command followed by the dtjshost -exit command.
2. Stop the trcserv process by running the trcserv -k command.
3. Create or edit the file /var/dirTalk/DTBE/native/aix/trcserv.ini and
add the following line:
trace.mode=3
4. Edit /var/dirTalk/DTBE/dtj.ini, and add the line trace.option=9
5. Restart the Java and VoiceXML environment environment by running the
command dtjshost followed by the dtjstart command. Trace is generated
in files:
/var/dirTalk/DTBE/dtj_logs/wvrtrace.*
6. Recreate the problem. The trace files are collected in dtbeProblem, there is
no need to send them to IBM separately. The trace.mode=3 line will force
the trcserv process to output trace all of the time. So after capturing the
problem you should revert to the original setting (or delete the file).
Chapter 2. Analyzing the problem 7

If support have requested a combined WebSphere Voice Response and Java
and VoiceXML environment trace you need to set trace.mode=5 in
trcserv.ini to redirect the Java and VoiceXML environment trace to a
WebSphere Voice Response AIX trace.
If you do this, to capture the trace output you need to run a standard
WebSphere Voice Response trace (by specifying, for example, trace -a -1
-L32000000 -T1000000). To format a WebSphere Voice Response trace with
Java and VoiceXML environment trace included, run this command:
print_trace | dtjtrcfmt > output file
7. Send output file to IBM support.
To run dtbeProblem automatically when a specified error is logged to the

VRBE log (.log) files or the WebSphere Voice Response trace (.trc) files, use the
dtjlogmon script. Refer to the section “dtjlogmon script” in the WebSphere
Voice Response: Deploying and Managing VoiceXML and Java Applications
manual for details.
To collect dtbeProblem data:

1. Logon as the WebSphere Voice Response userid (usually dtuser).
2. Type dtbeProblem /tmp to collect the dtbeProblem data. The file
/tmp/dtbeProblem... tar.Z is the output from dtbeProblem. Send
/tmp/dtbeProblem... tar.Z file to IBM support.
Determining how much disk space is free
WebSphere Voice Response includes both static and dynamic files. By default,
the static files are stored in the /usr file system. The dynamic files are stored
in the /home file system.
As part of the installation process, the dynamic files might have been moved
from /home to a different file system. Whichever file system is used, however,
if the directory in which the dynamic files are stored starts to run out of
space, WebSphere Voice Response might not perform as expected.
Checking disk space
The following instructions describe how to determine how much disk space is
available in each WebSphere Voice Response file system. For a complete
description of the WebSphere Voice Response file systems and information on
how to manage the files, see WebSphere Voice Response for AIX: Managing and
Monitoring the System. For information on moving the dynamic files to a
different file system, see WebSphere Voice Response for AIX: Installation.
To check the amount of free disk space, use the AIX operating system:
1. If no AIX window is open, open one by selecting an area on the screen
background and clicking AIX Login.
2. Log onto the WebSphere Voice Response AIX account (usually dtuser).
The system displays the User Login menu.
3. Type 2 and press Enter.
The system displays the system prompt, which is usually a dollar sign ($).
4. Type df and press Enter.
The system lists all file systems and the amount of space (in KB) that is
free in each. The name of the file system is on the far right.
Using SMIT to increase the size of your file system:

1. Log on to AIX as root.
2. To use SMIT, type smitty and press Enter:
The system displays the System Management menu.
From menus that follow, click:
v —> System Storage Management (Physical and Logical Storage)
v —> File systems
v —> Add / change / show / delete file systems
v —> Journaled file systems
v —> Change / show characteristics of a journaled file system
The system displays a list of file system names.
3. Select the name of the file system that you want to change:
The system displays the change / show characteristics of a journaled file
system menu
4. Change the number in the SIZE of file system field to the size you
want for the file system.
5. Click the Do button.
Determining the maximum number of user processes the system can
start
The number of user processes that WebSphere Voice Response can start
determines how much processing WebSphere Voice Response can perform. If
the system is extremely busy and it cannot start enough processes to handle
all the requests for service by component programs, the result may be a
problem. For example, WebSphere Voice Response might not initialize.
Checking user processes
To check the number of user processes defined for your system, you can use
either an AIX command or SMIT.
Using AIX:

2. Type the following command and press Enter:
lsattr -E -l sys0
The character l in the command is a lowercase L (for logical device), not the
number 1.
The number next to maxuproc is the value to which the parameter is set.
3. To change the maximum number of user processes, type the following
command and press Enter:
chdev -l sys0 -a maxuproc=###
where ### is the maximum number of processes. For example, the
command to reset the maximum number of processes to 150 looks like
this:
chdev -l sys0 -a maxuproc=150
The character l in the command is a lowercase L (for logical device), not the
number 1.
The system changes the upper limit on user processes to the number you
indicate, and stores the changed parameter in the database.
Using SMIT:
1. To use SMIT, type smitty and press Enter:
The system displays the System Management Menu.
2. Click System Environments.
The system displays the System Environments Menu.
3. Click Change/Show Characteristics of Operating System.
The system displays a list of characteristics. Note the number next to
Maximum Number of Processes Allowed Per User.
To calculate the number of user processes WebSphere Voice Response requires,

and instructions on how to increase the maximum number of user processes,
see WebSphere Voice Response for AIX: Installation.
Using this information
To calculate the number of user processes WebSphere Voice Response requires,

and instructions on how to increase the maximum number of user processes,
see WebSphere Voice Response for AIX: Installation.
Checking how much page space has been defined
To move information into and out of active memory, WebSphere Voice
Response uses space on the hard disk, defined as page space. When WebSphere
Voice Response does not have enough page space, the system might not be
able to process information correctly.
Checking page space
To check the amount of page space that is defined for WebSphere Voice
Response to use, you can use either an AIX command or SMIT.
2. Determining the size of a logical partition: The unit of measure for page
space is logical partitions. All logical partitions are the same size (usually 2
or 4 MB). To determine the size of each logical partition, type the
following command and press Enter:
lslv hd6
The system displays a list of characteristics in columns. The first column
starts with the identification of the logical volume (in this example, hd6).
The second column contains an entry labeled PP size. The number next to
this is the size of a logical partition.
3. Determining the existing page space: Type the following command and
press Enter:
lsps -a
The system displays the number of paging spaces defined and the size of
each page space logical volume.
4. 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.
Increasing page space
You can increase the page space in 2 ways:

v Add logical partitions to the existing page space
v Create a new page space
Adding logical partitions:
Type the following command and press Enter:

chps -s ## @@@
where ## is the number of logical partitions to add and @@@ identifies the
logical volume. For example,
chps -s 9 hd6
The system adds 9 logical partitions to the logical volume hd6.

Creating new paging space:
Type the following command and press Enter:

mkps -s ## -n -a volume_group_name
where ## is the number of logical partitions for the new page space. For
example,
mkps -s 10 -n -a volume_group_name
The system creates a new page space containing 10 logical partitions on the
logical volume named by volume_group_name.
WebSphere Voice Response requires page space equal to at least twice the
amount of RAM in the system. For optimum performance, and assuming you
have enough disk space available, define 256 MB of page space.
For instructions on how to increase the amount of page space, see WebSphere
Voice Response for AIX: Installation.
Determining how many buffers are defined for system use
WebSphere Voice Response uses buffers to hold the components of voice
applications and also to pass data between processes. Some of the buffers,
which are used to hold voice segments, are allocated in cache memory. If the
system uses all the available buffers, processing degrades.
Checking on buffers
Use the System Monitor and the DTmon command (see WebSphere Voice
Response for AIX: Managing and Monitoring the System) to find out how many
buffers WebSphere Voice Response is configured to use. If the system does not
have a suitable number of buffers available, it might not be able to process
correctly. Alternatively, use the following procedure:
1. Log on to WebSphere Voice Response.
2. Displaying the number of buffers: Click Configuration
3. Click System Configuration
4. Click Browse
The system displays the names of the WebSphere Voice Response
parameter groups.
5. Click Application Server Interface (ASI).
The system lists the parameters in the ASI parameter group, showing the
current value for each parameter.
6. Look at the value next to Maximum Cached Buffers. This number
indicates how many buffers are allocated for the voice cache memory. To
calculate what the value of Maximum Cached Buffers should be, see
WebSphere Voice Response for AIX: General Information and Planning.
7. Look at the value next to Number of Pool Buffers. This number indicates
the total number of buffers that the system can use (including the number
in cache).
Each buffer requires 4 KB of random access memory (RAM). Set the value of
Number of Pool Buffers to the highest value possible, minus the value of
Maximum Cached Buffers.
For instructions on how to reset the value of a system parameter, see

WebSphere Voice Response for AIX: Configuring the System.
Determining what level of software is installed
Use the AIX command lslpp to find out what versions of the software and
telephony hardware microcode are installed on your WebSphere Voice
Response system. If you call IBM Support, the support representative will ask
you for this information.
You can determine the level of software you have installed by using the lslpp
command. For example, to see what WebSphere Voice Response filesets are
installed, login to AIX as root, type the following command, then press Enter:
lslpp -l dirTalk*
The installed WebSphere Voice Response filesets are displayed.

Reviewing the error log
WebSphere Voice Response automatically maintains a file in which it logs all
errors that occur while the system is running. The file is called errorlog, and
it is stored in $OAM_LOG_PATH.
For more information:

v About the error log, see WebSphere Voice Response for AIX: Configuring the
System.
v About interpreting the messages, see Chapter 5, “Introducing the
WebSphere Voice Response alarm messages,” on page 107.
v About the messages themselves, see Appendix B, “WebSphere Voice
Response messages identified by number,” on page 173.
Review the contents of the error log by using the AIX editor.

1. Logging on: If no AIX window is open, open one by selecting an area on
the screen background and clicking AIX Login.
2. Log onto the WebSphere Voice Response AIX account (usually dtuser) .
The system displays the system prompt, which is usually a dollar sign ($).
4. Changing to the correct directory: Type the following command and press
Enter:
cd $OAM_LOG_PATH
5. To check whether the error log is present, type ls errorlog and press
Enter.
The system lists the error log file that is in the directory.
6. Opening the error log: Type the following command press Enter:
view errorlog
The system displays the contents of the error log. The view command
allows you look at the file, but not to make changes to it.
7. Use view to review the contents of the file.
8. Closing the file: Press Shift ZZ
The system closes the file and redisplays the system prompt.
Copying the error log to tape or diskette
Sometimes you need to copy the error log to tape or diskette. For example,
the IBM support representative might ask for a copy of the file to help
determine the cause of a problem.
To copy the error log, use the AIX tar command. You need the name of the
device (tape drive or diskette drive) to which the file will be written.
If the error log file is very large, or if there are many error log files, you
should compress the files (by using the AIX compress command) if you are
going to save them on a low density medium such as a diskette.
1. Logging on: If no AIX window is open, open one by selecting an area on
the screen background and clicking AIX Login.
2. Log onto the WebSphere Voice Response AIX account (usually dtuser).
The system displays the system prompt - usually a dollar sign ($).
4. Changing to the correct directory: Type the following command and press
Enter:
cd $OAM_LOG_PATH
5. To check on the correct name of the file, type ls err* and press Enter.
The system lists the error logs that are in the directory. The current file is
called errorlog. The history files have a date appended to the file name.
6. Copying the file: Type the following command, replacing the xxx with the
device name and the ######## with the name of the error log file that you
want to copy.
tar -cvf/dev/xxx ########
The system copies the file to the tape or diskette that is loaded in the
device specified by the command.
Before you call IBM Support

IBM Support can provide assistance if you encounter any problems. Before
you call, however, make sure you have cataloged the symptoms, know the
state of the system, and have documented the problem. Also be prepared to
assign a severity level to the problem. You can then give the support
representative all the necessary information.
To help in diagnosing a problem, IBM Support might ask you to provide trace
information. There are two types of trace that can be produced from a
WebSphere Voice Response system:
v System-level trace
v Binary trace
Capturing a system-level trace
It is sometimes useful to run a system-level trace, to get details of what is
happening to the signaling bits on the telephone channels.
If there is a lot of activity on the system, the system trace will be large and
more difficult to interpret. If possible, take the trace on a system with low
activity (if you can reproduce the problem there).
Before taking a trace, check that there is enough free space in the file system
for the trace file. The default trace file size is 1280 KB, but this can be
increased, for example to over 10 MB. The trace file is stored in the
/var/adm/ras directory, which must have enough space for the size of trace
file required. The default value is big enough for a short trace, but 8 MB is a
typical value for a system that has a lot of activity.
If you need to take a longer trace, perhaps to investigate an infrequently

occurring problem, you must allocate a larger amount of space to the trace
file. For example, 50 minutes of trace information for a system at moderate
load might require over 40 MB.
1. To log on before starting the trace: If no AIX window is open, open one
by selecting an area on the screen background and clicking AIX Login.
2. Log onto the WebSphere Voice Response AIX account (usually as dtuser).

The system displays the system prompt - usually a dollar sign ($).
4. To start the trace: Type the following command and press Enter:
trace -1 -L 8000000 -T 1000000
v For a short trace, the -L and -T options can be omitted.
v The -L option gives the trace file size in bytes. The default is 1280 KB. In
the example above it is set to 8 MB.
v The -T option gives the size of the trace file buffer in memory in bytes.
The default is 128 KB, and the maximum size is 1 MB, as used in the
example above.
The system displays the > prompt.
Note: By default, the trace command creates the trace file in the directory
/var/adm/ras, with a filename of trcfile.1. You can use the additional
option -o to change the location and filename of the trace file. For
example:
trace -1 -L8000000 -T1000000 -o /home/dtuser/tracefile
Remember to ensure that there is sufficient space in whichever location

you decide to use.
5. Perform the action on WebSphere Voice Response that causes the problem
you want to trace.
6. To stop the trace: Wait a short time to allow the actions to complete.
The system displays the > prompt.
Note: Although the default is for the trace command to run in an

interactive mode, for long traces you might find it useful to run tracing in
the background, thereby returning the command line prompt immediately
and allowing you to perform other tasks. To do this, use the -a option on
the trace command, as in the following example:
trace -1 -a -L8000000 -T1000000
In order to stop the trace using this asynchronous mode, enter the
command trcstop -1.
7. Type the following command and press Enter:
q
By default, the system writes the unformatted trace into a file in the
/var/adm/ras directory. These files are named trcfile.*, and they are in
binary format.
8. To save the trace in a file: Type the following command and press Enter:
print_trace > <filename>
The system writes the formatted trace, in ASCII format, into the file name
given in the command. The command assumes that you are using the
default file trcfile.1 in /var/adm/ras. If you created a different trace file in
/home/dtuser as described in step 4 above, then the new syntax would
be:
print_trace /home/dtuser/tracefile > formatted.trace
What files and information do I need to send to IBM Support if I have
taken a system trace?
Send the file or files that have been formatted by using the
print_trace command (see the procedure described in, “Capturing a
system-level trace” on page 15). These files are in ASCII format, so
take care to keep this format if they are transferred to another type of
operating system.
Alternatively, you might be asked to send the files that were created
in the /var/adm/ras directory. These files are named trcfile.*. Look
at the time and date of the files to determine which file (or files) you
want. These files are in binary format, so take care to keep this format
if you transfer them to another type of operating system.
You should include details of the version of WebSphere Voice
Response you are using, and details of any patches or PTFs that have
been applied.
Also include a description of the actions WebSphere Voice Response
was performing when you took the trace, and what happened when
the problem occurred. For example, you might say:
v Called into channel 5 (number = 408 555 1234)
v Tried to transfer to a busy phone (number = 408 555 5678)
v Application hung up after 30 seconds because it did not detect that
the phone was busy, and timed out
If there is more than one failure mode, try to take a separate trace for
each mode.
For more information about taking system traces see AIX: Technical
Reference: Base Operating System and Extensions Volume 2.
Using WebSphere Voice Response AIX system trace event

Ids
Table 1 on page 18 lists the AIX system trace event ID that WebSphere Voice
Response uses. If you want to trace only specific events, there is a -j option on
the AIX trace command which, when used with the event IDs listed below,
allows you to restrict tracing to only those events.

Table 1. AIX system trace event IDs used by WebSphere Voice Response
Event Subsystem
ID ID Location Users ID string
34F 0 User Servers
450 0 Kernel Device driver
451 0 Kernel Signaling driver
456 0 User CHP
456 1 User CHP manager
456 2 User Custom Server API CA_LIB
456 3 User VP library VPLIB
456 4 User Prompt manager PROMPTM
456 5 User Cache CACHEM
456 6 User State table STATEM
457 0 User OAM
457 1 User SDI
457 2 User ERROR_ENROLL ERROR_ENROLL
457 3 User Buffer pool BufPool
457 4 User Hardware configuration ADAPTUPDT
458 0 User Performance — file system PLT
458 1 User Performance — databases MBS
459 0 User Signaling interface SIGLIB
459 1 User SMSI signaling process
459 2 User ACL signaling process
459 3 User Signaling daemon SL_DAEMON
459 4 User ISDN signaling process ISDN
Capturing binary trace

The binary trace runs by default at a very low level, so that it can capture any
basic first-failure data if a problem arises. The binary tracing system combines
trace data into one contiguous store, and is used for tracing Java and
VoiceXML components as well as some custom servers. As described below,
two separate configuration files are used to set the default tracing level and
the method by which the system stores the trace data. All the trace data is
stored in binary format into a memory buffer, and also to disk in a managed
list of files, which are limited to a configurable maximum amount of disk
space. Once this space is used, the oldest file is discarded and reused.
Configuring the trace
You can either use dtjit to configure the trace (refer to the help for dtjit for
more information) or follow the instructions below to configure the trace
manually.
To set the tracing level for the Java and VoiceXML environment, edit the file
$DTJ_HOME/dtj.ini to include the line
trace.option=<trace_level>
In the absence of this value being set, a default trace level of 2 is used.
After you have updated the file, you must restart the Java and VoiceXML
environment environment for the changes to take effect.
To set the tracing level for any other code (such as custom servers), edit the
file $DTJ_HOME/native/aix/trcserv.ini to include the line
trace.option=<trace_level>
You do not have to restart any programs after changing trcserv.ini, although
you do need to run the command trcserv -ry. This resets the trace server so
that it picks up any new settings.
In both the above cases, <trace level> is an integer that can be set to the
following values:
0 All tracing off
1 All tracing off
2 Core trace points and errors only. It is recommended that trace level 2 is
used for the first pass of tracing.
3 As for 2, plus important trace points and function entry/exit only (minor
trace points and trace points with data excluded)
4 As for 2, plus important trace points (loop and CPU intensive trace points
excluded)
5 As for 2, plus important trace points, no exclusions
6 As for 5, plus warnings
7 As for 5, plus function entry/exit
8 All trace on (loop and CPU intensive trace points excluded)
9 All trace on
There are other useful parameters that can be set (in the trcserv.ini file only) to
alter the way in which the tracing works.

v To change the way in which trace data is stored include the line:
trace.mode=<mode_number>
where mode_number can take the following values:

1 All trace data is written to memory buffer only. This is the default value
and is recommended for the first pass of tracing.
3 Trace data is written to memory, but continuously written out to disk in
chunks.
5 All trace data is written to the AIX system trace instead. For this mode,
the raw binary data is written to the AIX trace buffer instead of the
binary trace system's own files. Because of this, you need to run an AIX
system trace to capture the trace data, and then use the command
print_trace | dtjtrcfmt > <filename> to format the trace correctly.
v To alter the amount of disk space to be used for storing binary trace files
include the line:
trace.max.disk=<number_of_kilobytes>
When this limit is reached, the oldest file is discarded and reused. Each file
is typically 5 MB in size and has a naming convention of
wvrtrace.<num>.trc, where <num> is an integer between one and the
number of files that make up the maximum disk limit (the default is 100
MB). Trace files are stored in the directory $DTJ_HOME/dtj_logs.
The trace server memory buffer can be flushed to disk on demand by using
trcserv -f command. This causes any trace data that was not previously
written in the current memory buffer to be written to disk.
Collecting the trace
The process for collecting binary trace is as follows:

1. To start the trace: Either edit the appropriate configuration files (as
described above) to have trace run automatically, or use the following
command:
dtjtrcmod <trace_level>
This command sets the trace level dynamically, without requiring a restart
of any program that uses this tracing system.
The trace mode should also be set to 3 to enable continuous data output to
be collected. Depending on how busy the system is or the level of trace
that is set, there may be a large amount of trace data created, and as a
result the maximum disk space parameter may need to be increased to
allow enough data to be captured. Also, you should monitor the extra
CPU load that the system will experience if it is running at the highest
trace level (9).
2. To stop the trace: Enter the command dtjtrcmod 0. This turns off all
binary tracing.
3. Enter the command trcserv -f to flush any remaining trace data from
memory to disk
4. To format the trace data: In the trace output directory
($DTJ_HOME/dtj_logs), enter the command
dtjtrcfmt wvrtrace.<n>.trc > <output filename>
or
dtjtrcfmt -o <output_filename> wvrtrace.<n>.trc
The output file contains the trace output in UTF-8 readable form.
5. Sending data to IBM Support: The dtbeProblem tool collects all the
binary trace files. However, if you have been specifically asked to run a
binary trace, then collect all the binary trace files that have been created,
and send them unformatted together with the dtbeProblem output data.
Documenting your problem
You should document any problem you might have with WebSphere Voice
Response, for the following reasons:
1. The more information you can provide to the support center, the more
easily and quickly IBM can help you.
2. Accumulating information about a problem can help you track it, and will
also be helpful if a similar problem ever occurs.
Capture as much of the relevant information as you can. “Copying the error
log to tape or diskette” on page 14 describes how to capture the contents of
the WebSphere Voice Response error log. Other means of capturing
information include the call detail record log, the DTstatus.out file, and
NetView® for AIX. WebSphere Voice Response for AIX: Configuring the System
describes how WebSphere Voice Response captures and stores information
that can assist you in documenting problems.
For more information on the DTstatus.out file, the call detail record log, see
Core file
The existence of a recent core file indicates that the system is having a
problem. Although you cannot solve the problem by yourself, IBM Support
will need to know that the core file exists. The support representative can

describe to you the steps you need to take.
Core file size
Some processes in WebSphere Voice Response set the SA_FULLDUMP flag so

that the entire user data area is dumped when a core file is created. The
default limit for a core dump is 1 MB (2,000 blocks), and because the user
data area is typically larger than this, you must increase this limit so that core
files are not truncated. Set this limit to 10 MB, because although core files are
infrequent, it is important that all the information is captured for problem
determination.
You can modify this limit by changing /etc/security/limits when

WebSphere Voice Response is installed, or you can simply check that it is
already set to a reasonably large value. The field you need to check or change
is core. Add the following to /etc/security/limits, if it is not already there:
dtuser:
core = 20480
Looking for a recent core file
Most WebSphere Voice Response processes run with $VAEBIN as the current
directory. If such a process encounters an exception, it creates a core file in
$VAEBIN. Only the root user can write to $VAEBIN, so during WebSphere
Voice Response installation the directory /var/adm/ras/dirTalk, and the
symbolic link $VAEBIN/core are created. Using the $VAEBIN/core symbolic link,
and the /var/adm/ras/dirTalk directory, any WebSphere Voice Response
process can write a core file without root privilege. The $VAEBIN/core
symbolic link is used by IBM Support to debug the problem that caused the
core dump, so do not remove it.
When a core file is created by a WebSphere Voice Response process, it is

written to the /var/adm/ras/dirTalk directory and has the name core.owner,
where owner is the name of the process that created the core file.
There are two ways to determine whether a core file exists. The first and most
direct way is to:
1. Login to AIX, using any valid userid.
2. Change directory to /var/adm/ras/dirTalk.
3. List the files by using the command: ls -l core.*
If files exist that match the file pattern core.* and they have a recent date
and time stamp, call IBM Support.
The second way uses the AIX error logging facility to notify the WebSphere
Voice Response system administrator when a WebSphere Voice Response
process creates a core file. This is achieved by creating a shell script called
coredump_notify_exit.sh in dtuser’s home directory. If this file exists and can
be run, it is called each time a core file is created. You can use this script to
send mail to the system administrator. A sample shell script called
coredump_notify_exit.sample is provided in the /usr/lpp/dirTalk/sw/
samples directory.
vaeinit.log and vaeinit.nox.log
Information that you see on the screen when you start WebSphere Voice
Response (either by logging on to the userid dtuser, or from inittab when
your system is restarted) is kept in either vaeinit.log or vaeinit.nox.log.
Each time you start WebSphere Voice Response the previous log file is
overwritten. Only one file is kept, so you see either vaeinit.log or
vaeinit.nox.log in the home directory.
This log might be useful if errors occur when you are using a terminal where
scroll bars are not available, or during system startup when the output
normally goes to a console display that is running in graphics mode, and
errors scroll off the screen before you can note all the information. To see any
messages you have missed, you can view the log file.
The vaeinit.log file is created when you start WebSphere Voice Response
from the WebSphere Voice Response userid (usually dtuser).
The vaeinit.nox.log file is created when you start WebSphere Voice Response
from inittab when your system is recycled. This file is also created when
WebSphere Voice Response starts automatically after a power failure.
Determining problem severity
If you cannot solve the problem yourself, IBM Support assigns a severity level
to the problem. The possible severity levels are 1 (most severe) through to 4
(least severe).

Severity 1 Critical business impact
This indicates that you cannot use WebSphere Voice

Response, resulting in a critical impact on operations. This
condition requires an immediate solution.
For example, if WebSphere Voice Response does not answer

the telephone correctly, or voice applications cannot run
because the 3270 servers cannot use the sessions configured
for them, you have a severity 1 problem.
Severity 2 Significant business impact
This indicates that WebSphere Voice Response is usable but is

severely limited.
For example, if you can run only a small subset of your voice
applications, you have a severity 2 problem
Severity 3 Some business impact
This indicates that WebSphere Voice Response is usable with

less significant features (not critical to operations)
unavailable.
For example, if voice applications are running correctly, but

the system is not collecting all the report statistics, you have a
severity 3 problem.
Severity 4 Minimal business impact
This indicates that the problem has little impact on operations

or that you have found a temporary work-around.
If the severity of the problem changes, you can increase or decrease it by

calling the IBM support center.
Reporting a problem with a C-language program
If you have a problem with a custom server that you developed, use custom
server tracing to determine whether the problem is in your code. Custom
server trace is described in WebSphere Voice Response for AIX: Custom Servers.
If you have a problem with a signaling process that you developed, use
signaling interface tracing to determine whether the problem is in your code.
Signaling interface trace is described in WebSphere Voice Response for AIX:
Programming for the Signaling Interface.
If you have a problem with a program that uses WebSphere Voice Response
C-language subroutines, and you need help from IBM Support, you must
provide a test case that contains no copyrighted code. This applies to:
v Custom servers that use the CA_ subroutines
v Signaling processes that use the sl_ subroutines
If all your code is copyrighted, send the binary files only. They are sufficient
in most situations to isolate the cause of the problem. Alternatively, create a
test case that contains no copyrighted code.
Running hardware diagnostic procedures

WebSphere Voice Response for AIX supports one type of PCI adapter board:
The IBM Quad Digital Trunk Telephony PCI Adapter (DTTA) The adapter
performs voice processing functions and interfaces with the T1 or E1
telephony trunks.
For more information about either the DTTA, refer to the IBM Quad Digital
Trunk Telephony PCI Adapter (DTTA): Installation and User's Guide.
Adapter feature codes
The Feature Codes for the DTTA are 6312 and 6313. The 6313 includes a short
Blind Swap Cassette (BSC) which is required for installing the DTTA in
machines that use the BSC (for example, the pSeries 650-6M2). The only
additional hardware that may be required specifically for the DTTA are the
H.100 cables. The DTTA uses standard RJ45 cables for connection to telephony
networks. The RJ45 cables are not provided by IBM but can be bought
separately.
DTTA device driver
The device driver for the DTTA is included with WebSphere Voice Response.
Before installing the DTTA adapters, you should ensure that WebSphere Voice
Response is installed.
After installing WebSphere Voice Response, and the DTTA device drivers, you
need to run a machine power cycle, reboot, or run the cfgmgr command to
configure the adapters.
To check that the DTTA is installed, type the following command:

lsdev -C | grep rpq
This will display a list of the installed adapters and associated device drivers.
Here is an example of what you would see if four adapters were installed:
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
The first column of the listing shows the name of the item.
rpqioadapter_number is a Quad Digital Trunk Telephony PCI Adapter (DTTA)
and ddrpqioadapter_number is the associated device driver (where
adapter_number is the number of the adapter).
The second column shows whether the adapter and device driver have been
correctly configured. Both should be shown as Available (the Defined state
means that the adapter has not been detected or configured, or that the device
driver has not been configured correctly).
The third column gives the slot position for the adapter. Refer to the manual
for your pSeries system for the meanings of this field.
The fourth column describes the item listed in the row.
For WebSphere Voice Response to recognize the DTTA adapters, and to

determine whether WebSphere Voice Response is running as T1 or E1, the
dt_setowner command has to be issued for each adapter (see WebSphere Voice
Response for AIX: Installation for more information).
To check that conditions are correct to start WebSphere Voice Response, type
the command:
lsdev -C | grep dtline
AIX will display something like this:

dtline0 Available 1H-08-01 DTTA E1
dtline1 Available 1V-08-01 DTTA E1
dtline2 Available 1Z-08-01 DTTA E1
dtline3 Available 1D-08-01 DTTA E1
where there is one dtlineadapter_number device for each adapter and

associated device driver (and where adapter_number is the same as in
rpqioadapter_number for the adapter).
To determine the positioning of the physical adapters within a machine, run

rpqtest diagnostics (for more information, see “Running diagnostics on the
DTTA” on page 27). The orange LED at the bottom of the card will flash at
the start of running the diagnostics. This is the easiest way of finding out in
which slot an adapter is located in. Diagnostics also need to be run after
installing your adapters and before starting WebSphere Voice Response.
If you do not see your DTTA as being available, or if you have been
experiencing problems that indicate a possible adapter fault, see “Diagnosing
unrecognized DTTAs on PCI systems.”
Ensure that if you have more than one adapter installed, there is an H.100
cable connecting all adapters together. If you have more than two adapters
installed, the H.100 termination jumper should be moved for those adapters
which are not at the end of the cable.
Diagnosing unrecognized DTTAs on PCI systems
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 (for
more information see WebSphere Voice Response for AIX: Installation).
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
this may take a few minutes.

3. To test an adapter once, type the following command, then 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.
Diagnosing telephony line errors

This section describes telephony line errors and their typical causes.
What causes telephony line errors?
Loss of signal (LOS, SL)
This is most likely caused by a break in the wiring between a DTTA
on your WebSphere Voice Response system and the network or the
switch. Check all connections and cables, replacing cables where
necessary. If the problem persists, contact your network service
provider.
BPV (bipolar violation), ER (error rate)
High error rates can be caused by a noisy line. Check all connections
and cables, replacing cables where necessary. If the problem persists,
contact your network service provider.
Other errors
If communication problems exist between WebSphere Voice Response
and the network, check your configuration, because the most likely
cause is a mismatch in configuration; for example, a line protocol.
Diagnosing telephony line errors on the DTTA
For DTTA systems, if there is a trunk alarm error, the hardware alarms can be
displayed by using the _alarms utility from the $VAE/tools directory. To use
this utility, type the following command, and press Enter:
$VAE/tools/DTTA_alarms
The utility displays a continuous stream of hardware alarms. These alarms are
also shown in the WebSphere Voice Response System Monitor, after a short
delay.
Note: The DTTA does not have LEDs on the backplate to indicate trunk
alarms.
Using debugrec to record input and output

The debugrec voice recording tool considerably simplifies what is required to
take a diagnostic recording of voice input and output on specific telephony
channels or an adapter trace. debugrec provides additional functionality
compared with the debugmon utility described in WebSphere Voice Response for
AIX: Voice over IP using Session Initiation Protocol.
debugrec is shipped as a single executable in the /usr/lpp/dirTalk/devives/

dtqa_bin directory.
debugrec can operate in one of three modes:

v Continuous recording to a stereo .wav file, with voice input recorded on the
right-hand channel and voice output recorded on the left-hand channel.
v Continuous recording of voice input and output to separate vrec* files.
v Circular recording to a 25 second capacity buffer on the adapter.
Syntax
debugrec trunk channel [option]
where:
trunk The WebSphere Voice Response trunk number in the range 1 to 16 (as
displayed on the WebSphere Voice Response System Monitor).
Mandatory
channel
The WebSphere Voice Response channel number (as displayed on the
WebSphere Voice Response System Monitor). Mandatory
option One of the following optional parameters or omitted (default):
-v debugmon option v compatibility. Recording is continuous (until

stopped) to three (DTTA) or four (DTNA) files in the /tmp/
directory. File names are of the form vrec*.
-a debugmon options 8 and 9 compatibility. Recording is done to a
25 second capacity circular buffer on the adapter. Adapter DSP
commands and status are also recorded. Files with the name
format trace_rec* are created in the /tmp/ directory.
By default (no option), recording is continuous (until stopped) and a stereo

8KHz A-law or µ-law .wav file is created, where the left channel is 'line out'
(what WebSphere Voice Response is playing to the line) and the right channel
is 'line in' (what WebSphere Voice Response is receiving from the line). The
file name used for the recording is /tmp/vrec_line_stereo.wav. All other
parameters required by the tool such as the adapter type and trunk type are
obtained automatically from WebSphere Voice Response internal configuration
information.
Usage
For most problems, the default option (stereo .wav file) will be all that is
required as it simply records what WebSphere Voice Response is sending to
and receiving from the specified telephony channel. In some cases, IBM
support may request that the -a option is used to record additional internal
information which will hopefully allow IBM to diagnose the cause of a
problem.
Chapter 3. Solving WebSphere Voice Response problems
This chapter describes how to solve some common problems.
The problems are divided into four categories:

v “Problems found during installation or system startup” on page 33 are
problems that occur when you start the WebSphere Voice Response
hardware or software, either for the first time, or when you have recycled
the system.
v “Network problems” on page 44 are problems that occur when WebSphere
Voice Response tries to access the telephone or data communications
network.
v “Problems found while running voice applications” on page 59 are
problems that occur when voice applications do not run correctly, either in
test or production.
v “Performance and other general problems” on page 83 are general
performance problems and other problems that do not fit into one of the
other categories.
How to use this information

Each problem is identified by the main symptom. For example, one of the
problems is identified as “Welcome window does not display”. When you
look at the problem description, you see an explanation of the situation in
which the problem occurs and the actions you should try in order to resolve
it.
Before you try any of the actions, always check the WebSphere Voice
Response error log for alarm messages. First, use the information provided in
the message and the information given in Appendix B, “WebSphere Voice
Response messages identified by number,” on page 173 to try to resolve the
problem. If the problem persists, read through all of the suggested actions
before you take further action—some of them might not apply to your
situation.
Many of the actions are described in terms of using the WebSphere Voice
Response Welcome window, its menus and sub-windows:
v The Pack Configuration and System Configuration options on the
Configuration menu are used to check and set system parameter values
that affect the operation of the system.

Attention: If you use System Configuration to change telephony-related
parameters, do not later use Pack Configuration to reset the
Country/Region, Trunk Parameters, Switch Type, or Line Signaling because
this resets the telephony configuration.
v The System Monitor on the Operations menu is used:
– To display systems, trunk and channel status
– To display alarms and the messages about them
– To control trunks and channels while the system is running
v The State Tables option on the Development menu is used to check the
details of voice applications.
Other options are also mentioned in this chapter. For a brief overview of the
whole interface, see WebSphere Voice Response for AIX: General Information and
Planning. For information about the mechanics of the user interface, see
WebSphere Voice Response for AIX: Installation.
You do not have to use the windows if you do not have access to a suitable
display. You can use the ASCII console from an ASCII terminal that is
connected, either locally or remotely, to your system. Type AC on the
command line while WebSphere Voice Response is running. You can then
perform many of the system management actions that the Welcome Window
Configuration, Administration, and Operations menus offer.
Alternatively, you can use an SNMP-compliant system management

application to monitor and control your system. For more information about
use of the ASCII console and remote system management, see WebSphere Voice
Response for AIX: Managing and Monitoring the System.
Note: You cannot perform the Development actions remotely. You must use
the Development menu on the Welcome Window for these.
Each problem also includes one or more references to WebSphere Voice

Response books. The referenced information provides additional information
that can help you avoid the problem in the future.
When nothing works

If you try all the suggestions and still cannot solve the problem, try recycling
WebSphere Voice Response. Sometimes shutting the system down and starting
it up again causes temporary problems to disappear.
If nothing works, call IBM support. Ensure that you read Chapter 2,
“Analyzing the problem,” on page 5 first and collect any information you
might not already have available. Then you are ready to talk to the support
representative.
Problems found during installation or system startup
This section describes what to do when you find one of the following
installation or system startup problems:
v “WebSphere Voice Response software does not start to initialize”
v “Fileset consistency warnings are displayed on startup” on page 35
v “Welcome window does not display” on page 36
v “DB2 error SQL6048N is generated when attempting to start WebSphere
Voice Response” on page 37
v “WebSphere Voice Response reports "SQL1042C with SQLSTATE=58004"
error” on page 38
v “The startup of WebSphere Voice Response takes longer than normal and
generates errors” on page 38
v “The windows on an Xstation are displayed in the wrong font” on page 39
v “restoreDT returns with an error from the "tar -xhv -f" command” on page
39
v “BrooktroutFax Adapter TR114 failure” on page 39
v “Failed to start Voice Response node - error_id 21004” on page 40
v “The ricdiag utility fails following a mksysb restore” on page 40
v “Error occurs when logging onto WebSphere Voice Response GUI after
running mksysb” on page 41
v “DTSNMPD_START fails to start after upgrading AIX” on page 41
v “Running vae.setenv produces DB2 errors” on page 42
v “Database error occurs when trying to connect to the WebSphere Voice
Response database” on page 42
v “License Enrollment errors during WebSphere Voice Response Version 6.1
migration” on page 42
v “DB2 errors during WebSphere Voice Response Version 6.1 installation” on
page 43
v “WebSphere Voice Response Version 6.1 migration errors related to DB2
software” on page 44
v “Configuring SS7 in a WebSphere Voice Response Single System Image” on
page 44
WebSphere Voice Response software does not start to initialize
When the WebSphere Voice Response hardware powers up and initializes
correctly but the software does not start, check the following:
Did you use the vae.setuser tool to create the WebSphere Voice Response
account ID?
WebSphere Voice Response starts initializing automatically when you
log on to the account defined as the WebSphere Voice Response AIX
Chapter 3. Solving WebSphere Voice Response problems 33

account. If you try to start the software any other way, it might not
start (and even if it does, it will not run correctly).
Create the account (with all of the correct privileges and environment
definitions) by using the tool called vae.setuser. WebSphere Voice
Response for AIX: Installation describes how to use vae.setuser.
Do you have enough disk space free?
To enable it to start, WebSphere Voice Response requires enough free
space in both of the file systems it uses (/home and /usr).. To find out
whether you have enough free space, log on as root, type df and press
Enter. Check the amount of free space displayed. If you do not have
enough, clean up the file systems and recover space. Check the
/home/dirTalk/current_dir/oamlog directory for any old error log and
oamtrace files that you no longer need and can delete to recover
space.
If you have spare capacity on your hard disk, you can increase the
size of some of you file systems. See “Using SMIT to increase the size
of your file system:” on page 9.
Is the AIX maxuproc parameter set high enough?
AIX includes a parameter that defines the ceiling on how many
processes can start. If the value of the parameter is too low,
WebSphere Voice Response cannot start the processes it needs. If the
parameter is set to a high-enough value but a large number of
processes are already running, WebSphere Voice Response cannot
start.
WebSphere Voice Response for AIX: Installation introduces user processes
and describes how to find out and change the number allowed (if
necessary). If the value of the maxuproc parameter is already high
enough, type ps and press Enter to determine whether an unusually
large number of processes are already running.
Is the tasklist.data file missing or is there more than one instance of it?
WebSphere Voice Response starts the processes listed in the
tasklist.data file. If the file is missing, the system cannot start.
The tasklist.data file is located in the directory identified by the value
of the $SYS_DIR variable in the profile for the WebSphere Voice
Response AIX account ID. WebSphere Voice Response for AIX: Installation
contains instructions for checking on the tasklist.data file.
Are the WebSphere Voice Response parameter files corrupted?
The WebSphere Voice Response configuration is defined by the values
of the WebSphere Voice Response system parameters. The
configuration includes initialization information (such as the status to
assign to trunks at system initialization). Without the parameter file,
the system cannot start.
The WebSphere Voice Response system parameter file is called
rd.data and is stored in the directory identified by the value of
$SYSPARM_DIR as defined in the profile for the WebSphere Voice
Response AIX account ID. WebSphere Voice Response for AIX: Installation
introduces the system parameter file and describes how to restore it if
it is corrupted.
Has the ISDN custom server started?
You cannot run two ISDN custom servers at the same time; you must
stop the first ISDN custom server before you can start another.
If you try to run two ISDN custom servers, the following message
appears in the WebSphere Voice Response log:
29203 ISDN signaling process initialization failure
The message description field contains “es_init() failed”.
Another reason why the ISDN custom server can fail to start is the
abnormal termination of the ISDNDL4 process. In this situation, even
if you stop the ISDN custom server, you might not be able to restart it
without first shutting down and restarting WebSphere Voice Response.
Are you using an SSI cluster?
If you are, ensure that:
v The clients and servers are configured correctly
v The network is available
v The database and any voice servers are up and running
v The voice and custom server filesystems of the correct server are
NFS-mounted on the clients
For information on the above, see the chapter on creating and
managing a single system image in WebSphere Voice Response for AIX:
Configuring the System.
Fileset consistency warnings are displayed on startup
The fileset consistency checker runs at WebSphere Voice Response startup and
checks whether all the WebSphere Voice Response filesets on your system are
at a consistent level. This check does not affect the WebSphere Voice Response
startup. The system displays the results in the DTstatus.out window.
Are the WebSphere Voice Response filesets at inconsistent levels?
If the WebSphere Voice Response filesets are not consistent, the system
displays a warning message. For example, if the fileset
dirTalk.ISDN.Euro-ISDN is out of step with the level of base
WebSphere Voice Response that is installed, the system would display
a message similar to the following:

Checking fileset consistency
*** WARNING ****************************************************
dirTalk.ISDN.Euro-ISDN is at level 2.2.2.3020 - the matching
level is 2.2.2.3027
****************************************************************
If the system displays a message of this type, upgrade the inconsistent

fileset to the required level.
Are any of the files being checked corrupt?
If any files that contain fileset information have been corrupted, the
system displays a message stating that not all consistency checks were
performed. For example:
Checking fileset consistency
Only 2 of 3 consistency checks performed
If the system displays a message of this type, contact IBM support.

This is not an urgent problem and your system will not be affected.
Welcome window does not display
The WebSphere Voice Response software might start initializing correctly, but
when the time comes to display the Welcome window, nothing happens. You
can recognize whether the initialization process has started by looking at the
status window. When the system is starting, the status window displays a
running list of processes as the system starts them. When all the processes are
started, WebSphere Voice Response displays the Welcome window.
When the Welcome window does not display, check the following:
Is the tasklist.data file corrupted or is there more than one instance?
tasklist.data file. If one or more of the entries is missing, the system
might start initializing but not complete the process. The tasklist.data
file is located in the directory that is identified by the value of the
$SYS_DIR variable in the profile for the WebSphere Voice Response
AIX account ID.
WebSphere Voice Response for AIX: Installation contains instructions for
checking the tasklist.data file.
Does the status window show the X error ‘Cannot open display’?
When you start WebSphere Voice Response from an Xstation or
remote console, you must provide the system with the name of your
display. If you are logging in remotely, you must also give WebSphere
Voice Response permission to access (open) the display on the remote
console. (Working at an Xstation that boots off a remote console is the
same as working at the remote console.) There are three possibilities:
v You did not give WebSphere Voice Response the required
permission.
v You provided the name of a nonexistent display.
v You did not provide a display name.
To give WebSphere Voice Response the required permission, ensure
you are logged on to your account on the remote console by typing
pwd and pressing Enter. Check the directory name to ensure it is on
the remote console. Then, type xhost + and press Enter. Restart
WebSphere Voice Response.
To provide a correct display name when you are sure that you
granted permission, log off AIX and log back on to restart WebSphere
Voice Response. Make sure you provide the name of the display you
are using.
Does the status window look normal?
When the status window displays no errors, you might have provided
the name of a valid display but not the display on which you are
working. Because the display name you provided identifies an
existing display, WebSphere Voice Response starts the processes in the
tasklist.data file. You must shut down the running processes and
restart the system. WebSphere Voice Response for AIX: Installation
contains instructions for shutting down running processes and
correcting an incorrect display name.
For more information on display names, see WebSphere Voice Response
for AIX: Installation.
DB2 error SQL6048N is generated when attempting to start WebSphere
Voice Response
If message SQL6048N is reported when starting WebSphere Voice Response,
this indicates that DB2 is not running. However, on issuing a db2start
command, you might see the following errors displayed, indicating that DB2
has failed to start:
exec(): 0509-036 Cannot load program db2stop because of the following errors:
0509-130 Symbol resolution failed for /usr/lib/threads/libc.a?aio_64.o
because:
0509-136 Symbol kaio_rdwr64 (number 0) is not exported from
dependent module /unix.
0509-136 Symbol listio64 (number 1) is not exported from
0509-136 Symbol acancel64 (number 2) is not exported from
0509-136 Symbol iosuspend64 (number 3) is not exported from
0509-136 Symbol aio_nwait (number 4) is not exported from
0509-130 Symbol resolution failed for
/usr/opt/db2_08_01/lib64/libdb2e.a?shr_64.o? because:
0509-136 Symbol aio_nwait (number 506) is not exported from
dependent module /usr/lib/threads/libc.a?aio_64.o?.
0509-150 Dependent module libdb2e.a(shr_64.o) could not be loaded.

0509-026 System error: Cannot run a file that does not have a valid
format.
0509-192 Examine .loader section symbols with the
’dump -Tv’ command.
This is a known DB2 problem that occurs when Kernelised Asynchronous I/O
(KAIO) is not enabled. To enable KAIO, use the following steps:
1. Log in as root
2. Enter smitty aio
3. Select Change/Show Characteristics of Asynchronous I/O
4. Set the STATE to be configured at system restart field to available
5. Reboot AIX.
WebSphere Voice Response reports "SQL1042C with SQLSTATE=58004"
error
When logging in using the account that you use to run WebSphere Voice
Response (the default is dtuser), the following error is returned:
SQL1042C with SQLSTATE=58004
The same DB2 error is also found in DTstatus.out. When an attempt is made
to start DB2 with db2start, the same error is returned.
The problem is caused by an incorrect setup of the instance for dtdb23in

during installation, or migration. As a result, the instance fails to start.
To resolve the problem, reset the instance with FencedID (the name of the user
under which fenced user defined functions (UDFs) and fenced stored
procedures will run.) To do this:
1. Log in as root
2. Type instance cd /opt/IBM/db2/V9.5/instance (or location where DB2 was
installed )
3. Type ./db2iupdt -u dtdb23in -e dtdb23in
4. Log in as dtuser (or equivalent) or dtdb23in
5. Start DB2 using db2start
The startup of WebSphere Voice Response takes longer than normal and
generates errors
Occasionally, the startup of WebSphere Voice Response can take longer than
normal, and messages are displayed in DTstatus.out log file, similar to:
killing old DT process nnnnn pid xxxxx
This situation arises if you attempt to start WebSphere Voice Response before
a previous shutdown has completed. You should always wait for shutdown to
complete before restarting WebSphere Voice Response. Under normal
operation, you can check whether shutdown has finished by entering the
command:
$ ps -ef | grep NODEM
If the NODEM process is still running, do not try to restart WebSphere Voice
Response.
The windows on an Xstation are displayed in the wrong font
When the WebSphere Voice Response software starts correctly but the
Welcome window is displayed on an Xstation in the wrong font, check the
following:
Has the Xstation login file been modified?
When you are using Xstations to run WebSphere Voice Response, the
system console includes a file that the X server uses to find the
directory in which the fonts that are used to display the WebSphere
Voice Response windows are stored. The default font path identifies
incorrect fonts. Unless the font path is modified, none of the
WebSphere Voice Response windows will display correctly on an
Xstation, even though they display correctly on the system console.
Your Xstation documentation tells you how to ensure that the X server
can locate the correct fonts.
restoreDT returns with an error from the "tar -xhv -f" command
When migrating from WebSphere Voice Response Version 4.2 to WebSphere
Voice Response Version 6.1 the restoreDT command can fail with the
following error message:
DATA UPGRADE FAILED: Error During tar -xhv -f .admclass_table admclass_table rd.data...
(more archive files)
This failure occurs even though the system has enough free space and all file
permissions are set correctly.
The reason for the failure is that the wrong version of saveDT from
WebSphere Voice Response Version 4.2 was used to create the application and
configuration backup.
Use the version of saveDT dated August 2009 which includes all updates for
migration to WebSphere Voice Response Version 6.1 to create the migration
archive and then run restoreDT again. To obtain the latest version of saveDT
before migrating to WebSphere Voice Response Version 6.1, please update
WebSphere Voice Response Version 6.1 to at least fix level 4.2.0.499 and use
the installed version of the saveDT script.
BrooktroutFax Adapter TR114 failure
The BrooktroutFax adapter TR114 fails with a DTstatus.out entry as follows:

Running /usr/lpp/dirTalk/sw/fax/bin/tsSCTSASSIGN_BTFAX
(takes approximately 30s per fax card)...
tsSCTSASSIGN_BTFAX: exiting with rc: RC_RESET_FAILED
The RC_RESET_FAILED error can indicate a conflict with the AIX script
install_assistant in inittab. Such a conflict can prevent the BrooktroutFax
adapter initialization code faxinit from running during inittab execution.
To resolve the problem, ensure that install_assistant is removed from

inittab, and reboot the system.
Failed to start Voice Response node - error_id 21004
The WebSphere Voice Response VRBE interface can fail to start with:
v A message in DTstatus.out:
Starting the HostManager...
The process ID of the HostManager is XXXXX
The HostManager failed to start after 60s.
Please check for any error messages.
v An error entry of error_id 21004 in errorlog:
DTBE Failed to start Websphere Voice Response node.
sequence = xxx csec = xx error_id = 21004
Even though all of the configured WebSphere Voice Response Java nodes
(defined in default.cff) are local, Java RMI still uses the TCP/IP stack for
communication and hostname resolution. This problem can occur if the
system is set up to use DNS for hostname resolution and either the DNS
server is not responding, or the DNS resolves to the wrong hostname or IP
address.
If the system is configured to use DNS, check the file /etc/resolv.conf for
the list of DNS servers. If any of these DNS servers, especially the first one on
the list, are not responding, change the TCP/IP setup to use a working DNS
server.
The ricdiag utility fails following a mksysb restore
After restoring a system, using the mksysb command, the ricdiag diagnostic
utility can fail, returning an error code ric0428. This is because, after running
mksysb, the file dgr0d31014d.00.00 is missing from /usr/lib/microcode. This
file is used by the ricdiag command and must be present.
To resolve the problem, either copy the file from another WebSphere Voice
Response system, or reinstall the DTTA driver from /usr/lpp/dirTalk/
devices/dtqa_bin directory. When the file has been restored, check that
ownership is set to bin:bin, and permissions are set to -r-xr-xr-x, then
restart WebSphere Voice Response.
Error occurs when logging onto WebSphere Voice Response GUI after
running mksysb
After running mksysb to load an environment from another host and
attempting to log on to the WebSphere Voice Response GUI, using the admin
user ID and password, the following error message is displayed:
Database server unavailable.
Access to database including HELP system is not possible at this time.
After loading mksysb from another host, the user was prompted with
information about the hostname change. The user selected the option n from
the fsupdate prompt, but no further action was taken to correct the extra
hostname in the database. Detailed messages can be found in the
DTstatus.out file (in /home/dirTalk/current_dir/oamlog/DTstatus.out).
However, the messages are not visible from the status window as it has rolled
over:
<DTstatus.out info>
ssistatus: new hostname is a Standalone system ssistatus 137:
ERROR Extra standalone hosts are defined in DB2 -
HOSTNAME
---------------------------
old hostname
1 record(s) selected.
ssistatus 154: ERROR Extra hosts cause unpredicatable results
ssistatus 155: ERROR Shutdown WebSphere Voice Response and run fsupdate
fscheck 188: Filesystem check ok
</end of message in DTstatus.out>
In the errorlog file, error_id 5312 is logged several times.
To correct this problem:

1. Shutdown WebSphere Voice Response using the DT_shutdown command.
2. Run fsupdate and select Press enter and they will be deleted now.
DTSNMPD_START fails to start after upgrading AIX
After upgrading to a new version of AIX, the WebSphere Voice Response for
AIX shell script DTSNMPD_START does not run correctly. Error 26003 is
generated in the errorlog and the following error is seen in the DTstatus.out
output file:
dtuser:/usr/lpp/dirTalk/sw/bin> ./DTSNMPD_START
dtuser:/usr/lpp/dirTalk/sw/bin> dtsnmpd: ---- dtsnmpd control
information ----
dtsnmpd: alarm array size = 200
dtsnmpd: traps = disabled
dtsnmpd: summary traps = disabled
dtsnmpd: alarm per trap = inactive (20)
dtsnmpd: alarm interval = inactive (5 secs)
dtsnmpd: --------------------------------------

dtsnmpd: text2obj(directTalk6000) failed:
dtsnmpd: error DTAInitializeObjects failed text2obj(agent.name)
dtsnmpd: shutdown complete at 08/26 09:29:31
The problem is caused by the MIB definitions that existed previously being
overwritten by the AIX upgrade.
Run the DTsnmpd.cfg shell script again to update the MIB definition file
/etc/mibs.def. Refer to “Installing SNMP support” in the WebSphere Voice
Response for AIX: Installation for instructions on how to do this.
Running vae.setenv produces DB2 errors
After migrating from WebSphere Voice Response Version 4.2 to Version 6.1, if
you are logged in as root and run the script /usr/lpp/dirTalk/tools/
vae.setenv, the following DB2 error is generated:
SQL1090C The release number of the pre-compiled application program or utility is not valid.
This is because files from /home/dtdb23in/sqllib are still linked to the library
files from the previous version of DB2.
You do not need to run vae.setenv before running DTdatabase -m. DTdatabase
-m alone will migrate the application database and also correctly link the
library files from DB2 Version 9.5 used by WebSphere Voice Response Version
6.1
Database error occurs when trying to connect to the WebSphere Voice
Response database
After applying a DB2 fix pack upgrade, or upgrading DB2 from one version
to the next, the connection to the WebSphere Voice Response database no
longer functions.
Perform actions specified in the DB2 upgrade notes and then run the
command vae.setuser after an upgrade to re-establish the DB2 connection and
set the permissions.
License Enrollment errors during WebSphere Voice Response Version 6.1
migration
When the administrator attempts to enroll the WebSphere Voice Response 6.1
licenses, the License User Management (LUM) tool i4blt returns one of the
following errors:
v CLN-83 “Incorrect target in password”
v CLN-84 “Invalid password or vendor incorrect”
The cause of the problem is that WebSphere Voice Response 4.2 has the
pre-requisite License User Management (LUM) of (ifor_ls.base.cli 5.2.0.10).
During the WebSphere Voice Response migration to 6.1, a newer version of
LUM (ifor_ls.base.cli 6.1.0.22) is required. The previous LUM database or
setup may not be converted completely correctly.
To resolve the problem, complete the following steps to remove the existing
LUM database before performing a clean setup for WebSphere Voice Response
using LUM:
1. Stop the LUM process by running the following command:
i4cfg -stop
2. Remove LUM database files by running the following commands:
cd /usr/opt/ifor/ls/conf
rm *.dat
rm *.log
rm *.idx
The System Administrator can now follow the instructions in the section
“Configuring your system for License Use Management” in WebSphere Voice
Response for AIX: Installation .
DB2 errors during WebSphere Voice Response Version 6.1 installation
Multiple DB2 DBI1087E errors are reported in smit.log during the WebSphere
Voice Response 6.1 (6.1.0.0) base installation. The installp may have reported
SUCCESS on all the filesets, but the following database setup (DTdatabase)
may fail.
DBI1087 errors are logged in the smit.log file for DB2 links in /usr/include
and /usr/lib directories. The error messages are like:
DBI1087E An attempt to create the link /usr/include/asn.h failed.
...
DBI1087E An attempt to create the link /usr/lib/libdb2.a failed.
The cause of the problem is that previously WebSphere Voice Response 4.2
was installed, and the installation program for WebSphere Voice Response
Version 6.1 failed to create links for DB2 V9.5.
Both /usr/include and /usr/lib directories still have the DB2 links
connecting to files from DB2 V8.1. For example, the problem system will have
the command output like:
cd /usr/include
ls -l asn.h
lrwxrwxrwx 1 root system <date> asn.h -> /usr/opt/db2_08_01/include64/asn.h
To resolve the problem:

1. Login to the system as root.
2. Remove the links for DB2 V8.1 using the command:
/usr/opt/db2_08_01/cfg/db2rmln
3. Create the links for DB2 V9.5 using the command:

/opt/IBM/db2/V9.5/cfg/db2ln
4. Check the links:
# ls -l /usr/lib/libdb2.a
It should now link to /opt/IBM/db2/V9.5/lib64/libdb2.a
# ls -l /usr/include/asn.h
It should now link to /opt/IBM/V9.5/include/asn.h.

5. Reboot the system then continue the installation.
WebSphere Voice Response Version 6.1 migration errors related to DB2
software
WebSphere Voice Response 6.1 installation program (smitty) does not
recognize a valid DB2 V9.5 installation when DB2 V9.5 already installed on
the system but at a level lower than 9.5.0.4. The installp may have reported
SUCCESS on all the filesets, but the following database setup (DTdatabase)
may fail.

1. Verify the DB2 level by running the command:
/usr/local/bin/db2ls
WebSphere Voice Response 6.1 requires a level of 9.5.0.4 or higher.

2. If DB2 V9.5 is back level, do NOT install another copy of DB2 at a
different install directory, instead upgrade the existing instance to DB2
V9.5 Fix Pack 4, downloadable from:
https://www.ibm.com/support/docview.wss?uid=swg24023213
3. Do not remove the DB2 V8 before running the DTdatabase -m command to
perform the migration. After a successful migration, DB2 V8 can then be
removed if required.
Configuring SS7 in a WebSphere Voice Response Single System Image
When using the SS7_MAINT program to configure a machine to WebSphere
Voice Response which is connected to an SSI server, error messages relating to
the importing of the SS7_D7 custom server may be generated. These can be
ignored as they refer only to the fact that the custom server is already loaded.
Network problems
This section describes what to do when you find one of the following network
problems:
v “WebSphere Voice Response does not initiate outbound calls” on page 45
v “WebSphere Voice Response does not answer the phone” on page 46
v “WebSphere Voice Response receives no information from the exchange
data link” on page 50
v “WebSphere Voice Response answers the phone with “technical
difficulties”” on page 51
v “Telephone channel is hung” on page 52
v “No SNMP traps are being sent” on page 53
v “WebSphere Voice Response cannot access a remote 3270 host” on page 54
v “3270 session is permanently disabled” on page 55
v “3270 emulation does not work” on page 55
v “Telephony connection does not synchronize” on page 55
v “Cannot enable trunk” on page 56
v “DB2 does not start if the machine name is changed after DB2 is installed”
on page 58
v “Resolving error_id 26001” on page 58
v Removed for V6.1: TCP problem on AIX affecting WVR
WebSphere Voice Response does not initiate outbound calls
When WebSphere Voice Response does not initiate outbound calls, check the
following:
Is at least one trunk in service?
Before WebSphere Voice Response can place a call, at least one of the
trunk lines that connects the telephone network must have the status
InService. WebSphere Voice Response for AIX: Configuring the System
describes how to activate a trunk. Either use this information to reset
the value of the Operating Status parameter that controls trunk
initialization status and recycle WebSphere Voice Response (shut it
down and restart it), or use the System Monitor to activate one trunk
dynamically.
Is at least one channel configured as Outgoing or Bothway?
Unless at least one channel on an InService trunk is configured to
process outgoing calls, WebSphere Voice Response cannot place an
outgoing call. Check the Direction setting for each trunk, using Pack
Configuration.
If you are using the MakeCall action, set SV178
(System : Call : Permitted channel groups system variable)
correctly. See MakeCall in WebSphere Voice Response for AIX: Application
Development using State Tables.
Is the switch configured for outbound calls?
The switch must be configured to allow outbound calls on the channel
or channels on which WebSphere Voice Response is trying to use to
make calls. Check the Direction setting for each trunk, by using Pack
Configuration.

Are you using a signaling process that you developed yourself?
Have you configured WebSphere Voice Response to use your
signaling process? (See WebSphere Voice Response for AIX: Configuring
the System for more information.)
Check that your signaling process is receiving the
SL_CALL_SETUP_REQ primitive.
Check that your signaling process is returning the
SL_CALL_SETUP_CNF primitive to WebSphere Voice Response, and
that the sl_send_confirm() subroutine is returning successfully.
Use signaling interface tracing the see the primitive sent by
WebSphere Voice Response to your signaling process. For information
on tracing signaling interfaces, see WebSphere Voice Response for AIX:
WebSphere Voice Response does not answer the phone
When WebSphere Voice Response does not answer the telephone, check the
following:
Is at least one trunk in service?
Before WebSphere Voice Response can answer the telephone, at least
one of the trunk lines that connects the adapter to the telephone
network must have the status InService. WebSphere Voice Response for
AIX: Configuring the System describes how to activate a trunk. Either
use this information to reset the value of the Operating Status
parameter that controls trunk initialization status and recycle
WebSphere Voice Response (shut it down and restart it), or use the
System Monitor to activate one trunk dynamically.
Is at least one channel configured as Incoming or Bothway?
Unless at least one channel on an InService trunk is configured to
accept incoming calls, WebSphere Voice Response cannot respond to
an incoming call. Check the Direction setting for each trunk, using
Pack Configuration.
Is the Ringing On Minimum parameter short enough?
In some telephone systems, internal and external calls are signalled
differently. For example, an external call might be a one-second ring,
while an internal call is two 0.5-second rings. If the value of Ringing
On Minimum is more than 0.5 seconds, WebSphere Voice Response
cannot recognize the internal ring as a signal to answer the telephone.
To correct this:
1. Find out which channel group is assigned to the trunk (by using
Pack Configuration is the quickest method).
2. Find out which Signaling Type is specified in the Channel Group
definition (by using System Configuration).
3. Reset the value of the Ringing On Minimum parameter in the
Signaling Type definition (by using System Configuration). Use
Help on the Ringing On Minimum window if you need an
explanation of the parameter.
Are enough channel processes available to answer calls?
When the telephone rings, WebSphere Voice Response allocates a
previously started channel process to handle the incoming call. If it
cannot allocate a channel process, it cannot answer the telephone.
There are several reasons why this could happen:
v The value of the maxuproc parameter, which controls the maximum
number of AIX processes, is too low. The maxuproc parameter must
be greater than the sum of the number of telephony channels
defined and the value of extra channel processes. See WebSphere
Voice Response for AIX: Installation for more information.
v The software component that creates channel processes (called
CHP) is not running.
v The value of the parameter that controls how many extra channel
processes WebSphere Voice Response can create is too low.
Channel processes are AIX user processes. Use the information in the
section “WebSphere Voice Response software does not start to
initialize” on page 33 to check on the maximum number of processes
that the system can run (maxuproc) and increase the value if
necessary.
To find out whether the process called CHP is running, type ps |
grep CHP and press Enter. If the process is not listed, recycle
WebSphere Voice Response (shut it down and restart it). If the process
still does not start, use the information provided in “WebSphere Voice
Response software does not start to initialize” on page 33 to ensure
the entry is present in the tasklist.data file.
WebSphere Voice Response normally starts as many channel processes
as there are channels, plus the number defined by the value of the
WebSphere Voice Response Extra Channel Process parameter in the
Application Server Interface parameter group. If you need to start
more channel processes, use the information provided in WebSphere
Voice Response for AIX: Configuring the System to reset the parameter.
Is Incoming_Call present?
The WebSphere Voice Response software includes a state table called
Incoming_Call, which issues an AnswerCall action, then invokes the
voice application. If Incoming_Call has been deleted or incorrectly
modified, the call is not handled correctly.
Use the information supplied in WebSphere Voice Response for AIX:
Application Development using State Tables, to list all state tables and to

determine whether Incoming_Call has been changed. If Incoming_Call
has been changed or is missing, use the information provided in
WebSphere Voice Response for AIX: Application Development using State
Tables to import the state table. Incoming_Call is in a file called
/usr/lpp/dirTalk/sw/samples/BaseData.imp.
For more information on how WebSphere Voice Response answers the
telephone, see WebSphere Voice Response for AIX: Configuring the System.
Have you installed an application to answer the call?
WebSphere Voice Response must be able to find an application profile
that is identified with either the dialed number identification digits
passed by the switch, the information that identifies the channel on
which the call signals are being transmitted, or the value of the
WebSphere Voice Response Default Application Profile ID parameter.
For a complete explanation of how WebSphere Voice Response
answers the telephone, see WebSphere Voice Response for AIX:
Use the information provided in WebSphere Voice Response for AIX:
Configuring the System to list all existing application profiles. If there is
no qualifying profile in the WebSphere Voice Response database, use
the information in WebSphere Voice Response for AIX: Configuring the
System to create one.
Are there continuous ISDN Layer 3 data link activated/deactivated white
alarms?
If you see the messages 29405—ISDN Layer 3 primary data link
activated and 29406—ISDN Layer 3 primary data link deactivated:
On an E1 system
There is a cable or connection problem between WebSphere Voice
Response and the switch.
On a T1 system
A cabling fault might have occurred, or the trunk framing mode or
line coding for the ISDN signaling trunk is set incorrectly. Check that:
v The switch is configured for Extended SuperFrame (ESF) with line
coding set to B8ZS for signaling trunks
v The trunk from the switch is not configured for CAS
v The CSU used supports ESF and B8ZS, and that it is configured
correctly
v WebSphere Voice Response is correctly configured
If you used Pack Configuration to configure the trunk, the parameters
should be correct.
Are you using ISDN with Non Facility Associated Signaling (NFAS)?
Check that you specified the correct trunk ids when you configured
the system.
If you are using ISDN NFAS, your Service Provider must tell you
which trunk ids to use. If you use the wrong ones, incoming calls are
not answered by WebSphere Voice Response; they are be cleared by
WebSphere Voice Response with a cause code of Channel
Unacceptable.
Use the ISDN_MONITOR tool to check the line signaling, see “The
channel ID information element” on page 100.
Do channels remain blocked when trunk is enabled and channels are put in
service?
If you are not using Non Facility Associated Signaling (NFAS), this
problem is likely to be caused by one of the following:
v The switch is taking too long to send the RESTART ACKnowledge
messages to WebSphere Voice Response (if the Send RESTART on
Channel Enable parameter is set to YES in the ISDN signaling
section of the System Configuration).
You can check this by selecting “channels out of service” and then
“channels in service”. The channels change to the IDLE state if the
ISDN Layer 2 link to the switch is working.
v ISDN Layer 2 from the switch is not responding.
If the switch ISDN Layer 2 does not respond after 90 seconds, a
message is logged that tells you the timer expired on the Primary
ISDN Layer 3 Data Link. Use the ISDN_MONITOR tool or an ISDN
Primary Rate Line monitor to monitor what the switch is doing.
The switch should send out Synchronous Asynchronous Balanced
Message Extended (SABME) Layer 2 frames to establish the link.
These must be Command frames, not Response frames. If these
frames appear on the ISDN_MONITOR trace as “Rsp” frames, the
switch is set up in “Network” mode. Change the mode to
“User-Side” because WebSphere Voice Response supports only this
mode.
You might also get these problems if you are using NFAS on T1
systems.
However, there is another possible cause of this problem, which can
show up as one or more non-signaling trunks having all their
channels in BLOCKED state while some other trunks are in IDLE
state.
If the ISDN trunk id does not match the trunk id configured in the
switch, the RESTART ACKnowledge messages that contain the trunk

id are incorrect, and the channels change to the IDLE state. This id (in
the range 0 through 31) is provided by the Service Provider.
Check that the trunk ids match those that are defined on the switch.
Use the ISDN_MONITOR or an ISDN Primary rate monitor to see
whether RESTART ACKnowledge messages are returned with the
correct trunk id values in the Channel Information Element (IE).
Check that your signaling process is still running. Message 32011 in
the error log indicates that a signaling process has terminated.
Check that your signaling process is receiving the call from the
network.
Check that your signaling process is sending the
SL_CALL_SETUP_IND primitive to WebSphere Voice Response, and
that the sl_send_indication() subroutine is returning successfully.
Use signaling interface tracing to see the primitive sent to your
signaling process by WebSphere Voice Response. For information on
tracing signaling interfaces, see WebSphere Voice Response for AIX:
WebSphere Voice Response receives no information from the exchange
data link
Particular switches transmit call information out of band using a serial line
called the exchange data link. When WebSphere Voice Response is directly
connected to such a switch and is not receiving the call information, check the
following:
Is the physical connection complete?
The connection between the pSeries computer and the switch is an
RS232 line, either with or without modems. Ensure that the line is still
connected correctly at both ends. WebSphere Voice Response for AIX:
Installation describes how to connect the exchange data link line.
Has the AIX configuration been changed?
Information on the exchange data link carries an identifier to identify
the channel to which the data pertains. Check that the system
parameters that define the exchange data link are correct. Use the
information provided in WebSphere Voice Response for AIX: Installation
to redefine the exchange data link device to AIX.
Has the WebSphere Voice Response telephony configuration been
changed?
The WebSphere Voice Response telephony configuration includes a
number of parameters that define the exchange data link connection
and the format of the information WebSphere Voice Response expects
from the switch. Use the information provided in WebSphere Voice
Response for AIX: Configuring the System to correct the WebSphere Voice
Response exchange data link configuration.
Are the exchange data link channels identified correctly?
Each channel on the exchange data link carries information about one
signaling channel on the trunk line. Information identifying the
exchange data link channel is part of the WebSphere Voice Response
telephony configuration. If the channels are not identified correctly,
WebSphere Voice Response cannot receive the exchange data link
information. Use the information provided in WebSphere Voice Response
for AIX: Configuring the System to correct the exchange data link line
identifier that correlates with each WebSphere Voice Response
channel.
Check that your signaling process is still running.
Check that your signaling process is receiving the call from the
network.
Check that your signaling process is sending the
SL_CALL_SETUP_IND primitive to WebSphere Voice Response, and
that the sl_send_indication() subroutine is returning successfully.
Check that the sl_call_data_st structure in the SL_CALL_SETUP_IND
primitive has been filled in correctly.
Use signaling interface tracing to the see the primitive sent by your
signaling process to WebSphere Voice Response. For information on
WebSphere Voice Response answers the phone with “technical
difficulties”
When WebSphere Voice Response answers the telephone and immediately
plays the “technical difficulties” message, check the following:
Have you installed an application to answer the call?
When WebSphere Voice Response is configured to go off-hook to
receive called number information from the switch, and no application
has been installed to answer the call, the system plays the technical
difficulties message to the caller. Use the information supplied in
“WebSphere Voice Response does not answer the phone” on page 46
to check on the presence of an installed application. Check the value

of the EDL Call Information Before Off Hook parameter that is in the
Application Server Interface parameter group, to see whether your
system is configured to go off-hook in order to receive dialed number
information.
Is the voice application state table invalid?
When a state table is invalid, WebSphere Voice Response plays the
technical difficulties message. A state table might be invalid only
when it is in memory, or the state table that is stored on disk might
also be invalid.
Application Development using State Tables to display the state table, and
validate it. The validation process checks the state table stored on
disk. If the copy of the state table on disk is invalid, use the
information that is also provided in the book to correct it. If the
invalid state table is in memory only, shut down and restart
Telephone channel is hung
When a telephone channel remains in an off-hook state after the caller has
hung up, check the following:
Does the voice application state table terminate with a CloseEverything or
TerminateCall action?
Voice applications require a state to indicate that the channel is no
longer in use. CloseEverything releases all resources allocated to the
application, including hanging up the telephone line and closing host
sessions. TerminateCall does not terminate state table processing, but
it does disconnect the current caller. Ensure that the state table uses
one of these actions to hang up the phone line.
For information about CloseEverything and TerminateCall, see
Tables.
Have you stopped and restarted the channel?
Sometimes stopping and restarting the channel can resolve temporary
problems. Use the information provided in WebSphere Voice Response
for AIX: Configuring the System to disable the channel then activate it
again.
Check that your signaling process is still running. Message 32011 in
the error log indicates that a signaling process has terminated.
The usual cause of this problem is that your signaling process has not
cleared a call correctly. Message 32012 in the error log indicates that
your signaling process has ignored an SL_CALL_ABORT_REQ
primitive. This is an error in your signaling process. See the
explanation of message 32012 in Appendix B, “WebSphere Voice
Response messages identified by number,” on page 173 and the
description of the SL_CALL_ABORT_REQ primitive in WebSphere
Voice Response for AIX: Programming for the Signaling Interface.
Use signaling interface tracing to see the primitive sent to your
signaling process by WebSphere Voice Response. For information on
No SNMP traps are being sent
When WebSphere Voice Response is part of a network, it can send either all
alarms or only the most serious messages to an SNMP compliant manager, for
example NetView for AIX. Alarms are listed in Appendix B; the most serious
are those marked as alertable. By using WebSphere Voice Response's own
SNMP sub-agent, you can send traps to an SNMP-compliant manager.
If some, but not all, messages are being received at the management station
check the following:
Is WebSphere Voice Response configured to make alarms alertable?
To send all alarms, not only the serious ones, set the system
parameter Alarms - Make All Alertable in the Application Server
Interface group to “Yes”. Also, you can change individual alarm
messages to be alertable or not, as described in WebSphere Voice
When using the WebSphere Voice Response sub-agent

Is the WebSphere Voice Response SNMP sub-agent configured correctly?
For the WebSphere Voice Response sub-agent to send traps with
WebSphere Voice Response alarms to NetView for AIX, it must be
running and configured to send traps and not to use trap-directed
polling. In addition, the AIX SNMP daemon, snmpd, must be
configured to send traps to the NetView for AIX system. For more
information, see WebSphere Voice Response for AIX: Configuring the
System .
Is NetView for AIX configured correctly?
For NetView for AIX to recognize and forward traps from WebSphere
Voice Response alarm messages, it must be configured to do so. In
Event Configuration in NetView for AIX, the enterprise specific trap
“1000001” (decimal) must be configured for enterprise
“directTalk6000”. In addition, NetView for AIX must be configured to

start its daemons that interface to AIX NetView Service Point. For
more information, see the NetView Entry for AIX: User's Guide.
WebSphere Voice Response cannot access a remote 3270 host
When WebSphere Voice Response is part of a data communications network,
and you know that the network is operating correctly but WebSphere Voice
Response is having difficulty accessing a remote 3270 host, check the
following:
For WebSphere Voice Response to communicate with a remote 3270 host, SNA
must be installed, SNA profiles must be created on the pSeries computer, and
SNA (with all the network connections) must be started.
WebSphere Voice Response for AIX: Installation describes how to determine

whether SNA is ready. Use this information to ensure that the correct profiles
have been created, and to start SNA and the connection if necessary.
Has the 3270 option been installed?
For WebSphere Voice Response to recognize the 3270 connection, the
value of the 3270 Installed parameter in the Application Server
Interface parameter group must be Real Mode. Use the information
provided in WebSphere Voice Response for AIX: Configuring the System to
correct it.
Are configured 3270 sessions available?
WebSphere Voice Response requires a ready 3270 session to enable it
communicate with a remote 3270 host. Use the information provided
in WebSphere Voice Response for AIX: Configuring the System to review
the status of 3270 sessions.
If all the sessions are initializing, allocated, or emulating, you need
additional sessions. Use the information provided in WebSphere Voice
Response for AIX: Configuring the System to configure additional
sessions.
If a session is disabled, use the information provided in WebSphere
Voice Response for AIX: Configuring the System to restart the disabled
session (or sessions).
If no sessions have been configured, use the information provided in
WebSphere Voice Response for AIX: Configuring the System to configure
sessions.
If all else fails, recycle WebSphere Voice Response (shut it down and
restart it). Use the information provided in WebSphere Voice Response
for AIX: Configuring the System to quiesce any active sessions first.
3270 session is permanently disabled
When you configure a 3270 session for use by a server but the session always
has the status “Disabled”, check the following.
The sample 3270 server provided with WebSphere Voice Response is only a
sample. The server can run in virtual mode, but not in real mode. If you try
to run this server in real mode, it disables all sessions that are configured to
use it. Use the information in WebSphere Voice Response for AIX: Configuring the
System to reconfigure the session or reconfigure the 3270 connection as virtual
mode. Use the comments that are included at the top of the login_amnu
script, which is the SrvrSample_3270 initial login script, to edit the script for
virtual mode operation.
When you activate a configuration for a 3270 session, WebSphere Voice

Response runs the initial script for the server that is defined to use the session
if one has been defined. If there is a problem with the initial script, the system
disables the session. Use the information provided in WebSphere Voice Response
for AIX: Application Development using State Tables to resolve any problems with
the initial script. Use the information provided in WebSphere Voice Response for
AIX: Configuring the System to restart the session. If you are sure the initial
script runs correctly but you cannot restart the session, recycle WebSphere
Voice Response (shut it down and restart it). Use the information provided in
WebSphere Voice Response for AIX: Configuring the System to quiesce any active
sessions first.
3270 emulation does not work
If you try to use the 3270 emulation function and it fails to operate, use the
information in “WebSphere Voice Response cannot access a remote 3270 host”
on page 54 and “3270 server does not start” on page 75 to try to solve the
problem. The emulation function cannot operate unless the 3270 connection is
established and a session is available for the emulation function to use.
For more information on 3270 emulation, see WebSphere Voice Response for AIX:
Telephony connection does not synchronize
When the hardware is receiving a loss of signal or other network alarm,
which can be displayed by using the DTTA_alarms utility from the
$VAE/tools directory (see “Running diagnostics on the DTTA” on page 27,
For T1, are the switch and WebSphere Voice Response configured correctly
for the T1 Line Code and T1 Framing Mode?
For T1 line code and framing mode values for different signaling
protocols, see the table in WebSphere Voice Response for AIX: Configuring
the System. Your telephone provider can help you verify these
parameters.

Is the trunk in service?
WebSphere Voice Response neither sends nor receives signals on a
trunk until you activate the trunk, by assigning the status InService.
When the pack is not enabled or in service, all the LEDs are on.
Use the System Monitor to put the trunk InService. For more
information, see WebSphere Voice Response for AIX: Configuring the
System.
Cannot enable trunk
WebSphere Voice Response cannot use a trunk unless a digital trunk adapter
(DTTA is installed in the pSeries computer to process the signals that are
transmitted by the switch. A trunk status of Available indicates that a digital
trunk adapter is physically present (is available) to handle the signals from
that trunk.
The way to inform WebSphere Voice Response that additional digital trunk
adapters are installed is to enable the trunks to which they are connected. The
enabling of a trunk informs WebSphere Voice Response that the digital trunk
adapter has been installed. (If you are looking at the System Monitor, you can
see that after you enable a trunk, the trunk status displayed at the top of the
graphic is Available.) When you cannot enable additional trunks, check the
following:
Is the digital trunk adapter installed?
Check that the trunk cable is installed and that the cable is connected
properly (you may need to try reseating it). Check that the trunk has
been configured with some channel licenses. Also check that the
dt_setowner command has been issued for each DTTA, see WebSphere
Voice Response for AIX: Installation.
Have you tried recycling WebSphere Voice Response?
Configuring the System to reset the Operating Status parameter for the
trunk to Available. Then use this information to recycle WebSphere
Voice Response (shut it down and restart it). If necessary, also try
restarting the pSeries computer. If you do, ensure that you shut down
WebSphere Voice Response first.
Has the switch disabled your trunk?
If you have been enabling and disabling the trunk frequently, or have
been experimenting with the telephony configuration, the switch to
which you are connected may have decided that there is something
wrong with the trunk. In this case, the switch may disable the trunk
temporarily or permanently. Your telephone provider can tell you if
the switch has disabled the trunk.
Trunk configured for ISDN does not enable using System Monitor
Check whether any warnings are visible in the alarm windows. These
can help you solve the problem, as described below:
27046 SDI failed to enable a pack because a signaling process was
missing
The process name is given at the end of the alarm parameters.
This custom server might not have been started or installed.
This error can also occur if the system was configured to run
with two different types of ISDN; for example, AT&T 5ESS
Versions 5E8 and 5E9, which is not allowed. Only one ISDN
custom server can be run at a time.
You can resolve this by checking whether the correct ISDN
custom server is installed and running. If it is, shutdown and
restart WebSphere Voice Response.
29604 ISDN Layer 2 opening/closing D channel via Device Driver
This problem occurs when an ISDN Layer 2 process is still
active because of a previous problem, and a new ISDN Layer
2 process is started. The file descriptor is being held by the
original process for the device driver, and cannot be reopened.
You can solve this by shutting down and restarting the
system; this action cleans up any old ISDN processes that are
still running in the system. If this problem happens frequently
call IBM Support.
29609 ISDN Layer 2 Internal Error29403 ISDN Layer 3 Internal Error
These messages occur when a fatal error has occurred on one
of the signaling channels on ISDN. Parameters are logged in
the error log, and WebSphere Voice Response System
Management attempts to restart the trunk automatically.
If the trunk does not restart automatically, Disable then Enable
it manually. If this action has no effect, disable all trunks, then
stop and restart the ISDN custom server. The trunks should
then enable.
Take a note of these alarm parameters and contact IBM
Support.
Check whether your signaling process is still running. Message 32011
indicates that a signaling process has terminated.
Check whether your signaling process is receiving the
SL_TRUNK_ENABLE_REQ primitive.

Check whether your signaling process is returning the
SL_TRUNK_ENABLE_CNF primitive to WebSphere Voice Response
and the sl_send_confirm() subroutine is returning successfully.
Use signaling interface tracing the see the primitive that WebSphere
Voice Response sent to your signaling process . For information on
tracing the signaling interface, see WebSphere Voice Response for AIX:
DB2 does not start if the machine name is changed after DB2 is installed
If a machine name is changed post-installation, DB2 fails to start, and
produces the following error:
SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing.
Note that due to retries at establishing communications, WebSphere Voice

Response may not produce the error for a considerable period of time (up to
10 minutes).
A TCP/IP communication error occurred while the START or STOP

DATABASE MANAGER command was trying to establish connection with all
the nodes defined in the sqllib/db2nodes.cfg file.
To resolve this problem, do the following:

1. Ensure that the node has the proper authorization defined in the .rhosts
or the host.equiv files.
2. Ensure that all the host names defined in the db2nodes.cfg file in the
sqllib directory are defined on the network and are running. The format
of the entries in db2nodes.cfg is:
0 hostshortname 0
For example, for a system called freda.hursley.ibm.com, it would be:

0 freda 0
To change a machine name in db2, go to/home/dtdb23in/sqllib, and make
the change in the db2nodes.cfg file.
Resolving error_id 26001
If the WebSphere Voice Response errorlog file (in $OAM_LOG_PATH) shows
repeated error_id 26001 every few seconds, with SMUX Info of
"join_tcp_server failed: Connection refused", the AIX SNMP process is not
running. This could be because the AIX SNMP agent is disabled or stopped.
Check if the AIX SNMP agent is running by running the command:

lssrc -a | grep snmpd
To resolve this problem, if the snmpd subsystem is disabled due to security
concerns, and there is no plan to make snmpd active on this WebSphere Voice
Response system, completing the following steps can prevent the repeated
error_id 26001:
1. Update the tasklist.data file in the $SYS_DIR (/usr/lpp/dirTalk/db/
sys_dir) and remove the following line:
A 20 DTSNMPD_START
2. Restart WebSphere Voice Response.
Problems found while running voice applications

This section describes what to do when you encounter one of the following
runtime problems:
v “Voice application does not start” on page 60
v “Calls do not transfer” on page 60
v “FileCache failures when running VoiceXML applications” on page 62
v “VXMLParserPool::Parser created over capacity” on page 64
v “Exceptions reported when a Java or VoiceXML application is started from
a VRNode” on page 64
v “Dial, MakeCall, or TransferCall actions behave unexpectedly” on page 65
v “Get actions that use the telephone line do not execute” on page 67
v “SendData or ReceiveData action does not provide expected results” on
page 67
v “Application fails attempting to play voice” on page 68
v “Common problems with voice interrupt detection” on page 70
v “Common problems with background music” on page 71
v “Results of running an application are not as expected” on page 74
v “Mailbox does not play recorded message” on page 75
v “3270 server does not start” on page 75
v “3270 server script fails” on page 76
v “Custom server does not start” on page 77
v “WebSphere Voice Response does not accept data from the caller's keypad”
on page 77
v “DTMF input is sometimes not recognized in a state table application” on
page 78
v “WebSphere Voice Response generates "unsupported language" error when
running VoiceXML Application” on page 78
v “Exceptions reported when a WebSphere Voice Response Java/VoiceXML
application is started from VRNode” on page 79

v “FileCache error on a WebSphere Voice Response VoiceXML 2.0 system with
multiple application Nodes” on page 80
v “Compression of voice messaging can result in poor quality audio” on page
80
v “error_id 1 and error_id 25032 caused by an unsupported application
design” on page 81
v “Error on recordutterance with Nuance speech server” on page 82
v “Text-to-speech audio in an application sounds like static” on page 82
v “Timeout waiting for response from grammar compiler” on page 82
Voice application does not start
When a voice application does not start when called, check the following:
Are the associated state tables and prompts validated?
Before a voice application can start, the state tables and prompts used
by the application must be validated. Use the State Tables option
from the Development menu to open the application’s state tables
and prompts and make sure that the Validated field displays Yes. If
not, select File then Validate for each object that needs to be
validated.
For more information about validating and modifying state tables and
prompts, see WebSphere Voice Response for AIX: Application Development
using State Tables.
Is the main state table identified in the application profile State Table
field? The application profile that is retrieved in response to an incoming
call must identify the state table that starts the voice application. Use
the Application Profile option on the Configuration menu to open
the application profile and check the State Table field.
For more information about defining and modifying application
profiles, see WebSphere Voice Response for AIX: Configuring the System.
Calls do not transfer
When a call does not transfer as expected during the execution of a voice
application, check the following:
Does your telephony configuration support call transfer?
Different switches interpret different signals as a request for call
transfer on CAS protocols. The signal that WebSphere Voice Response
sends is determined by the values of the Transfer Call Request Signal
and the Transfer Call Feature Code parameters of the signaling type
definition used by the channel processing the call. Some switches
might also require the state table to run a Dial action with hook flash
before the TransferCall action, to ensure that the TransferCall
completes successfully. To reset the value of the Transfer Call Feature
Code parameter:
1. Use Pack Configuration to determine which channel group is
assigned to the trunk.
2. Use System Configuration to determine which Signaling Type is
specified in the Channel Group definition.
3. Use System Configuration to reset the value of the Transfer Call
Feature Code parameter in the Signaling Type definition Use Help
on the Transfer Call Feature Code window if you need an
explanation of the parameter.
For more information about signaling types, see WebSphere Voice
Response for AIX: Configuring the System. For information about Dial
and TransferCall, see the WebSphere Voice Response for AIX: Application
Development using State Tables book.
Is TransferCall immediately followed by a TerminateCall action?
When a voice application runs a TransferCall action successfully, it
does not complete the connection to the new extension until it
performs an action that frees the channel, such as TerminateCall or
CloseEverything. Unless TransferCall is followed by TerminateCall,
the caller is forced to wait until the voice application reaches a
CloseEverything action, before the transfer is made. Use the
information provided in WebSphere Voice Response for AIX: Application
Development using State Tables to open the TransferCall action
definition and ensure that the Successful result passes control to a
TerminateCall action.
For information about TransferCall and TerminateCall, see the
Tables book.
Is the digit string format definition correct?
The stream of signals that is sent to a switch to achieve call transfer is
not the same for all switches. Use the information about TransferCall
that is provided in WebSphere Voice Response for AIX: Application
Development using State Tables to ensure that the digit string format
specified in the TransferCall action is correct for your switch.
Is the switch configured to allow calls to be transferred?
The extension to which the voice application is attempting to transfer
calls must be configured to accept transferred calls.
If your switch supports call transfer, the Class of Service for the
channels connected to WebSphere Voice Response must be set up to
allow call transfer.
For information specific to the configuration requirements of your
switch, see your telephone provider.

Does the switch automatically reconnect calls?
If the extension to which a call is transferred is busy or not available
for some reason, the caller should be reconnected to the line on which
the call was originally received. Verify that your switch performs this
action automatically, or that the state table contains a ReconnectCall
action to handle the situation when the connection to the transfer
extension fails. Note that some switches (for example, the ROLM
switch) require a Dial action with hook flash before the ReconnectCall
action.
For information about your switch, see your telephone provider. For
information about ReconnectCall and Dial, see WebSphere Voice
Response for AIX: Application Development using State Tables.
in the error log indicates that a signaling process has terminated.
Did your signaling process specify
SL_SIGPROC_CAPABILITY_TRANSFER when it called the sl_open()
subroutine?
Is the state table using the TransferCall action or the Dial action? You
should use the TransferCall action in your state tables because the
Dial action does not work when you are using a signaling process.
SL_CALL_TRANSFER_REQ primitive.
SL_CALL_TRANSFER_CNF primitive to WebSphere Voice Response
and that the sl_send_confirm() subroutine is returning successfully.
Use signaling interface tracing to see the primitive that WebSphere
Voice Response sent to your signaling process. For information on
FileCache failures when running VoiceXML applications
When running applications on a WebSphere Voice Response VoiceXML 2.0
system configured with multiple application nodes, a FileCache failure can
occur with error messages similar to the following:
v "Cannot lock a file because of a potential deadlock condition"
v "Unable to obtain exclusive file lock"
These errors are logged in the standard log.n.log files in the
/var/dirTalk/DTBE/dtj_logs directory.
As these problems only arise when multiple applications nodes are
configured, the solution is to use a separate FileCache directory for each
application node, by configuring the system as follows:
1. Stop the Java and VoiceXML environment by entering the commands
dtjstop followed by dtjshost -exit .
2. Edit the configuration file for the Java and VoiceXML environment,
/var/dirTalk/DTBE/native/aix/default.cff, so that in the configuration
section for each application node, you add (or modify) the JavaCommand
entry as follows:
-Dwvr.vxml.cachedir=/var/dirTalk/DTBE/native/aix/VXML2Cache/<cachename>
where <cachename> is a unique name for each application node (you can
use the application node name itself).
3. Save the changes, then import the new configuration by entering the
dtjconf command.
4. Restart the Java and VoiceXML environment by entering the commands
dtjshostfollowed by dtjstart.
Newly installed voice audio files not played by VoiceXML application
After a VoiceXML application is updated to use new voice files by copying
them into the filesystem, the old copies of the audio files are still played to
the caller after the Java and VoiceXML (VRBE) environment is restarted.
The reason for this is that the original voice data has been cached and unless
time and date expiration handling is in the code to determine when to fetch
from the filesystem again, the updated voice is not fetched, so the old data is
still used.
The solution is to do one of the following:

v Delete the voice cache directories:
1. Shutdown the VRBE environment
2. Delete the voice cache directories below $CUR_DIR/voice/ext/v2c/
dotted.ip.address
3. Restart VRBE
v Control when to fetch data again:
1. In the VoiceXML application code, use the maxage and/or maxstale
attributes of the <audio> element to control when to fetch data again.
For example:
<?xml version=1.0 encoding=iso-8859-1?>
<!DOCTYPE vxml PUBLIC -//W3C//DTD VOICEXML 2.0//EN vxml20-1115.dtd>
<vxml version=2.0 xml:lang=en-US xmlns=http://www.w3.org/2001/vxml>
<meta name=GENERATOR content=Voice Toolkit for WebSphere Studio/>
<meta http-equiv=Expires content=0/>
<meta http-equiv=Cache-control content=max-age=0/>

<form>
<block>
<audio maxage=20 src=hello.wav>Hello this is Dave</audio>
</block>
</form>
</vxml>
VXMLParserPool::Parser created over capacity

The following warning message can be generated in $DTJ_HOME/dtj_logs/
log.x.log:
(VXI50012) WARNING: VXMLParserPool::Parser created over capacity:
[VXMLParserPool (poolCapacity=19) (poolCount=19) (available=0)]
The message indicates that all 19 VoiceXML parsers are currently active, and
that one new parser has been created and added to the pool. The warning by
itself is not an indication of a problem and therefore no user action is
required. However, in order to minimize the frequency of the message
appearing, you should consider the following actions during application
development:
v Check that the initial documents are not excessive in size, as this increases
the parse time and therefore the usage of the parsers.
v Ensure that the cache parameters are set correctly, so that the WebSphere
Voice Response VoiceXML browser does not have to parse too many
identical documents. Refer to “Preventing caching” in the WebSphere Voice
Response: VoiceXML Programmer's Guide book.
Exceptions reported when a Java or VoiceXML application is started from
a VRNode
ClassNotFound exceptions can be reported from some, though not all Java or
VoiceXML application instances. The problem is caused by having different
NodeClassPath parameters for the nodes in which the application instances
are being run. While this can be caused by deliberate or accidental differences
in the classpath for application nodes, a common cause is when application
instances are run in the VRnode, which is not configured to run them. This
can happen if NodeDefAppName is coded in the VRnode and there are
insufficient application instances running to meet the demand.
To avoid or overcome this problem, ensure that you take the following
actions:
v Ensure that all nodes in which application instances are running have the
correct classpath.
v If the trigger was NodeDefAppName, then try to avoid using this
parameter and configure NumToApp mappings instead.
v Ensure that enough application instances are configured to meet peak
demand. The dtjqapps command can be used to monitor application
instances.
v If NodeDefAppName must be used, then it is even more important to
ensure that sufficient application instances are running to meet demand.
Running application instances in the VRnode is not recommended.
Dial, MakeCall, or TransferCall actions behave unexpectedly
When a voice application produces unexpected results from a Dial, MakeCall,
or TransferCall action, check the following:
Are the values of the controlling system parameters correct?
How Dial, MakeCall, and TransferCall behave is partially controlled
by the values of the Maximum Ring Time, Maximum Ring Wait, and
Maximum Dial Tone Wait parameters in the Application Server
Interface parameter group. Use the information provided in WebSphere
Voice Response for AIX: Configuring the System to check these values
and if necessary, redefine them. Make sure that WebSphere Voice
Response is configured to expect or not expect a dial tone by checking
the value of the Dial Tone Detection parameter.
For more information about defining Dial, MakeCall, and TransferCall,
see WebSphere Voice Response for AIX: Application Development using
State Tables.
Is the telephone line in the expected state?
The operation of Dial and TransferCall assume that the voice
application is running on a channel that is already active (handling an
in-progress call). MakeCall, however, requires a free channel for the
action to run correctly. Ensure that the Dial and TransferCall actions in
the state table are preceded by an AnswerCall (to begin processing an
inbound call) or MakeCall (to originate an outbound call). Ensure that
nothing in the state table instructs the application to connect a channel
and begin handling a call before the MakeCall action is run.
For more information about the operation of Dial, MakeCall, and
TransferCall, see WebSphere Voice Response for AIX: Application
Is your switch protocol FXS loop start?
MakeCall might occasionally fail if your switch protocol is FXS loop
start. Because glare conditions cannot be detected reliably on loop
start, MakeCall fails when an inbound call and an outbound call
attempt to use the same channel at the same time. In this situation,
WebSphere Voice Response flags a B-bit fault error and posts an alarm
to the System Monitor.
You can remove this problem if you configure the trunk channels to
handle either inbound calls or outbound calls but not ‘bothway’calls.
If you need bothway channels, you can minimize the likelihood of
this problem occurring. To do this, configure the switch and any hunt
group to locate a free channel for an inbound call (beginning with the

first channel on the trunk), and for an outbound call (beginning with
the last channel). This configuration significantly reduces the
possibility for collision between an inbound call and an outbound call
attempting to use the same channel at the same time.
For more information about defining channel groups and the System
Monitor, see WebSphere Voice Response for AIX: Configuring the System.
Does your switch have unique requirements?
Your configuration might require particular signals that are unique to
your switch. For example, for a TransferCall action to complete
successfully, the ROLM switch requires a Dial action with hook flash
before the TransferCall action . Check the signaling requirements of
your switch and ensure that all necessary states are implemented in
your state table.
For information that is specific to the requirements of your switch, see
your telephone provider.
Is the digit string format definition correct?
The stream of signals that is sent to a switch to obtain a dial tone,
make an outbound call, or transfer a call is not the same for all
switches. Use the information about Dial, MakeCall, and TransferCall
that is provided in WebSphere Voice Response for AIX: Application
Development using State Tables to ensure that the digit string format
specified in the TransferCall action is correct for your switch.
Did your signaling process specify
SL_SIGPROC_CAPABILITY_TRANSFER when it called the sl_open()
subroutine?
Is the state table using the TransferCall action or the Dial action? You
should use the TransferCall action in your state tables because the
Dial action does not work when you are using a signaling process.
SL_CALL_TRANSFER_REQ primitive.
SL_CALL_TRANSFER_CNF primitive to WebSphere Voice Response
and that the sl_send_confirm() subroutine is returning successfully.
Use signaling interface tracing to see the primitive that WebSphere
Voice Response sent to your signaling process. For information on
Get actions that use the telephone line do not execute
When Get actions that use the telephone line, such as GetData and GetKey, do
not execute, check the following:
Are these actions preceded by an AnswerCall action?
AnswerCall sets up the connection between the caller and WebSphere
Voice Response for an incoming call. An application cannot execute
actions that use the telephone line until this connection is made. The
AnswerCall action does not need to be in the state table that contains
the Get actions, but it must have been executed before the Get actions,
in a state table that is part of the same voice application.
For more information about AnswerCall, see WebSphere Voice Response
for AIX: Application Development using State Tables.
Is the timeout value long enough?
The Timeout parameter for a Get action specifies how many seconds
the application waits for a caller to provide input. Ensure that the
value specified by the Timeout parameter in the action definitions is
long enough to allow the caller to input required information.
For more information about the Get action parameters, see WebSphere
Voice Response for AIX: Application Development using State Tables.
SendData or ReceiveData action does not provide expected results
When SendData or ReceiveData do not run as expected, check the following:
Do the SendData and ReceiveData actions specify the same server?
The server that is specified in the SendData definition must match the
server specified in the following ReceiveData definition. Use the
information provided in the WebSphere Voice Response for AIX:
Application Development using State Tables book, to open the action
definition windows and check the server specification. This book also
contains details about defining SendData and ReceiveData actions.
Are the SendData and ReceiveData actions alternated?
WebSphere Voice Response allocates a single buffer for the data
transmitted by each server that uses the SendData and ReceiveData
actions. Therefore, you cannot run multiple SendData actions without
the alternating ReceiveData actions. Check the state table to make sure
that these actions alternate.
Have you allowed enough time for the data to be accessed by the server?
If the number of seconds that is specified for the Host Response Time
Limit in the SendData definition is lower than the time required for
the server application to run, ReceiveData returns a “Host Problem”
result. The value specified in the ReceiveDataTimeout parameter is the

length of time, in seconds, that ReceiveData will wait for data. Check
that the value specified is high enough to allow the host enough time
to respond.
If the number of seconds specified for the Timeout in the ReceiveData
definition is not long enough for the host to respond to the request for
information, ReceiveData does not receive the required information.
Increase the Timeout value, if necessary.
Are your 3270 server scripts correctly defined?
SendData or ReceiveData can fail if the 3270 server that is used to
transmit data contains inconsistencies in screen and field definitions.
Ensure that the screen and field definitions for the 3270 server scripts
are correct and consistent in name, length, and attributes.
For information about defining 3270 server screens and fields, refer to
the WebSphere Voice Response for AIX: Application Development using
State Tables book.
Application fails attempting to play voice
When voice does not play, check the following:
Is the correct prompt directory identified?
The state table definition includes the prompt directory that the voice
application is to use. Use the information provided in the WebSphere
Voice Response for AIX: Application Development using State Tables bookl
to open the state table and ensure that the Prompt Directory field
identifies the prompt directory containing all the prompts for the
application.
For information about specifying a prompt directory in a state table
definition, refer to the WebSphere Voice Response for AIX: Application
Have you recorded all voice segments used by the application?
Use the information in the provided WebSphere Voice Response for AIX:
Application Development using State Tables book to ensure that both the
definitions and the recorded voice exist for all voice segments
referenced by the application prompts.
For information about defining and recording voice segments and
referencing segments in a prompt, refer to the WebSphere Voice
Response for AIX: Application Development using State Tables.
When recording the voice segment, was RecordVoiceSegment followed by
SaveVoiceSegment?
Recorded voice segments remain in temporary workspace until they
are saved to disk with SaveVoiceSegment. Use the information
provided in the WebSphere Voice Response for AIX: Application
Development using State Tables book to open the state table and ensure
that it contains SaveVoiceSegment, to save your recordings to disk.
For information about RecordVoiceSegment and SaveVoiceSegment,
see WebSphere Voice Response for AIX: Application Development using
State Tables.
Is the compression indicator set correctly?
The system default compression type is set by system variable SV182.
A value of 0 indicates that the voice segments in a prompt played by
the PlayPrompt action are uncompressed. A value of 2 indicates that
the segments are compressed. If this variable contains a value of -1,
the compression type specified in the definition of the prompt
directory is used. If either SV182 or the prompt directory definition
specifies a compression type that does not match a voice segment that
the application plays, then the segment does not play. Check that the
compression indicator is set to match the voice segments played by
the application.
For more information about specifying the compression for segments that are
played by a prompt, refer to the WebSphere Voice Response for AIX: Application
Do any spoken variables include unrecognized characters?
The WebSphere Voice Response system prompts can play numeric
input as a number, date, time, or currency. The prompt statements
that you use to create your own prompts can play the contents of
variables as characters or digits, as long as the contents are characters
or digits that WebSphere Voice Response recognizes, and for which
voice segments have been recorded. The character that WebSphere
Voice Response recognizes as marking a decimal place (usually a
decimal point, or period) is defined by system variable SV168.
If the contents of a variable that is being used as input to a prompt
includes a character that is not recognized by the prompt, the
PlayPrompt action will fail. For example, if the contents of a variable
that is to be played as digits includes a dollar sign ($), the action fails.
Make sure that the contents of any variable that is to be played in a
prompt is valid for the prompt.
For information about expected input to system prompts, refer to the
Tables book. For information about prompt statements, and for more
information about SV168, refer to the WebSphere Voice Response for AIX:
Application Development using State Tables book.

Common problems with hangup detection
Problems with hangup detection often occur when you use a channel
associated signaling protocol that does not provide a disconnect (hangup)
indication in the signaling channel. The problems are usually related to the
setting of system parameters.
If WebSphere Voice Response does not recognize when the network party
disconnects:
v Determine (from your telephone provider) whether the switch provides an
audible disconnect signal; for example, dial or busy tone.
v Refer to WebSphere Voice Response for AIX: Configuring the System for
information about setting parameters for hangup tone detection.
v If the switch does not provide an audible hangup signal, see “Telephone
channel is hung” on page 52.
Common problems with voice interrupt detection
Problems with voice interrupt detection are usually related to the setting of
the system parameters or system variables.
Note: Use the system variables to override the system parameters by

application.
Caller cannot interrupt the prompt
If the caller cannot interrupt the prompt:
v Check that the prompt is not force played.
v Check that voice interrupt detection is turned on; see system
variable System : Voice Interrupt detection On/Off (SV217).
v Check the level of the voice interrupt detection level system
variable.
v If voice interrupt detection is not set, check the value of the system
parameter.
v Try setting the level either higher or lower.
Prompt does not play or does not complete, even though not interrupted by
the caller
The voice interrupt detection level system variable or system
parameter might be lower than echo on the line or background noise.
Increase the level.
Caller cannot interrupt the prompt with short words but can interrupt with
longer words
This problem can occur when the time that is specified in the voice
interrupt detection on time system variable or system parameter is too
short. Increase the value.
Caller has to shout to interrupt the prompt
The value of the voice interrupt detection level system variable or
system parameter is too high. Decrease the value of the level.
RecognizeWord is failing with Word Not Recognized result
This can occur if the time that is specified in the value of the voice
interrupt detection off time system variable or system parameter is not
long enough. Increase the off time.
Syllables or words from the caller who is trying to interrupt the prompt at
the beginning of the recorded voice, are recorded at the beginning of voice
data by a Record action, following the interrupt
This problem can occur when time that is specified in the voice
interrupt detection off time system variable or system parameter is not
long enough. Increase the off time, or add a tone between the Play
and Record actions in the state table.
For more information about voice interrupt detection system parameters, see
the section on setting parameters for voice interrupt detection in WebSphere
Voice Response for AIX: Configuring the System. For information about system
variables, see the WebSphere Voice Response for AIX: Application Development
using State Tables book.
Common problems with background music
Problems when using background music often relate to the setting of variables
or parameters.
Use the system variables to override the system parameters by application.

Music is not available, cannot fade it in
Use the state table debugger to step through the state table to where
the ControlMusic action error occurs.
Look at the Music Available window. From the Welcome Window
click Operations->System Monitor-> select a pack->Music Available.
If the music title is not listed, the cause could be one of the following:
v The trunk is disabled. Check the state of the trunk.
v A custom server has not opened a music channel using the correct
music title.
v A music player process has abnormally terminated.
v The custom server did not receive a request for this tune. Check
whether your state table is sending the request. If it is, the custom
server might be either not receiving, or misinterpreting the request.
Check that the music title in the ControlMusic action is exactly the
same as that displayed in the Music Available window. Something as

simple as a spelling mistake can create a mismatch between music
title strings. The strings are case sensitive and spacing and
punctuation are important.
The music does not fade in; it just starts at full volume
This can be caused by one of the following:
v The fade time parameter on the ControlMusic action is zero, or
close to zero. A very short fade in time increases the volume
quickly, so the music sounds as if it starts abruptly.
v This might be a characteristic of the piece of music. Listen to the
music to ensure that the music file or segment has not been clipped
at the start. You can use bvi_play to listen to the music; see the
Tables book for more information.
v If the previous tune that this state table used was stopped before it
was faded out, the volume of the new tune you fade in is the same
as the volume of the previous tune.
The music cuts out completely
v Does this tune end suddenly? Listen to the tune to check this. If
necessary, rerecord the tune including a gradual fade out.
v Is the fade time in the ControlMusic action zero or close to zero? A
very short fade time decreases the volume quickly, so the music
sounds as if it stops suddenly.
v Is the music title still shown the Music Available window? If it is
not, the custom server that is supplying that music data might have
closed its music channel. This happens when the custom server
exits or ends abnormally. Check the status of the custom server and
any error or warning messages in the Alarms window.
v Is that music title underrunning? Check it on the Music Available
window. If it is underrunning, the custom server supplying this
music data is blocked, has stopped or is looping. The most likely
cause of this is a coding error in the custom server. A
heavily-loaded system may be limiting the processing power or
data available to the music player. Increase the amount of data that
can be stored in the music player (parameter -b).
The music comes and goes, cutting in and out intermittently
v Is this the way the tune sounds? Listen to the tune. The audio file
might have been corrupted when recording or converting from one
format to another.
v Is the music title underrunning? Check it on the Music Available
window. If it is underrunning, the custom server that supplies the
music data might have a problem. The custom server or the music
player might be unable keep up with the 8 KB per second
requirement of the telephone line. This can happen if the process:
– Has a lower priority than it needs
– Is not programmed efficiently
– Is blocking for long periods of time
– Is being delayed between the CA_Poll(), and the
CA_Play_Voice_Elements, or CA_Play_Voice_Stream custom
server calls
A heavily-loaded system can cause a delay between the return of
the CA_Poll() call returns and when the player issues a
CA_Play() call. During this time, the data drains away from the
low water mark to empty. Increase the high water mark and low
water mark if possible.
Underrunning can happen on a system that is overloaded. It cannot
keep up with the real-time requirements of WebSphere Voice
Response. Check your system for processes that are using more
CPU or system time than expected using ps. Terminate some
processes to reduce the load on the system and check to see if this
affects underrunning on this music channel.
v Is the state table constantly performing fade in and fade out
operations, using a small value in the fade time parameter? Change
the state table to prevent this happening. This is not underrunning
but a fault in the way the application is coded.
v Are any of the following actions being used frequently? GetKey,
GetData, GetFindData, GetFindName, GetPassword, GetText,
RecordVoiceSegment, RecordAudioName, RecordUserGreeting,
RecordVoiceMessage, RecordVoiceToHost, RecognizeWord, Dial.
WebSphere Voice Response performs a fade out operation when
these state table actions are run, and a fade in when they have
completed. The fade time is set in system variable SV225,
System : Music : Automatic fade time. When this system variable
is set to a small value, the fade occurs over a very short time,
seeming to cut in and out.
v Is a short piece of music being played in the background in a
continual loop? Use a longer piece of music.
The ControlMusic action succeeded, but I still cannot hear any music
v Is the music file corrupted? Is it full of silence or low-volume
sounds? Listen to the source of the music to check this, or use the
segment editor to view the sample.
v Is the dBm level in the CA_Play_Voice_Stream custom server API
call set correctly? Check the level and reset it if necessary.

v Is the music channel underrunning? Check it on the Music
Available window. See also The music cuts out completely.
v Is the volume ceiling default set too high numerically? Your
application controls this using system variable SV224
(System : Music : Volume ceiling).
v Is the system variable SV224 (System : Music : Volume ceiling)
set too high numerically? This can limit the volume of the music
channel to an inaudible level.
v Is the system parameter Music Volume Ceiling Default set too high
numerically? You can override this default from your application by
using the system variable SV224 (System : Music : Volume
ceiling).
v Is the volume being faded to 0, or to a value that should be
audible, when combined with the existing setting of system variable
SV224 (System : Music : Volume ceiling).
For more information about Background Music system parameters see

WebSphere Voice Response for AIX: Configuring the System, for system variables
see, WebSphere Voice Response for AIX: Application Development using State Tables.
Element or segment files sound dull
If a tune that is played from an element file sounds dull, it might be
that the original signal was recorded using a “flat spectrum” in a
recording studio. It is a good idea to use equalizing equipment, either
when recording the music, or when playing it back to the Ultimedia
adapter.
The same thing can happen to segments. bvi_import can be used to
add a rudimentary filtering stage to reduce this effect. Use
equalization equipment to produce a clear tune, and do not use the
boost option on the bvi_import utility.
Results of running an application are not as expected
When non-specific problems occur during the running of an application, check
the following:
Is the state table logic producing the expected results?
Use the state table debugger to ensure that each state table action
operates as expected, and that the variables contain valid values.
For information about debugging a state table, see the WebSphere Voice
Response for AIX: Application Development using State Tables book.
Have you made changes to the definitions of variables that are passed
between state tables or between a custom server and state table?
Variables passed between a custom server and state table must be
defined to the custom server first, then the state table. Otherwise, you
need to redefine the variables in the state table. Ensure that the
definitions of variables passed between state tables match.
For information about defining variables in state tables and custom
servers, see the WebSphere Voice Response for AIX: Application
Mailbox does not play recorded message
When an attempt to play voice messages from a mailbox fails, check the
following:
Did the application that recorded the message follow RecordVoiceMessage
with SendVoiceMessage?
Recorded voice messages remain in temporary workspace until they
are associated with a mailbox (by SendVoiceMessage). Make sure that
the application used to record the message includes the
SendVoiceMessage action.
For information about RecordVoiceMessage and SendVoiceMessage,
and general information about voice messaging, see the WebSphere
Voice Response for AIX: Application Development using State Tables book.
Is PlayVoiceMessage preceded by CheckVoiceMessages?
Messages must first be retrieved from a mailbox with
CheckVoiceMessages before they can be played with
PlayVoiceMessage. Make sure that the application includes a
CheckVoiceMessages action before the PlayVoiceMessage action.
For information about PlayVoiceMessage and CheckVoiceMessages,
see the WebSphere Voice Response for AIX: Application Development using
State Tables book.
3270 server does not start
When an OpenHostServerLink action fails to start the specified 3270 server,
Does the calling state table correctly specify the 3270 server name?
Use the State Tables option on the Development menu to open the
state table that calls the 3270 server and ensure that the name of the
3270 server specified in the OpenHostServerLink action is correct.
For information about OpenHostServerLink, see the WebSphere Voice
Has SNA been configured and started?
For the server to communicate with a remote 3270 host, SNA must be
installed, SNA profiles must be created on the pSeries computer, and
SNA (with all the network connections) must be started.

WebSphere Voice Response for AIX: Installation describes how to
determine whether SNA is ready. Use this information to make ensure
that the correct profiles have been created, and to start SNA and the
connection if necessary.
Are configured 3270 sessions available?
Servers can only communicate with the 3270 host via 3270 sessions
that have been configured for them. Use the information provided in
WebSphere Voice Response for AIX: Configuring the System to review the
status of 3270 sessions.
If all of the sessions configured for the server are initializing or
allocated, you need additional sessions. Use the information provided
in WebSphere Voice Response for AIX: Configuring the System to configure
additional sessions.
If a session that would otherwise be available is disabled, use the
information provided in WebSphere Voice Response for AIX: Configuring
the System to restart the disabled session (or sessions).
If no sessions have been configured for the server, use the information
in WebSphere Voice Response for AIX: Configuring the System to configure
sessions.
If all else fails, recycle WebSphere Voice Response (shut it down and
restart it). Be sure to quiesce any active sessions first.
3270 server script fails
When a 3270 server is successfully invoked, and a script that is defined for
the server fails, check the following:
Is the host access timeout long enough?
The Host Response Time Limit value defined for the SendData action
specifies the number of seconds that the application waits for the 3270
host to respond to the request for information. If this value is lower
than the time required for the server application to run, SendData
times out. The Timeout value that is defined for the ReceiveData
action specifies the number of seconds that the application waits for a
response to the request for information. Use the State Tables option
from the Development menu to open the SendData and ReceiveData
action definitions to ensure that these values are high enough to allow
for the amount of time required.
For information about SendData and ReceiveData, see the WebSphere
Is the script logic producing the expected results?
Use the 3270 server debugger to ensure that each script statement
operates as expected and that data is sent and retrieved successfully.
For information about debugging a 3270 server, see the WebSphere
Custom server does not start
When an OpenHostServerLink action fails to start the specified custom server,
Does the state table correctly specify the custom server name?
Use the State Tables option on the Development menu to open the
state table that calls the custom server and ensure that the name of
the custom server specified in the OpenHostServerLink action is
correct.
For information about OpenHostServerLink, see the WebSphere Voice
Has the custom server been started?
Applications cannot access a custom server until the server is loaded
into memory. If the system has been recycled since the last time the
server was used, for example, the server might no longer be in
memory. Use the Custom Server Manager option on the Operations
menu to start the custom server.
Are enough free buffers available in the buffer pool?
Check the error log for error 12005 and parameter text “Pool Buffer
Threshold Exceeded”. This means that there are insufficient free
buffers available in the buffer pool for WebSphere Voice Response to
allow use of the custom server to proceed. Use DTmon to determine
the usage of the buffer pool and refer to WebSphere Voice Response for
AIX: Managing and Monitoring the System for information on how to
size the buffer pool.
The DTmon command is described in WebSphere Voice Response for
AIX: Managing and Monitoring the System.
If the custom server accesses data on another host computer, is the host
available?
Check the user function that sets up the links to the host computer,
and ensure that the code correctly specifies the communication path to
an active host.
For information about the communication protocols supported by the
pSeries computer, refer to the “Networks and communication” section
of the IBM AIX Version 6.1 information.
WebSphere Voice Response does not accept data from the caller's
keypad
When a voice application does not accept the data that a caller keys in, check
the following:

Is the caller pressing the pound key (#)?
If the caller has to enter a string of digits, check whether the GetData
action requires the # key to be pressed at the end of the string. Use
the State Tables option on the Development menu to ensure that the
GetData action is properly defined. If the caller must press the # key,
it helps if the preceding prompt makes this clear.
For more information see the WebSphere Voice Response for AIX:
Application Development using State Tables book.
Is the caller's telephone system producing tones of the correct frequency
and duration?
Some telephone systems produce non-standard tones that are not
within the tolerance levels of WebSphere Voice Response. When
someone calls from such a telephone, WebSphere Voice Response
cannot hear the data being sent. If customers call to complain that
they cannot use the voice applications, find out what telephone
company handles their service. You might then need to get
information from the telephone company to ensure that the
equipment produces tones according to the required standards.
DTMF input is sometimes not recognized in a state table application
If a DTMF key is pressed very early on in a prompt that is not set to force
play, it is not always recognized. This happens with a PlayPrompt state table
action that is immediately preceded by a GetData action. In the GetData
action, if the value defined for Minimum is the same as the value defined for
Maximum, the caller does not have to press the pound key (#) to indicate that
the information is complete. Once the action receives the number of characters
(or the number) defined by the values of Minimum and Maximum, it moves
to the next state. When this happens, the next prompt is force-played for the
first 0.8 seconds to discard any extra keys the caller has pressed. Any DTMF
keys that are received whilst a prompt is playing in force-play mode are
immediately flushed from the buffer.
If only a single key input is required, the action GetKey should be used
instead of GetData. If multiple DTMF input is required 0.8 seconds of silence
can be added to the start of the following prompt, thus when speech starts the
0.8 seconds of enforced ‘force-play’ will have completed.
WebSphere Voice Response generates "unsupported language" error
when running VoiceXML Application
The VXML2 application is of the type:
<vxml version=2.0 xmlns=http://www.w3.org/2001/vxml>
<form>
<field name=key1 type=digits>
<prompt>
<audio scr=PIN.wav />
</prompt>
</form>
</vxml>
A test call to such an application generates an error similar to the following:

error.unsupported.language:en: com.ibm.vxi.srvc.UnsupportedLanguageError: en
at com.ibm.wvr.vxml2.DTGrammarProcessorSupport.commitChanges(DTGrammarProcessorSupport.java:314)
at com.ibm.wvr.vxml2.DTAsrService.commitChanges(DTAsrService.java:128)
at com.ibm.vxi.intp.VXIContext.collect(VXIContext.java:3253)
at com.ibm.vxi.intp.VXIContext.collectInput(VXIContext.java:2858)
at com.ibm.vxi.intp.Efield.exec(Efield.java:220)
at com.ibm.vxi.intp.FIA.exec(FIA.java:1257)
at com.ibm.vxi.intp.FIA.collect(FIA.java:739)
at com.ibm.vxi.intp.FIA.main(FIA.java:536)
at com.ibm.vxi.intp.FIA.init(FIA.java:418)
at com.ibm.vxi.intp.FIA.run(FIA.java:227)
at com.ibm.vxi.intp.VXISession.run(VXISession.java:429)
at com.ibm.vxi.intp.VXIContext.interpret(VXIContext.java:475)
at com.ibm.vxi.intp.VoiceBrowser.run(VoiceBrowser.java:570)
at com.ibm.wvr.vxml2.VXML2BrowserLauncher.waitForCall(VXML2BrowserLauncher.java:1286)
at com.ibm.wvr.vxml2.DTVoicelet2.run(DTVoicelet2.java:460)
at java.lang.Thread.run(Thread.java:568)
and the application is terminated.
The problem is due to the default input for <field> in the application being
set to voice input. When the voice recognition is not configured, or not
available from the WebSphere Voice Response system, the error above occurs.
To use the <field> element in a VoiceXML 2 application without voice

recognition, the application needs to be changed to include <property
name=inputmodes value=dtmf/> after the <vxml> element and before the
<field> element for DTMF input.
Exceptions reported when a WebSphere Voice Response Java/VoiceXML
application is started from VRNode
In some circumstances, ClassNotFound exceptions are reported from some,
though not all Java/VoiceXML application instances.
The problem is caused by different NodeClassPath parameters for the nodes in

which the application instances are being run. While this can be caused by
deliberate or accidental differences in the classpath for application nodes, a
common cause is application instances being run in the VRnode, which is not
configured to run them. This can happen if NodeDefAppName is coded in the
VRnode and there are insufficient application instances running to meet
demand.
Ensure that all nodes in which application instances are running have the
correct classpath. If the trigger was NodeDefAppName, try to avoid using this
parameter and configure NumToApp mappings instead. Ensure that enough
application instances are configured to meet peak demand. The dtjqapps

command can be used to monitor application instances. If NodeDefAppName
must be used, then it is even more important to ensure that sufficient
application instances are running to meeting demand. Running application
instances in the VRnode is not recommended.
FileCache error on a WebSphere Voice Response VoiceXML 2.0 system
with multiple application Nodes
When running a WebSphere Voice Response VoiceXML 2.0 system configured
with multiple application nodes, a FileCache failure can occur with one of the
following descriptions:
v Cannot lock a file because of a potential deadlock condition.
v Unable to obtain exclusive file lock.
These errors are logged in the standard log.n.log files in the
/var/dirTalk/DTBE/dtj_logs directory.
Use a separate FileCache directory for each application node, by configuring

the system as follows:
1. Stop the VRBE environment by running'dtjstop followed by dtjshost -exit.
2. Edit the VRBE configuration file /var/dirTalk/DTBE/native/aix/
default.cff. In each of the application node configuration sections, add
(or modify) the JavaCommand entry so that it includes the following
parameter:
-Dwvr.vxml2.cachedir=/var/dirTalk/DTBE/native/aix/VXML2Cache/<cachename>
where <cachename> is a unique name for each application node. (You could
use the application node name.)
3. Save the changes and then import the new configuration using the dtjconf
command.
4. Restart the VRBE environment by running dtjshost followed by dtjstart.
Compression of voice messaging can result in poor quality audio
Voice messages are normally stored in a compressed format. Although this
reduces the storage requirements, it can cause problems if Unified Messaging
is used in an environment that also uses audio compression, notably some
Voice over IP infrastructures. Such use of multiple compression stages can
result in the audio signal degrading, so that poor quality is experienced when
listening to recorded messages.
WebSphere Voice Response and Unified Messaging for WebSphere Voice

Response support the storage of voice messages in an uncompressed format.
This facility can be used to maximize the quality of voice messages when they
are used in an environment that employs its own compression mechanisms,
for example a Voice over IP network using G.729A. The ability to use
uncompressed messages is controlled using a WebSphere Voice Response
system parameter called Voice Message Compression Type, which is in the
Application Server Interface group . It can be set to compressed (default) or
uncompressed.
Some points to note:

1. WebSphere Voice Response must be restarted for a change in the value of
Voice Message Compression Type to take effect.
2. Compressed and uncompressed messages cannot be mixed on a
WebSphere Voice Response system (either standalone or Single System
Image), nor on multiple systems exchanging voice messages using Unified
Messaging Internode Messaging.
3. If you are not using Unified Messaging for WebSphere Voice Response,
only change the Voice Message Compression Type system parameter when
the voice database is empty.
4. Incorrectly setting Voice Message Compression Type on an existing system
prevents the playback of existing voice messages. Callers hear an error
message and red alarms (error_id 20504) are displayed in the system
console and in the error log.
error_id 1 and error_id 25032 caused by an unsupported application
design
If a voice application terminates with CHP coredump, error messages
error_id = 1 and error_id = 25032 are reported from the CHP process and a
core file /var/adm/ras/dirTalk/core.CHP is generated.
The problem is caused by a VoiceXML application that invokes a state table,

which in turn then invokes another VoiceXML document, giving an
application flow like the following:
VoiceXML -> state table -> ... -> state table -> VoiceXML
where the route back to VoiceXML is by using an InvokeStateTable action to

call the JavaApplication state table. This design is causing the CHP coredump,
and is not supported.
To return to VoiceXML again, avoiding the problem, the application should be

coded to just exit the state tables. The call will then naturally end up back in
the original VoiceXML application, and can then be handed off to the new
VoiceXML application through a goto, submit or similar operation.
WebSphere Voice Response does support handing a call off to VoiceXML after
a state table, but only if the call has not already been in a VoiceXML
application. So an application flow like the following is supported:
state table -> VoiceXML

using an InvokeStateTable action to call the JavaApplication state table.
Error on recordutterance with Nuance speech server
A VoiceXML application cannot record caller audio input.
The following error is logged in the WebSphere Voice Response VRBE log:
com.ibm.telephony.directtalk.mrcp.MRCPReco.fetchWaveform() error fetching waveform:
com.ibm.telephony.directtalk.mrcp.MRCPException: Waveform fetcher: Socket I/O problem:
java.net.ConnectException: A remote host refused an attempted connect operation.
The cause of the problem is that by default, Nuance speech server uses port
90 for the URL of the recorded utterance. This setup does not match the
default setting of most HTTP servers. Customer should check the Nuance
speech server Installation and User's Guide for the "Waveform-logging
resources" to ensure the matching TCP port setup.
Text-to-speech audio in an application sounds like static
The problem occurs when WebSphere Voice Response 4.2 or 6.1 is connected
to WebSphere Voice Server 5.1 or 6.1.1 which is using a 22 KHz TTS voice.
The cause is that WebSphere Voice Response does not support the 22 KHz
TTS voice. Change the application or its configuration to use the 8KHz TTS
voice.
Timeout waiting for response from grammar compiler
The WebSphere Voice Response VRBE component reports the following error:
error.semantic: Timeout waiting for response from grammar compile
WebSphere Voice Response has a default timeout of 5 seconds when waiting

for a grammar to compile. This timeout can be changed by modifying a
parameter in configuration file $DTJ_HOME/dtj.ini:
wvr.mrcp.read.timeout=value_in_milliseconds
For the change in dtj.ini to take effect, you must restart VRBE.
To do this, run the following commands:

dtjstop
dtjshost -exit
dtjshost
dtjstart
Note: The parameter change will have an affect on all MRCP responses, not
just grammar compilation.
Performance and other general problems
This section describes what to do when you experience one of the following
general problems:
v “A process does not start when you expect it to”
v “WebSphere Voice Response windows start without being selected” on page
84
v “The system runs extremely slowly” on page 84
v “WebSphere Voice Response telephony activity is unexpectedly disrupted”
on page 87
v “WebSphere Voice Response cannot access the printer” on page 88
v “WebSphere Voice Response is not accumulating call detail records” on
page 88
v “Frequent “without sending detach” messages” on page 89
v “WebSphere Voice Response does not shut down” on page 89
v “Screen is blank or frozen while WebSphere Voice Response is running” on
page 89
v “Alarm graphic turns yellow or red” on page 90
v “Applications and operations keywords turn gray” on page 90
v “Channel available indicator turns red independently” on page 90
v “Telephony problem without an alarm indicator” on page 90.
v “Licenses are not granted” on page 91
v “The system configuration GUI crashes when being closed” on page 92
v “/dev/systrctl1... message is displayed in Dtstatus.out” on page 93
v “File db2diag.log increases up to the AIX system limit” on page 93
v “WebSphere Voice Response VRBE OutOfMemory error” on page 94
A process does not start when you expect it to
After you have been running WebSphere Voice Response for a while, you
become familiar with the list of processes that WebSphere Voice Response
starts whenever it is initialized. If WebSphere Voice Response does not start a
process that you expect it to start, check the following:
Is the tasklist.data file corrupted or is there more than one file?
tasklist.data file. If one or more of the entries is missing, the system
might start but not be able to perform all of the required processing.
The tasklist.data file is located in the directory identified by the value
of the $SYS_DIR variable in the profile for the WebSphere Voice
Response AIX account ID. To list all the processes that are running,
open an AIX window by selecting an area in the screen background
and selecting AIX Login. Then type ps -u “===” (replacing === with
the WebSphere Voice Response AIX account ID you previously created

using vae.setuser), and press Enter. Compare the list of processes to
the list supplied in WebSphere Voice Response for AIX: Installation.
Check the $VAEBIN directory for a tasklist.data file. If it is present, it
overrides the file of the same name that is in $SYS_DIR directory.
If the tasklist.data file is corrupted, you must correct it and restart
WebSphere Voice Response. WebSphere Voice Response for AIX:
Installation contains instructions for checking and correcting the
tasklist.data file.
WebSphere Voice Response windows start without being selected
When WebSphere Voice Response is running, the window manager starts the
windows only when they are selected. If the window manager is starting
windows that have not been selected, check the following:
Is the focus policy set correctly?
The window manager focus policy is defined in a file
called.Xdefaults. WebSphere Voice Response for AIX: Installation
describes how to check the focus policy.
The system runs extremely slowly
When WebSphere Voice Response slows down, check the following:
Is the AIX operating environment set up correctly?
WebSphere Voice Response requires two AIX resources to run quickly:
page space (for swapping software into and out of memory) and
processes. The parameters that control how much page space the
system can use and how many processes it can start might not be set
correctly. Use the information provided in Chapter 2, “Analyzing the
problem,” on page 5 to determine how much page space is defined
and the maximum number of processes the system can start.
The system should have a minimum of 100 MB of page space. Use the
information given in WebSphere Voice Response for AIX: Installation to
increase the amount of page space.
The optimum value for the maximum number of user processes
parameter differs from system to system. Generally, you should set
the maxuproc parameter to a number equal to 150, +1 for every
telephone channel to which WebSphere Voice Response is connected
and +3 for each 3270 session that is defined. For example, if your
system has 24 telephone channels and 24 3270 sessions, maxuproc
must be set to at least 246. When you have determined the minimum
acceptable number, round it up to the nearest hundred. Then use the
information provided in WebSphere Voice Response for AIX: Installation
to reset the maxuproc parameter.
Is enough disk space available?
WebSphere Voice Response requires a minimum amount of free disk
space to avoid performance problems. Ensure that your system has
enough disk space in /home for your applications, and that you have
enough space in /var (see “Ensuring you have enough space for the
new software” in WebSphere Voice Response for AIX: Installation.)
Use the information provided in Chapter 2, “Analyzing the problem,”
on page 5 to find out whether your system has enough free disk
space. If there is not enough, clean up the file systems and recover
disk space. If you still do not have enough space available, you might
need to get additional disk space on the system.
For more information on managing disk space, see WebSphere Voice
Is there enough real memory (RAM) available?
Without adequate available memory, WebSphere Voice Response runs
very slowly. The more RAM that is available, the more quickly the
system responds. For example, a system with 48 channels and no 3270
sessions needs at least 128 MB of RAM. A system with 72 channels
and the same number of 3270 sessions should have at least 256 MB of
RAM for optimum performance.
To find out how much RAM is on your system, log on as root, type
lsdev -C | grep mem, and press Enter. If you do not have enough
RAM, you may have to add more.
Always ensure that the amount of page space that is defined exceeds
the amount of RAM fitted in the pSeries computer. Otherwise, you
might not be able to access all the RAM.
Are there enough buffers?
WebSphere Voice Response uses buffers for voice segments and other
state table components. It also uses them to pass data backwards and
forwards between internal processes and servers. You need enough
buffers to handle the permitted number of simultaneous calls. The
number of buffers is affected by the number of state tables, prompts,
and servers that are in use and by the number and type of voice
segments (compressed and uncompressed). Symptoms that indicate
insufficient buffers include the system running slowly, and the system
not handling or answering calls correctly.
Configuring the System to redefine the number of buffers.
Are buffers released quickly enough?
WebSphere Voice Response releases buffers that are holding voice
segments according to how long the segment has been in memory
since it was last requested. If the parameter that controls this timeout
is set too high, WebSphere Voice Response might not be able to
release the buffers quickly enough.

Use the Configuration —> System Configuration —> Application
Server Interface menus to find out the value of the Time in Cache
parameter and reset it.
Is the DB2® buffer large enough?
If the DB2 indexes have grown too large to be held in the DB2 buffer,
WebSphere Voice Response has to access the hard disk every time it
needs to look up information in the database. This is far slower than
accessing the buffer directly, and can cause long delays. This problem
is most likely to occur on voice messaging systems or systems that
have large numbers of WebSphere Voice Response objects.
As dtuser, type the following commands to increase the size of the
DB2 buffer pool:
db2 connect to dtdbv230
db2 alter bufferpool ibmdefaultbp size n
where n is the new size of the buffer pool in 4 KB units. The default is
1000 (4 MB).
Try increasing the buffer to 32 MB (n=8000) at first, or to 128 MB
(n=32000) if more space is needed.
Is the database manager timing out too quickly?
When the process that retrieves information from the database times
out too quickly, other processes that require the information (such as
voice applications) cannot complete their tasks. However, they keep
trying to access the database and failing, thus using system resources
and slowing down the system.
You should set the database timeout parameter, DBIM Time Out, to a
value of 240 seconds. Use the information provided in WebSphere Voice
Response for AIX: Configuring the System to check the value of this
performance parameter, and reset it if necessary.
Is there a deadlock between WebSphere Voice Response and DB2?
The following are common causes of deadlock problems:
v Runstats are not being run regularly on the database server. If
db2_runstats script is not run periodically, the database queries
become slower, and eventually lead to deadlocks. The script should
be set to run when 25% of the data in the database has been
changed. It is particularly important to run it when a high number
of subscribers are added to the database, or when a significant
change is made.
v Ensure that DB2_RR_TO_RS is set to ON. To check this, enter the
following commands:
1. Login as root
2. su - dtdb23in
3. db2set
If the value is not set to ON, enter DB2_RR_TO_RS=ON to set it. Then
log in as dtuser and enter the following commands to get the value
to take effect:
1. db2stop force
2. db2start
Are you using SSI?
If you are using single system image:
v Use the monitoring tools to ensure that the network is not
overloaded. See the section about monitoring the performance of a
single system image in WebSphere Voice Response for AIX: Configuring
the System.
v Use the standard AIX monitoring tools to ensure that the server
(the database server or the voice server) is not overloaded.
v Use the DTmon -f command to check performance statistics. For
information about the DTmon command, see WebSphere Voice
Is the var file system filling up
By default, when the JVM experiences a problem, a javadump file is
created in the /var/dirTalk/DTBE/native/aix directory. To stop the
var file system filling, it may be necessary to configure the system so
that the javadump files are generated in a different location. To do
this, export the following environment variable:
IBM_JAVACOREDIR=path to javadump
where path to javadump is the new location.
For a WebSphere Voice Response installation, this variable should be

set in $VAE/sw/environ/.vaeprofile.user
WebSphere Voice Response telephony activity is unexpectedly disrupted
On a production system, you should 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; it is deactivated when you move your mouse. When it is
deactivated, 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 trunks and channels are
temporarily 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.

WebSphere Voice Response cannot access the printer
When WebSphere Voice Response is connected to a printer (either directly or
through a network) but you are unable to print reports or other information,
Is the qdaemon running?
AIX uses a process called the qdaemon to manage printers. If the
qdaemon is not running, nothing can be printed. Use the AIX
documentation that came with the system to find out more about the
qdaemon.
Has the AIX printer definition been changed?
The printer is defined to AIX as a device. If the AIX device definition
is changed, WebSphere Voice Response can no longer access the
printer. Use SMIT to validate the printer definition in AIX.
Has the WebSphere Voice Response configuration been changed?
The WebSphere Voice Response configuration includes parameters that
define the printer. If the device definition that is part of the
WebSphere Voice Response configuration does not match the device
definition in AIX, WebSphere Voice Response cannot access the
printer. Use the information provided in WebSphere Voice Response for
AIX: Configuring the System to validate the WebSphere Voice Response
device definition.
Is the printer enabled?
Check whether the printer is enabled. You can use the AIX command
qadm -U’printername’ or enable printername where printername is the
name of your printer. You might need to be logged on to AIX as root
to run these commands.
WebSphere Voice Response is not accumulating call detail records
When WebSphere Voice Response does not collect statistics about individual
calls (call detail records), check the following:
Are you looking in the correct place?
If you are using a single system image cluster, note that call detail
records are stored on each individual client, not centrally on the
server.
Is WebSphere Voice Response configured to record the statistics?
Call detail records are one of the log files that WebSphere Voice
Response creates. However, WebSphere Voice Response creates the call
detail record files only when it is configured to do so. Use the
information provided in WebSphere Voice Response for AIX: Configuring
the System to reset the value of the Call Detail Record Logging
parameter in the WebSphere Voice Response parameter group to
cdr.log, DB2, or Both.
Frequent “without sending detach” messages
When the status window (or the error log) indicates that the system is
frequently sending messages that end with the phrase “without sending
detach”, check the following:
Is there a recent core file?
The existence of a recent core file indicates that the system is having a
problem. Although you cannot solve the problem yourself, IBM
support will want to know that the core file exists. The support
representative can guide you through the steps you need to take. To
check whether a recent core file exists , see “Looking for a recent core
file” on page 22.
WebSphere Voice Response does not shut down
When you select Immediate Shutdown or Quiesce Shutdown from the
Operations menu and the system does not shut down correctly, check the
following:
Have you waited long enough?
When the system is very busy, it might take a few minutes for it to
shut down, especially if you requested a Quiesce Shutdown.
Is NODEM or OAM running?
Unless the processes that respond to the shutdown request are
running, the system cannot shut down. To find out whether NODEM
and OAM are running, type ps -ef | grep NODEM and press Enter.
Assuming NODEM is running, type ps -ef | grep OAM and press
Enter. If one or the other is missing, stop WebSphere Voice Response
manually. Refer to WebSphere Voice Response for AIX: Installation and
follow the procedure that describes how to correct an incorrect display
name to stop the running processes.
Screen is blank or frozen while WebSphere Voice Response is running
If the screen goes blank or freezes (that is, moving the mouse has no effect on
the pointer), check the following:
Is the display still connected correctly?
If the cabling that connects the display you are using to the pSeries
computer (or the Xstation cabling) becomes loose, the display cannot
function correctly. Ensure that the display is firmly connected.
Is Xwindows still running? Are all the WebSphere Voice Response
processes running?
If the system has used all the available memory, AIX might stop the
window manager process (or another process) to allocate memory
elsewhere. Use the information provided in “WebSphere Voice
Response does not shut down,” to stop all the WebSphere Voice

Response processes and recycle it (shut it down and restart it). If this
action solves the problem, you might consider adding more memory
to your system.
Alarm graphic turns yellow or red
The System Monitor Alarm window displays the alarm messages that
WebSphere Voice Response is generating. As the system posts messages to the
Alarms window, the alarm graphic changes color so that it is always the same
color as the most urgent message. When the alarm graphic turns yellow or
red, check the following:
Have you deleted the message?
A yellow or red message usually requires prompt action. Use the
information given in WebSphere Voice Response for AIX: Configuring the
System to review the message. Then use the information from
Appendix B, “WebSphere Voice Response messages identified by
number,” on page 173 to respond to the message and solve the
problem. When you delete the last red or yellow message, the alarm
indicator changes color.
Applications and operations keywords turn gray
When you are using WebSphere Voice Response and the Applications and
Operations keywords on the Welcome window both turn gray, the processes
that control the voice application development functions have stopped
running. Use the information in WebSphere Voice Response for AIX: Configuring
the System to shut the system down, and then restart it (recycle the system).
Channel available indicator turns red independently
When the channel available indicator on the System Monitor channel graphic
turns red, it indicates that the channel is out of service. When a channel goes
out of service but has not been taken out of service, check the following:
Can you return the channel to service?
Use System Monitor window to put the channel in service. For more
information see WebSphere Voice Response for AIX: Configuring the
System.
Telephony problem without an alarm indicator
WebSphere Voice Response can experience telephony problems that do not
produce an alarm indicator. When the system is having such a problem, check
the following:
Are all the channels in service?
Use the System Monitor to display the status of all channels to which
the system is connected. If any channels are out of service, bring them
back into service. If the channels are all in service, the problem might
be at the switch end.
For more information, see WebSphere Voice Response for AIX:
Configuring the System book.
Have you reactivated the trunk?
Use the System Monitor to deactivate the trunk and then activate it
again. This action performs a limited set of diagnostics on the digital
trunk adapter.
If the diagnostics indicate there is no problem with the digital trunk
adapter, you can use the information in the Installation, Maintenance,
and Parts Catalog to perform a more complete set of diagnostics on the
adapter.
Have you performed a loop-back test?
For DTTA, refer to the IBM Quad Digital Trunk Telephony PCI Adapter
(DTTA): Installation and User's Guide to perform a loop-back test
between selected points in the system.
Is the telephone network connection through a CSU?
If your configuration includes a CSU, request a loop-back test from
the Central Office to the CSU.
Use signaling interface tracing to check whether your signaling
process is still processing signaling interface primitives correctly. For
information on tracing signaling interfaces, see WebSphere Voice
Response for AIX: Programming for the Signaling Interface.
Licenses are not granted
If a license is requested but cannot be granted, a WebSphere Voice Response
alarm is generated. WebSphere Voice Response will continue to run but you
must correct the problem immediately, as you are breaking your licensing
agreement.
Do you have enough licenses?
It is your responsibility to ensure that you always have sufficient
licenses for your needs. If you do not have enough licenses for your
current WebSphere Voice Response usage, you must order more
immediately.
Are your licenses correctly enrolled and distributed?
If you think that you have ordered enough licenses for your usage of
WebSphere Voice Response, but the licenses are not being granted,
they might not be correctly enrolled and distributed. To find out
which licenses are not being granted use the following commands:
ps -ef | grep LRS

The system displays the process ID (PID) for LRS.
kill -30 LRS_process_ID
A table of licenses that have been requested since WebSphere Voice

Response was started is displayed on the screen. License requests to
which a license was not granted are indicated by two asterisks.
For example:
Caller’s pid Type Count ProductID ProductName

** 25368 0 1 9900 WebSphere Voice
Response for AIX
** License was not granted

Try enrolling and distributing any licenses that are not being granted.
See WebSphere Voice Response for AIX: Installation for instructions.
Changes made to the license configuration might not take effect until
you have restarted WebSphere Voice Response.
Are your licenses split across concurrent groups?
Each time you distribute a set of licenses, License Use Runtime puts
these licenses into a separate concurrent group. These concurrent
groups can be accessed only one at a time. If WebSphere Voice
Response requests more than one license, they are only granted if
there are enough available licenses in a single concurrent group. For
example, if a full E1 trunk is enabled, WebSphere Voice Response
requests 30 channel licenses. Thirty channel licenses might be
available in total, but if they are not in the same concurrent group, the
request will be denied.
Use the procedure described in Are your licenses properly enrolled
and distributed? to determine which licenses are not being granted. If
the problem is with channel licenses and you have distributed your
licenses in more than one group, try removing any concurrent groups
that are not a multiple of 24 or 30 (depending on whether your trunks
are T1 or E1). Redistribute the licenses as a single group.
The system configuration GUI crashes when being closed
When closing system configuration windows from an X server emulator, the
system configuration panel crashes causing a core file RDX_RO.core to be
generated in the /var/adm/ras/dirTalk directory.
The problem is caused by the use of an incompatible X server emulator.
Check that the emulator being used fully supports the modal window type.
To do this, open a child window from the System Configuration panel, such
as Signaling Type. This window should take focus, so that you cannot click
back in the System Configuration window until the child window (in this case
Signalling Type) is closed. If you can click in the System Configuration
window whilst a child window is open then your emulator does not properly
support modal type windows.
Change to an emulator which fully supports the modal window specification.

/dev/systrctl1... message is displayed in Dtstatus.out
Sometimes the following message is written to the WebSphere Voice Response
for AIX status window.
/dev/systrctl1: A file or directory in the path name does not exist.
This message is displayed when the dtalarmd daemon process attempts to run
the command trcstop -1 without trace running. It is not an error, but just a
message sent to stderr. The most likely reason for this to occur is that IBM
Support requested that a change be made to the file dtalarmd.update, to assist
in problem determination, but the change was subsequently not then reversed.

1. Edit the file $SYS_DIR/dtalarmd.update. If there is an alarm_id entry with
a command parameter that calls the trcstop -1 command, review whether it
is appropriate to still have this entry in the file. If it is, do not change the
line.
Ensure that the trace command is running the next time the errorid
specified in the alarm_id entry is encountered. The trcstop -1 command
will then correctly stop the trace.
2. If the alarm_id entry is no longer required, delete or comment it out and
save the file.
3. Run the command DTalarmd -u to refresh the dtalarmd process. This
command does not affect the normal operation of WebSphere Voice
Response.
File db2diag.log increases up to the AIX system limit
The file size of /home/dtdb23in/sqllib/db2dump/db2diag.log can grow up to
the AIX system limit, while both WebSphere Voice Response and DB2 appear
to still be running normally.
The problem is caused by high levels of errors being generated from the DB2
database manager because the diagnostic level is incorrectly set.
To check the current setting for the level of diagnostic error that is reported:
1. Login using the account that you use to run WebSphere Voice Response
(the default is dtuser).
2. Type the following command to check the database manager
configuration:
db2 get dbm cfg | grep DIAGLEVEL

If the current value for DIAGLEVEL is greater than 3, you should reset it
back to the default level of 3 as follows:
1. Shutdown WebSphere Voice Response by running the command
DT_shutdown.
2. Change the diagnostic level parameter by typing the following command:
db2 update dbm cfg using DIAGLEVEL 3
3. Stop and restart DB2 to bring the changed parameter into use by typing:
db2stop
db2start
4. Restart WebSphere Voice Response.
dtjflog fails during logging
The dtjflog command can fail if the output of the tail -f command is
passed to it without also specifying a sufficiently large buffer size for the tail
command (using the -b option).
Using tail -f log.n.log | dtjflog during logging sends a partial log tag to
dtjflog, from which dtjflog may sometimes fail to recover.
The problem occurs because the log file is a binary file, and tail needs to use
512-byte blocks to subdivide the content rather than use newline characters.
Changing the number of 512 byte blocks to a large enough buffer size
removes the first partial tag from the output.
Use the command: tail -f -b 20 log.n.log | dtjflog where n is a number

in the range 1 through 10.
WebSphere Voice Response VRBE OutOfMemory error
If the WebSphere Voice Response VRNode reports OutOfMemory errors,
specifically JVMCI015 or JVMCL053 when there are a large number of VRBE
application instances it means that the C-runtime heap of the Java process
(not the Java object heap) is full. Errors JVMCI015 and JVMCL053 are
reported in the VRNode log file (which is /var/dirTalk/DTBE/dtj_logs/
Node1.out by default.)
To resolve this problem, complete the following steps:

1. Stop VRBE (dtjstop followed by dtjshost -exit).
2. Edit the file /usr/lpp/dirTalk/DTBE/native/aix/dtjshost and comment
out, or delete, the following line:
export LDR_CNTRL=MAXDATA=0x40000000
3. Restart VRBE (dtjshost followed by dtjstart).
Chapter 4. Using the ISDN_Monitor
This chapter describes how you can use the ISDN_Monitor to help with
problem determination.
The ISDN_Monitor
The ISDN_Monitor is designed to monitor an ISDN D channel without using
an expensive external ISDN line monitor. It receives events from the ISDN
Layer 2 protocol in WebSphere Voice Response rather than monitoring the
ISDN line directly. All the message flows that the ISDN_Monitor sees are the
same as those on an external ISDN line monitor, but if you need real timings,
you must use an external monitor.
The ISDN_Monitor displays and decodes Layer 2 frames and Layer 3

messages that are passed between the switch and WebSphere Voice Response
trunks.
The ISDN_Monitor is for:

v Problem determination in the field for installation
v Problem determination in the field for possible call-related problems from
you and from IBM support personnel
The ISDN_Monitor supports both E1 and T1.

Starting the ISDN_Monitor
To start the ISDN_Monitor, you must either be in the $VAEBIN directory, or
have your path set up to include this directory.
The ISDN_Monitor must be started after the ISDN trunk is enabled because it
sends a message to the active Layer 2 process telling it to start sending trace
message events. Layer 2 is active and running when the Disable and
Channels In Service buttons are enabled on the Pack.
To start the ISDN_Monitor from an AIX window command line, type the
following:
ISDN_MONITOR trunk_number
where trunk_number is the number of the trunk.

ISDN Layer 2 and 3 events are written to stdout so that they can be
monitored.
You can run more than one ISDN_Monitor on the ISDN trunks, but it is better
to run only one at a time because the large amount of information displayed
on the screen can affect system performance.
Stopping the ISDN_Monitor
You can stop the ISDN_Monitor at any time by using Ctrl+C. System
performance returns to normal when the ISDN_Monitor has been stopped.
Restarting the ISDN_Monitor
If you are running the ISDN_Monitor on a trunk, restart it by using the same
command that you used to start it.
Monitoring a trunk which is then disabled
The ISDN_Monitor does not terminate if you are monitoring a D channel and
the trunk is disabled. You must stop the ISDN_Monitor yourself by using
Ctrl+C. No tracing information is shown on the screen when you re-enable
the trunk until the previous instance of ISDN_Monitor is stopped, and a new
instance of ISDN_Monitor is started. This is because the ISDN Layer 2 process
is terminated after the trunk is disabled, and a new ISDN Layer 2 process is
started when the trunk is re-enabled.
Logging the ISDN_Monitor trace information to a file
If you want to run the ISDN_Monitor, and save the output to a file for later
analysis, there are two ways to do this:
v If you want the output written to the screen and to a file (called trace1.out
in this example) use the following command:
ISDN_MONITOR 1 | tee trace1.out
If you want the output written to the file only, use the following command:
ISDN_MONITOR 1 > trace1.out
Make sure that you have enough disk space for the file.
v Before you start the ISDN_Monitor,
1. Select the aixterm window.
2. Press Ctrl and the left mouse button.
3. On the resulting screen choose the 'Logging' option to log everything
that appears in the window to an 'Aixtermxxxxxxxxx' file. This file is
written to the home directory of the userid which started the aixterm
window.
Decoding the ISDN_Monitor output
The ISDN_Monitor decodes Layer 2 ISDN frames and Layer 3 ISDN
messages so that you can find out what is happening to calls on specific
channels.
Layer 2
WebSphere Voice Response frames that are sent to the network are on the
left-hand half of the screen. Layer 2 frames that are sent to WebSphere Voice
Response from the network are shown on the right-hand half of the screen.
Figure 1 shows the trace of a typical startup sequence in which the switch
sends a Synchronous Asynchronous Balanced Mode Extended (SABME) frame
to start the ISDN Layer 2 link, and WebSphere Voice Response responds with
a UA frame to verify that the Layer 2 link is established. If no Layer 3
messages are being sent at this point, there is a handshake protocol on
Layer 2 with RR frames (RR means receiver-ready; that is, ready to receive
frames). This handshake is at 10 second intervals.
Q921 NETWORK 12:24:31 TEI=00 Cmd

SAPI=00 U FRAME - SABME
Q921 DT/6000 12:24:31 TEI=00 Rsp
SAPI=00 U FRAME - UA
Q921 DT/6000 12:24:41 TEI=00 Cmd
SAPI=00 S FRAME - RR NR=000
Q921 NETWORK 12:24:41 TEI=00 Rsp
Figure 1. Trace of a typical startup sequence
Trace elements
The elements of the trace are:

v Timestamp in hours, minutes and seconds.
v Terminal Endpoint Identifier (TEI). Only TEI = 00 is supported on Primary
rate. (Broadcast TEI = 127 is not supported.)
v Service Access Point Identifier (SAPI). This is 00 for Call primitives. (SAPI
16 for X.25 and 63 for Broadcast messages are not supported.)
v Cmd/Rsp flag. This decodes the Layer 2 Command/Response Flag to
determine whether the Layer 2 frame is a command or a response. In
Figure 1 the SABME was a command and the UA frame was a response.
An RR frame that is sent as a command expects the other end of the
connection to respond to the RR command with an RR response as shown
in Figure 1.
v On the second line of the decode there are U, S, and I frames
(Unnumbered, Supervisory, and Information frames).
Chapter 4. Using the ISDN_Monitor 97

v Unnumbered frames are used to establish and release the Layer 2 link and
have no connection to the data that is sent across it.
SABME is sent to try to establish the Layer 2 link.
UA (Unnumbered Acknowledgment) is sent in response to a SABME to verify

that the Layer 2 link is established, or sent in response to a DISC when the
link is released.
DISC (Disconnect) is sent to release the Layer 2 link.
DM (Disconnected Mode) is sent in response to a SABME if the Layer 2 link

cannot start. This is also sent in some error conditions.
Supervisory frames are used to control the flow of the data frames across the
Layer 2 link:
v RR (Receiver Ready)
v RNR (Receiver Not Ready)
v REJ (Reject Frame)
These frames have an associated Number of Frames Received (NR) counter;

this is displayed on the trace.
Information frames contain the Layer 3 messages for call processing, and for
link and channel initialization. These frames are sent with the Number of
Frames Received (NR) and also a Number of Frames Sent (NS).
When an ISDN trunk is disabled, WebSphere Voice Response sends a DISC

frame to the switch to inform it that the link is released and is unusable. See
Figure 2.
Q921 DT/6000 12:48:44 TEI=00 Cmd

SAPI=00 U FRAME - DISC
SAPI=00 U FRAME - UA
Figure 2. WebSphere Voice Response sending a DISC frame to the switch
When the trunk has been enabled, a delay sometimes occurs before the switch
starts its Layer 2 protocol. WebSphere Voice Response tries to establish the
link if it has a Layer 3 message to send, so it sends up to four SABME frames
at one-second intervals (see Figure 3 on page 99). If the switch responds in
this time, the Layer 3 messages are sent; otherwise WebSphere Voice
Response waits for the switch to activate the link by sending SABME.
Q921 DT/6000 12:50:01 TEI=00 Cmd
Q921 DT/6000 12:50:02 TEI=00 Cmd
Q921 DT/6000 12:50:03 TEI=00 Cmd
Q921 DT/6000 12:50:04 TEI=00 Cmd
Figure 3. WebSphere Voice Response sending SABME frames at one second intervals
Layer 3
Normally, the first Layer 3 messages that are sent between the switch and
WebSphere Voice Response are restart messages, which initialize trunks or
channels into a predefined state so that they are ready to initiate or receive
calls. Figure 4 shows an example of a RESTART message initializing a whole
trunk.

SAPI=00 I FRAME NS=001 NR=000
Q931 <---- RESTART Ref=0000 Len=8 08 02 00 00 46
- 79 01 86
RESTART INDICATOR
3 : Single Interface
Q921 DT/6000 13:01:44 TEI=00 Rsp
Q931 ----> RESTART ACKNOWLEDGE Ref=8000 Len=8 08 02 80 00 4E
- 79 01 86
RESTART INDICATOR
3 : Single Interface
Figure 4. A RESTART message initializing a whole trunk
Layer 3 messages are displayed on the left hand side of the screen to allow
room for textual decodes. The direction of the message is shown by an arrow.
The previous Layer 2 frame decode of the I frame also shows the direction of
the frame.
The message shown in Figure 4 can be decoded as follows:

v Q931 = ISDN Layer 3.
v RESTART = Layer 3 message type.
v Ref=0000 = ISDN Layer 3 Call Reference. For channel and trunk messages,
this value is 0, but it is non-zero for call related messages. The Most
Significant Bit (MSB) is used to show which side initiated the event (for
RESTART) or which side initiated the call.
If the MSB=0, the call or event was initiated from that side. If it is set to 1,
it was initiated at the other side. You can see this by comparing the 'Ref'
fields on the RESTART and RESTART ACKNOWLEDGE messages.
v Len=8 = Length of ISDN message
v 08 02 00 00 46
– The first byte is the protocol discriminator. 08 is the one normally used,
but different values are used for maintenance control.
– The second byte is the call reference length. This is normally 2, but when
RESTART messages are received from some switches, it is 1.
– The third and fourth bytes are the Call Reference value in hexadecimal.
If the Call Reference length is only 1, only the third byte is used.
– The fifth byte (or fourth byte if it is not used for the Call Reference
value) is used as the Layer 3 message value. The value 46 is RESTART,
and 4E is RESTART ACKNOWLEDGE.
v After the first line decode, each Information Element (IE) is decoded with
the hex information displayed first.
v 79 01 86
– 79 = RESTART INDICATOR information element
– 01 = length of the Information element
– 86 = Octet 3 which is decoded as 'Single Interface'
The channel ID information element
The default in WebSphere Voice Response is to send RESTART messages to

the network whenever a channel is enabled. The Channel ID Information
Element tells the network which channel is involved, as shown in Figure 5 on
page 101.
In octet 3 “Interface Implicit” means that the identified B channel is on the

same trunk as the signaling channel.

Q921 DT/6000 14:00:00 TEI=00 Cmd
Q931 ----> RESTART Ref=0000 Len=13 08 02 80 00 46
- 18 03 A9 07 83 81
CHANNEL IDENTIFICATION
3 : Interface Explicit, Primary, Exclusive, Not D-Chan, Channel in
next oct
4 : CCITT standard, Channel number in next octet, B channel units
5 : Channel 01
- 79 01 80
RESTART INDICATOR
3 : Indicated Channels
Figure 5. The channel ID information element
Figure 6 shows NFAS on a channel enabled on a trunk with no signaling. The

overall length of the message has increased by 1 byte, the interface is defined
as 'Explicit' which means that the Trunk Identifier in Octet 3a is defined.
Q921 DT/6000 14:02:23 TEI=00 Cmd

Q931 ----> RESTART Ref=0000 Len=14 08 02 80 00 46
- 18 03 C9 07 83 81
3 : Interface Explicit, Primary, Exclusive, Not D-Chan, Channel in
next oct
3a: Trunk Id 07
5 : Channel 01
- 79 01 80
RESTART INDICATOR
3 : Indicated Channels
Figure 6. Trace showing NFAS on a channel enabled on a trunk with no signaling
Outbound calls
Figure 7 on page 103 shows the flow of call related events for an outbound
call from WebSphere Voice Response:
The definition of the messages in Figure 7 on page 103 is:

v SETUP is used to ask for a Service Type in the Bearer IE. The channel to be
used is requested in the Channel Id IE. The number to telephone is in the

Called Party Number field. WebSphere Voice Response does not send
Calling Party Number to the switch, but as a service option the switch may
send this IE.
v CALL PROCEEDING is used to inform WebSphere Voice Response that the
channel can be used.
v ALERT is used to inform WebSphere Voice Response that the other party is
processing the call, but has not yet accepted it. You can think of this as the
RINGING state.
v CONNECT means that the other party has accepted the call and a voice
path has been established.
This is the Trunk Identifier provided by your service provider. WebSphere

Voice Response must be configured to use this trunk identifier or all calls on
this trunk will be rejected with the cause code of channel unacceptable.

Q921 DT/6000 14:22:04 TEI=00 Cmd
Q931 ----> SETUP Ref=0001 Len=21 08 02 00 01 05
- 04 03 80 90 A3
BEARER CAPABILITY
3 : CCITT standard, Speech
4 : Circuit mode, 64kbit/s
5 : Layer 1 protocol G.711 A-Law
- 18 03 A9 83 81
3 : Interface Implicit, Primary, Exclusive, Not D-Chan, Channel in
next oct
5 : Channel 01
- 70 04 80 31 31 30
CALLED PARTY NUMBER
3 : Unknown, Unknown
4 : Number is 1 1 0
SAPI=00 RR FRAME NR=032
Q931 <---- CALL PROCEEDING Ref=8001 Len=10 : 08 02 80 01 02
- 18 03 A9 83 81
next oct
5 : Channel 01
Q921 DT/6000 14:22:05 TEI=00 Rsp
Q931 <---- ALERTING Ref=8001 Len=5 : 08 02 80 01 01
Q921 DT/6000 14:22:05 TEI=00 Rsp
Q931 <---- CONNECT Ref=8001 Len=5 : 08 02 80 01 07
Q921 DT/6000 14:22:06 TEI=00 Rsp
Chapter 4. Using the ISDN_Monitor
Figure 7. Flow of call related events for an outbound call from WebSphere Voice Response
103
Unsuccessful outbound calls
Some outbound calls are unsuccessful because channels are busy or telephone
numbers are invalid, Figure 8 on page 105 shows the trace from such a call.
The Cause IE, in the Release Complete message, gives the reason why the call
was failed or rejected. These cause codes are mapped onto edges in the
MakeCall state table action; in this case a Network Busy edge will be
returned.

Q921 DT/6000 16:12:04 TEI=00 Cmd
Q931 ----> SETUP Ref=0005 Len=21 08 02 00 01 05
- 04 03 80 90 A3
BEARER CAPABILITY
3 : CCITT standard, Speech
4 : Circuit mode, 64kbit/s
5 : Layer 1 protocol G.711 A-Law
- 18 03 A9 83 81
next oct
5 : Channel 01
- 70 04 80 39 39 30
CALLED PARTY NUMBER
3 : Unknown, Unknown
4 : Number is 9 9 0
Q931 <---- RELEASE COMPLETE Ref=8005 Len=9 : 08 02 80 01 5A
- 08 02 80 AC
CAUSE
3 : CCITT standard, User
4 : Requested circuit/channel not available
Q921 DT/6000 16:12:05 TEI=00 Rsp
Figure 8. Outbound call fails
Call clearing
Call clearing messages are defined as follows:

v DISCONNECT starts the call clearing process on the specified Call
Reference. You don’t have to specify channel id because there is a table in
each Layer 3 protocol which links Call Reference to a channel.
v RELEASE acknowledges the clearing message so that both sides know that
the call is being cleared. When the protocol receives a RELEASE message it
sends a RELEASE COMPLETE message to the other end and clears the call
fully from that side of the interface.

v RELEASE COMPLETE is returned to the side which sent the RELEASE
message. The call is now fully cleared. The channel on which the call was
allocated is now free for another call to be set up.
Figure 9 shows a trace of a call clearing.

Q931 <---- DISCONNECT Ref=8009 Len=9 : 08 02 80 01 5A
- 08 02 80 90
CAUSE
3 : CCITT standard, User
4 : Normal Call Clearing
Q921 DT/6000 16:15:09 TEI=00 Rsp
Q921 DT/6000 16:15:09 TEI=00 Cmd
Q931 ----> RELEASE Ref=0009 Len=5 08 02 00 09 AD
Q931 <---- RELEASE COMPLETE Ref=8009 Len=5 : 08 02 80 01 5A
Figure 9. Trace of a call clearing
Other ISDN messages

Other ISDN messages may occur. For more information:
On ISDN Layer 2 frames see
ITU-T Q.921
On ISDN Layer 3 messages or Information elements see
v ITU-T Q.931 standards
v ETSI (European Telecom Standards Institute) ETS 300 102-1 User-network
interface Layer 3
v The relevant 5ESS or Northern Telecom ISDN Primary Rate Interface
Specifications.

Chapter 5. Introducing the WebSphere Voice Response
alarm messages
WebSphere Voice Response monitors its own hardware and software
operations. When something happens that affects an operation, WebSphere
Voice Response documents the situation by generating an error message. The
WebSphere Voice Response error messages are listed in Appendix B,
“WebSphere Voice Response messages identified by number,” on page 173.
WebSphere Voice Response categorizes error messages according to how

severely the situation affects system operations. Error messages are also filtered
to ensure that a potentially destructive situation is called to your attention
and does not go unresolved for long.
WebSphere Voice Response generates a different set of messages during data

migration activities. These messages are described in Appendix A, “Messages
issued during migration or import,” on page 169.
Message destinations
Every error message that WebSphere Voice Response generates has three
potential destinations:
1. The WebSphere Voice Response error log
2. Alerts logged in the AIX error log or set as SNMP traps
3. The WebSphere Voice Response alarms console (viewed using System
Monitor or the ASCII console)
All error messages are recorded in the WebSphere Voice Response error log.
Some of the messages are also alertable to a remote manager, either via the
AIX error log or via SNMP, or sent to the WebSphere Voice Response alarms
console. The information about each message in Appendix B, “WebSphere
Voice Response messages identified by number,” on page 173 includes the
destination. For details of how to configure WebSphere Voice Response to
send alertable errors to NetView/390 or NetView for AIX via the AIX error
log or SNMP traps, see WebSphere Voice Response for AIX: Configuring the
System.
You can look at messages in the error log, using a text editor. The error log
includes complete information about a message.
WebSphere Voice Response for AIX: Configuring the System describes how to use
the System Monitor to review a message. The System Monitor displays

complete information about a message, including the explanation and user
response as shown in Appendix B, “WebSphere Voice Response messages
identified by number,” on page 173.
Message content
An entry in the WebSphere Voice Response error log is shown here, with an
indication of the line and column numbers:
Line 1 always has exactly the format shown—the details of the time vary but
the type of information in each column does not change. The string, EE Entry,
in the first eight columns identifies the start of a new error message.
Line 2 contains a brief description of the error. Its length varies but it always
begins in column 1.
Line 3:
sequence (1- to 6-digit number left-justified in columns 16 through 21):
The sequence number of the error. This number begins at 1 each time
WebSphere Voice Response is started, and is incremented for each
subsequent error.
csec (1- to 2-digit number left-justified in columns 36 through 37):
The number of 1/100 seconds (centiseconds) that this error was
generated after the time in line 1.
error_id (1- to 5-digit number left justified in columns 56 through 60):
The WebSphere Voice Response error message ID, as listed in
Appendix B, “WebSphere Voice Response messages identified by
number,” on page 173.

1 1 2 2 3 3 4 4 5 5 6 6 7 7
1...5....0....5....0....5....0....5....0....5....0....5....0....5....0....5
1 EE Entry Time: Fri Jan 14 10:30:04 1994
2 OAM Problem with File Access
3 sequence = 74 csec = 97 error_id = 25022
4 asi_id = 1 appl_id = 16 error_no = 52
5 severity = WHITE vpd_discr = VAE module_id = GENVAE
6 assoc_cls = NONE alarm_thr = 0 assoc_alm = 0
7 appl name = OAM
8
9 parameter type parameter value
10 ---------- ------ -------------------
11 process string OAM
12 routine string OAM_log_trace_string()
file string /usr/lpp/dirTalk/db
access string fflush
Figure 10. Message information in the WebSphere Voice Response error log
Line 4:
asi_id: In the current implementation, this field is always 1.
appl_id (1- to 4-digit number left-justified in columns 36 through 39):
The WebSphere Voice Response internal identifier of the process that
generated the error.
errno (up to 6 digit number left justified in columns 56-610):
The value of the AIX-defined global variable, errno, at the time the
error was generated. This is irrelevant for some errors, but an
important parameter for others. You can find definitions for these
errors in the errno.h in the /usr/include/sys directory.
Line 5:
severity: (1- to 6-character string in columns 16 through 21):
Indicates the severity of the error. Possible values are WHITE, GREEN,
YELLOW and RED. The meanings of these severities are defined in
“Message Categories”. This program examines the first character only,
and converts to the numbers 1,2,3, and 4 respectively.
vpd_discr:
In the current implementation, this field does not provide useful
information.
module_id:
In the current implementation, this field always contains GENVAE.
Chapter 5. Introducing the WebSphere Voice Response alarm messages 109

Line 6:
assoc_cls:
In the current implementation, this field is not used (contains NONE).
alarm_thr:
In the current implementation, this field is not used.
assoc_alm:
In the current implementation, this field is not used.
Line 7:
appl name (variable character string from column 16 to the end of the line)
This is the WebSphere Voice Response name of the process that raised
the error.
Line 8 is always a blank line. The following lines occur only if the error has
parameters. Otherwise the next line is blank followed by the start of the next
error.
Line 9: If the error has parameters, this line is exactly as shown in Figure 10
on page 109.
Line 10: This line is exactly as shown in Figure 10 on page 109, underlining
the previous line.
Line 11: The start of a parameter.

Columns 16 through 23:
The name of the parameter. The name is defined separately for each
parameter of each error.
Columns 26 through 36:
The parameter type: decimal, integer, long, uinteger, ulong,
hexadecimal, address, character, uchar, or string.
Columns 38 through the end of the line (and beyond):
The parameter value. This is always a character string, so numeric
type parameters have been converted to strings, in the format you
would expect. So for hexadecimal, for example, to extract the original
value you could use sscanf() on the parameter value, specifying a
number base of 16 for the conversion.
Note: The parameters can contain new-line characters, so parameters

can span multiple lines. This is, however, very rare. This makes
parsing harder, because it is not so obvious where the next parameter
starts. This program only collects the first line of a parameter value,
and detects the start of the next parameter by looking for three spaces

at the start of the line, followed by a non-space, and a space in
column 25 and non-space in column 26.
Line 12 onwards
Further parameters, until the end of the error, where there is a blank
line followed by the start of the next error. The error log never
contains partial error messages—all the information described is
included for each error.
Message categories
Every WebSphere Voice Response message is assigned to one of four
categories. Each category is identified by a color. When a message is posted to
the System Monitor, the message generates an alarm. The alarm graphic on
the System Monitor reflects the urgency of the messages that have generated
alarms. (For more information about the color of the alarm graphic, see
WebSphere Voice Response for AIX: Configuring the System)
The four message categories are:

Red A red message documents a condition that requires immediate
attention. For example, a message documenting the failure of an
adapter is a red message.
The condition generating a red message must be resolved
immediately. Otherwise, WebSphere Voice Response cannot continue
to operate reliably. All red messages are posted to the System Monitor.
Red messages are also written to the AIX NetView log.
Yellow
A yellow message documents a problem situation. The situation
requires recovery, either by the WebSphere Voice Response recovery
function or by your intervention. For example, a message
documenting that a task received an unrecognizable response to an
internal request is a yellow message. A message indicating that the
system is about to run out of disk space or memory is also a yellow
message.
While a condition generating a yellow message may not cause the
system to fail, operations will be less effective until the condition is
alleviated. All yellow messages are posted to the System Monitor.
Green
A green message documents an event that clears an earlier error
condition. For example, the system may have generated a yellow
message because of a shortage of disk space. The message indicating
that the condition has been alleviated and the yellow message has
been cleared is a green message.

Green messages are posted to the System Monitor when they
document an “error clear” condition or include instructions for you to
do something.
White
A white message documents a nonerror event. Messages documenting
routine system maintenance, for example, are white messages.
White messages are posted to the System Monitor when they include
instructions for you to do something.
“Messages affected by filtering” on page 163 lists the WebSphere Voice

Response error messages by category.
Message filtering
Red and yellow messages document situations in which time is of the essence.
By posting these messages to the System Monitor, WebSphere Voice Response
uses the alarm graphic to alert you to such situations.
Some messages document situations that if attended to immediately, represent

relatively minor problems, but if ignored, can create a major disaster. For
example, the system generates a yellow message to alert you to a shortage of
disk space. If you free disk space immediately, there is usually no impact on
the system. But if you do not free disk space, the system may run out of space
and stop operating.
To help ensure that you resolve situations requiring prompt attention before it
is too late, WebSphere Voice Response filters all error messages. When the
filtering process determines that the rate at which the message is being
generated exceeds the predetermined threshold for that message, the system
increases the severity level of the message and may also route the message to
additional destinations.
For example, error message 5010 documents a situation in which the system
cannot retrieve information from the WebSphere Voice Response database.
This message is classified as a yellow message. The system sends the message
to the WebSphere Voice Response error log and also posts it to the System
Monitor, which displays a yellow alarm. If the system generates the message
12 times in 60 seconds, the filtering process reclassifies the message as red.
WebSphere Voice Response then sends the message to the AIX NetView log as
well as to the WebSphere Voice Response error log and to the System Monitor,
which displays a red alarm. The filtering process thereby encourages you to
attend to a potentially dangerous situation before the situation is out of
control.

The filtering process only affects certain predetermined messages. Both the
messages that are affected by filtering and the predefined threshold for each
message are listed in “Messages affected by filtering” on page 163.
Messages by severity
This section lists the numbers of the WebSphere Voice Response messages in
each color category.
This table Lists these messages
Table 2 Red
Table 3 on page 127 Yellow
Table 4 on page 151 Green
Table 5 on page 154 White
For detailed information about each message, see Appendix B, “WebSphere

Voice Response messages identified by number,” on page 173.
Red messages
Table 2. WebSphere Voice Response messages classified as Red
Message Number Message Text
2002 Channel process manager initialization failed
2003 Internal channel process manager error
5001 Cannot receive data from message queue
5002 Task initialization failed. Process exiting.
5003 Unable to attach to message queue. Process exiting.
5004 Could not allocate memory. System call malloc() failed.
5005 Notify_appl() failed
5007 Invalid file permissions

Table 2. WebSphere Voice Response messages classified as Red (continued)
5008 Get buffer blocks failed
5054 Request received with invalid data
5055 Invalidate failed
5056 Invalidate state table failed
5057 Invalidate prompt directory failed
5059 Invalidate var map relations failed
5061 System call fork() failed
5063 Create file or table failed (dmscrea or dmstopn)
5064 Create index failed (dmscrei or dmsicre)
5078 File type corrupted
5079 Function type corrupted
5093 Recover DMS failed
5095 Key is reserved: access not permitted
5103 Siglib error setting message waiting indicator
5200 SQL database transaction or request failure
5301 Database server down
5310 DBHEALTH reports problem with CUR_DIR files
5312 DBHEALTH reports problem with CUR_DIR or DB2
5313 DBHEALTH problem with CUR_DIR or DB2

5315 DBHEALTH DB2 Database problem
5316 DBHEALTH DB2 Database Fetch data length error
5317 DBHEALTH reports problem with CUR_DIR
10001 Could not fork a child process
10002 Could not execute the child process
10006 Attempt to allocate shared memory failed
10007 Attempt to allocate semaphore failed
10008 Attempt to allocate message queue failed
10012 Node manager message queue removed
10022 Abnormal termination detected in previous WebSphere Voice

Response execution
10100 System startup error
10101 Failed to execute initialization script
10500 Database and file system integrity check failed
13008 License request has failed because of hard-stop
13014 License request has failed because the license is unauthorized
14006 SMSI error retrieving sysparm data
14007 SMSI error opening tty device
14023 SMSI: signalling library call failed
14026 SMSI: could not connect to siglib
14027 SMSI: MWI database error

17001 I/O memory exception
17002 Telephony hardware not interrupting
17003 Channel error on pack
17004 E1 or ethernet signal loss qualified alarm
17005 E1 2MB alarm indicator signal qualified alarm
17006 E1 frame alignment loss qualified alarm
17007 E1 remote alarm indicator qualified alarm
17008 E1 excessive error qualified alarm
17012 T1 or ethernet loss-of-signal qualified alarm
17013 T1 alarm indicator signal qualified alarm
17014 T1 remote alarm indicator qualified alarm
17015 T1 out-of-frame qualified alarm
17033 Signalling software error
17061 Digital trunk adapter: irrecoverable status
17063 Power supply unit failure (dual configuration)
17068 Device driver counter corruption detected
17300 PCI adapter exception detected
17301 Pack failure reported by telephony adapter
17302 Telephony adapter detected failure
17305 DTTA adapter failure.

17600 TDM clock daemon died
17605 Armed master device failed to take over disabled master
17606 Internal error in TDM clock daemon
17607 TDM clock daemon experienced out of memory condition
17608 TDM clock daemon cannot find any telephony adapters
17610 TDM clock fork failed
17710 DSP microcode could not be loaded onto a DTTA adapter.
17800 Not enough parameters provided to startup diagnostics
17803 Unexpected error code reported by diagnostics
17805 Tested ARTIC card is not a telephony adapter
17806 Adapter flash PROM power-on self test failed
17807 Failed to access adapter components
17808 Adapter AIB VERO component test failed
17809 Telephony adapter VPIC component test failed
17810 SC4000 component test failed
17811 AIB diagnostics cannot open SC4000 device driver
17812 Unexpected software error during AIB startup diagnostics
17813 SCBus connection problem between telephony adapters
17820 Telephony adapter diagnostics cannot open device driver
17821 Unexpected software error during pack startup diagnostics

17826 Failed to load microcode file from system unit to adapter
17900 Failed to add stanza information to ODM database
17901 Failed to define device
17902 Failed to configure device
17903 Failed to create telephony adapter devices
17904 Failed to clean up telephony adapter devices
17905 Invalid parameter passed to script
17906 UNUSED
17907 Failed to unconfigure device
17908 Could not load file onto telephony adapter
17909 AIB initialize procedure failed
17910 ioctl to telephony adapter device failed
17911 File not found
17912 File not executable
17913 Syntax error invoking DTQA_ioctl program
17914 DTQA_ioctl program could not open device file
17916 DTQA_ioctl program error on ENABLE
17917 Not enough parameters when calling script
17918 UNUSED
17919 UNUSED

17920 Cannot move device from undefined to defined state
17921 Cannot move device from undefined to defined state
17922 Cannot move device from defined to undefined state
17923 Cannot move device from defined to available state
17924 Cannot move device from available to defined state
17925 Cannot add device information to PdDv class of ODM
17926 Cannot undefine all WebSphere Voice Response information

from ODM
17929 Root permission required to run tool
17931 DTQA_ioctl program could not query packs present
17932 DTQA_ioctl program returned invalid output
17933 DTQA_ioctl program failed
17934 Kernel extension already loaded
17935 dtdd define method failed
17942 Configuration method failed to get vital product data (VPD)

from hardware.
17943 Configuration method failed to get vital product data (VPD)

from hardware.
17944 Configuration method called with invalid parameters
17946 Configuration method failed to access ODM
17947 Configuration method failed to lock ODM
17948 Configuration method failed to lock ODM

17949 Configuration method failed to find expected data in ODM
17950 Configuration method failed to find data in ODM
17951 Configuration method called with device already available
17952 Configuration method failed to load kernel extension into

memory
17953 Configuration method failed to allocate a major number
17954 Configuration of logical device failed
17955 Configuration of logical device failed
17956 UNUSED
17957 UNUSED
17958 UNUSED
17961 odmadd failed to set up telephony adapter interrupt priority
17962 rmdev failed to remove an ARTIC device
17963 mkdev failed to make an ARTIC device available
17964 Adapter card not set up with high enough interrupt priority
17965 Failed to start tdmclockd daemon
17966 DTQA_ioctl program error on ENABLE
17967 Device driver I/O failure
17969 Device driver lost communications link to embedded software
17970 Adapter failure reported
17972 TDM hardware failure reported by telephony adapter

17973 Telephony adapter driver detected invalid size on primitive
17974 Telephony adapter driver ran out of CCS receive mbufs
17976 UNUSED
17979 Error found by adapter HAL (hardware access layer) or other

related software
17980 A wrap plug is installed in the telephony adapter cable socket
17981 Cable with unknown ID installed in telephony adapter
17982 No cable installed in telephony adapter
17983 Errors found testing SCBus connection to telephony adapter
17986 DTTA adapter could not be reset.
17987 DTTA adapter could not be loaded.
17988 DTTA adapter failed to load DSP microcode
17990 DTTA trunk type could not be set.
17991 Uncompressed dump of a DTTA adapter failed.
19006 ACL: error retrieving sysparm data
19007 ACL: error opening mpq device
19023 ACL: signalling library call failed
19026 ACL: cannot connect to siglib
19030 ACL: cannot access iconv functions for ASCII to EBCDIC

conversion
19031 ACL: iconv failed for ASCII to EBCDIC conversion

20504 Custom server user-defined red alarm
20603 SS7 component red alarm
23002 Error accessing database
23003 Error attaching queue
23004 Error allocating memory
23009 SMSERVER discarding statistics messages
24913 Call to malloc() failed in SNA library
24914 SNA system status could not be retrieved
25005 OAM test alert message for console
25028 OAM pool buffer alert message
25032 OAM process alert message
25039 OAM file system alert
25045 OAM process restart failed
25068 OAM test: sample SW alert test
25069 OAM test: sample HW alert test
25072 OAM corrupt buffer
25088 SNA attachment inactive
25100 OAM test message AIXLOG alert
25107 OAM time out on automatic enabling of trunks
26001 SNMP smux error

26002 SNMP read objects error
26003 SNMP agent text20bj error
26005 SNMP object entry not found
26006 SNMP smux registration error
26007 Smux PDU close error
26010 SNMP message queue attachment error
26011 SNMP failed access to system parameters
26012 SNMP failed attach to 3270 shared memory
26013 SNMP failed initializing SS7
27010 Pack enablement failed
27016 Diagnostics failed
27046 SDI failed to enable pack because signalling process was missing
27047 SDI: pack type changed while WebSphere Voice Response was
running
27048 SDI timed out on pack diagnostics
27055 SDI detected signalling process termination
27056 SDI timed out on trunk enable request to signalling process
27058 SDI enable trunk failed by signalling process
27062 SDI failed to initialize with signalling library
27065 Trunk disable requested by signalling process

27066 SDI enable channel failed by signalling process
27080 Pack has failed too many times. Re-enable cancelled.
27081 Telephony adapter has failed too many times. Re-enable

cancelled.
27084 Trunk Enable Failed due to missing TDM Management
29111 Insufficient disk space for ISDN environment services
29203 ISDN signalling process initialization failure
29209 ISDN signalling process executable could not be found
29210 ISDN signalling process could not start Layer 3
29211 ISDN signalling process could not start Layer 2
29217 ISDN signalling process trunk error
29218 ISDN signalling process detected Layer 3 death
29219 ISDN signalling process detected Layer 2 death
29400 Invalid ISDN Layer 3 task number passed from call control
29401 ISDN Layer 3 user initialization parameter error
29402 ISDN Layer 3 initialization parameter error
29403 ISDN Layer 3 internal error
29601 Invalid ISDN Layer 2 task number passed from call control
29602 ISDN Layer 2 user initialization parameter error
29604 ISDN Layer 2 failure opening/closing D channel access via

device driver

29605 ISDN Layer 2 failure. No response from ISDN Layer 1

microcode.
29608 ISDN Layer 1 failure to activate when enabled
29610 ISDN Layer 2 detected invalid incoming frames
29612 ISDN Layer 2 had an error trying to start its child process
29613 ISDN Layer 2 failed to stop its child process
29614 ISDN Layer 2 child died
29615 ISDN Layer 1 discarding incoming messages. Lack of buffers in

pool.
29617 ISDN Layer 3 is unable to process an incoming call.
29800 VoIP Media (UPA) Internal Failure
29802 VoIP H323 signalling process Internal Failure
29804 VoIP SIP signalling process Internal Failure
29809 VOIP signalling process initialization failure
29814 VOIP signalling process could not start Layer 3
29820 VOIP signalling process trunk error
29821 VOIP signalling process detected SIP Layer 3 termination
29823 Ethernet not in sync

29825 SIP Register Failed To Contact Registrar
29829 VoIP SIP Layer 3 Has Terminated


29831 VoIP SIP Layer 3 Will Not Be Restarted
29832 Allowed Hosts List Could Not Be Read
30001 D7 software component failure
30002 D7 request rejected
30003 D7 Configuration Problem
30018 Configuration Information not Loaded
30019 System Problem
30024 SS7 Link Not Active
30027 D7 Environment problem
30028 DTTA Loopback
30038 SS7 Environment Problem
30045 E1/T1 - Mixed Trunk Standards
30048 D7WVRErrorReport Custom Server
30100 SS7 - Distributed7 Not ready
30101 Distributed7 Initialisation Problems
30109 Signaling Library message for non-bearer circuit
30110 SS7 message for non-bearer circuit
30111 SS7 Error message for non-bearer circuit
30112 Block Pending SS7 Error message
30113 Distributed7 has issued a circuit reset
30203 SS7 Stack D7 - reports critical alert

30204 SS7 Stack D7 - reports fatal alert
30211 Machine removed from SS7/D7 Cluster
30218 SS7 - Distributed7 reports a LinkSet is DOWN
30219 SS7 - Distributed7 reports a Link is DOWN
30223 SS7 - Distributed7 has reported a Destination is UNAVAILABLE
30504 TDM connection management: connection server error (red)
30506 TDM connection management: configuration error
30507 Software error detected in TDM connection management
30508 TDM connection management aborted
32001 Signalling interface: task initialization failed
32002 Signalling interface: open device failed
32004 Signalling interface: polling error
32014 Signalling interface: device driver queue for CCS full
32017 Signalling interface: invalid trunk on alarm event from driver
32018 Signalling interface: invalid channel on alarm event from driver
Yellow messages
Table 3. WebSphere Voice Response messages classified as Yellow
1 Internal channel process error
2 Start/restart or initialization failed

Table 3. WebSphere Voice Response messages classified as Yellow (continued)
3 Call processing error
100 Action parameter invalid
101 Server data invalid
105 Error return from host request
106 Host server failed
110 Server timeout
111 Error receiving data from custom server or 3270 server
116 Could not translate key
117 DPRB manager function failed
199 State table action request timeout
200 State table request timeout
201 Voice buffer underrun
203 Cache request timeout
207 DBIM request timeout
209 Mailbox request timeout
211 Profile request timeout
214 Timed out waiting for disk space information
300 Voice segment not found
400 Profile not found
401 Default profile not found

402 Profile deleted in use
403 Invalid caller mailbox ID
404 Profile unlock request not granted
405 Audio name not found
406 No profile ID
407 No profile ID
408 User greeting not found
409 Invalid schedule ID specified
500 State table not found
501 State table nesting too deep
502 State table has not been validated
503 State ID not found in table
504 State label not found in state table
505 Parameter mismatch in InvokeStateTable area
507 Application loop detected
600 Prompt directory not found
601 Prompt not found
603 No prompt directory specified in state table
604 Unable to interpret operation in prompt description
605 Prompt directory could not be retrieved

620 System cannot retrieve specified variable
621 System cannot set the requested variable
624 Action failed during host execution
630 Host session received unknown request
650 Unexpected status found in DPRB
700 Could not create voice message.
701 Message request failed
702 Tried to delete invalid message
703 Distribution list request timed out
704 Distribution list request failed
705 Distribution list update request timed out
706 Distribution list update request failed
707 Action failed because of no valid message in mailbox
708 Action failed because of no valid message in workspace
800 Voice table not found
801 Voice table entry not found
810 Invalid variable assignment
900 System parameter undefined
901 System parameter invalid
906 System parameter for function key undefined or invalid

1000 Application error: invalid request # in data block
1001 Application error: invalid function or subfunction
1100 Could not initialize local variable table. Cannot start check.
1202 No line assigned
1300 Background music action failed
1304 Could not set requested channels
2000 Could not obtain memory buffers
2004 Channel process manager received invalid message
2006 No free channel processors could be allocated
2007 Low free channel process warning
5010 Unable to open database file
5027 Write failed
5031 Read failed
5036 File delete failed
5039 File compression failed
5045 Segment retrieve failed
5062 Open file or table failed (dmsopen or dmstopn)
5067 Add record failed (dmsadd)
5068 Get record by key failed (dmsgetk)
5069 Get record sequentially failed (dmsgets)

5070 Get record by RBA failed (dmsgetd)
5071 Deletion of row/record/table/file failed (dmsdelt)
5072 Modify record failed (dmsmod)
5073 Modify record failed (dmsmodc)
5074 Commit failed (dmscmit)
5076 Get record key failed (dmskey)
5077 Get record by address failed (dmsrba)
5082 Attempt to update nonexistent unit
5083 Could not make file name
5084 Select on table failed (dmsslct)
5085 Update row failed (dmsupdt)
5086 Fetch row failed (dmsftch)
5087 Insert row failed (dmsisrt)
5088 SGAM data unit locked
5089 No application level lock buffer available
5090 File descriptor list full
5094 Vital statistics corrupt
5097 Internal programming error
5201 Database connection failed
5250 __OM_OpenVoice returned an error

5251 __OM_CloseVoice returned an error
5252 __OM_GetVoice returned an error
5253 __OM_GetVoiceHdr returned an error
5254 __OM_PutVoice returned an error
5255 __OM_PutVoiceHdr returned an error
5256 __OM_DeleteVoice returned an error
5257 __OM_SaveVoice returned an error
5319 Invalid msg creation time detected
5320 System clock jumped
5322 Invalid msg sent time detected
10003 Could not start executable file
10013 System parameters file corrupt
10023 Signalling library configuration problem
11001 No table entries available
11003 Table received with bad CRC
11004 Routine called with invalid request
12001 Task_init() failed
12002 Msgrcv() failed
12003 Msgsnd() failed
12004 Pool_get() failed

12006 Malloc() failed
12007 Attachs() failed
12008 Attachq() failed
12009 Attachm() failed
12010 Invalid message type
12020 Signal setup failed
12021 Error enroll failed
12202 Message pointer is null. Cannot send message.
12250 Target appl_id not channel process
12252 DPRB circular buffer overflowed
12253 Invalid event type
12305 Core file created
12401 Truncated voice file detected
13001 License Request Server initialization failure
13002 LRS attempt to attach queue failure
13003 LRS attempt to clean up requested licenses failure.
13004 LRS failed to get storage from buffer pool.
13005 LRS attempt to initialise the License Use Manager failed.
13006 LRS attempt to receive a message from its queue failed

13007 LRS received bad message format on its message queue
13009 Request for license has failed.
13010 Release of license has failed.
13011 Request to keep a requested license has failed.
13015 License Use Management communication error.
13016 License Use Management server is not communicating.
13017 License request has failed because the license is not installed
and distributed.
13020 LRS client attempt to attach queue failure
13021 LRS client failed sending a message to its queue
14003 SMSI error writing to tty port
14004 SMSI error reading tty port
14005 SMSI: invalid message received
14008 SMSI error writing termio configuration
14015 SMSI: invalid line ID received
14016 SMSI: invalid calling number received
14017 SMSI: invalid called number received
14024 SMSI: MWI NAK retry failure
14025 SMSI: error sending hang-up request to siglib
14029 SMSI: invalid calling number length
14030 SMSI: invalid called number length

14031 SMSI: invalid MWI number length
14032 SMSI: invalid number configuration
15013 Cachem released segment before minimum time
16004 System parameter DBIM Time Out undefined
17009 E1 64KB alarm indicator signal qualified alarm
17010 E1 multiframe alignment loss qualified alarm
17011 E1 multiframe yellow qualified alarm
17016 T1 bi-polar violation qualified alarm
17035 Network does not respond
17036 Bit fault cleared
17038 Signal detected but could not establish call
17040 Ring on pulse exceeded expected width
17041 Ring off pulse exceeded expected width
17042 A-bit fault
17043 B-bit fault
17045 C-bit or D-bit fault
17046 Outbound call failed on Feature Group D
17060 Digital trunk adapter missed handshake
17069 Digital trunk adapter: slave parity error
17070 Digital trunk adapter: memory diagnostic error

17303 Runaway clock on pack
17304 CCS transmit error on telephony adapter
17509 Improper passing of local message
17601 TDM clock received error while polling device driver
17602 TDM clock event missing
17603 TDM clock event is invalid
17604 TDM clock event inconsistent with state of the adapter
17609 TDM clock ioctl failure
17968 Device driver error queue overflow
17971 WebSphere Voice Response failed to service adapter interrupt

fast enough
17975 Token ring adapter and telephony adapter coexistence warning
17977 SCBus problem detected by telephony adapter embedded

software
18002 Cannot receive request from VAGIO
18004 Notify Appl failed
18015 Malloc failed
18400 State symbolic to relative translation error
18401 State relative to symbolic translation error
19027 ACL: internal error
19028 ACL: link failure

19032 ACL: repeatedly failed to set monitor status
19033 ACL: HICOM rejected a request to set monitor status.
19034 ACL: internal error occurred during monitor processing
20001 CA entry requested not found
20002 Attempt to allocate memory failed
20003 Attempt to get system parameter failed
20004 Channel process link count for this CA is invalid
20006 Message to send has been corrupted
20007 Attempt to exec a process failed
20009 Request for all CAs not received
20010 Environment variable missing
20015 Failed to update length in newly created voice message
20016 Custom server function not called in initial thread
20017 Different software versions detected in custom server
20018 Requests already pending on custom server at

OpenHostServerLink
20019 Custom server missing or not executable
20020 Parameter conversion error
20022 Problem with file
20503 Custom server user-defined yellow alarm
20602 SS7 component yellow alarm

21001 DTBE initialization failure
21002 DTBE Failed to start Host Manager
21003 DTBE Failed to configure Environment
21004 DTBE Failed to start WebSphere Voice Response node.
21005 DTBE Failed to stop WebSphere Voice Response node.
23005 SM_SRVR: error retrieving environment variables
23007 sm_stat_send: invalid command received
23008 sm_stat_send: invalid message length
24007 System parameter information could not be retrieved
24010 LU pooling command failed
24302 LU session release failed
24303 LU session deactivation failed
24306 Fatal host error occurred
24307 Non-fatal host error occurred
24503 Internal stack underflow has occurred
24504 Internal stack overflow has occurred
24507 Script attempted invalid arithmetic operation
24508 Script attempted invalid comparison operation
24509 Script referred to invalid symbol identifier
24510 Script attempted invalid evaluation operation

24511 Script attempted invalid jump operation
24513 Invalid state occurred following exception processing
24514 Invalid state occurred returning from called script
24601 Invalid special command received
24602 Script invoked with invalid parameter type
24603 Application allocation type invalid
24701 Pool_get operation failed
24702 System parameter information retrieval failed
24704 Poolput operation failed
24705 Buffer chain contained incorrect count information
24706 Buffer chain contained incorrect count information
24801 Message receive system call failed
24802 LU pooling path lookup failed
24803 LU pooling table creation failed
24804 Executor process fork failed
24902 3270 configuration information could not be retrieved
24907 Invalid screen identifier detected
24908 SNA version information could not be retrieved
24909 SNA command could not be run
24911 SNA message catalog could not be opened

24912 SNA NLS message could not be retrieved
24915 Unable to retrieve application data from database
25001 OAM task initialization failure
25002 OAM attempt to attach queue failure
25003 OAM attempt to get VPACK sysparms failure
25006 OAM unknown requestor
25007 OAM cannot notify application
25008 OAM received unknown request
25010 OAM received unknown notification
25011 OAM received unknown message type
25012 OAM message receive failed
25015 OAM received invalid request for periodic report
25016 OAM cannot get buffer pool
25017 OAM unknown channel status
25018 OAM unknown WebSphere Voice Response status
25019 OAM exceeded maximum processes
25020 OAM unknown process status
25021 OAM bad periodic action schedule
25022 OAM problem with file access
25026 OAM library problem

25027 OAM pool buffer warning message
25030 OAM test warning message
25034 OAM messages for console overflow
25036 OAM received bad periodic action request
25037 OAM received unknown report request
25038 OAM file system warning
25041 OAM invalid data received
25043 OAM problem executing database cleanup
25047 OAM schedule queue full
25048 OAM tried to read empty queue
25049 OAM unknown errparm handle type
25050 OAM unknown error report type
25054 OAM test: junk in string parameter
25055 OAM test: label/parameter mismatch
25056 OAM test: chars sent to decimal desc
25057 OAM error reading sysparms
25060 OAM ODM error
25061 OAM could not allocate memory
25063 OAM failure in system parameter database
25064 OAM error getting sysparms from DBMS

25070 OAM could not retrieve NetView sysparm
25071 OAM invalid pointer to memory
25073 OAM CPU usage warning
25076 OAM error getting list of LU connection info
25077 OAM invalid request for session
25079 OAM invalid session status
25080 OAM invalid executor status
25081 OAM semaphore error
25092 OAM has detected that CHP has died
25093 Bad return code (vp_open_vpack)
25094 Bad return code (vp_get_lost_call_recs)
25095 Bad return code (vp_close_vpack)
25096 Unassociated call record
25103 OAM bad return code from ioctl: speech recognition statistics
25104 OAM bad return code from malloc: speech recognition statistics
25106 OAM bad return code from Notify_appl sending speech

recognition stats
25200 Underrun margin time less than defined threshold value
25202 Play latency time greater than defined threshold value
25204 Profile retrieval time greater than defined threshold value

25206 Time to check voice messages greater than defined threshold

value
27003 SDI message queue has disappeared
27004 System reached the maximum number of processes or is out of

memory
27006 SDI failed to configure device
27007 SDI received message with incorrect format
27011 SDI: ODM error
27012 SDI failed to quiesce a trunk or channel
27013 SDI failed to configure a channel group
27014 SDI received alarm from device driver
27019 SDI failed to open pack
27020 SDI failed to access system parameters
27021 SDI failed to make signalling library call
27022 SDI cannot load system parameters
27025 SDI could not notify CHPM
27032 SDI found invalid telephony parameter
27035 SDI message queue problem
27036 Bad parameter on signalling library request sent from SDI
27037 Invalid common channel signalling trunk configuration
27043 Signalling process reconfiguration problem

27044 Signalling library message: sequence number not expected
27049 SDI timed out on resetting voice recognition statistics
27050 SDI timed out on trunk reconfigure request to signalling process
27051 SDI timed out while disabling a pack
27052 SDI timed out while enabling a channel
27053 SDI timed out while disabling a channel
27054 SDI timed out while disabling a channel
27057 SDI timed out on trunk disable request to signalling process
27059 SDI disable trunk failed by signalling process
27060 SDI quiesce trunk failed by signalling process
27061 Enable trunk failed setting pack use
27067 SDI disable channel failed by signalling process
27068 SDI quiesce channel failed by signalling process
27071 SDI failed accessing error channel
27074 Telephony adapter loading exceeded warning threshold
27078 Telephony adapter interrupts have drifted together
29001 ISDN failure to activate
29002 ISDN D channel protocol error
29003 ISDN D rejected call
29100 Invalid ISDN environment services buffer address

29101 Storage overwrite in ISDN environment services buffer
29102 ISDN task attempted to use uninitialized message queue
29103 Failed system call within ISDN
29104 ISDN holding bay is full
29107 Error putting ISDN message from holding bay to queue
29108 ISDN environment services buffer pool is empty
29110 ISDN environment services buffer pool audit problems
29112 ISDN environment services file locking error
29200 ISDN signalling process call state machine error
29201 ISDN signalling process channel state machine error
29202 ISDN signalling process trunk state machine error
29204 ISDN signalling process configuration error
29205 ISDN signalling process signalling library error
29206 ISDN signalling process environment services error
29207 ISDN signalling process internal error
29212 ISDN call state machine invalid primitive
29213 ISDN channel state machine invalid primitive
29214 ISDN trunk state machine invalid primitive
29215 ISDN signalling process invalid primitive
29216 ISDN signalling process channel error

29220 ISDN signalling process cannot make call on alarmed trunk
29221 ISDN signalling process tag processing error
29222 ISDN signalling process unable to send IE
29223 ISDN Redial Limitation: Call Denied
29224 ISDN Redial Limitation: Failed Call List Full
29404 ISDN Layer 3 recoverable internal error
29411 ISDN Layer 3 had Layer 2 data link timer expiry
29412 ISDN Layer 3 invalid ISDN primitive detected
29413 ISDN Layer 3 primitive sequence error detected
29607 ISDN Layer 1 invalid primitive received
29801 VoIP Media (UPA) Internal Warning
29803 VoIP H323 signalling process Internal Warning
29805 VoIP SIP signalling process Internal Warning
29806 VOIP signalling process call state machine error
29807 VOIP signalling process channel state machine error
29808 VOIP signalling process trunk state machine error
29810 VOIP signalling process signalling library error
29811 VOIP signalling process environment services error
29812 VOIP signalling process internal error

29815 VOIP call state machine invalid primitive
29816 VOIP channel state machine invalid primitive
29817 VOIP trunk state machine invalid primitive
29818 VOIP signalling process invalid primitive
29819 VOIP signalling process channel error
29822 VOIP signalling process cannot make call on alarmed trunk
29824 Unable to access SIP Header Configuration File

29828 SIP Register Failed To Parse Ini Files
29833 Call Rejected From Forbidden IP Address
30000 SS7 Unclassified Alarm
30004 Internal D7 error detected
30006 Missing SS7 Parameter
30008 Unhandled State Table Component
30009 State Table Alarm Reported
30010 State Table detected bad parameter
30011 Signaling Library rejecting requests
30012 Unhandled Signaling Library Message
30013 Invalid Data Item
30017 Configuration Translation failure
30020 Missing Parameter in SS7 message
30022 Internal Overflow

30023 Problem in processing Tags
30026 Invalid Signaling Library parameter
30033 Application Tags problem
30034 Application Tags problem
30035 SS7 Child process death
30039 SS7 Environment Problem
30040 SS7/MTP Environment Problem
30046 Remote SS7/WVR failure
30114 Distributed7 reports a Message Sequence error
30201 SS7 Stack D7 - reports minor alert
30202 SS7 Stack D7 - reports major alert
30210 Machine added to SS7/D7 Cluster
30212 SS7/D7 Stack - Link/LinkSet down
30215 SS7 - Distributed7 MTP Layer 2 problem
30217 SS7 - Distributed7 Inter Machine Heartbeat failure
30220 SS7 - Distributed7 has reported that a LinkSet is available
30221 SS7 - Distributed7 has reported a Link is available
30222 SS7 - Distributed7 has reported a Destination as available
30224 SS7 - Distributed7 has reported Congestion
30503 TDM connection management: connection server error (yellow)

30505 TDM connection management error
31001 Configurator failed when writing to real-time database
31002 Configurator cannot initialize ODM
31003 Configurator: lock of ODM failed
31004 Configurator: open ODM CuAt class failed
31005 Configurator: close ODM_class failed
31007 Configurator: open directory failed
32003 Signalling interface: polling timeout
32005 Signalling interface: polling unexpected results
32006 Signalling interface: signalling library call failed
32007 Signalling interface: invalid data received from device driver
32008 Signalling interface: unknown cause received from device driver
32009 Signalling interface: call cleared by channel process failure
32012 Signalling interface: signalling process failed to clear call
32013 Signalling interface: error event with no signalling process
32015 Signalling interface: obsolete SL_CALL_ABORT_CNF
32016 Signalling interface: invalid pidOriginalCHP on

SL_CALL_ABORT_CNF
32019 Signalling interface: alarm event with no signalling process
32020 Signalling interface: signalling process did not respond to alarm

Green messages
Table 4. WebSphere Voice Response messages classified as Green
2008 Low free channel process warning cleared
5080 Data timeout exceeded
5202 Database connection established
5302 Database server up
5311 DBHEALTH problem has cleared
5314 DBHEALTH problem has cleared
14012 SMSI: data line up
14028 SMSI warning: switch type set to none
17017 Network alarm has cleared
17034 Illegal application command
17037 Glare on line
17044 Signalling error cleared
17978 SCBus problem cleared by telephony adapter embedded

software
19029 ACL: link failure has cleared
20014 Invalid buffer received
20502 Custom server user-defined green alarm
20601 SS7 component green alarm
25029 OAM pool buffer clear message
25031 OAM test clear message for console

Table 4. WebSphere Voice Response messages classified as Green (continued)
25033 OAM process clear message
25035 OAM test warning message for console
25040 OAM file system clear
25075 OAM CPU usage alert cleared
25082 OAM test codepoint error
25089 SNA attachment active
25099 OAM test message AIXLOG clear
25201 Underrun margin time has returned to normal
25203 Play latency time has returned to normal
25205 Profile retrieval time has returned to normal
25207 Time to check voice messages has returned to normal
27075 Telephony adapter loading has now reduced below warning

threshold
27079 Telephony adapter interrupts are now adequately separated
27082 Pack has now recovered
27083 Adapter has now recovered
29616 ISDN Layer 1 discarding signalling messages stopped

29826 SIP Register can contact registrar again
29827 SIP Register Started
29830 VoIP SIP Layer 3 Has Successfully Restarted
30007 Invalid SS7 Parameter
30014 Configuration Overflow Condition

Table 4. WebSphere Voice Response messages classified as Green (continued)
30015 Configuration Error Detected
30016 Configuration Parameter Error Detected
30025 SS7 Link Active
30029 D7 SS7 Timer problem
30030 Custom Server Manager Rejected Request
30037 SS7 Monitor
30043 SS7/ISUP Environment Change
30044 SS7/ISUP Pre-defined parameter Bank
30047 Remote SS7/WVR recovery
30102 Distributed7 Busy
30103 Received Inbound call when blocked
30104 Inbound call for a seized circuit
30106 SS7 Message re-synch problem
30200 SS7 Stack D7 - reports info alert
30213 SS7/D7 Stack - Link/LinkSet recovered
30216 SS7 - Distributed7 MTP Layer 2 problem - Recovered
30502 TDM connection management: connection server error (green)

White messages
Table 5. WebSphere Voice Response messages classified as White
113 Could not play voice
114 Could not turn play off
301 Could not stop recording
506 Possible application loop detected
1101 Could not reinitialize local variable table. Creating new table.
1102 Could not find local variable
1103 Failed to convert between string and number
1104 Error detected with multi precision calculation
1120 Recursive loop detected in macro call
1201 Line problem
1203 Phone number too long
1204 Invalid format string received
1205 Invalid parameter for voice interruption detection
1206 Unexpected interruption by voice detection
1207 Unexpected interruption by fax tone
1208 Line Problem whilst answering call
1301 Background music parameter out of range
1302 Background music parameter out of range
1303 Fax detection parameter out of range

Table 5. WebSphere Voice Response messages classified as White (continued)
1305 Invalid DTMF stop keys for Play Prompt
1400 Play Latency Time alert for this call
1401 Underrun Margin Time alert for this call
1402 Profile retrieval time alert for this call
1403 Time to check voice messages alert for this call
5018 Close failed
5021 Read lock failed
5022 Write lock failed
5024 Seek failed
5046 Segment create failed
5049 Could not retrieve voice segment text data
5065 Close file or table failed (dmsclos or dmstclo)
5096 Voice database file not found
5098 Invalid voice directory group ID specified
5099 Invalid profile ID specified
5100 Invalid mailbox ID specified
5101 Invalid distribution list ID specified
5102 Access not allowed to distribution list
5204 Database problem avoided
5205 MWI activation not configured. MWISERVER shutting down.

5300 Deinstall of custom server failed
5318 Incorrect Mailbox Count Detected
5321 Cannot set interval timer
10102 Failed to execute shutdown script
11002 Request list extended
12018 Applid for initialized task already in use
12031 Calculate unique key for AIX ID failed
12032 Environment variable is invalid
12100 Caller not allowed to call function
12101 Appl_id is not a channel process
12102 No channel process available to perform task
12103 Attempt to restart channel process failed
12200 Invalid target appl_id
12201 Invalid IPC_TYPE / IPC_ID
12203 Cannot send message
12251 PCB pointer in PPT invalid
12254 Caller not allowed to generate this event
12255 Semaphore notify call failed
12256 Semaphore operation failed

12304 Buffer already has registered owner
13012 The process that requested a license has failed
13013 Invalid license type
14011 SMSI error: data line down
15001 Initial malloc failed
15003 Additional malloc failed
15005 Could not get 4KB buffer
15007 Prompt segment descriptor not found
15008 No 4KB block reference in DPRB
15010 Voice descriptor not found
16005 Server responded after timeout interval
17067 Recognition algorithm did not return result
17501 Error reading from microphone
17502 Error opening microphone
17503 Error opening speaker to play
17504 Error writing to speaker
17506 Error reading data from temporary file

17508 Error creating local message queue
17511 Error opening line output
17516 Ultimedia Audio Adapter notify_appl failed
17517 Ultimedia Audio Adapter invalid request type
17518 ACPA unable to acquire ODM information
17985 No telephony adapter installed
18200 Incorrect password
18201 Database access failed to retrieve administrator data
19011 ACL error: data line down
20005 Channel process link ID returned is invalid
20008 Attempt to fork process failed
20011 Invalid message received
20012 Cannot stop child process
20013 CA currently being built
20021 Custom server AUTOEXEC overridden on this SSI node
20500 Custom server user-defined log-only alarm
20501 Custom server user-defined white alarm
20600 SS7 component white alarm
24001 Session attach failed

24002 Session detach failed
24003 Session not enabled: currently in use
24004 Session not enabled: already enabled
24005 Invalid emulator release request
24006 Session restart request could not be processed
24008 3270 support is not configured in this system
24009 3270 LU pooling could not be started
24301 Query host update command failed
24304 Connecting to an LU session was unsuccessful
24305 Disabling an LU session was unsuccessful
24398 User log information from 3270 language LOG_ERROR

statement
24399 Host session status information
24501 No free slots in local session table
24502 Field information could not be retrieved
24505 Invalid data used in arithmetic operation
24506 Division by 0 (zero) attempted
24512 Exception definition or handler load failed
24515 Maximum exception retries exceeded
24703 Internal function (NotifyAppl) failed
24901 3270 controller shutting down

24903 3270 table is full
24904 Specific application invalid
24905 Configuration of specified session failed
24906 3270 configuration information could not be retrieved
24910 SNA/6000 software not detected
25004 OAM test message for log only
25023 OAM test message for OAM recovery
25024 OAM received unsupported test request
25025 OAM test message for task recovery
25046 OAM test for in task recovery
25090 OAM test informative message for console
25091 OAM test run-time parameters go to console
25097 OAM test message with both strings and decimals on the
console
25101 OAM adapter has changed
25102 OAM pack has changed
26004 SNMP object text20bj error
26008 SNMP unsupported operation error
27001 An error occurred which should not happen
27015 SDI ioctl failed
27026 SDI failed to unconfigure device

27033 SDI re-enable notification
27038 SDI received invalid request
27039 SDI received request that cannot be accepted because SDI is

busy
27040 SDI received unsupported request
27041 SDI received unreasonable request
27042 SDI was asked to log this request
27063 Unexpected signalling library primitive received
27064 Unexpected signalling library alarm received
27069 SDI detected non-essential signalling process termination
27070 SDI detected missing non-essential signalling process during

enable
27072 SDI re-enable notification (adapter)
27073 SDI re-enable failed (adapter)
27076 SDI thread error
27077 SDI ioctl failed
29000 ISDN undefined counter
29105 Lost ISDN queue element found
29106 ISDN queue empty
29109 ISDN environment services buffer pool is low
29208 ISDN signalling process buffer allocation retry

29405 ISDN Layer 3 primary data link layer activated
29406 ISDN Layer 3 primary data link layer deactivated
29407 ISDN Layer 3 backup data link layer activated
29408 ISDN Layer 3 backup data link layer deactivated
29409 ISDN Layer 3 backup data link layer out of service
29410 ISDN Layer 3 primary data link layer out of service
29611 ISDN Layer 2 detected incoming NT/network mode L2 frames
29618 The trunk ISDN configuration has been updated
29813 VOIP signalling process buffer allocation retry
30005 Unhandled SS7 Message
30021 Shutting down SS7 Component
30031 SS7 Test Call
30032 Distributed7 - Internal component failure
30036 SS7 Processor Started
30105 SS7 Continuity test failed
30214 SS7 - Distributed7 State Change
30500 TDM connection management: connection server error (log-only)
30501 TDM connection management: connection server error (white)
30509 TDM connection management overcame AIX problem
30510 TDM connection management not supported on this system

30511 TDM connection management detected timeslot allocation

problem
31008 Configurator: vocabulary name not in ll_CC_nnnn format
31009 Configurator: vocabulary file has same numeric identifier as

another
32010 Signalling interface: call cleared by silence detected on line
32011 Signalling interface: signalling process termination detected
32021 Signalling interface: call cleared by cadenced hang-up tone
Messages affected by filtering

The numbers of the messages that are affected by the WebSphere Voice
Response filtering process are listed here.
The table indicates the severity level and destinations assigned by the filtering
process. For detailed information about each message, including the message
severity and destinations before filtering, see Appendix B, “WebSphere Voice
Response messages identified by number,” on page 173.
Table 6. WebSphere Voice Response messages affected by filtering
Threshold criteria
Message New Number Time

number severity New destination generated (seconds)
105 Red WebSphere Voice Response log, 12 60

System Monitor, Alertable

1120 White WebSphere Voice Response log, 10 120

System Monitor

Table 6. WebSphere Voice Response messages affected by filtering (continued)
Threshold criteria



5018 Yellow WebSphere Voice Response log, 12 60

System Monitor

System Monitor

System Monitor

System Monitor


System Monitor
5036 Red System Monitor 12 60




System Monitor

Threshold criteria



System Monitor

System Monitor

System Monitor

System Monitor




System Monitor

System Monitor

System Monitor

System Monitor

System Monitor

Threshold criteria





System Monitor


System Monitor

System Monitor

System Monitor

System Monitor

System Monitor

System Monitor

System Monitor

System Monitor

Threshold criteria



System Monitor





System Monitor

System Monitor




System Monitor
25081 Yellow WebSphere Voice Response log 10 3600

Threshold criteria


System Monitor

Appendix A. Messages issued during migration or import
This appendix lists the messages that you might see when migrating from an
IBM WebSphere Voice Response for AIX Version 4.2 system to WebSphere
Voice Response Version 6.1. These messages are produced by the stand-alone
migration process and also by the import utility when you import data
exported from earlier releases of WebSphere Voice Response.
You can find the stand-alone migration log, restoreDT.log, in the directory
from which you invoked restoreDT.
disconnect from the database.

MIG001 Failed to connect to DB2
User response: Check the migration log for
Explanation: WebSphere Voice Response could
errors reported for any WebSphere Voice
not establish a connection with the database. The
Response data objects earlier in migration. If
two most likely causes for this failure are:
there are no other errors, start WebSphere Voice
v The database manager has not been started Response. Otherwise, see Table 8 on page 191 for
(SQL message number SQL1032N). a description of the WebSphere Voice Response
v A DB2“ concurrent connect license was not database return codes. If the return code is not
found (SQL message number SQL8001N). listed, contact IBM Support.
User response: If the SQL message number was
SQL1032N, start the database manager. To start MIG004 Failed to open DMS table
the database manager, log on to the root userid,
Explanation: An error occurred opening the
then su to dtdb23in, and type the command
specified WebSphere Voice Response Version 4.2
db2start. For both SQL return codes see Table 8
database table. The two most likely causes of this
on page 191. If the return code is not listed,
error are:
contact IBM Support.
v Intentions denied (DMS return code = -4203).
The table is being held by another process
MIG002 Failed to commit migration whose intention (read/write access
Explanation: An error occurred committing the permission) causes the migration process to
database transactions during migration. fail to open the table.
v File needs recovery (DMS return code = -4208).
User response: Check the migration log for
The table needs recovery.
errors reported for any WebSphere Voice
Response data objects earlier in the migration. If User response: If the DMS return code is -4203,
there are no other errors, start WebSphere Voice you may have tried to run the migration process
Response. Otherwise, see Table 8 on page 191 for while WebSphere Voice Response is still running.
a description of the WebSphere Voice Response Shutdown WebSphere Voice Response and retry
database return codes. If the return code is not the migration process. If files need recovering,
listed, contact IBM Support. type recoverDMS on the command line. When
recovery is complete, retry the migration process.
If neither of these two errors appear in the
MIG003 Failed to release from DB2
migration error log, see Table 8 on page 191 for a
Explanation: The migration process failed to description of the WebSphere Voice Response

MIG005 • MIG010
database return codes. If the return code is not Table 8 on page 191 for a description of the
listed, contact IBM Support. WebSphere Voice Response Database return
codes. If the return code is not listed, contact
IBM Support.
MIG005 Failed to select/fetch row from
DMS table
MIG008 Failed to open directory
Explanation: An error occurred selecting or
fetching data from the specified WebSphere Voice Explanation: The directory specified in the error
Response Version 4.2 database table. message could not be opened.
User response: See Table 8 on page 191 for a User response: Check the file access
description of the WebSphere Voice Response permissions for the directory to see if you have
database return codes. If the DMS return code is read permission. If not, correct the permissions
not listed, contact IBM Support. and retry the migration process. You should run
the migration process from the root user. If you
are and these errors persist, contact IBM Support.
MIG006 Failed to close DMS table
Explanation: An error occurred closing the
MIG009 Failed to open DMS file
database table. Explanation: An error occurred opening the
User response: If the table was not already
database file. The two most likely causes for this
open, DMS return code -9 is generated. You can
failure are:
ignore this error because it does not affect the
migration process. If there are other error v Intentions denied (DMS return code = -4203).
messages in the migration log, check these in The file is being held by another process
Table 8 on page 191. If it is clear from the whose intention (read/write access
migration log that some data objects were not permission) causes the migration process to
migrated, contact IBM Support. fail to open the file.
v File needs recovery (DMS return code = -4208).
The file needs recovery.
MIG007 Failed to insert row into DB2
User response: If the DMS return code is -4203,
Explanation: An error occurred creating a
you may have tried to run the migration process
WebSphere Voice Response data object because a
while WebSphere Voice Response is still running.
table insert operation failed. The most common
Shutdown WebSphere Voice Response and retry
cause of this failure, indicated by the SQL return
the migration process. If files need recovering,
code SQL0803N, is a duplicate object with the
type recoverDMS on the command line. When
same primary key in the table. This is because
some or all of your objects already exist in the
If neither of these two errors appear in the
WebSphere Voice Response Version 6.1 database.
migration error log, check Table 8 on page 191
If you have already tried to migrate to
for a description of the WebSphere Voice
WebSphere Voice Response Version 6.1 and the
Response database return codes. If the return
migration failed, you must ensure that the
code is not listed, contact IBM Support.
Version 6.1 database is reset, before running the
migration process again.
MIG010 Failed to read first record from
User response: If the SQL return code is
DMS file
SQL0803N, use the command DT database -r to
reload the database with the default data Explanation: An error occurred reading the first
supplied with WebSphere Voice Response before record from the specified WebSphere Voice
retrying the migration process. Otherwise, check Response Version 1 database file. The file may be

MIG011 • MIG014
corrupted or need recovering. same primary key in the table. This is because
the <Default> Application already exists in the
User response: To recover WebSphere Voice
WebSphere Voice Response database. If you have
Response Version 1 database files, type
already tried to migrate to WebSphere Voice
recoverDMS on the command line. When
Response Version 6.1 and the migration failed,
you must ensure that the Version 6.1 database
If the problem persists, check Table 8 on page 191
and the tables are reset before running the
migration process again.
code is not listed, contact IBM Support. User response: If the SQL return code is
SQL0803N, use the command DT database -r to
reload the database with the default data
MIG011 Failed to read record from DMS
supplied with WebSphere Voice Response before
file
retrying the migration process. Otherwise, check
Explanation: An error occurred reading the table Table 8 on page 191 for a description of the
specified WebSphere Voice Response Version 4.2 WebSphere Voice Response database return
database file. The file may be corrupted or need codes. If the return code is not listed, contact
recovering. IBM Support.
User response: To recover WebSphere Voice

Response Version 4.2 database files, type MIG014 SQL message
recoverDMS on the command line. When
Explanation: The SQL message that was
generated because of a database error is
If the problem persists, check Table 8 on page 191
displayed with this message number. The SQL
message is associated with the preceding
migration message.
code is not listed, contact IBM Support.
User response: None. If you need to contact
IBM Support, quote the SQL error message as
MIG012 Failed to close DMS file
well as any other error messages.
Explanation: An error occurred closing the
database file.
User response: If the file was not already open,
DMS return code -9 is generated. You can ignore
this error message because it does not affect the
migration process. If there are no other errors,
start WebSphere Voice Response. If there are
other errors, check in Table 8 on page 191 for a
description of the WebSphere Voice Response
database return codes. If the return code is not
listed, contact IBM Support.
MIG013 Failed to create application

Explanation: An error occurred creating a
WebSphere Voice Response application because a
table insert operation failed. The most common
cause of this failure, indicated by the SQL return
code SQL0803N, is a duplicate object with the
Appendix A. Messages issued during migration or import 171

Appendix B. WebSphere Voice Response messages
identified by number
This appendix lists the WebSphere Voice Response error messages.
The WebSphere Voice Response error messages are listed in numerical order
by error_id, and are grouped by module area. For example, numbers 1
through 4999 are reserved for messages issued by the Session Manager/CHP
(channel process) modules. Any message with an ID number between 1 and
4999 is therefore generated by the session manager/CHP software.
Table 7 lists the numbers that are reserved for use by each component. The
rest of this appendix lists the messages in order by component. Each message
includes an explanation of the condition, followed by any actions you can
take to solve the problem.
Each message also includes the message severity and destination. The
destinations include Log (the WebSphere Voice Response error log), System
Monitor, and Alertable. For more information on the severity levels and
destinations, see Chapter 5, “Introducing the WebSphere Voice Response alarm
messages,” on page 107.
Table 7. Message numbers generated by each software component
Starting number Component name and page reference
1 “Session Manager/CHP” on page 176
5001 “DBSM (database server) return codes” on page 193
10001 “NODEM (Node Manager)” on page 211
11001 “STPD (State Table/Prompt Directory)” on page 215
12001 “VAE (General WebSphere Voice Response)” on page 216
13001 “LUM (License Use Management)” on page 222
14001 “SMSI (Simplified Message Service Interface)” on page 225
15001 “CACHE (Cache Manager)” on page 229

Table 7. Message numbers generated by each software component (continued)
16001 “DBIM (Internal Database Manager)” on page 231
17001 “VPACK, SPACK and XPACK” on page 232
18001 “VAD (Voice Application Development)” on page 263
19001 “ACL (Application Connectivity Link)” on page 264
20001 “CA (Custom Server)” on page 266
21001 “DTBE (Java and VoiceXML environment)” on page 271
23001 “SM_SRVR” on page 272
24001 “CTRL3270” on page 274
25001 “OAM (Operations and Maintenance)” on page 284
26001 “SNMP (Simple Network Management Protocol)” on page 297
27001 “SDI (Signaling Device Driver Interface)” on page 299
29000 “ISDN services” on page 312
29200 “ISDN signaling process and ISDN call control” on page 316
29400 “ISDN D Layer 3” on page 321
29600 “ISDN D Layer 2 and Layer 1” on page 324
29800 “VoIP” on page 329
30000 “SS7” on page 336
30500 “Timeslot Management” on page 349
31001 “Pack Configuration” on page 352
32001 “Signaling Interface” on page 354

<message number>
Table 7. Message numbers generated by each software component (continued)
35000 “SpeechServer custom server” on page 359
CP000 “CallPath_Sigproc Custom Server” on page 368
DTJ “Java and VoiceXML environment messages” on page 385
JB000 “Juke_Box custom server” on page 422
ISDN_XFER000 “ISDN_Call_Transfer custom server” on page 415
TROMBONE000 “IBM_Trombone_Custom_Server” on page 435
Message “VXML messages” on page 444
Example Message
<message number> <message text>

Explanation: Further information about why the
alarm occurred.
User response: What you should do.
Severity: Red, Yellow, Green or White. For
information about severities, see “Message
categories” on page 111).
Destination: Log, System Monitor or Alertable.
For information about destinations, see “Message
destinations” on page 107.
Appendix B. WebSphere Voice Response messages identified by number 175

1 • 111
Session Manager/CHP
1 Internal channel process error 101 Server data invalid

Explanation: A software malfunction occurred. Explanation: The custom server passed invalid
Examine the error log for details. data to a state table action. The system plays an
error message and hangs up.
User response: Call IBM Support.
User response: Correct the custom server
Severity: Yellow
program to pass valid data.
Destination: Log, System Monitor
Severity: Yellow
2 Start/restart or initialization failed
Explanation: One or more channel processes
105 Error return from host request
could not be started or properly initialized. This
may have been caused by a system error or Explanation: A request was detected but could
software malfunction. Examine the error log for not be found in the buffer.
details.
User response: Check the status of the state
User response: Call IBM Support. table debugger and custom servers.
Severity: Yellow Severity: Yellow
Destination: Log, System Monitor Destination: Log, System Monitor
3 Call processing error 106 Host server failed

Explanation: An error occurred while Explanation: A host server failed to execute the
processing an incoming call or request from a action requested by the channel process.
server.
User response: See the error log for details.
User response: Call IBM Support with full Check the status of the host servers. Call IBM
details of the error and circumstances. Support.
100 Action parameter invalid 110 Server timeout

Explanation: The state table action named in Explanation: A custom server or 3270 server
the error log entry was passed an invalid value did not respond within designated time.
in one of its parameters.
User response: Check the status of custom
User response: Check and correct parameters servers and 3270 servers.
for the specified action, validate state table. The
Severity: Yellow
error description may include the name of the
invalid parameter, its value, and guidance on Destination: Log
how to correct it.
Severity: Yellow 111 Error receiving data from custom
server or 3270 server

113 • 200
Explanation: See the error log for details. This User response: If this error persists, contact IBM
error can also occur if you issue a SendData() Support.
action and the associated parameters do not fit
Severity: Yellow
into a 4KB block. Part of the 4KB block is taken
by the SYS_ENVELOP and DPRBSTRUCT. Destination: Log, System Monitor
Variables (including header information) must fit
into the remaining 3948 bytes. The header
information for each variable consists of three 117 DPRB manager function failed
bytes: one for the type and two for the length. Explanation: A failure occurred in passing
The amount of data is therefore reduced to 3948 information between the channel process and a
bytes minus 3 bytes per variable. Also, for server using a buffer pool. The system plays an
SendData() each variable is converted to a string. error message and hangs up.
So, passing the parameter '1234.5678' uses three
bytes for the header and nine bytes for the value. User response: If this error persists, contact IBM
The information string for this error would Support.
contain "Too much data supplied to SendData". Severity: Yellow
User response: Change the application or server Destination: Log, System Monitor
so that less data is sent.
Severity: Yellow 199 State table action request timeout
Destination: Log, System Monitor Explanation: A state table action timed out
while waiting for an answer to a signalling
113 Could not play voice request. The system logs an error message and
the state table action fails appropriately.
Explanation: The channel process tried to start
playing voice but received an error code from the User response: Check that the expected
device driver. signalling process for this channel is installed
and running. Another possible cause might by an
User response: Check the status of the channel. error in the Signalling process code which
Severity: White handles the given request. If the problem persists
contact IBM support.
Severity: Yellow
114 Could not turn play off Destination: Log, System Monitor
Explanation: The channel process tried to stop

playing voice but received an error code from the 200 State table request timeout
device driver. Explanation: The system timed out while trying
User response: Check the status of the channel. to get a state table. The system plays an error
message and hangs up. This can be caused by a
Severity: White heavily-loaded system or it can indicate other
problems.
User response: Check the error log for other
related errors and follow the appropriate steps
116 Could not translate key
for dealing with them. Check that the process
Explanation: It was impossible to determine a named STATEM is still running. If not, this is
valid key from the tone received. probably the cause of the error. Check for core
files in /var/adm/ras/dirTalk and contact IBM

201 • 211
Support. If the system load is high, try to reduce Explanation: The system timed out while
it. waiting for a response from the Data Base
Interface Manager (DBIM). The system plays an
Severity: Yellow
error message and hangs up.
User response: Increase the value of the system
parameter for the DBIM timeout value which is
201 Voice buffer underrun in the General group under System
Configuration. If system load is high, try to
Explanation: While playing voice data with reduce it.
PlayPrompt, PlayAudioName, PlayGreeting,
PlayVoiceMessage, or PlayVoiceSegment the Severity: Yellow
device driver unexpectedly ran out of voice data
to play. The system continues to play voice data
when more is available, but the caller will hear a
pause in the voice. 209 Mailbox request timeout
User response: This is probably caused by the Explanation: The system timed out while
voice input buffer to the device driver being too waiting for a mailbox request from application
small, and is most likely to happen when the profile server. The system plays an error message
system is heavily loaded. Increase the size of the and hangs up. This can be caused by a
buffer using the Normal Play/Record Max Data heavily-loaded system, or it can indicate other
system parameter. problems.
Severity: Yellow User response: Check the error log for related
errors and follow the appropriate steps for
dealing with them. Check that the process named
UPSERVER is still running. If not, this is the
203 Cache request timeout probably cause of this error. Look for core files in
/var/adm/ras/dirTalk and contact IBM Support.
Explanation: The system timed out while If system load is high, try to reduce it.
waiting for a cache request. The system plays an
error message and hangs up. This can be caused Severity: Yellow
by a heavily-loaded system or it can indicate
other problems.
User response: Check the errorlog for other
211 Profile request timeout
related errors and follow the appropriate steps
for dealing with them. Check that the process Explanation: The system timed out while
named CACHEM is still running. If not, this is waiting for a profile request from application
the probable cause of this error; look for core profile server. The system plays an error message
files in /var/adm/ras/dirTalk and contact IBM and hangs up. This may be caused by the system
Support. If system load is high, try to reduce it. being heavily loaded or it could indicate other
As a work around, you might be able to change problems.
your application to use a PlayVoiceSegment
User response: Check the error log for related
action rather than PlayPrompt. This avoids use
of the cache.
Severity: Yellow UPSERVER is still running. If not, this is the
probable cause of this error. Check for core files
in /var/adm/ras/dirTalk and contact IBM
Support. If the system load is high, try to reduce
207 DBIM request timeout it.

214 • 403
Severity: Yellow
400 Profile not found
Explanation: The system requested an
application profile from the profile server and
214 Timed out waiting for disk space the server reported that the profile was not on
information file. The profile may have been deleted, but the
profile ID left in the channel assignments. The
Explanation: The system timed out while system plays an error message and hangs up.
waiting for disk space information. This may be
caused by the system being heavily loaded or User response: Add the missing profile or
could indicate other problems. change the assigned profile for the channel.
User response: Check the error log for related Severity: Yellow
VAGSERVER is still running. If not, this is the
probable cause of this error. Check for core files 401 Default profile not found
in /var/adm/ras/dirTalk and contact IBM
Explanation: The system requested the system
Support. If the system load is high, try to reduce
default profile from the profile server and the
it.
server reported that the profile was not on file.
Severity: Yellow The system default profile ID is specified by a
system parameter which is retrieved if the
assigned profile could not be retrieved. The
system plays an error message and hangs up.
300 Voice segment not found
User response: Add the missing profile or
Explanation: The system requested a voice change the assigned profile for the channel.
segment from the voice data segment server and
Severity: Yellow
the server reported that the voice data was not
on file. Destination: Log, System Monitor
User response: Check the error log for details of
the segment, including language and 402 Profile deleted in use
compression type. Check that the segment exists,
Explanation: A profile was deleted from the
that it contains voice data, and that its
system while it was being used by an application
specification in the state table is valid.
state table. The system disconnects the caller that
Severity: Yellow encountered the missing profile.
Destination: Log, System Monitor User response: If the profile was deleted in
error, add it back into the system.
301 Could not stop recording Severity: Yellow
Explanation: The channel process tried to stop Destination: Log, System Monitor
recording, but received an error code from the
device driver.
403 Invalid caller mailbox ID
User response: Check the status of the channel.
Explanation: The system variable Caller
Severity: White Mailbox Id is out of range.
Destination: Log, System Monitor User response: Make sure that variable Caller

404 • 500
Mailbox ID is set properly to a value between 1 Explanation: The system needed to request the
and 10. system default application profile, but the system
default profile ID is not set in the system
Severity: Yellow
parameters. The system plays an error message
Destination: Log, System Monitor and hangs up.
User response: Make the system parameter
404 Profile unlock request not granted assignments valid.
Explanation: The system refused a request to Severity: Yellow

unlock the user profile. This indicates a possible
database problem. The system plays the error
message and hangs up.
408 User greeting not found
User response: Verify the integrity of the
database by shutting down and recovering DMS. Explanation: The user greeting associated with
If the problem persists, call IBM Support. this application profile was not found in the
database.
Severity: Yellow
User response: Check that the user greeting is
correctly identified and present. You might need
to create a new user greeting.
405 Audio name not found
Severity: Yellow
Explanation: The audio name associated with
this application profile and mailbox was not
found in the database.
409 Invalid schedule ID specified
User response: Check that the audio name is
correctly identified and present. You may need to Explanation: An attempt was made to assign a
create a new audio name. Set Attributes system variable for either
Notification or Referral Schedules, but the
Severity: Yellow
specified ID was invalid. The error parameter
Destination: Log, System Monitor data contains a full textual description of the
problem.
406 No profile ID User response: Use the error parameter data to

determine which state table is at fault, and
Explanation: The system could not find an correct the error.
application profile ID to request an application
profile. In the system parameters, there is no Severity: Yellow
number in the channel assignments, no area code
in the channel group assignments, and no system
default profile ID. The system plays an error
message and hangs up. 500 State table not found
User response: Make the system parameter Explanation: The system requested a state table
assignments valid. that was not on file. The state table may have
been deleted, but the ID left in the profile. The
Severity: Yellow
system plays the error message and hangs up.
User response: Change the profiles to use a
different state table or reinstate the missing state
407 No profile ID table from backup data.

501 • 507
Severity: Yellow User response: Edit the application profile or

the InvokeStateTable action and assign a valid
state label. Validate and save the state table and
application profile.
501 State table nesting too deep
Severity: Yellow
Explanation: The number of nested state tables
has been exceeded by calling another state table
with the InvokeStateTable action. This means that
there is a recursion problem with the state table, 505 Parameter mismatch in
or too many calls to existing state tables. The InvokeStateTable area
system plays the error message and hangs up.
Explanation: An InvokeStateTable action failed
The limit for state table nesting is 30.
because its arguments did not match the set of
User response: Correct the deepest state table. input parameters expected by the state table
To work around this combine state tables instead which was to be invoked.
of nesting them.
User response: Verify that the parameters in the
Severity: Yellow InvokeStateTable action match the expected input
parameters of the corresponding state table.
Validate and save any changes. If the problem
persists, contact IBM Support.
502 State table has not been validated
Severity: Yellow
Explanation: The state table has not been
validated in the state table debugger. The
InvokeStateTable action returns state table Not
Invoked. 506 Possible application loop detected
User response: Validate and save the state table. Explanation: WebSphere Voice Response has
been configured to detect application loops
Severity: Yellow
within state tables. A potential loop has been
Destination: Log, System Monitor found, and a log file has been created containing
information about the loop. The application will
not be terminated, but will now be monitored
503 State ID not found in table more closely.
Explanation: The next state seen by the channel User response: Review the log referred to below
process does not exist. to decide whether you have a problem within
User response: Correct and validate the state the application. Alternatively you may wish to
table. tune the detection parameters labelled "State
Table Loop Detection", within the Application
Severity: Yellow Server Interface parameter group, to refine the
Destination: Log, System Monitor detection.
Severity: White
504 State label not found in state Destination: Log, System Monitor
table
Explanation: The state table entry label 507 Application loop detected
specified in the application profile or directly on
the InvokeStateTable action cannot be found in Explanation: WebSphere Voice Response has
the specified state table. been configured to detect application loops
within state tables. A loop has been detected. The

600 • 620
application is ended as if it had issued the prompt directory but a PlayPrompt action was
"CloseEverything" state table action. invoked.
User response: Review the log referred to in User response: Specify a prompt directory in
error message 506 to decide whether you have a the state table. A possible workaround is to use
problem within the application. Alternatively you the PlayVoiceSegment action.
may wish to tune the detection parameters
Severity: Yellow
labelled "State Table Loop Detection", within the
Application Server Interface parameter group, to Destination: Log, System Monitor
refine the detection.
Severity: Yellow 604 Unable to interpret operation in
prompt description
Explanation: The operation specified in the
prompt is not implemented in the channel
600 Prompt directory not found
process.
Explanation: The system requested a prompt
User response: Check all operations defined for
directory but could not find it. The prompt
prompts in the state table editor and the prompt
directory may have been deleted, but the prompt
editor if applicable. Validate and save the
directory IDs may still exist within the state
prompts and state tables.
table. The system plays the error message and
hangs up. Severity: Yellow
User response: Change the prompt directory ID Destination: Log, System Monitor
within the state table or reinstate the prompt
directory from backup data. To work around this
create a dummy entry in the prompt directory. 605 Prompt directory could not be
retrieved
Severity: Yellow
Explanation: The system requested a prompt
Destination: Log, System Monitor directory but the operation failed. See the error
log for details.
601 Prompt not found User response: Validate and save prompt
directories and state tables.
Explanation: The system requested a specific
prompt from a prompt directory but could not Severity: Yellow
find it. The prompt may have been deleted from
the directory and the state table may still rely on Destination: Log, System Monitor
its existence. The system plays the error message
and hangs up. 620 System cannot retrieve specified
User response: Change the state table Prompt variable
states to use a different prompt, or reinstate the Explanation: The system cannot find the
prompt in the prompt directory. variable it has been asked to retrieve.
Severity: Yellow User response: Check the variable declarations
Destination: Log, System Monitor in the state table.
Severity: Yellow
603 No prompt directory specified in Destination: Log, System Monitor
state table
Explanation: The state table did not specify a

621 • 702
custom server, check that the relevant custom

621 System cannot set the requested
server is installed, built, and waiting or active
variable
(that is, running). You can check this on the
Explanation: The system cannot set the Custom Server Monitor window. If you also get
requested variable. an error 2000, there are not enough free buffers
available for the OpenHostServerLink to succeed.
User response: Check the variable declaration
in the state table. See the error log for details and Severity: Yellow
correct the application if appropriate.
Severity: Yellow
Destination: Log, System Monitor 700 Could not create voice message.
Explanation: The system tried to create a new
624 Action failed during host voice message. The system plays the error
execution message and hangs up.
Explanation: An action being executed for a User response: Verify database integrity by
server did not complete successfully. shutting down DT then running
$VAETOOLS/vm_integrity to check for
User response: Check server requests to execute
inconsistency between the AIX file system and
state tables.
DB2 database. If problems are found, correct
Severity: Yellow them. To work around this use another profile. If
the problem persists, call IBM Support.
Severity: Yellow
630 Host session received unknown Destination: Log, System Monitor

request
Explanation: An unknown request was received 701 Message request failed
by the host.
Explanation: A request to the application profile
User response: Check server requests to execute server failed. The system plays the error message
state tables. Retry the action. If the problem and hangs up.
User response: Verify database integrity. Correct
Severity: Yellow any problems you find.
Destination: Log, System Monitor Severity: Yellow

650 Unexpected status found in DPRB
Explanation: There is a conflict between 702 Tried to delete invalid message
received status type and expected status type.
Explanation: The state table tried to delete a
This error can be caused by a custom server that
message without first setting up the message
is not in the custom server manager table.
information properly. The system plays the error
User response: Retry the action, and check the message and hangs up.
status of the custom applications. If the problem
User response: Correct the state table.
persists, contact IBM Support. If this error is
reported by CHP and the function Severity: Yellow
hsl_alloc_executory, and the DPRB return code is
2 when trying to open a host server link with a

703 • 801
operation on the message in the mailbox, but

703 Distribution list request timed out
there was no message.
Explanation: A distribution list could not be
User response: Ensure that the action is
retrieved from the server.
preceded by a CheckVoiceMessages action. If the
User response: Consistency check the database; problem persists, contact IBM Support.
make sure that UPSERVER is running. Reduce
Severity: Yellow
the system load.
Severity: Yellow
708 Action failed because of no valid
message in workspace
704 Distribution list request failed
Explanation: A state table action requested an
Explanation: A distribution list could not be operation on the message in the workspace, but
retrieved from the server. there was no message.
User response: Consistency check the database; User response: Ensure that the action is
make sure that UPSERVER is running. preceded by CheckVoiceMessages or
RecordVoiceMessage.
Severity: Yellow
Severity: Yellow
705 Distribution list update request
timed out 800 Voice table not found
Explanation: Could not update a distribution Explanation: The system could not find the
list because it timed out. voice table. It may have been inadvertently
deleted, or not exist in the specified language.
User response: Make a consistency check on the
The system plays the error message and hangs
database. Ensure that UPSERVER is running.
up.
Severity: Yellow
User response: Check that the table is correctly
Destination: Log, System Monitor identified and is present. You may need to
restore the table from backup data or create a
new one.
706 Distribution list update request
failed Severity: Yellow
Explanation: The distribution list could not be Destination: Log, System Monitor
updated by the server.
User response: Consistency check the database; 801 Voice table entry not found
make sure that UPSERVER is running.
Explanation: The system could not find an
Severity: Yellow expected entry in the voice table. It may have
been deleted. The system plays the error message
Destination: Log, System Monitor and hangs up.
User response: Add the missing entry to the
707 Action failed because of no valid variable mapping table.
message in mailbox
Severity: Yellow
Explanation: A state table action requested an

810 • 1001
Destination: Log, System Monitor files from backup data and check that they are
valid.
810 Invalid variable assignment Severity: Yellow
Explanation: Invalid variable assignment Destination: Log, System Monitor
detected.
User response: See the error log for details. 1000 Application error: invalid request
Ensure that the variable is of the proper type or # in data block
correct assignment value.
Explanation: A SendData action with a timeout
Severity: Yellow greater than 0 (that is, one that causes a response
from the server) has been followed by another
Destination: Log
SendData to the same server without waiting for
the response from the first SendData. There is no
900 System parameter undefined corresponding ReceiveData action, or there is one
but the application does not retry on a Timeout
Explanation: The system could not find a edge. The Timeout edge means that the
required system parameter. This indicates that ReceiveData has timed out, not that the server
the system parameter files have been corrupted. request has timed out. ReceiveData is retried
The system plays the error message and hangs until one of the following edges is returned: -
up. Succeeded - No More Data - Data Not Found -
User response: Restore the system parameter Host Problem Host Problem occurs when the
files from backup data. SendData timeout expires. If the server involved
is a custom server, the error parameters give its
Severity: Yellow name and process ID (PID). Note: This error can
Destination: Log, System Monitor be reported from any action, so the State
Table:Label and Action parameters are not
relevant.
901 System parameter invalid
User response: Ensure that all SendData actions
Explanation: The system detected an invalid with a timeout greater than 0 have a
system parameter. This indicates that the system corresponding ReceiveData action that is always
parameter files have been corrupted. The system properly executed before the next SendData to
plays the error message and hangs up. that server and before the application terminates.
User response: Restore the system parameter If you don't want to receive a response from a
files from backup data and check that they are SendData action, set the Timeout value to 0.
valid. Severity: Yellow
Severity: Yellow Destination: Log
1001 Application error: invalid function
906 System parameter for function or subfunction
key undefined or invalid Explanation: An application has issued a
Explanation: A system parameter describing a SendData action with a timeout greater than 0
function key could not be read or contained an (one that will cause a response from the server),
invalid value. and then closed the link to that server without
waiting for the response. The link is closed either
User response: Restore the system parameter using CloseHostServerLink or CloseEverything.
This happens because there is no corresponding

1100 • 1201
ReceiveData action, or there is one but the

1102 Could not find local variable
application does not retry on a Timeout edge.
The Timeout edge means that the ReceiveData Explanation: Could not find a local variable.
has timed out, not that the server request has
User response: Validate state tables and prompt
timed out. ReceiveData is retried until one of the
directories.
following edges is returned: - Succeeded - No
More Data - Data Not Found - Host Problem Severity: White
Host Problem occurs when the SendData timeout
expires. If the server involved is a custom server, Destination: Log, System Monitor
the error parameters give its name and process
ID (PID). Note: This error can be reported from 1103 Failed to convert between string
any action, so the State Table:Label and Action and number
parameters are not relevant.
Explanation: A conversion of a string to a
User response: Ensure that all SendData actions number, or a number to a string failed. See the
with a timeout greater than 0 have a error log for details.
corresponding ReceiveData action that is always
properly executed before the next SendData to User response: Correct the assignment in the
that server and before the application terminates. state table or call IBM Support as appropriate.
If you don't want to receive a response from a Severity: White
SendData action, set the Timeout value to 0.
Severity: Yellow
Destination: Log 1104 Error detected with multi
precision calculation
1100 Could not initialize local variable Explanation: An error occurred while
table. Cannot start check. performing mathematical calculations.
Explanation: The channel process cannot User response: See the error log for details.
allocate memory (from the buffer pool) for Correct the application if appropriate.
dynamic variables (dv).
Severity: White
User response: Increase the buffer pool size. A
possible workaround is to use system variables Destination: Log
instead of user-defined variables.
Severity: Yellow 1120 Recursive loop detected in macro
call
Explanation: A recursive loop was detected in a
macro call.
1101 Could not reinitialize local
variable table. Creating new table. User response: Edit the prompt macro and
remove the recursive loop.
Explanation: This channel process had to
restart. Severity: White
User response: None. The channel process has Destination: Log, System Monitor
recovered from the error.
Severity: White 1201 Line problem
Destination: Log, System Monitor Explanation: The channel process detected an

1202 • 1208
unacceptable error on the channel in use while Explanation: One of the system parameters for
trying to reconnect. voice interruption detection contains an invalid
value.
User response: Use another channel, or fix the
problem with channel. IBM Support should User response: Not coded
invoke diagnostics. Refer to the Configuring the
Severity: White
System book.
Severity: White
1206 Unexpected interruption by voice
detection
1202 No line assigned
Explanation: An action was interrupted by
Explanation: An action is executed that requires voice detection when voice detection had been
activity on the line, but the call has been deactivated.
terminated by the state table.
User response: Not coded
User response: Check and correct the state
Severity: White
table.
Severity: Yellow
1207 Unexpected interruption by fax
tone
1203 Phone number too long
Explanation: An action was interrupted by fax
Explanation: The specified phone number tone when this event was not expected.
(possibly combined with the area code) is too
User response: None.
long and has been truncated.
Severity: White
User response: Unless this was intended,
reduce the phone number length to the Destination: Log, System Monitor
maximum allowable (20 digits max should
work!) and try again.
1208 Line Problem whilst answering
Severity: White call
Destination: Log, System Monitor Explanation: The channel process detected an
error on the channel in use whilst trying to
answer an incoming call. This could be caused
1204 Invalid format string received
by incorrect configuration of the telephony
Explanation: A format string contains an invalid protocol or telephony parameters, or an error in
character or the string is not long enough for the the signalling software.
corresponding phone number.
User response: If this error occurs frequently,
User response: Correct the format string and check that the correct protocol has been selected
retry. on WebSphere Voice Response and the switch,
and that the parameters forWebSphere Voice
Severity: White
Response and the switch are compatible. If the
Destination: Log, System Monitor problem persists, call IBM Support. To help solve
the problem, have the following available when
you call: - Details of the switch and WebSphere
1205 Invalid parameter for voice Voice Response telephone setup - Details of the
interruption detection

1300 • 1305
version of WebSphere Voice Response you are

1303 Fax detection parameter out of
using, along with details of any PTFs that have
range
been applied - A system-level trace of the
problem Explanation: A parameter was out of the
allowed range. Fax detection must be set to one
Severity: White
of the following values: 0 - Off 1 - Inbound 2 -
Destination: Log, System Monitor Outbound 3 - Bothway The fax detector has been
turned off.
1300 Background music action failed User response: Correct the application to pass a
valid value.
Explanation: An attempt to control background
music failed. The application will continue, but Severity: White
music will not be mixed in. The return code and
the failing function are given.
User response: None. If the problem persists,
1304 Could not set requested channels
call IBM Support.
Explanation: The channel process manager
Severity: Yellow
could not interpret either or both of: * SV178
Destination: Log, System Monitor System : Call : Permitted channel groups * SV228
System : Call : Permitted channels The set of
channels to use for outbound calls has now been
1301 Background music parameter out set to the default: any channel and both variables
of range have been set to the null string.
Explanation: A parameter was out of the User response: Check the passed strings closely
allowed range. It has been set to the closest for errors and modify the application to pass
allowable value to the requested value, or to a valid values.
default value. The requested value and actual
value are given. Severity: Yellow
User response: Correct the application so that it Destination: Log, System Monitor
passes a valid value.
Severity: White 1305 Invalid DTMF stop keys for Play
Prompt
Explanation: The referenced action was coded
to stop on selected DTMF. Invalid DTMF keys as
1302 Background music parameter out indicated below in "Invalid keys" have been
of range specified. Only keys in the range
Explanation: A parameter was out of the "0123456789ABCD*#" are permitted. The Play
allowed range. It has been set to the closest Prompt action will continue, play being stopped
allowable value to the requested value, or to a using only those keys which are valid.
default value. The requested value and actual User response: Check and correct the specified
value are given. DTMF keys for the action, then save and validate
User response: Correct the application so that it the state table.
passes a valid value. Severity: White
Severity: White Destination: Log, System Monitor

1400 • 2000
1400 Play Latency Time alert for this 1402 Profile retrieval time alert for this
call call
Explanation: While playing voice data with Explanation: While retrieving application
PlayPrompt, PlayAudioName, PlayGreeting, profile information, for example while answering
PlayVoiceMessage, or PlayVoiceSegment, the a call or gathering mailbox information, the time
delay between the voice being requested by the taken to retrieval profile data from the database
application and being played became greater became greater than the alert threshold defined
than the alert threshold defined by the system by the system parameters in "Application Server
parameters in "Application Server Interface". This Interface". This equates to potentially increased
equates to an increased period of silence being periods of silence being heard by the caller
heard by the caller leading to a decreased quality leading to a decreased quality of service.
of service.
User response: Check for excessive disk, CPU,
User response: Check for excessive disk, CPU, or network load. These cause delays in retrieving
or network load. These cause delays in retrieving voice data from local disk or a remote SSI server.
voice data from local disk or a remote SSI server. If using a remote SSI server also check for
If using a remote SSI server also check for excessive load on the server and examine NFS
excessive load on the server and examine NFS performance.
performance.
Severity: White
Severity: White
1403 Time to check voice messages
1401 Underrun Margin Time alert for alert for this call
this call
Explanation: The time taken to retrieve voice
Explanation: While playing voice data with messaging information for a subscriber when
PlayPrompt, PlayAudioName, PlayGreeting, using the Check Voice Messages state table action
PlayVoiceMessage, or PlayVoiceSegment, the became greater than the alert defined by the
device driver was close to running out of voice system parameters in "Application Server
data to play. The accepted alert value is defined Interface". This equates to potentially increased
by the system parameters in "Application Server periods of silence being heard by the caller
Interface". If the device driver runs out of voice leading to a decreased quality of service.
data to play, the system continues to play voice
data when more is available, but the caller hears
or network load. These cause delays in retrieving
a pause in the voice. Note: This report is based
voice data from local disk or a remote SSI server.
on an average calculated every minute
If using a remote SSI server also check for
User response: This is probably caused by the excessive load on the server and examine NFS
voice input buffer to the device driver being too performance.
small, and is most likely to happen when the
Severity: White
system is heavily loaded. Increase the size of the
buffer using the Normal Play/Record Max Data Destination: Log, System Monitor
system parameter.
Severity: White 2000 Could not obtain memory buffers
Destination: Log, System Monitor Explanation: The system could not obtain
memory buffers and tried to free any available
memory buffers. The application requires more
memory than is available.

2002 • 2008
User response: Increase the size of the buffer

2006 No free channel processors could
pool. Increase the Application Server Interface :
be allocated
Number of Pool Buffers system parameter. If a
lot of voice is played, trying using compressed Explanation: No free channel processes are
rather than clear channel. If a large number of available.
prompts are played, ensure that Application
User response: Change the Application Server
Server Interface : Time in Cache is no longer than
Interface : extra channel process system
the longest prompt segment. If a lot of voice is
parameter to increase the number of channel
played outside prompts, call IBM to ask for your
processes.
voice preload parameters to be decreased.
Severity: Yellow
Severity: Yellow
2007 Low free channel process warning

2002 Channel process manager
initialization failed Explanation: The system has a low number of
free channel processes available. This is a
warning to take remedial action. No further error
initialization failed.
2007s will be logged until error 2008 has
User response: WebSphere Voice Response is occurred.
inoperable. Call IBM Support.
User response: Change the Application Server
Severity: Red Interface : extra channel process system
parameter to increase the number of channel
Destination: Log, System Monitor, Alertable
processes.
Severity: Yellow
2003 Internal channel process manager
error Destination: Log, System Monitor
detected an invalid condition. 2008 Low free channel process warning
cleared
User response: Try again. If the problem
persists, call IBM Support. Explanation: The system now has enough free
channel processes available.
Severity: Red
User response: None. This message is issued to
help you to assess the number of channel
processes that you need. If the number of free
2004 Channel process manager received channel processes falls below the threshold
invalid message again, error 2007 is logged.
Explanation: The channel process manager Severity: Green

received an invalid message.
User response: If the problem persists, call IBM
Support.
Severity: Yellow

DB2 return codes
The return codes in Table 8 are generated by database access routines and
recorded in the errno value in the errorlog entry.
If an errno value is not described here, check the AIX errno value for a
description of the error, and contact IBM Support if necessary.
If while creating or restoring the WebSphere Voice Response database or

starting WebSphere Voice Response you see a DB2 error not listed in Table 8,
try recycling WebSphere Voice Response. Shutting down and restarting the
system can make temporary problems disappear. If you still experience DB2
errors after this, contact IBM Support.
Table 8. DB2 return codes
SQL
code SQLSTATE Explanation User response
-0001 not A database function failed The DB2 server may have been
applicable because the database was stopped manually, make sure it is
not connected or had been running and restart WebSphere
disconnected. Voice Response. If the problem
-0968 57011 One of the file systems Make sure that your file systems
containing the WebSphere have enough free space, then retry
Voice Response DB2 the operation.
database is full. The
transaction or request
failed.
-3006 not This error can occur when Make sure that the file system
applicable exporting or importing containing the $DB directory has
WebSphere Voice Response enough free space, then retry the
application data using operation.
either the Application
Manager or the command
line utilities. The most
likely cause is that there is
not enough space in the
file system to write the
SQL message file.

Table 8. DB2 return codes (continued)
SQL
code SQLSTATE Explanation User response
-10018 not This error occurs when Make sure that the file system
applicable exporting WebSphere Voice containing the $DB directory has
Response application data enough free space, then retry the
using either the operation.
Application Manager or
the command line utilities
and there is not enough
space in the file system to
create the exported data.
1032N 57019 The database manager has The database manager needs to be
not been started. The started. You can either:
WebSphere Voice Response v Restart the pSeries computer; the
database cannot be created database manager should start
and WebSphere Voice automatically, or,
Response cannot be started
v Log in as root and key the
until the database manager
following commands to start the
has been started.
database manager:
cd /usr/lpp/dirTalk/tools
. ./vae.setenv
su - $DBINSTANCE -c db2start
You can then start WebSphere

Voice Response. If the problem

DBSM (database server) return codes
The return codes in Table 8 on page 191 are generated by database access
routines and recorded in the error_no value in the errorlog entry.
If an error_no value is not described here, check the AIX errno value for a
description of the error, and contact IBM Support if necessary.
Table 9. WebSphere Voice Response database return codes
error_no Description Explanation User response
2 No such file or An operation failed Try to establish which

directory because the specified file operation received this error,
could not be found. check and correct the data if
necessary, and retry.
5 I/O error An operation failed Check the AIX system log

because a input/output (using the "errpt -a"
error has occurred. This command) for any evidence
may indicate a hardware of hardware errors. If there is
problem. a hardware error, consider
shutting down WebSphere
Voice Response, as system
operation may be affected.
9 Bad file An operation failed Check the errorlog, because

descriptor because an invalid file this error can be preceded by
descriptor was specified. one which more correctly
describes the problem. If not
and this error persists after
you have restarted
WebSphere Voice Response,
13 Permission An operation failed Check the error details, and

denied because the file the ownership and file
permissions would not permissions. See the
allow it. "vae.setuser" utility in
WebSphere Voice Response for
AIX: Installation to reset the
permissions if necessary.
17 File exists An attempt was made to Try to establish what

create a database file or operation received this error,
table, but it already check and correct the data if
exists. necessary, and retry.

Table 9. WebSphere Voice Response database return codes (continued)
24 Too many open A process has reached the Restart WebSphere Voice
files per-process limit on the Response. If this problem
number of files open persists, then contact IBM
concurrently. Support.
27 File too large An attempt was made to Check the error details of the
increase the size of a affected file.
database file or table
beyond the system limit.
28 No space left on An operation failed Delete any unnecessary data

device because there was or increase the size of the
insufficient space in the relevant file system(s).
file system. Restart WebSphere Voice
Response, specifying forced
recovery.
30 Read only file A write operation failed Reconfigure the file system
system because the file system and restart WebSphere Voice
was mounted as Response.
read-only.
-4201 End-of-file The end of the file was None normally required.
encountered encountered on a read of However, this can happen
a database file or table. when an operation expects a
record or row to exist, but it
doesn’t.
-4202 Beginning-of-file The beginning of the file None normally required.

encountered was encountered on a However, this can happen
read of a database file or when an operation expects a
table. record or row to exist, but it
doesn’t.
-4203 Intentions denied The requested database Try to establish which

access intentions cannot operation received this error,
be granted because and retry. This may be a
another process(es) transient condition. If the
already hold more problem persists, contact IBM
restrictive intentions on Support.
the file.

5001 • 5003
Table 9. WebSphere Voice Response database return codes (continued)
-4204 Duplicate key An attempt was made to Try to establish which

add/insert a record/row operation received this error,
into a database file/table, check and correct the data if
but the request failed necessary, and retry. If the
because a unique index problem persists, contact IBM
already contains the same Support.
data.
-4206 No record Either no record was If the problem persists after

found which matched the restarting WebSphere Voice
specified key, or a Response specifying forced
delete/update was recovery, then contact IBM
attempted when the Support.
record was not locked.
-4207 Not an index An operation was Restart WebSphere Voice

attempted which required Response. If the problem
the use of a database persists, then contact IBM
index, but the specified Support.
index did not exist.
-4208 File needs A file was found to need Restart WebSphere Voice
recovery recovery when it was Response and specify forced
opened. recovery, noting any errors
that occur. If the problem
persists, contact IBM
Support.
Explanation: A database server process could

5001 Cannot receive data from message
not initialize correctly. This may cause the system
queue
not to function as expected.
Explanation: A process could not receive a
User response: Restart WebSphere Voice
message from an AIX message queue. This error
Response, and, if necessary, AIX. If the problem
may cause the process to exit.
persists, call IBM Support.
Severity: Red
persists, call IBM Support. Destination: Log, System Monitor, Alertable
Severity: Red
5003 Unable to attach to message
queue. Process exiting.
5002 Task initialization failed. Process
not attach to an AIX message queue. The process
exiting.

5004 • 5021
exits abnormally and the system may not Severity: Red

function as expected.
5008 Get buffer blocks failed
Explanation: Could not get a system 4KB buffer
Severity: Red
for a database server operation.
User response: Increase the buffer pool as
appropriate.
5004 Could not allocate memory.
Severity: Red
System call malloc() failed.
not allocate memory when required. If sufficient
memory was not available when the process was 5010 Unable to open database file
being initialized, the process may abend. If the
memory was required to satisfy an application Explanation: An attempt to open a database file
request, the request will fail. failed.
User response: Restart WebSphere Voice User response: If the errno is -2, the file could
Response, and, if necessary, AIX. If the problem not be opened because it does not exist. This
persists, call IBM Support. could be because an application has made an
incorrect request (for example, invoking a
Severity: Red PlayVoiceSegment action when the voice
directory has not been created). Use the message
parameters to determine if this error is being
produced because of an application error.
Severity: Yellow
Explanation: A database server could not send
data to another process. The affect of this will
vary, but in the case where a process has
requested data from the database server, an 5018 Close failed
appropriate notification will be returned to the
application. Other messages may be issued Explanation: The system failed to close a file.
which supplement the data in this message. User response: Keep track of the frequency of
User response: Restart WebSphere Voice the error. If it happens frequently, call IBM
Response, and, if necessary, AIX. If the problem Support.
persists, call IBM Support. Severity: White
Severity: Red Destination: Log, System Monitor
5021 Read lock failed
5007 Invalid file permissions Explanation: The system failed to establish read
Explanation: The file permissions prevented a lock.
particular operation. User response: Keep track of the frequency of
User response: Check the permissions on the the error. If it happens frequently, call IBM
file specified in the errorlog. Support.

5022 • 5046
Severity: White
5036 File delete failed
Explanation: The system could not delete the
file.
5022 Write lock failed
User response: If this problem persists, call IBM
Explanation: The system failed to establish Support.
write lock.
Severity: Yellow
User response: Keep track of the frequency of
Destination: System Monitor
the error. If it happens frequently, call IBM
Support.
5039 File compression failed
Severity: White
Explanation: An attempt to compress a voice
database file (segment or message) failed. When
the data in a file becomes fragmented,
5024 Seek failed WebSphere Voice Response automatically tries to
reclaim the free space by compressing the file.
Explanation: Could not move the file pointer to The most likely reasons for such a failure is a
the specified location. This can be caused by a lack of free disk space required to complete the
bad file descriptor or bad parameter passed in. operation, or the file may have been in use when
User response: Keep track of the frequency of the compression was attempted.
the error. If it happens frequently, call IBM User response: WebSphere Voice Response
Support. retries the operation daily until it is successful. If
Severity: White the reason for the failure is lack of disk space,
you may want to increase the size of the file
Destination: Log, System Monitor system or delete any unnecessary data (for
example, error logs, statistics, test applications, or
5027 Write failed test data).
Explanation: VAGSERVER could not write data Severity: Yellow

to a file. This error can be caused by a bad file Destination: Log, System Monitor
descriptor or locked file.
User response: Verify that the file descriptor 5045 Segment retrieve failed
and file are not locked. If you can`t correct the
problem, call IBM Support. Explanation: There are four possible reasons for
this: 1. memcpy() from DMS buffer to write
Severity: Yellow segment text parm failed. 2. Segment text file
Destination: Log, System Monitor length is corrupted. 3. Segment text seg_id is
corrupted. 4. memcpy() from DMS buffer to
write segment text failed.
5031 Read failed
Explanation: The system failed to read data
from a file. Severity: Yellow
User response: If this problem persists, call IBM Destination: Log, System Monitor
Support.
Severity: Yellow 5046 Segment create failed

5049 • 5061
Explanation: Tried to create a voice segment Severity: Red

that already exists.
User response: Choose another voice segment
ID or remove the existing voice segment.
Severity: White
Explanation: The subfunction on an invalidate
Destination: Log, System Monitor prompt directory function call is incorrect.
5049 Could not retrieve voice segment
Severity: Red
text data
Explanation: A request to obtain the text data
for a voice segment failed.
Support. Explanation: The subfunction on an invalidate
segment function call is incorrect, but the
Severity: White
segment file is actually a variable length file.
Destination: Log
Severity: Red
5054 Request received with invalid
data Destination: Log, System Monitor
Explanation: A database server received a
request which was not in the expected format. 5059 Invalidate var map relations failed
User response: This error normally indicates a Explanation: The subfunction on an invalidate
software malfunction. If it continues to occur var map function call is incorrect.
after restarting WebSphere Voice Response, call
IBM Support. User response: Call IBM Support.
Severity: Red Severity: Red
5055 Invalidate failed 5061 System call fork() failed
Explanation: One of the parameters to the Explanation: A process could not recreate
SGAM server routine, which sends invalidate another instance of itself using the fork() system
voice data messages, is incorrect. call. The system may not function correctly. The
most likely reason for the failure is a lack of
User response: Call IBM Support. system resources.
Severity: Red User response: Check that the WebSphere Voice
Response account does not own too many
processes. There is a system wide limit called
"Maximum number of user processes" (or
5056 Invalidate state table failed MAXUPROCS) which controls this. You may
want to increase this value using the SMIT tool
Explanation: The subfunction on an invalidate
after checking that there are no unexpected
state table function call is incorrect.
processes (for example, custom servers under
User response: Call IBM Support. test) currently running. Check also that system

5062 • 5069
memory is not constrained and that any paging

5065 Close file or table failed (dmsclos
devices are not fully used.
or dmstclo)
Severity: Red
Explanation: An attempt to close a database file
Destination: Log, System Monitor, Alertable or table failed. The error details contain the name
of the file or table. The error_no value is set to
the AIX errno or database return code received.
5062 Open file or table failed
(dmsopen or dmstopn) User response: Refer to the description of
WebSphere Voice Response database return codes
Explanation: An attempt to open a database file in the Problem Determination book.
or table failed. The error details contain the file
or table. The error_no value is set to the AIX Severity: White
errno or database return code received.
Destination: Log
User response: Refer to the description of
5067 Add record failed (dmsadd)
the Problem Determination book.
Explanation: An attempt to add a record to a
Severity: Yellow
database file failed. The error details contain the
Destination: Log, System Monitor name of the file. The error_no value is set to the
AIX errno or database return code received.
5063 Create file or table failed User response: Refer to the description of
(dmscrea or dmstopn) WebSphere Voice Response database return codes
in the Problem Determination book.
Explanation: An attempt to create a database
file or table failed. The error details contain the Severity: Yellow
file or table. The error_no value is set to the AIX
errno or database return code received.
5068 Get record by key failed
(dmsgetk)
Explanation: An attempt to read a record by
Severity: Red
key from a database file has failed. The error
Destination: Log, System Monitor, Alertable details contain the name of the file. The error_no
value is set to the AIX errno or database return
code received.
5064 Create index failed (dmscrei or
dmsicre) User response: Refer to the description of
Explanation: An attempt to create an index on a in the Problem Determination book.
database file or table failed. The error details
contain the name of the file or table. The Severity: Yellow
error_no value is set to the AIX errno or database
return code received.
5069 Get record sequentially failed
(dmsgets)
Explanation: An attempt to read the next record
Severity: Red
in a key search from a database file has failed.
Destination: Log, System Monitor, Alertable The error details contain the name of the file.

5070 • 5076
The error_no value is set to the AIX errno or WebSphere Voice Response database return codes
database return code received. in the Problem Determination book.
User response: Refer to the description of Severity: Yellow
in the Problem Determinationbook.
Severity: Yellow
5073 Modify record failed (dmsmodc)
Destination: Log
Explanation: An attempt to modify a record in
a database file failed. The error details contain
5070 Get record by RBA failed the name of the file or table. The error_no value
(dmsgetd) is set to the AIX errno or database return code
received.
Explanation: An attempt to read a record by
address failed. The error details contain the name User response: Refer to the description of
of the file or table. The error_no value is set to WebSphere Voice Response database return codes
the AIX errno or database return code received. in the Problem Determination book.
User response: Refer to the description of Severity: Yellow
Severity: Yellow
5074 Commit failed (dmscmit)
Explanation: An attempt to force file or table
updates to disk failed. The error details contain
5071 Deletion of row/record/table/file the name of the file or table. The error_no value
failed (dmsdelt) is set to the AIX errno or database return code
received.
Explanation: An attempt to delete a row or
record from a file or table failed, or an error was User response: Refer to the description of
received when deleting a file or table. The error WebSphere Voice Response database return codes
details contain the name of the file or table. The in the Problem Determination book.
error_no value is set to the AIX errno or database
Severity: Yellow
return code received.
Destination: Log
in the Problem Determination book. 5076 Get record key failed (dmskey)
Severity: Yellow Explanation: An attempt to read a record by
key from a database file has failed. The error
Destination: Log
details contain the name of the file. The error_no
5072 Modify record failed (dmsmod) code received.
Explanation: An attempt to modify a record in User response: Refer to the description of
a database file failed. The error details contain WebSphere Voice Response database return codes
the name of the file or table. The error_no value in the Problem Determination book.
is set to the AIX errno or database return code
Severity: Yellow
received.

5077 • 5085
User response: If the requester has failed, other

5077 Get record by address failed
error messages will be generated to show this. If
(dmsrba)
no such error messages are logged, restart
Explanation: An attempt to read a record by WebSphere Voice Response and if the problem
address from a database file failed. The error persists, call IBM Support.
details contain the name of the file. The error_no
Severity: Green
code received. Destination: Log
WebSphere Voice Response database return codes 5082 Attempt to update nonexistent
in the Problem Determination book. unit
Severity: Yellow Explanation: A block from a multi-block request
is received. It is not the first block in the request,
yet there is no record of any previous blocks
having been written.
5078 File type corrupted
User response: None. If the problem persists,
Explanation: During the processing of a request, call IBM Support.
an internal variable became corrupted. This may
Severity: Yellow
indicate a software malfunction.
Destination: Log
Response. If the problem persists, call IBM
Support. 5083 Could not make file name
Severity: Red Explanation: The print routine used to create
file names failed.
5079 Function type corrupted Severity: Yellow
Explanation: During the processing of a request Destination: Log, System Monitor
an internal variable became corrupted. This may
indicate a software malfunction.
5084 Select on table failed (dmsslct)
Response. If the problem persists, call IBM Explanation: A query on a database table has
Support. failed. The error details contain the name of the
file. The error_no value is set to the AIX errno or
Severity: Red database return code received.
Destination: Log, System Monitor, Alertable User response: Refer to the description of
5080 Data timeout exceeded
Severity: Yellow
Explanation: In a multi-block request for voice
data, the next block was not received within an Destination: Log, System Monitor
internally defined time period. The request fails,
and an appropriate indication is returned to the
application. This may indicate that the requesting 5085 Update row failed (dmsupdt)
process has failed or is not functioning correctly. Explanation: An attempt to update a database
table row failed. The error details contain the

5086 • 5094
name of the file. The error_no value is set to the Explanation: An application level lock buffer
AIX errno or database return code received. could not be obtained because a free buffer could
not be found. The request is rejected and an
appropriate indication returned to the
application.
Severity: Yellow
Destination: Log, System Monitor Support.
Severity: Yellow
5086 Fetch row failed (dmsftch)
Explanation: An attempt to fetch a database
table row failed. The error details contain the
5090 File descriptor list full
name of the file. The error_no value is set to the
AIX errno or database return code received. Explanation: The file descriptor list for either
voice segment files, greeting files, audio name
files, or message files is full. This is caused by
the improper definition of system parameters.
The size of the file descriptor lists are determined
Severity: Yellow from the maximum number of languages,
compression codes, and application groups that
Destination: Log, System Monitor are defined as system parameters.
User response: Modify the system parameters
5087 Insert row failed (dmsisrt) for this area. If the problem persists, call IBM
Explanation: An attempt to insert a row into a Support.
database table failed. The error details contain Severity: Yellow
the name of the file. The error_no value is set to
the AIX errno or database return code received. Destination: Log, System Monitor

WebSphere Voice Response database return codes 5093 Recover DMS failed
Explanation: The recover() function failed
Severity: Yellow because there is no more disk space or there has
been a database internal error.
5088 SGAM data unit locked Severity: Red
Explanation: A request was made on a data Destination: Log, System Monitor, Alertable
unit that is already in use.
User response: None. 5094 Vital statistics corrupt
Severity: Yellow Explanation: For vag_dsptch.c/add_SMSI_db()

this means one of: 1. Record size larger than file.
Destination: Log 2. Corrupt record count in header. 3. Unexpected
EOF encountered in header. 4. Corrupt CRC
5089 No application level lock buffer number in file. For make_fname.c, the file type is
available not listed in the main case statement.

5095 • 5101
User response: Determine the cause of the Severity: Yellow

problem and correct it, if possible. If the problem
Severity: Yellow
5098 Invalid voice directory group ID
Destination: Log, System Monitor specified
Explanation: A request to use a voice directory
5095 Key is reserved: access not in a state table failed because the group ID
permitted provided is invalid. The group must be an
existing voice directory in the current language.
Explanation: There was either a create, update,
delete, or annotate request on voice data with User response: Ensure that you are specifying
key=0. This key is reserved to hold WebSphere an existing directory group ID in the request.
Voice Response release and version information.
Severity: White
Severity: Red
Destination: Log, System Monitor 5099 Invalid profile ID specified
Explanation: An attempt was made to retrieve
5096 Voice database file not found an application profile, but the profile ID specified
did not exist.
Explanation: A request was made to access
voice data (for example, segment, message, audio User response: Ensure that a correct application
name, or greeting) but the requested database file profile ID is specified in the request.
did not exist.
Severity: White
User response: This error is normally caused by
an application trying to retrieve voice data that
has not yet been created, or that has been deleted
by the administrator or developer in error. The 5100 Invalid mailbox ID specified
parameters identify which voice directory or
message file has been specified, and if the Explanation: An attempt was made to use a
request was for a greeting or an audio name. An particular mailbox ID, but the ID did not exist.
appropriate edge is returned to the state table, or User response: Ensure that a correct mailbox ID
return code to the custom server, that generated is specified in the request.
this request. If the request is valid, ensure the
voice data is recreated. If the request is invalid, Severity: White
correct the application that caused the error. Destination: Log, System Monitor
Severity: White
Destination: Log, System Monitor 5101 Invalid distribution list ID
specified
5097 Internal programming error Explanation: An attempt was made to use a

particular distribution list ID, but the ID did not
Explanation: An internal software error exist.
occurred.
User response: Ensure that a correct
User response: Restart WebSphere Voice distribution list ID is specified in the request.
persists, call IBM Support. Severity: White

5102 • 5205
Destination: Log, System Monitor Destination: Log, System Monitor, Alertable
5102 Access not allowed to distribution 5201 Database connection failed

list
Explanation: An error occurred while trying to
Explanation: A request was made to access a connect to the database. The database is
private mailbox using an application profile that currently being recovered because of an AIX
does not own the mailbox. system crash. The command is retried until a
connection has been established.
User response: Any requests to access a private
mailbox must originate from the owner of the User response: None.
mailbox. Correct the request and try again.
Severity: Yellow
Severity: White
5202 Database connection established
5103 Siglib error setting message
Explanation: The database recovery has
waiting indicator
completed. A connection to the database has
Explanation: An error occurred trying to set the been established.
message waiting indicator.
User response: Specify No for the MWI
Severity: Green
Automatically Set parameter in the Exchange
Data Link parameters group (use the System Destination: Log, System Monitor
Configuration option on the Configuration
menu).
5204 Database problem avoided
Severity: Red
Explanation: A potential problem with the
Destination: Log, System Monitor, Alertable database has been avoided. See error text for
more details.
5200 SQL database transaction or User response: See error text for details.
request failure
Severity: White
issue a database function. The operation which Destination: Log, System Monitor
caused this error has not completed, and an error
indication has been returned to the application, 5205 MWI activation not configured.
custom server, or user interface component that MWISERVER shutting down.
issued the request. The application state table
action, custom server call, returns a failure Explanation: WebSphere Voice Response is not
condition. The user interface produces an configured to set the message waiting indicator
appropriate error dialog. (MWI) when voice messages are received by
subscribers. The system parameter "MWI
User response: Refer to the section in the Automatically Set" in the Exchange Data Link
Problem Determination book that describes parameter group is set to "No". The
expected database errors, using the error alarm MWISERVER server process which sets MWI is
parameters to provide further diagnosis. If the not required and has shutdown.
error is not documented in that section, contact
IBM Support. User response: If you need MWI to be set,
change the system parameter and restart
Severity: Red

5250 • 5252
WebSphere Voice Response. pathname to the voice storage directory

$CUR_DIR:
Severity: White
Segments:
Destination: Log, System Monitor voice/segment/<lang>/<vdirname>/<compr>
<segid>
Greetings:
5250 __OM_OpenVoice returned an voice/greet/<userid>.<greetid>.<compr>
error Audio Names:
Explanation: An error occurred opening a voice voice/aname/<userid>.<boxid>.<compr>
object. Messages:
voice/msg/<YYMMDDHH>/<msgid>
User response: .<msgcreatetime>.<compr>
Attachments:
Examine the error log for details. The voice/msg/<YYMMDDHH>/<msgid>
filename parameter is normally formatted .<msgcreatetime>.@.<atttype>.<attid>
as follows, in all cases prefixed by the Java voice files:
pathname to the voice storage directory voice/ext/<javaid>
$CUR_DIR: In addition temporary work files may be
Segments: found as follows in all of these locations
voice/segment/<lang>/<vdirname>/<compr> .workspace.<hostname>.<pid> where <xx>
<segid> should be replaced:
Greetings:
voice/greet/<userid>.<greetid>.<compr> Severity: Yellow
Audio Names: Destination: Log, System Monitor
voice/aname/<userid>.<boxid>.<compr>
Messages:
voice/msg/<YYMMDDHH>/<msgid> 5252 __OM_GetVoice returned an error
.<msgcreatetime>.<compr> Explanation: An error occurred retrieving voice
Attachments: data from the database.
.<msgcreatetime>.@.<atttype>.<attid> User response:
Java voice files: voice/ext/<javaid>
In addition temporary work files may be Examine the error log for details. The
found as follows in all of these locations filename parameter is normally formatted
.workspace.<hostname>.<pid> where <xx> as follows, in all cases prefixed by the
should be replaced: pathname to the voice storage directory
$CUR_DIR:
Severity: Yellow
Segments:
Destination: Log, System Monitor voice/segment/<lang>/<vdirname>/<compr>
<segid>
Greetings:
5251 __OM_CloseVoice returned an voice/greet/<userid>.<greetid>.<compr>
error Audio Names:
Explanation: An error occurred closing a voice voice/aname/<userid>.<boxid>.<compr>
object. Messages:
User response: .<msgcreatetime>.<compr>
Attachments:
filename parameter is normally formatted .<msgcreatetime>.@.<atttype>.<attid>
as follows, in all cases prefixed by the

5253 • 5255
Java voice files: User response:

voice/ext/<javaid>
In addition temporary work files may be Examine the error log for details. The
found as follows in all of these locations filename parameter is normally formatted
.workspace.<hostname>.<pid> where <xx> as follows, in all cases prefixed by the
should be replaced: pathname to the voice storage directory
$CUR_DIR:
Severity: Yellow
This information is subject to change in
Destination: Log, System Monitor further releases but may prove useful in
case of file access problems ie check
permissions, disk storage.
5253 __OM_GetVoiceHdr returned an
Segments:
error
voice/segment/<lang>/<vdirname>/<compr>
Explanation: An error occurred retrieving the <segid>
voice header data from the database. Greetings:
voice/greet/<userid>.<greetid>.<compr>
User response: Audio Names:
Examine the error log for details. The Messages:
filename parameter is normally formatted voice/msg/<YYMMDDHH>/<msgid>
as follows, in all cases prefixed by the .<msgcreatetime>.<compr>
pathname to the voice storage directory Attachments:
$CUR_DIR: voice/msg/<YYMMDDHH>/<msgid>
Segments: .<msgcreatetime>.@.<atttype>.<attid>
voice/segment/<lang>/<vdirname>/<compr> Java voice files:
<segid> voice/ext/<javaid>
Greetings: In addition temporary work files may be
voice/greet/<userid>.<greetid>.<compr> found as follows in all of these locations
Audio Names: .workspace.<hostname>.<pid> where <xx>
voice/aname/<userid>.<boxid>.<compr> should be replaced:
Messages:
voice/msg/<YYMMDDHH>/<msgid> Severity: Yellow
.<msgcreatetime>.<compr> Destination: Log, System Monitor
Attachments:
.<msgcreatetime>.@.<atttype>.<attid> 5255 __OM_PutVoiceHdr returned an
Java voice files: error
voice/ext/<javaid>
Explanation: An error occurred writing the
In addition temporary work files may be
voice header data to the database.
found as follows in all of these locations
.workspace.<hostname>.<pid> where <xx> User response:
should be replaced:
Examine the error log for details. The
Severity: Yellow
filename parameter is normally formatted
Destination: Log, System Monitor as follows, in all cases prefixed by the
pathname to the voice storage directory
$CUR_DIR:
5254 __OM_PutVoice returned an error
Segments:
Explanation: An error occurred writing voice voice/segment/<lang>/<vdirname>/<compr>
data to the database. <segid>

5256 • 5300
Greetings: found as follows in all of these locations

voice/greet/<userid>.<greetid>.<compr> workspace.<hostname>.<pid> where <xx>
Audio Names: should be replaced:
Severity: Yellow
Messages:
voice/msg/<YYMMDDHH>/<msgid> Destination: Log, System Monitor
.<msgcreatetime>.<compr>
Attachments:
voice/msg/<YYMMDDHH>/<msgid> 5257 __OM_SaveVoice returned an
.<msgcreatetime>.@.<atttype>.<attid> error
Java voice files: Explanation: An error occurred saving a voice
voice/ext/<javaid> object.
In addition temporary work files may be
found as follows in all of these locations User response:
.workspace.<hostname>.<pid> where <xx>
should be replaced: Examine the error log for details. The
filename parameter is normally formatted
Severity: Yellow as follows, in all cases prefixed by the
Destination: Log, System Monitor pathname to the voice storage directory
$CUR_DIR:
Segments:
5256 __OM_DeleteVoice returned an voice/segment/<lang>/<vdirname>/<compr>
error <segid>
Explanation: An error occurred deleting a voice Greetings:
object. voice/greet/<userid>.<greetid>.<compr>
Audio Names:
User response: voice/aname/<userid>.<boxid>.<compr>
Messages:
filename parameter is normally formatted .<msgcreatetime>.<compr>
as follows, in all cases prefixed by the Attachments:
pathname to the voice storage directory voice/msg/<YYMMDDHH>/<msgid>
$CUR_DIR: .<msgcreatetime>.@.<atttype>.<attid>
Segments: Java voice files: voice/ext/<javaid>
voice/segment/<lang>/<vdirname>/<compr> In addition temporary work files may be
<segid> found as follows in all of these locations
Greetings: .workspace.<hostname>.<pid> where <xx>
voice/greet/<userid>.<greetid>.<compr> should be replaced:
Audio Names:
Severity: Yellow
Messages: Destination: Log, System Monitor
.<msgcreatetime>.<compr>
Attachments: 5300 Deinstall of custom server failed
voice/msg/<YYMMDDHH>/<msgid> Explanation: You tried to deinstall a custom
.<msgcreatetime>.@.<atttype>.<attid> server which was running on another WebSphere
Java voice files: Voice Response node. You cannot deinstall a
voice/ext/<javaid> custom server if it is running on any WebSphere
In addition temporary work files may be Voice Response node in an SSI (single system
image) cluster.

5301 • 5314
User response: Stop the custom server that is previously reported problem with the file
running on the indicated WebSphere Voice identified below is now clear.
Response node, before trying to deinstall the
User response: None
custom server.
Severity: Green
Severity: White
5312 DBHEALTH reports problem with

5301 Database server down
CUR_DIR or DB2
Explanation: The DBHEALTH process
connect to the database. The database server is
periodically checks files under CUR_DIR. The
currently down. The command is retried until a
AIX statx() on the file identified below is
connection has been established.
different from that stored in the DB2 by
User response: Investigate network and DB2. fsupdate. WebSphere Voice Response will cease
taking calls until the problem is fixed.
Severity: Red
User response: Investigate network and DB2.
Check that the file indicated below is accessible.
If the file has been erased run fsupdate.
5302 Database server up
Severity: Red
Explanation: The database server has come up.
A connection to the database has been
established.
5313 DBHEALTH problem with
CUR_DIR or DB2
Severity: Green
Destination: Log periodically checks DB2 and files under
CUR_DIR. The timeout for the resource set on
the Application Server Interface panel was
5310 DBHEALTH reports problem with exceeded. WebSphere Voice Response will cease
CUR_DIR files taking calls until the problem is fixed.
Explanation: The DBHEALTH process User response: Investigate network and DB2.
periodically checks files under CUR_DIR. The Check that the resource indicated is accessible. If
AIX statx() has found a problem as indicated by the resource is a file which has been erased run
error_no. WebSphere Voice Response will cease fsupdate.
Severity: Red
User response: Investigate network. Check that
the file indicated below is accessible. If the file Destination: Log, System Monitor, Alertable
has been erased run fsupdate.
Severity: Red 5314 DBHEALTH problem has cleared
Destination: Log, System Monitor, Alertable Explanation: The DBHEALTH process
periodically checks DB2 and files under
CUR_DIR. The previously reported problem with
5311 DBHEALTH problem has cleared file is now clear.
Explanation: The DBHEALTH process User response: None
periodically checks files under CUR_DIR. The

5315 • 5320
Severity: Green
5318 Incorrect Mailbox Count Detected
Explanation: The system detected that a users
New or Saved message count is incorrect. The
5315 DBHEALTH DB2 Database system will take steps to fix the invalid count.
problem
User response: The system has corrected the
Explanation: A problem was reported by a SQL invalid count. If the problem persists please call
function. WebSphere Voice Response will cease IBM support.
Severity: White
User response: See below for SQL diagnostic
message. Investigate network and DB2.
Severity: Red
5319 Invalid msg creation time detected
Explanation: The system detected that a
message's creation time was invalid. When using
5316 DBHEALTH DB2 Database Fetch a remote database server in a SSI cluster, a time
data length error daemon should be used to maintain the same
time on all machines, for example, the Network
Explanation: The SQLFetch on the stored Time Protocol (NTP) daemon. However,
filesystem statx() SELECT keystamp from occasionally the times can become
dtuser.nodes where (( db2state = 2 ) or ( db2state unsynchronized and the 5319 DBSM (database
= 0 )) did not return enough data. WebSphere server) return code can be thrown.
Voice Response will cease taking calls until the
problem is fixed. User response: To resolve the problem if using
the NTP daemon (as the root user):
The data can be reset with fsupdate. Extra 1. Stop xntpd on the clients and on the database
debugging information is added to DTstatus.out server by using the command: stopsrc -s
if the DBHEALTH process is sent SIGUSR1 kill xntpd
-30 pidDBHEALTH. The same extra debugging is 2. Set the clock's time by calling the
also in trace trace. settimeofday subroutine by using the
command: ntpdate -b
Severity: Red
3. Clear the contents from the /etc/ntp.drift
Destination: Log, System Monitor file
4. Restart the servers by using the command:
5317 DBHEALTH reports problem with startsrc -s xntpd
CUR_DIR
If the problem persists please call IBM support.
periodically checks files under CUR_DIR. An Severity: Yellow
attempt to write and read the file identified
below failed. WebSphere Voice Response will
cease taking calls until the problem is fixed.
5320 System clock jumped
Check that the file indicated below is accessible. Explanation: The system detected that the
system clock was changed by a value greater
Severity: Red
than 4 seconds.
User response: If conflicting clock deamons are

5321 • 5322
present on the system disable all but one. If the

system clock is changed by large values it may
result in unexpected system behaviour.
Severity: Yellow
5321 Cannot set interval timer

Explanation: DBHEALTH was unable to set an
interval timer, and may raise timeout errors if the
system clock is adjusted by large values.
User response: If the system clock is changed
by large values it may result in unexpected
system behaviour. Please ensure this does not
happen. A common cause of this is conflicitng
clock deamons.
Severity: White
5322 Invalid msg sent time detected

Explanation: The system detected that a
message's sent time was invalid.
User response: If the problem persists please
call IBM support.
Severity: Yellow

10001 • 10008
NODEM (Node Manager)

because shared memory is still allocated from a
10001 Could not fork a child process
previous session ofWebSphere Voice Response .
Explanation: Node manager tried to start more This can occur after WebSphere Voice Response
processes than allowed by the AIX system malfunctions when you try to restart it. It
parameter for maximum processes per user. indicates that there is not enough memory in the
system to allocate the number of buffers
User response: Increase the AIX parameter for
specified in the system parameters. This problem
maximum processes per user.
can occur if the number in the system parameter
Severity: Red Number of Pool Buffers is set too high.
Destination: Log, System Monitor, Alertable User response: Release previously allocated AIX
system resources. To change the value of the
system parameter Number of Pool Buffers, use
10002 Could not execute the child the command line utility RDSETBUFS. Type
process RDSETBUFS n, where n is the number of buffers.
Explanation: A major component of the system The number in the system parameter Maximum
will not start because the executable component Cached Buffers will be reset to not more than
is not found or is corrupted. The system may not 60% of the Number of Pool Buffers value.
be able to answer calls, or one or both of the Severity: Red
display panels may not appear.
User response: Restore the named component
from a backup tape. If the condition persists, call
IBM Support. 10007 Attempt to allocate semaphore
failed
Severity: Red
Explanation: Semaphores are still allocated from
Destination: Log, System Monitor, Alertable a previous session of WebSphere Voice Response.
This can occur afterWebSphere Voice Response
10003 Could not start executable file malfunctions when you try to restart it.
Explanation: The system will not start. One of User response: Run the WebSphere Voice
the components required to retrieve WebSphere Response cleanup utility to release previously
Voice Response system parameters will not run. allocated AIX system resources.
This may be because the component initialization Severity: Red
failed, or because the component program file
has been deleted or corrupted. Destination: Log, System Monitor, Alertable
User response: Verify that the component's
start-up requirements are correct. Restore the 10008 Attempt to allocate message
component from backup tape and try again. If queue failed
the condition persists, call IBM Support.
Explanation: Message queues are still allocated
Severity: Yellow from a previous session of WebSphere Voice
Response. This can occur afterWebSphere Voice
Destination: Log, System Monitor Response malfunctions when you try to restart it.
User response: Run the WebSphere Voice
10006 Attempt to allocate shared Response cleanup utility to release previously
memory failed allocated AIX system resources.
Explanation: The system will not initialize Severity: Red

10009 • 10102
Destination: Log, System Monitor, Alertable Severity: Red

Explanation: This indicates that WebSphere 10023 Signalling library configuration
Voice Response resources and function may be problem
limited. It is caused by a component or server
Explanation: A problem occurred while
sending messages to the wrong queue.
WebSphere Voice Response was trying to
User response: Verify that the messages are not configure signalling processes. This is likely to be
coming from a custom server. Call IBM Support. a software error.
Severity: White User response: Not coded
10012 Node manager message queue
removed
10100 System startup error
Explanation: The AIX message queue for node
Explanation: There has been an error while
manager was removed. The system will not
loading default values for host and ASI IDs, or
answer calls, node manager will terminate, and
the system cannot allocate the shared memory
other components will start to fail if they are still
segments SYSPARMS, RD, or UPSERVER.
running.
User response: See "WebSphere Voice Response
User response: Review the system error logs for
software does not start initializing" in the Problem
indications of possible problems. Call IBM
Determination book.
Support.
Severity: Red
Severity: Red
10101 Failed to execute initialization

10013 System parameters file corrupt
script
Explanation: The WebSphere Voice Response
Explanation: The script below failed during
system startup parameters are either invalid or
WebSphere Voice Response system initialization.
not found and the system will not initialize.
The system will not start.
User response: Restore the system parameters
User response: Check that the script
file from backup copies.
"$VAE/sw/bin/dirTalk_atStartup" exists, is
Severity: Yellow executable, and is appropriately owned. Check
the $OAM_LOG_PATH/errorlog and
$OAM_LOG_PATH/DTstatus.out files for
additional errors.
10022 Abnormal termination detected in
Severity: Red
previous WebSphere Voice
Response execution Destination: Log, System Monitor, Alertable
Explanation: WebSphere Voice Response or AIX
may have failed. 10102 Failed to execute shutdown script
User response: Restart systems. Explanation: The script below failed during

10500 • 10202
WebSphere Voice Response system shutdown.

10200 TLS can’t be used as VOIP
The shutdown will complete, but some cleanup
Transport
may not be completed, which could lead to
problems during subsequent startup attempts. Explanation: TLS has been selected as the VoIP
transport protocol, but use of secure SIP TLS has
User response: Check that the script
not been enabled. Secure SIP is not enabled.
"$VAE/sw/bin/dirTalk_atShutdown" exists, is
executable, and is appropriately owned. Check User response: From the VoIP Signalling
the $OAM_LOG_PATH/errorlog and configuration window, either enable use of
$OAM_LOG_PATH/DTstatus.out files for secure SIP (TLS) by setting Secure SIP Enabled
additional errors. to Yes, or set the Transport Protocol to UDP or
TCP.
Severity: White
Severity: Yellow
10500 Database and file system integrity
check failed 10201 Secure SIP Keystore database
does not exist or has incorrect
Explanation: When WebSphere Voice Response
permissions.
starts, it checks to ensure that the AIX file system
being used to store WebSphere Voice Response Explanation: The keystore database required for
AIX voice elements matches the DB2 database secure SIP support does not exist or has incorrect
being used to store data about those voice permissions. Secure SIP is not enabled.
elements. On a standalone system a checksum is
User response: Ensure that the
written to the file system and the DB2 database
/usr/lpp/dirTalk/db/sys_dir/voip/keyring.db
when "DTdatabase -r" is run following
keystore database has been created as
installation. On a single system image (SSI)
documented in “Create the keyring.db database”
cluster, this checksum is written when the
in the WebSphere Voice Response: Voice over IP
database and voice servers are configured.
using Session Initiation Protocol manual., and all its
User response: Check the following: * files haves read/write permission for the
"DTdatabase -r" has been run after installing a WebSphere Voice Response user, typically dtuser.
new release or build. * If working in an SSI
Severity: Yellow
environment, this client has mounted all
necessary remote file systems and is configured Destination: Log, System Monitor, Alertable
with the correct remote database. A typical
reason for failure is a failed NFS mount or
incorrect permissions. * All file systems can be 10202 Unable to access WVR server
read from and written to. If all the above are certificate in Keystore database.
correct and the check still fails, shut down all Explanation: WebSphere Voice Response has
client nodes using the same database and voice been unable to access the server certificate it
servers and run "/usr/lpp/dirTalk/tools/ requires in the keystore database. This may be
fsupdate" to create and write a new checksum to due to one of the following reasons:
the file system and database. Then run
v The database password has not been stashed.
"/usr/lpp/dirTalk/tools/fscheck" to ensure the
check works correctly. WebSphere Voice v The database password has been updated
Response can then be successfully started. since being stashed.
v The certificate has not been added to the
Severity: Red
keystore database. The error text provides an
Destination: Log, System Monitor, Alertable indication of error cause.

10203
User response: Ensure that

the/usr/lpp/dirTalk/db/sys_dir/voip/
keyring.db keystore database has been created
with a stashed password. Ensure that any
password update is reflected in the stashed
password.
Severity: Yellow
10203 Failure Opening GSKit

Explanation: There has been a failure opening
GSKit. Secure SIP is not enabled.
User response: If you want to use TLS
connections and/or secure SIP, enable the flag
using the System Configuration Transport
Protocol parameter.
Severity: White

11001 • 11004
STPD (State Table/Prompt Directory)
11001 No table entries available 11004 Routine called with invalid

request
Explanation: A request for a state table or
prompt directory is denied. The Number of Non Explanation: Invalid subfunction for this
Swap State Tables system parameter is not set component.
high enough for the applications environment.
User response: Set the Number of Non Swap
Severity: Yellow
State Tables system parameter so that when it is
added to the number of channels, the sum Destination: Log, System Monitor
exceeds the maximum number of state tables
expected to be active concurrently.
Severity: Yellow
11002 Request list extended

Explanation: Either the initial table allocations
are too small, or some component is requesting
tables and not releasing them. The system may
run normally when this error occurs occasionally
such as in the first traffic load after starting
WebSphere Voice Response. When the error
continues to occur, the situation may gradually
deplete the buffer pool.
Support.
Severity: White
11003 Table received with bad CRC

Explanation: The state table failed a consistency
check when it was last edited. It was saved
without the consistency check using the State
Generator's SAVE function. This means the state
table is corrupted or was incorrectly edited with
a non-WebSphere Voice Response utility. The
system notifies CHP, plays a system error
message, and then hangs up.
Severity: Yellow

12001 • 12005
VAE (General WebSphere Voice Response)

and restarting AIX, call IBM Support.
12001 Task_init() failed
Severity: Yellow
Explanation: The system tried to restart a
component that was logged in the Process Profile Destination: Log, System Monitor
Table as currently running. Components generate
this error to log an initialization and termination.
12004 Pool_get() failed
User response: This error can be caused by
other error conditions in the system. Review the Explanation: This is a buffer pool problem
WebSphere Voice Response logs and try to caused by one of the following conditions: 1)
correct other problems first. If the problem There are not enough buffers in the buffer pool
persists after shutting down and restarting to handle current traffic load, 2) A system
WebSphere Voice Response, and shutting down component that receives 4KB buffers is not
and restarting AIX, call IBM Support. processing or releasing them fast enough to keep
up with the current traffic, or, 3) A system
Severity: Yellow component is not releasing 4KB buffers when it
is done with them. Many components allocate
some of the 4KB buffers at system start-up. It is
normal for the buffer pool to be partially empty.
12002 Msgrcv() failed This condition causes the system to ignore
incoming calls and can terminate an existing
Explanation: This is an AIX system error. The
session.
message queue is too large to be retrieved. A
component cannot retrieve messages from its User response: This error can be caused by
queue, so it terminates. other error conditions in the system. Review the
WebSphere Voice Response error logs and try to
correct other problems first. If the problem
other error conditions in the system. Review the
persists after shutting down and restarting
WebSphere Voice Response, and shutting down
WebSphere Voice Response, and shutting down Severity: Yellow
Severity: Yellow
Destination: Log, System Monitor 12005 Notify_appl() failed
Explanation: The target component might have
12003 Msgsnd() failed terminated because of other errors or the target
component is invalid. This causes some
Explanation: A component message queue has
WebSphere Voice Response resources to work
been removed, never existed, or the message
incorrectly.
itself is invalid. This causes a request to the
targeted component to be denied. User response: This error can be caused by

12006 • 12018
Severity: Yellow and try to correct other problems first. If the

problem persists after shutting down and
restarting WebSphere Voice Response, and
shutting down and restarting AIX, call IBM
12006 Malloc() failed Support.
Explanation: No system memory is available for Severity: Yellow

allocation. This causes the affected components
to function incorrectly.
12009 Attachm() failed
WebSphere Voice Response error logs and try to Explanation: The WebSphere Voice Response
correct other problems first. If the problem system is not running or a component will not
persists after shutting down and restarting run because it is being started with the wrong
WebSphere Voice Response, and shutting down user name.
User response: Start the WebSphere Voice
Severity: Yellow Response system correctly. This error can be
caused by other error conditions in the system.
Review the WebSphere Voice Response error logs
and try to correct other problems first. If the
12007 Attachs() failed problem persists after shutting down and
restarting WebSphere Voice Response, and
Explanation: The WebSphere Voice Response shutting down and restarting AIX, call IBM
system is not running or a component will not Support.
run because it is being started with the wrong
user name. Severity: Yellow
User response: Start the WebSphere Voice Destination: Log, System Monitor
Response system correctly. This error can be
caused by other error conditions in the system.
Review the WebSphere Voice Response error logs
and try to correct other problems first. If the Explanation: A component received a message
problem persists after shutting down and with an unexpected type. The system ignores
restarting WebSphere Voice Response, and invalid messages.
shutting down and restarting AIX, call IBM
Support.
Severity: Yellow WebSphere Voice Response error logs and try to
12008 Attachq() failed and restarting AIX, call IBM Support.
Explanation: The WebSphere Voice Response Severity: Yellow

system is not running or a component will not
run because it is being started with the wrong
user name.
12018 Applid for initialized task already
User response: Start the WebSphere Voice
in use
Response system correctly. This error can be
caused by other error conditions in the system. Explanation: A component is using the wrong
Review the WebSphere Voice Response error logs application identification (APPL_ID) when it

12020 • 12100
initializes or the system is starting a failed Destination: Log, System Monitor

component. There might be no symptoms on the
system, or a component may seem to be not
12031 Calculate unique key for AIX ID
working, but shows active using the AIX ps
failed
command.
Explanation: Unable to generate unique key for
path of sys_dir and user ID.
WebSphere Voice Response error logs and try to User response: This error can be caused by
correct other problems first. If the problem other error conditions in the system. Review the
persists after shutting down and restarting WebSphere Voice Response error logs and try to
WebSphere Voice Response, and shutting down correct other problems first. If the problem
and restarting AIX, call IBM Support. persists after shutting down and restarting
Severity: White
Severity: White
Destination: Log
12020 Signal setup failed
Explanation: This is an AIX or WebSphere Voice
12032 Environment variable is invalid
Response error. The system shuts down with a
SIGINT signal (kill -2 (Process Id)). The system Explanation: Value for SYS_DIR is incorrect.
should continue to run normally. This error
affects only WebSphere Voice Response User response: This error can be caused by
shutdown. other error conditions in the system. Review the
User response: This error can be caused by correct other problems first. If the problem
other error conditions in the system. Review the persists after shutting down and restarting
WebSphere Voice Response error logs and try to WebSphere Voice Response, and shutting down
correct other problems first. If the problem and restarting AIX, call IBM Support.
WebSphere Voice Response, and shutting down Severity: White
and restarting AIX, call IBM Support. Destination: Log
Severity: Yellow
Destination: Log, System Monitor 12100 Caller not allowed to call function
Explanation: OAM can request a dead channel
12021 Error enroll failed process to be restarted. If a task other than OAM
or NODEM requests this action, this error is
Explanation: Bad parameters in call to generated.
error_enroll.
User response: This error can be caused by other error conditions in the system. Review the
other error conditions in the system. Review the WebSphere Voice Response error logs and try to
WebSphere Voice Response error logs and try to correct other problems first. If the problem
correct other problems first. If the problem persists after shutting down and restarting
persists after shutting down and restarting WebSphere Voice Response, and shutting down
WebSphere Voice Response, and shutting down and restarting AIX, call IBM Support.
Severity: White
Severity: Yellow
Destination: Log

12101 • 12203
Explanation: Attempt to send message with

12101 Appl_id is not a channel process
Notify_appl() with an appl_id out of range of
Explanation: The requested restart_chp valid appl_ids.
application ID is not a channel process.
Severity: White
Severity: White
Destination: Log
Destination: Log
12201 Invalid IPC_TYPE / IPC_ID
12102 No channel process available to
Explanation: Invalid ipc_id used in
perform task
Notify_appl().
Explanation: The restart_chp could not find an
idle channel process to close.
User response: This error can be caused by WebSphere Voice Response error logs and try to
other error conditions in the system. Review the correct other problems first. If the problem
WebSphere Voice Response error logs and try to persists after shutting down and restarting
correct other problems first. If the problem WebSphere Voice Response, and shutting down
persists after shutting down and restarting and restarting AIX, call IBM Support.
Severity: White
Destination: Log
Severity: White
Destination: Log
12202 Message pointer is null. Cannot
send message.
12103 Attempt to restart channel process
Explanation: Message pointer in Notify_appl()
failed
is null or invalid.
Explanation: Program error in restart_chp().
Severity: Yellow
Severity: White
Destination: Log
12203 Cannot send message
12200 Invalid target appl_id

12250 • 12254
Explanation: Cannot send message within

12252 DPRB circular buffer overflowed
Notify_appl().
Explanation: During a host session, the process
requesting host session action from channel
process is sending request DPRBs faster than
channel process can process and the buffer space
for host session is filled up.
WebSphere Voice Response, and shutting down User response: This error can be caused by
and restarting AIX, call IBM Support. other error conditions in the system. Review the
Severity: White
Destination: Log persists after shutting down and restarting
12250 Target appl_id not channel
process Severity: Yellow
Explanation: Appl_id is out of range in call to Destination: Log

post_chp_event. This error is logged when a
process tries to post an event to any channel
12253 Invalid event type
process, but application ID specified by process
posting the event is incorrect. Explanation: An event was generated by the
device driver for channel process that is
unauthorized by channel process.
Severity: Yellow
Severity: Yellow
Destination: Log
12251 PCB pointer in PPT invalid
Explanation: Invalid pointer in Process Profile
12254 Caller not allowed to generate this
Table (PPT) deleted when Post_chp_event()
event
invoked.
Explanation: An event that is generally handled
by NODEM/OAM was sent to CHP.
Severity: White
Destination: Log
Severity: White

12255 • 12401

12305 Core file created
Explanation: A WebSphere Voice Response
12255 Semaphore notify call failed
process has generated a core file. A core file is
Explanation: Semaphore operation failed while generated when a WebSphere Voice Response
passing buffers to the channel process. Buffers process encounters an unrecoverable error.
are returned to sender.
User response: Use a debugging tool, such as
User response: This error can be caused by dbx, to determine the nature of the error. Check
other error conditions in the system. Review the the WebSphere Voice Response error log for
WebSphere Voice Response error logs and try to additional information. You might need to
correct other problems first. If the problem shutdown and restart WebSphere Voice Response
persists after shutting down and restarting if the the system stops working. If the problem
WebSphere Voice Response, and shutting down persists, call IBM Support
Severity: Yellow
Severity: White
Destination: Log
12401 Truncated voice file detected
12256 Semaphore operation failed
Explanation: A WebSphere Voice Response
Explanation: General semaphore failure. process was not able to read a significant number
of bytes expected from a voice file. The number
User response: This error can be caused by of voice bytes in the file is significantly less than
other error conditions in the system. Review the the expected total voice length indicated in the
WebSphere Voice Response error logs and try to header of the voice file. This error is raised when
correct other problems first. If the problem more than a threshold number of milliseconds
persists after shutting down and restarting (indicated below) of voice is lost.
and restarting AIX, call IBM Support. User response: If the file was truncated, as it
may have been if copied over a network, try to
Severity: White recover the original file and start over. If the
Destination: Log original file cannot be recovered or was
originally too short, you will need to record
another voice file. If the problem persists, call
12304 Buffer already has registered IBM Support.
owner
Severity: Yellow
Explanation: Failure in pool_get() when it tried
to get an already owned buffer. Destination: Log, System Monitor

Severity: White
Destination: Log

13001 • 13006
LUM (License Use Management)

13001 License Request Server
initialization failure
13004 LRS failed to get storage from
Explanation: On starting the internal License
buffer pool.
Request Server the Task_init call failed. License
requesting will not function properly. Explanation: The license request server attempt
to acquire a 4K buffer failed. License requesting
User response: Review the hardware and
will not function properly.
software install operation as described in the
Installation book to ensure that both hardware User response: Review the hardware and
and software are installed correctly. If the software install operation as described in the
problem persists, call IBM Support. Installation book to ensure that both hardware
and software are installed correctly. If the
Severity: Yellow
problem persists, call IBM Support.
Severity: Yellow
13002 LRS attempt to attach queue
failure
13005 LRS attempt to initialise the
Explanation: The license request server could
License Use Manager failed.
not attach to shared memory queue. License
requesting will not function properly. Explanation: The license request server failed
initialising connection to the License Use
Manager. License requesting will not function
properly.
Installation book to ensure that both hardware
and software are installed correctly. If the User response: Review the hardware and
problem persists, call IBM Support. software install operation as described in the
Severity: Yellow
and software are installed correctly. Check that
Destination: Log, System Monitor License Use Management is correctly installed
and started. If the problem persists, call IBM
Support.
13003 LRS attempt to clean up requested
licenses failure. Severity: Yellow
Explanation: The license request server failed Destination: Log, System Monitor
attempting a clean up the list of requested
licenses during recovery. License requesting may
13006 LRS attempt to receive a message
not function properly, and counts of requested
from its queue failed
licenses may be too high.
Explanation: The license request server failed
trying to extracta message from an internal
queue. License requesting will not function
properly.
and software are installed correctly. Check that
License Use Management is correctly installed User response: This is an internal error. If the
and started. If the problem persists, call IBM problem persists, call IBM Support.
Support.
Severity: Yellow
Severity: Yellow

13007 • 13013
Destination: Log, System Monitor User response: Check the reason for the failure
using License Use Management documentation.
Check that License Use Management is correctly
13007 LRS received bad message format
installed and running. If the problem persists,
on its message queue
call IBM Support.
Explanation: The license request server did not
Severity: Yellow
recognise type of message on its internal
message queue. Destination: Log, System Monitor
User response: This is an internal WebSphere
Voice Response error. If the problem persists, call 13011 Request to keep a requested
IBM Support. license has failed.
Severity: Yellow Explanation: A request to hold on to a license
from the License Use Manager has failed. License
requesting will not function properly.
User response: Check the reason for the failure
13008 License request has failed because
of hard-stop
Explanation: The requested license has not been installed and running. If the problem persists,
supplied because hard-stop was specified during call IBM Support.
license registration.WebSphere Voice Response
Severity: Yellow
will continue to operate normally.
User response: Review the license creation with
the system administrator and either request more
licenses or specify soft-stop. 13012 The process that requested a
license has failed
Severity: Red
Explanation: The license request server is
holding on to a license for a WebSphere Voice
Response process that has terminated. The
13009 Request for license has failed. license will be automatically released.
Explanation: A request for license from the User response: No action is needed but if the
License Use Manager has failed. License problem persists, call IBM Support.
requesting may not function properly.
Severity: White
User response: Check the reason for the failure
installed and running. If the problem persists, 13013 Invalid license type
call IBM Support.
Explanation: The license request server has
Severity: Yellow been sent a message to request or release a
license it does not recognise.
User response: This is an internal error. Call
IBM Support.
13010 Release of license has failed.
Severity: White
Explanation: A request to release license from
the License Use Manager has failed. License Destination: Log, System Monitor
requesting may not function properly.

13014 • 13021
13014 License request has failed because 13017 License request has failed because
the license is unauthorized the license is not installed and
distributed.
Explanation: The requested license has not been
supplied because it's use was specified as Explanation: The requested license has not been
unauthorized during license supplied because it has not been installed or has
registration.WebSphere Voice Response will been installed and not distributed.WebSphere
continue to operate normally. Voice Response will continue to operate
normally.
User response: Check why the license has been
requested when not authorized. Review the User response: Install and distribute the license
license creation with the system administrator. using the Basic License Tool of License Use
Management.
Severity: Red
Severity: Yellow
13015 License Use Management
communication error. 13020 LRS client attempt to attach queue
failure
Explanation: Attempt to communicate with the
License Use Management server has failed. This Explanation: The license request client could
may be because of a server or network not attach to shared memory queue. License
failure.WebSphere Voice Response will continue requesting will not function properly.
to operate normally.
User response: Check that License Use software install operation as described in the
Management has been started and/or the Installation book to ensure that both hardware
network connections between this node and the and software are installed correctly. If the
license server are operating normally. problem persists, call IBM Support.
13016 License Use Management server is 13021 LRS client failed sending a
not communicating. message to its queue
Explanation: Attempt to communicate with the Explanation: The license request server failed
License Use Management server has failed. This trying to send a message to an internal queue.
may be because of a server or network failure or License requesting will not function properly.
because the server has been stopped.WebSphere
User response: This is an internal error. If the
Voice Response will continue to operate
normally.
Severity: Yellow
User response: Check that License Use
Management has been started and/or the Destination: Log, System Monitor
network connections between this node and the
license server are operating normally. Restart the
LUM server if necessary.
Severity: Yellow

14003 • 14015
SMSI (Simplified Message Service Interface)

Explanation: Cannot open SMSI port. This error
14003 SMSI error writing to tty port
may also occur if you have the SMSI process
Explanation: Could not write to SMSI port. setup in "run in tasklist.data", but do not have it
configured.
User response: Ensure that system parameter
and smit tty configuration match actual line User response: Check smit tty configuration,
characteristics, such as baud and parity. and check that the tty port is in an available
state. If you do not require SMSI support, delete
Severity: Yellow
the following line from tasklist.data: A 20 SMSI
Severity: Red
14004 SMSI error reading tty port
Explanation: Encountered error while reading
14008 SMSI error writing termio
SMSI port.
configuration
User response: Ensure that system parameter
Explanation: Cannot update SMSI tty termio
tty and smit tty configuration match line
data.
characteristics.
User response: Set baud, parity or stop bits
Severity: Yellow
using smit and call IBM Support.
Severity: Yellow
14005 SMSI: invalid message received
Explanation: Unexpected message received on
14011 SMSI error: data line down
SMSI queue.
Explanation: SMSI tty connection down.
User response: Check that both the `switch
type' and `signalling process type' parameters are User response: Check tty cable connection to
set up for your switch. Call IBM Support. the pSeries modem and switch. Have switch
operator check connections.
Severity: Yellow
Severity: White
14006 SMSI error retrieving sysparm
data 14012 SMSI: data line up
Explanation: Cannot access SMSI system Explanation: SMSI tty connection now working.
parameter data.
User response: Check that the parameters are
Severity: Green
set up. Call IBM Support.
Severity: Red
14015 SMSI: invalid line ID received
Explanation: SMSI line ID not valid.
14007 SMSI error opening tty device
User response: Verify line IDs in channel

14016 • 14028
system parameters with those sent by switch. User response: Check the serial line and
The Message Line Identifier field in the channel adapter. If the problem persists, call IBM
parameters needs to include both the line group Support.
(3 digits) and the line number (4 digits), when
Severity: Yellow
configured for SMSI.
Severity: Yellow
14025 SMSI: error sending hang-up
request to siglib
14016 SMSI: invalid calling number
Explanation: Signalling library reported an error
received
when SMSI tried to issue a hang-up command
Explanation: Non-alphanumeric data received for the associated channel. This error affects only
from calling number. Ericsson far-end-hup detection.
User response: Verify tty line quality, system User response: If the error persists, call IBM
parameters and smit tty SMSI configuration. Support.
14017 SMSI: invalid called number 14026 SMSI: could not connect to siglib
received
Explanation: SMSI could not connect to the
Explanation: Non-alphanumeric data received signalling library. It therefore cannot perform any
for called number. functions. The error code is logged.
User response: Verify tty line quality, system User response: Call IBM Support.
parameters and smit tty SMSI configuration.
Severity: Red
Severity: Yellow
14027 SMSI: MWI database error
14023 SMSI: signalling library call
Explanation: The SMSI call history database is
failed
having problems. The attempted function and
Explanation: A signalling library call failed. The error is logged. This affects only Ericsson MWI
attempted function and error code are logged. block update features. Other SMSI functions
should not be affected.
Severity: Red
Destination: Log, System Monitor, Alertable Support.
Severity: Red
14024 SMSI: MWI NAK retry failure
Explanation: The switch sent an MWI NAK
request with an extension number that SMSI
14028 SMSI warning: switch type set to
does not recognize. Possible problems are: -
none
Severe system performance problems. - Serial
line errors. Explanation: For SMSI to start, the EDL switch

14029 • 14031
type must be set correctly. padding is enabled, the stripping character, the
actual called number received before any of the
User response: Set the EDL Switch Type
padding characters are stripped, and the
parameter in the Message Information
complete EDL message.
parameters group to AT&T (using the System
Configuration option on the Configuration User response: Check that the numbers sent by
menu). You also need to set the Signalling the switch are consistent with the configuration
Process Type parameter for the Channel Group parameters for Called Number. If the
to SMSI/SMDI/VMS. configuration appears to be correct, call IBM
Support and give them: - Details of your
Severity: Green
configuration for the Exchange Data Link. - A
Destination: Log, System Monitor, Alertable copy of the error log showing one or more
examples of this error condition. - A system trace
covering a complete call that generated this error.
14029 SMSI: invalid calling number - If you are using the padding facility for
length numbers, give brief details of the numbering
Explanation: The length of a received calling system you are using for your telephony setup
number is invalid. It does not equal the Calling (minimum length number, maximum length
Number Length parameter. The error parameters number, and the padding character if numbers
indicate the expected number length, whether are padded to a constant length).
padding is enabled, the stripping character, the Severity: Yellow
actual calling number received before any of the
padding characters are stripped, and the Destination: Log, System Monitor
complete EDL message.
User response: Check that the numbers sent by 14031 SMSI: invalid MWI number
the switch are consistent with the configuration length
parameters for Calling Number. If the
Explanation: The length of the MWI number
configuration appears to be correct, call IBM
received from the signalling library did not equal
the MWI Number Length parameter. It is invalid.
The error parameters indicate the expected
copy of the error log showing one or more
number length, whether padding is enabled, the
padding character, and the actual MWI number
covering a complete call that generated this error.
received before any of the padding characters are
- If you are using the padding facility for
added.
numbers, give brief details of the numbering
system you are using for your telephony setup User response: Check that the numbers sent by
(minimum length number, maximum length the switch are consistent with the configuration
number, and the padding character if numbers configuration parameters for Calling Number. If
are padded to a constant length). the configuration appears to be correct, call IBM
Severity: Yellow
Destination: Log, System Monitor copy of the error log showing one or more
covering a complete MWI request that generated
14030 SMSI: invalid called number this error. You can generate MWI requests either
length from a State Table application that stores a voice
Explanation: The length of a received called message, or from a custom server that sends a
number is invalid. It does not equal the Called request to the Signalling Library. - If you are
Number Length parameter. The error parameters using the padding facility for numbers, give brief
indicate the expected number length, whether details of the numbering system you are using

14032
for your telephony setup (minimum length

number, maximum length number, and the
padding character if numbers are padded to a
constant length).
Severity: Yellow
14032 SMSI: invalid number

configuration
Explanation: There is an error in the
configuration of the number lengths. This error
occurs if one or more of the number stripping
parameters is set to Yes. The Calling Number
Length parameter must be greater than or equal
to the Calling Number Length (minimum)
parameter, and the Called Number Length
parameter must be greater than or equal to the
Called Number Length (minimum) parameter.
The error parameters indicate which number
type is causing the error. This is either Calling
Number or Called Number, or both.
User response: Check that the configuration for
the Calling Number and Called Number is
correct. If the configuration appears to be correct,
call IBM Support and give them: - Details of
your configuration for the Exchange Data Link. -
A copy of the error log showing one or more
examples of this error condition. - If you are
using the padding facility for numbers, give brief
details of the numbering system you are using
for your telephony setup (minimum length
number, maximum length number, and the
padding character if numbers are padded to a
constant length).
Severity: Yellow

15001 • 15008
CACHE (Cache Manager)

management; the cache manager terminates
abnormally.
Explanation: There is no system memory to
User response: If possible, increase the number
allocate; the cache manager will not initialize.
of buffers in the buffer pool. If not, call IBM
User response: This should not occur. Call IBM Support.
Support.
Severity: White
Severity: White
Explanation: The system cannot access a buffer
Explanation: There is no system memory to from the buffer pool for internal table
allocate; the cache manager will not initialize. management; the cache manager terminates
abnormally.
User response: This should not occur. Call IBM
Support. User response: If possible, increase the number
of buffers in the buffer pool. If not, call IBM
Severity: White
Support.
Severity: White
Explanation: The system cannot expand the
15007 Prompt segment descriptor not
internal table to handle all the requests; the cache
found
manager terminates abnormally.
User response: This should not occur. Call IBM
internal pointer, possibly because memory is
Support.
corrupted.
Severity: White
User response: Monitor system behavior. If it is
Destination: Log, System Monitor not running correctly, shut down the system and
restart it. Call IBM Support.
15004 Additional malloc failed Severity: White
Explanation: The system cannot expand the Destination: Log, System Monitor
internal table to handle all the requests; the cache
manager terminates abnormally.
15008 No 4KB block reference in DPRB
Explanation: The cache manager received a
Severity: White message with missing information. Requests for
voice segments can time out.
User response: Verify that the message is not
mistakenly being sent by a custom server to the
15005 Could not get 4KB buffer cache manager. Call IBM Support.
Explanation: The system cannot access a buffer Severity: White
from the buffer pool for internal table

15010 • 15013
15010 Voice descriptor not found

internal pointer, possibly because of memory
corruption. The system may run without
problems, or a buffer pool may be slowly
depleted.
User response: If the system is not running
correctly, shut it down and restart it. Call IBM
Support.
Severity: White
15013 Cachem released segment before

minimum time
Explanation: An error occurred in the cache's
hash table. The hash table is disabled.
User response: Check that the system still plays
prompts successfully. Check the error description
for any other suggested actions. To re-enable the
hash table, recycle WebSphere Voice Response. If
Severity: Yellow

16004 • 16005
DBIM (Internal Database Manager)
16004 System parameter DBIM Time

Out undefined
Explanation: The internal database manager
could not read the system parameter DBIM Time
Out during initialization. It has assigned a
default value of 20 seconds. This may indicate a
problem with the system parameter database.
User response: If the application name is DBIM,
increase the value of the DBIM Time Out system
parameter by clicking Configuration...System
Configuration... from the Welcome window. If
this cannot be displayed, or you get errors, call
IBM Support. If this error message is displayed
when you restart WebSphere Voice Response, call
IBM Support.
Severity: Yellow
16005 Server responded after timeout

interval
Explanation: A server request completed after
the timeout interval specified by the application
had elapsed. This can occur with a 3270 server or
custom server which for some reason is not
returning data within the time specified by the
Timeout parameter of a ReceiveData state table
action. The amount of time elapsed since the
actual timeout is shown below.
User response: If this occurs frequently, check
the 3270 host network connections to ensure that
they are available and that the response time is
reasonable. If you are using custom servers,
ensure that they are running and operating
correctly. You may need to increase the timeout
values to match the typical response time of the
host system or custom server. If a state table
action receives a timeout edge, it is the
responsibility of the application to handle it in a
sensible manner.
Severity: White

17001 • 17004
VPACK, SPACK and XPACK

17001 I/O memory exception
Explanation: The device driver tried to process
17003 Channel error on pack
an interrupt from a pack and encountered an
addressing exception within the interrupt Explanation: The microcode on the pack
handler. This could indicate faulty memory on indicates that one or more of its channels has
the pSeries computer or pack, but usually encountered an error. WebSphere Voice Response
indicates a defective or corrupt device driver. logs the error, which may indicate a faulty pack
WebSphere Voice Response disables the pack or a problem with the microcode.
where the interrupt error was found. This pack
raises an alarm relay and will not be reenabled User response: Dial the channel or pack and
automatically by WebSphere Voice Response reenable it; this may clear the error. Check the
even after a delay. telecommunications cables and connections to
the network. Check that all cable connectors are
User response: Try swapping adapters around firmly seated. Run the diagnostics described in
in your system unit to see if the problem is the Problem Determination book. If the problem
related to the slot where the adapter is located or persists, call IBM Support.
to the adapter itself. Run diagnostics on the pack,
adapter, and pSeries system memory. If the Severity: Red
problem still persists, call IBM Support with Destination: Log, System Monitor, Alertable
details and results of all the tests you have tried.
Severity: Red 17004 E1 or ethernet signal loss
Destination: Log, System Monitor, Alertable qualified alarm
Explanation: A signal loss (SL) occurs when
17002 Telephony hardware not WebSphere Voice Response is not receiving an E1
interrupting digital signal. WebSphere Voice Response sends
the Remote Alarm Indication (RAI) signal to the
Explanation: The device driver monitors every far end. If the terminating equipment (PABX,
pack to ensure that they interrupt the pSeries channel bank, and so on) shows RAI, the
system unit at regular intervals. The device transmission path from WebSphere Voice
driver has detected a pack that has not Response to the terminating equipment, the
interrupted the system unit for longer than is transmit side of WebSphere Voice Response, and
allowed. This could indicate a problem with the the receive side of the terminating equipment are
digital trunk adapter. WebSphere Voice Response probably functioning correctly.
disables the suspect pack and raises the alarm
relay on other packs to notify the administrator User response: For a Digital Trunk Adapter:
of the problem. After a short delay WebSphere Check the telecommunication cables and
Voice Response tries to reenable the pack. connections to the network. Check that all cable
connectors are firmly seated. Run the diagnostics
User response: Try swapping adapters around described in the Problem Determination book. If
in your system unit to see if the problem is the cable and WebSphere Voice Response are OK,
related to the slot where the adapter is located or the problem is with the terminating equipment
the adapter itself. Run diagnostics on the adapter or the transmission path beyond the WebSphere
and pSeries system memory. If the problem Voice Response telecommunication line cable.
persists, call IBM Support with details and Call IBM Support with the details and results of
results of all the tests you have tried. all the tests you have tried. If this error occurs
when WebSphere Voice Response is first
Severity: Red
connected to the terminating equipment, check

17005 • 17007
that the transmit port on WebSphere Voice Destination: Log, System Monitor, Alertable
Response is connected to the receive port on the
terminating equipment, and that the transmit
17006 E1 frame alignment loss qualified
port on the terminating equipment is connected
alarm
to the receive port on WebSphere Voice
Response. For DTEA: Check that the ethernet Explanation: WebSphere Voice Response has
cables are properly connected to the DTEA received the frame alignment signal (FAS) in
adapter and to your other ethernet equipment error three times consecutively, and has sent the
(eg hub or switch). Check that your other Remote Alarm Indication (RAI) signal to the far
ethernet equipment are functioning correctly. If end. This condition can be caused by loss of E1
the cable and WebSphere Voice Response are digital signal, receiving 2MB AIS, or some other
functioning correctly then the problem is with fault condition such as defective transmission
the network itself. Call IBM Support with the path or hardware failure. Error 17004 (E1 signal
details and results of all the tests you have tried. loss qualified alarm) is reported instead of 17006
if frame alignment loss (FAL) is caused by signal
Severity: Red
loss; error 17005 (E1 2MB alarms indicator signal
Destination: Log, System Monitor, Alertable qualified alarm) is reported if FAL is caused by
receiving a 2MB AIS. If the terminating
equipment (PABX, channel bank, and so on)
17005 E1 2MB alarm indicator signal
shows RAI, the transmission path from
qualified alarm
WebSphere Voice Response to the terminating
Explanation: The 2MB Alarm Indication Signal equipment, the transmit side of WebSphere Voice
(AIS) is a continuous stream of binary 1s Response, and the receive side of the terminating
transmitted in all timeslots of the E1 digital equipment are probably functioning correctly.
signal. When this error occurs, WebSphere Voice
User response: Check the telecommunication
Response sends the Remote Alarm Indication
cables and connections to the network. Check
(RAI) signal to the far end. If the terminating
that all cable connectors are firmly seated. Run
equipment (PABX, channel bank, and so on)
the diagnostics described in the Problem
shows RAI, the transmission path from
Determination book. If the cable and WebSphere
WebSphere Voice Response to the terminating
Voice Response are OK, the problem is with the
equipment, the transmit side of WebSphere Voice
terminating equipment or the transmission path
Response, and the receive side of the terminating
beyond the WebSphere Voice Response
equipment are probably functioning correctly.
telecommunication line cable. Run appropriate
(See explanation for 17007).
diagnostics on the terminating equipment. If the
User response: Check the telecommunication problem persists, call IBM Support with the
cables and connections to the network. Check details and results of all the tests you have tried.
Severity: Red
Determination book. If the cable and WebSphere Destination: Log, System Monitor, Alertable
Voice Response are OK, the problem is with the
terminating equipment or the transmission path
17007 E1 remote alarm indicator
qualified alarm
telecommunication line cable. Run appropriate
diagnostics on the terminating equipment to see Explanation: WebSphere Voice Response has
why it is generating a 2MB AIS. If the problem received the remote alarm indication signal (RAI)
persists, call IBM Support with the details and from the terminating equipment. The RAI is sent
results of all the tests you have tried. by the far end when it is not receiving the E1
digital signal, cannot maintain frame alignment,
Severity: Red
or is receiving the frame alignment signal (FAS)

17008 • 17010
with an error rate greater than 1 in 10,000. If problem persists, call IBM Support with the
WebSphere Voice Response shows RAI, the details and results of all the tests you have tried.
transmission path from the terminating
Severity: Red
equipment to WebSphere Voice Response, the
transmit side of the terminating equipment, and Destination: Log, System Monitor, Alertable
the receive side of WebSphere Voice Response are
probably functioning correctly. If WebSphere
Voice Response has a flashing RAI LED, the 17009 E1 64KB alarm indicator signal
remote end has lost multiframe synchronization. qualified alarm
User response: Check the telecommunications Explanation: The 64KB Alarm Indication Signal
cables and connections to the network. Check (64KB AIS) is a continuous stream of binary 1s
that all cable connectors are firmly seated. Run transmitted only in timeslot 16 in all frames,
the diagnostics described in the Problem including frame 0 (the frame with the multiframe
Determination book. If the cable and WebSphere alignment signal or MAS). 64KB AIS results in
Voice Response are OK, the problem is with the the loss of multiframe alignment. When it
terminating equipment or the transmission path receives 64KB AIS, WebSphere Voice Response
beyond the WebSphere Voice Response sends a loss of multiframe alignment alarm
telecommunication line cable. Run appropriate (RMFAI) to the far end. If the terminating
diagnostics on the terminating equipment to see equipment (PABX, channel bank, and so on)
why it is generating the RAI. If the problem shows RMFAI, the transmission path from
persists, call IBM Support with the details and WebSphere Voice Response to the terminating
results of all the tests you have tried. equipment, the transmit side of WebSphere Voice
Severity: Red equipment are probably functioning correctly.
Destination: Log, System Monitor, Alertable User response: Check the telecommunication
17008 E1 excessive error qualified alarm
Explanation: WebSphere Voice Response has Determination book. If the cable and WebSphere
detected an error rate in the frame alignment Voice Response are OK, the problem is with the
signal (FAS) of more than 1 in 10,000, and has terminating equipment or the transmission path
sent a remote alarm indication signal (RAI) to the beyond the WebSphere Voice Response
terminating equipment. If the terminating telecommunication line cable. Run appropriate
equipment (PABX, channel bank, and so on) diagnostics on the terminating equipment to see
shows RAI, the transmission path from why it is generating a 64KB AIS. If the problem
WebSphere Voice Response to the terminating persists, call IBM Support with the details and
equipment, the transmit side of WebSphere Voice results of all the tests you have tried.
Severity: Yellow
equipment are probably functioning correctly.
that all cable connectors are firmly seated. Run 17010 E1 multiframe alignment loss
the diagnostics described in the Problem qualified alarm
Voice Response are OK, the problem is with the Explanation: WebSphere Voice Response has
terminating equipment or the transmission path received the multiframe alignment signal (MAS)
beyond the WebSphere Voice Response in error twice in a row. When multiframe
telecommunication line cable. Run appropriate alignment is lost, WebSphere Voice Response
diagnostics on the terminating equipment. If the sends a loss of multiframe alignment alarm

17011 • 17012
(RMFAI) to the far end. Receiving 64KB AIS telecommunication cables and connections to the
causes loss of multiframe alignment. However, if network. Check that all cable connectors are
WebSphere Voice Response is receiving 64KB firmly seated. Run the diagnostics described in
AIS, it reports error 17009, E1 64KB alarm the Problem Determination Guide. If the cable
indicator signal qualified alarm, rather than this and WebSphere Voice Response are OK, the
error. If the terminating equipment (PABX, problem is with the terminating equipment or
channel bank, and so on) shows RMFAI, the the transmission path beyond the WebSphere
transmission path from WebSphere Voice Voice Response telecommunication line cable.
Response to the terminating equipment, the Run appropriate diagnostics on the terminating
transmit side of WebSphere Voice Response, and equipment to see why it is generating the RMFA.
the receive side of the terminating equipment are If the problem persists, call IBM Support with
probably functioning correctly. the details and results of all the tests you have
tried.
cables and connections to the network. Check Severity: Yellow
Voice Response are OK, the problem is with the 17012 T1 or ethernet loss-of-signal
terminating equipment or the transmission path qualified alarm
telecommunication line cable. Run appropriate Explanation: When the pack does not receive a
diagnostics on the terminating equipment. If the T1 digital signal for more than approximately
problem persists, call IBM Support with the 150ms, a loss of signal (LOS) occurs. This error
details and results of all the tests you have tried. occurs only when the pack is already enabled. If
the terminating equipment (CSU, PABX, channel
Severity: Yellow bank, and so on) shows a remote alarm (yellow
alarm), the transmission path from WebSphere
Voice Response to the terminating equipment,
the transmit side of WebSphere Voice Response,
17011 E1 multiframe yellow qualified and the receive side of the terminating
alarm equipment are functioning correctly. See 17014
for an explanation.
Explanation: WebSphere Voice Response has
received the remote multiframe alignment loss User response: For a DTTA: Check the
alarm indication signal (RMFA) from the telecommunication cables and connections to the
terminating equipment. The RMFA is sent by the network. Check that all cable connectors are
far end when it cannot maintain multiframe firmly seated. Run the diagnostics described in
alignment. Receiving 64KB AIS causes loss of the Problem Determination book. If the cable and
multiframe alignment and there are conditions WebSphere Voice Response are OK, the problem
during which WebSphere Voice Response is with the terminating equipment or the
transmits 64KB AIS. If WebSphere Voice transmission path beyond the WebSphere Voice
Response shows RMFA, the transmission path Response telecommunication line cable. Call IBM
from WebSphere Voice Response to the Support with the details and results of all the
terminating equipment, the transmit side of tests you have tried. If this error occurs when
WebSphere Voice Response, and the receive side WebSphere Voice Response is first connected to
of the terminating equipment are probably the terminating equipment, check that the
functioning correctly. transmit port on WebSphere Voice Response is
connected to the receive port on the terminating
User response: If WebSphere Voice Response is
equipment, and that the transmit port on the
not sending 64KB AIX, check the
terminating equipment is connected to the
telecommunication line cable. Check the

17013 • 17015
receive port on WebSphere Voice Response. For a equipment. Normally the RAI clears in 10 to 20
DTEA: Check that the ethernet cables are seconds and message 17017 is logged. If the
properly connected to the DTEA adapter and to alarm does not clear after 20 seconds, follow the
your other ethernet equipment (eg hub or steps in User Response.
switch). Check that your other ethernet
User response: Check that the WebSphere Voice
equipment is functioning correctly. If the cable
Response T1 Remote Alarm Format (RAI using
and WebSphere Voice Response are functioning
bit 2 or FS bit) matches the remote alarm format
correctly then the problem is with the network
of the terminating equipment. Determine the
itself. Call IBM Support with the details and
WebSphere Voice Response T1 Remote Alarm
results of all the tests you have tried.
Format by clicking Configuration... System
Severity: Red Configuration... Trunk Interface and selecting the
trunk concerned. The most common format is
RAI using bit 2. If the configurations match, test
the telecommunication line cable. Check the
17013 T1 alarm indicator signal telecommunications cables and connections to
qualified alarm the network. Check that all cable connectors are
firmly seated. Run the diagnostics described in
Explanation: The Alarm Indication Signal (AIS), the Problem Determination book. If the cable and
also known as the blue alarm, is a continuous WebSphere Voice Response are OK, the problem
stream of binary 1s transmitted in all timeslots of is with the terminating equipment or the
the T1 digital signal. The AIS is an unframed transmission path beyond the WebSphere Voice
signal and results in an out-of-frame (OOF) Response telecommunication line cable. Call IBM
condition. If WebSphere Voice Response receives Support with the details and results of all tests
the AIS for more than two seconds, a Remote you have tried.
Alarm Indication (RAI), also known as a yellow
alarm, is transmitted to the terminating Severity: Red
equipment (CSU, PABX, channel bank and so
on). AIS is normally sent to keep a T1 digital line
open while making the line unusable for traffic.
17015 T1 out-of-frame qualified alarm
User response: Run the appropriate diagnostics
on the terminating equipment to see why AIS is Explanation: The pack cannot synchronize the
being generated. incoming T1 digital signal. An out of frame
condition (OOF) is caused by loss of signal
Severity: Red
(LOS), an Alarm Indication Signal (AIS), or some
Destination: Log, System Monitor, Alertable other fault condition such as a defective
transmission path, hardware failure, or
incompatible T1 framing mode. The OOF
17014 T1 remote alarm indicator condition is declared when received T1 framing
qualified alarm bits are in error in the range 2 out of 4 to 2 out
Explanation: WebSphere Voice Response has of 5. Error 17012 is reported if the OOF is caused
received a Remote Alarm Indication (RAI) from by loss of signal; error 17013 is reported if the
the terminating equipment (CSU, PABX, channel OOF is caused by receiving AIS.
bank, and so on) for 335ms to 1000ms. The RAI User response: Check that WebSphere Voice
is sent to indicate that the terminating equipment Response T1 framing mode (D4 or ESF) matches
is in an out-of-frame (OOF) condition for more the framing mode of the terminating equipment
than two seconds. RAI is transmitted by setting (CSU, PABX, channel bank and so on).
bit two to 0 in every channel, or by the FS bit in Determine the WebSphere Voice Response T1
frame 12 of the T1 digital signal. RAI occurs framing mode by clicking Configuration...
when enabling a pack connected to terminating System Configuration... Trunk Interface and

17016 • 17034
selecting the trunk concerned. D4 framing is diagnostics described in the Problem

normally used with CAS. Extended superframe Determination book. If the cable and WebSphere
(ESF) is normally used with CCS, for example, Voice Response are OK, the problem is with the
ISDN. If the configurations match, test the terminating equipment or the transmission path
telecommunication line cable. Check the beyond the line cable. Call IBM Support with the
telecommunication cables and connections to the details and results of all tests you have tried.
network. Check that all cable connectors are
Severity: Yellow
firmly seated. Run the diagnostics described in
the Problem Determination book. If the cable and Destination: Log, System Monitor
WebSphere Voice Response are OK, the problem
is with the terminating equipment or the
transmission path beyond the WebSphere Voice 17017 Network alarm has cleared
Response telecommunication line cable. Call IBM Explanation: An earlier alarm on the digital
Support with the details and results of all tests trunk has gone away.
you have tried.
Severity: Red
Severity: Green
17016 T1 bi-polar violation qualified

alarm 17033 Signalling software error
Explanation: A bi-polar violation (BPV) Explanation: The signalling software has

condition has occurred. The BPV may be caused attempted to enter an unexpected or illegal state.
by a defective telecommunication line cable, This could be caused by incorrect configuration
defective hardware, or incompatible line coding of the telephony protocol or telephony
between WebSphere Voice Response and the parameters, or an error in the signalling
terminating equipment (CSU, PABX, channel software.
bank, and so on). User response: If this error occurs frequently,
User response: Check that the WebSphere Voice check that the correct protocol has been selected
Response T1 line code (AMI ZCS or B8ZS) on WebSphere Voice Response and the switch,
matches the T1 line code of the terminating and that the timing parameters for WebSphere
equipment. Determine the WebSphere Voice Voice Response and the switch are compatible. If
Response T1 Remote Alarm Format by clicking the problem persists, call IBM Support. To help
Configuration... System Configuration... Trunk solve the problem, have the following available
Interface and selecting the trunk concerned. when you call: - Details of the switch and
AMI/ZCS is more common than B8ZS which is WebSphere Voice Response telephone setup -
normally used for clear channel operation and Details of the version of WebSphere Voice
ISDN. ZCS (zero-code suppression) and B8ZS Response you are using, along with details of
(bi-polar eight zero substitution) are two ways of any PTFs that have been applied - A system-level
ensuring an adequate density of "ones" in the T1 trace of the problem
digital signal. B8ZS deliberately introduces Severity: Red
bi-polar violations at the transmitting end and a
high BPV error rate occurs unless the receiving Destination: Log, System Monitor, Alertable
end is configured to decode them. If the
configurations match, test the telecommunication 17034 Illegal application command
line cable. Check the telecommunication cables
and connections to the network. Check that all Explanation: The state table application tried to
cable connectors are firmly seated. Run the perform an action that is invalid for the present
state of the call. For example, trying to transfer a

17035 • 17038
call that has already been hung up by the clears: 17042, 7043, 17045
application.
Severity: Yellow
User response: Check the application for
nonsensical execution of telephony-related
commands. If you are unable to locate the source
of the problem call IBM Support. To help solve 17037 Glare on line
you call: - Details of the switch and WebSphere Explanation: The switch and WebSphere Voice
Voice Response telephone setup - Details of the Response have both tried to seize a line at the
version of WebSphere Voice Response you are same time. The frequency with which these
using, along with details of any PTFs that have errors are likely to occur depends on the protocol
been applied - If possible, a simple test case that being used, and on the way in which the switch
reproduces the problem determines which line to call in on next. If a
glare condition occurs, WebSphere Voice
Severity: Green Response allows the incoming call to be
processed. The outgoing call fails with the
channel active and the application can try again.
If the error occurs more than once in every 100
17035 Network does not respond calls it may be due to incorrect configuration of
the telephony protocol or telephony parameters,
Explanation: The switch did not respond within
or an error in the signalling software.
the expected time. This could be caused by
incorrect configuration of the telephony protocol User response: If this error occurs frequently,
or telephony parameters, or an error in the check that the correct protocol has been selected
signalling software. on WebSphere Voice Response and the switch,
and that the timing parameters for WebSphere
User response: If this error occurs frequently,
Voice Response and the switch are compatible. If
check that the correct protocol has been selected
the problem persists, call IBM Support. To help
on WebSphere Voice Response and the switch,
solve the problem, have the following available
and that the timing parameters for WebSphere
when you call: - Details of the switch and
Voice Response and the switch are compatible. If
WebSphere Voice Response telephone setup -
Details of the version of WebSphere Voice
Response you are using, along with details of
any PTFs that have been applied - A system-level
trace of the problem
Response you are using, along with details of Severity: Green
any PTFs that have been applied - A system-level
trace of the problem
Severity: Yellow
17038 Signal detected but could not
Destination: Log, System Monitor establish call
Explanation: An incoming call was not
17036 Bit fault cleared answered by the application in time. The time
given to answer an incoming call is defined by
Explanation: A fault on one of the signalling
the No Answer Warning system parameter. This
bits has cleared. To determine which signalling
can be due to the No Answer Warning parameter
bit was causing the error see earlier messages.
being too short, an application error, a very
User response: Check for earlier errors and heavily loaded system, or an error in the
follow the user response for that error. This signalling software.

17040 • 17042
User response: If this error occurs frequently, with details of any PTFs that have been applied -
check that the No Answer Warning system A system-level trace of the problem
parameter is set to a reasonable value, such as 2
Severity: Yellow
to 4 ring periods. Check that the application
answers a call as soon as possible after it is Destination: Log, System Monitor
started up. If there are any actions that can take
a long time before the answer call, such as open
host server link, check that the timeouts are 17041 Ring off pulse exceeded expected
shorter than the No Answer Warning system width
parameter and that the application correctly Explanation: WebSphere Voice Response
handles cases where the actions time out. Check detected a ring off pulse from the switch that
the CPU load on the system. If it is permanently was longer than expected. This could be due to
heavily loaded, reduce the load by disabling incorrect configuration of the telephony protocol,
some channels or trunks to see if this reduces the the `Ringing Off Maximum' system parameter
frequency that this problem occurs. If the being too short, or an error in the signalling
problem persists, call IBM Support. To kelp solve software.
you call: - Details of the switch and WebSphere User response: If this error occurs frequently,
Voice Response telephone setup - Details of the check that the correct protocol has been selected
version of WebSphere Voice Response you are on WebSphere Voice Response and the switch,
using, along with details of any PTFs that have and that the `Ringing Off Maximum' system
been applied - A system-level trace of the parameter for WebSphere Voice Response and
problem - Details of the application being run, the switch are compatible. If the problem
and an estimate of average and peak call persists, call IBM Support. To help solve the
volumes. problem, have the following available when you
call: - Details of the switch and WebSphere Voice
Severity: Yellow Response telephone setup - Details of the version
Destination: Log, System Monitor of WebSphere Voice Response you are using,
along with details of any PTFs that have been
applied. - A system-level trace of the problem
17040 Ring on pulse exceeded expected
width Severity: Yellow
Explanation: WebSphere Voice Response Destination: Log, System Monitor

detected a Ring On pulse from the switch that
was longer than expected. This could be due to 17042 A-bit fault
incorrect configuration of the telephony protocol,
the `Ringing on Maximum' parameter being too Explanation: WebSphere Voice Response
short, or an error in the signalling software. detected unexpected behavior of the signalling
A-bit. This could be due to incorrect
User response: If this error occurs frequently, configuration of the telephony protocol or an
check that the correct protocol has been selected error in the signalling software. If the A-bit fault
on WebSphere Voice Response and the switch, clears, message 17036 will be issued.
and that the `Ringing on Maximum' parameter
for WebSphere Voice Response and the switch User response: If this error occurs frequently
are compatible. If the problem persists, call IBM check, that the correct protocol has been selected
Support. To help solve the problem, have the on WebSphere Voice Response and the switch. If
following available when you call: - Details of the problem persists, call IBM Support. To help
the switch and WebSphere Voice Response solve the problem, have the following available
telephone setup - Details of the version of when you call: - Details of the switch and
WebSphere Voice Response you are using, along WebSphere Voice Response telephone setup -

17043 • 17060
Response you are using, along with details of User response: If this error occurs frequently,
any PTFs that have been applied - A system-level check that the correct protocol has been selected
trace of the problem Cleared by: 17036 on WebSphere Voice Response and the switch. If
Severity: Yellow
Destination: Log, System Monitor when you call: - Details of the switch and
17043 B-bit fault Response you are using, along with details of
Explanation: WebSphere Voice Response any PTFs that have been applied - A system-level
detected unexpected behavior of the signalling trace of the problem Cleared by: 17036
B-bit. This could be due to incorrect Severity: Yellow
configuration of the telephony protocol or an
error in the signalling software. If the B-bit fault Destination: Log, System Monitor
clears, message 17036 will be issued.
User response: If this error occurs frequently, 17046 Outbound call failed on Feature
check that the correct protocol has been selected Group D
on WebSphere Voice Response and the switch. If
Explanation: An outbound call using Feature
Group D could not complete. This can be caused
by an incorrect dialed number format, or because
Feature Group D is not enabled on the switch.
Note: Outbound Feature Group D is supported
only on the E&M and DID protocols.
any PTFs that have been applied - A system-level User response: Check the state table action
trace of the problem Cleared by: 17036 performing the outbound call. The format of the
digits should look something like
Severity: Yellow
C0123DC4567D, where 0123 is the ANI number
Destination: Log, System Monitor and 4567 is the DNIS (destination) number.
Check that Feature Group D support is enabled
on the switch. If the problem persists, call IBM
17044 Signalling error cleared Support. To help solve the problem have the
Explanation: A fault on one of the signalling following available when you call: - Details of
bits has cleared. To determine which signalling the switch and WebSphere Voice Response setup.
bit was causing the error see earlier messages. - Details of the version of WebSphere Voice
User response: Check for earlier errors and any PTFs that have been applied. - A
follow the user response for that error. system-level trace of the problem
Severity: Green Severity: Yellow
17045 C-bit or D-bit fault 17060 Digital trunk adapter missed

Explanation: WebSphere Voice Response handshake
detected unexpected behavior of the signalling Explanation: WebSphere Voice Response has
C-bit or D-bit. This could be due to incorrect failed to service a hardware interrupt from the
configuration of the telephony protocol or an digital trunk adapter. The pack can continue to
error in the signalling software. If the fault clears,
message 17036 will be issued.

17061 • 17070
function. This may be caused by a hardware Severity: Red

problem.
User response: Run diagnostics on the pack or
try using another pack if you have one. If the
17067 Recognition algorithm did not
return result
Severity: Yellow
Explanation: The speech recognition algorithm
Destination: Log, System Monitor could not identify the incoming signal with any
of the words in the expected vocabulary.
17061 Digital trunk adapter: User response: Not coded.
irrecoverable status
Severity: White
Explanation: A serious error has occurred on
this pack. The pack is no longer usable.
WebSphere Voice Response disables then
reenables the pack, and repeats this operation a 17068 Device driver counter corruption
number of times. WebSphere Voice Response detected
leaves the pack disabled if the problem persists.
You need to intervene at this time. Explanation: The WebSphere Voice Response
device driver has detected a corrupted variable
User response: Try swapping packs around relating to the amount of data left buffered, and
between digital trunk adapters to see if the ready to be read by a user state-table record
problem follows a particular pack around. Try action or custom server read call. This is a severe
swapping adapters around in your system unit error, which can result in lost voice data, or
to see if the problem is related to the slot where looping applications.
the adapter is located or the adapter itself. Run
diagnostics on the pack, adapter, and pSeries User response: Report this error to IBM Support
system memory. If the problem persists, call IBM immediately.
Support with details and results of all the tests Severity: Red
you have tried.
Severity: Red
Destination: Log, System Monitor, Alertable 17069 Digital trunk adapter: slave parity
error
17063 Power supply unit failure (dual Explanation: The digital trunk adapter
configuration) microcode has detected a slave parity error; this
Explanation: One of the power supplies has may be caused by a hardware problem. The pack
failed or been turned off. This error is reported can continue to function.
only once. An enclosure alarm relay is raised to User response: Run diagnostics on the pack or
alert the administrator that intervention is try using another pack if you have one. If the
required. problem persists, call IBM Support.
User response: All devices have been left Severity: Yellow
running, but it is recommended that you shut
down WebSphere Voice Response as soon as Destination: Log, System Monitor
possible to avoid overloading the remaining
power supply where multiple packs are in use. 17070 Digital trunk adapter: memory
The power supply unit should then be turned diagnostic error
back on or replaced.

17300 • 17303
Explanation: The digital trunk adapter performance glitch in AIX, caused by a

microcode has detected a memory error during high-priority device holding interrupts longer
self diagnostics; this may be caused by a than it should. - A pack whose clock drifts,
hardware problem. The pack can continue to possibly because the SCBus TDM cable is
function. disconnected. - Loading on the adapter being too
high. - Failure of the TDM clock management
User response: Run diagnostics on the pack or
part of WebSphere Voice Response
try using another pack if you have one. If the
problem persists, call IBM Support. User response: The pack is automatically
recycled. Check the error log for other errors;
Severity: Yellow
eliminate the reasons for those errors if possible.
Destination: Log, System Monitor Check that when running, the adapter
performance figures are not too high. (See the
documentation for the DTmon tool for more
17300 PCI adapter exception detected information on how to do this). Check all white
Explanation: The ARTIC device driver (ricio) cables are connected securely, and that cables do
has detected a problem with accessing the not move. Check that the SCBus cable is securely
telephony adapter. The WebSphere Voice connected to all adapters. Run diagnostics on the
Response device driver cannot communicate adapter Try removing other adapters on the
with software running on the PCI adapter. A system to see if their device drivers are
high priority streams message has been sent to responsible for a performance glitch. If the
the WebSphere Voice Response device driver to problem persists, call IBM Support.
warn of the error. The type of exception could be Severity: Red
RESET, DUMP, or INTR: the adapter has been
reset, a dump has been taken of the adapter, or Destination: Log, System Monitor, Alertable
some software on the adapter failed.
User response: If this is the only PCI adapter 17302 Telephony adapter detected
on the system, the PCI adapter and associated failure
packs are recycled automatically. If there are two
Explanation: A failure on the adapter has been
PCI adapters, the PCI adapter remains in the
detected by the software which runs on the
failed state and you need to restart WebSphere
adapter (RTT). RTT has sent the WebSphere Voice
Voice Response to recover from this error. If the
Response device driver an RTT_ERROR_IND
primitive. This can be caused by an internal
Severity: Red programming error, but it may indicate a
hardware problem. The adapter and associated
Destination: Log, System Monitor, Alertable packs are no longer usable.
User response: If this is the only adapter on the
17301 Pack failure reported by system, the adapter and associated packs are
telephony adapter recycled automatically. If there are two adapters,
Explanation: Software running on the adapter the adapter remains in the failed state until
has reported to the WebSphere Voice Response WebSphere Voice Response is restarted. If the
device driver that a pack has failed, or that the problem persists, call IBM Support.
pack can no longer be accessed. The Severity: Red
RTT_ERROR_IND primitive was sent by the
adapter software to the WebSphere Voice Destination: Log, System Monitor, Alertable
Response device driver. The pack has failed and
the WebSphere Voice Response device driver
17303 Runaway clock on pack
cannot communicate with the adapter pack
device drivers. Causes of this can include: - A Explanation: The adapter software synchronizes

17304 • 17506
packs on the same adapter by slipping frames to device file /dev/acpa0hmrcd.

correct for clock variances. The software cannot
User response: Make sure there is a onboard
keep up with the large variances occurring on
Ultimedia Audio Adapter installed and
the pack. Voice traffic will degrade on this pack.
configured.
User response: Make sure that the packs are
Severity: White
connected to trunks coming from the same
service provider and that they draw their clock Destination: Log, System Monitor
source from the same place. If the problem
17502 Error opening microphone
Severity: Yellow
Explanation: Cannot open microphone device
Destination: Log, System Monitor, Alertable file /dev/acpa0hmrcd.
User response: Make sure there is a onboard
17304 CCS transmit error on telephony Ultimedia Audio Adapter installed and
adapter configured.
Explanation: This error represents a problem in Severity: White
the IBM software. There have been problems
transmitting CCS data; this is a warning that Destination: Log, System Monitor
some CCS traffic has been lost between the
signalling process and the line. Signalling 17503 Error opening speaker to play
protocols can often recover from data loss, so
calls may not have been affected. The pack and Explanation: Cannot open speaker device file
the adapter remain active. /dev/acpa0srcd.
User response: Contact IBM Support. User response: Make sure there is a onboard
Ultimedia Audio Adapter installed and
Severity: Yellow configured.
Destination: Log, System Monitor, Alertable Severity: White
17305 DTTA adapter failure.
Explanation: Software running on the DTTA has 17504 Error writing to speaker
reported to the WebSphere Voice Response
device driver that it has encountered a serious Explanation: Cannot write to speaker device file
problem and cannot continue to function. Causes /dev/acpa0srcd.
of this can include: - Adapter hardware failure. - User response: Make sure there is a onboard
Adapter software failure. Ultimedia Audio Adapter installed and
User response: The adapter is automatically configured.
recycled. Check the error log for other errors; Severity: White
eliminate the reasons for those errors if possible.
If the problem persists, call IBM Support. Destination: Log, System Monitor
Severity: Red
17506 Error reading data from temporary
Destination: Log, System Monitor, Alertable file
Explanation: A temporary file cannot be read.
17501 Error reading from microphone
User response: Check read-permissions for
Explanation: Cannot read from microphone

17508 • 17603
/tmp/dt6umstmp1, /tmp/dt6umstmp2, and may be using the ODM database, or have locked
/tmp/dt6umstmp3. it. Try again later.
Severity: White Severity: White
17508 Error creating local message 17600 TDM clock daemon died
queue
Explanation: The tdmclockd daemon died
Explanation: Cannot create a local message unexpectedly. This could be because of a lack of
queue. AIX system resources (for example, memory), or
incorrectly configured hardware (for example, no
User response: Check write/read permissions
telephony adapter has been configured). See
for /tmp/.msgkey. Make sure that it was
earlier messages for the cause of death.
properly created.
User response: Check that the system has
Severity: White
enough paging space, and that the WebSphere
Destination: Log, System Monitor Voice Response device driver is correctly
configured. If the problem still persists, call IBM
Support with details.
17509 Improper passing of local message
Severity: Red
Explanation: An attempt to write to an internal
message queue failed. Destination: Log, System Monitor, Alertable
User response: Restart the system. If the

problem persists, call IBM Support. 17601 TDM clock received error while
polling device driver
Severity: Yellow
Explanation: The tdmclockd daemon uses the
Destination: Log, System Monitor poll system call to receive asynchronous event
notification from the device driver. An error has
17511 Error opening line output occurred in poll system call.
Explanation: Cannot open line output device User response: If the problem persists, call IBM
file dev/acpa0llcd. Support with details.
User response: Make sure there is a onboard Severity: Yellow

Ultimedia Audio Adapter installed and Destination: Log, System Monitor, Alertable
configured.
Severity: White 17602 TDM clock event missing
Destination: Log, System Monitor Explanation: The device driver has indicated to
the tdmclockd daemon that an asynchronous
17518 ACPA unable to acquire ODM event is available when none has occurred.
information User response: Call IBM Support.
Explanation: The ACPA program encountered Severity: Yellow
an error when asking the system about
configured devices. Destination: Log, System Monitor, Alertable
User response: Check for other programs that
17603 TDM clock event is invalid

17604 • 17710
Explanation: The tdmclockd daemon received out of memory condition

an event for an invalid adapter.
Explanation: Your system is low on memory or
User response: Call IBM Support. paging space or both.
Severity: Yellow User response: Increase the amount of paging
space available. If the problem persists, install
more memory.
Severity: Red
17604 TDM clock event inconsistent
with state of the adapter Destination: Log, System Monitor, Alertable
Explanation: The tdmclockd daemon received
an event which is inconsistent with the internal 17608 TDM clock daemon cannot find
state of the telephony adapter. The tdmclockd any telephony adapters
daemon will try to correct this error by
Explanation: No adapter is installed or
restarting.
configured.
User response: Install one or more adapters and
Support.
try again. If the problem persists, call IBM
Severity: Yellow Support.
Destination: Log, System Monitor, Alertable Severity: Red
17605 Armed master device failed to
take over disabled master
17609 TDM clock ioctl failure
Explanation: The Digital Trunk Quad Adapter
Explanation: The tdmclockd daemon cannot
performing the role of the armed master TDM
communicate with the device driver because an
clock source failed to take over when the master
ioctl system call failed.
clock source was disabled. This may be caused
by a defective telephony adapter. User response: Call IBM Support.
User response: Run stand-alone diagnostics on Severity: Yellow
the adapter in question. Call IBM Support if the
problem persists. Destination: Log, System Monitor, Alertable
Severity: Red
17610 TDM clock fork failed
Explanation: The tdmclockd daemon cannot
start because the fork system call failed. This is
17606 Internal error in TDM clock likely to be caused by a lack of memory or
daemon paging space on the system.
Explanation: An unexpected internal error has User response: Follow the response procedure
occurred. described under error 17607. If the problem
Severity: Red
Severity: Red
17710 DSP microcode could not be

17607 TDM clock daemon experienced

17800 • 17808
loaded onto a DTTA adapter. adapter card. If the problem persists, call IBM
Support.
Explanation: WebSphere Voice Response failed
to load DSP microcode onto a DTTA adapter. Severity: Red
User response: Try restarting the pSeries system Destination: Log, System Monitor, Alertable
unit. Check that all required filesets are installed.
If the problem persists, call IBM Support.
17806 Adapter flash PROM power-on
Severity: Red self test failed
Destination: Log, System Monitor, Alertable Explanation: An error has occurred during the
AIB power-on self-test. The power-on self-tests
are executed every time the card is reset or the
17800 Not enough parameters provided
system is restarted.
to startup diagnostics
User response: Try restarting the pSeries system
Explanation: A script was called with the
unit. If the problem persists, call IBM Support.
wrong number of, or invalid, parameters. The
correct syntax is: Severity: Red
User response: Try restarting the pSeries system Destination: Log, System Monitor, Alertable
Severity: Red 17807 Failed to access adapter
components
Explanation: During the startup procedure, the
diagnostics detected an error on the telephony
17803 Unexpected error code reported by
adapter card. The diagnostics cannot access a
diagnostics
component on the card.
Explanation: An error occurred during the
User response: Try to re-run the startup
adapter or pack diagnostics but the reported
procedure. If the problem persists, run the
error code is not recognized.
stand-alone diagnostics to get more information
User response: Try restarting the pSeries system on the failure and to identify the FRU to be
unit. If the problem persists, call IBM Support. replaced.
Destination: Log, System Monitor, Alertable Destination: Log, System Monitor, Alertable
17805 Tested ARTIC card is not a 17808 Adapter AIB VERO component
telephony adapter test failed
Explanation: Before starting to test the ARTIC Explanation: A failure was detected on the
AIB, the diagnostics check the ID of the AIB telephony adapter card during the startup
attached to the ARTIC card. If the detected ID diagnostics.
doesn't correspond to the telephony adapter ID,
it means either that the test card is not a
telephony adapter or that the vital product data
(VPD) is corrupted.
on the failure and to identify the FRU to be
User response: Check that the card plugged replaced.
into the corresponding slot is a telephony
Severity: Red

17809 • 17821
Destination: Log, System Monitor, Alertable Explanation: During the startup procedure, the
diagnostics detected an error which should never
occur. The problem is located in the script file
17809 Telephony adapter VPIC
that drives the diagnostics. It is an internal
component test failed
software error.
Explanation: A failure was detected on the
adapter card during the startup diagnostics.
procedure. If the problem persists, call IBM
User response: Try to re-run the startup Support.
Severity: Red
on the failure and to identify the FRU to be Destination: Log, System Monitor, Alertable
replaced.
Severity: Red 17813 SCBus connection problem
between telephony adapters
diagnostics detected that at least one adapter is
17810 SC4000 component test failed
not connected to the others through the SCBus
Explanation: During the startup procedure, the cable. If more than one adapter is present in the
diagnostics detected a failure on the adapter. system unit, all adapters need to be connected
together through the SCBus cable.
procedure. If the problem persists, run the User response: Check that an SCBus cable
adapter stand-alone diagnostics to get more connects all adapters together. If the problem
information on the failure and to identify the persists, call IBM Support.
FRU to be replaced.
Severity: Red
Severity: Red
17820 Telephony adapter diagnostics
17811 AIB diagnostics cannot open cannot open device driver
SC4000 device driver
Explanation: During the startup procedure, the diagnostics detected an error when they try to
diagnostics detected an error when trying to use use a device driver resource. It is an internal
the SC4000 device driver resources. It is an software error. Either the device drivers have not
internal software error. Either the SC4000 device been loaded on the ARTIC or it is already used
driver has not been loaded on the ARTIC or it is by another process.
already used by another process.
User response: Try to re-run the startup procedure. If the problem persists, call IBM
procedure. If the problem persists, call IBM Support.
support.
Severity: Red
Severity: Red
17821 Unexpected software error during
17812 Unexpected software error during pack startup diagnostics
AIB startup diagnostics

17826 • 17903
diagnostics detected an error which should never devices need to be defined. To define a device,
occur. The problem is located in the script file the define method for that device is used. A
that drives the diagnostics. It is an internal define method creates an entry in the ODM
software error. database for the new device, so that the rest of
AIX knows about the device, and so that, when
the device is configured later using a
procedure. If the problem persists, call IBM
configuration method, there are some parameters
Support.
to retrieve and use. A define method moves the
Severity: Red device from the undefined state to the defined
state in ODM. One such define method failed.
Destination: Log, System Monitor, Alertable The device cannot be used until this problem is
corrected. This can indicate that the define
17826 Failed to load microcode file from method is not being called with root access, that
system unit to adapter a data file is not installed with correct
permissions, or that ODM has been locked by
Explanation: During the startup procedure, the some other software. The I/O subsystem cannot
diagnostics detected a problem when a be started.
microcode file is transferred from system unit to
the ARTIC memory. User response: If the problem persists, call IBM
Support.
procedure. If the problem persists, call IBM Severity: Red
Support. Destination: Log, System Monitor, Alertable
Severity: Red
Destination: Log, System Monitor, Alertable 17902 Failed to configure device
Explanation: As part of the WebSphere Voice
17900 Failed to add stanza information Response startup procedure, several logical
to ODM database devices need to be configured. To configure a
device, the configuration method for that device
Explanation: As part of the WebSphere Voice is used. A configuration method creates a special
Response startup procedure, the dtdd device file in /dev, allocates major and minor numbers
driver needs to have its details added to the for the device, and tells AIX that the device is
ODM database, so other software knows it is now available. A configuration method moves a
available to use. The odmadd tool is used to do device from defined to available state in ODM.
this. The tool failed to add the dtdd device One such define method has failed. The device
information to the ODM databases. The I/O cannot be used until this problem is corrected.
subsystem cannot be started. The I/O subsystem cannot be started.
User response: Check that the file specified User response: If the problem persists, call IBM
exists in your file system, and that is has read Support.
access from the root userid. If the problem
persists, call IBM Support. Severity: Red
Severity: Red Destination: Log, System Monitor, Alertable

17903 Failed to create telephony adapter
devices
17901 Failed to define device
Explanation: As part of the WebSphere Voice Response startup procedure, several logical
Response startup procedure, several logical devices need to be configured. The

17904 • 17910
DTQA_aib_walker cycles through all the cards User response: UNUSED

on the system, making those devices usable by
Severity: Red
the rest of WebSphere Voice Response. The
DTQA_aib_walker program failed. The I/O Destination: Log, System Monitor, Alertable
subsystem cannot be started.
User response: Try restarting the pSeries system 17907 Failed to unconfigure device
unit. Try reseating or removing certain adapters
to see if the problem follows a particular adapter. Explanation: Unconfigure method of a device
If the problem persists, call IBM Support. failed.
Severity: Red User response: Try restarting the pSeries system

Severity: Red
17904 Failed to clean up telephony Destination: Log, System Monitor, Alertable

adapter devices
Explanation: As part of the WebSphere Voice 17908 Could not load file onto
Response startup procedure, or when WebSphere telephony adapter
Voice Response shuts down, WebSphere Voice Explanation: Failed to load a file onto the
Response makes sure that everything is cleaned adapter.
up. Remnants of any logical devices are removed
at this point. The DTQA_destroy_adapter User response: Check that WebSphere Voice
program is used to make sure that logical Response filesets are installed correctly. Try
devices associated with the telephony device are restarting WebSphere Voice Response. Try
removed correctly. This program failed. The I/O restarting the pSeries system unit. If the problem
subsystem cannot be started. persists, call IBM Support.
User response: Try restarting the pSeries system Severity: Red

unit. Try reseating or removing certain cards to Destination: Log, System Monitor, Alertable
see if the problem follows a particular adapter. If
17909 AIB initialize procedure failed
Severity: Red
Explanation: AIB_initialize script failed.
User response: Check that WebSphere Voice
Response filesets are installed correctly. Try
17905 Invalid parameter passed to script restarting WebSphere Voice Response. Try
Explanation: A script was called with an invalid restarting the pSeries system unit. If the problem
parameter. persists, call IBM Support.
User response: Try restarting the pSeries system Severity: Red

unit. If the problem persists, call IBM Support. Destination: Log, System Monitor, Alertable
Severity: Red
Destination: Log, System Monitor, Alertable 17910 ioctl to telephony adapter device
failed
17906 UNUSED Explanation: DTQA_ioctl program reported a

failure.
Explanation: UNUSED

17911 • 17920
User response: If the problem persists, call IBM User response: Call IBM Support.
Support.
Severity: Red
Severity: Red
17916 DTQA_ioctl program error on
17911 File not found ENABLE
Explanation: A file required by WebSphere Explanation: DTQA_ioctl failed to enable the
Voice Response was not found. adapter card. The ioctl
IOCTL_ADAPTER_ENABLE failed.
User response: Make sure that all WebSphere
Voice Response filesets are installed correctly. If User response: Call IBM Support.
Severity: Red
Severity: Red
17917 Not enough parameters when
17912 File not executable calling script
Explanation: A file required by WebSphere Explanation: A script was called with the
Voice Response was found, but it does not have wrong number of parameters.
execute permissions set.
User response: Make sure that all WebSphere unit. If the problem persists, call IBM Support.
Voice Response filesets are installed correctly. If
Severity: Red
Severity: Red
17918 UNUSED
Explanation: UNUSED
17913 Syntax error invoking DTQA_ioctl
program User response: UNUSED
Explanation: WebSphere Voice Response uses Severity: Red
DTQA_ioctl to manipulate the adapter.
Severity: Red 17919 UNUSED
Destination: Log, System Monitor, Alertable Explanation: UNUSED
User response: UNUSED
17914 DTQA_ioctl program could not
open device file Severity: Red
Explanation: The open() system call issued by Destination: Log, System Monitor, Alertable
DTQA_ioctl to open the WebSphere Voice
Response device driver failed. WebSphere Voice 17920 Cannot move device from
Response uses DTQA_ioctl to manipulate the undefined to defined state
telephony adapter.
Explanation: The device is already defined in

17921 • 17929
the CuDv ODM database. The device must be in Explanation: The device must be in the
the undefined state for this to work. available state for this to work.
User response: Try restarting the pSeries system User response: Try restarting the pSeries system
unit. If the problem persists, call IBM Support. unit. If the problem persists, call IBM Support.
17921 Cannot move device from 17925 Cannot add device information to
undefined to defined state PdDv class of ODM
Explanation: The device must be in the Explanation: WebSphere Voice Response needs
undefined state before it can be defined. It is to add information to the PdDv class of ODM to
currently in some other state. tell AIX about the telephony devices. The
information is already there. The information
needs to be removed before it can be added.
Severity: Red
Severity: Red
17922 Cannot move device from defined
to undefined state
17926 Cannot undefine all WebSphere
Explanation: The device must be in the defined
Voice Response information from
state before it can be made undefined. It is
ODM
currently in some other state.
Explanation: There are still available WebSphere
Voice Response devices. All devices need to be
made unavailable before dtdd_undef can be
Severity: Red called.
Destination: Log, System Monitor, Alertable User response: Try restarting the pSeries system
17923 Cannot move device from defined Severity: Red

to available state
Explanation: The device must be in the defined
state before it can be made available. It is
17929 Root permission required to run
currently in some other state.
tool
Explanation: WebSphere Voice Response uses
tools to manipulate hardware devices. Some of
Severity: Red these tools need root permissions; one of these
tools has been called without these permissions.
Destination: Log, System Monitor, Alertable Use dirtalk_run to provide root permissions.
User response: Try restarting WebSphere Voice
17924 Cannot move device from Response. Try restarting the pSeries system unit.
available to defined state If the problem persists, call IBM Support.

17931 • 17942
Severity: Red Explanation: WebSphere Voice Response tries to

load a device driver into AIX kernel memory
when it starts up. The dtdd kernel extension is
already loaded. This implies that there has been
17931 DTQA_ioctl program could not a problem cleaning up the system when
query packs present WebSphere Voice Response was shutdown
previously.
the DTQA_ioctl program to query which packs User response: WebSphere Voice Response
and types of packs are presently connected to cannot start up with telephony devices. Try
each telephony adapter. This program could not restarting the pSeries system unit. If the problem
find out this information. persists, call IBM Support.
User response: Try restarting WebSphere Voice Severity: Red

Response. Try restarting the pSeries system unit.
Severity: Red
17935 dtdd define method failed
Explanation: WebSphere Voice Response needs
to add some information to ODM so that the rest
17932 DTQA_ioctl program returned of AIX knows about the telephony devices. It
invalid output uses the standard AIX define method to do this.
It failed.
the DTQA_ioctl program to manipulate the User response: Try restarting WebSphere Voice
telephony adapter. This program returned invalid Response. If the problem persists, call IBM
output. Support.
User response: Try restarting WebSphere Voice Severity: Red

Support.
Severity: Red
17942 Configuration method failed to
Destination: Log, System Monitor, Alertable get vital product data (VPD) from
hardware.
17933 DTQA_ioctl program failed Explanation: As part of the WebSphere Voice

Response startup procedure, several hardware
Explanation: WebSphere Voice Response uses devices are configured. To configure a device,
the DTQA_ioctl program to manipulate the WebSphere Voice Response needs to know the
telephony adapter. This program reported an device type, model, and version number. This
error in an operation it was asked to do. information is held in a block of data known as
User response: Try restarting WebSphere Voice the vital product data (VPD). The VPD is
Response. If the problem persists, call IBM burnt-in to memory on the hardware device. The
Support. sysconfig() call is used to ask the hardware
device driver what the VPD contains. The
Severity: Red configuration method failed to read this VPD
Destination: Log, System Monitor, Alertable information from the hardware device, due to a
failure reported by the sysconfig() AIX function
call. Either the sysconfig call itself failed, or some
17934 Kernel extension already loaded other failure was detected by the device driver.

17943 • 17947
User response: The I/O subsystem cannot use incorrect) command-line parameters are supplied
this device. The I/O subsystem cannot be by whatever data is stored in ODM for this
started. If the problem persists, call IBM Support. device in the PdDv database, in addition to some
flags supplied by the caller of mkdev.
Severity: Red
User response: The I/O subsystem cannot use
this device. Extract the contents of the ODM
PdDv database using odmget and send the
17943 Configuration method failed to output, together with the error log to IBM
get vital product data (VPD) from Support.
hardware.
Severity: Red
devices are configured. To configure a device,
WebSphere Voice Response needs to know the 17946 Configuration method failed to
type of the device, its model and version access ODM
numbers. This information is held in a block of
data known as the vital product data (VPD). The
VPD is burnt-in to memory on the hardware
devices are configured. To configure a device, the
device. The sysconfig() call is used to ask the
configuration method for that device is used. The
hardware device driver what the VPD contains.
configuration method needs to access ODM to
This function is passed a data structure into
find parameters with which the device should be
which the device driver must copy the VPD
configured. The odm_initialize call is used to
information. The size of this structure that the
gain access to ODM. This call failed. The I/O
device driver expects is different from what the
subsystem cannot use this device.
configuration method is passing. This usually
indicates a mismatch between the versions of the User response: Backup the error log. Try
device driver and the configuration method. restarting the pSeries system unit. If the problem
persists, send the error log to IBM Support.
User response: The I/O subsystem cannot use
this device. Check that any service updates made Severity: Red
to WebSphere Voice Response completed
correctly. If you are currently using a Destination: Log, System Monitor, Alertable
privately-patched version of the device driver,
restore the original and contact IBM Support. 17947 Configuration method failed to
Severity: Red lock ODM
Destination: Log, System Monitor, Alertable Explanation: As part of the WebSphere Voice
17944 Configuration method called with configuration method for that device is used. The
invalid parameters configuration method needs to access ODM to
find parameters with which the device should be
configured. To avoid race and deadlock
conditions, the ODM database has a lock which
must be obtained before it can be used. The
odm_lock call is used to gain access to ODM.
configuration method could not parse its
This call failed. The I/O subsystem cannot use
command-line parameters correctly.
this device.
Configuration methods are called indirectly by
the mkdev system command. The (apparently User response: Backup the error log. Try

17948 • 17952
restarting the pSeries system unit. If the problem

find data in ODM
Severity: Red
Destination: Log, System Monitor, Alertable Response startup procedure, several hardware
17948 Configuration method failed to configuration method needs to access ODM to
lock ODM find parameters with which the device should be
Explanation: As part of the WebSphere Voice configured. It uses an SQL-like query language
Response startup procedure, several hardware to get the information needed, using the
devices are configured. To configure a device, the odm_get_first system call. This call failed. The
configuration method for that device is used. The I/O subsystem cannot use this device.
configuration method needs to access ODM to User response: Backup the error log. Try
find parameters with which the device should be restarting the pSeries system unit. If the problem
configured. Parameters are stored in ODM in persists, use the odmget <ODM_class_name> call
various classes of database. The odm_open_class to dump the contents of ODM to a file, and send
system call is used to give access to part of the this with the error log to IBM Support.
ODM database. This call failed. The I/O
subsystem cannot use this device. Severity: Red
User response: Backup the error log. Try Destination: Log, System Monitor, Alertable
17951 Configuration method called with
Severity: Red device already available
17949 Configuration method failed to configuration method for that device is used. The
find expected data in ODM configuration does many things, then moves the
Explanation: As part of the WebSphere Voice device from the defined state to the available
Response startup procedure, several hardware state. The configuration method for this device
devices are configured. To configure a device, the noticed that the device is already in the available
configuration method for that device is used. The state. The I/O subsystem cannot use this device.
configuration method needs to access ODM to User response: Backup the error log. Try
find parameters with which the device should be restarting the pSeries system unit. If the problem
configured. It uses an SQL-like query language persists, use the odmget CuAt and lsdev -C calls,
to get the information needed. The information place the output into a file, and send it with the
queried was not in the expected place in ODM. error log to IBM Support.
The I/O subsystem cannot use this device.
Severity: Red
User response: Backup the error log. Try
restarting the pSeries system unit. If the problem Destination: Log, System Monitor, Alertable
persists, use the odmget <ODM_class_name> call
to dump the contents of ODM to a file, and send
this with the error log to IBM Support.
load kernel extension into
Severity: Red memory

17953 • 17956
devices are configured. To configure a device, the detailed information about the cause of the error.
configuration method for that device is used. The The kernel extension can usually send this
configuration does many things, including trying information back to the config method. Here, this
to load a device driver that services the is not the case. The reason field in the failure
hardware into AIX kernel memory. The loadext report is still undefined. This usually implies a
system call is used to do this. This call failed. failure in the copy_out() system call, or in the
This problem usually indicates that the previous sysconfig call itself. The I/O subsystem cannot
shutdown of WebSphere Voice Response did not use this device.
complete cleanly. The I/O subsystem cannot use
this device.
User response: Backup the error log. Try persists, call IBM Support.
Severity: Red
Severity: Red
17955 Configuration of logical device
failed
allocate a major number
Explanation: As part of the WebSphere Voice devices are configured. To configure a device, the
Response startup procedure, several hardware configuration method for that device is used. The
devices are configured. To configure a device, the configuration does many things, including
configuration method for that device is used. The calling the configuration entry point of the kernel
configuration does many things, including trying extension for the device it is trying to configure.
to allocate a unique major number which is The kernel extension has failed to execute its
associated with all devices used by WebSphere entry point as an error has occurred. Technical
Voice Response. The genmajor call is used to details of the report have been passed back up to
provide this number. This call failed. The I/O the configuration method. The information is
subsystem cannot use this device. provided in the parameters to this error. This
error usually indicates that there is a serious
problem in the device driver. The I/O subsystem
cannot use this device.
Severity: Red
Destination: Log, System Monitor, Alertable persists, call IBM Support.
Severity: Red
17954 Configuration of logical device
failed
17956 UNUSED
devices are configured. To configure a device, the Explanation: UNUSED
configuration does many things, including
calling the configuration entry point of the kernel Severity: Red
extension for the device it is trying to configure.
This is done using the sysconfig system call. The Destination: Log, System Monitor, Alertable
call reported an error, which usually provides

17957 • 17964
User response: This problem should clear when

17957 UNUSED
you restart WebSphere Voice Response. Backup
Explanation: UNUSED the error log. If the problem persists, call IBM
Support.
Severity: Red
Severity: Red
17963 mkdev failed to make an ARTIC

17958 UNUSED
device available
Explanation: UNUSED
Explanation: As part of its startup procedure,
User response: UNUSED WebSphere Voice Response checks the interrupt
priority of all telephony adapters by temporarily
Severity: Red removing the ARTIC960 device drivers.
Destination: Log, System Monitor, Alertable WebSphere Voice Response uses the mkdev tool
to recreate them with the new interrupt priority.
A call to mkdev failed. A device driver cannot be
17961 odmadd failed to set up telephony recreated; the adapter is not set to the correct
adapter interrupt priority interrupt priority. WebSphere Voice Response
Explanation: When WebSphere Voice Response will not start.
starts, it makes sure that all adapters have the User response: This problem should clear when
correct interrupt priority. WebSphere Voice you restart WebSphere Voice Response. Backup
Response uses the AIX odmadd tool to add an the error log. If the problem persists, call IBM
ODM stanza to CuAt for each card. The odmadd Support.
tool returned an error. The I/O subsystem cannot
use this device. Severity: Red
User response: Backup the error log. Try Destination: Log, System Monitor, Alertable
persists, call IBM Support. 17964 Adapter card not set up with high
Severity: Red enough interrupt priority
Destination: Log, System Monitor, Alertable Explanation: As part of its startup procedure,
WebSphere Voice Response must make sure that
all adapters have the correct interrupt priority.
17962 rmdev failed to remove an ARTIC This should be done automatically whenever
device WebSphere Voice Response starts up. The
Explanation: As part of its startup procedure, operation to set up the interrupt priority has not
WebSphere Voice Response must make sure that completed successfully, leaving this adapter with
all telephony adapters have the correct interrupt an incorrect interrupt priority. The card will not
priority. To do this, it must temporarily remove be made available for use by WebSphere Voice
all device drivers that support the hardware Response.
directly, that is, all the ARTIC960 device drivers. User response: This problem should clear when
The rmdev tool is used for this. The rmdev tool you restart WebSphere Voice Response. Backup
returned an error. A device cannot be removed, the error log. If the problem persists, call IBM
so the adapter cannot be set to the correct Support.
interrupt priority. WebSphere Voice Response
will not start up. Severity: Red

17965 • 17970

17965 Failed to start tdmclockd daemon
device driver has detected many problems,
Explanation: The tdmclockd daemon manages which are queued. The queue is full and new
the clock source; this daemon did not start errors cannot be queued. This can indicate an
because of one of: (1) The dtalarmd daemon is error storm: the device driver may be generating
not available (2) Lack of system resources (3) A numerous errors repeatedly. The WebSphere
device driver failure Voice Response process collecting these errors
may be blocked, hung, or have died abnormally.
User response: Check the error log for
tdmclockd entries. If there are no entries for the User response: Look through the error log, and
dtalarmd daemon, the tdmclockd daemon is not try to solve any problems that may have caused
available, and you should check that all further problems to be reported by the device
WebSphere Voice Response filesets are correctly driver. Restart WebSphere Voice Response. If this
installed. If you suspect a device driver failure, problem persists, call IBM Support.
try restarting your pSeries system unit, reseating
Severity: Yellow
your adapter, or trying a different adapter. If the
problem persists, call IBM Support. Destination: Log, System Monitor, Alertable
Severity: Red
17969 Device driver lost
communications link to
embedded software
17966 DTQA_ioctl program error on
ENABLE
device driver has detected a problem with the
Explanation: WebSphere Voice Response uses communications link which connects the device
DTQA_ioctl to manipulate the telephony driver with the embedded software running on
adapters. The tool tried to enable the adapter. the adapter. The device driver detects there is a
The ioctl IOCTL_ADAPTER_ENABLE failed. problem in several ways, including: * A primitive
has been sent to the adapter, but a response to
that primitive was not received by the device
Severity: Red driver in the allowable time period. The
correlator object used to track the primitive
Destination: Log, System Monitor, Alertable response timed out. * The Primitive_DataCnf
primitive timed out. * The driver waited for a
17967 Device driver I/O failure location in memory to be set to a value before it
could use the information in a DMA data block. *
Explanation: The WebSphere Voice Response The driver waited for too long, indicating some
device driver has detected a problem getting problem either in the embedded software, the
data from, or putting data to, the hardware driver timeout code, or the DMA operation over
device, or has found that some data from the the PCI bus.
hardware is corrupted or invalid.
User response: The adapter, and all packs Response. If this problem persists, call IBM
connected to the failing adapter, are disabled. Support.
Call IBM Support.
Severity: Red
Severity: Red
17970 Adapter failure reported

17968 Device driver error queue
overflow Explanation: RTT, the software that runs on the

17971 • 17972
adapter, has detected a failure on the adapter. User response: Interrupts to AIX can be delayed
RTT has sent the WebSphere Voice Response if there are other devices in this system with
device driver a confirmation primitive to an higher interrupt priority. Check if removal of
earlier request. That primitive contains the failure other devices solves the problem. DMA
reason. This error is usually caused by an operations can be delayed if there is a lot of
internal programming error, but it can indicate a DMA activity caused by other adapters, or
hardware problem. The adapter and associated components on the motherboard which have a
packs are no longer usable. This error may be a higher arbitration level than the adapter. This can
symptom of another error that has already been often be solved by moving the adapter to a
reported. different slot, one that is on the primary bus for
this machine type. To see which slots are primary
User response: If this is the only adapter on the
and which are secondary, refer to the manuals
system, the adapter and associated packs are
for your machine.
recycled automatically. If there are two adapters,
the adapter remains in the failed state until you It is also possible that software or firmware
restart WebSphere Voice Response. Check the updates are required. The cause of the problem
error log for errors pointing to an earlier failure can be due to one or more of the following:
of adapter software. If there is a report of v Check the firmware levels if you have a
adapter software failure, you can ignore this pSeries type 7028-6C4. Some versions can
error. If the problem persists, call IBM Support. cause adapter interrupt problems. These were
Severity: Red corrected in Firmware update 3R050405.
v Check that the system is not running a
program that locks out the hardware
interrupts (such as pmcycles).
17971 WebSphere Voice Response failed
to service adapter interrupt fast If the problem persists, call IBM Support.
enough
Severity: Yellow
Explanation: Every 20 milliseconds the adapter:
- Passes voice data to AIX using DMA, so it can
be recorded. - Interrupts AIX so the data can be
processed. - Copies voice data from AIX, using 17972 TDM hardware failure reported
DMA, to transmit on the line. These operations by telephony adapter
must complete within a certain time, or the
packs connected to this adapter will not have Explanation: RTT, the software that runs on the
any data to transmit in this 20ms timeslot. This adapter, has detected a failure on the adapter.
error indicates that one or all of these operations RTT has sent the WebSphere Voice Response
has taken longer than expected, and the pack device driver a confirmation primitive to an
cannot be supplied with voice data for a 20ms earlier request. This primitive contains the failure
period or longer. Small amounts of inbound data reason of RTT_SC4K_ERROR. The error detected
are lost, when recovering from this error, concerns the part of the adapter hardware that
resulting in break-up of recorded messages. interfaces with the TDM bus (SCBus). This error
Outbound data is not lost, but is stalled until it is usually caused by an internal programming
can be played to the caller. While the adapter error, but it can indicate a hardware problem.
recovers from this error, the pack cannot be The adapter and associated packs are no longer
supplied with more voice data, and it plays the usable. This error may be a symptom of another
previous 40ms loop of voice data until the error that has already been reported.
problem has passed. So the outbound voice data User response: If this is the only adapter on the
can sound like stuttering or stammering to the system, the adapter and associated packs are
caller. recycled automatically. If there are two adapters,

17973 • 17977
the adapter remains in the failed state until your pool), or the system running out of mbufs.
restart WebSphere Voice Response. Check the
User response: Make sure that the number of
error log for other errors pointing to an earlier
mbufs available on your system is adequate. Try
failure of the adapter software. If the problem
increasing it to see if this problem persists. Make
sure that the system parameter controlling the
Severity: Red number of mbufs in the CCS receive mbuf pool
is large enough. Try increasing it. If the problem
persists, call IBM Support for assistance.
Severity: Red
17973 Telephony adapter driver detected
invalid size on primitive Destination: Log, System Monitor, Alertable
device driver has detected that a primitive 17975 Token ring adapter and telephony
(RTT_DMA_DATA_IND) sent by the embedded adapter coexistence warning
software (RTT) on the adapter has an invalid size
field. This indicates either a mismatch in versions
detected a token-ring adapter. In some models of
between the device driver (dtdd) and the
pSeries computer token-ring adapters must be in
embedded software (RTT), a data corruption, or
lower-number slots than adapters to avoid
a software programming error. This situation
performance problems when the adapter is
results in interrupts from the adapter being
enabled. The error parameters show adapters are
ignored. If the same problem occurs on
causing this problem.
successive interrupts, the adapter fails, and all
packs connected to it disable their trunks. User response: Shut down your system. Move
the token-ring adapters to lower-number slots
User response: This error is not expected to
than the telephony adapters. Restart your
occur, but if it does, call IBM Support
system. Use the diag -a tool to remove logical
immediately for assistance.
devices where the physical devices have been
Severity: Red moved. If the problem persists, call IBM Support
for assistance.
Severity: Yellow
17974 Telephony adapter driver ran out Destination: Log, System Monitor, Alertable
of CCS receive mbufs
Explanation: The WebSphere Voice Response 17976 UNUSED
device driver has two pools of memory buffers
Explanation: UNUSED
(mbufs) that are used to temporarily store CCS
data when it arrives from the pack. This error User response: UNUSED
indicates CCS data has arrived, but there are no
mbufs in the required pool in which the data can Severity: Red
be held. The CCS data is lost. Signalling Destination: Log, System Monitor, Alertable
transitions carried by the signalling link from the
switch to the CCS signalling process will not be
passed. This failure can be caused by the mbuf 17977 SCBus problem detected by
pool not being large enough to cope with the telephony adapter embedded
amount of CCS receive traffic on this trunk, the software
CCS signalling process not reading data from the Explanation: The embedded software on the
device driver regularly enough (causing a card continually monitors the status of the
build-up of used mbufs, and a drain on the mbuf SCBus, and has detected a problem. The adapter

17978 • 17980
was writing data to the SCBus. It read back the transmitted by this DTTA over the SCBus may be
data, and compared what was read-back against corrupted.
what was written, to detect corruptions. Such
User response: Check that all devices on the
corruptions were detected. This error is
SCBus are configured correctly. Try re-starting
generated when the first SCBus problem is
the system to check if the problem recurs. Run
detected. The same check is made every 20ms.
diagnostics on the card that reported the
When the problem clears, error 17978 is raised.
problem. Run diagnostics on all other
Possible causes of the problem are: - SCBus cable
SCBus-connected devices. If the problem persists,
- Hardware in the card which detected this
call IBM Support for assistance.
problem - Hardware of other SCBus-connected
devices - Incorrect configuration of other Severity: Green
SCBus-connected devices During the period
between this error being reported, and when the Destination: Log, System Monitor, Alertable
error clears, voice data transmitted by this card
over the SCBus may be corrupted. 17979 Error found by adapter HAL
User response: Check that all devices on the (hardware access layer) or other
SCBus are configured correctly. Try re-starting related software
the system to check if the problem recurs. Run Explanation: One of the software components
diagnostics on the card that reported the which handles the initialization, testing, and
problem. Run diagnostics on all other interface to the telephony adapter has found a
SCBus-connected devices. If the problem persists, problem that is further identified by the two
call IBM Support for assistance. string and three numeric parameters that
Severity: Yellow accompany this error. Possible causes of the
problem are: - Hardware in the adapter that
Destination: Log, System Monitor, Alertable detected this problem - Software installation
errors or problems
17978 SCBus problem cleared by User response: Try re-starting the system to
telephony adapter embedded check if the problem recurs. Run diagnostics on
software the card that reported the problem. If the
problem persists, call IBM Support for assistance.
Explanation: The embedded software on the
adapter card continually monitors the status of Severity: Red
the SCBus. A problem was previously detected,
and reported with error code 17977. The problem Destination: Log, System Monitor, Alertable
has now cleared. The adapter was writing data
to the SCBus. It read back the data, and 17980 A wrap plug is installed in the
compared what was read-back against what was telephony adapter cable socket
written, to detect corruptions. Such corruptions
were detected. Error 17977 is generated when the Explanation: A 36-pin wrap plug is installed in
first SCBus problem is detected. The same check the connector on the backplate. This has
is made every 20ms. The problem has now probably been left in place from some previous
cleared. Possible causes of the problem are: - diagnostic testing, or your cable or card
SCBus cable - Hardware in the adapter that connector may be bad. The Wrap plug prevents
detected this problem - Hardware of other WebSphere Voice Response determining whether
SCBus-connected devices - Incorrect the trunk should be configured as T1 or E1.
configuration of other SCBus-connected devices Possible causes of the problem are: - A wrap
During the period between the error being first plug is installed - Your cable is bad (the one that
reported, and when the error clears, voice data plugs into the adapter) - The connector on your
adapter or the card itself is bad

17981 • 17987
User response: Replace the wrap plug with a system initialization. Possible causes of the
T1 or E1 cable. Replug the cable. Replace the problem are: - There is no SCBus/H.100 cable
cable. If the problem persists, call IBM Support connecting the adapters - There is a cable and it
for assistance. is faulty
Severity: Red User response: Plug an SCBus/H.100 cable.
Replug the cable and make sure that all
connectors are seated correctly. Replace the cable
with a known good T1 or E1 cable. If the
17981 Cable with unknown ID installed problem persists, call IBM Support for assistance.
in telephony adapter
Severity: Red
Explanation: The cable installed in the adapter
has an unknown type. The unknown cable
prevents WebSphere Voice Response determining
whether the trunk should be configured as T1 or 17984 Errors found running ricdiag on
E1. Possible causes of the problem are: - Your telephony adapter
cable is bad (the one that plugs into the adapter)
Explanation: The adapter diagnostics failed
- You have made the cable with an incorrect ID -
during system initialization. Possible causes of
The connector on your adapter or the card itself
the problem are: - A bad DTTA adapter - There is
is bad
no SCBus/H.100 cable connecting the adapters -
User response: Replug the cable. Replace the There is a cable and it is faulty
cable with a known good T1 or E1 cable. If the
User response: Run the tests again. Replace the
problem persists, call IBM Support for assistance.
DTTA adapter. Plug an SCBus/H.100 cable.
Severity: Red Replug the cable and make sure that all
connectors are seated correctly. If the problem
persists, call IBM Support for assistance.
Severity: Red
17982 No cable installed in telephony
adapter Destination: Log, System Monitor, Alertable
Explanation: There does not appear to be a
cable plugged into the telephony adapter. 17986 DTTA adapter could not be reset.
Possible causes of the problem are: - There is no
cable plugged into the adapter - You have a cable
to reset a DTTA adapter.
and it is bad - The connector on your adapter or
the card itself is bad User response: Try restarting WebSphere Voice
User response: Plug the cable. Replug the cable.
Replace the cable with a known good T1 or E1
cable. If the problem persists, call IBM Support Severity: Red
for assistance.
Severity: Red
Destination: Log, System Monitor, Alertable 17987 DTTA adapter could not be
loaded.
17983 Errors found testing SCBus Explanation: WebSphere Voice Response failed
connection to telephony adapter to load microcode onto a DTTA adapter.
Explanation: Clocking or data transfer problems User response: Try restarting WebSphere Voice
have been detected by the SCBus test during

17988 • 17991
Response. Try restarting the pSeries system unit. Destination: Log, System Monitor, Alertable
Check that all WebSphere Voice Response filesets
are installed. If the problem persists, call IBM
Support.
Severity: Red
17988 DTTA adapter failed to load DSP

microcode
to load DSP microcode onto a DTTA adapter.
User response: Try restarting WebSphere Voice
Check that all WebSphere Voice Response filesets
are installed. If the problem persists, call IBM
Support.
Severity: Red
17990 DTTA trunk type could not be set.

to set the trunk type of a DTTA adapter.
unit. Check that all WebSphere Voice Response
filesets are installed. If the problem persists, call
IBM Support.
Severity: Red
17991 Uncompressed dump of a DTTA

adapter failed.
to perform an uncompressed dump of a failed
DTTA adapter. This dump could have been used
for problem determination purposes. a DTTA
adapter.
User response: Ensure that there is at least
32MB of space in the /home filesystem. Ensure
that the dump file is writeable by dtuser. If the
Severity: Red

18002 • 18401
VAD (Voice Application Development)

administrator user account are provided.
18002 Cannot receive request from
VAGIO User response: None.
Explanation: The I/O interface is not Severity: White
responsive. This may indicate the system is not
working properly. Destination: Log, System Monitor
User response: Restart the system, if possible. If

the problem persists, call IBM Support. 18201 Database access failed to retrieve
administrator data
Severity: Yellow
Explanation: During the logon process the
Destination: Log, System Monitor retrieval of administrator data from the database
failed.
18004 Notify Appl failed User response: Retry the logon process after a
delay. If the problem persists restart the system.
Explanation: VAGIO could not to send database
If the fails to cure the problem call IBM Support.
requests to DBIM. This probably means that the
system is already in an unusable state. Severity: White
User response: Restart the system. Destination: Log, System Monitor
Severity: Yellow
18400 State symbolic to relative
translation error
Explanation: When saving a state table, the ID
18015 Malloc failed
of the state could not be found within the
Explanation: An application tried to allocate symbol table.
main storage, but the request failed. This occurs
User response: Have the error log available and
either because the work load on the system is too
call IBM Support.
heavy, causing a shortage of storage, or because
an internal programming error causes allocated Severity: Yellow
storage not to be freed when it is no longer
needed. Destination: Log, System Monitor
User response: Close as many windows as

possible and restart the application.Try the 18401 State relative to symbolic
function again when the work load on the translation error
system has been lightened. If the problem Explanation: When opening a state table, the
persists, have the error log available and call label ID of the relative state (for the state edge)
IBM Support. could not be found in the labels.
Severity: Yellow User response: Have the error log available and
Destination: Log, System Monitor call IBM Support.
Severity: Yellow
18200 Incorrect password Destination: Log, System Monitor
Explanation: An administrator entered an
invalid ID or password. Information about the
display where the logon was tried and the

19006 • 19028
ACL (Application Connectivity Link)

19006 ACL: error retrieving sysparm
data
19026 ACL: cannot connect to siglib
Explanation: Cannot access or recognize ACL
system parameter data. Explanation: ACL cannot connect to the
signalling library. It therefore cannot perform any
User response: Check that all system
functions. The error code is logged.
parameters for ACL are correct. If they are
correct, call IBM Support. User response: Call IBM Support.
19007 ACL: error opening mpq device 19027 ACL: internal error
Explanation: Cannot open ACL port. If this Explanation: Refer to the error field for more
error is issued at startup, it is fatal. If this error is information. The error field shows the error
issued after recovery from an ACL link failure, returned by the mpq device driver. Possible
check the errno field for the reason. values are: 27 CANNOT_GET_SEM 28
CANNOT_OPEN_DEVICE 29
User response: Check mpq card, port, and
OPEN_PORT_INIT_FAILED 30
switch.
OPEN_ACESS_DENIED 32
Severity: Red CANNOT_POLL_FOR_STATUS 33
CANNOT_GET_MPQ_STATUS 34
CANNOT_START_MPQ 35
MPQ_NOT_STARTED 46 CANNOT_HALT_MPQ
19011 ACL error: data line down 47 CANNOT_CLOSE_MPQ 48
MPQ_NOT_HALTED
Explanation: ACL mpq connection is down.
This error is issued if WebSphere Voice Response User response: Call IBM Support.
receives a cleardown request from the switch.
Severity: Yellow
This is usually caused by the switch becoming
temporarily overloaded. Destination: Log, System Monitor, Alertable
User response: If the ACL link does not recover
within a few minutes, check the ACL cable and 19028 ACL: link failure
the switch setup. If the problem persists, call
Explanation: The ACL link has gone down
IBM Support.
without a cleardown request from the
Severity: White switch.WebSphere Voice Response tries to restart
the link at 30 second intervals.
User response: If the ACL link does not recover
within a few minutes, check the ACL cable and
19023 ACL: signalling library call failed
the switch setup. If the problem persists, call
Explanation: The ACL or WebSphere Voice IBM Support. Cleared by: 19029
Response signalling library has a problem.
Severity: Yellow
Severity: Red

19029 • 19034
other ACL links to the HICOM are creating an

19029 ACL: link failure has cleared
excessive amount of traffic on the ACL link.
Explanation: The ACL link has been restarted.
Severity: Yellow
This message will normally follow an ACL link
failure (message number 19028). If the ACL link Destination: Log, System Monitor, Alertable
is down for a short time, the ACL link failure
message may not be issued.
19033 ACL: HICOM rejected a request
User response: None. Clears: 19028 to set monitor status.
Severity: Green Explanation: The ACL process tried to set a
monitor by sending a request to the HICOM.
This request was rejected by HICOM as being
invalid.
19030 ACL: cannot access iconv
User response: Check that ACL is running
functions for ASCII to EBCDIC
correctly on the HICOM. Check that the monitor
conversion
(lineid) requested is valid for the HICOM.
Explanation: The ACL process needs access to
Severity: Yellow
the iconv functions to perform conversion
between ASCII and EBCDIC. Destination: Log, System Monitor, Alertable
User response: Install the AIX iconv packages.
19034 ACL: internal error occurred
Severity: Red
during monitor processing
Explanation: The ACL process controls the
setting up of monitors with an internal state
19031 ACL: iconv failed for ASCII to machine. Some sequence of events occurred that
EBCDIC conversion is not permitted by the state machine. There
might not be a monitor setup for this trunk and
Explanation: A call to iconv failed when ACL
channel.
was trying to convert between ASCII and
EBCDIC. User response: Check that the problem can be
reproduced, and take an AIX system trace of the
User response: Ensure that the AIX iconv
problem. Call IBM Support.
packages are installed.
Severity: Yellow
Severity: Red
19032 ACL: repeatedly failed to set

monitor status
Explanation: The ACL process attempted to set
a monitor by sending a request to the HICOM.
This request was rejected by HICOM a number
of times because the HICOM replied that it was
busy. The ACL process gives up after a number
of attempts to set the monitor.
User response: Check that ACL is running
correctly on the HICOM. Check to see if any

20001 • 20007
CA (Custom Server)
20001 CA entry requested not found 20004 Channel process link count for
this CA is invalid
Explanation: Before building or starting a
custom server, there must be an entry in the CA Explanation: The custom server entry table is
entry table that corresponds to this application. corrupted, and a counter for the number of
Such an entry has not been found, and the action channel process links is invalid.
of building or starting the custom server has
User response: Restart the custom server
been aborted. This occurs only if the CA entry
control program and all the custom servers. If
table has been corrupted, and should not occur
during normal operations.
Severity: Yellow
control program and all the custom servers. If Destination: Log, System Monitor
Severity: Yellow 20005 Channel process link ID returned
is invalid
Explanation: A request for a channel process
link ID has returned with an invalid ID. An
20002 Attempt to allocate memory failed
invalid ID is one that is greater than the total
Explanation: Some of the subroutines require number of channel processes running, or less
some temporary memory to be allocated. This than zero.
error indicates that the attempt to allocate this
User response: Retry the request for the channel
memory has failed.
process link. Call IBM Support.
User response: Reduce memory usage if
Severity: White
possible.
Severity: Yellow
20006 Message to send has been
corrupted
20003 Attempt to get system parameter
Explanation: The message to be sent has been
failed
corrupted. Some messages use shared memory
Explanation: While a custom server was areas, so it is possible for one process to corrupt
starting up, the initialization process could not the data of another process.
obtain a system parameter needed. Your system
parameter database could be corrupted.
control program and all the custom servers. If
User response: Try to update the parameters in the problem persists, call IBM Support.
the system parameters. You might try bringing
Severity: Yellow
the system down and doing a recoverDMS. If
this fails, restore your system parameters from Destination: Log, System Monitor
the backup. If the problem persists, call IBM
Support.
20007 Attempt to exec a process failed
Severity: Yellow
Explanation: The AIX subroutine call execl() or
Destination: Log, System Monitor execv() has failed to execute. See the IBM AIX
Version 4.2 Technical Reference: Volume 1.

20008 • 20014

Severity: Yellow
Explanation: A message has been sent to a
Destination: Log custom server that does not correspond to the
predefined functions handled by this custom
server. This could occur if custom servers are
20008 Attempt to fork process failed stopped and started, and state tables use the
Explanation: The AIX subroutine call fork() has Host Actions improperly. For example, they may
failed to execute. This is most likely to occur attempt to send a message to a custom server
when the maximum number of user processes with a link ID that was never received or is
has been reached. See IBM AIX Version 4.2 invalid.
Technical Reference: Volume 1. User response: Call IBM Support.
User response: Increase the maximum number Severity: White
of user processes allowed by your AIX systems
management. Call IBM Support. Destination: Log
Severity: White
20012 Cannot stop child process
Explanation: A custom server has used the
CA_Stop_CA() subroutine call, sending as an
20009 Request for all CAs not received argument the name of a server that is not
Explanation: At system initialization, the running.
custom server control program has requested the User response: Check that the custom server is
list of custom servers to start, and the request not running.
has failed or a timeout has occurred. The most
probable cause is that the database needs Severity: White
recovering.
Destination: Log
User response: Recover the database and restart
the system. Call IBM Support.
20013 CA currently being built
Severity: Yellow
Explanation: A request to build a custom server
Destination: Log, System Monitor has been issued while that same custom server is
being built as a result of a previous request.
20010 Environment variable missing User response: Wait until the first build
completion notification is received before
Explanation: The custom server subsystem uses reissuing a build request for the same custom
some of the environment variables provided with server.
the product. If one of them is missing, some
functions within the custom server subsystem Severity: White
cannot execute.
Destination: Log
User response: Set the appropriate value for the
missing environment variable and restart the
20014 Invalid buffer received
system. Call IBM Support.
Explanation: An internal buffer has been
Severity: Yellow
received with invalid contents. This should never
Destination: Log, System Monitor happen. An attempt to recover from the error has
been made.

20015 • 20019
User response: Try it again. If the problem Destination: Log

Severity: Green 20017 Different software versions
detected in custom server
Destination: Log
Explanation: The software version detected in
the custom server application is not the same as
20015 Failed to update length in newly
the version registered in the custom server
created voice message
library. This can result in errors when the custom
Explanation: When a voice message is created server application is run.
using CA_Create_Voice_Msg(), the length of the
User response: Rebuild the custom server
message is updated via UPSERVER. Here, the
application with the current version of
message has been created successfully, but the
WebSphere Voice Response. Alternatively, run the
length has not been updated correctly.
custom server application with the version of
User response: Delete the voice message and WebSphere Voice Response with which the
repeat the process. If the problem persists, call executable was originally built.
IBM Support.
Severity: Yellow
Severity: Yellow
Destination: Log
Destination: Log
20018 Requests already pending on
20016 Custom server function not called custom server at
in initial thread OpenHostServerLink
Explanation: Multi-threaded use of the custom Explanation: The custom server already had at
server library is not supported. Here, a custom least one pending request present, previously
server function has been called from a thread received from the same channel process, before
other than the initial thread. The error is logged OpenHostServerLink was executed. This can
only once for each custom server application result in errors when the custom server
process, when the first out-of-initial-thread application is run, and some shared memory
function call is detected. By default WebSphere buffers might not be freed.
Voice Response runs with the environment
User response: Correct the custom server
variable AIXTHREAD_SCOPE=S. If
program logic. Make sure that every message
AIXTHREAD_SCOPE is changed this error can
that is received using CA_Receive_DT_Msg(),
be issued because of the mapping of user and
and is for a custom server function that has at
kernel threads even though only one user thread
least one input parameter, is followed by a
is used.
CA_Get_DT_Parameters() or is cancelled by a
User response: No action is required unless CA_Send_DT_Error().
there are problems running the custom server. If
Severity: Yellow
custom server functions are called from different
threads in the custom server program, Destination: Log, System Monitor
unexpected results can occur. In this case it will
be necessary to redesign the custom server
20019 Custom server missing or not
program to avoid the problematic thread
executable
interaction. To find which functions use which
threads format a trace with print_trace Explanation: The custom server executable was
-Opid=on,tid=on,cpu=on not found in the required path.
Severity: Yellow User response: Re-install the custom server.

20020 • 20504
Severity: Yellow
20500 Custom server user-defined
Destination: Log, System Monitor log-only alarm
Explanation: The meaning of this error message
20020 Parameter conversion error is defined by the custom server programmer.
Explanation: A parameter received from a state User response: Depends on the custom server.
table cannot be converted to the format required
Severity: White
by the custom server. It may contain invalid
characters or it may be too long to fit the Destination: Log
receiving variable.
User response: Modify the state table to send 20501 Custom server user-defined white
data of the required type and range. It may be alarm
necessary to change the function definition in the
Explanation: The meaning of this error message
custom server.
is defined by the custom server programmer.
Severity: Yellow
User response: Depends on the custom server.
Severity: White
20021 Custom server AUTOEXEC
overridden on this SSI node
20502 Custom server user-defined green
Explanation: During WebSphere Voice Response
alarm
initialization, the custom server named in the
alarm parameters was not started. It has Explanation: The meaning of this error message
previously been set to be overridden on this is defined by the custom server programmer.
particular node in an SSI complex.
User response: Depends on the custom server.
User response: None. If the custom server
should be started on this SSI node, start the Severity: Green
custom server manually and use the DTcs Destination: Log, System Monitor
command to prevent this override taking place in
the future.
20503 Custom server user-defined
Severity: White yellow alarm
Destination: Log, System Monitor Explanation: The meaning of this error message
is defined by the custom server programmer.
20022 Problem with file User response: Depends on the custom server.
Explanation: WebSphere Voice Response has Severity: Yellow
encountered a problem with the file identified.
Details are in the parameters section. Destination: Log, System Monitor
User response: Examine the file and filesystem

with standard AIX commands such as ls. Pay 20504 Custom server user-defined red
particular attention to 1) access permissions 2) alarm
full filesystems Explanation: The meaning of this error message
Severity: Yellow is defined by the custom server programmer.
Destination: Log, System Monitor User response: Depends on the custom server.

20600 • 20603
Severity: Red
20600 SS7 component white alarm

Explanation: An SS7 component has raised an
alarm at the INFO level
User response: Depends on the alarm
Severity: White
20601 SS7 component green alarm

Explanation: An SS7 component has raised a
MINOR alarm
Severity: Green
20602 SS7 component yellow alarm

alarm at the MAJOR level
Severity: Yellow
20603 SS7 component red alarm

alarm at the CRITICAL level
Severity: Red

21001 • 21005
DTBE (Java and VoiceXML environment)

Contact IBM Support if you are attempting to
21001 DTBE initialization failure
use the Java and VoiceXML Environment and
Explanation: DTBEMGR failed to initialize with this error continues to occur.
Severity: Yellow
User response: Contact IBM Support if you are
attempting to use the Java and VoiceXML
Environment and this error continues to occur.
21004 DTBE Failed to start WebSphere
Severity: Yellow
Voice Response node.
Explanation: DTBEMGR failed to start the
Beans Environment.
21002 DTBE Failed to start Host
User response: Review any previous error
Manager
messages relating to DTBE. Check the beans
Explanation: DTBEMGR failed to start the environment is installed and configured correctly.
DTBE Host Manager Start the beans environment manually using
'dtjstart'
User response: Attempt to start the host
manager manually using "dtjstart". Verify that Severity: Yellow
the dirTalk.DTBE.common &
dirTalk.DTBE.VRnode filesets are installed.
Contact IBM Support if you are attempting to
use the Java and VoiceXML Environment and 21005 DTBE Failed to stop WebSphere
this error continues to occur. Voice Response node.
Severity: Yellow Explanation: DTBEMGR failed to stop the
Beans Environment.
User response: Review any previous error
messages relating to DTBE. Check the beans
21003 DTBE Failed to configure
environment is installed and configured correctly.
Environment
Stop the beans environment manually using
Explanation: DTBEMGR failed to configure the 'dtjstop'
Beans Environment to run default applications
Severity: Yellow
the first time it was run. The environment must
be configured manually. Destination: Log, System Monitor
User response: Verify that the
dirTalk.DTBE.common and dirTalk.DTBE.VRnode
filesets are installed. Then attempt to configure
the Beans Environment manually. This involves:
1. Verifying the pathnames specified in
$DTBE_HOME/dtj.ini
2. Creating a valid configuration file in
$DTJ_HOME/default.cff
3. Importing that configuration using dtjconf
4. Installing appropriate language packs using
dtjnlsin

23001 • 23009
SM_SRVR
see if it is there and complete.
Severity: Yellow
Explanation: Unexpected message received on
the server queue. Destination: Log, System Monitor
Support. 23007 sm_stat_send: invalid command
received
Severity: White
Explanation: A process has tried to send a
Destination: Log
message with an invalid command.
23002 Error accessing database
Severity: Yellow
Explanation: An error occurred performing a
DB2 operation. Destination: Log, System Monitor
User response: Examine the error log for
details. If the problem persists call IBM Support 23008 sm_stat_send: invalid message
and have the error log available. length
Severity: Red Explanation: A process has tried to send a
message with an invalid length.
23003 Error attaching queue Severity: Yellow
Explanation: Cannot attach server's queue. Destination: Log, System Monitor
23009 SMSERVER discarding statistics
Severity: Red
messages
Explanation: SMSERVER could not open one or
more vital files. As a result SMSERVER cannot
23004 Error allocating memory process any messages it receives from other parts
of the system and is discarding them. This means
Explanation: Cannot perform allocation.
that ALL statistics information is being
User response: Get more memory and/or disk discarded, and the functions in the Call
space. Information window will not function correctly.
The parameter below indicates how many
Severity: Red messages have been discarded since SMSERVER
Destination: Log, System Monitor, Alertable started. This message will be repeated
periodically as more messages are deleted. This
should not affect the operation of the rest of
23005 SM_SRVR: error retrieving WebSphere Voice Response.
environment variables
User response: Other errors in the WebSphere
Explanation: Cannot establish connection to Voice Response error logs will identify which
directories CUR_DIR or ARC_DIR which will files SMSERVER could not open. Correct these
contain log and archive data respectively. errors and restart WebSphere Voice Response. If
User response: Check "sw/environ/.profile" to the problem persists, call IBM Support.

Severity: Red

24001 • 24006
CTRL3270
24001 Session attach failed 24004 Session not enabled: already

enabled
Explanation: The 3270 controller was trying to
attach to a session to shut down the system, but Explanation: The 3270 controller received a
the attach was unsuccessful. request to enable a session that is already in the
READY state. This request is ignored.
User response: This problem is usually handled
by theWebSphere Voice Response initialization User response: If you need to recycle the
cleanup: active sessions are deactivated and LU session, it must be DISABLED before generating
pooling is halted. If WebSphere Voice Response an enable request.
exhibits further problems during initialization,
Severity: White
shut it down again and recycle the SNA
attachment using the SNA subsystem command Destination: Log
interface.
Severity: White 24005 Invalid emulator release request
Destination: Log, System Monitor Explanation: The 3270 controller received a
request to release an emulation session with an
invalid session identifier.
24002 Session detach failed
User response: If an emulator session is being
Explanation: The 3270 controller could not
closed, check that the session becomes available
detach from a session that it had previously
for use again. If not, disable the session using the
attached to. This occurs while trying to bring
3270 session management console and reactivate
down the system.
it. If the problem persists and the session cannot
User response: This problem is usually handled be recovered, you may need to wait until the
by theWebSphere Voice Response initialization next WebSphere Voice Response shutdown to
cleanup: active sessions are deactivated and LU recover the session.
pooling is halted. If WebSphere Voice Response
Severity: White
exhibits further problems during initialization,
shut it down again and recycle the SNA Destination: Log, System Monitor
attachment using the SNA subsystem command
interface.
24006 Session restart request could not
Severity: White be processed
Destination: Log, System Monitor Explanation: The 3270 management console or
the 3270 server screen capture emulator
requested that a session be restarted, but there
24003 Session not enabled: currently in
are no 3270 executor processes free to process the
use
request.
Explanation: The 3270 controller received a
User response: Try again when there is less
request to enable a session that is already
3270 traffic and 3270 executor processes are
allocated or in an incorrect state. This request is
available. It may be useful to increase the value
ignored.
of the system parameter "Number of 3270 exec
User response: None. processes to spawn" in the Application Server
Interface parameter group. Change this
Severity: White
parameter using the System Configuration utility.
Destination: Log
Severity: White

24007 • 24303
Destination: Log, System Monitor Severity: White

24007 System parameter information
could not be retrieved
24010 LU pooling command failed
Explanation: The 3270 controller could not
Explanation: An unexpected error occurred
determine whether 3270 support should be
while trying to issue an LU pooling command.
started on the system. As a result, no 3270
The state of 3270 operations is unpredictable
support is enabled.
following this.
User response: Check the WebSphere Voice
User response: Verify that there is at least one
Response system error log to determine the
3270 session configured and that the pooling
reason for the failure. If the problem persists
module (e32pool) is executable. You may need to
after a WebSphere Voice Response shutdown and
stop the system, manually disable pooling, and
restart, replace the system parameter database
restart the system.
with a backup version.
Severity: Yellow
Severity: Yellow
24301 Query host update command

24008 3270 support is not configured in
failed
this system
Explanation: While attempting to determine the
Explanation: The system configuration
status of a host session, the executor received an
information indicated that 3270 support is not
unexpected return code. Depending on the
required in this system. As a result, the 3270
severity of the error, the executor either
controller and sessions were not started.
recovered from the error or disabled the session.
User response: If the 3270 support is installed,
User response: Verify that the host link is up.
check that the installation process completed
successfully. This can be checked in the smit.log Severity: White
produced for the installation session (if the SMIT
tool was used). If no errors are detected, use the Destination: Log
RDSET3270 tool (enabled from an AIX command
line) to set the 3270 option to enabled. 24302 LU session release failed
Severity: White Explanation: A 3270 executor encountered an
Destination: Log, System Monitor unexpected error while releasing a previously
allocated session. The session may not be usable.
24009 3270 LU pooling could not be User response: This problem may have been
started caused by a transaction invoked by a running
3270 script. Check that the 3270 script running
Explanation: The 3270 controller could not start when this problem occurred is correct and that
the LU pool manager. As a result, 3270 support the host response time is good.
is not started.
Severity: Yellow
User response: If the 3270 executor did not
recover the session, it has been disabled. If the Destination: Log, System Monitor
session is still disabled after further recovery,
check the status of the LU connection at the host, 24303 LU session deactivation failed
and restart it if necessary.

24304 • 24399
Explanation: An error occurred while

24306 Fatal host error occurred
deactivating an LU in the system. The session is
disabled; WebSphere Voice Response will attempt Explanation: An error occurred while trying to
to recover the session later. execute a 3270 script. The host session is disabled
and the script is aborted. The 3270 controller will
User response: If the session is not recovered,
attempt to recover the session later.
check the status of the LU connection at the host
and check for any communication errors. If this User response: Check the cause of the problem.
error was generated by an emulation session If it occurs only when a particular script is
being released, it may indicate that the emulation executing, check that the script is correct. This
function is not working correctly. Try to re-create error can be caused by attempting invalid
the problem on another session to check for operations on a particular 3270 screen, or an
errors produced on the 3270 host machine or in invalid host response. The error parameters
theWebSphere Voice Response status window. should indicate the reason for the failure and
also give the name of the failing session. If the
Severity: Yellow
same session continues to report these errors
Destination: Log, System Monitor check the session status at the host and verify its
availability.
24304 Connecting to an LU session was Severity: Yellow

unsuccessful
Explanation: An unexpected error occurred
while trying to attach to an LU session to process
24307 Non-fatal host error occurred
requests. The session is disabled; recovery will be
tried later. Explanation: An error occurred while trying to
execute a 3270 script. The operation failed but
User response: If the session continues to cause
the script should continue to execute.
problems, check the WebSphere Voice Response
and system error log for possible causes. Also, User response: Check the cause of the problem.
check the availability and status of the LU at the If it occurs only when a particular script is
host and note any errors generated while executing, check that the script is performing
manually reenabling the session. functions correctly.
Severity: White Severity: Yellow
Destination: Log, System Monitor Destination: Log
24305 Disabling an LU session was 24398 User log information from 3270
unsuccessful language LOG_ERROR statement
Explanation: An unexpected error occurred Explanation: This record contains the
while deactivating an LU session, but the information passed as the argument to the 3270
operation may have completed successfully. The language LOG_ERROR call statement.
session is disabled andWebSphere Voice
User response: For information only; no action
Response will attempt recovery later.
required.
User response: If the session is not recovered,
Severity: White
check the status of the LU connection at the host
and check for any communications errors. Destination: Log, System Monitor
Severity: White
24399 Host session status information

24501 • 24506
Explanation: General status information for

24503 Internal stack underflow has
3270. This is generated in conjunction with other
occurred
host communication errors in the error log and
contains error codes reported by the 3270 Explanation: An internal error occurred while
executor at the time of the failure. It can be executing a script resulting in a stack underflow
ignored in all cases and is used to give more error.
specific information if the problem is reported to
User response: Verify that the 3270 script is
IBM Support.
valid, and retry the script.
User response: Check for other 3270 errors
Severity: Yellow
logged at the same time. These will give you
some indication of the reason for the failure. Destination: Log, System Monitor
Severity: White
24504 Internal stack overflow has
Destination: Log
occurred
Explanation: An internal error occurred while
24501 No free slots in local session table
executing a script. As a result of a stack overflow,
Explanation: A request was received by an the script is aborted.
executor to allocate one or more host sessions.
However, the executor does not have enough
valid, and retry the operation. If possible,
free entries in its internal tables to handle the
simplify the logic within the script.
request.
Severity: Yellow
User response: If the problem persists, it may
help to increase the value of the system Destination: Log, System Monitor
parameter "Number of 3270 Executor processes
to spawn". To change this parameter, click
Configuration...System Configuration... 24505 Invalid data used in arithmetic
Application Server Interface... from operation
theWebSphere Voice Response Welcome window. Explanation: The contents of the left operand of
Severity: White an arithmetic operation were not numeric. If an
exception handler is defined
Destination: Log, System Monitor (EX_MATH_ERROR), it is called. Otherwise, the
script aborts.
24502 Field information could not be User response: Correct the script, ensuring that
retrieved the variables used within arithmetic operations
contain only numeric data.
Explanation: An executor could not retrieve the
information on a field. If an exception handler is Severity: White
set up for this (EX_NO_FIELD), it is called. If
not, the script aborts. Destination: Log, System Monitor
User response: Verify that the field is defined,

and that the correct screen was displayed when 24506 Division by 0 (zero) attempted
trying to access the field. Explanation: The divisor in a division operation
Severity: White was 0, so the operation could not be performed.
If an exception handler is defined
Destination: Log, System Monitor (EX_MATH_ERROR), it is called. Otherwise, the
script aborts.

24507 • 24514
User response: Correct the script. User response: Verify that the 3270 script is
valid, and retry the operation.
Severity: White
Severity: Yellow
24507 Script attempted invalid
arithmetic operation 24511 Script attempted invalid jump
operation
executing a script. As a result, the script is Explanation: An internal error occurred while
aborted. executing a script. As a result, the script is
aborted.
valid, and retry the operation. User response: Verify that the 3270 script is
Severity: Yellow
Severity: Yellow
24508 Script attempted invalid
comparison operation 24512 Exception definition or handler
load failed
executing a script. As a result, the script is Explanation: An unexpected error occurred
aborted. while trying to retrieve an exception handler or
definition. If an exception handler exists for this
condition (EX_NO_SCRIPT), it is called.
Otherwise, the script aborts.
Severity: Yellow
User response: Verify that the 3270 script
Destination: Log, System Monitor referenced in the exception statement exists and
is valid.
24509 Script referred to invalid symbol Severity: White

identifier
executing a script. As a result, the script is
24513 Invalid state occurred following
aborted.
exception processing
Severity: Yellow aborted.
Destination: Log, System Monitor User response: Verify that the 3270 script is
24510 Script attempted invalid Severity: Yellow

evaluation operation
Explanation: An internal error occurred which
caused the script to try an invalid evaluation
24514 Invalid state occurred returning
operation.
from called script

24515 • 24702

24602 Script invoked with invalid
parameter type
aborted.
Explanation: An executor received a request to
execute a script, but the request contained
invalid parameter information. The parameter is
Severity: Yellow ignored, and the executor attempts to process the
request.
User response: Verify that the state table is
sending valid data when trying to use 3270
24515 Maximum exception retries services.
exceeded
Severity: Yellow
Explanation: An exception handler for a
user-defined exception returned the unsure or Destination: Log, System Monitor
retry code more times than the system allows, or
an exception handler for a system-defined
24603 Application allocation type
exception returned unsure or retry. In either case,
invalid
the script is aborted.
Explanation: An application was defined with
User response: If the exception was
an allocation type other than `by phone' or `first
user-defined, provide additional logic within the
available'.
handler to handle the unsure case (return 0 or 1
instead of 2). If the exception was system-defined User response: The database may be corrupt.
you must not return the unsure return code. Run recoverDMS.
Allowable values are 0 and 1. See the RETURN
Severity: Yellow
script language statement in the 3270 Servers
book. Destination: Log, System Monitor
Severity: White
24701 Pool_get operation failed
allocate a system buffer needed to communicate
24601 Invalid special command received
with a 3270 peeker session.
Explanation: An executor received a command
User response: Verify that the system has
that was invalid, or unexpected in the context it
enough buffers to perform any tasks necessary.
was received. The command is ignored. This
error is generated if the 3270 controller or Severity: Yellow
executor process is already processing a normal
command on a specific session, in which case Destination: Log, System Monitor
they will only acknowledge and process
particular special commands including enable, 24702 System parameter information
disable, quiesce, and abort script. The usual case retrieval failed
is trying to enable a session while the executor is
already processing an enable request. Explanation: An error occurred while trying to
load the 3270 configuration information. The
User response: None. 3270 controller and sessions are not started.
Severity: Yellow User response: Try to restart the system. If this
Destination: Log fails, verify that the system parameters are not
corrupt.

24703 • 24804
Severity: Yellow did not match the number that were contained in
the chain.
24703 Internal function (NotifyAppl) Severity: Yellow
failed
Destination: Log
trying to communicate with another process on
24801 Message receive system call failed
this system.
Explanation: An attempt to receive a message
User response: Check the status of system
from another process on this system was not
processes.
successful.
Severity: White
User response: If the message persists,
Destination: Log determine whether the message queue has been
removed, and if so, how.
24704 Poolput operation failed Severity: Yellow
Explanation: An attempt to release system Destination: Log
buffers failed. As a result, one or more system
buffers may be unusable by the system.
24802 LU pooling path lookup failed
User response: Monitor the buffer usage and
Explanation: The environment variable
check that the system still has enough buffers to
specifying the location for the LU pooling file
perform correctly. If the usage continues to
could not be retrieved.
increase, you may need to shutdown and restart
WebSphere Voice Response. User response: Verify that the environment
variable containing the path (E32DDIR) is set
Severity: Yellow
properly, and restart the system.
Destination: Log
Severity: Yellow
24705 Buffer chain contained incorrect
count information
24803 LU pooling table creation failed
Explanation: While processing a chain of
system buffers, the number of buffers that were Explanation: The 3270 controller could not
actually found in the chain did not match the create the file needed to store LU pool
count that was supposed to be there. information. As a result, no 3270 support is
installed.
User response: Verify that the pool path
Severity: Yellow
environment variable (E32DDIR) is set correctly,
Destination: Log and points to a valid, writeable directory. In
addition, verify that either no e32ptab file exists,
or that an existing one is writeable.
24706 Buffer chain contained incorrect
count information Severity: Yellow
Explanation: While releasing a chain of system Destination: Log, System Monitor
buffers, the number of buffers actually released
24804 Executor process fork failed

24901 • 24906
Explanation: The 3270 controller could not start servers and restart WebSphere Voice Response.
up the executors necessary to run. As a result,
Severity: White
the 3270 portion of the system is not functional.
User response: Try to restart the system. If that
fails, determine the reason for the failure.
24904 Specific application invalid
Severity: Yellow
Explanation: While trying to configure host
sessions, the 3270 controller was unable to locate
or retrieve the necessary information for the
24901 3270 controller shutting down session's application. As a result, the session is
not configured.
Explanation: The 3270 controller has received a
request to shut down, or an error occurred which User response: Verify that the application
caused it to exit. database is not corrupt, and that the application
exists.
Severity: White
Severity: White
Destination: Log
24905 Configuration of specified session

24902 3270 configuration information
failed
could not be retrieved
configure a host session. The failing host session
retrieve the session configuration information.
is not configured.
The operation will be retried.
User response: Verify that the session and
User response: Verify that the configuration
application exist, and that the parameters
database is not corrupted. You may need to
specified by the session table entry correspond to
recover the database and restart the system.
those expected by the application-specific scripts.
Severity: Yellow
Severity: White
24903 3270 table is full

24906 3270 configuration information
Explanation: The configuration database could not be retrieved
contained more session entries or more
concurrent 3270 servers than the maximum
retrieve a 3270 session or application
allowed by the 3270 services. As a result, any
configuration information from the host
extra sessions are not configured.
database.
User response: The maximum number of
User response: Verify that the database contains
sessions that can be configured is 255. If the
the necessary information, and that it is
number of configured sessions is greater than
accessible by the 3270 controller.
this, remove the excess sessions and restart
WebSphere Voice Response. The maximum Severity: White
number of 3270 servers that can be used
concurrently is 40. If the number of servers is
greater than this, then reconfigure to use less

24907 • 24912
not be detected even though WebSphere Voice

24907 Invalid screen identifier detected
Response 3270 support is installed. 3270 support
Explanation: An attempt was made to match a cannot be used until this is installed correctly.
screen with an invalid identifier to another
User response: Install the required level of SNA
screen. It has been rejected; please correct for
Server/6000 if 3270 emulation is required. If not,
later use.
run the command `RDSET3270 disabled' to
User response: Check that the field and screen deconfigure 3270 support.
specified in the error have constant data correctly
Severity: White
defined. In particular, check that the constant
data string for the field is not empty, or does not Destination: Log, System Monitor
contain invalid characters. If the constant data
information for a screen is lost, you may need to
recover the WebSphere Voice Response database 24911 SNA message catalog could not be
at the next system restart. opened
Severity: Yellow Explanation: The SNA NLS message files could

not be opened. Some text strings will not be
Destination: Log, System Monitor translated correctly, and 3270 support may not
operate correctly.
24908 SNA version information could User response: Check that the LOCALE of the
not be retrieved operating system is correct and that the system
language is set correctly so that WebSphere Voice
Explanation: The version of the SNA/6000
Response can access the correct NLS files. The
product could not be determined because of an
LOCALE can be found by issuing the command
unexpected error.
"locale" and looking for the LANG environment
User response: WebSphere Voice Response has variable. If this is correct, check that the SNA
tried to check if SNA Services/6000 or SNA message catalog files exist in the directory called
Server/6000 are installed. If one of these is /usr/lib/nls/msg/${LANG}. If the LANG
installed, check that the install is correct and environment variable is set to C, the default SNA
restart the system. message catalog directory (/usr/lib/nls/msg/
en_US) is used.
Severity: Yellow
Severity: Yellow
24909 SNA command could not be run
24912 SNA NLS message could not be
Explanation: An SNA command failed to start
retrieved
because of an unexpected error.
Explanation: A specific NLS string could not be
User response: Check that the command
loaded from the SNA NLS message catalog
information in the error entry is correct and that
although the catalog itself exists and has been
the WebSphere Voice Response environment is
opened correctly.
correctly configured.
User response: Check the error information for
Severity: Yellow
more detail. Check that the SNA message catalog
Destination: Log, System Monitor exists in the directory called
/usr/lib/nls/msg/${LANG}. Issue the command
"locale" on the command line to see the setting
24910 SNA/6000 software not detected for $LANG. If it is set to C, WebSphere Voice
Explanation: The SNA support software could Response uses the directory /usr/lib/nls/msg/

24913 • 24915
en_US. Also check that the SNA/6000 support relevant screen. To do this, from the 3270 Servers
has been correctly installed, and that the correct window, click Options->Define Unique Fields,
language files have been installed for the system and re-select the fields defined as unique (that is
LOCALE. those that are highlighted on the 3270 Field
Selection window), and re-save them by clicking
Severity: Yellow
OK. Take care not to change the definition when
Destination: Log, System Monitor you do this.
Severity: Yellow
24913 Call to malloc() failed in SNA
library
SNA library failed to allocate some memory.
User response: Check real and paged memory
usage for resource over-commitment.
Severity: Red
24914 SNA system status could not be

retrieved
to obtain SNA Server/6000 status. SNA may
have been inactive at the time of the query.
User response: Check the status of the SNA
subsystem and check the configuration to ensure
that the SNA Server is set to auto-respawn. If the
SNA Server/6000 is configured to start at system
restart and also respawn if ended, this ensures
that SNA is available forWebSphere Voice
Response operations. If the problem persists
check SNA Server/6000 operation for problems.
Severity: Red
24915 Unable to retrieve application

data from database
Explanation: During the execution of a script, a
request to obtain application data failed. The
application may not behave as expected.
User response: The error information tells you
which application object could not be retrieved.
Check that this object exists using the 3270
Development screens. If the object is a field, try
to save the definition of unique fields for the

25001 • 25008
OAM (Operations and Maintenance)

User response: None, ignore this message.
25001 OAM task initialization failure
Severity: White
Explanation: On startup, the Task_init call
failed. OAM will abort startup. Destination: Log
software install operation as described in the 25005 OAM test alert message for
Installation book to ensure that both hardware console
and software are installed correctly. If the
problem persists, call IBM Support. Explanation: This message is used for test
purposes only.
Severity: Yellow
Destination: Log
Severity: Red
25002 OAM attempt to attach queue Destination: Log, System Monitor, Alertable
failure
Explanation: OAM could not attach to shared 25006 OAM unknown requestor
memory queue. Start-up will abort. Explanation: OAM received a request from an
User response: Review the hardware and unexpected component of WebSphere Voice
software install operation as described in the Response. This can be associated with other
Installation book to ensure that both hardware errors occurring in WebSphere Voice Response.
and software are installed correctly. If the User response: Check for and correct other
problem persists, call IBM Support. errors, and if the problem persists, call IBM
Destination: Log Severity: Yellow

25003 OAM attempt to get VPACK
sysparms failure 25007 OAM cannot notify application
Explanation: OAM could not read system Explanation: OAM tried to send a notification
parameters with VPACK data. Start-up will to another process, but the message could not be
abort. sent.
User response: Ensure that the system User response: Check for dead processes (error
parameter file is accessible and is not corrupted. number 25032) and rectify associated problems, if
Retry the process. If the problem persists, call possible. If the problem persists, call IBM
IBM Support. Support.
Destination: Log Destination: Log, System Monitor
25004 OAM test message for log only 25008 OAM received unknown request
Explanation: This message is used for test Explanation: OAM received a request of an
purposes only. unknown type from another component of

25010 • 25018
User response: Check for and correct other Explanation: OAM received a request for
errors, and if the problem persists, call IBM periodic reports from another component of
Support. WebSphere Voice Response. The request contains
invalid timing values, and is ignored. Some
Severity: Yellow
System Monitor functions might not function
Destination: Log, System Monitor correctly.
25010 OAM received unknown Support.
notification
Severity: Yellow
Explanation: OAM received a notification of an
unknown type from another component of
25016 OAM cannot get buffer pool
User response: Check for and correct other
errors, and if the problem persists, call IBM Explanation: There might be no buffers left.
Support.
User response: Verify that buffers are available
Severity: Yellow and free them if possible. If necessary, increase
the number of pool buffers. If the problem
Severity: Yellow
25011 OAM received unknown message
type Destination: Log, System Monitor
Explanation: OAM received a message of an
unknown type from another component of 25017 OAM unknown channel status
Explanation: OAM has found a channel with a
User response: Check for and correct other status it does not recognize.
errors, and if the problem persists, call IBM
User response: Disable the channel and restart
Support.
it. If this does not clear the problem, disable and
Severity: Yellow re-enable the trunk. If the problem persists, call
IBM Support.
Severity: Yellow
25012 OAM message receive failed Destination: Log, System Monitor
Explanation: OAM message receive (msgrcv)
failed. èrrno' field indicates reason. Possibly the 25018 OAM unknown WebSphere Voice
OAM message queue has disappeared. Response status
User response: Stop and restart WebSphere Explanation: System run-time data shows
Voice Response. If the problem persists, call IBM unknown system state. This might be associated
Support. with other errors occurring in WebSphere Voice
Response.
Severity: Yellow
Support.
25015 OAM received invalid request for
Severity: Yellow
periodic report

25019 • 25026
Destination: Log, System Monitor could not complete the access.

User response: Make sure the indicated file has
25019 OAM exceeded maximum not been erased, has the correct permissions, and
processes test for `disk full' condition. If you cannot rectify
the problem and it persists, call IBM Support.
Explanation: There are more WebSphere Voice
Response processes, 3270 executors, or 3270 Severity: Yellow
sessions than OAM can handle. This can be due
to other errors occurring inWebSphere Voice
Response .
25023 OAM test message for OAM
recovery
Support. Explanation: This message is used for test
purposes only.
Severity: Yellow
Severity: White
25020 OAM unknown process status Destination: Log, System Monitor
Explanation: OAM has found a WebSphere
Voice Response process with operating status 25024 OAM received unsupported test
that it does not recognize. This can be due to request
other errors occurring in WebSphere Voice
Response. Explanation: This message is used for test
purposes only.
errors, and if the problem persists, call IBM User response: None, ignore this message.
Support. Severity: White
Severity: Yellow Destination: Log, System Monitor
25025 OAM test message for task
25021 OAM bad periodic action recovery
schedule Explanation: This message is used for test
Explanation: OAM tried to schedule an internal purposes only.
periodic action and the required interval was User response: None, ignore this message.
invalid. This can be due to other errors occurring
in WebSphere Voice Response. Severity: White
User response: Check for and correct other Destination: Log, System Monitor
Support. 25026 OAM library problem
Severity: Yellow Explanation: This is an internal OAM error. It
Destination: Log, System Monitor can be associated with other errors occurring in
25022 OAM problem with file access User response: Check for and correct other
Explanation: OAM tried to access a file, but Support.

25027 • 25034

25027 OAM pool buffer warning 25031 OAM test clear message for
message console
Explanation: More than 80% of the pool buffers Explanation: This message is used for test
are in use. The system will probably continue to purposes only.
operate normally.
User response: If this condition persists for
Severity: Green
considerable periods of time, the percentage of
buffers used approaches 100%, or other errors Destination: Log, System Monitor
indicate problems are occurring due to buffer
usage, consider increasing the number of pool
buffers. 25032 OAM process alert message
Severity: Yellow Explanation: A WebSphere Voice Response

process has stopped unexpectedly. If a channel
Destination: Log, System Monitor, Alertable process stops it should be restarted automatically,
but the call will be lost. Other processes are not
restarted and WebSphere Voice Response might
25028 OAM pool buffer alert message
no longer operate correctly.
Explanation: All the pool buffers are in use. See
User response: If other errors indicate a system
the error number 12004. Many system functions
malfunction, stop and restart WebSphere Voice
will fail.
User response: Reduce the call load on the Support.
system: it might be necessary to restart
Severity: Red
WebSphere Voice Response to clear the problem.
Investigate the reason for all buffers being used. Destination: Log, System Monitor, Alertable
If necessary increase the number of pool buffers.
Severity: Red 25033 OAM process clear message
Destination: Log, System Monitor, Alertable Explanation: The stopped process has been
restarted.
25029 OAM pool buffer clear message User response: None.
Explanation: Pool buffer usage has fallen below Severity: Green
80%. The system is no longer at risk.
Severity: Green 25034 OAM messages for console
overflow
Explanation: Too many alarms have been raised
in a short period of time; some have not been
25030 OAM test warning message
sent to the System Monitor. This is to protect
Explanation: This message is used for test WebSphere Voice Response from an excessive use
purposes only. of Pool Buffers if an alarm storm occurs. Alarms
will start being sent to the System Monitor again

25035 • 25041
after a few seconds, although if the alarm storm

25038 OAM file system warning
continues, this alarm will occur again.
Explanation: The usage of the WebSphere Voice
User response: Look in the error log for the
Response file system has exceeded the limit set
alarms that have not been passed to the System
in the System Disk Threshold system parameter.
Monitor. Try to correct error conditions that
cause alarms, especially if they cause storms of User response: You need to make space
alarms to occur. available. See the Managing and Monitoring the
System book for guidance on removing data you
Severity: Yellow
no longer need. If you are unable to resolve it,
Destination: Log, System Monitor reproduce the problem while running a system
trace and contact IBM Support. How to run a
system trace is described in the Problem
25035 OAM test warning message for Determination book.
console
Severity: Yellow
Explanation: This message is used for test
purposes only. Destination: Log, System Monitor, Alertable

25039 OAM file system alert
Severity: Green
Explanation: The usage of the WebSphere Voice
Destination: Log, System Monitor Response file system has exceeded 99%. If the
file system becomes 100% full, WebSphere Voice
25036 OAM received bad periodic action Response will malfunction.
request User response: Shut down WebSphere Voice
Explanation: OAM received a request for an Response and perform file maintenance in AIX.
action from another component of WebSphere See the Managing and Monitoring the System book
Voice Response. The request contains invalid for guidance on removing data you no longer
timing values, and is ignored. Some System need.
Monitor functions might not function correctly. Severity: Red
User response: If the problem persists, call IBM Destination: Log, System Monitor, Alertable
Support.
Severity: Yellow 25040 OAM file system clear
Destination: Log Explanation: The WebSphere Voice Response
file system usage has dropped below the limit set
25037 OAM received unknown report in the System Disk Threshold system parameter.
request The system is no longer at risk of running out of
disk space.
Explanation: OAM received a request of a
report of an unknown type from another User response: None.
component of WebSphere Voice Response. Severity: Green
User response: Check for and correct other Destination: Log, System Monitor
Support.
25041 OAM invalid data received
Severity: Yellow
Explanation: OAM received an invalid data
Destination: Log block from another WebSphere Voice Response

25043 • 25054
component. This can be due to other errors User response: If the problem persists, call IBM
occurring in WebSphere Voice Response. Support.
User response: Check for and correct other Severity: Yellow
Support.
Severity: Yellow
25048 OAM tried to read empty queue
Destination: Log
Explanation: OAM found its internal schedule
queue was unexpectedly empty.
25043 OAM problem executing database
cleanup
Support.
Explanation: OAM failed to run the AIX script
Severity: Yellow
oamscript using the AIX call system(). This script
is run periodically to compress the WebSphere Destination: Log
Voice Response database files. The files have not
been compressed.
25049 OAM unknown errparm handle
User response: If the problem persists, call IBM type
Support.
Explanation: OAM was sent an error for the
Severity: Yellow console with an unrecognized severity.
Destination: Log User response: If the problem persists, call IBM
Support.
25045 OAM process restart failed Severity: Yellow
Explanation: An attempt to restart a stopped Destination: Log
channel process failed.
User response: If the problem continues, call 25050 OAM unknown error report type
IBM Support.
Explanation: OAM was sent an error report of
Severity: Red an unknown type by another WebSphere Voice
Response component. This can be due to other
errors occurring inWebSphere Voice Response .
25046 OAM test for in task recovery
Explanation: This message is used for test Support.
purposes only.
Severity: Yellow
Destination: Log
Severity: White
Destination: Log, System Monitor 25054 OAM test: junk in string
parameter
25047 OAM schedule queue full Explanation: This message is used for test
purposes only.
Explanation: OAM tried to schedule an internal
action or report, but had insufficient room on its User response: None, ignore this message.
internal schedule queue.
Severity: Yellow

25055 • 25069

25061 OAM could not allocate memory
Explanation: OAM could not allocate memory
25055 OAM test: label/parameter
to check on WebSphere Voice Response
mismatch
processes. The system will continue to run, but
Explanation: This message is used for test this problem can indicate a serious problem.
purposes only.
User response: If the problem persists, shut
User response: None, ignore this message. down and restart WebSphere Voice Response. If
Severity: Yellow
Severity: Yellow
Destination: Log
25056 OAM test: chars sent to decimal
desc 25063 OAM failure in system parameter
database
purposes only. Explanation: Internal software error in system
parameter database.
Destination: Log
25057 OAM error reading sysparms
Explanation: OAM tried to read a system 25064 OAM error getting sysparms from
parameter. The system parameter file might be DBMS
corrupted.
Explanation: OAM tried to read a system
User response: If the problem persists try parameter. The system parameter file might be
restoring a backup copy of the file, and, if corrupted.
necessary call IBM Support.
User response: If the problem persists try
Severity: Yellow restoring a backup copy of the file, and, if
Destination: Log, System Monitor necessary call IBM Support.
Severity: Yellow
25060 OAM ODM error Destination: Log
Explanation: OAM encountered an error
accessing the ODM database. The error message 25068 OAM test: sample SW alert test
indicates which ODM call failed, and the errno
value shown is the odmerrno value returned by Explanation: This message is used for test
the call. purposes only.
User response: If you cannot correct the User response: None, ignore this message.
problem and it persists, call IBM Support.
Severity: Red
Severity: Yellow
Destination: Log
25069 OAM test: sample HW alert test

25070 • 25077
Explanation: This message is used for test Explanation: The CPU idle time has fallen
purposes only. below the warning level, set by the CPU
Warning Threshold system parameter.
User response: Identify activities that might be
Severity: Red
needlessly consuming CPU time and stop them.
Destination: Log, System Monitor, Alertable If this condition persists, we recommend
quiescing traffic.
25070 OAM could not retrieve NetView Severity: Yellow

sysparm
Explanation: OAM could not retrieve either or
both of the NetView Installed or NetView Send
25075 OAM CPU usage alert cleared
ALL Errors system parameters. No errors will be
logged in the AIX error log to be sent to Explanation: The CPU idle time has risen above
NetView. the clear level, set by the CPU clear system
parameter.
Support. User response: Start putting quiesced channels
back into service, and, at the same time, monitor
Severity: Yellow
CPU idle time.
Destination: Log
Severity: Green
25071 OAM invalid pointer to memory
Explanation: OAM could not get a pointer to
25076 OAM error getting list of LU
AIX resources that it requires. This will happen if
connection info
the OAM executable is not owned by root.
Explanation: See the message for details. It
User response: Check the owner of OAM and
could be an ODM problem, in which case èrrno'
OAMEXEC. If the owner is not root, try setting it
is odmerrno.
to root or restoring the files from a backup.
Severity: Yellow
Severity: Yellow
Destination: Log
25072 OAM corrupt buffer
25077 OAM invalid request for session
Explanation: An unallocated pool buffer has
been corrupted. This can be due to other errors Explanation: OAM received an invalid 3270
occurring inWebSphere Voice Response . session control request from another WebSphere
Voice Response component. This can be due to
other errors occurring inWebSphere Voice
Response .
Support.
Severity: Red
Destination: Log, System Monitor, Alertable Support.
Severity: Yellow
25073 OAM CPU usage warning
Destination: Log

25079 • 25092
Explanation: The SNA attachment is not

25079 OAM invalid session status
responding and is assumed to be disconnected or
Explanation: OAM has found a 3270 session otherwise inactive.
with a status it does not recognize. This can be
User response: Contact your SNA administrator.
due to other errors occurring in WebSphere Voice
If the SNA attachment is active and WebSphere
Response.
Voice Response does not recognize it, call IBM
User response: Check for and correct other Support.
Severity: Red
Support.
Severity: Yellow
Destination: Log
25089 SNA attachment active
Explanation: The SNA attachment is now
25080 OAM invalid executor status
responding.
Explanation: OAM has found an executor with
a status it does not recognize. This can be due to
other errors occurring in WebSphere Voice Severity: Green
Response.
Support. 25090 OAM test informative message for
console
Severity: Yellow
Destination: Log purposes only.
25081 OAM semaphore error
Severity: White
Explanation: OAM could not get a valid status
on a semaphore. Destination: Log, System Monitor

Support. 25091 OAM test run-time parameters go
to console
Severity: Yellow
Destination: ** ERROR ** No destination purposes only.
defined
25082 OAM test codepoint error Severity: White
Explanation: This message is used for test Destination: Log, System Monitor
purposes only.
User response: None, ignore this message. 25092 OAM has detected that CHP has
died
Severity: Green
Explanation: OAM has detected a channel
Destination: Log, System Monitor process that died during a call, but it has been
unable to find the associated call record. The
statistics for this call will not be logged.
25088 SNA attachment inactive

25093 • 25102
User response: If the problem persists, call IBM Severity: Yellow

Support.
Destination: Log
Severity: Yellow
Destination: Log 25097 OAM test message with both
strings and decimals on the
console
25093 Bad return code (vp_open_vpack)
Explanation: OAM received a bad return code
purposes only.
from vp_open_vpack.
Support. Severity: White
Destination: Log
25099 OAM test message AIXLOG clear
25094 Bad return code Explanation: This message is used for test
(vp_get_lost_call_recs) purposes only.
Explanation: OAM received a bad return code User response: None, ignore this message.
from vp_get_lost_call_recs.
Severity: Green
Destination: Log, Alertable
Support.
Severity: Yellow
25100 OAM test message AIXLOG alert
Destination: Log
purposes only.
25095 Bad return code (vp_close_vpack)
Explanation: OAM received a bad return code
Severity: Red
from vp_close_vpack.
Destination: Log, Alertable
Support.
25101 OAM adapter has changed
Severity: Yellow
Explanation: Notification that a digital trunk
Destination: Log
adapter or digital trunk dual adapter is different
from the last time the system was used.
25096 Unassociated call record
User response: Investigate if you are not aware
Explanation: OAM received a call record, which of any changes having been made.
it retrieved using vp_get_lost_call_recs, but it has
Severity: White
determined that there is no associated channel
process. It is therefore an orphan and will be Destination: Log, System Monitor
purged. This could be an internal channel
process or OAM process error.
25102 OAM pack has changed
Support. Explanation: Notification that a pack type has
changed since last time the system was used.

25103 • 25200
User response: Investigate if you are not aware

25107 OAM time out on automatic
of any changes having been made.
enabling of trunks
Severity: White
Explanation: System configuration parameters
Destination: Log, System Monitor specify that one or more trunks should be
enabled automatically after WebSphere Voice
Response starts. The necessary preconditions
25103 OAM bad return code from ioctl: were not satisfied within the time specified in the
speech recognition statistics Trunk Initialization Timeout parameter. The error
Explanation: A request for speech recognition message indicates the precondition that was not
statistics has failed. satisfied. These are: 1. If 3270 support is installed,
and at least one session is configured, the 3270
User response: Look at the error log for more server must be ready. 2. If the trunk is
information, such as the value of errno. If the configured to use one or more signalling
problem persists and you are unable to correct it, processes, the signalling processes must be ready.
call IBM Support. 3. If this trunk uses common channel signalling
Severity: Yellow from another trunk (for example, ISDN NFAS),
that trunk must be enabled. Other error
Destination: Log messages can identify a problem with those
subsystems.
25104 OAM bad return code from User response: Check that there is no problem
malloc: speech recognition with 3270 servers or signalling processes. Both
statistics these must be ready for use before VPACKs and
Explanation: Internal storage for speech SPACKs can be initialized. If the problem
recognition statistics might be unavailable. concerns 3270 server, and you do not require
Statistics will not be collected. 3270, disable the 3270 interlock using the Trunk
Initialization Interlock - 3270 Server system
User response: Take action to free storage. For parameter. Likewise, you can disable the DTBE
example, close as many WebSphere Voice interlock using the Trunk Interlock - DTBE
Response windows as you can. If the problem Environment system parameter. If you cannot
persists, call IBM Support. find anything wrong, increase the value of the
Trunk Initialization Timeout parameter.
Severity: Yellow
Severity: Red
Destination: Log
25106 OAM bad return code from
Notify_appl sending speech 25200 Underrun margin time less than
recognition stats defined threshold value
Explanation: OAM could not send statistics Explanation: While playing voice data with
data. PlayPrompt, PlayAudioName, PlayGreeting,
PlayVoiceMessage, or PlayVoiceSegment, the
User response: Check that the SMSERVER
device driver was close to running out of voice
process is running, by issuing ps -def grep |
data to play. The accepted threshold value is
SMSERVER from the AIX prompt.
defined by the system parameters in "Application
Severity: Yellow Server Interface". If the device driver runs out of
voice data to play, the system continues to play
Destination: Log
voice data when more is available, but the caller
hears a pause in the voice. Note: This report is

25201 • 25205
based on an average calculated every minute.

25203 Play latency time has returned to
User response: This is probably caused by the normal
voice input buffer to the device driver being too
Explanation: This clears the performance
small, and is most likely to happen when the
degradation reported by an earlier error 25202.
system is heavily loaded. Increase the size of the
buffer using the Normal Play/Record Max Data User response: No response is required. The
system parameter. system is working normally.
Severity: Yellow Severity: Green
25201 Underrun margin time has 25204 Profile retrieval time greater than
returned to normal defined threshold value
Explanation: This clears the performance Explanation: While retrieving application
degradation reported by an earlier error 25200. profile information, for example while answering
a call or gathering mailbox information, the time
User response: No response is required. The
taken to retrieve profile data from the database
system is working normally.
became greater than the defined threshold
Severity: Green defined by the system parameters in "Application
Server Interface". This equates to potentially
Destination: Log, System Monitor, Alertable increased periods of silence being heard by the
caller leading to a decreased quality of service.
25202 Play latency time greater than Note: This report is based on an average
defined threshold value calculated every minute.
Explanation: While playing voice data with User response: Check for excessive disk, CPU,
PlayPrompt, PlayAudioName, PlayGreeting, or network load which cause delays in retrieving
PlayVoiceMessage, or PlayVoiceSegment, the voice data from local disk or a remote SSI server.
delay between voice being requested by the If using a remote SSI server also check for
application, and the voice actually being played, excessive load on the server and examine NFS
became greater than the defined threshold performance.
defined by the system parameters in "Application Severity: Yellow
Server Interface". This equates to an increased
period of silence being heard by the caller Destination: Log, System Monitor, Alertable
leading to a decreased quality of service. Note:
This report is based on an average calculated
25205 Profile retrieval time has returned
every minute.
to normal
or network load, which cause delays in retrieving
If using a remote SSI server also check for User response: No response is required. The
excessive load on the server and examine NFS system is working normally.
performance.
Severity: Green
Severity: Yellow

25206 • 25207
25206 Time to check voice messages

greater than defined threshold
value
Explanation: The time taken to retrieve voice
messaging information for a subscriber when
using the Check Voice Messages state table action
became greater than the defined threshold
defined by the system parameters in "Application
Server Interface". This equates to potentially
increased periods of silence being heard by the
caller leading to a decreased quality of service.
Note: This report is based on an average
calculated every minute.
or network load which cause delays in retrieving
If using a remote SSI server also check for
excessive load on the server and examine NFS
performance.
Severity: Yellow
25207 Time to check voice messages has

returned to normal
User response: No response is required. The
system is working normally.
Severity: Green

26001 • 26008
SNMP (Simple Network Management Protocol)

Explanation: There may be a problem with a
26001 SNMP smux error
particular data item, which is a tree leaf of the
Explanation: The WebSphere Voice Response WebSphere Voice Response sub-tree.
SNMP sub-agent is having difficulty
User response: Examine the contents of the file
synchronizing with the AIX SNMP agent. The
and ensure that it is complete and in the correct
particular reason for this will be in the message.
format.
User response: Attempt to solve this problem
Severity: White
using information in the message. If you can`t
solve the problem, call IBM Support. Destination: Log, System Monitor, Alertable
Severity: Red
26005 SNMP object entry not found
sub-agent is not properly registered.
26002 SNMP read objects error
User response: Examine two files:
/etc/snmpd.conf and snmpd.peers.
failed to read a file. The file is either corrupt or
does not exist. Severity: Red
User response: Ensure that the file etc/mib.defs Destination: Log, System Monitor, Alertable
exists and examine its contents.
Severity: Red 26006 SNMP smux registration error
Destination: Log, System Monitor, Alertable Explanation: There is a problem with the data
passing between the WebSphere Voice Response
sub-agent and the snmpd agent.
26003 SNMP agent text20bj error
User response: Look at the SNMPD agent log
Explanation: WebSphere Voice Response cannot
file to help determine what went wrong. If this is
interpret the contents of the file. The format of
unsuccessful, contact IBM Support.
the file may be inconsistent or incomplete. There
may be a problem with the WebSphere Voice Severity: Red
Response sub-tree. If you have upgraded your
version of AIX, the error can also be caused by Destination: Log, System Monitor, Alertable
the MIB definitions reverting to the AIX default
values. 26007 Smux PDU close error
User response: Examine the contents of the file Explanation: The agent has chosen to close
and ensure that it is complete and in the correct connections with the sub-agent.
format. If the problem has been caused by an
AIX upgrade, run the command DTsnmpd.cfg, to User response: Look at the snmpd agent log file
reinstall the WebSphere Voice Response to help determine why this happened. If this is
definitions. unsuccessful, contact IBM Support.
26004 SNMP object text20bj error 26008 SNMP unsupported operation

error

26010 • 26013
Explanation: WebSphere Voice Response has User response: Check SS7 installation and retry.
received an smux request that it does not If the problem persists, call IBM Support.
support.
Severity: Red
User response: If the problem persists contact
IBM Support.
Severity: White
26010 SNMP message queue attachment

error
Explanation: The sub-agent cannot synchronize
with WebSphere Voice Response.
User response: Ensure that WebSphere Voice
Response is running normally or is not running.
Severity: Red
26011 SNMP failed access to system

parameters
Explanation: There is data corruption in the
WebSphere Voice Response system parameters.
Severity: Red
26012 SNMP failed attach to 3270 shared

memory
Explanation: Not coded
Severity: Red
26013 SNMP failed initializing SS7

sub-agent could not determine whether the SS7
option is installed, or could not initialize a
connection to the WebSphere Voice Response
MTP subsystem. Other functions of the sub-agent
will continue to work.

27001 • 27010
SDI (Signaling Device Driver Interface)

check the errno value against those in
27001 An error occurred which should
/usr/include/sys/errno.h.
not happen
Severity: Yellow
Explanation: This is probably a software bug.
User response: Note the routine field and call
IBM Support. This is an error that only
minimally affects the running of SDI. It may be 27006 SDI failed to configure device
useful to check the errno value against those in
/usr/include/sys/errno.h. Explanation: SDI failed to make a device
available for use. The pack cannot be used.
Severity: White
User response: Check that the trunk listed is the
Destination: Log one you expect to use. If not, check the initial
states of all your packs using Pack Configuration
or System Configuration. You may find that the
27003 SDI message queue has
initial state of a pack that is not connected is set
disappeared
to ENABLED or INSERVICE, causing the error. If
Explanation: The message queue has gone it is, check that the hardware is connected
away. SDI will terminate. correctly and powered on. Check the cables. It
may be useful to check the errno value against
User response: Get $OAM_LOG_PATH/
those in /usr/include/sys/errno.h. Restart the
errorlog, and the output from `ps -efl' and ìpcs
AIX system. If the problem persists, call IBM
-a' and call IBM Support. It may be useful to
Support.
check the errno value against those in
/usr/include/sys/errno.h. Severity: Yellow
Destination: Log
27007 SDI received message with
incorrect format
27004 System reached the maximum
number of processes or is out of Explanation: Another process sent SDI a
memory message in an incorrect format. There may be a
problem with the other process or with shared
Explanation: (1) SDI needs to create a new
memory. SDI ignores the message.
process to quiesce a pack or channel, but the
system-imposed limit on the number of processes User response: Check the `sending process' field
has already been reached. (2) SDI needs to to determine the process problem. If the problem
execute a program but the system is out of persists, call IBM Support.
memory.
Severity: Yellow
User response: (1) Stop any processes that are
Destination: Log
not needed, by having people log off the system
or by using the kill command. (2) Free memory
by doing system maintenance. In either case, 27010 Pack enablement failed
increase max user processes with chdev -1 sys0
-a maxuproc='nnn' where nnn is the number you Explanation: SDI received an error from ioctl
require. The current value can be obtained with call to enable the pack. This may be caused by
`lsattr -E lsys0'. You need to be logged on as root invalid parameters for the pack. The reason for
to perform this operation. It may be useful to the failure is given in the Ìnformation' field.

27011 • 27015
Sometimes after pack configuring a partial CAS òdmerrno' field, check /usr/include/odmi.h to
protocol trunk (a T1 trunk with less than 24 identify the particular error. Consult the ODM
channels or E1 trunk with less than 30 channels) documentation for more information.
the red alarm 27010 (Pack enablement failed)
Severity: Yellow
occurs when WebSphere Voice Response is
started and the trunk enabled. Whole trunks on Destination: Log, System Monitor
the same system can be enabled without this
error.
27012 SDI failed to quiesce a trunk or
First time through, not all channels of a partially channel
configured trunk are initializd properly. Unused
channels (those not included in the partial trunk Explanation: SDI failed to quiesce a trunk or
channel group configuration) can give rise to a channel. Some of the quiesce processing may
27010 error (Pack enablement failed / channel have already completed but not all operations
group is not initialized for channel). This device succeeded. The trunk or channel will be disabled.
driver error occurs because of the need to User response: Check for any other errors. If
initialize all channels in a trunk for signalling there are none and the error persists call IBM
even though all are not included in the channel Support.
group.
Severity: Yellow
User response: Check the settings of parameters
in the Trunk Interface, Signalling Type, and Destination: Log, System Monitor
Channel Group parameter groups for this pack.
It may be useful to check the errno value against 27013 SDI failed to configure a channel
those in /usr/include/sys/errno.h. If the group
information field says that files are missing,
corrupt, or cannot be opened, check that the files Explanation: SDI received a failure indication
exist and that read permissions are set. when issuing an ioctl to configure a channel
group.
To avoid the partially configured trunk problem:
User response: The parameter information lists
1. Reconfigure the trunk (Configuration -> Pack
the parameter at fault. Verify the configuration,
Configuration -> Change) to include ALL
using Pack Configuration or System
channels of the trunk in the channel group.
Configuration.
2. Save the configuration and shut down
WebSphere Voice Response (DT_shutdown). Severity: Yellow
3. Restart WebSphere Voice Response and Destination: Log, System Monitor
change the pack configuration back to the
desired partial trunk configuration. On restart
the 27010 error should now be avoided since 27014 SDI received alarm from device
the unused channels of the partial trunk are driver
correctly initialized. Explanation: SDI received a non-specific alarm
Severity: Red from the device driver.
Destination: Log, System Monitor User response: Ignore this message unless it
occurs repeatedly.
27011 SDI: ODM error Severity: Yellow
Explanation: SDI encountered an error when Destination: Log, System Monitor

dealing with ODM.
User response: Using the number in the 27015 SDI ioctl failed

27016 • 27022
Explanation: SDI received a failure indication be useful to check the errno value against those
from a device driver ioctl request. In some cases, in /usr/include/sys/errno.h.
this may adversely affect the functioning of the
Severity: Yellow
system. This error may be caused if there is
currently an ALARM situation on the telephony Destination: Log, System Monitor
line.
User response: Ignore this message unless there 27020 SDI failed to access system
are other problems with the system. Disable and parameters
re-enable the trunk and ensure that all errors
have cleared before attempting to make the Explanation: SDI tried to look up a
channels available for use. It may be useful to configuration parameter in the database but was
check the errno value against those in unable to access it. This may be caused by a back
/usr/include/sys/errno.h. If the problem level or corrupted database.
persists, note all details of the error and call IBM User response: SDI can probably continue,
Support. using default values, so if the system is
Severity: White functioning normally, ignore this message. You
should have the $SYSPARM_DIR/rd.data binary
Destination: Log, System Monitor data file available if you call IBM Support.
Severity: Yellow
Explanation: The diagnostics were not
successfully completed (abort condition). This
was probably caused by a hardware problem. 27021 SDI failed to make signalling
library call
details. Explanation: SDI tried to send a request to a
configured signalling process but the request
Severity: Red failed. This may be either because the process
has not been started or because it has crashed.
Check the `rc' field against $VAE/db/
current_dir/ca/include/slcommon.h.
User response: Check that any signalling
Explanation: A software malfunction has processes in use are started and that no core files
occurred while diagnostics were running. are found in $VAEBIN. You should also check
that the correct signalling process is configured
by using System Configuration on the
details, and call IBM Support.
Configuration menu to check the value of the
Severity: Red Signalling Process Type parameter in the
Channel Group parameters group. It may be
Destination: Log, System Monitor, Alertable useful to check the errno value against those in
/usr/include/sys/errno.h.
27019 SDI failed to open pack Severity: Yellow
Explanation: SDI received a negative return Destination: Log, System Monitor
code while attempting to open a pack.
User response: Check that the hardware is 27022 SDI cannot load system
connected correctly and powered on. Check the parameters
cables. If this fails, restart the AIX system. It may

27025 • 27035
Explanation: The configuration database could User response: Check the settings of parameters
not be loaded. in the Trunk Interface, Signalling Type, and
Channel Group parameters groups for this pack.
User response: Check that $SYSPARM_DIR/
rd.data is present and read/write by your Severity: Yellow
WebSphere Voice Response userid AND root
userid. Check that neither System Configuration
nor Pack Configuration windows are open, and
that the ASCII console (AC) is not being used. 27033 SDI re-enable notification
Retry the operation that failed. If it fails again,
restartWebSphere Voice Response . If the problem Explanation: SDI has scheduled a re-enable
persists, call IBM Support. request for this pack. An unrecoverable error had
previously been detected, which required the
Severity: Yellow pack to be disabled. The pack will shortly return
to service. Should the re-enable fail it will be
retried the number of times specified by the
"Maximum Retries for Pack/Adapter Reenabling"
27025 SDI could not notify CHPM parameter in the General parameter group in
System Configuration, with progressively
Explanation: SDI could not notify CHPM that a
increasing time delays between each attempt.
trunk had been put into service or taken out of
service. User response: Check that the pack is
re-enabled. If the pack correctly returns to service
the problem was probably temporary and can be
Response. Check for channel process (CHP or
ignored unless it occurs repeatedly. If the pack
CHPM) failures. If the problem persists, call IBM
continues to be enabled and disabled, manually
Support.
remove the pack from service and run
Severity: Yellow diagnostics on it when convenient. Check also
that all cables are firmly in place, that the pack is
Destination: Log, System Monitor securely fitted in the 9295 (if relevant), and that
all the adapters in the pSeries computer are
27026 SDI failed to unconfigure device correctly seated.
Explanation: SDI failed to unconfigure a device Severity: White

in response to a PACK Remove request. Destination: Log, System Monitor
User response: Ignore this message unless you
are changing the hardware or upgrading 27035 SDI message queue problem
theWebSphere Voice Response software. If so,
ensure that you restart the AIX system before Explanation: SDI has experienced problems
starting WebSphere Voice Response. It may be trying to read data from an AIX message queue.
useful to check the errno value against those in The errno field gives a more precise indication of
/usr/include/sys/errno.h. the exact problem. SDI may have terminated in
response to this error; if so, control of telephony
Severity: White will be lost.
Destination: Log, System Monitor User response: Consult /usr/include/sys/
errno.h. Restart WebSphere Voice Response. If
27032 SDI found invalid telephony the problem persists restart the AIX system.
parameter Severity: Yellow
Explanation: The parameter listed below is Destination: Log, System Monitor
outside the valid range.

27036 • 27041
made available, nor can any channel operations

27036 Bad parameter on signalling
be performed until the pack is in service. Retry
library request sent from SDI
the operation when the prerequisite actions are
Explanation: The parameter indicated was complete. The relevant requests and states are
about to be passed from SDI to a signalling shown below the message. If you can`t resolve
process. However the parameter failed the problem, reproduce it while running a
validation. system trace as documented in the Problem
Determination book, ("trace -a -1" to start; "trcstop
-1" to stop) and contact IBM Support.
Severity: Yellow
Severity: White
27037 Invalid common channel

27039 SDI received request that cannot
signalling trunk configuration
be accepted because SDI is busy
Explanation: The request to enable a pack has
Explanation: A request was received to perform
failed because of a configuration error. SDI has
a request that conflicts with a request that SDI
detected that the pack has channels that are
previously received and is still working on, for
defined to use more than one type of signalling
instance, attempting to enable a pack while
process. If a trunk is defined to use a common
diagnostics is still running. The request may be
channel signalling protocol, all channels on that
tried again at a later time.
trunk must be in channel groups that use the
same Signalling Process Type. User response: Retry the operation when the
current action is complete.
User response: Check the setting of the
Signalling Process Type parameter for the Severity: White
Channel Group. If it is correct, check the settings
of the Channel Group parameter for all the
channels on the trunk to ensure that they are all
in the same group. The Signalling Process Type 27040 SDI received unsupported request
must be the same for each channel, but the
channels do not have to be in the same group. Explanation: An obsolete request was received
by SDI. This is a programming error.
Severity: Yellow
User response: You may safely ignore this error.
Severity: White
27038 SDI received invalid request Destination: Log, System Monitor
Explanation: A request has been received by the

SDI process to perform an action, usually on a 27041 SDI received unreasonable
channel or trunk. This request was not valid, for request
one of the following reasons: - The request is not Explanation: A pack-related request was
a valid type - The pack number or channel received for a channel, a channel-related request
number is out of range - The pack is not in the was received for a pack, or a request that
correct state for the action to occur - The channel contained corrupted parameters was received.
is not in the correct state for the action to occur The request will be ignored. This is a
User response: Check that all prerequisite programming error.
actions are complete. For example, a pack cannot User response: Restart WebSphere Voice
be placed in service until the pack has been Response and repeat the operation. If you can`t

27042 • 27048
resolve the problem, please reproduce whilst

27046 SDI failed to enable pack because
running a system trace as documented in the
signalling process was missing
Problem Determination book ("trace -a -1" to start;
"trcstop -1" to stop), and contact IBM Support. Explanation: The signalling process specified in
the parameters was not active when an attempt
Severity: White
to enable a pack using that signalling process
Destination: Log, System Monitor was attempted.
User response: Check that all signalling
27042 SDI was asked to log this request processes required for your configuration are
active and also that the Signalling Process Type
Explanation: A request was received and SDI parameter in the Channel Group definition is
was asked to log it. correct. This message is repeated for each
User response: None. missing signalling process type. If you are using
an Exchange Data Link Signalling process to
Severity: White gather additional call information, you might
Destination: Log, System Monitor want to allow the trunk enable if the signalling
process is missing, and to default to a different
application profile. If so, change the setting of
27043 Signalling process reconfiguration "Trunk Interlock - EDL" parameter (in the Trunk
problem Interface Group) to DISABLED. The trunk will
Explanation: A signalling process was sent a then be enabled.
request to reconfigure, because its configuration Severity: Red
information may have changed. WebSphere Voice
Response did not receive a successful reply, Destination: Log, System Monitor, Alertable
either because there were problems delivering
the request, or because the signalling process 27047 SDI: pack type changed while
failed the request, which is not valid behavior. WebSphere Voice Response was
User response: Check that signalling process running
configuration is correct and that all signalling Explanation: When an attempt was made to
processes are running. configure the pack indicated in the trunk
Severity: Yellow parameter, SDI found that the pack type was
different from found previously. You cannot
Destination: Log, System Monitor, Alertable change pack types (VPACK and SPACK) while
WebSphere Voice Response is running. The pack
27044 Signalling library message: has not been made available for use.
sequence number not expected User response: You must either replace the
Explanation: SDI received an unexpected original pack and try the operation again, or
message from the signalling library. The restartWebSphere Voice Response with the new
sequence number of the message did not match pack.
any request that had been made. Severity: Red
User response: Try again to enable the pack. If Destination: Log, System Monitor, Alertable
this fails restart WebSphere Voice Response.
Severity: Yellow 27048 SDI timed out on pack
Destination: Log, System Monitor, Alertable diagnostics
Explanation: SDI issued a request for pack
diagnostics. A reply was not received within the

27049 • 27053
timeout period. The pack will not be placed in This action did not complete within the timeout
service. period. Check for errors relating to the disabling
of channels. The pack will be taken out of
User response: Check for core files in $VAEBIN.
service, but some errors may be logged and the
Try to enable the trunk. If this fails, restart
signalling processes may malfunction.
WebSphere Voice Response. If this still fails,
restart the AIX system. User response: Review the error log and check
the signalling process configuration.
Severity: Red
Severity: Yellow
27049 SDI timed out on resetting voice
recognition statistics 27052 SDI timed out while enabling a
channel
Explanation: SDI issued a request to OAM for
the statistics to be reset. A reply was not received Explanation: SDI sent a request to the
within the timeout period. The pack will not be appropriate signalling process for this channel to
placed in service. enable the channel. This action did not complete
within the timeout period. The channel will not
User response: Try to enable the trunk. If this
be made available for use.
fails, restart WebSphere Voice Response. If this
still fails, restart the AIX system. User response: Check your signalling process
configuration and, if you are writing a signalling
Severity: Yellow
process, check that you correctly send an
Destination: Log, System Monitor, Alertable SL_CHANNEL_ENABLE_CNF in response to an
SL_CHANNEL_ENABLE_REQ. The operation
can be repeated.
27050 SDI timed out on trunk
reconfigure request to signalling Severity: Yellow
process
Explanation: SDI issued a request to all
registered signalling processes informing them
27053 SDI timed out while disabling a
that their configuration might have changed. Not
channel
all replies were received within the timeout
period. Explanation: SDI sent a request to the
appropriate signalling process for this channel to
User response: You should check your
disable the channel. This action did not complete
signalling process configuration, and if you are
within the timeout period. The channel will be
writing a signalling process check that you
disabled, but this can cause the signalling
correctly send an
process to malfunction.
SL_TRUNK_RECONFIG_CONFIRM in response
to SL_TRUNK_RECONFIG_REQUEST. User response: Check your signalling process
configuration. When writing a signalling process
Severity: Yellow
check that you correctly send an
Destination: Log, System Monitor, Alertable SL_CHANNEL_DISABLE_CNF in response to an
SL_CHANNEL_DISABLE_REQ.
27051 SDI timed out while disabling a Severity: Yellow

pack
Explanation: SDI requested that all channels be
placed out of service before disabling the pack.

27054 • 27058
27054 SDI timed out while disabling a 27056 SDI timed out on trunk enable
channel request to signalling process
Explanation: SDI sent a request to the Explanation: SDI issued a request to the
appropriate signalling process for this channel to signalling process controlling this trunk to
disable the channel before it is taken out of prepare the trunk for use. A reply was not
service. This action did not complete within the received within the timeout period. The pack
timeout period. The channel will be taken out of will not be placed in service.
service, but this can cause the signalling the
User response: Check your signalling process
process to malfunction.
configuration. When writing a signalling process,
User response: Check your signalling process see “Channel and trunk management primitives”
configuration. When writing a signalling process in the Programming for the Signalling Interface
check that you correctly send an book.
SL_CHANNEL_DISABLE_CNF in response to an
Severity: Red
SL_CHANNEL_DISABLE_REQ.
Severity: Yellow
27057 SDI timed out on trunk disable
request to signalling process
27055 SDI detected signalling process
Explanation: SDI issued a request to the
termination
signalling process controlling this trunk to
Explanation: SDI has been notified that the prepare the trunk for removal from service. A
signalling process (shown below the message) reply was not received within the timeout
has died. If any trunk is currently controlled by period. The trunk is disabled.
this signalling process, operations will be
adversely affected. SDI detects this situation and
configuration. When writing a signalling process,
automatically takes the trunk out of service until
see trunk management primitives in the
the signalling process has recovered. The
Programming for the Signalling Interface book.
symbolic procedure name is listed as a
parameter, for example, SL_PROC_EUROISDN. Severity: Yellow
User response: Disable any trunks using this Destination: Log, System Monitor
signalling process, restart the signalling process,
then re-enable the affected trunks. To find out
which signalling process the ID refers to, see the 27058 SDI enable trunk failed by
WebSphere Voice Response header file signalling process
`slcommon.h'. If you are using an Exchange Data Explanation: SDI issued a request to the
Link Signalling process to gather additional call signalling process controlling this trunk to
information, you might want to keep the trunk prepare the trunk for use. The signalling process
enabled if the signalling process fails, and to failed the request. The pack is not placed in
default to a different application profile. If so, service.
change the setting of the "Trunk Interlock - EDL"
parameter (in the Trunk Interface Group) to User response: Check your signalling process
DISABLED. The trunk will then not be disabled. configuration. When writing a signalling process,
see “Channel and trunk management primitives”
Severity: Red in the Programming for the Signalling Interface
Destination: Log, System Monitor, Alertable book.
Severity: Red

27059 • 27064

27062 SDI failed to initialize with
signalling library
27059 SDI disable trunk failed by
Explanation: SDI received an error from the
signalling process
sl_register or sl_open call to the signalling
Explanation: SDI issued a request to the library. SDI terminates, making WebSphere Voice
signalling process controlling this trunk to Response telephony unusable. This error is to be
remove the trunk from use. The signalling expected if you have no telephony devices
process failed the request. The trunk is disabled. attached to the system, in which case the lack of
SDI will have no effect, because its job is to
User response: Check your signalling process control the hardware. In other cases this error is
configuration. When writing a signalling process, fatal, because control of telephony is not
see trunk management primitives in the possible.
Programming for the Signaling Interface book.
User response: If you are not using any
Severity: Yellow telephony hardware you may ignore this
Destination: Log, System Monitor message. In other cases, check the return code
given in the Programming for the Signaling
Interface book to determine the cause of the error.
27060 SDI quiesce trunk failed by Restart the AIX system and try again.
signalling process
Severity: Red
signalling process controlling this trunk to Destination: Log, System Monitor, Alertable
quiesce the trunk. The signalling process failed
the request. The trunk is disabled. Calls in 27063 Unexpected signalling library
progress may be terminated. primitive received
User response: Check your signalling process Explanation: SDI received a signalling library
configuration. When writing a signalling process, request that it cannot handle. Either the primitive
see “Channel and trunk management primitives” was sent in error by the respective signalling
in the Programming for the Signalling Interface process, or the $VAEBIN/SDIEXEC executable is
book. back level or in error. This error may indicate
Severity: Yellow missing function. This primitive has been
ignored; other processing continues normally.
User response: Check the signalling process
code. Check that your executables are at a
27061 Enable trunk failed setting pack consistent level, that is, installed using installp or
use updatep and not copied from an earlier version.
Explanation: SDI received an error from an ioctl Report the problem to the writer of your
call to set up the pack for the configured use. signalling process.
User response: Check the errno value against Severity: White

/usr/include/sys/errno.h. Check the relevant Destination: Log, System Monitor
pack configuration. If the configuration appears
to be correct, restart the AIX system. If the
problem persists, call IBM Support. 27064 Unexpected signalling library
alarm received
Severity: Yellow
Explanation: SDI received an unexpected
Destination: Log, System Monitor indication of a trunk alarm. Either the primitive
was sent in error by the signalling daemon, or

27065 • 27069
the $VAEBIN/SDIEXEC executable is back level

27067 SDI disable channel failed by
or in error. This error may indicate missing
signalling process
function. This primitive has been ignored; other
processing continues normally. Explanation: SDI issued a request to the
signalling process controlling this channel to
User response: If the problem persists, contact
disable the channel The signalling process failed
IBM Support.
or the request timed out. The channel is disabled.
Severity: White
Destination: Log, System Monitor configuration. When writing a signalling process,
see trunk management primitives in the
Programming for the Signalling Interface book.
27065 Trunk disable requested by
signalling process Severity: Yellow
Explanation: SDI received an Destination: Log, System Monitor

SL_TRUNK_DISABLE_IND from a signalling
process controlling the trunk listed below. The
27068 SDI quiesce channel failed by
trunk is recycled (disabled then re-enabled).
signalling process
User response: Usually no action is required;
the trunk is automatically disabled by
signalling process controlling this channel to
WebSphere Voice Response and returned to
quiesce the channel. The signalling process failed
service after a short delay. If this error persists,
or timed out the request. The channel is disabled.
or the trunk does not return to service, refer to
Calls in progress may be terminated.
the WebSphere Voice Response error log in
$OAM_LOG_PATH/errorlog for more User response: Check your signalling process
information about the problems. Contact your configuration. When writing a signalling process,
signalling process writer for problem see trunk management primitives in the
determination and resolution. If necessary, Programming for the Signaling Interface book.
contact IBM Support for additional assistance.
Severity: Yellow
Severity: Red
27069 SDI detected non-essential
27066 SDI enable channel failed by signalling process termination
signalling process
Explanation: SDI has been notified that the
Explanation: SDI issued a request to the signalling process (shown below the message)
signalling process controlling this channel to has died. The trunk is not disabled as this
prepare the channel for use. The signalling Signalling process is not essential to call
process failed or the request timed out. The handling.
channel is not enabled.
User response: To find out which signalling
User response: Check your signalling process process the ID refers to, see the WebSphere Voice
configuration. When writing a signalling process, Response header file `slcommon.h'. Verify the
see trunk management primitives in the configuration and setup of this signalling
Programming for the Signalling Interface book. process, and restart if necessary. If you wish to
automatically disable the trunk when the
Severity: Red
Exchange Data Link process fails, change the
Destination: Log, System Monitor, Alertable setting of the "Trunk Interlock - EDL" parameter
(in the Trunk Interface Group) to ENABLED. The

27070 • 27074
trunk will then be disabled.

27072 SDI re-enable notification
Severity: White (adapter)
Destination: Log, System Monitor, Alertable Explanation: SDI has scheduled a re-enable
request for this adapter. An unrecoverable error
had previously been detected, which required the
27070 SDI detected missing adapter and associated trunks to be disabled. The
non-essential signalling process adapter and associated trunks will shortly return
during enable to service.
Explanation: The signalling process specified in User response: If all associated trunks correctly
the parameters was not active when an attempt return to service the problem was probably
was made to enable a pack using that signalling temporary and can be ignored unless it occurs
process. The pack has been enabled because the repeatedly. If the adapter continues to be enabled
"Trunk Interlock - EDL" system parameter (in the and disabled, run diagnostics on it when
Trunk Interface Group) is set to DISABLED. convenient. Check also that all cables are firmly
User response: Check that all signalling in place, that the pack is securely fitted in the
processes required for your configuration are 9295 (if relevant) and that all adapters in the
active and that the Signalling Process Type pSeries computer are correctly seated.
parameter in the Channel Group definition is Severity: White
correct. This message is repeated for each
missing signalling process type. If you want to Destination: Log, System Monitor, Alertable
fail attempts to enable the trunk when the
Exchange Data Link process is missing, change
27073 SDI re-enable failed (adapter)
the setting of the "Trunk Interlock - EDL" system
parameter to ENABLED. The trunk will then not Explanation: SDI has failed to recycle an
be enabled. adapter.
Severity: White User response: Review the error log for other
errors and act appropriately. If no other errors
are indicated and the problem occurs repeatedly,
contact IBM Support for further problem
27071 SDI failed accessing error channel diagnosis and resolution.
Explanation: SDI could not open the device Severity: White

through which telephony hardware errors are
piped. None of these errors can now be logged.
This error may also occur if no telephony
hardware is available. 27074 Telephony adapter loading
exceeded warning threshold
User response: If no telephony hardware is
currently available, no action need be taken. Explanation: The loading of the adapter has
Otherwise, restart WebSphere Voice Response. If reached the warning threshold. If the loading is
the problem recurs, check the errno value against not brought under control it is possible that
those in /usr/include/sys/errno.h. If you are telephony errors may occur, or the packs may
still unable to resolve the problem contact IBM fail.
Support.
User response: Remove load from the adapter
Severity: Yellow by shutting down packs or channels.
Destination: Log, System Monitor, Alertable Severity: Yellow

27075 • 27080
with the interval between them being long

27075 Telephony adapter loading has
enough so that the interrupt from the first card
now reduced below warning
can be serviced before the interrupt from the
threshold
second card arrives. WebSphere Voice Response
Explanation: The loading of the telephony monitors this interval constantly, and has
adapter has now reduced below the warning detected that the interval between the interrupts
threshold. Operation should now be normal. is not enough. This is a serious error caused
either by loading problems on the card, or
User response: None required.
software problems with the WebSphere Voice
Severity: Green Response device driver and the adapter
embedded software. This error can precede the
Destination: Log, System Monitor, Alertable failure of one or more packs, and can be
followed by other seemingly unrelated errors. In
27076 SDI thread error such cases, this error might indicate the root
cause of the problem.
Explanation: A system call error occurred while
trying to perform AIX thread operations. errno User response: Call IBM Support.
should give the pthread library's error code. Severity: Yellow
User response: Report this problem to IBM Destination: Log, System Monitor, Alertable
Support.
Severity: White 27079 Telephony adapter interrupts are
Destination: Log, System Monitor, Alertable now adequately separated
Explanation: Telephony adapters rely on
27077 SDI ioctl failed interrupting AIX every 20 milliseconds.
Interrupts from two adapters must alternate,
Explanation: SDI received a failure indication with the interval between them being long
from a device driver ioctl request. In some cases, enough so that the interrupt from the first card
this may adversely affect the functioning of the can be serviced before the interrupt from the
system. This error can be generated when there second card arrives.WebSphere Voice Response
is an ALARM situation on the telephony line. monitors this interval constantly, and has
User response: If there are no other problems detected that the interval between the interrupts
on the system, you can ignore this message. is adequate.
Disable and reenable the trunk and ensure that User response: None required.
all errors have cleared before trying to make the
channels available. It may be useful to check the Severity: Green
errno value /usr/include/sys/errno.h. If the Destination: Log, System Monitor, Alertable
problem persists, note all details of the error and
call IBM Support.
27080 Pack has failed too many times.
Severity: White Re-enable cancelled.
Destination: Log, System Monitor Explanation: The referenced pack has failed
more times during the current one-hour period
27078 Telephony adapter interrupts have than specified in the system parameter
drifted together "Maximum Retries for Pack/Adapter
Reenabling". The pack will NOT be reenabled,
Explanation: Telephony adapters rely on despite any indications you receive. This is to
interrupting AIX every 20 milliseconds. stop the pack constantly recycling and
Interrupts from two adapters must alternate, potentially severely impacting the availability of

27081 • 27084
the rest of WebSphere Voice Response. The pack User response: None required.
is left disabled.
Severity: Green
User response: Check the error log to find out
why the pack is failing. You can try to re-enable
this pack manually, but it is not likely to work. If
you want to allow the pack recovery procedures 27083 Adapter has now recovered
to attempt more retries, modify the value of the
"Maximum Retries for Pack/Adapter Reenabling" Explanation: The referenced adapter has now
system parameter in the General parameter recovered following an earlier failure.
group in System Configuration, although any User response: None required.
change will not take effect until WebSphere Voice
Response is restarted. Severity: Green
Severity: Red Destination: Log, System Monitor

27084 Trunk Enable Failed due to
missing TDM Management
27081 Telephony adapter has failed too
many times. Re-enable cancelled. Explanation: The trunk has failed to enable due
to missing TDM Management. On DTTA Systems
Explanation: The referenced adapter has failed the TSLOT process manages TDM connections.
more times during the current one-hour period Some of these are setup when the TSLOT process
than specified in the system parameter runs. Since TSLOT is not present it is possible
"Maximum Retries for Pack/Adapter these connections are incorrectly setup and there
Reenabling". The pack will NOT be reenabled, would be a risk of silent calls if the trunk were
despite any indications you receive. This is to to be enabled. To protect system integrity the
stop the pack constantly recycling and trunk will not be enabled.
potentially severely impacting the availability of
the rest of WebSphere Voice Response. The User response: Investigate the errorlog for
adapter is now no longer usable by WebSphere reasons why TSLOT has failed. If you are using
Voice Response. any TDM functions check your connection
servers are running correctly. Try restarting
User response: Check the error log to find out $VAE/sw/bin/TSLOT and watching for any
why the card is failing. To regain use of the card errors. If this works manually reenable all trunks.
you need to restart WebSphere Voice Response. If If this fails restart WebSphere Voice Response. If
you want to allow the recovery procedures to you are unable to resolve the problem, contact
attempt more retries, modify the value of the IBM support.
"Maximum Retries for Pack/Adapter Reenabling"
parameter in the General parameter group in Severity: Red
System Configuration, although any change will Destination: Log, System Monitor
not take effect until WebSphere Voice Response is
restarted.
Severity: Red
27082 Pack has now recovered

Explanation: The referenced pack has now
recovered following an earlier failure.

29000 • 29101
ISDN services
information about the type of call, such as
29000 ISDN undefined counter
speech, fax, or data. Data calls are rejected by
Explanation: An ISDN counter has been WebSphere Voice Response.
incremented which does not have a specific
User response: This message is provided for
explanation. This is caused by an internal
information and does not indicate an error in the
programming error in WebSphere Voice
system. If you are concerned about this
Response.
condition, check the error log for more
User response: If this error occurs frequently it information on the calls that were rejected by the
may indicate a problem with WebSphere Voice ISDN signalling process. You may find that some
Response. If the problem persists, contact IBM of your callers are using an incorrect phone
Support. number, or are trying to make the wrong type of
call.
Severity: White
Severity: Yellow
29002 ISDN D channel protocol error
29100 Invalid ISDN environment
Explanation: A protocol error occurred on the
services buffer address
ISDN D channel. The D channel carries the
signalling for ISDN trunks. The D channel Explanation: The ISDN protocol software
protocol is designed to be able to recover from encountered an invalid buffer address. The
protocol errors. address of the buffer and the reason it is invalid
are given in the detailed section of the error log
User response: If this error occurs frequently it
entry. A software problem in the ISDN protocol
may indicate a problem with WebSphere Voice
is the probable cause of this error.
Response. Check the error log for other errors by
the ISDN signalling process; this may identify User response: The system may continue
the origin of the error. There are several steps without further problems. If not, stop and restart
you can take to attempt to solve this problem. the ISDN signalling process using the Custom
Check that the configuration of WebSphere Voice Server Manager. If the problem persists, call IBM
Response matches the network configuration. If Support. When reporting ISDN software
they do not match, stop the ISDN signalling problems, take a copy of all files with names
process using the Custom Server Manager. beginning es_ in the /var/tmp directory as soon
Reconfigure WebSphere Voice Response to match as the error occurs.
the network, then restart the signalling process
Severity: Yellow
and re-enable the trunks.
Severity: Yellow
29101 Storage overwrite in ISDN
environment services buffer
29003 ISDN D rejected call
Explanation: The ISDN protocol detected a
Explanation: The number of calls rejected by buffer storage overwrite. A software problem in
the ISDN signalling process has reached its the ISDN protocol is the probable cause of this
predefined threshold. The ISDN signalling error.
process will reject calls that are not compatible
User response: The system may continue
with the WebSphere Voice Response voice
without further problems. If not, stop and restart
response unit function. ISDN signalling includes

29102 • 29106
the ISDN signalling process using the Custom

29104 ISDN holding bay is full
Server Manager. If the problem persists, call IBM
Support. When reporting ISDN software Explanation: One of the ISDN protocol
problems, take a copy of all files with names components tried to write a message into the
beginning es_ in the /var/tmp directory as soon message holding bay, but it is full. A software
as the error occurs. problem in the ISDN protocol is the probable
cause of this error.
Severity: Yellow
User response: Stop and restart the ISDN
signalling process using the Custom Server
Manager. If the problem persists, call IBM
29102 ISDN task attempted to use Support. When reporting ISDN software
uninitialized message queue problems, take a copy of all files with names
beginning es_ in the /var/tmp directory as soon
Explanation: One of the ISDN protocol as the error occurs.
components attempted to use a corrupted or
uninitialized message queue. A software problem Severity: Yellow
in the ISDN protocol is the probable cause of this
error.
29105 Lost ISDN queue element found
without further problems, but if not, stop and
restart the ISDN signalling process using the Explanation: A queue element was found on an
Custom Server Manager. If the problem persists, ISDN environment services queue, in a location
call IBM Support. When reporting ISDN software where no queue element was expected. This
problems, take a copy of all files with names queue element was freed. A software problem in
beginning es_ in the /var/tmp directory as soon the ISDN protocol is the probable cause of this
as the error occurs. error.
Severity: Yellow User response: The system should continue
without further problems. If further problems do
occur, stop and restart the ISDN signalling
process using the Custom Server Manager. If the
29103 Failed system call within ISDN problem persists, call IBM Support. When
reporting ISDN software problems, take a copy
Explanation: One of the ISDN protocol of all files with names beginning es_ in the
components attempted a system call but it failed. /var/tmp directory as soon as the error occurs.
Details of the system call and error code returned
are in the error log entry. Severity: White
User response: The system may continue Destination: Log, System Monitor
without further problems, but if not, stop and
restart the ISDN signalling process using the
29106 ISDN queue empty
Custom Server Manager. If the problem persists,
call IBM Support. When reporting ISDN software Explanation: One of the ISDN protocol
problems, take a copy of all files with names components tried to read a message from an
beginning es_ in the /var/tmp directory as soon empty message queue. A software problem in the
as the error occurs. ISDN protocol is the probable cause of this error.
Severity: Yellow User response: The system should continue

29107 • 29111
problem persists, call IBM Support. When Explanation: One of the ISDN protocol
reporting ISDN software problems, take a copy components tried to allocate a buffer, but there
of all files with names beginning es_ in the are insufficient buffers available.
/var/tmp directory as soon as the error occurs.
Severity: White without further problems. If further problems do
problem persists, call IBM Support. When
29107 Error putting ISDN message from reporting ISDN software problems, take a copy
holding bay to queue of all files with names beginning es_ in the
Explanation: One of the ISDN protocol
components tried to put a message onto a Severity: White
message queue from the holding bay, but this
failed. A software problem in the ISDN protocol
is the probable cause of this error.
29110 ISDN environment services buffer
pool audit problems
occur, stop and restart the ISDN signalling Explanation: Auditing of the ISDN environment
process using the Custom Server Manager. If the services buffer pool discovered potential
problem persists, call IBM Support. When problems with the pool. A software problem in
reporting ISDN software problems, take a copy the ISDN protocol is the probable cause of this
of all files with names beginning es_ in the error.
Severity: Yellow without further problems. If further problems do
problem persists, call IBM Support. When
29108 ISDN environment services buffer reporting ISDN software problems, take a copy
pool is empty of all files with names beginning es_ in the
Explanation: One of the ISDN protocol
components tried to allocate a buffer, but there Severity: Yellow
are no buffers available.
29111 Insufficient disk space for ISDN
environment services
problem persists, call IBM Support. When Explanation: ISDN environment services tried
reporting ISDN software problems, take a copy to allocate disk space for control files, but there
of all files with names beginning es_ in the was insufficient disk space.
User response: The name of the directory in
Severity: Yellow which the ISDN environment services files are
stored, the space required, and the space
available are recorded in this error log entry.
Make more space available, either by deleting
29109 ISDN environment services buffer old files from this directory, or by allocating
pool is low

29112
more disk space to the file system containing this

directory.
Severity: Red
29112 ISDN environment services file

locking error
Explanation: ISDN environment services tried
to lock a memory mapped file, but it could not
do so because of a software problem.
User response: You should report this problem
to IBM Support. When reporting ISDN software
problems, take a copy of all files with names
beginning es_ in the /var/tmp directory as soon
as the error occurs.
Severity: Yellow

29200 • 29203
ISDN signaling process and ISDN call control

Severity: Yellow
29200 ISDN signalling process call state
machine error Destination: Log, System Monitor
Explanation: An unexpected error occurred in
the ISDN signalling process call state machine. 29202 ISDN signalling process trunk
Detailed information of the error is logged. If a state machine error
call is in progress on the channel on which the
error occurred the signalling process attempts to Explanation: An unexpected error occurred in
terminate it. the ISDN signalling process trunk state machine.
Detailed information on the error is logged. The
User response: Check the error log for other trunk on which the error occurred is disabled
errors in the ISDN signalling process, which may after any active calls on it have been cleared and
identify the origin of the error. If this error its channels disabled.
occurs frequently it may indicate a problem with
WebSphere Voice Response. Disable and User response: Check the error log for other
re-enable the channel on which the error errors within the ISDN signalling process, which
occurred and try again. If this does not work, may identify the origin of the error. If this error
disable and re-enable the trunk to which the occurs frequently it may indicate a problem with
channel belongs. If the problem still persists, shut WebSphere Voice Response. Disable and
down and restart WebSphere Voice Response. If re-enable the trunk on which the error occurred
none of the above is successful call IBM Support. and try again. If this does not work, stop and
restart the signalling process using the Custom
Severity: Yellow Server Manager menu option. If this does not
solve the problem shut down and restart
WebSphere Voice Response. If none of the above
is successful call IBM Support.
29201 ISDN signalling process channel
Severity: Yellow
state machine error
the ISDN signalling process channel state
machine. Detailed information of the error is 29203 ISDN signalling process
logged. If a call is in progress on the channel on initialization failure
which the error occurred the signalling process
attempts to terminate it and disables the affected Explanation: The ISDN signalling process could
channel. not initialize and has terminated. No outbound
or inbound calls can be made or received on
User response: Check the error log for other your trunks. Detailed information on the cause of
errors in the ISDN signalling process, which may the failure is logged.
identify the origin of the error. If this error
occurs frequently it may indicate a problem with User response: Initialization fails if the
WebSphere Voice Response. Disable and signalling library or the environment services are
re-enable the trunk on which the error occurred not responding. Check the error log for related
and try again. If this does not work, stop and errors from the signalling library or the
restart the signalling process using the custom environment services, or for an internal error in
server manager menu option. If this does not the ISDN signalling process.
solve the problem shut down and restart Severity: Red
is successful call IBM Support. Destination: Log, System Monitor

29204 • 29208
you are trying to run two instances of the ISDN

29204 ISDN signalling process
custom server.
configuration error
User response: Check the Custom Server
Explanation: An error occurred validating the
Monitor window to see if you have more than
configuration data for the ISDN signalling
one ISDN custom server running. Check the
process. Detailed information on the error is
error log for related errors originating from the
logged. The trunk on which the error occurred is
environment services. If this error occurs
not enabled.
frequently it may indicate a problem with
User response: Determine which configuration WebSphere Voice Response. Stop and restart the
parameter is invalid from the error log and signalling process using the Custom Server
change the value of the parameter using the Manager menu option. If this does not work,
Configuration menus. Try to enable the trunk. shut down and restart WebSphere Voice
You may have to shut down and restart Response. If none of the above is successful call
WebSphere Voice Response for your change to be IBM Support.
effective. If you still have a problem, check your
Severity: Yellow
switch configuration with your network provider.
If none of the above is successful call IBM Destination: Log, System Monitor
Support.
Severity: Yellow 29207 ISDN signalling process internal
error
the ISDN signalling process. Detailed information
about the error is logged.
signalling library error
Explanation: A call to the signalling library
functions failed. The relevant function and return
Response. Stop and restart the signalling process
codes are logged.
using the Custom Server Manager menu option.
User response: Check the error log for related If this does not work, shut down and restart
errors originating from the signalling library. If WebSphere Voice Response. If none of the above
this error occurs frequently it may indicate a is successful call IBM Support.
problem with WebSphere Voice Response. Stop
Severity: Yellow
and restart the signalling process using the
Custom Server Manager menu option. If this Destination: Log, System Monitor
does not work, shut down and restart WebSphere
Voice Response. If none of the above is successful
call IBM Support. 29208 ISDN signalling process buffer
allocation retry
Severity: Yellow
Explanation: The ISDN signalling process
Destination: Log, System Monitor cannot obtain an environment services buffer.
Detailed information about the error is logged.
The trunk on which the error occurred is
disabled after any active calls on it have been
environment services error
cleared and its channels disabled.
Explanation: A call to the environment services
codes are logged. If the error description is
"es_init_failed" and the environment service is 29,

29209 • 29214
If this does not work, shut down and restart User response: If this error occurs frequently it
WebSphere Voice Response. If none of the above may indicate a problem with WebSphere Voice
is successful call IBM Support. Response. Stop and restart the signalling process
Severity: White
If this does not work, shut down and restart
Destination: Log WebSphere Voice Response. If none of the above
is successful call IBM Support.
29209 ISDN signalling process Severity: Yellow

executable could not be found
Explanation: The executable file for the ISDN
signalling process was not found. The process
29213 ISDN channel state machine
could not be started.
invalid primitive
Severity: Red channel state machine received an unexpected
primitive. This means that the primitive could
Destination: Log, System Monitor not be identified or that the primitive was not
expected in the current state of the channel.
29210 ISDN signalling process could not User response: If this error occurs frequently it
start Layer 3 may indicate a problem with WebSphere Voice
Explanation: The ISDN signalling process could Response. Stop and restart the signalling process
not run the executable file for Layer 3. The using the Custom Server Manager menu option.
process has terminated. If this does not work, shut down and restart
User response: Call IBM Support. is successful call IBM Support.
Severity: Red Severity: Yellow
29211 ISDN signalling process could not 29214 ISDN trunk state machine invalid
start Layer 2 primitive
Explanation: The ISDN signalling process could Explanation: The ISDN signalling process trunk
not run the executable file for Layer 2. The state machine received an unexpected primitive.
process has terminated. This means that the primitive could not be
User response: Call IBM Support. identified or that the primitive was not expected
in the current state of the trunk.
Severity: Red
Destination: Log, System Monitor may indicate a problem with WebSphere Voice
29212 ISDN call state machine invalid using the Custom Server Manager menu option.
primitive If this does not work, shut down and restart
Explanation: The ISDN signalling process call is successful call IBM Support.
state machine received an unexpected primitive.
This means that the primitive could not be Severity: Yellow
identified or that the primitive was not expected Destination: Log, System Monitor
in the current state of the call.

29215 • 29220
none of the above is successful call IBM Support.

29215 ISDN signalling process invalid
primitive Severity: Red
Explanation: The ISDN signalling process Destination: Log, System Monitor
received a primitive it could not identify. This
error is usually reported by the primitive to
event mapper as the state machines have their 29218 ISDN signalling process detected
own errors defined for this situation. Layer 3 death
User response: If this error occurs frequently it Explanation: The ISDN signalling process
may indicate a problem with WebSphere Voice detected that there is no longer a Layer 3
Response. Stop and restart the signalling process process. The signalling process will attempt to
using the Custom Server Manager menu option. clear existing calls on this trunk before disabling
If this does not work, shut down and restart it. If you are running in an NFAS system, all the
WebSphere Voice Response. If none of the above active trunks will be disabled.
is successful call IBM Support. User response: If this error occurs frequently it
Severity: Yellow may indicate a problem with WebSphere Voice
Response. Re-enable the trunk from the System
Destination: Log, System Monitor Monitor window. If this does not work, shut
down and restart WebSphere Voice Response. If
29216 ISDN signalling process channel
error Severity: Red
Explanation: The ISDN signalling process Destination: Log, System Monitor
detected an internal error on the channel. The
signalling process will attempt to clear any
existing call on this channel before disabling it. 29219 ISDN signalling process detected
Layer 2 death
may indicate a problem with WebSphere Voice Explanation: The ISDN signalling process
Response. Re-enable the channel from the system detected that there is no longer a Layer 2
monitor window. If this does not work, shut process. The signalling process will attempt to
down and restart WebSphere Voice Response. If clear existing calls on this trunk before disabling
none of the above is successful call IBM Support. it.
Severity: Yellow User response: If this error occurs frequently it

Destination: Log, System Monitor Response. Re-enable the trunk from the System
Monitor window. If this does not work, shut
29217 ISDN signalling process trunk
error
Severity: Red
detected an internal error on the trunk. The Destination: Log, System Monitor
signalling process will attempt to clear existing
calls on this trunk before disabling it.
29220 ISDN signalling process cannot
User response: If this error occurs frequently it make call on alarmed trunk
Response. Re-enable the trunk from the system Explanation: The ISDN signalling process
monitor window. If this does not work, shut detected that the trunk on which a call setup
down and restart WebSphere Voice Response. If attempt was made is alarmed. No calls can be

29221 • 29224
made on a trunk on which there are one or more

29223 ISDN Redial Limitation: Call
alarms.
Denied
User response: Wait for the alarm to clear
Explanation: The Redial Limitation module has
before attempting to make the call again. If the
detected that too many calls have been
call fails to establish once the alarm has cleared,
unsuccessfully placed to a particular number.
check the error log for other errors in the
The homologation requirement for this area will
signalling process. If the problem persists, stop
not allow any more calls to be placed to this
number until a timer has elapsed. The number
Custom Server Manager menu option. If this
dialed is in the message below.
does not solve the problem, shut down and
restart WebSphere Voice Response. If none of the User response: Wait for the timer to elapse
above is successful call IBM Support. before placing further calls to this number. Check
your equipment to find out why calls are failing.
Severity: Yellow
Severity: Yellow
29221 ISDN signalling process tag
processing error 29224 ISDN Redial Limitation: Failed
Call List Full
Explanation: ISDN signalling process
experienced an error while trying to process a Explanation: The Redial Limitation module
tag string. Details of the error are logged below. maintains a list of unsuccessful calls. This list has
The IE with problems will not be built or sent to become full. Calls will not be placed until there
the line. are free entries in the list.
User response: Check that the application, User response: Check your equipment to find
custom server or state table is generating the out why calls are failing. Increase the size of the
correct tag string. If the tag string is correctly failed call list in System Configuration. Wait for
formated and valid and the error is still the timer to elapse to free up entries in the list.
generated call IBM Support. (The list is cleared after a certain period defined
by the homologation requirements of your area.)
Severity: Yellow
Severity: Yellow
29222 ISDN signalling process unable to
send IE
Explanation: Whilst constructing the message to
send to Layer 3, the ISDN signalling process ran
out of space in the buffer.
User response: The Information Elements are
too large or there are too many for the buffer. If
you are constructing the IEs from tag strings
then reduce the size or quantity of IEs.
Severity: Yellow

29400 • 29404
ISDN D Layer 3
29400 Invalid ISDN Layer 3 task
number passed from call control
Response. Disable and re-enable the trunk on
Explanation: The ISDN signalling process which the error occurred and try again. If the
passed an invalid task number when starting the problem persists, stop and restart the signalling
ISDN Layer 3 process. The trunk on which this process using the Custom Server Manager menu
error occurred is not enabled. option. All other trunks using the signalling
process are disabled. If this does not solve the
problem shut down and restart WebSphere Voice
errors within the ISDN signalling process as this
Response. If none of the above is successful call
may identify the origin of the error. If this error
IBM Support.
WebSphere Voice Response. Disable and Severity: Red
re-enable the trunk on which the error occurred
and try again. If the problem persists, stop and
Server Manager menu option. All other trunks 29403 ISDN Layer 3 internal error
using the signalling process are disabled. If this
does not solve the problem, shut down and Explanation: The ISDN Layer 3 software has
restart WebSphere Voice Response. If none of the detected an internal error. All calls using this
above is successful, call IBM Support. Layer 3 process are cleared and the data link
layer is deactivated.
Severity: Red
Destination: Log, System Monitor may indicate a problem with WebSphere Voice
which the error occurred and try again. If the
29401 ISDN Layer 3 user initialization
problem persists, stop and restart the signalling
parameter error
process using the Custom Server Manager menu
Explanation: A parameter was set incorrectly option. All other trunks using the signalling
when initializing ISDN Layer 3 with parameters process are disabled. If this does not solve the
from the ISDN signalling section in the System problem shut down and restart WebSphere Voice
Configuration menu option. Response. If none of the above is successful, call
IBM Support.
User response: Select the System Configuration
menu option, then select ISDN Signalling section Severity: Red
and modify the failing parameter. Save your
changes. If the trunk is enabled, disable and
re-enable it to pass the new changes to ISDN
Layer 3. 29404 ISDN Layer 3 recoverable internal
error
Severity: Red
Explanation: The ISDN Layer 3 software has
detected a recoverable internal error. Individual
calls may be cleared by these errors.
29402 ISDN Layer 3 initialization
parameter error
Explanation: An error was detected in a Response. Disable and re-enable the trunk on
parameter when initializing ISDN Layer 3 with which the error occurred and try again. If the
parameters from the ISDN Signalling Process. problem persists, stop and restart the signalling

29405 • 29410
process using the Custom Server Manager menu informed ISDN Layer 3 that it can send Layer 3
option. All other trunks using the signalling messages to the switch.
User response: This message is for information
only.
IBM Support. Severity: White
29408 ISDN Layer 3 backup data link
layer deactivated
29405 ISDN Layer 3 primary data link
layer activated Explanation: ISDN Layer 2 has informed ISDN
Layer 3 that it is not possible to send Layer 3
Explanation: ISDN Layer 2 has told ISDN Layer
messages to the switch. If the system is T1/uLaw
3 that it is possible to send Layer 3 messages to
and NFAS is being used with a backup D
the switch.
channel, the Layer 3 process may switch the
User response: This message is for information backup data link to the primary data link on a
only. different trunk automatically. Active calls are
preserved, but all other calls are cleared.
Severity: White
only.
Severity: White
layer deactivated Destination: Log, System Monitor
Explanation: ISDN Layer 2 has told ISDN Layer
3 that it is not possible to send Layer 3 messages 29409 ISDN Layer 3 backup data link
to the switch. If the timer T309 is enabled (see layer out of service
ISDN signalling section of the System
Explanation: The ISDN Layer 3 backup data
Configuration menu option), all calls are cleared
link layer is out of service.
except active calls until the timer times out (after
120 seconds), or the link is activated again. If User response: This message is for information
T309 is disabled, all calls are cleared. If the only.
system is T1/uLaw and NFAS is being used with
a backup D channel, the Layer 3 process may Severity: White
automatically switch the primary data link to the Destination: Log, System Monitor
backup data link on a different trunk. Active
calls are preserved, but all other calls are cleared.
User response: This message is for information layer out of service
only.
Explanation: The ISDN Layer 3 has set the
Severity: White primary data link layer into out of service (OOS)
Destination: Log, System Monitor mode.
29407 ISDN Layer 3 backup data link only.
layer activated Severity: White
Explanation: The backup ISDN Layer 2 has Destination: Log, System Monitor

29411 • 29413

29411 ISDN Layer 3 had Layer 2 data
option. All other trunks using the signalling
link timer expiry
Explanation: The ISDN Layer 3 started a timer problem shut down and restart WebSphere Voice
on trying to get Layer 2 to establish a data link Response. If none of the above is successful call
to the switch so that Layer 3 messages could be IBM Support.
sent. This timer has expired; the data link could
Severity: Yellow
not be established, so no outbound or incoming
calls can be made. Destination: Log, System Monitor
User response: Check that there are no other
alarms on the pack, such as Loss Of Signal (LOS) 29413 ISDN Layer 3 primitive sequence
or Remote Alarm Indication (RAI). If there are, error detected
check the cabling between the switch and the
pack to remove these alarms. If there are no Explanation: The ISDN Layer 3 software has
trunk alarms present it may mean that the ISDN detected a primitive sequence error. If there is a
Layer 2 protocol between the switch and call on the channel which had the sequence error
WebSphere Voice Response is not active or it will be cleared and the channel will be
working. Contact someone who can check the disabled. If the sequence error concerned the
status of the Layer 2 protocol using a Protocol trunk, all calls will be cleared on that trunk and
Analyzer or the ISDN_MONITOR tool in the trunk changed to the disabled state.
WebSphere Voice Response, which displays Layer User response: If this error occurs frequently it
2 and 3 when working. If the switch is sending may indicate a problem with WebSphere Voice
out Layer 2 messages to start the link SABMEs Response. Disable and re-enable the trunk on
and WebSphere Voice Response is not which the error occurred and try again. If the
responding, there may be a problem. Disable and problem persists, stop and restart the signalling
re-enable the trunk on which the error occurred process using the Custom Server Manager menu
and try again. If the problem persists, stop and option. All other trunks using the signalling
restart the signalling process using the Custom process are disabled. If this does not solve the
Server Manager menu option. All other trunks problem shut down and restart WebSphere Voice
using the signalling process are disabled. If this Response. If none of the above is successful call
does not solve the problem shut down and IBM Support.
restart WebSphere Voice Response. If none of the
above is successful call IBM Support. Severity: Yellow
29412 ISDN Layer 3 invalid ISDN

primitive detected
detected an invalid primitive that should have
been processed. A call on the channel which had
the invalid primitive may be cleared.

29601 • 29605
ISDN D Layer 2 and Layer 1

29601 Invalid ISDN Layer 2 task
number passed from call control
Explanation: The ISDN signalling process which the error occurred and try again. If the
passed an invalid task number when starting the problem persists, stop and restart the signalling
ISDN Layer 2 process. The trunk on which this process using the Custom Server Manager menu
error occurred will not be enabled. option. All other trunks using the signalling
errors within the ISDN signalling process, which
may identify the origin of the error. If this error
IBM Support.
WebSphere Voice Response. Disable and Severity: Yellow
re-enable the trunk on which the error occurred
and try again. If the problem persists, stop and
Server Manager menu option. All other trunks 29604 ISDN Layer 2 failure
using the signalling process are disabled. If this opening/closing D channel access
does not solve the problem shut down and via device driver
above is successful call IBM Support. Explanation: The device driver did not send a
valid file descriptor to Layer 2 when opening the
Severity: Red signalling D channel, or did not accept the file
descriptor when closing it.
29602 ISDN Layer 2 user initialization
parameter error
which the error occurred and try again. If this
Explanation: A parameter was set incorrectly does not solve the problem shut down and
when initializing ISDN Layer 2 with parameters restart WebSphere Voice Response. If this does
from the ISDN signalling section in the System not solve the problem shut down and restart the
Configuration menu option. pSeries system unit. If none of the above is
successful call IBM Support.
User response: Select the System Configuration
menu option, then select the ISDN signalling Severity: Red
section and modify the failing parameter. Save
your changes. If the trunk is still enabled, disable
and re-enable it to pass the changed parameter to
ISDN Layer 2. 29605 ISDN Layer 2 failure. No
response from ISDN Layer 1
Severity: Red
microcode.
Explanation: The ISDN Layer 1 microcode on
the PACK did not send a valid initialization
29603 ISDN Layer 2 initialization message back to Layer 2. The trunk is not
parameter error enabled. This may be caused by the wrong
microcode being downloaded to the pack, or by
Explanation: An error was detected in a
an internal error.
parameter when initializing ISDN Layer 2 with
parameters from the ISDN signalling process. User response: On the WebSphere Voice

29606 • 29609
Response logon screen, click Configuration, then Explanation: The ISDN Layer 1 microcode
Pack Configuration. The trunk parameters button received a message from Layer 2 with an
should display ISDN. If it does not, click the unrecognized primitive. This is an internal error
button and set trunk signalling mode to ISDN. in the ISDN protocol stack. The trunk with the
This ensures the correct ISDN Layer 1 microcode signalling channel is disabled.
is downloaded. Check the pack configuration
against the Installation book or Configuring the
System book. Save any changes. Try to re-enable
the trunk on which the error occurred. If this
which the error occurred and try again. Have the
error log available when you call IBM Support.
restart WebSphere Voice Response. If this does
not solve the problem, shut down and restart the Severity: Yellow
pSeries system unit. If none of the above is
successful call IBM Support. Destination: Log, System Monitor
Severity: Red
29608 ISDN Layer 1 failure to activate
Destination: Log, System Monitor when enabled
Explanation: The ISDN Layer 1 microcode was
29606 ISDN Layer 1 initialization unable to activate the D channel Layer 1 when
parameter error the trunk was enabled. This could be caused by
having no cable for the trunk, a bad cable
Explanation: A parameter was set incorrectly
between the trunk and the switch, or the switch
when initializing ISDN Layer 1 with parameters
not being configured correctly.
from the Trunk Interface section in the System
Configuration menu option. For ISDN on E1 the User response: Ensure the cable from the switch
CCS signalling timeslot must be 16; for T1 it to the 9295 is plugged in at both ends. If the
must be 24. cable is plugged in, ensure that there are no
alarms being detected when trying to enable this
User response: Checking individual parameters
pack, for example, Loss of Signal, Loss of
can only be done using the 'field' access at the
Synchronization, or Bipolar violations. If there
logon panel on WebSphere Voice Response. If
are, this normally indicates a cable problem or a
System Configuration was used to configure the
switch configuration error. Refer to the
pack, check that the correct ISDN template was
WebSphere Voice Response Installation book to
copied to the trunk group used for the pack, for
see the requirements for ISDN installation of
example, E1 or T1. If Pack Configuration was
WebSphere Voice Response. Temporary RAI red
used to configure the pack, check that the pack is
alarms at enable time are normal and should not
set up for ISDN and that the configuration was
cause this error. Try to re-enable the trunk on
saved. Try to re-enable the trunk on which the
which the error occurred. If this does not solve
error occurred. If this does not solve the problem
the problem, shut down and restart WebSphere
shut down and restart WebSphere Voice
Voice Response. If this does not solve the
Response. If this does not solve the problem then
problem, shut down and restart the pSeries
shut down and restart the pSeries system unit. If
system unit. If none of the above is successful
call IBM Support.
Severity: Red
Severity: Red
29607 ISDN Layer 1 invalid primitive

received

29610 • 29613
detected an internal error. All calls set up on this User response: Any changes made to the switch
signalling channel are cleared unless a backup D or service provider configuration have solved
channel has been configured using Non Facility this problem.
Associated Signalling (NFAS). This feature is for
Severity: White
T1 systems only.
Response. Disable and re-enable the trunk on 29612 ISDN Layer 2 had an error trying
which the error occurred and try again. If the to start its child process
process using the Custom Server Manager menu Explanation: The ISDN Layer 2 software had an
option. All other trunks using the signalling error starting its child process. It cannot read
process are disabled by taking this action. If this incoming Layer 2 frames on the signalling
does not solve the problem, shut down and channel. The trunk is not enabled.
restart WebSphere Voice Response. If none of the User response: If this error occurs frequently it
above is successful call IBM Support. may indicate a problem with WebSphere Voice
Severity: Red Response. Disable and re-enable the trunk on
Destination: Log, System Monitor problem persists, stop and restart the signalling
29610 ISDN Layer 2 detected invalid
incoming frames
Explanation: The ISDN Layer 2 software Response. If none of the above is successful call
detected invalid incoming frames with their C/R IBM Support.
bit set to mean TE mode. The WebSphere Voice
Severity: Red
Response ISDN software can only be run in TE
or user mode, so the switch must be configured Destination: Log, System Monitor
as NT or Network mode.
User response: Check the switch configuration 29613 ISDN Layer 2 failed to stop its
or ask the service provider to ensure the switch child process
is configured to be Network Termination (NT) or
Network mode, because WebSphere Voice Explanation: The ISDN Layer 2 software has
Response cannot make or receive any calls in this detected that its child process cannot be stopped.
state. If the switch configuration or service This process will keep polling the device driver
provider configuration is changed, the trunk to read data on the ISDN link.
should be disabled and re-enabled. If none of the User response: After the trunk has been
above is successful call IBM Support. disabled, go to an AIX window and issue the
Severity: Red command 'ps -eaf | grep lape'. On an active
trunk there should be pairs of this process seen
Destination: Log, System Monitor as 'lape 36'. If there are an odd number of 'lape'
processes, do a 'kill -9' on the process with the
unpaired number after it. If this error occurs
29611 ISDN Layer 2 detected incoming
frequently it may indicate a problem with
NT/network mode L2 frames
WebSphere Voice Response. Disable and
Explanation: The ISDN Layer 2 software has re-enable the trunk on which the error occurred
detected that the invalid frames warning has and try again. If the problem persists, stop and
cleared and it is now receiving NT or network restart the signalling process using the Custom
frames correctly. Server Manager menu option. All other trunks

29614 • 29617
using the signalling process are disabled by process using the Custom Server Manager menu
taking this action. If this does not solve the option. All other trunks using the signalling
problem, shut down and restart WebSphere Voice process are disabled by taking this action.
Response. If none of the above is successful call Restarting the custom server re-initializes the
IBM Support. ISDN buffers in the system for use and should
fix the immediate problem. If this does not solve
Severity: Red
the problem, shut down and restart WebSphere
Destination: Log, System Monitor Voice Response. If none of the above is successful
call IBM Support.
29614 ISDN Layer 2 child died Severity: Red
Explanation: The ISDN Layer 2 child process Destination: Log, System Monitor
has had an internal error and died. Any calls
using this trunk for signalling will be cleared and
29616 ISDN Layer 1 discarding
the trunk will have to be re-enabled.
signalling messages stopped
Explanation: The ISDN Layer 1 reading process
has stopped discarding incoming ISDN Layer 2
and 3 signalling messages. Buffers in the pool are
now available for passing these to Layer 2.
Signalling has been restarted. A loss of some
incoming calls or incoming call clearing
messages may have occurred while the messages
process are disabled by taking this action. If this
were being discarded. If this error occurs
frequently, the system is running very close to
the limit of the current buffer pool.
above is successful call IBM Support.
Severity: Red
Destination: Log, System Monitor Response. Disable and re-enable the trunk on
29615 ISDN Layer 1 discarding process using the Custom Server Manager menu
incoming messages. Lack of option. All other trunks using the signalling
buffers in pool. process are disabled. Restarting the custom
Explanation: The ISDN Layer 1 reading process server re-initializes the ISDN buffers in the
is discarding incoming ISDN Layer 2 and 3 system for use and should fix the immediate
signalling messages because of a lack of buffers problem. If this does not solve the problem, shut
in the pool. Any new incoming calls and down and restart WebSphere Voice Response. If
incoming clearing of existing calls will be none of the above is successful call IBM Support.
ignored until this situation is resolved. Look out Severity: Green
for the message saying "Layer 1 Discarding
Messages Stopped", which means that the ISDN Destination: Log, System Monitor
signalling channel is fully functional again
although messages have been previously lost.
29617 ISDN Layer 3 is unable to process
User response: If this error occurs frequently it an incoming call.
Explanation: The buffer pool used for
processing calls is almost exhausted. New
incoming calls will be released until there are

more resources avaliable. The situation will
improve when some of the current calls that are
being processed have been cleared.
IBM Support.
Severity: Red

29800 • 29806
VoIP
User response: Report this error to your IBM
29800 VoIP Media (UPA) Internal
development support
Failure
Severity: Yellow
the VoIP Media process. This is a hard failure Destination: Log, System Monitor
and the media process has halted. Detailed
information about the error is logged.
29804 VoIP SIP signalling process
User response: Report this error to your IBM Internal Failure
development support
Severity: Red the VoIP SIP signalling process. This is a hard
failure and the media process has halted.
29801 VoIP Media (UPA) Internal
development support
Warning
Severity: Red
the VoIP Media process. This is a warning only. Destination: Log, System Monitor
User response: Report this error to your IBM 29805 VoIP SIP signalling process
development support Internal Warning
Severity: Yellow Explanation: An unexpected error occurred in
the VoIP SIP signalling process. This is a warning
only. Detailed information about the error is
logged.
29802 VoIP H323 signalling process
Internal Failure
development support
Severity: Yellow
the VoIP H323 signalling process. This is a hard
failure and the media process has halted. Destination: Log, System Monitor
User response: Report this error to your IBM 29806 VOIP signalling process call state
development support machine error
Severity: Red Explanation: An unexpected error occurred in
the VOIP signalling process call state machine.
Detailed information of the error is logged. If a
call is in progress on the channel on which the
29803 VoIP H323 signalling process error occurred the signalling process attempts to
Internal Warning terminate it.
Explanation: An unexpected error occurred in User response: Check the error log for other
the VoIP H323 signalling process. This is a errors in the VOIP signalling process, which may
warning only. Detailed information about the identify the origin of the error. If this error
error is logged. occurs frequently it may indicate a problem with
WebSphere Voice Response. Disable and

29807 • 29810
re-enable the channel on which the error WebSphere Voice Response. Disable and
occurred and try again. If this does not work, re-enable the trunk on which the error occurred
disable and re-enable the trunk to which the and try again. If this does not work, stop and
channel belongs. If the problem still persists, shut restart the signalling process using the Custom
down and restart WebSphere Voice Response. If Server Manager menu option. If this does not
none of the above is successful call IBM Support. solve the problem shut down and
restartWebSphere Voice Response . If none of the
Severity: Yellow
Severity: Yellow
29807 VOIP signalling process channel
state machine error
29809 VOIP signalling process
initialization failure
the VOIP signalling process channel state
machine. Detailed information of the error is Explanation: The VOIP signalling process could
logged. If a call is in progress on the channel on not initialize and has terminated. No outbound
which the error occurred the signalling process or inbound calls can be made or received on
attempts to terminate it and disables the affected your trunks. Detailed information on the cause of
channel. the failure is logged.
User response: Check the error log for other User response: Initialization fails if the
errors in the VOIP signalling process, which may signalling library or the environment services are
identify the origin of the error. If this error not responding. Check the error log for related
occurs frequently it may indicate a problem with errors from the signalling library or the
WebSphere Voice Response. Disable and environment services, or for an internal error in
re-enable the trunk on which the error occurred the VOIP signalling process.
and try again. If this does not work, stop and
Severity: Red
restart the signalling process using the custom
server manager menu option. If this does not Destination: Log, System Monitor
solve the problem shut down and restart
is successful call IBM Support. 29810 VOIP signalling process
signalling library error
Severity: Yellow
Explanation: A call to the signalling library
Destination: Log, System Monitor functions failed. The relevant function and return
codes are logged.
29808 VOIP signalling process trunk User response: Check the error log for related
state machine error errors originating from the signalling library. If
this error occurs frequently it may indicate a
problem with WebSphere Voice Response. Stop
the VOIP signalling process trunk state machine.
Detailed information on the error is logged. The
Custom Server Manager menu option. If this
trunk on which the error occurred is disabled
does not work, shut down and restart WebSphere
after any active calls on it have been cleared and
Voice Response. If none of the above is successful
its channels disabled.
call IBM Support.
Severity: Yellow
errors within the VOIP signalling process, which
may identify the origin of the error. If this error Destination: Log, System Monitor

29811 • 29816
disabled after any active calls on it have been

29811 VOIP signalling process
cleared and its channels disabled.
environment services error
Explanation: A call to the environment services
codes are logged. If the error description is
"es_init_failed" and the environment service is 29,
If this does not work, shut down and
you are trying to run two instances of the VOIP
custom server.
User response: Check the Custom Server
Severity: White
Monitor window to see if you have more than
one VOIP custom server running. Check the Destination: Log
error log for related errors originating from the
environment services. If this error occurs
frequently it may indicate a problem 29814 VOIP signalling process could not
withWebSphere Voice Response . Stop and restart start Layer 3
the signalling process using the Custom Server Explanation: The VOIP signalling process could
Manager menu option. If this does not work, not run the executable file for Layer 3. The
shut down and restart WebSphere Voice process has terminated.
IBM Support. User response: Call IBM Support.
Severity: Yellow Severity: Red
29812 VOIP signalling process internal 29815 VOIP call state machine invalid
error primitive
Explanation: An unexpected error occurred in Explanation: The VOIP signalling process call
the VOIP signalling process. Detailed information state machine received an unexpected primitive.
about the error is logged. This means that the primitive could not be
identified or that the primitive was not expected
User response: If this error occurs frequently it in the current state of the call.
Response. Stop and restart the signalling process User response: If this error occurs frequently it
using the Custom Server Manager menu option. may indicate a problem with WebSphere Voice
If this does not work, shut down and Response. Stop and restart the signalling process
restartWebSphere Voice Response . If none of the using the Custom Server Manager menu option.
above is successful call IBM Support. If this does not work, shut down and
Severity: Yellow above is successful call IBM Support.
29813 VOIP signalling process buffer
allocation retry
29816 VOIP channel state machine
Explanation: The VOIP signalling process invalid primitive
cannot obtain an environment services buffer.
Detailed information about the error is logged. Explanation: The VOIP signalling process
The trunk on which the error occurred is channel state machine received an unexpected

29817 • 29821
primitive. This means that the primitive could Severity: Yellow

not be identified or that the primitive was not
expected in the current state of the channel.
29819 VOIP signalling process channel
error
using the Custom Server Manager menu option. Explanation: The VOIP signalling process
If this does not work, shut down and detected an internal error on the channel. The
restartWebSphere Voice Response . If none of the signalling process will attempt to clear any
above is successful call IBM Support. existing call on this channel before disabling it.
Severity: Yellow User response: If this error occurs frequently it
Response. Re-enable the channel from the system
monitor window. If this does not work, shut
29817 VOIP trunk state machine invalid down and restartWebSphere Voice Response . If
primitive none of the above is successful call IBM Support.
Explanation: The VOIP signalling process trunk Severity: Yellow
state machine received an unexpected primitive.
This means that the primitive could not be
identified or that the primitive was not expected
in the current state of the trunk. 29820 VOIP signalling process trunk
error
may indicate a problem with WebSphere Voice Explanation: The VOIP signalling process
Response. Stop and restart the signalling process detected an internal error on the trunk. The
using the Custom Server Manager menu option. signalling process will attempt to clear existing
If this does not work, shut down and calls on this trunk before disabling it.
above is successful call IBM Support. User response: If this error occurs frequently it
Severity: Yellow Response. Re-enable the trunk from the system
monitor window. If this does not work, shut
down and restartWebSphere Voice Response . If
29818 VOIP signalling process invalid
Severity: Red
primitive
Explanation: The VOIP signalling process
received a primitive it could not identify. This
error is usually reported by the primitive to 29821 VOIP signalling process detected
event mapper as the state machines have their SIP Layer 3 termination
own errors defined for this situation.
Explanation: The VOIP signalling process
User response: If this error occurs frequently it detected that there is no longer a Layer 3
may indicate a problem with WebSphere Voice process. The signalling process will attempt to
Response. Stop and restart the signalling process clear existing calls on this trunk before disabling
using the Custom Server Manager menu option. it. If you are running in an NFAS system, all the
If this does not work, shut down and active trunks will be disabled.
above is successful call IBM Support. User response: If this error occurs frequently it

29822 • 29826
Response. Re-enable the trunk from the System has either not been found or has properties set so
Monitor window. If this does not work, shut that it cannot be opened for reading.
down and restartWebSphere Voice Response . If
User response: Check for the presence of the
SIP Header Configuration File and that it has
Severity: Red properties such that WebSphere Voice Response
can read it. If it does not, quiesce any active calls
on VOIP trunks, set read access for
siphdrtags.cfg and restart the SIP_VOIP custom
29822 VOIP signalling process cannot server. If this does not solve the problem, or if
make call on alarmed trunk the file does not exist, call IBM Support.
Explanation: The VOIP signalling process Severity: Yellow

detected that the trunk on which a call setup
attempt was made is alarmed. No calls can be
made on a trunk on which there are one or more
alarms. 29825 SIP Register Failed To Contact
Registrar
User response: Wait for the alarm to clear
before attempting to make the call again. If the Explanation: The SIP Register process cannot
call fails to establish once the alarm has cleared, register a SIP address at this machine with a
check the error log for other errors in the registrar because a registrar cannot be contacted.
signalling process. If the problem persists, stop The registrar is likely to be out of service.
and restart the signalling process using the Further contact problems with this registrar will
Custom Server Manager menu option. If this not be alarmed until a successful contact is
does not solve the problem, shut down and made.
User response: Check that the Ethernet network
is operating correctly, and that the registrar is
Severity: Yellow operational. Check the register configuration files
in the $SYS_DIR/voip/ directory for mistakes.
If you are using TLS to connect securely, ensure
that you have added the appropriate key to the
29823 Ethernet not in sync
keystore at $SYS_DIR/voip/keyring.db. You need
Explanation: The DTEA adapter cannot detect a either the key the registrar is using or a parent
valid ethernet signal. key of that key.
User response: Check that the ethernet network If none of the above is successful, call IBM
is operating correctly and that WebSphere Voice Support.
Response is correctly configured. Then attempt to
Severity: Red
re-enable the trunk. If this does not solve the
problem, shut down and restartWebSphere Voice Destination: Log, System Monitor
Response . If none of the above is successful then
call IBM Support.
29826 SIP Register can contact registrar
Severity: Red again
Destination: Log, System Monitor Explanation: The SIP Register process can now
contact the SIP registrar that could not be
contacted earlier. Normal register requests to this
29824 Unable to access SIP Header
registrar should now continue.
Configuration File
User response: You can now disregard the
Explanation: The SIP Header Configuration File

29827 • 29831
associated 29825 RED alarm message. User response: Fix the configuration files as
directed by the error code. The master.ini file is
Severity: Green
in $SYS_DIR/voip/ directory.
Severity: Yellow
29827 SIP Register Started
Explanation: The SIP Register process has
29829 VoIP SIP Layer 3 Has Terminated
started up and has contacted at least one
registrar. Calls directed from one or more Explanation: The VOIPL3_SIP process has
registrars can now be expected. terminated unexpectedly. This indicates a severe
error and should be reported to IBM Support.
User response: If you expected this to happen,
WebSphere Voice Response will attempt to restart
ignore this notification. If you have not yet
layer 3. If successful, a green alarm will be
configured the registrars, refer to the .ini files in
raised.
the $SYS_DIR/voip/ directory.
User response: Check if Layer 3 has recovered
Severity: White
with a 29830 alarm. It is likely that a core file
Destination: Log, System Monitor that will be of use in diagnosing the problem has
been written to the /var/adm/ras/dirTalk/
directory. Please contact IBM Support for advice.
29828 SIP Register Failed To Parse .ini
Files Severity: Red
Explanation: The SIP Register process failed to Destination: Log, System Monitor
parse the .ini files located in the $SYS_DIR/voip/
directory. See below for the line # and file being
29830 VoIP SIP Layer 3 Has Successfully
read. Error codes are as follows:
Restarted
1. Registrar line needs an IP address or
hostname. Explanation: The VOIPL3_SIP process has
restarted after being terminated. The system
2. IniFile line must supply a file to read.
should now be capable of taking calls again.
3. Too many .ini files in one registrar
definition. User response: Investigate the cause of
abnormal termination by examining any core file
4. Port line must be supplied a number.
recently written to the /var/adm/ras/dirTalk/
5. Timeout line must be supplied a number. directory. It is likely that such a core file will be
6. UserAgent line must be supplied a string. of use in diagnosing the problem. Please contact
7. Semicolon encountered not terminating a IBM Support for advice.
registrar. Severity: Green
8. Error loading from a .ini file defined in
registrar, see trace for details.
9. Unrecognized format of line.
29831 VoIP SIP Layer 3 Will Not Be
10. Registrar declared without closing open
Restarted
registrar. Most likely missing terminating
line of a semi-colon. Explanation: The VOIPL3_SIP process has
11. Last registrar in file not terminated. terminated five times within a minute, indicating
an issue that is systematically killing the process
12. TraceLevel needs a value.
every time that it is comes back up. WebSphere
13. Priority line must be supplied a number. Voice Response will not attempt to restart the

29832 • 29834
process again until WebSphere Voice Response is sockets library failed to start up. Secure
restarted. connections will not be possible for VoIP sockets
until this is resolved.
Response to allow calls again. Please contact IBM User response: Check that the
Support for further assistance. file $SYS_DIR/voip/keyring.db has been
generated. Check that the folder/usr/lib/gskit
Severity: Red
exists and contains files that are readable and
Destination: Log, System Monitor executable by the user used to run WebSphere
Voice Response, typically dtuser. Check that the
file $SYS_DIR/voip/ciphers.ini exists and is
29832 Allowed Hosts List Could Not Be readable by the user used to run WebSphere
Read Voice Response. If the permissions are incorrect,
Explanation: You have selected the change them and restart WebSphere Voice
configuration option Use Allowed Host List, but Response. If this does not resolve the issue,
the file $SYS_DIR/voip/allowedHostList.ini please contact IBM Support.
could not be read. Severity: Red
User response: Please check that the Destination: Log, System Monitor
$SYS_DIR/voip/allowedHostList.ini file is
present, and readable by the WebSphere Voice
Response user, then disable all VoIP trunks
before re-enabling them.
Severity: Red
29833 Call Rejected From Forbidden IP

Address
Explanation: The Allowed Hosts configuration
option has been set, and a caller from an IP
address not allowed by the $SYS_DIR/voip/
allowedHostList.ini file has tried to call
User response: Check that the IP Address noted
below is not supposed to be allowed to call into
this machine. If necessary changes may be made
to the allowedHostList.ini file in the
$SYS_DIR/voip directory. Changes will not take
effect until all VoIP trunks are disabled, then
enabled
Severity: Yellow
29834 Secure Socket Library Failed To

Start
Explanation: The environment for the secure

30000 • 30005
SS7
30000 SS7 Unclassified Alarm
Explanation: An unclassified SS7 Alarm has
30003 D7 Configuration Problem
been detected..
Explanation: There is configuration confliction
User response: If these messages occur on a
between this SS7 Cluster and the Network. When
regular basis and the Description does not make
this machine attempts to reference a circuit (see
clear what the problem (if any)is then refer to
CIC ref below) the Network reports that it was
IBM Support.
no configuration for that circuit or that it is
Severity: Yellow Unequiped.
Destination: Log, System Monitor User response: Check the configurations of the
SS7 cluster if they have changed recently
otherwise contact Network operator to confirm
30001 D7 software component failure
circuit configuration.
Explanation: The SS8-D7 software component
Severity: Red
has reported a failure.
User response:
User response: This may be due to a
30004 Internal D7 error detected
component failure if the Distributed 7 network or
that not all the component are in service. Check Explanation: The Distributed 7 system has
the Distributed 7 network. If any configuration reported a conflict between its internal states and
change have taken place recently then check message being received. In most cases
these values are correct and have been Distributed 7 is waiting for a message event
distributed to the relevant components. either from Custom Server SS7_D7 or must
probably the Network.
Severity: Red
User response: The most probably cause for
these message is a SS7 link failure or a failure at
the remote end (Switch). If original problem has
30002 D7 request rejected. been resolved but these message are still
appearing then restart the SS7_D7 custom server
Explanation: The Distributed 7 component has and if that fails restart the Distributed 7
rejected a request component.
User response: This may be due to a Severity: Yellow
component failure in the Distributed 7 cluster or
component on this machine is not in service. An Destination: Log, System Monitor, Alertable
error in the area of ISUPD or Network demon
suggests that Distributed 7 is not running. Check
30005 Unhandled SS7 Message
the Distributed 7 network. (i) If any
configuration changes have taken place recently Explanation: The SS7_D7 custom server has
then check these values are correct and that all received a message from the Distributed7
components have been activate. (ii) Check that package for which it has no code to handle it.
D7 component "isupd" is running if not This may have occurred due to a new signalling
investigate why. variant being used.
Severity: Red User response: These messages need to
analysed and may be connected with a different

30006 • 30011
characteristic of the Network that Distributed7 it operation. If there are further problems now stop
connected to. If these messages are occurring on and restart the SS7_D7 custom server. If these
a regular basis or are believed to be causing call message keep appearing on a regular basis then
failure then seek IBM support. An trace capture seek IBM support. An event capture will be
will be required by IBM to analysis this problem required by IBM to analysis this problem - refer
- refer to the SS7 User's Guide book to find out to the SS7 User's Guide book to find out how to
how to obtain one of these. obtain one of these.
Severity: White Severity: Yellow
30006 Missing SS7 Parameter 30009 State Table Alarm Reported

Explanation: The Custom Server SS7_D7 was Explanation: This alarm has been generated by
not able to find a critical parameter in a SS7 the Signalling State Table because it has found an
message. This means the underlying action will invalid sequence of messages. The description
have failed and may mean calls are being below will indicate the nature of the problem.
rejected.
User response: This alarm is a warning and the
User response: Check the remote switch is Signalling State Table would how corrected the
configured for the same operation as condition. How there may be other alarm
Distributed7. messages relating to the same problem which
should be handled appropiately.
Severity: Yellow
Severity: Yellow
30007 Invalid SS7 Parameter
30010 State Table detected bad
Explanation: An IE within a SS7 message
parameter
received by SS7_D7 has been found to be invalid
or out of range. Explanation: The SS7_D7 custom server has
detected a problem in the internal design of the
User response: If these messages are appearing
Signalling State Table.
on a regular basis then seek IBM Support.
User response: This should be reported to IBM
Severity: Green
for assistance. An trace capture will be required
Destination: Log, System Monitor, Alertable by IBM to analysis this problem - refer to the SS7
User Guide book to find out how to obtain one of
these.
30008 Unhandle State Table Component
Severity: Yellow
Explanation: The Signalling State Table has
reported one of the following conditions:- - State Destination: Log, System Monitor, Alertable
and Stimulus match cannot be found - missing
condition data. - missing action routine. This
30011 Signalling Library rejecting
implies that an unexpected sequence of messages
requests
have been received from Distributed7 and the
Network. Explanation: The WVR Signalling Library has
rejected a message sent to it by the SS7_D7
User response: If these messages occurred
Custom Server.
during bring the SS7 cluster into service after
problem in the network, then check for correct User response: This is most probably due to

30012 • 30017
WVR and the Network performing operations at identify which configuration file has a problem.
the same time. For example both WVR and caller Review the contents of the associated file and
terminating the call at the same time. If this is correct.
the case then these should be rare and
Severity: Green
infrequent. However, if this is not the case then
investigate the health of the WVR and analysis Destination: Log, System Monitor, Alertable
any other alarm message being generated.
Severity: Yellow 30015 Configuration Error Detected
Destination: Log, System Monitor, Alertable Explanation: In loading and processing the
configuration information an item has been
found to be invalid.
30012 Unhandled Signalling Library
Message User response: The Description field will
identify the configuration file has the problem.
Explanation: The SS7_D7 custom server has
Review the contents of that file and correct.
received a message from the WVR Signalling
Library which it did not expect and cannot been Severity: Green
handled.
User response: If there has been a recent
installation or upgrade check that all components
have been correctly installed. 30016 Configuration Parameter Error
Detected
Severity: Yellow
Explanation: In loading and processing the
Destination: Log, System Monitor, Alertable configuration information a parameter of an item
has been found to be invalid or out of range.
30013 Invalid Data Item User response: The Description field will
identify the configuration file which has the
Explanation: An internal data item has been
problem. Review the contents of that file and
found to be invalid or out of range.
correct.
User response: Check for failure of other
Severity: Green
components with in the system and fix as
necessary. However if no other problem is found Destination: Log, System Monitor, Alertable
then seek IBM support. An trace capture will be
required by IBM to analysis this problem - refer
to SS7 User's Guide book to find out how to 30017 Configuration Translation failure
obtain one of these. Explanation: A request has been made to
Severity: Yellow translate a value. However the associated
configuration table does not have sufficient
Destination: Log, System Monitor, Alertable information to perform the operation.
User response: The Description field will
30014 Configuration Overflow identify the configuration file which has the
Condition problem. Review the contents of that file and
correct.
Explanation: In loading and processing the
configuration information one of the following Severity: Yellow
conditions of occurred. - a duplicate item. - too
many in a list of items. Destination: Log, System Monitor, Alertable
User response: The Description field will

30018 • 30025
User response: Normal operation - no action

30018 Configuration Information not
required
Loaded
Severity: White
Explanation: No configuration information has
been detected and therefore not loaded. This Destination: Log, System Monitor, Alertable
suggests that the custom server has been
restarted before configuration distribution has
been completed during installation 30022 Internal Overflow
User response: Complete configuration and Explanation: A situation has occurred where too
restart Custom Server SS7_D7. many items have been attempted to be stored
internally resulting in lost of data due to it being
Severity: Red discarded..
Destination: Log, System Monitor, Alertable User response: If possible collect an Event log
and seek IBM support. Refer to theSS7 User's
Guide book about capturing an Event log.
30019 System Problem
Severity: Yellow
requested that the operating system perform an Destination: Log, System Monitor, Alertable
action, but has been rejected.
User response: Examine any other critical 30023 Problem in processing TAGS
conditions that have occurred recently within the
same computer and correct. Otherwise a system Explanation: A problem has occurred in
restarted may be required as O/S resources may processing the TAGS information within a WVR
no longer be available. Signalling Library message in one of the
following cases - Message received from an
Severity: Red application. - A message being generated to send
to an application.
User response: If a configuration change has
been performed recently then review these
30020 Missing Parameter in SS7
changes. If not then examine the application
message
program.
Explanation: An expected parameter within a
Severity: Yellow
SS7 message was not found.
User response: This may be due to an incorrect
network variant being applied. Check the
configuration of Distributed7 and compare with 30024 SS7 Link Activate
the Network connected to the SS7 Link.
Explanation: The system reports that at all the
Severity: Yellow SS7 links are in a DOWN state. While in this
state no calls will be received or delivered.
User response: Investigate why the SS7 Link are
in the Down state and correct as necessary.
30021 Shutting down SS7 Component.
Severity: Red
Explanation: An external request has been
made to the SS7_D7 custom server to perform a Destination: Log, System Monitor, Alertable
shutdown.
30025 SS7 Link Activate

30026 • 30032
Explanation: The system reports that at least Explanation: The Distributed7 package has
one of the SS7 Links is in an up and activate reported a timer expiring within the SS7 stack. It
state. was expected a message from the Network
which has not bee received within the expect
User response: No action required.
time.
Severity: Green
User response: This may be as a result of
Destination: Log, System Monitor, Alertable previous SS7 communication problem (i.e. link
failure) in which case these can be ignored.
Althernatively there may be a fault in the
30026 Invalid Signalling Library Network and the Network operator shoiuld be
parameter contacted. Also examine other error messages for
Explanation: A message received from the WVR a similar cause.
Signalling Library has a parameter which is Severity: Green
either invalid or out of range.
User response: If there has been a recent
installation or upgrade then check that all
components have been successfully installed. 30030 Custom Server Manager Rejected
Request
Severity: Yellow
Explanation: The Custom Server Manager has
Destination: Log, System Monitor, Alertable rejected a message request.
User response: If the text below suggests that
30027 D7 Environment problem the Custom Server is already running then wait
Explanation: The Distributed7 package has 30 seconds and try again. Otherwise, if a recent
reported an environmetal problem. upgrade and installation has taken place then
check all relevant components have been
User response: Seek IBM Support. installed successfully.
Severity: Red Severity: Green
30028 DTTA Loopback 30031 SS7 Test Call

Explanation: A request has been made to Explanation: The SS7 Network has placed an
perform a traffic loopback on a given circuit has inbound Test call. This will have overriden any
failed. out of service indication that might be in place
User response: If the circuit is not based on a for the given circuit.
DTTA card then the configuration needs to be User response: No action is necessary. However
reviewed as the Loopback facility is only as by the nature of a Test Call that can bypass an
supported on these cards. However if the circuit out of service indicator it may explain why other
is on a DTTA card then review and act on any errors might have occurred.
other Alarm being detected by the DTTA card.
Severity: White
Severity: Red
30032 Distributed 7 - Internal

30029 D7 SS7 Timer problem component failure.

30033 • 30040
Explanation: The Distributed7 library has

30036 SS7 Processor Started.
rejected an operation.
Explanation: The SS7_D& custom server process
User response: Check the current health of
has been started.
Distributed7 package both on this machine and
connected SS7 Servers. Refer to the SS7 User's User response: This is an information message
Guide book for using commands such as ebs_ps and no action is required.
and AccessMonitor.
Severity: White
Severity: White
30037 SS7 Monitor.
30033 Application Tags problem.
Explanation: A problem has been found in detected a potential problem within the WVR
analysing the Tags supplied by an application environment.
program.
User response: Review the information below
User response: Review the application program and correct as necessary..
sending these tags in light of the information
Severity: Green
supplied below.
Severity: Yellow
30038 SS7 Environment Problem.
30034 Application Tags problem.
found problems during its initialisation phase
Explanation: A value passed in a Tag is invalid regarding its environment.
for the SS7 operation.
User response: Analyses the information below
User response: Review the application program and correct has necessary.
sending these tags in light of the information
Severity: Red
supplied below.
Severity: Yellow
30039 SS7 Environment Problem.
Explanation: Distributed7 has reported a
30035 SS7 Child death.
problem with accessing the MTP Layer.
Explanation: The SS7 Stay-Alive facility has
User response: This normally occurs when
detected the death of the SS7_D7 custom server.
WVR/SS7 is started and cannot access the SS7
User response: No immediate remedial action is Servers. Check the operation state of the SS7
required as the Stay-Alive facility will have Servers.
restarted the SS7 process. However if this
Severity: Yellow
message is appearing on a regulate basis then the
cause needs to be analysed. Destination: Log, System Monitor, Alertable
Severity: Yellow
30040 SS7/MTP Environment Problem.

30041 • 30047
Explanation: Distributed7 has reported that the

30044 SS7/ISUP Pre-defined parameter
MTP layer is down.
Bank.
Explanation: A request to use a pre-defined
ISUP parameter has failed because it could not
Servers. Check the operation state of the SS7
be located.
Servers.
User response: Check the following to identify
Severity: Yellow
the cause. (i) Check the ISUP ISUPPARM tag in
Destination: Log, System Monitor, Alertable description below. (ii) Check the the
ISUPPARM.cfg as the present. (iii) Check that
SS7_D7 Custom Server has been restarted since
30041 SS7/MTP Environment Problem. any change to ISUPPARM.cfg
Explanation: Distributed7 has report that the Severity: Green
MTP layer is down.
Servers. Check the operation state of the SS7 30045 E1/T1 - Mixed Trunk Standards.
Servers.
Explanation: The SS7 Custom Server has been
Severity: Green asked to initialise Circuit 25+ on a T1 Traffic
bearer.
User response: This suggests there is a
confusion to whether this machine is T1 or E1.
30042 SS7/MTP Environment Problem. Review the WVR Pack Configuration or the
Explanation: Distributed7 has reported that the SS7itty configuration as necessary.
MTP layer is down. Severity: Red
User response: This normally occurs when Destination: Log, System Monitor, Alertable
Servers. Check the operation state of the SS7
Servers. 30046 Remote SS7/WVR failure.
Severity: Green Explanation: This WVR has been requested by
the Distributed7 system to manage the CIC range
Destination: Log, System Monitor, Alertable listed below. This is as a result of another WVR
nolonger being able to service these ranges. This
30043 SS7/ISUP Environment Change. circuit range will be taken out of service and all
active calls released.
Explanation: Distributed7 has reported has
reported a change in ISUP Service state. User response: Identify which WVR is in a
failure condition and take remedial action as
User response: This message normally occurs necessary.
when Distributed7 has gone through a general
service change. Investigate the health of the SS7 Severity: Yellow
Servers and Network if the change was not Destination: Log, System Monitor, Alertable
expected.
Severity: Green 30047 Remote SS7/WVR recovery.
Destination: Log, System Monitor, Alertable Explanation: The trunks listed below being
supervised by this WVR on behave of another

30048 • 30105
WVR have now been returned to the origitating

30102 Distributed 7 Busy.
WVR as it is now in an operational state.
Explanation: An attempt to enable a trunk
User response: No action is required.
failed due to Distributed7 being busy processing
Severity: Green a stop message and synchronising because of a
prior problem..
User response: Wait a few moments and retry
enabling the trunk. If the problem still persists
30048 D7WVRErrorReport Custom then correct the SS7 Link and remote switch.
Server
Severity: Green
Explanation: The D7WVRErrorReport Custom
Server has terminated because the Distributed7 Destination: Log, System Monitor, Alertable
package is no longer running.
User response: Investigate why the Distributed7 30103 Receive Inbound call when
package is not running and once corrected restart blocked.
D7WVRErrorReport through the CS manger GUI
Explanation: SS7_D7 Custom Server has
Severity: Red received a request for Call Setup for a circuit
which is out of service. This request has been
Destination: Log, System Monitor, Alertable ignored.
User response: It is possible that the inbound
30100 SS7 - Distributed 7 Not ready. call request was queued before the out of service
Explanation: An attempt has been made to had been processed. In which case this can be
enable a WVR Trunk before the Distributed7 ignored. However if this is a repeating problem
package is ready. then put the circuit back into service and then
out again.
User response: Check the current state of the
SS7 Links and attempt re-enabling the Trunks. Severity: Green
Severity: Red Destination: Log, System Monitor, Alertable

30104 Inbound call for a seized circuit.
30101 Distributed7 Initialisation Explanation: An inbound Call Setup request

Problems.. has been received for a circuit which already has
a call present. This probably due to a glare
Explanation: During the initialisatiin phase of situation (Inbound call meet an Outbound Call).
SS7_D7 Custom Server, the Distributed7 package The New inbound call will be rejected.
reported problems with a SS7 message or a
sequence of SS7 messages. User response: No action required.
User response: Check the SS7 Link and the Severity: Green
associated remote switch. If the problem was Destination: Log, System Monitor, Alertable
initiated by a prior problem which has now been
solved then the SS7_D7 Custom Server may need
to be restarted. 30105 SS7 Continuity test failed.
Severity: Red Explanation: The network has requested a
traffic loop back continuity test on a circuit. The
Destination: Log, System Monitor, Alertable Lop-back operation has failed. This is always be

30106 • 30113
the case for Websphere voice Response which do SS7 system and WVR configuration. A possible
not use DTTA. area of confusion may be between E1 and T1
Trunks.
User response: If the WebSphere Voice
Response is using DTTA and it was expected to Severity: Red
pass the test then check the Traffic Bearer trunks
connection WebSphere Voice Response. If these
have been interchanged then the physical circuit
will not have had the correct loop back applied. 30111 SS7 Error message for
non-bearing circuit
Severity: White
received a request from Distributed7 which
relates to a non-bearer circuit (Frame or
30106 SS7 Message re-synch problem. Signaling). This message will be ignored.
Explanation: SS7_D7 Custom Server is in the User response: No action as this message has
process of re-synching the messages between probably occured as a result of a previous
Distributed7 and WVR, when a message was problem..
received from the WVR Signaling Library.
Severity: Red
User response: No action, although it may take
a couple of messages to correct.
Severity: Green
30112 Block Pending SS7 Error message
received a SS7 Error message while waiting for
30109 Signaling Library message for acknowledgement to an out of service request.
non-bearing circuit
User response: If the out of service request
Explanation: SS7_D7 Custom Server has failed then then try again.
received a request for the WVR Signaling library
Severity: Red
which relates to a non-bearer circuit (Frame or
Signaling). This message will be ignored. Destination: Log, System Monitor, Alertable
User response: Check the configuration of the
SS7 system and WVR configuration. A possible 30113 Distributed7 has issued a circuit
area of onfusion may be between E1 and T1 reset
Trunks.
Explanation: Distributed7 has found contention
Severity: Red between components in the SS7 Stack and the
Network. To recovery from this problem it has
issued a Circuit Reset.This may have result in the
early termination of a call that may have been
30110 SS7 message for non-bearing present on the circuit.
circuit
User response: No direct action is required.
Explanation: SS7_D7 Custom Server has However if these messages appear on a regular
received a request from Distributed7 which basis then the Network's SS7 variant need to be
relates to a non-bearer circuit (Frame or compared with the SS7 Variant used in
Signaling). This message will be ignored. WebSphere Voice Response.
User response: Check the configuration of the Severity: Red

30114 • 30210

30202 SS7 Stack D7 - reports major alert
Explanation: This is an alert report from the
30114 Distributed 7 reports a Message
Distributed 7 package indicating a non-specific
Seq. error.
major condition within the D7 cluster has
Explanation: The SS7 Stack - Distrbuted7 has occurred.
report an error relating to a message received
User response: Examine the description field
from this customer server or the network. This
below and if necessary cross-reference with the
message was not expected for the current
D7 reference given below with the relevant
operation the circuit is performing.
documentation. A major condition within the D7
User response: If these are regular occurance cluster suggest a temporary loss of facility and
message then the message sequence needs to be should be investigated.
analysed to ensure the network variant matches
Severity: Yellow
WVR configuration. If there has been a resent
link failure then this message can be ignored. Destination: Log, System Monitor, Alertable
Severity: Yellow
30203 SS7 Stack D7 - reports critical
alert
30200 SS7 Stack D7 - reports info alert
Explanation: This is an alert report from the critical condition within the D7 cluster as
Distributed7 package indicating a non-specific occurred.
information condition within the D7 cluster has
occurred.
User response: Examine the description field D7 reference given below with the relevant
below and if necessary cross-reference with the documentation. This suggest that there has be a
D7 reference given below with the relevant critical component failure with the cluster and
documentation. This alert report suggests one of service is now impaired.
the following:- (i) Change of condition or state of
Severity: Red
a machine (ii) Recovery from an early problem.
Severity: Green
30204 SS7 Stack D7 - reports fatal alert
30201 SS7 Stack D7 - reports minor alert
Explanation: This is an alert report from the fatal condition within the D7 cluster has occurred
Distributed7 package indicating a non-specific
minor condition within the D7 cluster has
occurred.
User response: Examine the description field documentation. The D7 must be shutdown and
below and if necessary cross-reference with the restarted to regain service.
Severity: Red
documentation.
Severity: Yellow

30211 • 30217
Explanation: This is an information alert User response: This is for information only - no
indicating that another machine within the response is required.
SS7/D7 cluster now has D7 activate on it. It is
Severity: Green
now able to communicate with the other
machines in the same cluster. Destination: Log, System Monitor, Alertable
User response: No action is required as this
information alert is a normal message received 30214 SS7 - Distributed 7 State Change
when a machine has been restarted.
Explanation: The Distributed7 package has
Severity: Yellow reported a change in operation status.
Destination: Log, System Monitor, Alertable User response: This is just a notification
message and response is not required unless the
state change was not expected.
Severity: White
Explanation: This is an critical alert indicating
that a machine within the SS7/D7 cluster can no Destination: Log, System Monitor
longer be accessed.
User response: If the machine was not planned 30215 SS7 - Distributed7 MTP Layer 2
to be removed from the cluster then investigate it problem
current health and restart as necessary. It is also
possible that the LAN connection between these Explanation: Distributed7 has reported a layer 2
machines could be faulty and may need problem within the cluster.
investigation. User response: If this link was originally
Severity: Red functioning correctly then check the physical
connection and the operation condition of the
Destination: Log, System Monitor, Alertable remote switching equipment. However if this is
the initial activation of the Link, check the items
mentioned above and the following parameters
30212 SS7/D7 Stack - Link/LSet down.
listed below of the problematic link. (i)
Explanation: This is reporting a DOWN Destination Point Code. (ii) SLC. (iii) Selection of
condition with a Link within a LinkSet. timeslot with the trunk.
User response: If this link is not planned to be Severity: Yellow
down, investigate the following:- (i) Physical
connection to the associated SS7 card. (ii)
Configuration state of the D7 associated with
Link. (iii) Health of the remote end of the SS7 30216 SS7 - Distributed7 MTP Layer 2
Link.. problem - Recovered
Severity: Yellow Explanation: Distributed7 has reported a layer 2
problem within the cluster has been recovered.
User response: No response if required..
30213 SS7/D7 Stack - Link/LSet Severity: Green
recovered.
Explanation: This is reporting a recovered
condition with a Link within a LinkSet.
30217 SS7 - Distributed7 Inter Machine
Heartbeat failure

30218 • 30224
Explanation: Distributed7 has reported a loss of a LINKSET is available.

Heartbeat between this machine and another.
Explanation: Distributed7 has reported that at
User response: If this message is as a result of least one Link in the associated LinkSet is
another machine within the cluster being available also making the Link Set available.
unavailable then other alarm messages will also
User response: No response necessary
be posted. However, if it is as a result of a LAN
failure and a second LAN is present then it will Severity: Yellow
takeover operations. Investigate the reason from
loss of machine or LAN. Destination: Log, System Monitor
Severity: Yellow
30221 SS7 - Distributed7 has report a
Destination: Log, System Monitor LINK is available.
Explanation: Distributed7 has reported that a
30218 SS7 - Distributed7 report a Link is now available. available.
LINKSET is DOWN
User response: No response necessary
Explanation: Distributed7 has reported that all
Links within a Linkset are in the down or failed Severity: Yellow
condition. Destination: Log, System Monitor
User response: If the condition was not
expected then the Links of the LinkSet should be 30222 SS7 - Distributed7 has report a
investigate to their failure condition. This could Destination as avaiable.
include (i) Check health of remote switch. (ii)
Check cabling and other physical connections. Explanation: Distributed7 has reported that a
(iii) Check any recent changes to the D7 underlying Linkset is now available and open for
configuration. (iv) Check health of D7 servers. Call Control. available.
Severity: Red User response: No response necessary

30219 SS7 - Distributed7 Inter Machine
Heartbeat failure 30223 SS7 - Distributed7 has report a
Explanation: Distributed7 has reported that a Destination is UNAVAILBLE.
Link is in the down or failed condition. Explanation: Distributed7 has reported that a
User response: If the associated LinkSet has underlying Linkset has no available Links and
additional/redundant links then WebSphere can nolonger support Call Control. available.
Voice Response will continue to support call User response: No response necessary
control. If the condition was not expected then
check the following (i) Health of remote switch. Severity: Red
(ii) Cabling and other physical connections. (iii) Destination: Log, System Monitor
Any recent changes to the D7 configuration. (iv)
Health of D7 servers.
30224 SS7 - Distributed7 has report
Severity: Red Congestion.
Destination: Log, System Monitor Explanation: Distributed7 has reported a
congestion situation on one or more of the SS7
30220 SS7 - Distributed7 has report the

links. This condition may result in lost or delay
call handling.
User response: Investigate the current call
volume and review to whether the current SS7
link capacity can meet its needs.
Severity: Yellow

30500 • 30505
Timeslot Management
30500 TDM connection management:
connection server error (log-only)
Explanation: A connection server logged an
connection server error (yellow)
error. The meaning is defined by the specific
connection server. Explanation: A connection server logged an
User response: Look at the error text for more
connection server.
explanation. If this does not clarify the cause of
the problem and possible user actions to remedy User response: Look at the error text for more
the problem, contact either IBM Support, or the explanation. If this does not clarify the cause of
provider of the connection server identified in the problem and possible user actions to remedy
the error log entry. the problem, contact either IBM Support, or the
provider of the connection server identified in
Severity: White
the error log entry.
Destination: Log
Severity: Yellow
connection server error (white)
connection server error (red)
connection server. Explanation: A connection server logged an
connection server.
explanation. If this does not clarify the cause of
the problem and possible user actions to remedy User response: Look at the error text for more
the problem, contact either IBM Support, or the explanation. If this does not clarify the cause of
provider of the connection server identified in the problem and possible user actions to remedy
the error log entry. the problem, contact either IBM Support, or the
provider of the connection server identified in
Severity: White
Severity: Red
connection server error (green)
30505 TDM connection management
error
connection server. Explanation: An error occurred in TDM
connection management.
explanation. If this does not clarify the cause of User response: Look at the error text for more
the problem and possible user actions to remedy explanation. If this does not clarify the cause of
the problem, contact either IBM Support, or the the problem and possible user actions to remedy
provider of the connection server identified in the problem, contact IBM Support.
Severity: Yellow
Severity: Green

30506 • 30511
update to fix the problem to avoid performance

or reliability problems.
configuration error
User response: Contact IBM Support to obtain a
Explanation: An error was discovered in the
fix for the problem, then apply this fix. The
configuration files for TDM connection
APAR number for the problem is specified in the
management resource groups.
detailed error log entry. A fileset name and
User response: Details of the file and line version which is known to fix the problem is also
number of the offending configuration are given specified.
in the error log entry. Examine this configuration
Severity: White
file, correct the errors, and restartWebSphere
Voice Response . Destination: Log, System Monitor
Severity: Red
30510 TDM connection management not
supported on this system
Explanation: TDM connection management
30507 Software error detected in TDM
aborted because it should not be run on this
connection management
system.
User response: This error can be generated
detected an internal inconsistency and could not
following a system restore using mksysb. If this
continue to execute.
occurs, you might find that no available trunks
User response: Contact IBM Support and are shown in the WebSphere Voice Response
provide them with this error log, and the core System Monitor. If, however, the results of
file which should be found in $VAEBIN. running the lsdev -C command show that the
adapter (DTTA) is in the Available state, run the
Severity: Red
dt_setowner command on ALL adapters as
Destination: Log, System Monitor follows: 1. Shutdown WebSphere Voice Response
by using the DT_shutdown comand. 2. Login as
root by entering the su command 3. Run
30508 TDM connection management dt_setowner (for syntax details specific to
aborted adapter type refer to the WebSphere Voice
Explanation: A software error caused TDM Response for AIX: Installation book).
connection management to exit unexpectedly. Severity: White
User response: A core file should be found in Destination: Log
$VAEBIN. Contact IBM Support and provide
them with this error log and the core file.
30511 TDM connection management
Severity: Red detected timeslot allocation
Destination: Log, System Monitor problem
30509 TDM connection management aborted startup of a TDM connection server
overcame AIX problem because it detected a clash between the source
port timeslot allocation of this connection server
Explanation: TDM connection management and a previously started connection server.
detected that a known AIX problem exists on this
system. A workaround has been installed so that User response: Contact the developer of the
WebSphere Voice Response can continue to failing connection server who should help you
operate. We recommend that you install an AIX determine why there is a clash between the

timeslot allocations for the two connection
servers.
Severity: White

31001 • 31009
Pack Configuration
31001 Configurator failed when writing 31005 Configurator: close ODM_class

to real-time database failed
Explanation: CFG received an invalid return Explanation: A call to odm_close_class has
code when updating the database during a save returned an error.
operation.
User response: Consult the error log file for
User response: Consult the error log for more more details. Message source: Configuration
details. Message source: Internal
Severity: Yellow
Severity: Yellow
Destination: Log
Destination: Log
31007 Configurator: open directory
31002 Configurator cannot initialize failed
ODM
Explanation: A call to opendir for the
Explanation: A call to odm_initialize has vocabulary directory associated with a VPACK
returned an error. has returned an error.
User response: Consult the error log for more User response: Consult the error log for more
details. Message source: Configuration details. Message source: Configuration
Destination: Log Destination: Log
31003 Configurator: lock of ODM failed 31008 Configurator: vocabulary name

not in ll_CC_nnnn format
Explanation: A call to odm_lock has returned
an error. Explanation: The vocabulary name specified
does not conform to the format ll_CC_nnnn,
User response: Consult the error log for more
where ll is a lowercase language code, CC is an
details. Message source: Configuration
uppercase country/region code, and nnnn is a
Severity: Yellow numeric identifier.
Destination: Log User response: Check the vocabulary directory

(/usr/lib/microcode/vocab), and remove files
with invalid names. Message source:
31004 Configurator: open ODM CuAt Configuration
class failed
Severity: White
Explanation: A call to odm_open_class for CuAt
class has returned an error. Destination: Log
User response: Consult the error log file for

more details. Message source: Configuration 31009 Configurator: vocabulary file has
same numeric identifier as
Severity: Yellow another
Destination: Log Explanation: File names in the vocabulary
directory must conform to the pattern

ll_CC_nnnn, where nnnn must be a unique
numeric identifier.
User response: Check the vocabulary directory
(/usr/lib/microcode/vocab), and remove files
with duplicate numeric identifiers. Do not
rename these files to change the nnnn number;
this will not solve the problem and may cause
more problems in future. If you have vocabulary
files with non-unique numeric identifiers, contact
IBM Support. Message source: Configuration
Severity: White
Destination: Log

32001 • 32005
Signaling Interface
channel signalling or a signalling process, you
32001 Signalling interface: task
can ignore this message. If you are using
initialization failed
common channel signalling or a signalling
Explanation: The WebSphere Voice Response process, frequent occurrences of this error can
signalling interface has failed to initialize indicate a problem within WebSphere Voice
successfully, and has terminated. The common Response. If the problem persists, call IBM
channel signalling processes (such as the Support.
Signalling System Number 7 Telephony User
Severity: Yellow
Part) are unable to function. Both outbound and
inbound calls are affected. Destination: Log, System Monitor
User response: Shut down and restart
theWebSphere Voice Response system. If the 32004 Signalling interface: polling error
Severity: Red signalling interface has encountered an error on a
poll() system call, and has terminated. This
means that common channel signalling processes
(such as the Signalling System Number 7
32002 Signalling interface: open device Telephony User Part (TUP)) are unable to
failed function. Both outbound and inbound calls are
affected.
signalling interface has failed to open a device it User response: If you are not using common
needed, and has terminated. Common channel channel signalling or a signalling process, you
signalling processes (such as ISDN) are unable to can ignore this message. If you are using
function. Both outbound and inbound calls are common channel signalling or a signalling
affected. If this is a machine in an SSI system process, you should shut down and
with no telephony, this will only affect you in as restartWebSphere Voice Response . If the problem
much as there will be no notification of abnormal persists, call IBM Support.
process termination by the signalling daemon.
Severity: Red
User response: Shut down and restart
theWebSphere Voice Response system unless
your machine is in an SSI system and has no
telephony, in which case you do not need to do 32005 Signalling interface: polling
anything. If the problem persists, call IBM unexpected results
Support.
Severity: Red signalling interface has received an unexpected
returned event from a poll() system call.
User response: If you are not using common
channel signalling or a signalling process, you
32003 Signalling interface: polling
can ignore this message. If you are using
timeout
common channel signalling or a signalling
Explanation: The WebSphere Voice Response process, you should shut down and
signalling interface has encountered a timeout on restartWebSphere Voice Response . If the problem
a poll() system call. persists, call IBM Support.
User response: If you are not using common Severity: Yellow

32006 • 32010
Destination: Log, System Monitor SL_CALL_ABORT_REQ primitive. (The Cause

field indicates the reason why an active call is
being cleared.) The signalling interface is
32006 Signalling interface: signalling
continuing.
library call failed
channel signalling or a signalling process, this
signalling interface detected an error when
error should not occur. If you are using common
invoking a signalling library subroutine. The
channel signalling or a signalling process,
signalling interface is continuing.
frequent occurrence of this error indicates a
User response: If you are not using common problem in WebSphere Voice Response. Shut
channel signalling or a signalling process, this down and restart WebSphere Voice Response. If
error should not occur. If you are using common the problem persists, call IBM Support.
Severity: Yellow
problem in WebSphere Voice Response. Shut Destination: Log, System Monitor
32009 Signalling interface: call cleared
Severity: Yellow by channel process failure
Destination: Log, System Monitor Explanation: The WebSphere Voice Response
signalling interface detected a channel process
failure while a call is active. The signalling
32007 Signalling interface: invalid data
interface has instructed the signalling process
received from device driver
that is responsible for the call to clear.
signalling interface detected invalid data in an
event received from the device driver. The
invalid data is the sizetLength field of the
SL_CALL_ABORT_REQ primitive. The signalling
interface is continuing.
problem in WebSphere Voice Response. Shut
User response: If you are not using common down and restart WebSphere Voice Response. If
channel signalling or a signalling process, this the problem persists, call IBM Support.
Severity: Yellow
frequent occurrence of this error indicates a Destination: Log, System Monitor
by silence detected on line
Severity: Yellow
Destination: Log, System Monitor signalling interface detected an extended period
of silence on the line, while recording voice. This
usually occurs because the caller has hung up, or
32008 Signalling interface: unknown
is not saying anything. In some countries
cause received from device driver
interactive voice response systems are required to
Explanation: The WebSphere Voice Response hang up when this happens. The signalling
signalling interface detected an unknown cause interface has instructed the signalling process
in an event received from the device driver. This that is responsible for the call to clear.
is caused by an error in the Cause field of the

32011 • 32014
User response: If you are not using common does NOT indicate an error inWebSphere Voice
channel signalling or a signalling process, this Response .
Severity: Yellow
message is for information only. Destination: Log, System Monitor
Severity: White
32013 Signalling interface: error event
with no signalling process
signalling interface detected that an error event
process termination detected
that requires a call to be cleared, but there is no
Explanation: The WebSphere Voice Response configured signalling process.
signalling interface detected that a signalling
process has terminated.
User response: If you are not using common error should not occur. If you are using common
channel signalling or a signalling process, this channel signalling or a signalling process,
error should not occur. If you are using common frequent occurrence of this error indicates a
channel signalling or a signalling process, this problem in WebSphere Voice Response. Shut
message is for information only. down and restart WebSphere Voice Response. If
Severity: White
Severity: Yellow
process failed to clear call 32014 Signalling interface: device driver
queue for CCS full
signalling interface detected that a signalling Explanation: The WebSphere Voice Response
process has failed to clear a call it was requested signalling interface has detected that the queue
to clear. The signalling process is required to which is used by some common channel
clear calls when WebSphere Voice Response signalling processes has overflowed. This queue
sends it the SL_CALL_ABORT_REQ primitive. is used only by Signalling System Number 7
This error indicates that the signalling process Telephony User Part and ISDN signalling
did not respond by sending the processes, but these will be unable to function.
SL_CALL_ABORT_CNF primitive with a reply Both outbound and inbound calls are affected.
code of SL_REPLY_SUCCESS.
User response: If you are not using common channel signalling or a signalling process, this
channel signalling or a signalling process, this error should not occur. If you are using ISDN
error should not occur. If you are using common this error indicates a problem in WebSphere
channel signalling or a signalling process, this Voice Response. Stop and restart the signalling
message indicates a serious error in your process using the Custom Server Manager menu
signalling process. If you are developing a option. If this does not resolve the problem, shut
signalling process, such as a Signalling System down and restart WebSphere Voice Response. If
Number 7 Telephone User Part (TUP), it must the problem persists call IBM Support.
support the SL_CALL_ABORT_REQ primitive. If
Severity: Red
you are using such a signalling process contact
the supplier of the TUP or other signalling Destination: Log, System Monitor, Alertable
process and report this problem. This message

32015 • 32018
error should not occur. If you are using a

32015 Signalling interface: obsolete
signalling process, this error indicates that your
SL_CALL_ABORT_CNF
signalling process has not been updated to take
Explanation: The WebSphere Voice Response account of a change introduced in IBM
signalling interface has detected that a signalling WebSphere Voice Response Release 1.5.
process has used an obsolete format of the Programmer response: The
SL_CALL_ABORT_CNF primitive. If this error SL_CALL_ABORT_CNF primitive was extended
occurs immediately after error 32010, a voice in IBM WebSphere Voice Response Release 1.5.
channel might also be blocked, and unavailable Update your signalling process to include the
for use until you shutdown and process ID of the originating channel process in
restartWebSphere Voice Response . the pidOriginalCHP field of the
SL_CALL_ABORT_REQ primitive. Failure to do
this means that it is not possible to terminate the
call when an extended period of silence is
error should not occur. If you are using a
detected. (Note: in the SL_CALL_ABORT_CNF
signalling process, this error indicates that your
primitive, the pidCHP field contains the process
signalling process has not been recompiled using
ID of the signalling daemon, not the channel
the latest header files supplied with WebSphere
process.)
Voice Response. Ensure that any signalling
processes are recompiled. Programmer response: Severity: Yellow
The SL_CALL_ABORT_CNF primitive was
extended in IBM WebSphere Voice Response
Release 1.5. Update your signalling process to
include the process ID of the originating channel 32017 Signalling interface: invalid trunk
process in the pidOriginalCHP field of the on alarm event from driver
SL_CALL_ABORT_REQ primitive. Failure to do
this means that it is not possible to terminate the Explanation: The WebSphere Voice Response
call when an extended period of silence is signalling interface has received an alarm event
detected. (Note: in the SL_CALL_ABORT_CNF from the WebSphere Voice Response device
primitive, the pidCHP field contains the process driver, which does not include a valid trunk. One
ID of the signalling daemon, not the channel of your trunks might be unusable because of the
process.) alarm condition.
Severity: Yellow User response: If you are not using common

Destination: Log, System Monitor error should not occur. If you are using common
channel signalling (ISDN or SS7) or a signalling
process, this error indicates a problem
32016 Signalling interface: invalid
inWebSphere Voice Response . If the problem
pidOriginalCHP on
persists, stop and restart the signalling process
SL_CALL_ABORT_CNF
Explanation: The WebSphere Voice Response If this does not resolve the problem, shut down
signalling interface has detected that a signalling and restartWebSphere Voice Response . If the
process has not specified a valid process ID with problem persists call IBM Support.
the SL_CALL_ABORT_CNF primitive. If this
Severity: Red
error occurs immediately after error 32010, a
voice channel might also be blocked, and Destination: Log, System Monitor
unavailable for use until you shutdown and
restartWebSphere Voice Response .
32018 Signalling interface: invalid
User response: If you are not using common channel on alarm event from
channel signalling or a signalling process, this driver

32019 • 32021
Explanation: The WebSphere Voice Response SL_TRUNK_ALARM_REQ primitive, which is

signalling interface has received an alarm event sent byWebSphere Voice Response to indicate
from the WebSphere Voice Response device that an alarm has occurred (or been cleared) on a
driver, which does not include a valid channel. trunk. This error indicates that the signalling
One of your trunks might be unusable because of process did not respond by sending the
the alarm condition. SL_TRUNK_ALARM_CNF primitive with a reply
code of SL_REPLY_SUCCESS.
channel signalling or a signalling process, this User response: If you are not using common
error should not occur. If you are using common channel signalling or a signalling process, this
channel signalling (ISDN or SS7) or a signalling error should not occur. If you are using common
process, this error indicates a problem channel signalling or a signalling process, this
inWebSphere Voice Response . Disable and message indicates a serious error in your
reenable the trunk using the System Monitor. If signalling process. If you are developing a
the problem persists, stop and restart the signalling process, such as a Signalling System
signalling process using the Custom Server Number 7 Telephone User Part (TUP), if your
Manager menu option. If this does not resolve signalling process registers support for trunk
the problem, shut down and restartWebSphere management
Voice Response . If the problem persists call IBM (SL_SIGPROC_CAPABILITY_TRUNK_MGMT) it
Support. must support the SL_CALL_ABORT_REQ
primitive. If you are using such a signalling
Severity: Red
process contact the supplier of the TUP or other
Destination: Log, System Monitor signalling process and report this problem. This
message does NOT indicate an error in
32019 Signalling interface: alarm event
with no signalling process Severity: Yellow
Explanation: The WebSphere Voice Response Destination: Log, System Monitor

signalling interface received an alarm for a trunk,
but there is no configured signalling process.
User response: If you are not using common by cadenced hang-up tone
signalling interface detected a cadenced hang-up
tone on the line. The signalling interface has
instructed the signalling process that is
responsible for the call to clear it.
the problem persists, call IBM Support. User response: If you are not using common
Severity: Yellow
Destination: Log, System Monitor channel signalling or a signalling process, this
message is for information only.
32020 Signalling interface: signalling Severity: White

process did not respond to alarm
signalling interface detected that a signalling
process did not respond to an alarm it was sent.
A signalling process capable of trunk
management must handle the

35000 • 35005
SpeechServer custom server

This section lists errors that can be issued by the SpeechServer custom server.
Errors are enrolled as standard custom server errors in the range 20500 to
20504. The SpeechServer error IDs are shown in parameter 5 of the standard
custom server error numbers.
With any of these errors, if you have followed the suggestions in the User
Response, restarted the SpeechServer custom server, restarted WebSphere
Voice Response, and you are unable to solve the problem, contact IBM
Support. When you call, have details of any errors, your system setup, and
details of the conditions that cause the problem. An AIX system trace taken
when the problem occurs may also be required. Before taking the trace, set the
-d option in the custom server. For more information on the command line
options see WebSphere Voice Response for AIX: Configuring the System.
Destination: Log
35000 SpeechServer queue has been
removed unexpectedly
35003 SpeechServer received invalid
Explanation: See “SpeechServer custom server.”
function request
User response: Restart the SpeechServer custom
server. If the error persists, restart WebSphere
Voice Response. User response: Restart the SpeechServer custom
Severity: Red (error_id= 20504)
Voice Response.
Severity: Yellow (error_id = 20502)
35001 SpeechServer failed to send
request
35004 SpeechServer CA_Get_Parameters
failed
Voice Response.
35002 SpeechServer has detected an
unknown error
35005 Reco channel table could not be
allocated for process
Explanation: See the introduction to these
server, if the error persists you should restart
messages.
Severity: White (error_id = 20501)

35006 • 35012
server. If the error persists, restart WebSphere Destination: Log

Voice Response.
Severity: Red (error_id= 20504) 35009 Call to CA_Get_Parameters failed
Destination: Log, System Monitor Explanation: See the introduction to these
messages.
35006 Error occurred while initializing User response: Restart the SpeechServer custom
protocol layers server. If the error persists, restart WebSphere
Voice Response.
Explanation: As the SpeechServer custom server
is initialized, it creates a connection management Severity: Yellow (error_id = 20502)
socket bound to the resource controller port
extracted from the configuration file. If this port
is not set, or is set to zero, the initialization fails.
35010 UseRecoTable command could not
User response: Check that the RECOCONF
be processed
environment variable is set to point to the correct
configuration file. Check that the port is set to Explanation: See the introduction to these
the “well_known” port of the remote voice messages.
server’s resource controller, which should be
non-zero. User response: Restart the SpeechServer custom
Severity: Red (error_id= 20504) Voice Response.
Destination: Log, System Monitor Severity: White (error_id = 20501)
Destination: Log
35007 Process could not allocate enough
memory
35011 A call to CA_Put_Parameters
Explanation: The SpeechServer custom server failed
requested memory from the system and the
request failed. Explanation: See the introduction to these
messages.
User response: Check that no unnecessary
processes are running in your system. If any are, User response: Restart the SpeechServer custom
close them down and restart the SpeechServer server. If the error persists, restart WebSphere
custom server. Voice Response.
Severity: White (error_id = 20501) Severity: Yellow (error_id = 20502)
35008 Acknowledgment was received 35012 Acknowledgment to request could

out of sequence not be sent
Explanation: See the introduction to these Explanation: See the introduction to these
messages. messages.
User response: Restart the SpeechServer custom User response: Restart the SpeechServer custom
server. If the error persists, restart WebSphere server. If the error persists, restart WebSphere
Voice Response. Voice Response.
Severity: White (error_id = 20501) Severity: White (error_id = 20501)

35013 • 35020
35013 Process could not add function to 35017 Process failed to open channel
timer queue
Explanation: See the introduction to these messages.
messages
User response: Restart the SpeechServer custom server. If the error persists, restart WebSphere
server. If the error persists, restart WebSphere Voice Response.
Voice Response.
Destination: Log
35018 Process has lost contact with
35014 Process exceeded timeout value resource controller
Explanation: See the introduction to these Explanation: All network traffic to the voice
messages. server’s resource controller has timed out.
User response: Restart the SpeechServer custom User response: Check that the voice server is
server. If the error persists, restart WebSphere still active and restart it if not. If the voice server
Voice Response. is active, check that your network does not have
a problem.
Destination: Log
35015 Recochannel could not be found
for referenced ID 35019 Packet could not be sent
messages. messages.
35016 All recochannels are in use 35020 File could not be opened
Explanation: More calls are being made to the Explanation: See the introduction to these
SpeechServer custom server than it can handle. messages.
User response: Increase the number of User response: Restart the SpeechServer custom
processes initially spawned by the SpeechServer server. If the error persists, restart WebSphere
custom server by increasing the appropriate Voice Response.
parameter in the configuration file, then restart
the custom server.
Destination: Log

35021 • 35029
35021 Stats for file could not be 35026 SpeechServer detected RECO
retrieved failure
Explanation: See the introduction to these Explanation: The remote voice server received
messages. enough data to perform recognition, but sent a
negative acknowledgment to indicate that a
problem occurred.
Voice Response. User response: Check that the voice recognition
units are active.
Destination: Log
35022 File could not be read
35027 Error occurred in SpeechServer
statistics collection
messages.
messages.
Voice Response.
Destination: Log
Destination: Log
35024 SpeechServer detected unexpected
channel error
35028 Error occurred in reco download
process
messages.
messages.
Voice Response.
35025 SpeechServer could not acquire
recochannel
35029 SpeechServer detected bad socket
or file handle
messages.
messages.
Voice Response.

35030 • 35037
35030 SpeechServer detected connection 35034 SpeechServer detected bogus

failure sequence number
messages. messages.
35031 SpeechServer detected bogus 35035 Channel not in correct state to

acknowledgment perform specified function
messages. messages.
35032 SpeechServer detected bogus 35036 Connection not correct type to

channel perform specified function
messages. messages.
35033 SpeechServer detected bogus 35037 Failure detected receiving on

command function connection
messages. messages .

35038 • 35045
35038 Failure detected sending on 35042 Failure detected

connection binding/connecting connection
messages. messages .
35039 Failure detected opening 35043 Failure detected changing

connection connection’s characteristics
messages. messages.
35040 Failure detected closing 35044 Failure detected accepting on

connection connection
messages. messages.
35041 Connection ID invalid 35045 Failure detected listening on

connection
messages. Explanation: See the introduction to these
messages.
server. If the error persists, restart WebSphere User response: Restart the SpeechServer custom
Voice Response. server. If the error persists, restart WebSphere
Voice Response.

35046 • 35053
Destination: Log Severity: White (error_id = 20501)

Destination: Log
35046 Maximum value for retry on this
operation exceeded
35050 Recognize command could not be
Explanation: The SpeechServer custom server sent
tried to send a particular packet more than the
maximum allowed value for the system.
messages.
User response: Check the network for increased
traffic. Check that the remote voice server is still
active.
Voice Response.
Destination: Log
35047 Reco process could not be

35051 Channel close command could not
allocated to receive request
be sent
messages.
messages.
Voice Response.
Voice Response.
35048 Reco channel deallocation did not

35052 Device voice channel already
complete successfully
open for this reco channel
messages.
messages.
Voice Response.
Voice Response.
35049 Invalid reco handle received for

35053 Device driver voice channel could
request
not be opened
messages.
messages.
Voice Response.
Voice Response.

35054 • 35061

35058 Could not find broadcast interface
Destination: Log, System Monitor to send IDENT message
Explanation: The SpeechServer custom server
35054 Device driver voice channel could makes initial contact with the resource controller
not be closed of the remote voice server by issuing a broadcast
message to the “well-known” port. To do this it
Explanation: See the introduction to these must extract the configured broadcast address
messages. from the interface.
User response: Restart the SpeechServer custom User response: Check that the interface name
server. If the error persists, restart WebSphere parameter specified in the configuration file is a
Voice Response. valid one. Given a valid interface name,
Severity: Red (error_id= 20504) type ifconfig interface_name on any AIX
command line, and the broadcast address should
Destination: Log, System Monitor be stated. If this is not the case, call IBM
Support.
35055 Error occurred in RTT function Severity: Red (error_id= 20504)
Explanation: See the introduction to these Destination: Log, System Monitor
messages.
User response: Restart the SpeechServer custom 35059 Could not find local interface
server. If the error persists, restart WebSphere address to send IDENT message
Voice Response.
Severity: White (error_id = 20501) messages.
Destination: Log User response: Restart the SpeechServer custom
35056 Select statement failed Voice Response.
Explanation: See the introduction to these Severity: Red (error_id= 20504)

messages. Destination: Log, System Monitor
server. If the error persists, restart WebSphere 35060 Could not find local interface port
Voice Response. to send IDENT message
Severity: White (error_id = 20501) Explanation: See the introduction to these
Destination: Log messages.
35057 Ioctl() call failed in routine named server. If the error persists, restart WebSphere
Voice Response.
messages. Severity: Red (error_id= 20504)
User response: Restart the SpeechServer custom Destination: Log, System Monitor
Voice Response. 35061 Connection to remote port
Severity: White (error_id = 20501) unexpectedly closed
Destination: Log Explanation: SpeechServer was in the process of

35062 • 35066
receiving information from across the network processes exceeded

when the remote voice server closed the
Explanation: The number of processes specified
connection.
in the parameter ‘reco_processes’ exceeds the
User response: Check that the remove voice value of the parameter ‘max_reco_proc’ in the
server is still active and restart it if necessary. configuration file.
Restart SpeechServer.
User response: Reduce the value of
Severity: Red (error_id= 20504) ‘reco_processes’ or increase the value of
‘max_reco_proc’.
35062 RESTART initiated but failed Destination: Log, System Monitor
messages. 35066 SpeechServer could not dump
voice data as requested
server. If the error persists, restart WebSphere Explanation: See the introduction to these
Voice Response. messages.
Severity: White (error_id = 20501) User response: Restart the SpeechServer custom
Destination: Log
Voice Response.
35063 Child process exited and could
not be restarted Destination: Log, System Monitor
Explanation: One of the SpeechServer child
processes has unexpectedly died. These should
be respawned automatically, but in this case, the
child could not be restarted.
User response: Check that the system is not
overloaded with processes. Kill any unnecessary
processes.
35064 Reco process not present

messages.
Voice Response.
35065 Maximum number of server

CP000 • CP006
CallPath_Sigproc Custom Server

This section lists errors that can be issued by the CallPath_Sigproc custom
server. Errors are enrolled as standard custom server errors in the range 20500
to 20504. The CallPath_Sigproc error ids are shown in parameters 1 and 2 of
the standard custom server error numbers.
Response, and you are unable to solve the problem, contact IBM Support.
When you call, have details of any errors, your system setup, and details of
the conditions that cause the problem. An AIX system trace taken when the
problem occurs may also be required. Before taking the trace, set the -d option
in the custom server. For more information on the command line options see
Explanation: Not issued.
CP000 Cannot configure server. Exiting...
User response: Not applicable.
Explanation: This custom server cannot be
configured because there are errors in the Severity: White (error_id = 20501)
confirmation parameters. This error is issued as a
result of one or more white errors. Destination: Log, System Monitor
User response: Correct the configuration error

then start the custom server. To see which CP004 Cannot close configuration file
parameters are causing the problem, look at the Explanation: Not issued.
white errors issued immediately before this error.
User response: Not applicable.
Severity: Red (error_id = 20504)
CP001 Bad switch in configuration file

CP005 Problem reading configuration
Explanation: Not issued. file
User response: Not applicable. Explanation: Not issued.
Severity: White (error_id = 20501) User response: Not applicable.
Destination: Log, System Monitor Severity: White (error_id = 20501)
CP002 Bad argument in configuration
file
CP006 Bad switch in command line
Explanation: An invalid command line switch
User response: Not applicable. was used to start the custom server. The invalid
Severity: White (error_id = 20501) command line switch is printed as one of the
parameters in this error.
User response: Correct the command line
switch. You can see the command line switches
CP003 Cannot open configuration file by selecting Properties from the File window for

CP007 • CP014
this custom server. Permitted command line Destination: Log, System Monitor
options are: -sn, -si, -st, -sc, and -d.
For more information on these command line CP010 Failed to register with signaling
options see WebSphere Voice Response for AIX: library
Explanation: The sl_register() call to the
Severity: White (error_id = 20501) signaling library failed. The return code is
printed as a parameter to this error.
User response: Record the return code and the
configuration parameters and see CP008.
CP007 Bad argument in command line
Explanation: An invalid argument was used in
the command line to start the custom server. The Destination: Log, System Monitor
switch and the corresponding invalid argument
are printed as the parameters in this error.
CP011 Failed to add timestamp to
User response: Correct the command line message trace filename
argument. You can see the command line
switches by selecting Properties from the File
window for this custom server. For more User response: Not applicable.
information on these command line options see
WebSphere Voice Response for AIX: Configuring the Severity: Yellow (error_id = 20502)
System. Destination: Log, System Monitor
Destination: Log, System Monitor CP012 Failed to open message trace file
CP008 Cannot connect to signaling User response: Not applicable.
library. Exiting...
Explanation: The custom server could not
contact the WebSphere Voice Response signaling Destination: Log, System Monitor
library. This error is issued as a result of one or
more white errors being issued. CP013 Polling for messages failed
User response: Check the white errors and Explanation: A call to CA_Poll() failed. The
contact IBM Support. CA_Poll return code and global CA_errno are
Severity: Red (error_id = 20504) printed as parameters to this error.
Destination: Log, System Monitor User response: If the problem occurs frequently,
record the parameters and contact IBM Support.
CP009 Failed to open signaling library Severity: White (error_id = 20501)
Explanation: The sl_open() call to the signaling Destination: Log, System Monitor
library failed. The return code is printed as a
parameter to this error. CP014 Bad message (internal to this
User response: Record the return code and see server)
CP008. Explanation: An unknown internal message
Severity: White (error_id = 20501) was received by CA_Poll(). The internal message

CP015 • CP021
type is printed as a parameter to this error.

CP018 Failed to reconfigure from
User response: If the problem occurs frequently, Monitor task
record the parameter and contact IBM Support.
Explanation: The custom server failed to
Severity: White (error_id = 20501) reconfigure the monitors in the monitor task
(used to refresh monitors).
User response: Take a trace of this failure and
CP015 Failed to set up message queues
for internal communications Severity: Red (error_id = 20504)
within server
Explanation: The custom server failed to set up
the necessary message queue for internal
CP019 Failed to refresh monitors from
communications.
Monitor task
User response: Take a trace which covers the
Explanation: The custom server failed to refresh
period of time between when the custom server
the state of a channel monitor with the CallPath
started and this error message is issued and
Server.
contact IBM Support. To take a trace, see
“Capturing a system-level trace” on page 15, of User response: Check that the CallPath server
the WebSphere Voice Response for AIX: Problem link is functioning. Check for white errors
Determination. relating to CallPath STLMON calls. Use the
information in these errors to determine the
cause of the error. If you can’t determine the
Destination: Log, System Monitor cause of the error, take a trace and contact IBM
Support.
CP016 Failed to start background task Severity: Red (error_id = 20504)

process
Explanation: The custom server failed to start
the background task process necessary for
CP020 Switch not supported by server
providing monitor refresh and transfer time-outs.
Explanation: The specified switch type is not
supported by this custom server.
User response: Select a switch type that is
supported. For more information on
Destination: Log, System Monitor configuration options, see WebSphere Voice
Response for AIX: Configuring the System.
CP017 Failed to initialize Monitor task Severity: Red (error_id = 20504)
Explanation: The custom server failed to start Destination: Log, System Monitor
the monitor task that refreshes the monitor.
User response: Take a trace of this failure and CP021 Cannot access configuration
contact IBM Support. information for channels
Severity: Red (error_id = 20504) Explanation: The custom server cannot set up
any channel monitors because it could not read
Destination: Log, System Monitor the channel configuration information.

CP022 • CP051
User response: Check the white errors and resolve the problem contact IBM Support.
As a workaround, you can configure the custom
Severity: Red (error_id = 20504) server using the command line switches (from
the Custom Server window, click File then
Properties). This error is still issued, even though
the command line operations override the
CP022 Cannot read parameter from default values. Permitted command line options
WebSphere Voice Response are: -sn, -si, -st, -sc, and -d.
configuration database
For more information on the command line
Explanation: The custom server could not read options, see WebSphere Voice Response for AIX:
the configuration information from the Configuring the System.
WebSphere Voice Response configuration
database, so default values will be used. These
defaults may not be suitable for your telephony Destination: Log, System Monitor
set up. This error gives some details of the
parameter it couldn’t read.
CP024 Monitor setup complete
User response: Check that you have set up all
Explanation: All monitors have been set up
the required configuration parameters. If you
with the CallPath Server. This is issued a few
cannot resolve this problem, contact IBM
seconds after a trunk has been enabled.
Support.
As a workaround, you can configure the custom
server using the command line switches (from Severity: White (error_id = 20501)
the Custom Server window, click File then
Properties). This error is still issued, even though Destination: Log, System Monitor
the command line operations override the
default values. Permitted command line options CP025-049 Reserved.
are: -sn, -si, -st, -sc, and -d.
For more information on the command line CP050 Cannot initialize CallPath because
options, see WebSphere Voice Response for AIX: invalid switch type defined
Explanation: The switch type defined in the
Severity: White (error_id = 20501) configuration is not recognized by
Destination: Log, System Monitor CallPath_Sigproc. This error should occur only if
the -st option has been used in the command line
configuration with an invalid switch type. The
CP023 Bad parameter from WebSphere actual value of the switch type parameter is
Voice Response configuration printed as one of the parameters of this error.
database
User response: Make the -st option valid. For
Explanation: The custom server read an invalid more information on this command line option
custom configuration parameter in the see WebSphere Voice Response for AIX: Configuring
WebSphere Voice Response configuration the System.
database, so default values will be used. These
defaults may not be suitable for your telephony Severity: Red (error_id = 20504)
set up. This error gives details of the invalid Destination: Log, System Monitor
parameter.
User response: Check that you have set up the CP051 Failed to initialize CallPath
configuration parameter correctly. If you can’t

CP052 • CP057
Explanation: Attempts to initialize the CallPath User response: Check that the CallPath Server
link failed. This error is issued as a result of one is available and that the switch link is running
or more white errors being issued. correctly.
User response: Use the white errors to Severity: Red (error_id = 20504)
determine the cause of the problem.
Destination: Log, System Monitor CP055 CallPath link now available
Explanation: The custom server has
CP052 Failed to start STLRCV child re-established communications with the CallPath
process Server.
Explanation: The custom server failed to start User response: None.
the STLRCV child process. This process provides
Severity: Green (error_id = 20503)
communications between CallPath_Sigproc and
the CallPath Server. Destination: Log, System Monitor
contact IBM Support. CP056 CallPath call STLISN
(Identify_Server_Name) failed
Explanation: STLISN failed during CallPath
server link initialization. This notification is
usually issued just before a CP053 or CP054
CP053 CallPath link unavailable. Trying message. The CallPath return code and the
to reconnect. parameters passed to and from the call are
printed in the error.
Explanation: The CallPath Server sent a
message to the custom server saying that the STLISN identifies the CallPath Server name.
CallPath link is not available. The custom server
User response: Check that the CallPath Server
tries to recover the link, but cannot succeed until
name is configured correctly. Also check that the
the CallPath link is available again. Green error
named CallPath Server is available, and can be
CP055 is issued when the link is available again.
reached by the WebSphere Voice Response
User response: Check that the CallPath Server system. To check that it is available, from
is available and that the switch link is running WebSphere Voice Response run ping
correctly. server_name, and check that you get a valid
response. The CallPath Server must be available
before the custom server will work properly.
Check the CallPath return code. This might give
the reason for the STLISN failure. For CallPath
CP054 CallPath link failure. Trying to return codes, see the CallPath documentation.
reconnect.
Explanation: The custom server received a
CallPath return code indicating that the CallPath
link has failed. The custom server tries to recover
the link, but cannot succeed until the CallPath CP057 CallPath call STLCRT
link is available again. Green error CP055 is (Create_Program_Name) failed
issued when the link is available again.
Explanation: STLCRT failed during CallPath

CP058 • CP060
Server link initialization. This notification is Severity: White (error_id = 20501)

message. The CallPath return code and the
parameters passed to and from the call are
printed in the error. CP059 CallPath call STLREL
(Release_Program_Name) failed
STLCRT tells the CallPath Server to create a
unique application identifier for the Explanation: STLREL failed either during
CallPath_Sigproc. CallPath Server link initialization or during
CallPath_Sigproc shutdown. This notification is
is available, and can be reached by the
WebSphere Voice Response system. To check that
it is available, from WebSphere Voice Response
run ping server_name, and check that you get a
valid response. The CallPath Server must be STLREL tells the CallPath Server to clean up
available before the custom server will work resources allocated to CallPath_Sigproc.
properly.
Check the CallPath return code. This might give is available, and can be reached by the
the reason for the STLCRT failure. For CallPath WebSphere Voice Response system. To check that
return codes, see the : CallPath Server it is available, from WebSphere Voice Response
Programmer's Guide and Reference. run ping server_name, and check that you get a
valid response. The CallPath Server must be
available before the custom server will work
Destination: Log, System Monitor properly.
CP058 CallPath call STLIDEN the reason for the STLREL failure. For CallPath
(Identify_Program_Name) failed return codes, see the : CallPath Server
Programmer's Guide and Reference.
Explanation: STLIDEN failed during CallPath
Server link initialization. This notification is If this error occurs frequently, you may need to
normally issued just before a CP053 or CP054 manually remove the program names associated
message. The CallPath return code and the with the CallPath_Sigproc from CallPath Server
parameters passed to and from the call are using the CallPath Server Management facility.
printed in the error. This frees resources allocated to those program
names. Identify these program names by their
STLIDEN identifies CallPath_Sigproc processes
descriptions which have “WebSphere Voice
to the CallPath Server.
Response to CallPath Server Interface” in the
User response: Check that the CallPath Server description field.
it is available, from WebSphere Voice Response Destination: Log, System Monitor
CP060 CallPath call STLIPGV
(Identify_Program_Version) failed
properly.
Explanation: STLIPGV failed during CallPath
Server link initialization. This notification is
the reason for the STLIDEN failure. For CallPath
return codes, see the CallPath documentation.

CP061 • CP063
parameters passed to and from the call are available before the custom server will work
printed in the error. properly.
STLIPGV identifies the version of the API that Check the CallPath return code. This might give
CallPath_Sigproc uses to communicate with the the reason for the STLIPD failure. For CallPath
CallPath Server. CallPath_Sigproc currently uses return codes, see the: CallPath Server
“STL_VERSION_1”. Programmer's Guide and Reference .
User response: Check that the CallPath Server Severity: White (error_id = 20501)
run ping server_name, and check that you get a CP062 CallPath call STLINIT
valid response. The CallPath Server must be (Initialise_Call_Profile) failed
properly. Explanation: STLINIT failed during CallPath
Check the CallPath return code. This might give normally issued just before a CP053 or CP054
the reason for the STLIPGV failure. For CallPath message. The CallPath return code and the
return codes, see the : CallPath Server parameters passed to and from the call are
Programmer's Guide and Reference. printed in the error.
Severity: White (error_id = 20501) STLINIT initializes the values for telephone call
characteristics. A call_profile_ID is returned to
CallPath_Sigproc for use in future telephony
related requests.
CP061 CallPath call STLIPD
User response: Check that the configured
(Identify_Program_Description)
switch ID is available on the CallPath Server. For
failed
more information on switch configuration see the
Explanation: STLIPD failed during CallPath WebSphere Voice Response for AIX: Configuring the
Server link initialization. This notification is System.
normally issued just before a CP053 or CP054
Check that the CallPath Server is available, and
can be reached by the WebSphere Voice Response
system. To check that it is available, from
WebSphere Voice Response run ping
STLIPD specifies descriptive text, associated with server_name, and check that you get a valid
the program name, that identifies response. The CallPath Server must be available
CallPath_Sigproc to the CallPath Server. This text before the custom server will work properly.
appears on the CallPath Server Management
window for the CallPath Server. The text
the reason for the STLINIT failure. For CallPath
includes the version number of the
return codes, see the : CallPath Server
CallPath_Sigproc and the following text:
“WebSphere Voice Response to CallPath Server
Interface”. Severity: White (error_id = 20501)
User response: Check that the CallPath Server Destination: Log, System Monitor
it is available, from WebSphere Voice Response CP063 CallPath call STLMONS
run ping server_name, and check that you get a (Monitor_System_Messages)
valid response. The CallPath Server must be failed

CP064 • CP066
Explanation: STLMONS failed during CallPath return codes, see the : CallPath Server
Server link initialization. This notification is Programmer's Guide and Reference.
parameters passed to and from the call are Destination: Log, System Monitor
STLMONS tells the CallPath Server to send CP065 CallPath call STLSHPC
system messages concerning the status of (Set_Holding_Party_Calling)
CallPath and the switch to CallPath_Sigproc. failed
User response: Check that the CallPath Server Explanation: STLSHPC failed during CallPath
is available, and can be reached by the Server link initialization. This notification is
WebSphere Voice Response system. To check that normally issued just before a CP053 or CP054
it is available, from WebSphere Voice Response message. The CallPath return code and the
run ping server_name, and check that you get a parameters passed to and from the call are
valid response. The CallPath Server must be printed in the error.
properly. STLSHPC sets the ‘holding party calling’ option
in the switch. CallPath_Sigproc uses the switch
Check the CallPath return code. This might give default value for this option.
the reason for the STLMONS failure. For
CallPath return codes, see the : CallPath Server User response: Check that the CallPath Server
Programmer's Guide and Reference. is available, and can be reached by the
Severity: White (error_id = 20501) it is available, from WebSphere Voice Response
CP064 CallPath call STLSAA properly.
(Set_Automatic_Answer) failed
Explanation: STLSAA failed during CallPath the reason for the STLSHPC failure. For CallPath
Server link initialization. This notification is return codes, see the : CallPath Server
normally issued just before a CP053 or CP054 Programmer's Guide and Reference.
printed in the error. Destination: Log, System Monitor
STLSAA sets the ‘automatic answer’ option in
the switch. CallPath_Sigproc uses the switch CP066 CallPath call STLSHPB
default value for this option. (Set_Holding_Party_Callback)
failed
is available, and can be reached by the Explanation: STLSHPB failed during CallPath
WebSphere Voice Response system. To check that Server link initialization. This notification is
it is available, from WebSphere Voice Response normally issued just before a CP053 or CP054
run ping server_name, and check that you get a message. The CallPath return code and the
valid response. The CallPath Server must be parameters passed to and from the call are
available before the custom server will work printed in the error.
properly.
STLSHPB sets the ‘holding party callback’ option
Check the CallPath return code. This might give in the switch. CallPath_Sigproc uses the switch
the reason for the STLSAA failure. For CallPath default value for this option.

CP067 • CP069
User response: Check that the CallPath Server problem with the CallPath Server link. This
is available, and can be reached by the notification is normally issued just before a
WebSphere Voice Response system. To check that CP053 or CP054 message. The CallPath return
it is available, from WebSphere Voice Response code and the parameters passed to and from the
run ping server_name, and check that you get a call are printed in the error.
STLDISC drops a transfer request when the
transfer has timed out.
properly.
the reason for the STLSHPB failure. For CallPath
return codes, see the: CallPath Server
Severity: White (error_id = 20501) valid response. The CallPath Server must be
properly.
CP067 CallPath call STLSRR
the reason for the STLDISC failure. For CallPath
(Set_Return_Response) failed
Explanation: STLSRR failed during CallPath Programmer's Guide and Reference.
message. The CallPath return code and the Destination: Log, System Monitor
CP069 CallPath call STLDISC
STLSRRR sets the ‘return response’ option in the (Disconnect) failed - program
switch. CallPath_Sigproc uses the switch default problem
value for this option.
Explanation: STLDISC failed for one of the
User response: Check that the CallPath Server following reasons:
is available, and can be reached by the v There is a temporary communications problem
WebSphere Voice Response system. To check that with the CallPath Server.
v There is an invalid parameter in the STLDISC
call.
available before the custom server will work v There are no CallPath resources available.
properly.
The CallPath return code and the parameters
Check the CallPath return code. This might give passed to and from the call are printed in the
the reason for the STLSRRR failure. For CallPath error.
STLDISC drops a transfer request when the
Severity: White (error_id = 20501) transfer has timed out.
Destination: Log, System Monitor User response: If this problem occurs
frequently, make sure that the CallPath Server
configuration is suitable for your setup. For
CP068 CallPath call STLDISC guidance on how to estimate application
(Disconnect) failed - link problem program requirements, see the : CallPath Server
Explanation: STLDISC failed because of a

CP070 • CP072
Planning, Installation and Problem Determination available before the custom server will work
Guide. properly.
Make sure that the number of concurrent users Check the CallPath return code. This might give
in your CallPath configuration is set to at least the reason for the STLIMMT failure. For CallPath
the number of WebSphere Voice Response return codes, see the : CallPath Server
channels you are using and more if you have Programmer's Guide and Reference.
other applications using CallPath.
CP072 CallPath call STLIMMT
CP070 CallPath call STLDISC (Immediate_Transfer) - program
(Disconnect) failed - unknown problem
problem
Explanation: STLIMMT failed for one of the
Explanation: STLDISC failed because of an following reasons:
unexpected or unknown error. The CallPath v There is a temporary communications problem
return code and the parameters passed to and with the CallPath Server.
from the call are printed in the error.
v There is an invalid parameter in the STLIMMT
STLDISC drops a transfer request when the call.
transfer has timed out. v There are no CallPath resources available.
User response: If this problem occurs
frequently, take a trace of it and contact IBM The CallPath return code and the parameters
Support. passed to and from the call are printed in the
error.
Destination: Log, System Monitor STLIMMT performs a single step transfer on
switches that support this call.
CP071 CallPath call STLIMMT User response: If this problem occurs

(Immediate_Transfer) - link frequently, make sure that the CallPath Server
problem configuration is suitable for your setup. For
guidance on how to estimate application
Explanation: STLIMMT failed because of a program requirements, see the : CallPath Server
problem with the CallPath Server link. This Planning, Installation and Problem Determination
notification is normally issued just before a Guide.
CP053 or CP054 message. The CallPath return
code and the parameters passed to and from the Make sure that the number of concurrent users
call are printed in the error. in your CallPath configuration is set to at least
the number of WebSphere Voice Response
STLIMMT performs a single step transfer on channels you are using and more if you have
switches that support this call. other applications using CallPath.
User response: Check that the CallPath Server If you have set up program data to be passed
is available, and can be reached by the with this transfer, make sure that the length of
WebSphere Voice Response system. To check that the program data does not exceed that allowed
it is available, from WebSphere Voice Response for your switch.
valid response. The CallPath Server must be Check that the length of the number to which

CP073 • CP076
you are does not exceed that allowed for your Programmer's Guide and Reference.
switch.
For more information see the entry for STLIMMT
in the CallPath reference guide for your switch.
CP075 CallPath call STLMON (Monitor)
Destination: Log, System Monitor - program problem
Explanation: STLMON failed for one of the
CP073 CallPath call STLIMMT following reasons:
(Immediate_Transfer) - unknown v There is a temporary communications problem
problem with the CallPath Server.
Explanation: STLIMMT failed because of an v There is an invalid parameter in the STLMON
unexpected or unknown error. The CallPath call.
return code and the parameters passed to and v There are no CallPath resources available.
STLIMMT performs a single step transfer on The CallPath return code and the parameters
switches that support this call. passed to and from the call are printed in the
error.
frequently, trace it and contact IBM Support. STLMON sets up CallPath monitors on the
Severity: White (error_id = 20501) WebSphere Voice Response channel during trunk
initialization.
CP074 CallPath call STLMON (Monitor) configuration is suitable for your setup. For
- link problem guidance on how to estimate application
Explanation: STLMON failed because of a program requirements, see the : CallPath Server
problem with the CallPath Server link. This Planning, Installation and Problem Determination
notification is normally issued just before a Guide.
CP053 or CP054 message. The CallPath return Make sure that the number of concurrent users
code and the parameters passed to and from the in your CallPath configuration is set to at least
call are printed in the error. the number of WebSphere Voice Response
STLMON sets up CallPath monitors on the channels you are using and more if you have
WebSphere Voice Response channel during trunk other applications using CallPath.
initialization. Severity: White (error_id = 20501)
User response: Check that the CallPath Server Destination: Log, System Monitor
it is available, from WebSphere Voice Response CP076 CallPath call STLMON (Monitor)
run ping server_name, and check that you get a - unknown problem
valid response. The CallPath Server must be Explanation: STLMON failed because of an
available before the custom server will work unexpected or unknown error. The CallPath
properly. return code and the parameters passed to and
Check the CallPath return code. This might give from the call are printed in the error.
the reason for the STLMON failure. For CallPath STLMON sets up CallPath monitors on the

CP077 • CP079
WebSphere Voice Response channel during trunk Check the CallPath return code. This might give
initialization. the reason for the STLPIND failure. For CallPath
return codes, see the: CallPath Server
frequently, trace it and contact IBM Support.
CP079 CallPath call STLPIND (MWI) -

CP077 CallPath response message:
program problem
cannot set monitor
Explanation: STLPIND failed for one of the
Explanation: A negative CallPath response
following reasons:
corresponding to an earlier STLMON (Monitor)
call was received indicating that CallPath could v There is a temporary communications problem
not set up the specified monitor. The trunk, with the CallPath Server.
channel, and line ID associated with the earlier v There is an invalid parameter in the STLPIND
STLMON call is printed in the error. call.
STLMON sets up CallPath monitors on the v There are no CallPath resources available.
WebSphere Voice Response channel during trunk
initialization. The CallPath return code and the parameters
passed to and from the call are printed in the
User response: Check the WebSphere Voice error.
Response configuration for the given trunk and
channel. The line ID should be set to the phone The STLPIND call is used to set or reset an MWI
number for the channel. indicator on a phone.
Severity: Yellow (error_id = 20503) User response: If this problem occurs
Destination: Log, System Monitor frequently, make sure that the CallPath Server
CP078 CallPath call STLPIND (MWI) - program requirements, see the : CallPath Server
link problem Planning, Installation and Problem Determination
Explanation: STLPIND failed because of a Guide.
problem with the CallPath Server link. This Make sure that the number of concurrent users
notification is normally issued just before a in your CallPath configuration is set to at least
CP053 or CP054 message. The CallPath return the number of WebSphere Voice Response
code and the parameters passed to and from the channels you are using and more if you have
call are printed in the error. other applications using CallPath.
STLPIND sets or resets an MWI indicator on a Check that the length of the number you are
phone. setting the MWI for does not exceed that allowed
User response: Check that the CallPath Server for your switch.
is available, and can be reached by the Note that STLPIND can be issued either
WebSphere Voice Response system. To check that automatically when a WebSphere Voice Response
it is available, from WebSphere Voice Response mailbox is updated, or by the Set_MWI custom
run ping server_name, and check that you get a server call.
valid response. The CallPath server must be
available before the custom server will work For more information see the entry for STLPIND
properly. in the CallPath reference guide for your switch.

CP080 • CP083
Severity: White (error_id = 20501) is available, and can be reached by the

CP080 CallPath call STLPIND (MWI) - valid response. The CallPath Server must be
unknown problem available before the custom server will work
properly.
Explanation: STLPIND failed because of an
unexpected or unknown error. The CallPath Check the CallPath return code. This might give
return code and the parameters passed to and the reason for the STLRCV failure. For CallPath
from the call are printed in the error. return codes, see the : CallPath Server
STLPIND sets or resets an MWI indicator on a
phone. Severity: White (error_id = 20501)
User response: If this problem occurs Destination: Log, System Monitor

Severity: White (error_id = 20501) CP083 CallPath call STLRCV (Receive) -
program problem
Explanation: STLRCV failed for one of the
following reasons:
CP081 CallPath response message:
cannot set MWI v There is a temporary communications problem
with the CallPath Server.
Explanation: A negative CallPath response v There is an invalid parameter in the STLRCV
corresponding to an earlier SLTPIND (MWI) call, call.
indicating that CallPath could not set the MWI to
the requested state. The MWI number and other v There are no CallPath resources available.
details relating to the earlier STLPIND call are
printed in the error. The CallPath return code and the parameters
passed to and from the call are printed in the
STLPIND sets or resets an MWI indicator on a error.
phone.
User response: Check that the phone number STLRCV gets messages from the CallPath Server.
for the STLPIND request is valid. User response: If this problem occurs
Severity: Yellow (error_id = 20503) frequently, make sure that the CallPath Server
Destination: Log, System Monitor guidance on how to estimate application
program requirements, see the : CallPath Server
CP082 CallPath call STLRCV (Receive) - Planning, Installation and Problem Determination
link problem Guide.
Explanation: STLRCV failed because of a Make sure that the number of concurrent users
problem with the CallPath Server link. This in your CallPath configuration is set to at least
notification is normally issued just before a the number of WebSphere Voice Response
CP053 or CP054 message. The CallPath return channels you are using and more if you have
code and the parameters passed to and from the other applications using CallPath.
call are printed in the error. Severity: White (error_id = 20501)
STLRCV gets messages from the CallPath Server. Destination: Log, System Monitor

CP084 • CP088
v There is a temporary communications problem

CP084 CallPath call STLRCV (Receive) -
with the CallPath Server.
unknown problem
v There is an invalid parameter in the STLRETR
Explanation: STLRCV failed because of an call.
unexpected or unknown error. The CallPath
v There are no CallPath resources available.
return code and the parameters passed to and
STLRCV gets messages from the CallPath Server. passed to and from the call are printed in the
error.
STLRETR reconnects to the original caller if a
Severity: White (error_id = 20501) transfer call fails.
Destination: Log, System Monitor User response: If this problem occurs
CP085 CallPath call STLRETR
(Retrieve_Call) - link problem
program requirements, see the : CallPath Server
Explanation: STLRETR failed because of a Planning, Installation and Problem Determination
problem with the CallPath Server link. This Guide.
notification is normally issued just before a
Make sure that the number of concurrent users
in your CallPath configuration is set to at least
code and the parameters passed to and from the
call are printed in the error.
channels you are using and more if you have
STLRETR reconnects to the original caller if a other applications using CallPath.
transfer call fails.
it is available, from WebSphere Voice Response CP087 CallPath call STLRETR
run ping server_name, and check that you get a (Retrieve_Call) - unknown
valid response. The CallPath Server must be problem
properly. Explanation: STLRETR failed because of an
Check the CallPath return code. This might give return code and the parameters passed to and
the reason for the STLRETR failure. For CallPath from the call are printed in the error.
Programmer's Guide and Reference. STLRETR performs a single step transfer on
Destination: Log, System Monitor frequently, trace it and contact IBM Support.
CP086 CallPath call STLRETR
(Retrieve_Call) - program problem Destination: Log, System Monitor
Explanation: STLRETR failed for one of the

following reasons: CP088 CallPath call STLTRAN
(Transfer_Call) - link problem

CP089 • CP091
Explanation: STLTRAN failed because of a Planning, Installation and Problem Determination

problem with the CallPath Server link. This Guide.
notification is normally issued just before a
Make sure that the number of concurrent users
in your CallPath configuration is set to at least
code and the parameters passed to and from the
channels you are using and more if you have
STLTRAN completes a transfer operation after an other applications using CallPath.
STLXTND (Extend_Call) call has completed.
it is available, from WebSphere Voice Response CP090 CallPath call STLTRAN
run ping server_name, and check that you get a (Transfer_Call) - unknown
valid response. The CallPath Server must be problem
properly. Explanation: STLTRAN failed because of an
Check the CallPath return code. This might give return code and the parameters passed to and
the reason for the STLTRAN failure. For CallPath from the call are printed in the error.
Programmer's Guide and Reference. STLTRAN completes a transfer operation after an
STLXTND (Extend_Call) call has completed.
Destination: Log, System Monitor frequently, trace it and contact IBM Support.
CP089 CallPath call STLTRAN
(Transfer_Call) - Program problem Destination: Log, System Monitor
Explanation: STLTRAN failed for one of the

following reasons: CP091 CallPath call STLXTND
(Extend_Call) - Link problem
v There is a temporary communications problem
with the CallPath Server. Explanation: STLXTND failed because of a
v There is an invalid parameter in the STLTRAN problem with the CallPath Server link. This
call. notification is normally issued just before a
v There are no CallPath resources available. code and the parameters passed to and from the
passed to and from the call are printed in the STLXTND initiates a two part transfer operation
error. (STLXTND + STLTRAN).
STLTRAN completes a transfer operation after an is available, and can be reached by the
STLXTND (Extend_Call) call has completed. WebSphere Voice Response system. To check that
User response: If this problem occurs it is available, from WebSphere Voice Response
frequently, make sure that the CallPath Server run ping server_name, and check that you get a
configuration is suitable for your setup. For valid response. The CallPath Server must be
guidance on how to estimate application available before the custom server will work
program requirements, see the : CallPath Server properly.

CP092 • CP095
the reason for the STLXTND failure. For CallPath Destination: Log, System Monitor
CP093 CallPath call STLXTND
Severity: White (error_id = 20501) (Extend_Call) - unknown problem
Destination: Log, System Monitor Explanation: STLXTND failed because of an
return code and the parameters passed to and
CP092 CallPath call STLXTND
(Extend_Call) - program problem
STLXTND performs a single step transfer on
Explanation: STLXTND failed for one of the
following reasons:
v There is a temporary communications problem User response: If this problem occurs
with the CallPath Server. frequently, trace it and contact IBM Support.
v There is an invalid parameter in the STLXTND Severity: White (error_id = 20501)
call.
v There are no CallPath resources available.
The CallPath return code and the parameters CP094 CallPath call STLPIND (MWI) -
passed to and from the call are printed in the response not received within
error. timeout period
Explanation: An earlier STLPIND call timed out
STLXTND initiates a two part transfer operation waiting for a response from CallPath indicating
(STLXTND + STLTRAN). that CallPath has not yet received a confirmation.
User response: If this problem occurs If the confirmation arrives after the timeout, it is
frequently, make sure that the CallPath Server ignored. The MWI number and other details
configuration is suitable for your setup. For relating to the earlier STLPIND call are printed
guidance on how to estimate application in the error.
program requirements, see the : CallPath Server STLPIND sets or resets an MWI indicator on a
Planning, Installation and Problem Determination phone.
Guide.
User response: If this problem is caused by a
Make sure that the number of concurrent users timeout, increase the timeout value in the
in your CallPath configuration is set to at least Set_MWI custom server call. If this reduces the
the number of WebSphere Voice Response problem, the problem may be caused by the
channels you are using and more if you have system load.
other applications using CallPath.
If you have set up program data to be passed
with this transfer, make sure that the length of Destination: Log, System Monitor
the program data does not exceed that allowed
for your switch. CP095 CallPath link has been initialized
Check that the length of the number you are Explanation: This is a notification to say that
transferring to does not exceed that allowed for the CallPath link has been initialized. This
your switch. indication should be given only once after the
For more information see the entry for STLXTND custom server has been started.
in the CallPath reference guide for your switch. User response: None


DTJ1000 • DTJ1010
Java and VoiceXML environment messages

DTJ messages are written to log files in the $DTJ_HOME/dtj_logs directory. You
can format these log files by using the dtjflog command (see WebSphere Voice
Response for AIX: Deploying and Managing VoiceXML and Java Applications for
more information). Some DTJ messages include completion codes.
DTJ1000 optionname is not a valid option
User response: Check that the configuration
User response: Check that the option is not
name is not misspelled. Use the -action list
misspelled and is valid.
option to see what configurations exist in the
configuration database.
DTJ1001 Missing value for option
optionname
DTJ1006 Configuration configurationname
Explanation: This option requires a value to be already exits in configuration
entered. database databasename, and
-replace has not been specified
User response: Reenter the option with a valid
value. User response: If you want to replace the
configuration, use the -replace option.
DTJ1002 Configuration database
databasename was not found DTJ1007 value is not a valid value for
optionname
User response: Check that the database name is
not misspelled and that the database exists. User response: Re-enter the optionname option
with a valid value.
DTJ1003 I/O error reading from
configuration database DTJ1008 The configuration file filename
databasename already exists and -replace has not
been specified
Explanation: The command is not able to read
the file. Explanation: The filename is already in use, and
-replace has not been specified.
User response: Review the StackTrace on stdout
for additional information. Retry the operation. If User response: If you want to replace the
the problem persists recreate the configuration configuration, then use the -replace option.
database.
DTJ1009 I/O error writing configuration
DTJ1004 I/O error writing to configuration file filename
database databasename
Explanation: The command is not able to write
Explanation: The command is not able to write to the file.
to the file.
User response: Ensure that there is enough disk
User response: Ensure that there is enough disk space to write the file and, if the file already
space to write the database and, if the database exists, it is not read-only.
already exists, it is not read-only.
DTJ1010 The following line does not
DTJ1005 Configuration configurationname contain a keyword and a
was not found in the parameter separated by a '='

DTJ1011 • DTJ1022
Explanation: All lines must have a Keyword Explanation: parametername cannot be specified
and a Parameter separated by a '='. more than once in....
User response: Correct the error and resubmit User response: Correct the error and resubmit
the request. the request.
DTJ1011 keyword is an invalid keyword in DTJ1017 The following line in... contains
the following line parametername which is an invalid
parameter...
User response: Correct the error and resubmit
the request. User response: Correct the error and resubmit
the request.
DTJ1012 The import configuration file
filename was not found DTJ1018 The following line in... contains
keyword which is an invalid
User response: Check that the configuration file
keyword
name is not misspelled and that it exists.
the request.
configuration file filename
DTJ1019 Missing ';' in...
the file. Explanation: All primary keywords must be
delimited by a ';'.
for additional information. Retry the operation. If User response: Correct the error and resubmit
the problem remains, recreate the configuration the request.
file.
DTJ1020 keyword keyword is missing in...
DTJ1014 keyword keyword contains the
parameter parametername which
the request.
already exists
Explanation: The name specified on the keyword
DTJ1021 object objectname in... does not
keyword must be unique.
exist...
Explanation: The object must have been
the request.
previously specified.
User response: Specify the object and resubmit
DTJ1015 The following line in filename
the request.
does not contain a keyword and a
parameter separated by a '='
DTJ1022 The following NumToApp line
Explanation: All lines must have a Keyword
in... does not contain two
and a Parameter separated by a '='.
parameters separated by a
User response: Correct the error and resubmit comma...
the request.
Explanation: NumToApp must contain two
parameters. The first is the phone number and
DTJ1016 parametername has already been the second is the application.
specified in...

DTJ1023 • DTJ1032
User response: Correct the error and resubmit the configuration into the database.
the request.
DTJ1028 Configuration configurationname
DTJ1023 The following NumToApp line has been successfully copied from
in... contains a phone number that databasename to filename
already exists...
Explanation: The phone number cannot map to DTJ1029 Configuration configurationname
more than one application. has been successfully added from
filename to databasename
the request.
DTJ1030 The following RecoType or TTSType
line in filename contains a locale
that already exists for this
in... contains a non-numeric
application
value...
Explanation: A locale cannot be used in more
Explanation: The NumToApp parameter must
than one RecoType or TTSType for any one
be a numeric value.
application.
the request.
the request.

DTJ1031 Multiple voice response nodes are
in... contains line number
defined in host name. Only one
linenumber which has already been
voice response node can be
specified...
defined in a host.
Explanation: Line numbers cannot be specified
Explanation: A host can only have one voice
in more than one place.
response node; you have defined more than one
User response: Correct the error and resubmit voice response node in the configuration
the request. database.
User response: Ensure only one voice response
DTJ1026 Configuration database node is defined for host name.
databasename contains the
following configurations
DTJ1032 The NodeDefVRNode=name
Explanation: You have requested a list of the definition for voice response node
configurations in a database. The list will follow name is obsolete and will be
this message. ignored.
Explanation: Applications running in a voice
DTJ1027 Configuration database response node cannot use the services of another
databasename contains no voice response node. Therefore NodeDefVRNode
configurations is no longer valid for a NodeName entry when
VRNode=yes.
Explanation: You have requested a list of the
configurations in a database but the database is User response: Remove this keyword from the
empty. NodeName entry.

correct, then run the dtjconf command to import

DTJ1033 • DTJ1040
NodeDefHost keywords of the NodeName entry

DTJ1033 The NodeDefHost=name
for the application node.
definition for voice response node
name is obsolete and will be User response: Remove this keyword from the
ignored. AppName entry.
response node cannot use the services of another DTJ1037 The NodeDefLocale=locale
voice response node, therefore NodeDefHost is definition for node name is
no longer valid for a NodeName entry when obsolete and will be ignored
VRNode=yes. because name is an application
node.
User response: Remove this keyword from the
NodeName entry. Explanation: NodeDefLocale is valid only for
voice response nodes.
DTJ1034 Application name has multiple User response: This message is information
parameters with name only. NodeDefLocale does not apply to an
parametername. application node. Remove the
NodeDefLocale=locale definition. To set a default
Explanation: It is not valid to have more than
locale, use the NodeDefLocale keyword in the
one parameter with the same name for an
voice response node configuration entry.
application.
User response: Make sure that application name
DTJ1038 The NodeDefHost=name for
has only one parameter with name
NodeName=nodename does not
parametername.
exist.
Explanation: The NodeDefHost for a voice
DTJ1035 The AppDefVRNode=name
response node must refer to a host that is
definition for application name is
defined in this configuration.
obsolete and will be ignored.
DTJ1039 The NodeDefVRNode=name for
response node always use the services of that
NodeName=nodename does not
node; applications running in an application
exist on NodeDefHost=name
node use the services of the voice response node
specified using the NodeDefVRNode and Explanation: The NodeDefVRNode for an
NodeDefHost keywords of the NodeName entry application node must refer to a voice response
for the application node. node that is configured for the host specified by
NodeDefHost.
AppName entry.
DTJ1040 The NodeDefVRNode=name for
NodeName=nodename exists on
DTJ1036 The AppDefHost=name definition
NodeDefHost=name, but is not a
for application name is obsolete
voice response node.
and will be ignored.
Explanation: The NodeDefVRNode for an
application node must refer to a voice response
response node always use the services of that
node that is configured for the host specified by
node; applications running in an application
NodeDefHost.
node use the services of the voice response node
specified using the NodeDefVRNode and

DTJ1042 • DTJ1052
Explanation: The parameters must be a positive

DTJ1042 Keyword keyword is defined in
integer, or zero.
NodeName=nodename but is not
valid for application nodes.
DTJ1048 The following keyword line in
Explanation: This occurs if a keyword that is
CCXService=name must specify a
valid only for voice response nodes is specified
second parameter greater than or
for an application node. The configuration is not
equal to the first\n\ linenumber
imported.
Explanation: The two parameters represent an
integer range which specify a minimum and
NodeName entry.
maximum value \ , where the second value must
be equal to or greater than the first.
DTJ1043 Cannot define CTIService and
NodeCallPathService on same
node nodename
NodeName=nodename contains a
Explanation: A voice response node cannot phone number mapping that
support CTIService and NodeCallPathService at overlaps another CCXML
the same time. service\n\ linenumber
Explanation: The phone number cannot map to
DTJ1044 The following CTIService line in more than one CCXML service.
NodeName=nodename contains
more than two parameters
the request.
separated by a comma linenumber
Explanation: CTIService must contain up to two
DTJ1050 In CCXService name the specified
parameters. A CTI service name optionally
DefAppService=appservicename
followed by the word default.
declares a Node that does not
exist.
DTJ1045 The following CTIService line in
Explanation: The DefAppService in a
NodeName=nodename contains an
CCXService definition must refer to a Node that
invalid second parameter
exists.
linenumber
Explanation: The second optional parameter of
DTJ1051 In CCXService name the specified
CTIService must be the word default.
DefAppService=appservicename
declares a Node that does not
DTJ1046 CCXML service parameter has have a CCXAppService entry.
multiple parameters with name
Explanation: The DefAppService in a
parametername.
CCXService definition must refer to a Node that
Explanation: It is not valid to have more than contains a CCXAppService entry
one parameter with the same name for a CCXML
service.
DTJ1052 The CCXService name was not
referenced by any Node with the
DTJ1047 The following keyword line in CCXAppService entry.
CCXService=name cannot contain
Explanation: There must be a Node in the
parameters with negative
configuration to run the defined CCXService.
values\n\ linenumber

DTJ1053 • DTJ2000
configuration that references the CCXService.

CCXService=servicename cannot
contain a second parameter that is DTJ1061 VoiceXML 1.0 applications are no
zero linenumber longer supported. Please choose
an alternative application type.
Explanation: The second parameter must be
Application found:
greater than zero
AppName=appname.
Explanation: Choose a an application type other
DTJ1056 The CCXService name cannot
than VoiceXML 1.0.
have the same name as an
application.
DTJ1062 The application with name
Explanation: Each CCXService and AppName
appname does not exist, so cannot
definition must be unique within the
be mapped to number appnumber
configuration
Explanation: The application name specified in
the NumToApp mapping is not valid.
DTJ1057 The AppName appname cannot
have the same name as a User response: Specify a valid application
CCXService. NumToApp mapping.
Explanation: All CCXService and AppName
definitions must be unique within the DTJ1063 Error in AAIKVPSeparator
configuration. separator definition
TelephonyService
DTJ1058 The following keyword line in Explanation: The AAIKVPSeparator definition
NodeName=nodename contains a is not valid.
phone number mapping that has a
CCXML service referenced in User response: Check the AAIKVPSeparator
another node\n\ linenumber definition and correct it.
Explanation: The phone number cannot map to

a CCXML service that is already mapped by DTJ1064 Invalid AAIKVPSeparator
another node. separator key value character in
TelephonyService.
User response: orrect the error and resubmit the
request. Explanation: The separator character used in
the AAIKVPSeparator definition is not valid.
Valid separator characters are:
DTJ1059 The VRNode name cannot be : ; , . | ! ^ * + - ~ #
defined on more than one host as
it references CCXServices.
The default character is a colon (:)
Explanation: VRNodes that reference CCXML
User response: Specify a valid separator value
services cannot be defined in more than one host.
in the AAIKVPSeperator definition.
DTJ1060 The CCXService name was not

DTJ2000 Node nodename at host hostname
referenced by any Node with a
was found in the RMI registry.
NumToApp or NodeDefAppName
entry. Explanation: The RMI registry has an entry for
node nodename at host hostname. The system will
Explanation: There must be a Node in the
attempt to use this node.

DTJ2001 • DTJ2012
DTJ2001 Node nodename at host hostname is DTJ2009 Classpath entry classpath entry may
not responding. not be valid: reason
Explanation: The RMI registry has an entry for Explanation: Output in the node.out files
node nodename at host hostname, but it is not during startup of a VRBE node to identify entries
responding. The system will create a new in the NodeClassPath that may not be valid and
ApplicationManagerImpl for this node. will therefore be ignored by Java.
User response:
DTJ2002 Creating a new
ApplicationManagerImpl for node
DTJ2010 Node nodename has exceeded the
nodename at host hostname.
heap threshold. Heap = (heapsize)
Explanation: The Java heap memory has
DTJ2003 The creation of the
exceeded 90% of the maximum allocated
ApplicationManagerImpl for node
memory.
nodename at host hostname has
failed. User response: Investigate increasing each
Node's maximum heap size using the -Xmx flag
User response: Check that the RMI registry is
in the JavaCommand section of each node in
running. Review the printStackTrace() on stdout.
configuration file default.cff.
If the error persists, report this problem to your
service representative.
DTJ2011 Node nodename has returned
below the heap threshold. Heap =
DTJ2004 ApplicationManagerImpl for node
(heapsize)
nodename at host hostname
successfully created. Explanation: The Java heap memory has
dropped below 90% of the maximum allocated
memory.
DTJ2005 ApplicationManagerImpl for node
nodename at host hostname is User response: Investigate increasing each
already running. Node's maximum heap size using the -Xmx flag
in the JavaCommand section of each node in
Explanation: You requested to start node
configuration file default.cff.
nodename at host hostname, but it is already
running.
DTJ2012 Applications should not be
User response: Check that you are requesting
configured to start within VRnode
the correct node to start.
VRnodename
Explanation: Configuration file default.cff
DTJ2006 Quiesce shutdown for node
includes at least one group that has been defined
nodename at host hostname has
to start within the VRNode. This practice is no
started.
longer recommended.
User response: Reconfigure the WebSphere
DTJ2007 Immediate shutdown of node
Voice Response Java and VoiceXML Environment
nodename at host hostname has been
by running the dtjit configuration tool file as
requested.
described in the “Updating the configuration
database” section of the WebSphere Voice
DTJ2008 Node nodename at host hostname Response for AIX Deploying and Managing
has shutdown. VoiceXML and Java Applications book.
Alternatively, edit default.cff so that the group

DTJ2013 • DTJ2501
starts in an application node.

DTJ2015 Node nodename is configured to
use NodeDefAppName rather
DTJ2013 Node nodename has more than NumToApp which is not
applications configured than the recommended
maximum recommended limit of
Explanation: Indicates that file default.cff has
default threshold
been configured to have all applications
Explanation: More than the recommended 30 launched using NodeDefAppName and there are no
(default threshold) applications have been NumToApp references. This is not recommended as
defined to start within a given application node. NodeDefAppName should only be used for failover
applications and can have bad consequences to
User response: Reconfigure the WebSphere machine operation if used for general calls.
by running the dtjit configuration tool file as User response: Reconfigure the WebSphere
described in the “Updating the configuration Voice Response Java and VoiceXML Environment
database” section of the WebSphere Voice by running the dtjit configuration tool file as
Response for AIX manual. Alternatively, redefine described in the “Updating the configuration
the existing groups defined in default.cff database” section of the WebSphere Voice
manually so that each group contains fewer Response for AIX Deploying and Managing
applications. VoiceXML and Java Applications book.
Alternatively, edit default.cff using actual
As a temporary measure, modify the specific NumToApp numbers or a ‘wildcard’
dtj.node.application.threshold value in the NumToApp=* definition.
dtj.ini file. Take care when editing dtj.ini and
always make a backup copy first! Message
DTJ2014 will be issued if the default value of the DTJ2500 No default locale for Node
dtj.node.application.threshold value is nodename at host hostname
modified. specified in configuration
Explanation: The configuration file does not
DTJ2014 Node nodename has had its specify a default locale for nodename at host
maximum application threshold hostname. The node cannot start.
overridden to modified value
User response: Update the configuration to
Explanation: The default maximum threshold of specify the NodeDefLocale parameter.
30 applications per application node has been
overridden by modifying the
DTJ2501 Inbound call to phonenumber
dtj.node.application.threshold parameter in
rejected by SCR. Reason=reason.
the dtj.ini file.
Explanation: The System Call Router rejected a
User response: Reconfigure the WebSphere
call to the number phonenumber, because either
an application was not available, or no
by running the dtjit configuration tool file as
application was configured for calls to this
described in the “Updating the configuration
number. The System Call Router returned a
database” section of the WebSphere Voice
reason of - reason -.
Response for AIX manual. Alternatively, redefine
the existing groups defined in default.cff User response: Check that NumberToApp
manually so that each group contains fewer settings are correct; make sure that the phone
applications. number matches the number on which calls are
arriving. Also check that there are enough copies
of the application running and waiting for calls.

DTJ3000 • DTJ3014
Explanation: optionname requires a value to be

DTJ3000 A HostManagerImpl was found in
entered.
the RMI registry on this machine.
User response: Reenter the option with a valid
Explanation: The RMI registry has an entry for
value.
a HostManagerImpl. The system will attempt to
use this HostManagerImpl.
DTJ3008 value is not a valid value for
optionname
DTJ3001 The HostManagerImpl is not
responding. User response: Reenter the optionname option
with a valid value.
a HostManagerImpl, but it is not responding.
The system will create a new HostManagerImpl DTJ3009 A network error occurred during a
for this machine. action request.
DTJ3002 Creating a new HostManagerImpl running. Check that all remote machines and
for this machine. HostManagerImpls are running. Review the
printStackTrace() on stdout. If the error remains,
report this problem to your service
DTJ3003 The creation of the
representative.
HostManagerImpl for this
machine has failed.
has started.
running. Review the printStackTrace() on stdout.
If the error remains, report this problem to your
service representative. DTJ3011 Node nodename at host hostname
has stopped.
DTJ3004 The HostManagerImpl for this Explanation: Node nodename has stopped
machine was successfully created. following a quiesce stop request (for example,
stopNode).
DTJ3005 A HostManagerImpl for this
machine is already running. DTJ3012 Node nodename at host hostname
already started.
Explanation: You requested to start a
HostManagerImpl for this machine, but it is Explanation: You have requested to start node
already running. nodename, but it is already started. No action will
be taken.
User response: Check that you are requesting
the correct HostManagerImpl to start.
already stopped.
DTJ3006 optionname is not a valid option
Explanation: You have requested to stop node
User response: Check that the option is not
nodename, but it is already stopped. No action
misspelled and is valid.
will be taken.
DTJ3007 Missing value for option

optionname
has terminated.
Explanation: Node nodename has terminated

DTJ3015 • DTJ3025
following an immediate stop request (for hostname at port portnumber but it could not be
example, terminateNode). found.
User response: Check that the host machine is
DTJ3015 Starting voice response node running and that the HostManagerImpl is
nodename at host hostname. running. Check that the HostManagerImpl is
using the correct RMI port number. Use ping to
Explanation: The system will wait for up to 60
ensure that communications are available to the
seconds for the voice response node to start.
host.
DTJ3016 voice response node nodename at

DTJ3021 Host hostname is not responding.
host hostname has started.
host hostname, but it is not responding.
DTJ3017 voice response node nodename at
host hostname failed to start. User response: Check that the
HostManagerImpl is running.
Explanation: Node nodename has started but the
voice response node failed to start. Processing
will continue, and any other nodes in this start DTJ3022 There is no configuration for node
request will be started. This may be caused by an nodename at host hostname.
overloaded system, in which case the voice
Explanation: Configuration data could not be
response node may start later.
found for node nodename.
User response: Try to start the voice response
User response: Check that you are using the
node when no other programs are running. If the
correct configuration and that node nodename is
error remains, report this problem to your service
defined and enabled. Check that the node name
representative.
is not misspelled and is in the correct case.

DTJ3023 There is no configuration for host
could not be contacted.
hostname.
Explanation: This might be caused by one of
Explanation: Configuration data could not be
the following:
found for host hostname.
1. The node nodename abnormally terminating
User response: Check that you are using the
2. The host hostname abnormally terminating
correct configuration and that host hostname is
3. The communication link failing defined. Check that the host name is not
User response: Check the status of the node to misspelled and is in the correct case.
try to determine the cause of the error. If the
error remains, report this problem to your service DTJ3024 Configuration configurationname
representative. was not found in configuration
database databasename.
DTJ3019 Application applicationname was User response: Check that the configuration
started on node nodename at host name is not misspelled. Use the -action list
hostname. option of ConfigManager to see what
configurations exist in the configuration
DTJ3020 HostManager at host hostname at database.
port portnumber was not found.
Explanation: A request required access to host DTJ3025 Configuration database

DTJ3026 • DTJ3040
databasename was not found

DTJ3032 Host hostname is available.
not misspelled and that the database exists.
DTJ3033 Host hostname is not available.

DTJ3034 Node nodename at host hostname is
available.
databasename
DTJ3035 Node nodename at host hostname is
the file.
not available.
for additional information. Retry the operation. If
DTJ3036 applicationname, Inbound wait, at
the problem remains, recreate the configuration
telephony node-host
database.
nodename-hostname.
Explanation: This is from the output of the
DTJ3027 The request to start application
dtjqapps command. applicaitionname is waiting
applicationname on node nodename
for an inbound call from the voice response
at host hostname failed.
node-host nodename-hostname.
User response: Check that node nodename is
running on host hostname. Check that the class
DTJ3037 applicationname, Outbound wait, at
for application applicationname is in the Classpath
telephony node-host
for node nodename.
nodename-hostname.
DTJ3028 Starting node nodename at host
dtjqapps command. applicationname is waiting for
hostname. The system will wait for
an outbound call from the voice response
up to 60 seconds for the node to
node-host nodename-hostname.
start.
DTJ3038 applicationname, Active, at

telephony node-host
failed to start.
nodename-hostname.
Explanation: Processing will continue, and any
other nodes in this start request will be started.
dtjqapps command. applicationname is processing
This might be caused by an overloaded system,
a call from the voice response node-host
in which case the node might start later.
nodename-hostname.
User response: Try to start the node when no
other programs are running. If the remains,
DTJ3039 There are no applications active at
report this problem to your service
Node nodename at host hostname.
representative.
DTJ3040 applicationname, Inbound wait,

DTJ3030 Starting applications for node
from application node-host
nodename at host hostname.
nodename-hostname.
DTJ3031 Stopping node nodename at host
dtjqapps command. applicationname is running at
hostname.
nodename-hostname and is waiting for an inbound

DTJ3041 • DTJ3052
call from the voice response node-host

DTJ3047 No active telephony nodes were
nodename-hostname.
found at host hostname.
Explanation: A request was made to import or
DTJ3041 applicationname, Outbound wait,
export voice segments to host hostname but no
from application node-host
voice response node is active.
nodename-hostname.
User response: Start a voice response node on
host hostname and resubmit the request.
dtjqapps command. applicationname is running at
nodename-hostname and is waiting for an
outbound call from the voice response node-host DTJ3048 filename is not a valid
nodename-hostname. import/export voice file.
User response: Check that filename is a valid
DTJ3042 applicationname, Active, from import/export file and that the voice files it
application node-host refers to exist and are valid.
nodename-hostname.
Explanation: This is from the output of the DTJ3049 The following file was not found:
dtjqapps command. applicationname is running at filename.
nodename-hostname and is processing a call from
the voice response node-host nodename-hostname.
DTJ3050 I/O error during import/export
operation.
DTJ3043 Message log file filename was not
Explanation: The command is not able to access
found.
the file.
User response: Check that the file name is not
User response: Review the stack trace on stdout
misspelled and that the file exists.
for information about where the I/O error
occurred. If you have both the Simulator and
DTJ3044 Date and/or time are not in the WebSphere Voice Response for Windows
correct format. installed on the same machine you must ensure
that:
User response: Enter the date as yyyy/mm/dd
and the time as hh:mm:ss. 1. They are installed in completely separate
directories.
2. They are never both used at the same time.
DTJ3045 The following applications are
running at node nodename at host
You must completely shut down one version
hostname.
(both the host manager and the node) before
starting up the other.
DTJ3046 I/O error. The following data was
returned by the I/O system:...
DTJ3051 Successfully imported voicesegment
Explanation: The command is not able to create at host hostname at node nodename.
the file.
User response: If the input file is in error, DTJ3052 Failed to import voicesegment at
ensure that it is a valid message log file. If the host hostname at node nodename,
output file is in error, ensure that the directory reason is...
where the file is to be written exists, and that no
'read only' properties are stopping the creation of
the file.

DTJ3053 • DTJ3067
DTJ3053 Missing '=' at line linenumber in DTJ3062 The voice segment with
file filename segment_name, segment_category,
segment_locale does not exist on
node node at host host.
DTJ3054 parametername parameter missing
in file filename Explanation: The voice segment does not exist.
User response: Ensure that the name, category,
DTJ3055 Import hints, voice segment and locale have been specified correctly.
format, or export_type missing in
file filename.
DTJ3063 I/O error writing to file
User response: If you are importing, you must VoiceSegmentFile.
specify either import_hints or segment_encoding
Explanation: The command is not able to write
and segment_rate. If you are exporting, you must
the file.
specify export_type. For details, see WebSphere
Voice Response for AIX: Deploying and Managing User response: Ensure that there is enough disk
VoiceXML and Java Applications. space to write the file and, if it already exists, it
is not read-only.
DTJ3056 The parameter at line linenumber
in file filename has already been DTJ3064 An error occurred copying from
specified. node, host, segment_locale to
target_segment_name,
target_segment_category,
DTJ3057 The value for the parameter at
target_segment_locale on node node
line linenumber in file filename is
at host host. additional
invalid.
information if available
Explanation: An error occurred on the base
DTJ3058 The Wave file specified in file
WebSphere Voice Response system trying to copy
filename contains invalid data.
the voice segment.
DTJ3059 Successfully exported voicesegment

DTJ3065 The voice segment segment_name,
from host hostname.
segment_category, segment_locale was
successfully added on node node
DTJ3060 Failed to export voicesegment at at host host.
host hostname at node nodename,
reason is...
DTJ3066 I/O error occurred reading the
control file ControlFile during
DTJ3061 The voice segment with action action.
segment_name, segment_category,
segment_locale already exists on
the control file.
node node at host host and -replace
has not been specified. User response: Verify that the filename is
correct, and is accessible by the application.
User response: Specify the replace option to
replace the existing voice segment, or chose a
different name, category, or locale for the target DTJ3067 The voice segments on node node
voice segment. at host host have been listed in
VoiceSegmentFile.

DTJ3068 • DTJ3079

DTJ3068 The file filename is not terminated
replace the file or specify a different file name.
by a semi-colon (;).
Explanation: The control file entries are
DTJ3074 Error occurred adding voice
delimited by semi-colons. The last entry has not
segment language_identifier,
been delimited.
base_voice_directory,
User response: Add a semi-colon after the last base_segment_identifier,
entry in the file. segment_compression on node node
at host host.
DTJ3069 Error occurred adding voice Explanation: An error occurred on the base
segment base_segment_name, WebSphere Voice Response system trying to add
base_segment_database on node node the voice segment.
at host host.
Explanation: An error occurred on the base DTJ3075 ControlFile is not a valid control
WebSphere Voice Response system trying to add file.
the voice segment.
User response: Ensure that the control file is
valid.
DTJ3070 The voice segment with
name=segment_name,
DTJ3076 Application name was not found
category=segment_category,
in configuration.
locale=segment_locale successfully
deleted on node node at host host. Explanation: A request was made to start an
application that does not exist in configuration.
DTJ3071 An error occurred deleting voice
segment segment_name, DTJ3077 The source and target voice
segment_category, segment_locale on segments are the same,
node node at host host. name=segment_name,
category=segment_category,
Explanation: An error occurred on the base
locale=segment_locale.
WebSphere Voice Response system trying to
delete the voice segment. User response: Specify a different category,
name, or locale for the target voice segment.
User response: Check that all the details are
correct and that the voice segment exists.
DTJ3078 Encoding is not a supported
character encoding. The default
DTJ3072 The voice segment with
encoding will be used.
name=segment_name,
category=segment_category, User response: Ensure that the encoding is a
locale=segment_locale has been supported character encoding and is spelled
copied to target_segment_name, correctly.
target_segment_category,
target_segment_locale on node at host
host. DTJ3079 invalid parameter at line line number
in file control file is not a valid
parameter.
DTJ3073 The output file VoiceSegmentFile
already exits and -replace has not User response: Ensure that the parameter is
been specified valid and is spelled correctly.

DTJ3080 • DTJ3090
DTJ3080 The parameters DTJ3087 Base voice segment with

base_segment_name=name, name=base_segment_name and
base_segment_database=database database=base_segment_database has
are not valid on host name. already been added to node node
at host host.
Explanation: You have tried to add a
WebSphere Voice Response for Windows voice Explanation: Voice segments created within the
segment to a WebSphere Voice Response for AIX Java and VoiceXML environment cannot be
system. added to a voice response node.
DTJ3081 The parameters replace the file or specify a different file name.
base_language_identifier=identifier,
base_voice_directory= directory,
DTJ3088 Base voice segment with language
base_segment_identifier=identifier,
identifier=base_language_identifier,
base_segment_compression=
voice directory=base_voice_directory,
compression are not valid on host
segment
host.
identifier=base_segment_identifier
Explanation: You have tried to add a and segment compression =
WebSphere Voice Response for AIX voice base_segment_compression has
segment to a WebSphere Voice Response for already been added to node node
Windows system. at host host.
Explanation: Voice segments created within the
DTJ3082 An outbound session could not be Java and VoiceXML environment cannot be
created for line {0} on {1} at {2}. added to a voice response node.
Explanation: An error occurred when
communicating with the base WebSphere Voice DTJ3089 Base voice segment with
Response system when trying to create the name=base_segment_name and
session. This is only a warning; the voice database=base_segment_database
response node continues to start up. does not exist on node node at
host host.
DTJ3083 An inbound session could not be Explanation: You have tried to add a voice
created for line {0} on {1} at {2}. segment that does not exist.
Explanation: An error occurred communicating
with the base WebSphere Voice Response system DTJ3090 Base voice segment with language
when trying to create the session. This is only a identifier=base_language_identifier,
warning; the voice response node continues to voice directory=base_voice_directory,
start up. segment identifier=
base_segment_identifier and segment
compression=
DTJ3084 An inbound / outbound session
base_segment_compression does not
could not be created for line {0}
exist on node node at host host.
on {1} at {2}.
Explanation: You have tried to add a voice
Explanation: An error occurred when
segment that does not exist.
communicating with the base WebSphere Voice
Response system when trying to create the
session. This is only a warning; the voice
response node continues to start up.

DTJ3091 • DTJ3099
further processing is taking place due to the

DTJ3091 I/O error occurred performing
upgrade.
action name on node name at host
name User response: Do not enter any commands
until you see the message DTJ3095.
Explanation: The command is not able to
perform the specified action.
DTJ3095 The upgrade of voice response
User response: Ensure that the disk that
node name at host name to version
contains the base WebSphere Voice Response
number has completed.
system is not full or damaged.
Explanation: The system has completed the
upgrade. See also message DTJ3094.
DTJ3092 Unable to list the voice segments
on node name at host name. User response: The Java and VoiceXML
environment can now be used as normal.
Explanation: An error occurred when an
attempt was made to access the voice segment
database on the voice response node. DTJ3096 The upgrade of voice response
node name at host name to version
User response: Check that the node and host
number failed because reason.
are correct. Check that the node is running.
Check that the network is functioning correctly Explanation: The system could not upgrade the
voice response node due to the specified reason.
See also message DTJ3094.
DTJ3093 The base WebSphere Voice
Response system at node name on User response: The specified reason will give
host name is not responding. more information about the cause of the error.
Retrying... Possible causes include lack of disk space, long
voice segment names and the existence of more
Explanation: The Java and VoiceXML
than one voice segment with the same name.
environment tried to establish a connection with
WebSphere Voice Response, but WebSphere Voice
Response is not running. The Java and VoiceXML DTJ3097 The character encoding used in
environment will keep trying to establish the the control file filename is not
connection. supported.
User response: Check that WebSphere Voice User response: Ensure that the
Response is running, if not, restart it. If the character_encoding keyword in the control file
AIXPortNumber configuration parameter is contains a valid value. If you are using the Java
specified, make sure the number matches the Runtime Environment (JRE), make sure that the
CHPM Socket Port Number on WebSphere Voice internationalization (i18n) support has been
Response. installed.
DTJ3094 The voice response node name at DTJ3098 Log file filename has been
host name is being upgraded to formatted into formatted_filename.
version number. This may take
some time.
DTJ3099 Voice segment with name=name,
Explanation: This message may be seen when category=category and locale=locale
the Java and VoiceXML environment is started on voice response node nodename
after the WebSphere Voice Response system has at host hostname contains long
been upgraded. The message indicates that field name(s).
Explanation: In later releases the lengths of the

DTJ3100 • DTJ3107
voice segment name and category and the locale

DTJ3104 In future releases, voice segments
variant are restricted.
will not be able to have such long
User response: Contact IBM for help. field names. The following voice
segments have field names longer
than will be permitted. These
DTJ3100 Voice segment with name=name, voice segments should be copied
category=category and locale=locale to voice segments with shorter
on voice response node nodename field names and the original voice
at host hostname contains field segment deleted. The limits for
name(s) too long to be upgraded. voice segment fields are name
Explanation: Long field names in voice length = length, category length =
segments are no longer supported. length and locale variant length =
length. Applications which use
User response: Contact IBM for help. these voice segments will also
need to be changed. Please contact
DTJ3101 The exceptionmessage field of the IBM for help.
voice segment with name=name,
category=category and locale=locale DTJ3105 The following voice segments
on the voice response node have field names that are longer
nodename at host hostname is too than the limits now supported.
long. These voice segments cannot
Explanation: The maximum length for the name currently be used. They need to
is 20, the maximum length for the category is 20, be imported from the audio file
and the maximum length for the locale variant is indicated by the "file_name="
9. field and given shorter field
names. The limits for voice
segment fields are name length =
DTJ3102 See file {0} on node nodename at length, category length = length
host hostname for more and locale variant length = length.
information about the voice Applications which use these
segments with long field names. voice segments will also need to
be changed. Please contact IBM
DTJ3103 See file {0} on node nodename at for help.
host hostname for more
information about the voice DTJ3106 Voice response node nodename at
segment field names that are too host hostname contains voice
long to upgrade.. segments with long field names.
Explanation: In later releases the lengths of the
voice segment name and category and the locale
variant will be restricted.
User response: Contact IBM for help.
DTJ3107 Voice response node nodename at

host hostname failed to start
because it is using an invalid
locale locale.

DTJ3108 • DTJ3131
Explanation: The variant field of the locale User response: Check that the audio files
must be 9 characters or less in length. contain valid data.
DTJ3108 The locale locale of the voice DTJ3115 The version of Host Manager
response node nodename at host running is incompatible with this
hostname will not be valid in command. Please terminate the
future releases. Host Manager manually.
Explanation: The variant field of the locale
must be 9 characters or less in length.. DTJ3120 The number of applications of
type name waiting for inbound
calls has fallen below the
DTJ3109 Application name could not be
threshold of waiting threshold.
started on node nodename at host
hostname because the locale locale Explanation: There are only a small number of
is not valid. applications of the specified type waiting for
inbound calls. If more calls arrive, they may be
rejected.
must be 9 characters or less in length..
User response: Consider configuring more
applications of this type to start.
DTJ3110 The locale locale of the application
name running on node nodename
at host hostname will not be valid DTJ3130 Last heartbeat was between 60 to
in future releases. 90 seconds ago for application (0)
at node (1)
must be 9 characters or less in length.. Explanation: A heartbeat between the voice
response node and a voice application is
expected every 45 seconds. The last heartbeat
DTJ3112 Host hostname cannot be contacted
with the named voice application and node was
to determine the state of the
received between 60 to 90 seconds ago,
nodes.
indicating that the voice application may have
Explanation: The HostManager cannot be lost contact with the voice response node.
contacted on the specified host.
User response: If there are no network
User response: Ensure that the host system is problems, contact support.
running and if necessary, start the HostManager
by running dtjshost from the host system’s
DTJ3131 Heartbeat with applicationname at
command line.
node nodename has failed
Explanation: The voice response node has lost
DTJ3113 Opening log file <log file name>.
contact with the named application and node.
Explanation: Log messages will be written to This could be caused by either the voice
the log file. application or the application node terminating
unexpectedly, or by network problems. The voice
application running at the named node will not
DTJ3114 The au file specified in file <file> handle any more calls.
contains invalid data.
User response: Check that the application node
Explanation: This message will occur when has not stopped unexpectedly and that there are
importing Java voice segments. no network problems.

DTJ3132 • DTJ5010
PTFs to the system, especially if a PTF includes

DTJ3132 Recovering the CallTokens
modifications to the configuration values that can
Explanation: If the voice application with the be added to configuration file default.cff.
failed heartbeat was waiting for a call, the call
User response: Run dtjconf to refresh.
has been cancelled. Any calls that were being
processed by the voice application have been
returned. DTJ3139 dtjcache - message text
User response: If there are no network DTJ3139 is a general purpose message that
problems, contact support. relays the output from the dtjcache command.
DTJ3133 RMIRegistry cannont be created - DTJ4500 CallPath support not active!

Check that the HostManager Unable to load required CallPath
process has terminated. support class.
User response: If there is a HostManager Jjava Explanation: CallPath support could not be
process still running, even after dtjshost -exit has activated as the system was unable to load the
been run, terminate this process manually and class
then restart the HostManager. com.ibm.telephony.beans.callpath.CPLineResource
User response: Ensure that the CallPath support

DTJ3134 Unable to exit Hostmanager, child classes (ibmcpath.jar) are accessible via
processes still executing. CLASSPATH.
User response: Check that all the nodes that
were started under this Hostmanager have DTJ4501 CallPath support not active!
already exited, then re-run dtjshost -exit. Exception while loading support
class (exceptionname).
DTJ3135 Found number CCXML Explanation: CallPath support could not be
applications runing on number activated as the system encountered an exception
nodes. exceptionname while attempting to load the class
com.ibm.telephony.beans.callpath.CPLineResource
DTJ3136 Service name on Node nodename on User response: Ensure that the CallPath support
Host hostname running number classes (ibmcpath.jar) are accessible via
Applications Started start-time CLASSPATH.
UpTime up-time
DTJ4502 CallPath could not find an active
DTJ3137 Application "name" Service "name" connection item for address <line
URI "uri" Started start-time address>.
UpTime up-time Explanation: The CallPath support is not
functioning correctly.
DTJ3138 Configuration database filename User response: Ensure that everything is
may be from previous release, run configured correctly.
dtjconf to refresh.
Explanation: The identified configuration DTJ5010 The speech recognition plug-in
database file is not recognized as a valid specified plugin could not be
configuration database file for the current version found.
of WebSphere Voice Response. This error can
occur after applying WebSphere Voice Response Explanation: The configuration for this voice

DTJ5011 • DTJ5020
response node and this application specifies the corresponding RecoService entry is in the node
plug-in class to be used for speech recognition configuration. Otherwise, configure the
for the current locale. This class could not be application to use an available speech recognition
found. technology, or stop trying to run the application.
User response: Ensure that the class is
accessible via CLASSPATH. DTJ5014 A speech recognition plug-in
caused a runtime exception.
Details follow...
DTJ5011 The speech recognition plug-in
specified {0} is not a speech Explanation: A speech recognition plug-in
recognition plug-in. caused a runtime exception to occur, which was
detected and caught by the Java and VoiceXML
Explanation: A speech recognition plug-in must
environment. The details of the exception are
extend
included in the error message.
com.ibm.telephony.directtalk.RecoAsynchPlugIn.
The class specified is not a speech recognition User response: Report the error to the supplier
plug-in. of the plug-in and provide them with the details
to assist in diagnosing the problem.
User response: Ensure that the correct class is
specified in the configuration and that the correct
version is accessible via CLASSPATH. DTJ5015 A speech recognition plug-in has
failed with the following reported
error...
DTJ5012 Speech recognition is not
configured for locale locale on this Explanation: A speech recognition plug-in has
node. detected an error condition.
Explanation: To find a speech recognition User response: Correct the reported error, or
service that can provide speech recognition for report it to the supplier of the plug-in. Report
an application, the application or the voice also an any other details that might assist with
response node (or both) must be configured diagnosing the problem.
correctly. The application must be configured to
specify which recognition technology is required
DTJ5016 A speech recognition plug-in has
for each locale (or defaults must be specified on
returned an unexpected error code
the node), and this must match the technology
{0} along with the following
available on the node. None could be found to
details...
match the locale.
Explanation: A speech recognition plug-in has
User response: Ensure that the configuration is
returned an error code that the Java and
correct. For details please refer to the WebSphere
VoiceXML environment did not understand.
Voice Response for AIX: Developing Java applications
book. User response: Report the error to the supplier
of the plug-in. Report also any other details that
might assist with diagnosing the problem.
DTJ5013 No RecoService for RecoType {0}
configured for this node.
DTJ5020 The text to speech plug-in
Explanation: The application has requested
specified {0} could not be found.
speech recognition of the given RecoType, but
this voice response node is not configured with a Explanation: The configuration for this voice
RecoService that provides this RecoType. response node and this application specifies the
plug-in class to be used for text to speech for the
User response: If the recognition technology is
current locale. This class could not be found.
available on this node, ensure that a

DTJ5021 • DTJ6000
User response: Ensure that the class is

DTJ5024 A TTS plug-in caused a runtime
accessible via CLASSPATH.
exception. Details follow...
Explanation: A TTS plug-in caused a runtime
DTJ5021 The text to speech plug-in
exception to occur, which was detected and
specified {0} is not a text to speech
caught by the Java and VoiceXML environment.
plug-in.
The details of the exception are included in the
Explanation: A text to speech plug-in must error message.
extend
User response: Report the error to the suppliers
com.ibm.telephony.directtalk.TTSPlayPlugIn or
TTSGeneratePlugIn. The class specified is not a
text to speech plug-in. This error is not reported
if the wrong TTS plug-in type has been specified
in the configuration. DTJ5025 A TTS plug-in has failed with the
following reported error...
User response: Ensure that the correct class is
specified in the configuration and that the correct Explanation: A TTS plug-in has detected an
version is accessible via CLASSPATH. error condition.
User response: Correct the reported error or
DTJ5022 Text to speech is not configured report it to the suppliers of the plug-in. Report
for locale {0} for this application also any other details that might assist with
and node. diagnosing the problem.
Explanation: To find a text to speech service
that can provide text to speech for an DTJ5026 A TTS plug-in has returned an
application, the application or voice response unexpected error code {0} along
node (or both) must be configured correctly. The with the following details...
application must be configured to specify which
Explanation: A TTS plug-in has returned an
text to speech technology is required for each
error code that the Java and VoiceXML
locale (or defaults must be specified on the
environment did not understand.
node), and this must match the technology
available on the node. User response: Report the error to the suppliers
User response: Ensure that the configuration is
correct. For details please refer to WebSphere Voice
Response for AIX: Developing Java applications.
DTJ6000 Unable to locate the audio cache.
Check that the VXML
DTJ5023 No TTSService for TTSType {0}
DTPlayURLPlugIn is defined in
configured for this node.
the configuration database.
Explanation: The application has requested text
Explanation: The VoiceXML browser is unable
to speech of the given TTSType, but this voice
to find the audio cache.
response node is not configured with a
TTSService that provides this TTSType. User response: Check that the VoiceXML plugin
DTPlayURL is defined in the configuration
User response: If the text to speech technology
database.
is available on this node, ensure that a
corresponding TTSService entry is in the node
configuration. Otherwise, configure the
application to use an available text to speech
technology, or stop trying to run the application.

DTJ6001 • DTJ6306
details of some of these errors.

DTJ6001 Unable to locate the audio cache.
Please check that the voice
response node has started and/or DTJ6301 SRGS grammar has no root rule
specify the correct voice response declared.
node to use.
Explanation: The grammar does not have a root
Explanation: The VoiceXML browser is unable rule, which is required by the VoiceXML browser.
to find the audio cache.
User response: Check the syntax of the
User response: Check that the voice response specified grammar and ensure that a public root
node has been started and that the correct voice rule is defined.
response node has been specified.
DTJ6302 Application loop detected.

DTJ6002 Unable to locate the audio cache. Recursive entry to catch block.
Please check that the voice
response node has started. Explanation: The VoiceXML browser has
detected that a catch block may be throwing the
Explanation: The VoiceXML browser is unable same event as it will catch, thus creating an
to find the audio cache. infinite execution loop.
User response: Check that the voice response User response: Check the VoiceXML
node has been started. application, and remove the potential for this
situation by ensuring that a catch block does not
throw an event type that it is subsequently
DTJ6100 No resources are available for
required to catch.
speech recognition. The use of
speech recognition is being
disabled. DTJ6303 Unable to set locale of call to ...
Explanation: Required resources for speech Explanation: The VoiceXML was unable to set
recognition are not available. the Locale for the call to the value specified.
User response: Check that the ViaVoice® User response: Ensure that the Locale trying to
Custom Server is running. Also check the be set is a valid Java Locale type.
configuration of the plugin in default.cff.
DTJ6304 Exiting due to uncaught event
DTJ6200 Unable to proceed, lost contact
with the VR node. The VR node Explanation: The VoiceXML browser's default
may have stopped or there may be catch handler was invoked for the specified
network problems. event
Explanation: The voice response node cannot be User response: This is not necessarily an error.
contacted. If necessary, implement a catch block in the
VoiceXML page to handle the event.
User response: Check that the voice response
node is still running. Also check the network
connectivity and throughput. DTJ6305 Caller has hung up
Explanation: Not an error. The caller hung up.
DTJ6300 message text User response: Not required
Explanation: This message code covers various
errors output by the VoiceXML 1.0 browser. See DTJ6306 Document interpretation complete
“Messages and explanations” on page 447 for

DTJ6307 • DTJ7004
Explanation: Not an error. The VoiceXML number of seconds to wait between preload
browser form interpretation algorithm has attempts.
finished processing the VoiceXML application
Module: DTVoicelet2
Severity: Warning
DTJ6307 Disconnecting
Explanation: Not an error. The VoiceXML
DTJ7001 VXML browser preload failed.
browser has executed a disconnect tag and has
Error text: error
hung up the call.
Explanation: The VoiceXML Browser has been
User response: Not required
configured to preload an initial document while
initializing, but the preload operation failed.
DTJ6308 Root rule of SRGS grammar is not
User response: Check that the document to be
declared public. Rule name= .
preloaded exists and can be accessed from the
Explanation: The root rule of the specified rule machine on which the browser is running.
has not been declared as being public.
Module: DTVoicelet2
Severity: Error
specified rule and ensure that the root rule is
declared as being public
DTJ7002 VXML browser timed out waiting
for call - delaying nms before
DTJ6309 Rule not defined. Rule name=
cycling.
Explanation: The specified rule does not have a
Explanation: The time that the VoiceXML
root rule defined.
Browser waits for a connection has been
User response: Check the syntax of the exceeded.
grammar and ensure that the specified rule has a
User response: Check the appropriate
root rule defined.
WebSphere Voice Response and telephony service
logs for further information.
DTJ6310 No root rule defined for external
Module: DTVoicelet2
SRGS grammar. src= .
Severity: Information
Explanation: The externally specified grammar
does not have a root rule defined.
DTJ7003 VXML browser caught an
exception: exception, cause: cause
specified grammar and ensure that there is a
public root rule defined. Explanation: The VoiceXML Browser session
ended for the reasons stated. Additional
information is provided in message 1007035.
DTJ7000 Invalid preload retry interval
number specified in default.cff. User response: Examine the messages to
Defaulting to n seconds. determine cause of the exception and then
correct the problem.
Explanation: The initial document preload retry
interval value specified in configuration file Module: DTVoicelet2
default.cff is not valid.
Severity: Error
User response: Edit default.cff to correct the
value specified for the preload retry interval.
Valid values are: -1 to disable retry or a positive DTJ7004 Cache preload failed. No URI

DTJ7005 • DTJ7011
parameters were specified.

DTJ7008 Assert failed:
Explanation: The VoiceXML Browser has been VXML2BrowserLauncher
configured to preload an initial document after .asyncPlay, playList not empty.
initializing, but no URI was specified for the
Explanation: The VoiceXML Browser could not
document in configuration file default.cff.
be launched because unplayed audio data is
User response: Edit default.cff to specify a URI waiting in a queue to be played.
value for the preload document.
User response: This error should not occur.
Module: DTVoicelet2 Contact IBM support.
Severity: Error Module: VXML2BrowserLauncher

Severity: Error
DTJ7005 Cache preloading, URI=URI
Explanation: The VoiceXML Browser has been DTJ7009 AsyncPlay audioproxy Exception
configured to preload an initial document after on open: exception Stack trace: trace
initializing. The document is currently being
Explanation: Cached audio data could not be
loaded.
played because the cache was not in an open
User response: None required. state.
Module: DTVoicelet2 User response: Fatal error. Examine preceding

messages to determine root cause of the problem.
Module: VXML2BrowserLauncher
DTJ7006 VXML BrowserException caught: Severity: Error
exception
Explanation: The VoiceXML Browser session DTJ7010 AsyncPlay audioproxy Exception:
ended for the reasons stated. Additional exception Stack trace: trace
Explanation: The VoiceXML Browser was
User response: Examine the messages to unable to play cached audio data.
determine cause of the exception and then
User response: Examine the exception and stack
correct the problem.
trace in the message to determine the cause of
Module: DTVoicelet2 the error.

Severity: Error
DTJ7007 RMI RemoteException caught:
remote exception
DTJ7011 Unexpected event occurred during
Explanation: The VoiceXML Browser session AsyncPlay: event
ended for the reasons stated. Additional
Explanation: A problem occurred when the
VoiceXML Browser was playing cached audio
User response: Possible network problem. data.
Examine the messages to determine the cause of
User response: The event detailed in the
the exception and then correct the problem.
message was not expected during AsyncPlay. If
Module: DTVoicelet2 the cause is not apparent, contact IBM support.

DTJ7012 • DTJ7018
Severity: Error reference had not yet been allocated by the

VoiceXML Browser.
DTJ7012 Unexpected event occurred during User response: This error should not occur.
stopAsyncPlay: event Contact IBM support.
Explanation: A problem occurred when the Module: VXML2BrowserLauncher
VoiceXML Browser finished playing cached
Severity: Error
audio data.
User response: The event detailed in the
DTJ7016 Unable to continue running
message was not expected during this operation.
because the VRnode is down.
If the cause is not apparent contact IBM support.
Explanation: The VoiceXML Browser has been
configured to preload an initial document after
Severity: Error initializing, but the preload operation failed
because the Voice Response node is no longer
available.
waitForInput: event User response: Examine preceding messages to
determine the cause of the problem with the
VR-node.
VoiceXML Browser was waiting for a response
from a user. Module: VXML2BrowserLauncher
User response: The event detailed in the Severity: Error
message was not expected during this operation.
If the cause is not apparent contact IBM support.
DTJ7017 Waiting for VRnode to start. Will
Module: VXML2BrowserLauncher try again in 5 seconds.
Severity: Error Explanation: The VoiceXML Browser has been
configured to preload an initial document after
initializing, but the preload operation cannot
start until the Voice Response node has started.
waitForOutput: event
User response: Wait until the Voice Response
node has started.
VoiceXML Browser was waiting for a response
from a speech recognition, text-to-speech, or Module: VXML2BrowserLauncher
other resource.
Severity: information
User response: Check that the problem resource
is operating correctly and can communicate with
DTJ7018 ServiceException setting
the VoiceXML Browser.
properties. Stack trace: trace
Explanation: The VoiceXML Browser had a
Severity: Error problem getting the default audio properties
from the configuration file dtj.ini.
DTJ7015 Audio cache proxy is null. Unable User response: Check that the configuration file
to set properties. dtj.ini exists and can be accessed by the
VoiceXML Browser.
Explanation: The audio cache could not be
instantiated because the required resources and Module: VXML2BrowserLauncher

DTJ7019 • DTJ7025
Severity: Error
DTJ7022 Unable to obtain a call token,
exception: exception
DTJ7019 Exception thrown while finding a
Explanation: An exception was generated when
matching grammar: exception Stack
attempting to contact the base WebSphere Voice
trace:trace
Response system to obtain a call token.
Explanation: The VoiceXML Browser had a
problem finding an appropriate speech
recognition grammar for a context in the
logs for further information.
telephone call with the ID specified.
Module: DTTelServiceSupport
User response: Validate the document and
grammars producing the exception. If the cause Severity: Error
cannot be determined, contact IBM support.
Module: VXML2BrowserLauncher DTJ7023 DTTelServiceSupport
.fireDisconnectEvent() caught a
Severity: Error
NoSuchElementException:
exception Stack trace: trace
DTJ7020 Unable to continue as the system
Explanation: The VoiceXML Browser was
property dtj.home is not set.
unable to disconnect from a telephony service
Explanation: The VoiceXML Browser could not connected to WebSphere Voice Response.
be launched because the required value for the
dtj.home environment variable was not set.
User response: Set the value of the dtj.home logs for further information.
environment variable to the pathname of the
Module: DTTelServiceSupport
directory where WebSphere Voice Response Java
and VoiceXML Environment is installed. (The Severity: Error
default is /var/dirTalk/DTBE. )
Module: VXML2BrowserLauncher DTJ7024 ServiceException during property
initialisation: exception Stack trace:
Severity: Error
trace
Explanation: Speech recognition parameters
DTJ7021 Unable to create browser cache
defined in the RecoService entry in file
directory: directory
default.cff could not be set when the
Explanation: The VoiceXML Browser was RecoService was initialized.
unable to create a cache directory at the default
User response: Check access to and contents of
location or that specified in configuration file
the configuration file default.cff, where speech
dtj.ini.
recognition parameters must be defined in a
User response: Check that the user has the RecoService entry.
necessary permissions to create directories in the
Module: DTAsrService
directory set for dtj.home or specified in
configuration file dtj.ini. Severity: Error
DTJ7025 AudioService play unable to open
Severity: Error
audio proxy, Exception: exception
Stack trace: trace

DTJ7026 • DTJ7032
Explanation: Cached audio data could not be

DTJ7029 IOException while getting FSG:
played because the cache was not in an open
state.
Explanation: The precompiled finite state
User response: Internal error. Try stopping and
grammar could not be found or accessed at the
restarting the RecoService.
specified URL or location.
Module: DTAudService
User response: Check that the URL or location
Severity: Error specified for the precompiled finite state
grammar in the RecoService entry in
configuration file default.cff is correct.
DTJ7026 Exception thrown in
DTAudService.play: exception Module: DTGrammarCache
Stack trace: n
Severity: Error
Explanation: There was an error in playing
cached audio data.
DTJ7030 Failed to compile grammar.
User response: Check the resource where the Error=error. The grammar that
cache is located, access to the cache, and the failed to compile was grammar,
integrity of the data. You may need to increase locale=locale, mediaType=media
the space available for the cache or the amount type, grammar source=source
of memory in the machine running speech
Explanation: The speech recognition grammar
recognition.
compiler could not compile the specified
Module: DTAudService grammar for the named locale and media type.
Severity: Error User response: Check that the locale and media
type are correct and that the grammar exists in
the specified source file. Check that the format of
DTJ7027 vxml2.DTAudioCache Initialising the grammar is correct and is compatible with
Explanation: Audio parameters are being the compiler.
verified and cached. Module: DTGrammarCache
User response: Wait until initialization is Severity: Error
complete.
Module: DTAudioManagerImpl DTJ7031 Unable to create a new compiler
Severity: Information service manager. Stack trace: trace
Explanation: Internal error. The speech
DTJ7028 vxml2.DTAudioCache recognition grammar compiler could not be
Initialisation complete - Loaded started.
sucessfully User response: Try stopping and restarting the
Explanation: Audio cache initialization is RecoService.
complete. All audio parameters have been loaded Module: DTGrammarCache
successfully.
Severity: Error
User response: No action required.
Module: DTAudioManagerImpl DTJ7032 MalformedURLException caught
Severity: Information in getFSG: exception Stack trace:
trace

DTJ7033 • DTJ7038
Explanation: The URL specified for the Explanation: Additional information provided
precompiled finite state grammar was not for message 1007003
formatted correctly.
User response:
User response: Correct the URL specified for
Module: DTVoicelet2
the compiled finite state grammar in the
RecoService entry in configuration file Severity: Error
default.cff.
Module: DTGrammarCache DTJ7036 VXML2BrowserLauncher
.initSystemwideProperties. Invalid
Severity: Error
value specified for parameter
wvr.vxml2.memcachesize: n. This
DTJ7033 VXML2BrowserLauncher value must be a non negative
.initSystemwideProperties. Cannot integer value in KB units.
create URI for builtInPath: path
Explanation: The Java system property for the
Explanation: The VoiceXML Browse cannot be size of the grammar memory cache is not valid.
launched because of a problem setting the
User response: Specify the Java system property
default path to the grammar cache:
as a positive integer value in KB units.
$dtjhome/vxml2/grammars
User response: Check that the value of the
dtjhome environment variable is set correctly and Severity: Error
that default path to the grammar cache is valid
for your system.
DTJ7037 VXML2BrowserLauncher
Module: VXML2BrowserLauncher .initSystemwideProperties. Invalid
Severity: Error
wvr.vxml2.filecachesize: n. This
value must be a non negative
DTJ7034 VXML2BrowserLauncher. integer value in KB units.
initSystemwideProperties. Cannot
Explanation: The Java system property for the
create URI for siteDocPath: path
size of the grammar file cache is not valid.
Explanation: The VoiceXML Browse cannot be
User response: Specify the Java system property
launched because of a problem setting the
as a positive integer value in KB units.
default path to a site document:
dtjhome/vxml2/site/ (or dtjhome/vxml2/ Module: VXML2BrowserLauncher
site.dtmfonly/ for a dtmf site document.)
Severity: Error
User response: Check that the value of the
dtjhome environment variable is set correctly and
that default path to the site document is valid for DTJ7038 IOException caught in getFSG:
your system. exception Stack trace: trace
Module: VXML2BrowserLauncher Explanation: The precompiled finite state

grammar could not be found or accessed at the
Severity: Error specified URL or location.
User response: Check that the URL or location
DTJ7035 (Additional information: Stack specified for the precompiled finite state
trace: trace) grammar in the RecoService entry in
configuration file default.cff is correct.

DTJ7039 • DTJ7044
Module: DTGrammarCache
DTJ7042 DTMF grammar cache statistics:
Severity: Error hit rate=n%, miss rate=n%, cache
warnings=n, last warning=date,
mem usage=n%, disk usage=n%,
DTJ7039 VXML2BrowserLauncher average mem=n%, average
.initSystemwideProperties. Invalid disk=n%
wvr.vxml2.maxage: n. This value Explanation: Statistics on usage of the DTMF
must be a non negative integer grammar cache:
value in KB units. v Speech recognition success rate
Explanation: The Java system property for the v Speech recognition failure rate
maximum age of grammar fetched from the v Date of last cache capacity warnings, if any
grammar file is not valid
v Cache capacity warnings
User response: Specify the Java system property v Memory usage
as a positive number of seconds.
v Disk usage
User response:
Severity: Error
DTJ7040 IOException while getting FSG:
DTJ7043 ASR grammar cache statistics: hit
Explanation: A precompiled finite state
rate=n%, miss rate=n%, cache
grammar (.FSG) file could not be loaded.
warnings=n, last warning=date,
User response: Check that the grammar exists mem usage=n%, disk usage=n%,
and can be accessed from the machine running average mem=n%, average
speech recognition. disk=n%
Module: DTGrammarCache Explanation: Statistics on usage of the

non-DTMF grammar cache:
Severity: Error
v Speech recognition success rate
v Speech recognition failure rate
DTJ7041 Grammar cache reaching capacity.
Cleanup was unable to find v Date of last cache capacity warnings, if any
sufficient unused grammars. v Cache capacity warnings
Memory at n%, disk at n%. v Memory usage
Explanation: Large grammars may no longer be v Disk usage
added to the grammar cache. Speech recognition
User response:
performance is likely to deteriorate if all the
available space is used up. Module: DTGrammarCache
User response: Increase the size of the grammar Severity: Information
cache.
Module: DTGrammarCache DTJ7044 The grammar cache is full.
Overcommitment of resources
Severity: Warning
may result. Memory at n%, disk at
n%.

DTJ7045 • DTJ7051
Explanation: No more grammars can be added Explanation: The VoiceXML Browser was
to the grammar cache. Speech recognition unable to connect with an incoming telephone
performance is likely to deteriorate if additional call to the WebSphere Voice Response system.
grammars are compiled or specified.
User response: Examine the exception in the
User response: Increase the size of the grammar message to determine the cause of the error.
cache. For instructions on how to do this, refer to
Module: DTVoicelet2
the section “Increasing the grammar cache size”
in WebSphere Voice Response for AIX: VoiceXML Severity: Error
Programmer's Guide .
Severity: Error
DTJ7045 (Additional information: Stack

trace: trace)
Explanation: Additional information provided
for message 1007007
User response:
Module: DTVoicelet2
Severity: Error
DTJ7046 (Additional information: Stack

trace: trace)
Explanation: Additional information provided
for message 1007006
User response:
Module: DTVoicelet2
Severity: Error
DTJ7050 VXML browser terminated with

exception exception delaying nms
before cycling.
Explanation: The VoiceXML Browser session
ended for the reasons stated.
User response: Examine the exception in the
message to determine the cause of the error.
Module: DTVoicelet2
DTJ7051 VXML browser unable to get

inbound call. Exception exception

ISDN_XFER000 • ISDN_XFER002
ISDN_Call_Transfer custom server

The ISDN_Call_Transfer custom server issues the following types of message:
v Red messages are issued for all fatal problems.
v Yellow messages are warnings of any problems that may cause future
failures.
v White messages give information.
The messages are issued as standard custom server messages. The

ISDN_Call_Transfer custom server error title and ID are shown in parameters
1 and 2 of the standard custom server errors. The error IDs have the form
ISDN_XFERnnn. The remaining parameters contain information specific to the
particular error.
When you call, you will need details of any errors, your system setup, and
details of the conditions that cause the problem. You may also require an AIX
system trace taken when the problem occurs. Before taking the trace, set the
-d option in the custom server. For more information on the command line
options see the section on configuring the custom server in the WebSphere
Voice Response for AIX: Designing and Managing State Table Applications.
one or more white notification messages being
ISDN_XFER000 Unknown error
issued.
Explanation: The custom server tried to enroll
User response: Correct the problem as indicated
an error that was out of range. The error ID it
in the white notification messages that were
tried to enroll is given as one of the parameters.
enrolled immediately before this error.
User response: Restart the ISDN_Call_Transfer
Severity: Red (errorid = 20504)
custom server.
Destination: Log, System Monitor.
If the problem persists, before calling IBM
Support, take an AIX system trace while
re-creating the problem. Specify the -d command ISDN_XFER002 Failed to fork() required
line parameter for the custom server. number of child processes.
Exiting...
Explanation: The custom server could not fork()
the required number of child helper processes.
This probably means that AIX is not configured
ISDN_XFER001 Failed to initialize the custom to allow sufficient processes per user.
server. Exiting...
User response: Check that the command line
Explanation: The custom server could not be parameter -pn has not been set up to request an
initialized because there are errors in either the unreasonably large number of child helper
command line parameters or in setting up the processes.
internal memory and communication
Check that AIX is configured to allow sufficient
requirements. This error is issued as a result of
processes per user.

Severity: Red (errorid = 20504) User response: Correct the command line
argument. You can see the command line
arguments by selecting Properties from the File
window for this custom server. For permitted
ISDN_XFER003 Failed to retrieve WebSphere command line arguments for this custom server,
Voice Response information using see the section on configuring the custom server
CA_Get_DT_Info() in the WebSphere Voice Response for AIX: Designing
and Managing State Table Applications.
Explanation: The custom server was unable to
retrieve system information about WebSphere Severity: White (errorid = 20501)
Voice Response. This will generate fatal error
ISDN_XFER001.
ISDN_XFER006 - Failed to create message
Response. If the problem persists, before calling
queue for internal
IBM Support, take an AIX system trace while
communications
re-creating the problem. Specify the -d command
line parameter for the custom server. Explanation: The custom server could not create
the internal message queues required for internal
Severity: White (errorid = 20501)
communications between the parent process and
Destination: Log, System Monitor. the child helper processes. This will generate
fatal error ISDN_XFER001.
ISDN_XFER004 Failed to malloc() memory User response: Before calling IBM Support, take
an AIX system trace while re-creating the
Explanation: The custom server was unable to problem. Specify the -d command line parameter
malloc() memory for its internal requirements. for the custom server.
This is likely to occur if the system does not
have sufficient main memory or paging space Severity: White (errorid = 20501)
available. This will generate fatal error
ISDN_XFER001.
User response: Shut down some other tasks
ISDN_XFER007 Failed to fork() a child process
running on the system to free up memory or
paging space. Explanation: A child helper process could not
be created. This will generate fatal error
If the problem occurs at startup, before calling
ISDN_XFER002.
IBM Support, take an AIX system trace while
re-creating the problem. Specify the -d command User response: Check the AIX errno given in
line parameter for the custom server. the other parameters for the failure reason. If this
does not help, before calling IBM Support, take
Severity: White (errorid = 20501
Destination: Log, System Monitor. problem. Specify the -d command line parameter
for the custom server.
ISDN_XFER005 Invalid commandline Severity: White (errorid = 20501)

argument
Explanation: One of the command line
arguments used to start the custom server was
ISDN_XFER008 Polling for messages failed
invalid. The invalid argument is printed as one
of the parameters in the error details. This will Explanation: A call to CA_Poll() failed.
generate fatal error ISDN_XFER001.
User response: Check the CA_errno given in

the other parameters for the failure reason. If this internal message queues is not functioning
does not help, before calling IBM Support, take correctly.
problem. Specify the -d command line parameter
custom server.
If the problem persists, take an AIX system trace
while re-creating the problem. Specify the -d
Destination: Log, System Monitor. command line parameter for the custom server.
Then call IBM Support.
ISDN_XFER009 CA_Poll indicated a message Yellow (errorid = 20503)
waiting, but it couldn’t be
Log, System Monitor.
received
Explanation: CA_Poll() indicated that there was
ISDN_XFER012 Internal message could not be
a message to process, but CA_Receive_DT_Msg()
recognized
failed.
Explanation: A message on one of the internal
message queues could not be recognized as a
the other parameters for the failure reason. If this
valid message.
does not help, before calling IBM Support, take
an AIX system trace while re-creating the User response: Restart the ISDN_Call_Transfer
problem. Specify the -d command line parameter custom server.
Severity: White (errorid = 20501) while re-creating the problem. Specify the -d
command line parameter for the custom server.
Then call IBM Support.
Yellow (errorid = 20503)
ISDN_XFER010 Internal message could not be
sent Log, System Monitor.
Explanation: An internal message could not be
sent, which probably means that one of the ISDN_XFER013 CA_TDM_Connect() failed
internal message queues is not functioning
correctly. Explanation: A request to connect two TDM
port sets failed.
custom server. User response: If the problem persists, take an
AIX system trace while re-creating the problem.
If the problem persists, take an AIX system trace Specify the -d command line parameter for the
while re-creating the problem. Specify the -d custom server. Then call IBM Support.
Then call IBM Support. Severity: Yellow (errorid = 20503)
Yellow (errorid = 20503) Destination: Log, System Monitor.

ISDN_XFER014 CA_TDM_Disconnect() failed
ISDN_XFER011 Internal message could not be Explanation: A request to disconnect two TDM
received port sets failed.
Explanation: An internal message could not be User response: If the problem persists, take an
received, which probably means that one of the AIX system trace while re-creating the problem.

Specify the -d command line parameter for the that the outbound party of the a transfer had
custom server. Then call IBM Support. terminated. This error may indicate the presence
of a race condition.
Severity: Yellow (errorid = 20503)
User response: If the problem persists, take an
Specify the -d command line parameter for the
ISDN_XFER015 Invalid event occurred custom server. Then call IBM Support.
Explanation: An invalid event occurred for the Severity: Yellow (errorid = 20503)
current state of the transfer operation. This might
happen if the default state tables have been
customized and the sequence of the operations
needed to complete a transfer is now incorrect. ISDN_XFER018 SetUserData is not valid at
this time
User response: Check that the state tables
implementing the Transfer are doing this Explanation: A SetUserData request has been
correctly. Use the default state tables as a guide made to the ISDN_Call_Transfer custom server at
to correct operation. an invalid time (out of sequence). The
SetUserData function should be called by the
incoming application before the TransferCall
action is performed.
Then call IBM Support. Be prepared to give User response: Check that the state tables
details of any customizations that have been implementing the transfer are doing this
made to the default trombone state tables. correctly. Use the default state tables as a guide
to correct operation.
IISDN_XFER016 Failed to retrieve channel Then call IBM Support. Be prepared to give
information details of any customizations that have been
made to the default transfer state tables.
Explanation: A call to CA_Get_Channel_Info()
failed. This probably means that the outbound Severity: White (errorid = 20501)
party of the transfer has terminated prematurely
and the ISDN_Call_Transfer custom server has
not yet received a notification.
ISDN_XFER019 GetUserStatus is not valid at
this time
Specify the -d command line parameter for the Explanation: A GetUserStatus request has been
custom server. Then call IBM Support. made to the ISDN_Call_Transfer custom server at
an invalid time (out of sequence). The
GetUserStatus function should be called by the
Destination: Log, System Monitor. incoming application after the TransferCall action
has returned but before the TerminateCall or
ReconnectCall actions are performed.
ISDN_XFER017 Failed to send channel event
Explanation: A call to implementing the transfer are doing this
CA_Report_Channel_Event() failed when the correctly. Use the default state tables as a guide
ISDN_Call_Transfer custom server tried to report to correct operation.


ISDN_XFER022 CA_Execute_State_Table()
failed
Then call IBM Support. Be prepared to give Explanation: The state table for the outbound
details of any customizations that have been part of the transfer operation could not be
made to the default transfer state tables. executed. This may be caused if the state table
does not exist or is not validated.
User response: Ensure that the name and entry
point to the outbound state tables are valid for
your system, and that the state tables have been
ISDN_XFER020 MakeCallStatus is not valid at validated. If the names and entry points are not
this time specified in the command line options to the
custom server, they default to ISDN_Imm_Xfer,
Explanation: A MakeCallStatus request has ISDN_SupA_Xfer, and begin). Also, if you have
been made to the ISDN_Call_Transfer custom customized the outbound state tables, ensure that
server at an invalid time (out of sequence). The you have not altered the input parameters (for
MakeCallStatus function should be called by the the correct input parameters, see the supplied
outgoing application after the MakeCall action state tables).
has returned.
implementing the transfer are doing this Destination: Log, System Monitor.
correctly. Use the default state tables as a guide
to correct operation.
ISDN_XFER023 CA_Close_CHP_Link() failed
Explanation: A call to CA_Close_CHP_Link()
failed. This means that the link to the CHP for
the outbound part of a transfer operation cannot
Then call IBM Support. Be prepared to give
be closed. This may be caused if the outbound
details of any customizations that have been
state table exits before the ISDN_Call_Transfer
made to the default transfer state tables.
custom server has a chance to release the link.
Severity: White (errorid = 20501) This should not happen if the outbound state
table is working correctly.
ISDN_XFER021 CA_Open_CHP_Link() failed Specify the -d command line parameter for the
Explanation: A call to CA_Open_CHP_Link() custom server. Then call IBM Support.
failed. This means that the outbound part of a Severity: Yellow (errorid = 20503)
transfer operation cannot be performed. This
may be caused if there are no spare CHPs Destination: Log, System Monitor.
available.
User response: Ensure that there are enough ISDN_XFER024 Could not remove child
CHPs available for your system. If your system process on custom server
does a lot of processing after a call is completed, shutdown
you may require more spare CHPs to be defined.
Explanation: Could not destroy a child process
Severity: Yellow (errorid = 20503) during custom server shutdown. This does not
cause runtime problems, but may leave
Destination: Log, System Monitor. unnecessary processes running after WebSphere
Voice Response has shut down.

User response: If the problem persists and is User response: Restart WebSphere Voice
causing operational problems, take an AIX Response. If this does not clear the problem,
system trace while re-creating the problem.
take an AIX system trace while re-creating the
custom server. Then call IBM Support.
for the custom server. Then call IBM Support.
ISDN_XFER025 Could not remove message

ISDN_XFER028 Could not read what type of
queue on custom server shutdown
adapter hardware is present
Explanation: Could not remove an internal
Explanation: The custom server was unable to
message queue during custom server shutdown.
determine what type of telephony hardware is
This does not cause runtime problems, but may
connected to WebSphere Voice Response. This
leave unnecessary message queues after
will generate fatal error ISDN_XFER001
WebSphere Voice Response has shut down.
User response: If the problem persists and is
Response. If this does not clear the problem,
causing operational problems, take an AIX
system trace while re-creating the problem. take an AIX system trace while re-creating the
Specify the -d command line parameter for the problem. Specify the -d command line parameter
custom server. Then call IBM Support. for the custom server. Then call IBM Support.
Severity: White (errorid = 20501) Severity: White (errorid = 20501)
Destination: Log, System Monitor. Destination: Log, System Monitor.
ISDN_XFER026 Could not open a file ISDN_XFER029 IDSN L4 requested a Make

descriptor to the Signaling Library Call which is invalid at this time
Explanation: The custom server was unable to Explanation: A MakeCall message from ISDN
connect to the signaling library. This will Layer 4 was received at an invalid time (out of
generate fatal error ISDN_XFER001. sequence). This probably indicates an internal
problem.
Response. If this does not clear the problem, User response: Restart WebSphere Voice
Response. If the problem persists, take an AIX
take an AIX system trace while re-creating the
for the custom server. Then call IBM Support.
White (errorid = 20501)
ISDN_XFER027 Could not register this custom

ISDN_XFER030 IDSN L4 requested a TDM
server with the Signaling Library
Connect which is invalid at this
Explanation: The custom server was unable to time
register itself with the signaling library. This will
Explanation: A TDM Connect message from
generate fatal error ISDN_XFER001.
ISDN Layer 4 was received at an invalid time

(out of sequence). This probably indicates an

internal problem.
ISDN_XFER031 IDSN L4 requested a TDM

Disconnect which is invalid at
this time
Explanation: A TDM Disconnect message from
internal problem.
ISDN_XFER032 IDSN L4 requested a

Disconnect Call, which is invalid
at this time
Explanation: A Disconnect Call message from
internal problem.

JB002 • JB010
Juke_Box custom server

This section lists errors that can be issued by the Juke_Box custom server.
Errors are enrolled as standard custom server errors in the range 20500 to
20504.
Response, restarted the Juke_Box custom server, restarted WebSphere Voice
the conditions that cause the problem.
JB002 Too many parameters. All JB006 Exiting because of an error. Exit
parameters after 'string' ignored. code='number'.
Explanation: More than one parameter was Explanation: The Juke_Box custom server has
specified in the custom server properties found an error it cannot recover from. To
window, and was passed to the Juke_Box custom determine the cause of the error, look up the exit
server main() routine. The Juke_Box custom code in the file jb_error.h in the
server will accept only one parameter. $DB/current_dir/ca/juke_box_dir directory.
User response: Change the custom server User response: Correct the cause of the error
properties so that the main arguments panel has and restart the Juke_Box custom server.
only one filename. This filename must either
have a fully-qualified path name, or a path name
relative to the $DB/current_dir/ca directory. If Destination: Log, System Monitor
you change the properties, remember to save
them.
JB008 Cannot find mandatory
Severity: White (error_id = 20501) environment variable $DB
Destination: Log, System Monitor Explanation: The Juke_Box custom server uses
the DB environment variable. It must hold the
fully-qualified path name of the directory which
JB004 Could not use file 'string' to
is used to access the configuration file, the music
configure
player program files, message files, and so on.
Explanation: The filename passed to the
User response: Check that the shell or program
Juke_Box custom server main() routine could not
calling the Juke_Box custom server sets the DB
be opened as a configuration file.
environment variable, then restart the Juke_Box
User response: Check that the userid running custom server.
WebSphere Voice Response has access to the file,
that the file exists, and that it has either a
fully-qualified path name, or a path name Destination: Log, System Monitor
relative to the $DB/current_dir/ca directory. The
filename is specified in the properties window
from the Juke_Box custom server window. If you JB010 Cannot access directory 'string'.
change the properties, remember to save them. $DB environment variable set
incorrectly. errno='number'.
Explanation: The Juke_Box custom server could

JB012 • JB022
not access the directory specified in the $DB Explanation: The Juke_Box custom server
environment variable. generates processes to run the music players. It
communicates with them using a message queue.
User response: Check that the directory exists,
This error can indicate that an earlier Juke_Box
that the Juke_Box custom server has access to it,
custom server has not cleaned up correctly, or is
and that the environment variable is correct, then
still active. The Juke_Box custom server
restart the Juke_Box custom server.
continues, and if it finds an existing message
Severity: Yellow (error_id = 20502) queue, generates message JB022.
Destination: Log, System Monitor User response: Remove the file

/tmp/juke_box_message_queue_<userid> and
make sure that the userid that started the
JB012 CA_Set_Options() failed. Cannot Juke_Box custom server has write access to the
start. rc='number', /tmp directory. Restart the Juke_Box custom
CA_errno='number'. server.
Explanation: The CA_Set_Options() custom Severity: White (error_id = 20501)
server library call is used by the Juke_Box
custom server to prepare for the CA_Init() call. Destination: Log, System Monitor
Parameters are set to indicate that this custom
server has multiple processes. Possible causes are
JB020 Cannot get existing message
documented in the WebSphere Voice Response for
queue
AIX: Application Development using State Tables
book. Explanation: This error can indicate that an
earlier Juke_Box custom server has not cleaned
User response: Check CA_errno and see the
up correctly, or is still active. The Juke_Box
CA_Set_Options() custom server call in the
custom server cannot create a message queue or
WebSphere Voice Response for AIX: Application
use an existing message queue.
Development using State Tables book for more
information. User response: Remove the file
/tmp/juke_box_message_queue_<userid> and
make sure that the userid that started the
Destination: Log, System Monitor Juke_Box custom server has write access to the
/tmp directory. Restart the Juke_Box custom
server.
JB014 CA_Init() failed. Cannot start.
rc='number', CA_errno='number'. Severity: Yellow (error_id = 20502)
Explanation: The CA_Init() custom server call Destination: Log, System Monitor
failed. The Juke_Box custom server cannot start.
User response: See the CA_Init() custom server JB022 Got existing message queue.
call in the WebSphere Voice Response for AIX: Using it now.
Application Development using State Tables
Explanation: The Juke_Box custom server uses
reference manual for more information. Restart
the existing message queue.
the Juke_Box custom server.
User response: None; this message is for
information only. To prevent reoccurrence of this
Destination: Log, System Monitor message, next time the Juke_Box custom server is
stopped, remove the file /tmp/
juke_box_message_queue_<userid> and make
JB018 Cannot create new message sure that the userid that started the Juke_Box
queue. Trying to use existing custom server has write access to the /tmp
message queue.

JB024 • JB036
directory. Restart the Juke_Box custom server.

JB030 Cannot set reader pipe to
Severity: White (error_id = 20501) non-blocking. rc='number'
errno='number'
Explanation: AIX system call fcntl() failed. The
Juke Box cannot start.
JB024 sigaction() to intercept SIGINT
signals failed. rc='number' User response: Check rc and errno for the fcntl()
errno='number'. call in the AIX documentation.
Explanation: The AIX system call sigaction() Severity: Yellow (error_id = 20502)
failed. The Juke_Box custom server was trying to
register a handler for the SIGINT event.
User response: Check rc and errno for the
JB032 Cannot set writer pipe to
sigaction() call in the AIX documentation.
non-blocking. rc='number'
Severity: Yellow (error_id = 20502) errno='number'
Destination: Log, System Monitor Explanation: AIX system call fcntl() failed. The
JukeBox custom server cannot start.
JB026 sigaction() to intercept SIGCHLD User response: Check rc and errno for the fcntl()
signals failed. rc='number' call in the AIX documentation.
errno='number'.
Explanation: The AIX system call sigaction()
failed. The Juke_Box custom server was trying to
register a handler for the SIGCHLD event.
JB034 Cannot destroy message queue.
rc='number' errno='number'
sigaction() call in the AIX documentation.
Explanation: AIX system call msgctl() failed.
msgctl() call in the AIX documentation.
JB028 Unable to create messaging pipe.
rc='number' errno='number' Destination: Log, System Monitor
Explanation: The Juke_Box custom server’s AIX
system call pipe() failed. The Juke_Box custom JB036 CA_Poll() failed. rc='number'
server uses the pipe to keep track of process CA_errno='number'
terminations, and to terminate itself when it gets errno='number'
a request from the WebSphere Voice Response
Explanation: CA_Poll() custom server call
custom server manager.
failed.
User response: Check rc, errno, and CA_errno
pipe() call in the AIX documentation. Correct the
for the CA_Poll() custom server call in WebSphere
problem, then restart the Juke_Box custom server.
Voice Response for AIX: Application Development
Severity: Yellow (error_id = 20502) using State Tables book.
Destination: Log, System Monitor Severity: Yellow (error_id = 20502)

JB038 • JB048
JB038 CA_Poll() timed out when we JB044 CA_Get_DT_Parameters() failed.

wanted to wait forever rc='number' CA_errno='number'.
Message from state table ignored.
Explanation: The CA_Poll() routine completed,
Check that SendData() is used
indicating a timeout event. The Juke_Box custom
after call is set up.
server specified that the CA_Poll() routine
should not timeout. There may be a problem Explanation: SendData to the Juke_Box custom
with the WebSphere Voice Response custom server is only allowed once the call is connected.
server interface. Using the Juke_Box custom server before the call
has been connected, or after it has been hung-up,
generates this error.
User response: Change that the state table
Destination: Log, System Monitor obeys this rule. Check that the call is connected
before the SendData() action to start or stop a
tune playing. You can check this using the State
JB040 CA_Poll() reports unexpected Table Debugger.
number of file descriptors having
input Severity: White (error_id = 20501)
Explanation: The CA_Poll() routine completed, Destination: Log, System Monitor

indicating that more than one file descriptor has
an event to be processed. The only file descriptor
JB046 Cannot determine which state
the Juke_Box custom server expects events on is
table sent a message. Message
the pipe connecting the signal handler routines
ignored.
to the main get...process message loop.
Explanation: To start or stop a tune playing, the
User response: There may be an error with the
Juke_Box custom server must have channel and
custom server interface. If the problem persists,
pack information. The CA_Get_Channel_Info()
call IBM Support.
custom server call, which the Juke_Box custom
Severity: White (error_id = 20501) server uses to get this information, failed.
Destination: Log, System Monitor User response: Check that the call is connected
before the SendData() action to start or stop a
tune playing. You can check this using the State
JB042 Unrecognized message 'number' Table Debugger.
from WebSphere Voice Response.
Ignored. Severity: White (error_id = 20501)
Explanation: The Juke_Box custom server has Destination: Log, System Monitor
received a message that it does not recognize
from WebSphere Voice Response. The message is
JB048 Failed to add title to catalog
ignored.
User response: None. This message is for
not add the music title to the dynamic catalog in
information only. If the problem persists, there
memory. Causes of this error can be:
may be a problem with the Juke_Box custom
server. Call IBM Support. v Insufficient memory
v Trying to add a music title that is already in
the catalog, but has different parameters
User response: Check that the music catalog file
does not already contain the music title, and if it
does, that the parameters passed to the Juke_Box

JB050 • JB060
custom server for dynamic configuation match Juke_Box custom server or the music player.
the catalog entry. If the same music title is
User response: Check that the build and install
configured more than once, check that the
levels of the Juke_Box custom server and the
parameters are the same for each occurrence.
music players match by re-compiling them, by
Severity: White (error_id = 20501) clicking build and then install on the Custom
Server window.
JB050 Unexpected message size received Destination: Log, System Monitor
from a player. Size
received='number', size
JB056 There was no data on the pipe to
expected='number'.
read. CA_Poll() said there was.
Explanation: The Juke_Box custom server and
Explanation: CA_Poll() indicated an event on
player programs communicate with each other
the pipe between the signal handler code and the
using a data structure of a set size. If these sizes
get...process message loop of the main process.
do not match, there may be a difference in the
The Juke_Box custom server tried to read a
levels of the Juke_Box custom server and player
message from this queue, but found no data
programs.
there. This can indicate an error in the Juke_Box
User response: Recompile the Juke_Box custom custom server, or in the custom server CA_Poll()
server modules and the music player program call.
modules by clicking build and then install on the
User response: If this problem persists, contact
Custom Server window.
IBM Support.
JB052 Terminating because of request

JB058 Failed to read() from message
from test rig
pipe. rc='number', errno='number'
Explanation: The pl_test test rig was used to
Explanation: The AIX system call fread() failed.
develop the Juke_Box custom server. It sent a
TERMINATE to the Juke_Box custom server to User response: Check rc and errno for the
force it to clean up and exit. fread() system call in the AIX documentation.
User response: Restart the Juke_Box custom Severity: Yellow (error_id = 20502)
server.
Destination: Log, System Monitor JB060 Music player process 'number'
terminated. Exit code='number'
JB054 Initialized message received from Explanation: The music player terminated using
an inactive player process the exit() system call.
'number'
User response: For the meaning of the exit
Explanation: The Juke_Box custom server code, see the documentation or code for the
received a message from a player to indicate that music player.
it is initialized. The Juke_Box custom server was
not expecting such a message from this player Severity: White (error_id = 20501)
process. This may indicate an error in the

JB062 • JB072
Destination: Log, System Monitor User response: If this problem persists, call IBM
Support.
JB062 State table tried to stop music title Severity: Yellow (error_id = 20502)
'string', which is not playing
Explanation: The state table tried to stop the
music title, but that tune is not currently playing.
JB068 Cannot allocate memory for new
Either the music player is not working properly
music title 'string'
or has terminated abnormally, or your state table
has issued a Juke_box_stop_music when the tune Explanation: The Juke_Box custom server could
did not start playing. not malloc() enough memory. The new music
title was not added to the catalog.
User response: Check the error log for
information about the music player program, User response: If this problem persists, call IBM
and check that your state table correctly handles Support.
return codes from the Juke_Box custom server,
only issuing juke_box_stop_music when a tune is Severity: White (error_id = 20501)
playing. Destination: Log, System Monitor
Destination: Log, System Monitor JB070 Attempt to redefine music title
'string' rejected
JB064 State table tried to stop music title Explanation: The music title is already defined,
'string', which it never started but the parameters do not match. Either a state
table is trying to add a music title to the music
Explanation: The state table tried to stop the catalog dynamically, or the Juke_Box custom
music title, but that tune is not currently playing. server is starting and is processing the
Either the music player is not working properly configuration file.
or has terminated abnormally, or your state table
has issued a Juke_box_stop_music when the tune User response: If a state table caused this error,
did not start playing. use another music title, or delete the dynamic
entries in the music catalog by stopping and
User response: Check that the music tune restarting the Juke_Box custom server. If the
started correctly, and that the state table checks error is caused by the configuration file, edit it,
the return status of the start request. The state then stop and start the Juke_Box custom server
table should not try to stop any tune playing that to make changes the active.
it didn’t start. Check that the parameters passed
on the stop request are correct, and exactly Severity: White (error_id = 20501)
match those passed on the start request. Destination: Log, System Monitor
Destination: Log, System Monitor JB072 Configuration: cannot open
configuration file 'string'
JB066 Failed to send CHP a message Explanation: The Juke_Box custom server is
starting, but cannot access the configuration file
Explanation: The Juke_Box custom server tried specified in the ’parameters to main’ section of
to send a message to a state table, passing the the custom server properties window.
return code from a request to the state table. It
failed to do this. This indicates a possible error in User response: Check that the file exists, and
the Juke_Box custom server. that the path name is correct. Check that the
Juke_Box custom server has the correct

JB074 • JB084
permission to read the file. User response: If this problem persists, call IBM
Support.
JB074 Configuration: music title 'string'
has no player or parameter JB080 Configuration: trailing bracket not
strings. Ignored. found before end of line
Explanation: The Juke_Box custom server is Explanation: The configuration file used by the
starting and is parsing the configuration file. A Juke_Box custom server is incorrect; each entry
music title has been defined, but the fields must contain three fields. Each field must be
specifying a music player and its parameters are enclosed by double quote characters.
missing. The error is ignored and the Juke_Box
User response: Check that the fields in the
custom server continues. Other entries in the
configuration file have matching double quotes,
configuration file may be correct, or your state
save the file, then restart the Juke_Box custom
table can add music titles dynamically.
server.
User response: Correct the music title entry in
the configuration file, then restart the Juke_Box
custom server. Destination: Log, System Monitor
JB082 State table requested music title
'string', which is not configured
Explanation: The state table, using SendData(),
JB076 Configuration: music title 'string'
has asked the Juke_Box custom server to make a
has no player parameters. Ignored.
piece of music available. The music title is not
Explanation: The Juke_Box custom server is known to the Juke_Box custom server.
starting and is parsing the configuration file. A
User response: Check that the music title
music title and its music player have been
exactly matches the one known to the Juke_Box
defined, but the music player parameters are
custom server, either in the configuration file or
missing. The music title is ignored and the
added dynamically. If the music titles match,
Juke_Box custom server continues. Other entries
check return values from the SendData() action
in the configuration file may be correct, or your
using ReceiveData().
state table can add music titles dynamically.
User response: Correct the music title entry in
the configuration file, then restart the Juke_Box Destination: Log, System Monitor
custom server.
Severity: White (error_id = 20501) JB084 Cannot start up music player
'string'
not start up the specified player process.
JB078 Configuration: cannot add music
title 'string' to the music catalog User response: Check that the program name is
specified relative to the $DB/current_dir/CA
directory, that the program exists and has
not dynamically add the specified music title to
execute permission for the userid that started the
the music catalog.
Juke_Box custom server, and that it is linked

JB086 • JBS006
using Ld (in the same way that the pl_seg and

JB092 load() system call to load music
pl_elem music players are).
player 'string' failed. rc='number'
Check that build and install versions of the errno='number'
Juke_Box custom server, and the music players
Explanation: The AIX system call load() failed.
match.
The Juke_Box custom server uses this system call
Severity: White (error_id = 20501) to load the music player into its forked program
image.
User response: Check errno and rc for load() in
the AIX documentation.
JB086 msgsnd() failed to send
TERMINATE to music player. Severity: White (error_id = 20501)
Using kill() to terminate process.
rc='number' errno='number'
Explanation: The Juke_Box custom server sent a
JBS002 'string' flag: should be followed
TERMINATE message to a music player. The
by a number
msgsnd() AIX system call failed.
Explanation: This flag must be followed by a
User response: Check rc and errno for msgsnd()
number.
in the AIX documentation.
User response: Correct the music player
parameter string, either in the configuration file,
Destination: Log, System Monitor or in the state table when the music title is
dynamically added to the music catalog. Restart
the Juke_Box custom server.
JB088 Cannot allocate memory for a
player structure Severity: White (error_id = 20501)
Explanation: The Juke_Box custom server tried Destination: Log, System Monitor
to allocate memory in which to store details
about a new music player process. The malloc()
JBS004 'string' flag: 'string' is not a
AIX system call failed.
number. Ignored.
Support.
number. This flag has been ignored.
User response: Correct the value in the music
Destination: Log, System Monitor player parameter string, either in the
configuration file, or in the state table when the
music title is dynamically added to the music
JB090 fork() system call failed. catalog. Restart the Juke_Box custom server.
errno='number'
Explanation: The AIX system call fork() failed.
The Juke_Box custom server uses this system call Destination: Log, System Monitor
to start a process.
User response: Check errno for fork() in the AIX JBS006 flag 'string': value 'number' is not
documentation. a multiple of 'number'. Rounded
to 'number'
Explanation: The value of this flag must be an
Destination: Log, System Monitor exact multiple of the specified number. The

JBS008 • JBS018
music player adjusts the value by rounding it Severity: White (error_id = 20501)
down, and uses this value.
player parameter string either in the
JBS014 CA_Open_Music_Channel()
failed. rc='number'
CA_errno='number'
catalog. Restart the Juke_Box custom server.
errno='number'
Explanation: The music player used the
Destination: Log, System Monitor WebSphere Voice Response custom server
interface call CA_Open_Music_Channel() to open
a music channel. CA_Open_Music_Channel()
JBS008 flag 'string': value 'number'
failed.
invalid. Must be in range
'number' to 'number' inclusive. User response: For more information, check
CA_errno in the WebSphere Voice Response for AIX:
Custom Servers book.
number in the allowed range.
player parameter string, either in the Destination: Log, System Monitor
JBS016 No flag letters found after '-'
Explanation: The music player found a dash
character in the parameter string with no flag or
Destination: Log, System Monitor numeric characters following.
JBS010 CA_Get_Segment_Info() failed. player parameter string, either in the
Segment 'number' Directory configuration file, or in the state table when the
'string' Language 'number' music title is dynamically added to the music
rc='number' CA_errno='number' catalog. Restart the Juke_Box custom server.
Explanation: The WebSphere Voice Response Severity: White (error_id = 20501)
custom server call CA_Get_Segment_Info() failed.
User response: For more information, check
CA_errno in WebSphere Voice Response for AIX:
JBS018 Parsing parameters: -d flag:
Application Development using State Tables.
directory string expected. Ignored.
Explanation: This flag must be followed by the
Destination: Log, System Monitor directory name.
JBS012 Cannot allocate 'number' bytes of player parameter string, either in the
voice-buffer configuration file, or in the state table when the
Explanation: The music player used the AIX
system call malloc() to allocate a large buffer of
memory. The call failed. Severity: White (error_id = 20501)
User response: See the AIX documentation. Destination: Log, System Monitor

JBS020 • JBS030

JBS020 Parsing parameters: unrecognized
flag 'string'. Ignored
JBS026 Mandatory parameter -l
Explanation: This flag is not recognized by the
'language_code' missing
music player.
Explanation: The music player needs to know
the language code so that it can locate the
player parameter string, either in the
segment to be played to the music channel. The
music player expected the -l flag in the input
parameters, but it was missing. The music player
cannot continue until this error is corrected.
Destination: Log, System Monitor player parameter string, either in the
JBS022 Mandatory parameter -s
'segment_number' missing
Explanation: This music player needs to know
which segment to extract from the WebSphere Destination: Log, System Monitor
Voice Response segment database. This segment
is played to the music channel. The music player
JBS028 CA_Poll() failed. rc='number',
expected the -s flag in the input parameters, but
CA_errno='number',
it was missing. The music player cannot continue
errno='number'
until this error is corrected.
Explanation: The custom server API call
CA_Poll() failed.
configuration file, or in the state table when the User response: For more information, check
music title is dynamically added to the music CA_errno in the WebSphere Voice Response for AIX:
catalog. Restart the Juke_Box custom server. Custom Servers book.
JBS024 Mandatory parameter -d JBS030 CA_Poll() timed out when we

'directory_name' missing wanted to wait forever
Explanation: The music player needs to know Explanation: The music player asked that the
the name of the voice directory containing the call should never timeout, but CA_Poll()
segment. The music player expected the -d flag reported a timeout event. This can indicate an
in the input parameters, but it was missing. The error in the music player or the WebSphere Voice
music player cannot continue until this error is Response custom server interface.
corrected.
User response: Correct the value in the music Support.
configuration file, or in the state table when the Severity: White (error_id = 20501)
music title is dynamically added to the music Destination: Log, System Monitor

JBS032 • JBS044
message from the queue it uses to communicate

JBS032 CA_Poll() reports wrong number
with the Juke_Box custom server. The length of
of message queues causing events
the message on the queue was incorrect. This can
Explanation: CA_Poll() reports that more mean that the Juke_Box custom server and the
message queues have events on them than the music player are at different levels.
music player expected. This can indicate an error
User response: Recompile the music player and
in the music player or the WebSphere Voice
the Juke_Box custom server, then restart the
Response custom server interface.
Juke_Box custom server. If the problem persists,
User response: If this problem persists, call IBM call IBM Support.
Support.
JBS040 Message type 'number' is
JBS034 CA_Poll reports events on music unknown. Ignored.
channel other than POLLOUT
Explanation: The music player received a
rtnevents='number'
message which it did not recognize from the
Explanation: The music player used the Juke_Box custom server. The message is ignored
CA_Poll() routine. The music channel being and the music player continues.
polled returned with an event other than the
User response: Check that the versions of the
expected POLLOUT event. The music player
music player and the Juke_Box custom server are
continues.
compatible.
Support.
JBS042 CA_Play_Voice_Elements() failed.
rc='number' CA_errno='number'
JBS036 msgrcv() failed. rc='number' errno='number'
errno='number'
Explanation: The music player tried to get a custom server call CA_Play_Voice_Elements()
message from the queue that links it to the failed.
Juke_Box custom server. The AIX system call
msgrcv() failed.
User response: Check rc and errno for msgrcv() Application Development using State Tables
in the AIX documentation. reference manual.
JBS038 Unexpected message size received JBS044 Ran out of voice data to write to
from Juke_Box custom server. Size music channel
received='number'
Explanation: The music player didn’t have
Size expected='number'
enough data in its buffer ready to pass to the
Explanation: The music player tried to get a music channel. If this persists, it causes an

JBS046 • JBE058
underrun on the music channel, and the caller

JBE052 Unable to open source file 'string'.
will hear the music breaking up.
errno='number'
Destination: Log, System Monitor system call fopen() to get read access to the
music data source file. The system call failed.
JBS046 CA_Get_Segment() failed. User response: Check rc and errno for fopen() in
CA_errno='number' the AIX documentation.
errno='number'.
custom server API function CA_Get_Segment()
failed.
JBE054 Cannot query size of source file
'number' using stat()
Custom Servers book. Explanation: The music player used the AIX
system call stat() to find out how big the music
data source file is. The system call failed.
User response: Check rc and errno for stat() in
the AIX documentation.
JBS048 CA_Get_Segment() failed to read
correct number of elements.
CA_errno='number' Destination: Log, System Monitor
errno='number'
Explanation: The music player used the JBE056 Source file contains fractional
WebSphere Voice Response custom server API elements. Some data at the end of
function CA_Get_Segment(). It did not return the the file will not be played.
expected number of elements. This can indicate
Explanation: Source files used by the music
that the size of the segment is not the same as
player must contain exact multiples of the
reported earlier by the CA_Get_Segment_Info()
element structure. Partial elements exist at the
call.
end of the music data source file. When it is
Severity: White (error_id = 20501) being played to the music channel, the voice data
at the end of the file will not be played.
User response: Check that the data file was
created correctly, that it is the correct format, and
JBS050 More elements in queue 'number'
that it is compatible with WebSphere Voice
than there should be 'number'
Response.
Explanation: The music player has too many
elements in its internal voice buffer. Variables in
the music player which track the amount of data Destination: Log, System Monitor
buffered have been corrupted.
User response: Call IBM Support. JBE058 Parsing parameters: -f flag:
filename expected. Ignored.
Explanation: The filename associated with the -f
flag is missing.

JBE060 • JBE064
User response: Correct the value in the music Severity: White (error_id = 20501)
JBE060 Mandatory parameter -f 'filename'

missing
Explanation: The music player needs the name
of the file containing the music data. The -f
parameter must be followed by a filename, and
the file is assumed to be in the
$DB/current_dir/ca directory unless a a
fully-qualified path name is given.
User response: Correct the file name and try
again.
JBE062 CA_Poll() reports file descriptor

event, when we are not polling
any file descriptors
Explanation: The music player used the
WebSphere Voice Response custom server call
CA_Poll(). It reports that a file descriptor has an
event to be processed, but this music player was
not polling on a file descriptor. This indicates a
problem in the music player or in WebSphere
Voice Response.
Support.
JBE064 fread() failed. errno='number'

fread() system call.
User response: Check errno for fread() in the
AIX documentation.

TROMBONE000 • TROMBONE002
IBM_Trombone_Custom_Server
Red errors are issued for all fatal problems and yellow (warnings) and white
(information) errors for any problems that may cause future failures or for
information purposes.
The errors are issued as standard custom server errors in the range 20500 to
20504. The IBM_Trombone_Custom_Server error title and ID are shown in
parameters 1 and 2 of the standard custom server errors. The error IDs have
the form TROMBONEnnn.The remaining parameters contain information
specific to the particular error.
problem occurs may also be required. Before taking the trace, set the -d option
in the custom server. For more information on the command line options see
the second on configuring the IBM_Trombone_Custom_Server in the
WebSphere Voice Response for AIX: Designing and Managing State Table
Applications.
in the white notification errors enrolled
TROMBONE000 Unknown error
immediately before this error.
Explanation: The custom server tried to enroll
Severity: Red (error id = 20504)
an error that was out of range. The error id it
tried to enroll is given as one of the parameters. Destination: Log, System Monitor.
User response: Re-start
IBM_Trombone_Custom_Server. TROMBONE002 Failed to fork() required
number of custom servers.
If the problem persists, re-create the problem and
Exiting...
take an AIX system trace (specify the -d
command-line parameter for the custom server), Explanation: The custom server could not fork()
before calling IBM Support. the required number of child helper processes.
This probably means that AIX is not configured
to allow sufficient processes per user.
User response: Check that the command-line
parameter -pn has not been set up to request an
TROMBONE001 Failed to initialize the custom unreasonably large number of child helper
server. Exiting... processes.
Explanation: The custom server could not be Check that AIX is configured to allow sufficient
initialized because there are errors either in the processes per user.
command line parameters or in setting up the
internal memory and communication
requirements. This error is issued as a result of Destination: Log, System Monitor.
one or more white notification errors.
User response: Correct the problem as indicated

Explanation: One of the command-line

TROMBONE003 Failed to retrieve WebSphere
arguments used to start the custom server was
Voice Response information using
invalid. The invalid argument is printed as one
CA_Get_DT_Info()
of the parameters in the error details.This
Explanation: The custom server was unable to generates fatal error TROMBONE001.
retrieve system information about WebSphere
User response: Correct the command-line
Voice Response. This is unlikely to happen, but if
argument. You can see the command-line
it does, it probably means that something has
arguments by selecting “Properties” from the
gone very wrong with WebSphere Voice
“File” window for this custom server. Permitted
Response. This generates fatal error
command-line arguments for this custom server
TROMBONE001.
are: -d, -s, -a, -pn, -en, -in.
User response: Re-start WebSphere Voice
Severity: White (error id = 20501)
Response. If the problem persists, re-create the
problem and take an AIX system trace (specify Destination: Log, System Monitor.
the -d command-line parameter for the custom
server), before calling IBM Support.
TROMBONE006 Failed to create message
Severity: White (error id = 20501) queue for internal
communications
Explanation: The custom server could not create
the internal message queues required for internal
TROMBONE004 Failed to malloc() memory
communications between the parent process and
Explanation: The custom server was unable to the child helper processes. This generates fatal
malloc() memory for its internal requirements. error TROMBONE001.
This is likely to occur if the system does not
User response: Re-create the problem and take
have sufficient main memory or paging space
an AIX system trace (specify the -d
available.
command-line parameter for the custom server),
If this problem is issued when the custom server before calling IBM Support..
is started, it generates fatal error
TROMBONE001.
If this problem is issued while the custom server
is running, the custom server calls related to the
OpenHostServerLink that provoked the error fail. TROMBONE007 Failed to fork() a child
process
User response: Shutdown some other tasks
running on the system to free up memory or Explanation: A child helper process could not
paging space. be created. This generates fatal error
TROMBONE002.
If the problem occurs at start-up, re-create the
problem and take an AIX system trace (specify User response: Check the AIX errno given in
the -d command-line parameter for the custom the other parameters for the failure reason. If this
server), before calling IBM Support. doesn’t help, re-create the problem and take an
AIX system trace (specify the -d command-line
parameter for the custom server), before calling
Destination: Log, System Monitor. IBM Support.
TROMBONE005 - Invalid command-line
argument

TROMBONE008 Polling for messages failed TROMBONE011 Internal message could not
be received
Explanation: A call to CA_Poll() failed.
received, which probably means that one of the
the other parameters for the failure reason. If this
doesn't help, re-create the problem and take an
correctly.
parameter for the custom server), before calling User response: Re-start
IBM Support. IBM_Trombone_Custom_Server.
Severity: Red (error id = 20504) If the problem persists, re-create the problem and
before calling IBM Support.
TROMBONE009 CA_Poll indicated a message
Severity: Yellow (error id = 20503)
waiting, but it couldn’t be
received Destination: Log, System Monitor.
Explanation: CA_Poll() indicated that there was
a message to process, but CA_Receive_DT_Msg() TROMBONE012 Internal message could not
failed. be recognized
User response: Check the CA_errno given in Explanation: A message on one of the internal
the other parameters for the failure reason. If this message queues could not be recognized as a
doesn’t help, re-create the problem and take an valid message.
IBM_Trombone_Custom_Server.
IBM Support.
Destination: Log, System Monitor. command-line parameter for the custom server),
TROMBONE010 Internal message could not Severity: Yellow (error id = 20503)
be sent
sent, which probably means that one of the
TROMBONE013 CA_TDM_Connect() failed
correctly. Explanation: A request to connect two TDM
PortSets failed.
IBM_Trombone_Custom_Server. User response: Re-create the problem and take
before calling IBM Support. Severity: Yellow (error id = 20503)
Severity: Yellow (error id = 20503) Destination: Log, System Monitor.
TROMBONE014 CA_TDM_Disconnect() failed

Explanation: A request to disconnect two TDM Explanation: An inconsistency was

PortSets failed. unexpectedly detected for the state information
related to a particular trombone operation.
an AIX system trace (specify the -d User response: Re-create the problem and take
command-line parameter for the custom server), an AIX system trace (specify the -d
before calling IBM Support. command-line parameter for the custom server),
TROMBONE015 NULL pointer detected for
trombone state information TROMBONE018 Failed to retrieve channel
information
Explanation: A NULL pointer was unexpectedly
detected for the state information related to a Explanation: A call to CA_Get_Channel_Info()
particular trombone operation. failed. This probably means that one of the
parties of the trombone has terminated
prematurely and IBM_Trombone_Custom_Server
has not received a notification yet.
before calling IBM Support. User response: Re-create the problem and take
Destination: Log, System Monitor. before calling IBM Support.
TROMBONE016 Invalid event occurred
Explanation: An invalid event occurred for the
current state of the trombone operation. This
TROMBONE019 Failed to send channel event
might happen if you have customized the default
state tables and the order of the operations Explanation: A call to
needed to complete a trombone is now incorrect. CA_Report_Channel_Event() failed when
IBM_Trombone_Custom_Server tried to report
that one of the partners in a trombone had
implementing the trombone are doing this
terminated. It’s possible that this error may
correctly (the default state tables should be used
indicate the presence of a race condition.
as a guide to correct operation).
before calling IBM Support. Also be prepared to
give details of any customization that has been Severity: Yellow (error id = 20503)
made to the default trombone state tables.
Destination: Log, System Monitor. TROMBONE020 TromboneDisconnectCall is
not valid at this time
TROMBONE017 Inconsistency with internal Explanation: A TromboneDisconnectCall request
pointers has been made to

IBM_Trombone_Custom_Server at an invalid time (out of sequence). This might happen if the

time (out of sequence). This might happen if the default state tables have been customized and
default state tables have been customized and the order of the operations needed to complete a
the order of the operations needed to complete a trombone is now incorrect.
trombone is now incorrect.
User response: Check that the state tables implementing the trombone are doing this
implementing the trombone are doing this correctly (the default state tables should be used
correctly (the default state tables should be used as a guide to correct operation).
If the problem persists, re-create the problem and take an AIX system trace (specify the -d
take an AIX system trace (specify the -d command-line parameter for the custom server),
command-line parameter for the custom server), before calling IBM Support. Also be prepared to
before calling IBM Support. Also be prepared to give details of any customization that has been
give details of any customization that has been made to the default trombone state tables.
made to the default trombone state tables.
TROMBONE023 CA_Open_CHP_Link() failed
TROMBONE021 TromboneMakeCall is not
Explanation: A call to CA_Open_CHP_Link()
valid at this time
failed. This means that the outbound part of a
Explanation: A TromboneMakeCall request has trombone operation cannot be performed. This
been made to IBM_Trombone_Custom_Server at may occur if there are no spare CHPs available.
an invalid time (out of sequence). This might
User response: Ensure that there are enough
CHPs available for your system. If your system
customized and the order of the operations
does lots of processing after a call is completed,
needed to complete a trombone is now incorrect.
you may need to define more spare CHPs.
correctly (the default state tables should be used Destination: Log, System Monitor.
If the problem persists, re-create the problem and TROMBONE024 CA_Execute_State_Table()
take an AIX system trace (specify the -d failed
before calling IBM Support. Also be prepared to Explanation: The state table for the outbound
give details of any customization that has been part of the trombone operation could not be
made to the default trombone state tables. executed. This may occur if the state table does
not exist or is not validated.
User response: Ensure that the name and entry
Destination: Log, System Monitor. point to the outbound state table are valid for
your system, and that the state table has been
validated. (If the name and entry point are not
TROMBONE022 TromboneMakeCallStatus is
specified, they default to IBMTromboneOut and
not valid at this time
begin.) Also ensure that, if you have customized
Explanation: A TromboneMakeCallStatus the outbound state table, you have not altered
request has been made to the input parameters (see the default
IBM_Trombone_Custom_Server at an invalid

IBMTromboneOut state table for the correct input WebSphere Voice Response has shutdown.
parameters).
Severity: Yellow (error id = 20503) causing operational problems, re-create the
problem and take an AIX system trace (specify
the -d command-line parameter for the custom
TROMBONE025 CA_Close_CHP_Link() failed
Explanation: A call to CA_Close_CHP_Link()
failed. This means that the link to the CHP for
the outbound part of a trombone operation
cannot be closed. This may occur if the outbound TROMBONE028 TromboneConnectCall is not
state table exits before valid at this time
IBM_Trombone_Custom_Server has a chance to
Explanation: A TromboneConnectCall request
release the link. This shouldn’t happen if the
has been made to the
outbound state table is working correctly.
IBM_Trombone_Custom_Server at an invalid
User response: Re-create the problem and take time (out of sequence). This might happen if the
an AIX system trace (specify the -d default state tables have been customized and
command-line parameter for the custom server), the order of the operations needed to complete a
before calling IBM Support. trombone is now incorrect.
Severity: Yellow (error id = 20503) User response: Check that the state tables
correctly (use the default state tables as a guide
to correct operation).
TROMBONE026 Could not remove child
If the problem persists, re-create it and take an
process on custom server
shutdown
Explanation: Could not destroy a child process IBM Support. Also be prepared to give details of
during custom server shutdown. This does not any customization that has been made to the
cause runtime problems, but may leave default trombone state tables.
unnecessary processes running after WebSphere
Voice Response has shutdown.
causing operational problems, re-create the
problem and take an AIX system trace (specify TROMBONE029 TromboneCall is not valid at
the -d command-line parameter for the custom this time
Explanation: A TromboneCall request has been
Severity: White (error id = 20501) made to the IBM_Trombone_Custom_Server at
an invalid time (out of sequence). This might
customized and the order of the operations
TROMBONE027 Could not remove message needed to complete a trombone is now incorrect.
queue on custom server shutdown
Explanation: Could not remove an internal implementing the trombone are doing this
message queue during custom server shutdown. correctly (use the default state tables as a guide
This does not cause runtime problems, but may to correct operation).
leave unnecessary message queues after

If the problem persists, re-create it and take an
IBM Support. Also be prepared to give details of
any customization that has been made to the
default trombone state tables.

1002956 • 1008006
MRCP messages
MRCP-related VRBE messages are written to $DTJ_HOME/dtj_logs/log.x.log
The errors are issued as standard VRBE errors in the range 1002956 to
1008061. The error IDs have the format 100nnnn. The remaining parameters
contain information specific to the particular error.
problem occurs may also be required.
1002956 Successfully re-established 1008004 Attempting to open new session

connection to host: hostname or IP with backup server,
address on port: number. InitSessionString=value.
Explanation: This error is logged when the Explanation: If a backup server has been
initial connection to a speech recognition or TTS configured, this error is logged after message
server cannot be made. 1008007 when the recognition grammars have
been compiled successfully, and an attempt has
User response: Check that the speech
been made to start the speech recognition
recognition or TTS session completes
process, but the recognition engine returns
successfully.
something problematic, such as a code indicating
no free sessions.
1008001 ERROR: Lost connection to TTS
User response: Check that the interrupted
server. InitSessionString=value.
speech recognition session has now restarted on
Explanation: This error is logged when the the backup server.
initial connection to a TTS server cannot be
made.
1008005 ERROR: Lost connection to TTS
User response: If a backup server has been server. InitSessionString=value.
configured, check that MRCP message 1008003
Explanation: This error is logged when the
has also been logged.
initial connection to a TTS server can be made,
but the TTS engine returns something
1008003 Attempting to open new session problematic, such as a code indicating no free
with backup server, sessions.
InitSessionString=value.
User response: If a backup server has been
Explanation: If a backup server has been configured, check that MRCP message 1008006
configured, this error is logged after message has also been logged.
10080001 when the initial connection to the TTS
server cannot be made.
1008006 Attempting to open new TTS
User response: Check that the interrupted TTS session with backup server,
session has now restarted on the backup server. InitSessionString=value.
Explanation: If a backup server has been
configured, this error is logged after message

1008008 • 1008061
10080005 when the initial connection to the TTS Explanation: If a backup server has been
server cannot be made. configured, this error is logged after message
1008061 when the initial connection to the speech
User response: Check that the interrupted TTS
recognition server can be made, but the speech
session has now restarted on the backup server.
recognition engine returns something
problematic, such as a code indicating no free
1008008 Attempting to open new session sessions.
with backup server,
Explanation: If a backup server has been the backup server.
1008002 when the recognition grammars have
1008061 ERROR: Lost connection to
been compiled successfully, and an attempt has
Speech Recognition server.
been made to start the speech recognition
process, but the recognition engine returns
something problematic, such as a code indicating Explanation: This error is logged when the
no free sessions. initial connection to a speech recognition server
can be made, but the speech recognition engine
returns something problematic, such as a code
indicating no free sessions.
the backup server.
1008048 Attempting to open new session
has also been issued.
with backup server,
Explanation: If a backup server has been
10080491 when the initial connection to the
speech recognition server cannot be made.
the backup server.
1008049 ERROR: Lost connection to

Speech Recognition server.
Explanation: This error is logged when the
initial connection to a speech recognition server
cannot be made.
has also been logged.
1008060 Attempting to open new session

with backup server,

VXML messages
The messages described in this section are related to the VoiceXML Browser.
For information about other messages related to the Java and VoiceXML
environment, see “Java and VoiceXML environment messages” on page 385.
Where messages are written
The system writes messages to Node1.out, for VoiceXML documents that run
automatically (documents that belong to the application group in the node
configuration). Messages for speech browsers and VoiceXML documents that
are started with the vxml command are displayed on the console when they
are generated. You can display additional debug messages on the console by
using the -debug option on the vxml command:
vxml -debug myapplication.vxml
Some VoiceXML browser messages are only written to the vxml.log file. For
details of this file, refer to the WebSphere Voice Response SDK VoiceXML
Programmer's Guide book.
Note: The VoiceXML Browser provides error messages in U.K. English,

French, German, and U.S. English.
Message codes
Some messages have a code prefix that indicates the message category:
Table 10. Message codes and meanings
Code Description
A Logged when the VoiceXML browser detects audio input, but the
speech recognition engine does not return a recognized phrase; this
may be due to breath or background noise. The message column
contains audio level messages.
C Logged when the computer plays a prompt. The message column
displays the prompt text.
E Logged when the VoiceXML browser throws an event. The message
column indicates the type of event.
F Logged when the VoiceXML browser fetches a resource such as a
grammar file, an audio file, or a script. The message column contains
the URI of the file, and indicates whether it was fetched from the
server or was in the cache.
H Logged when the user responds using voice input. The message
column displays the word or phrase that was recognized by the
speech recognition engine.

Table 10. Message codes and meanings (continued)
Code Description
K Provides information about cache activity. This information is
provided only in the vxml.log file; it is not written to the Java console.
S Indicates system information, including the version of the VoiceXML
browser and the system time. This information is provided only in the
vxml.log file; it is not written to the Java console.
T Simulated DTMF input received.
V Logged when the VoiceXML browser fetches a .vxml file. The message
column contains the URI of the file, and indicates whether it was
fetched from the server or was in the cache.
Note: When transferring control within a document (using a URI that
begins with #), the document is not reloaded; in this condition, the
message column contains the form id.
W Indicates a warning.
X Specifies the version of JVM. This information is provided only in the
vxml.log file; it is not written to the Java console.
? Logged when the speech recognition engine determines that the user
said something, but the confidence level is not high enough to justify
using the results. In response, the VoiceXML browser throws a
nomatch event. The message column contains the word or phrase that
was recognized.

Example
15:07:42.289 S: Starting V010412 at Fri Nov 09 15:07:42 GMT+00:00 2001
15:07:42.289 X: Java: Sun Microsystems Inc. 1.3.0
15:07:42.289 X: requested locale: en_GB
15:08:02.909 A: not listening
15:08:02.949 A: listening
15:08:04.882 S: initializing application
15:08:04.902 V: file:C:/Program Files/VoiceToolkit/Eclipse/workspace/myProject/Weather.vxml (fetch get)
15:08:05.182 F: file:C:/Program Files/VoiceToolkit/Eclipse/workspace/myProject/Goodbye.wav (prefetch get)
15:08:05.412 S: running
15:08:13.424 F: file:C:/Program Files/VoiceToolkit/Eclipse/workspace/myProject/en_GB/Weather.gram (cache)
15:08:13.604 V: #main_menu
15:08:13.604 C: (audio clip)
15:08:22.948 T: 2
15:08:22.958 H: 2
15:08:22.968 V: #tts
15:08:22.968 C: This is an example of text to speech. Text to speech, or T T S,
uses synthesized speech as an alternative to playing pre-recorded audio prompts.
15:08:23.118 V: #main_menu
15:08:23.128 C: (audio clip)
15:08:38.140 T: 3
15:08:39.151 H: 4
15:08:39.151 V: #weather_info
15:08:39.161 C: Welcome to the weather information service.
15:08:39.191 V: #rest_of_weather
15:08:39.231 C: Please say temperature, humidity or pollen count. Say exit if
you wish to go back to the main menu.
15:08:46.311 ?: temperature (still speaking)
15:08:47.443 A: Too quiet (0.1)
15:08:54.613 A: Audio level (0.7)
15:08:56.045 H: temperature
15:08:56.055 V: file:C:/Program Files/VoiceToolkit/Eclipse/workspace/myProject/en_GB/CompositePrompts.vxml
(fetch get)
15:08:56.105 C: Do you want to hear the temperature for England?
15:09:00.201 A: Audio level (0.3)
15:09:01.663 H: yes
15:09:01.673 V: #say_result
15:09:01.683 V: file:C:/Program Files/VoiceToolkit/Eclipse/workspace/myProject/en_GB/CompositePrompts.vxml
(cache)
15:09:01.693 C: The temperature report for England is Always cool.
15:09:01.693 V: #rest_of_weather
15:09:01.703 C: Please say temperature, humidity or pollen count. Say exit if
you wish to go back to the main menu.
15:09:05.449 A: Too loud (1.0)
15:09:19.489 H: exit
15:09:19.499 C: Thank you for using the weather information service.
15:09:19.499 V: #main_menu
15:09:19.509 C: (audio clip)
15:09:49.903 E: timeout
15:09:49.913 C: (audio clip)
15:10:07.899 T: 0
15:10:07.909 H: 0
15:10:07.919 V: #end_sample
15:10:11.724 K: clean cache 1
15:10:11.784 K: lock retries 0
15:10:11.784 S: exit (0)

Message:
Messages and explanations

Messages described here are not allocated message numbers, but are prefixed
instead with alphabetic codes. For more information see “Message codes” on
page 444.
URI might be output in the error log as
Message: A remote host refused an
file:/C:/dtalk/iscac/main_menu.vxml.
attempted connect operation
Explanation: The system could not resolve a
Message: event.error.semantic
URI to a working host.
Explanation: You have specified markup in a
User response: Check that the host name and
VoiceXML document that is semantically
the URI defined in the default.cff configuration
incorrect. For example, this can occur if you have
file is correct and check that the host is not
referenced a nonexistent audio file without
down.
providing an alternative text-to-speech string in
an audio markup element. If the audio file
Message: event.error.badfetch welcome.wav is not available, but referenced in
the markup element <audio src=welcome.wav/
Explanation: A problem occurred while a
>, a semantic error occurs.
VXML document was loading. This might be
because an incorrect host name was specified in User response: To ensure that the example error
param=URI in the default.cff configuration file, an does not occur, define a text string alternative as
incorrect URI was linked to in a VoiceXML a backup, like this: <audio
document, or an invalid VoiceXML document src=welcome.wav>Welcome to this
was linked to. service.</audio>. You can avoid other semantic
errors by following the guidelines in the
User response: The message usually contains
WebSphere Voice Response: VoiceXML Programmer's
additional information about the nature of the
Guide book and the VoiceXML 1.0 Specification.
problem. Firstly, ensure that the URI link is
correct, and that the file is a valid VXML
document. Message: java.io.FileNotFoundException
To resolve an incorrect configuration, for a Explanation: This error has occurred for one of
VoiceXML document that you are running these reasons:
automatically: v You have incorrectly specified the name of a
1. Stop the node with dtjstop VoiceXML document file in the path of an
2. Edit param=URI in the default.cff configuration appname entry in the default.cff configuration
file file and an error has occurred during dtjstart
3. Run dtjconf v You have referred to a secondary VoiceXML
4. Restart the node with dtjstart. document from an initial one using an
incorrect filename. In this case dtjstart is
If you are running your VoiceXML document
successful, but the error occurs when the
manually with the vxml command, reissue the
secondary document is called with the wrong
command with the correct host name. You
filename.
should also ensure that the referenced document
is actually a .vxml file. User response: To resolve this problem for a
speech browser that runs automatically, stop the
Note that the URI syntax given in the error node with dtjstop, edit the filename in appname
message itself is not necessarily correct. For entry of the default.cff configuration file, run
example, if default.cff correctly defines a dtjconf and restart the node with dtjstart.
document as: file:///C:\dtalk\iscac\
For a speech browser that you started manually
main_menu.vxml but this document is invalid, the

Message:
with the vxml command, reissue the command Explanation: A VoiceXML document contains a
with the correct VoiceXML document filename. markup element or tag that is unsupported.
This error can occur for an incorrectly referenced
User response: To solve this problem, remove
root document or an incorrectly referenced
the unsupported markup element or tag from the
VoiceXML document.
VoiceXML document and replace it with
For audio files that the system cannot locate, this supported markup.
error occurs if no text string alternative has been
defined in the audio markup element in a
Message: No resources are available for
VoiceXML document.
speech recognition
Explanation: Speech recognition has been
Message: Unable to locate the audio cache.
disabled because no free engines are available.
Check that the VXML
This might be because they have been configured
DTPlayURLPlugIn is defined in
to be released when the call ends, rather than
the configuration database
immediately after recognition.
Explanation: The system appears to have
User response: Ensure that the system frees up
started normally (dtjstart was successful), but
each speech recognition engine immediately a
the error written to Node1.out indicates that a
speech recognition process ends rather than
cache has not been created (cache is a key
when the call ends. To do this:
prerequisite for successful system functioning).
1. Stop the node with dtjstop
Ensure that you have defined the cache plug-in
2. Add the attribute Engine_Free=True to
as part of the TTSService entry, and ensure you
InitSessionString= in the default.cff
have referenced the cache plug-in the NodeName
configuration file
entry, in the default.cff configuration file.
3. Run dtjconf
User response: To solve this problem for all 4. Start the node again with dtjstart.
speech browsers, edit the TTSService entry or
If this does not work, check whether speech
NodeName entry, or both, run dtjconf and restart
recognition resources are available on the base
the node with dtjstart.
system:
v Is WebSphere Voice Server installed?
Message: Synthesizer does not support new v Is the WebSphere Voice server running?
pronunciations v Are the entries in VVTdefaults correctly
configured?
Explanation: Your VoiceXML document contains
v Has the shared file system become corrupted?
the unsupported element <ibmlexicon>. In this
condition, dtjstart is successful and the speech
browser is running, but the error is generated Message: error.com.ibm.grammar.storage
when the unsupported element is found. The
Explanation: The system has found a problem
caller might not hear exactly what they expected,
while attempting to store the native forms of
but VoiceXML document processing continues
JSGF defined grammars to the shared file space.
normally to completion. This message is specific
This error can occur if the shared file area runs
to <ibmlexicon> but it is really an unsupported
out of free space, or if you have defined an
element error.
incorrect file path in the speech recognition
User response: Remove the unsupported plug-in definition, in the default.cff
element<ibmlexicon> from your VoiceXML configuration file.
document and use a supported element.
User response: Ensure that enough free space is
available on your JSGF grammars shared file
Message: Unknown or unsupported element system. If storage is not the problem:
1. Stop the node with dtjstop

Message:
2. Modify the path in the RecoService entry in

the default.cff configuration file
3. Run dtjconf
4. Start the node again with dtjstart.
Message: error.com.ibm.grammar.invalid
Explanation: The speech recognition plug-in has
detected a JSGF syntax error
User response: Correct the syntax error in the
JSGF grammar file and run the speech browser
again.
Message: error.com.ibm.configuration.TTS
Explanation: A VoiceXML document has
attempted to play a text-to-speech string but you
have not defined the text-to-speech plug-in in the
default.cff configuration file.
User response: Stop the node with dtjstop,
modify the plug-in entry TTSService in the
default.cff configuration file, run dtjconf and
start the node again with dtjstart.
Message: error.com.ibm.resource.TTS
Explanation: No text-to-speech resources are
available when a VoiceXML document attempts
to play a text-to-speech string. This can occur if
not enough TTS engines are defined in the
procman.cfg file on the server to service the
number of active calls.
User response: Ensure that the system frees up
each text-to-speech engine immediately a
text-to-speech process ends, rather than when the
call ends. To do this, stop the node with dtjstop,
add the attribute Engine_Free=True to
InitSessionString= in the default.cff
configuration file, run dtjconf and start the node
again with dtjstart.

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:
Intellectual Property Licensing,

Legal and Intellectual Property Law,
IBM Japan, Ltd.,
19-21, Nihonbashi-Hakozakicho, Chuo-ku,
Tokyo 103-8510, 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

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 Corp., registered in many jurisdictions
worldwide. Other product and service names might be trademarks of IBM or
other companies. A current list of IBM trademarks is available on the Web at
Copyright and trademark information at http://www.ibm.com/legal/
copytrade.shtml.
Adobe, is a registered trademark of Adobe Systems Incorporated in the

United States, and/or other countries.
Java and all Java-based trademarks and logos are trademarks of Oracle
and/or its affiliates.
Microsoft, Windows, and the Windows logo are trademarks of Microsoft

Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and
other countries.
Notices 453
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

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 457
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,

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 459
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

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 461
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

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 463
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

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 465
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.

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 467
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.

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 469
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

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 471
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.

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 473
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

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 475
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

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 477
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,

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 479
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

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 481
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

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 483
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

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 485
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

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 487
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: MRCP for State Tables, SC34-7086
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
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
List of WebSphere Voice Response and associated documentation 491

v ADC NewNet AccessMANAGER™: User Manual
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:

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 493

Index
channel processes
Special characters messages 176
_alarms utility 29
CHP
<audio> element
messages 176
maxage, maxstale attributes 63
configurator messages 352
“without sending detach” messages 89
connection
Numerics telephony, problems with 55
copying
3270
error log to tape or diskette 14
problems with host access 54
core file 21, 89
problems with server 75, 76
custom server
problems with terminal emulation 55
messages 266
A problems with 77
accessibility xii problems with executing 74
ACL
See Application Connectivity Link (ACL) 264
D
data communications network
AIX trace event ids 17
problems with 44
alarm
database
green 111
DB2 return codes 191
red 111
DBSM return codes 193
See also messages 107
startup error 37
white 112
database manager
yellow 111
messages 231
alarm messages
database serve
See messages 107
DBSM messages 193
analyzing problems 5
DB2
Application Connectivity Link (ACL) messages 264
error on startup 37
B messages 191
background music DBIM
messages 422 messages 231
problems with 71 DBSM messages 193
bipolar violation, telephony line error 28 debugrec 29
blank screen 89 device driver
books, WebSphere Voice Response 3 DTTA 25
buffers rpqio 25
checking 12 diagnosing problems 5
diagnostic recording 29
C Dial action, problems with 65
cache manager messages 229 Digital Trunk Telephony Adapter (DTTA)
call detail record device driver 25
problems with 88 diagnosing unrecognized 27
call transfer diagnostic Procedures 25
problems with 60 diagnostics 27
channel rpqio 25
out of service 90 running diagnostics 27
problems with 52 unrecognized, diagnosing 27
channel available indicator 90 disconnect frame (DISC) 98
disk space
checking on 8

disk space (continued) IBM_Trombone_Custom_Server
problems caused by lack of 8 messages 435
required to avoid performance problems 84 import command
documentation 3 messages issued 169
dtbeProblem 7 incoming call
dtProblem 6 problems with 46
DTTA information frame (I) 98
See Digital Trunk Telephony Adapter (DTTA) 29 initializing
WebSphere Voice Response, problems with 33
E installing
error rate, telephony line error 28 WebSphere Voice Response, problems with 33
errorlog file internal database manager messages 231
copying to tape or diskette 14 ISA 2
errors, system ISDN
messages about 107 D channel monitoring 95
exchange data link line monitor
problems with 50 See ISDN_Monitor 95
ISDN_Call_Transfer custom server
F messages 415
feature codes ISDN_Monitor
DTTA 25 decoding the output 96
file locking problem 62 introduction 95
FileCache failure with VoiceXML applications 62 restarting 96
FileCache problem with VoiceXML applications 63 starting 95
frame stopping 96
disconnect, DISC 98 trace elements 97
information, I 98 writing trace information to a file 96
receive ready, RR 97 writing trace information to a screen 96
supervisory 98
supervisory, REJ (reject) 98 J
supervisory, RNR (receiver not ready) 98 Java and VoiceXML environment messages 271, 385
supervisory, RR (receiver ready) 98 Java exceptions 64
synchronous asynchronous balanced mode extended Juke_Box custom server
(SABME) 97 messages 422
unnumbered acknowledgment, UA 98
unnumbered, U 98 K
free space required to avoid performance problems 84 keys, telephone
frozen screen 89 problems with getting data from 77
G L
GetData action, problems with 67 level of software, checking 13
GetKey action, problems with 67 Licenses 91
grammar compiler log
timeout 82 migration 169
grayed-out applications and operations keywords 90 restoreDT.log 169
green alarm 111 loss of signal, telephony line error 28
LUM messages 222
H
hardware diagnostic procedures M
See diagnostic procedures 25 mailbox, voice
host access, problems with 54 problems with 75
MakeCall action
I problems with 65
IBM Support 1 manuals, WebSphere Voice Response 3
IBM Support Assistant 2 message
problems with 75

messages
“without sending detach” 89
O
OAM
ACL (Application Connectivity Link) 264
messages 284
CA (custom server) 266
outbound call
CACHE (cache manager) 229
problems with 45
categories 111
content 108
CTRL3270 274
P
pack
DBIM (internal database manager) 231 configuration, messages 352
DBSM (database server) 193 page space, system
destination 175 checking 11
destinations 107 performance
DTBE (Java and VoiceXML environment) 271, 385 problems with 83
example 175 PlayVoiceMessage action
explanation 175 problems with 75
filtering 112, 163 print_trace 16
green 154 printer
IBM_Trombone_ Custom_Server 435 problems with 88
ISDN_Call_Transfer custom server 415 problem
issued by import command 169 diagnosis 5
issued by stand-alone migration process 169 solutions 31
Juke_Box custom server 422 processes
LUM (License Use Management) 222 problems with 83
MRCP 442 prompt directory, messages 215
NODEM (node manager) 211
OAM (operations and maintenance) 284 R
pack configuration 352 receive ready frame (RR) 97
SDI (signaling device driver interface) 299 ReceiveData action, problems with 67
session manager/CHP 176 recordutterance error with Nuance speech server 82
severity 113 RecordVoiceMessage action
signaling interface 354 problems with 75
SM_SRVR 272 red alarm 90, 111
SMSI (Simplified Message Service Interface) 225 red channel available indicator 90
SNMP (Simple Network Management remote host access
Protocol) 297 problems with 54
SpeechServer custom server 359
STPD (state table/prompt directory) 215 S
user response 175 SABME, synchronous asynchronous balanced mode
VAD (voice application development) 263 extended frame 97
VAE (general WebSphere Voice Response) 216 SAPI, service access point identifier 97
VPACK, SPACK and XPACK 232 screen
yellow 127, 154 blank or frozen while WebSphere Voice Response is
migrating from WebSphere Voice Response running 89
messages issued 169 SDI messages 299
migration See Digital Trunk Telephony Adapter (DTTA) 29
log 169 SendData action, problems with 67
stand-alone migration process messages 169 service access point identifier (SAPI) 97
MRCP session manager messages 176
messages 442 shutting down WebSphere Voice Response
problems with 89
N signaling interface
NODEM (node manager) messages 211 messages 354
Nuance speech server Simple Network Management Protocol (SNMP)
recordutterance error 82 messages 297
no traps being sent 53
Index 497
Simplified Message Service Interface (SMSI) trace
messages 225 event ids, AIX 17
single system image 35 how to take a trace 15
slow-running system 84 saving 16
SM_SRVR messages 272 starting 16
SMSI stopping 16
See Simplified Message Service Interface system-level Trace 15
(SMSI) 225 TransferCall action
SNMP problems with 65
See Simple Network Management Protocol trunk
(SNMP) 53, 297 problems with enabling 56
software TTS
checking level 13 static 82
solving WebSphere Voice Response problems 31
space U
See disk space 84 unnumbered
SpeechServer acknowledgment frame (UA) 98
messages 359 frame (U) 98
SQL6048N error 37 utilities
SR-INS-002461 Bellcore specification 493 keywords turn gray 90
SSI 35 utilities, debugrec 29
startup, problems with 33, 38 utility, _alarms
state table See Digital Trunk Telephony Adapter (DTTA) 29
messages 215
problems with executing 74 V
static-like TTS 82 VAD (VAG) messages 263
STPD messages 215 VAE messages 216
supervisory frame (S) 98 vaeinit.log file 23
support, WebSphere Voice Response 1 vaeinit.nox.log file 23
synchronous asynchronous balanced mode extended voice application
frame (SABME) 97 problems with 59
system voice interrupt detection
dtbeProblem to describe 7 problems with 70
dtProblem to describe 6 voice segment
trace 15 problems with playing 68
system-level trace 15 VoiceXML
cannot record caller audio input 82
T VoiceXML exceptions 64
technical difficulties message 51 VoiceXML file lock 62
TEI, terminal endpoint identifier 97 voicexml voice audio files 63
telephone network VPACK messages 232
problems with 44 VXML messages 444
telephony connection
problems with 55 W
telephony line errors WebSphere Voice Response
bipolar violation 28 database return codes 191, 193
error rate 28 Welcome window
loss of signal 28 problems with 36
other errors 28 white alarm 112
telephony problem without an alarm indicator 90 window
terminal emulation, problems with 55 problems with
terminal endpoint identifier (TEI) 97 WebSphere Voice Response activates without
timeout waiting for grammar compiler 82 being selected 84
TR-NWT-001273 Bellcore specification 493 Welcome window does not display 36
Xstation displayed in wrong font 39

X
XPACK
messages 232
Xstation
problems with windows 39
Y
yellow alarm 90, 111
Index 499

Product Number: 5724-I07
GC34-7087-07

WVR61 Problem Determination c3470877

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WVR61 Problem Determination c3470877

Uploaded by

Copyright:

Available Formats

WebSphere Voice Response for AIX with DirectTalk

© Copyright IBM Corp. 1991, 2013 iii

© Copyright IBM Corp. 1991, 2013 vii

© Copyright IBM Corp. 1991, 2013 ix

If you are a newcomer to WebSphere Voice Response, start with Chapter 1,

If you get a message when migrating or importing data, look it up in

If you get a numbered WebSphere Voice Response message in the error.log

How to use this information

The background information explains when to use the procedures and

Following the procedures in this information

© Copyright IBM Corp. 1991, 2013 xi

xii Problem Determination

Where to find more information

About this information xiii

Making comments on this book

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

xiv Problem Determination

© Copyright IBM Corp. 1991, 2013 1

IBM Support Assistant (ISA)

ISA provides the following services:

To obtain ISA, go to the download page at https://www14.software.ibm.com/

IBM support resources

What to expect when you call IBM Support

Chapter 1. Introducing WebSphere Voice Response support 3

This chapter is organized as follows:

Cataloging the symptoms

Try to isolate all events that seem to be symptoms of the problem. It is

© Copyright IBM Corp. 1991, 2013 5

Because hardware and software problems are handled by different IBM

Describing the state of the system

This section contains instructions for the following:

On the output directory is a file called dtProblem.tar.Z, ready for

Collecting Java and VoiceXML environment specific information

If the problem can be easily re-created, collect a trace. To do this:

Chapter 2. Analyzing the problem 7

To run dtbeProblem automatically when a specified error is logged to the

To collect dtbeProblem data:

Checking disk space

Using SMIT to increase the size of your file system:

Checking user processes

Chapter 2. Analyzing the problem 9

To calculate the number of user processes WebSphere Voice Response requires,

Using this information

To calculate the number of user processes WebSphere Voice Response requires,

Increasing page space

You can increase the page space in 2 ways:

Adding logical partitions:

Type the following command and press Enter:

The system adds 9 logical partitions to the logical volume hd6.

Chapter 2. Analyzing the problem 11

Type the following command and press Enter:

Using this information

Using this information

For instructions on how to reset the value of a system parameter, see

The installed WebSphere Voice Response filesets are displayed.

For more information:

Chapter 2. Analyzing the problem 13

Before you call IBM Support

If you need to take a longer trace, perhaps to investigate an infrequently

Chapter 2. Analyzing the problem 15

Remember to ensure that there is sufficient space in whichever location

Note: Although the default is for the trace command to run in an

Using WebSphere Voice Response AIX system trace event

Chapter 2. Analyzing the problem 17