Professional Documents
Culture Documents
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
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
Throughout this book, the IBM WebSphere Voice Response for AIX voice
processing system is referred to as WebSphere Voice Response.
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.
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
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.
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.
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.
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.
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.
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
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.
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.
4 Problem Determination
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.
6 Problem Determination
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.)
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.
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.
8 Problem Determination
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.
To check the number of user processes defined for your system, you can use
either an AIX command or SMIT.
Using AIX:
1. Log on to AIX as root.
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.
10 Problem Determination
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.
1. Log on to AIX as root.
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.
where ## is the number of logical partitions to add and @@@ identifies the
logical volume. For example,
chps -s 9 hd6
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.
12 Problem Determination
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.
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*
Review the contents of the error log by using the AIX editor.
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 User Login menu.
3. Type 2 and press Enter.
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.
14 Problem Determination
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.
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.
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
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>
16 Problem Determination
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.
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.
18 Problem Determination
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.
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.
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
20 Problem Determination
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
WebSphere Voice Response for AIX: Configuring the System.
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
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.
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.
22 Problem Determination
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.
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).
For example, if you can run only a small subset of your voice
applications, you have a severity 2 problem
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.
24 Problem Determination
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.
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.
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
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.
To check that conditions are correct to start WebSphere Voice Response, type
the command:
lsdev -C | grep dtline
26 Problem Determination
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).
Note: For the DTTA, the Field Replaceable Unit (FRU) is the entire adapter.
28 Problem Determination
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.
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
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.
30 Problem Determination
Chapter 3. Solving WebSphere Voice Response problems
This chapter describes how to solve some common problems.
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.
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.
Note: You cannot perform the Development actions remotely. You must use
the Development menu on the Welcome Window for these.
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.
32 Problem Determination
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
34 Problem Determination
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:
When the Welcome window does not display, check the following:
Is the tasklist.data file corrupted or is there more than one instance?
WebSphere Voice Response starts the processes listed in the
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.
36 Problem Determination
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
dependent module /unix.
0509-136 Symbol acancel64 (number 2) is not exported from
dependent module /unix.
0509-136 Symbol iosuspend64 (number 3) is not exported from
dependent module /unix.
0509-136 Symbol aio_nwait (number 4) is not exported from
dependent module /unix.
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.
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.
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
38 Problem Determination
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:
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.
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.
40 Problem Determination
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>
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
42 Problem Determination
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
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
44 Problem Determination
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.
46 Problem Determination
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
48 Problem Determination
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
50 Problem Determination
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.
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 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
tracing signaling interfaces, see WebSphere Voice Response for AIX:
Programming for the Signaling Interface.
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
52 Problem Determination
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
tracing signaling interfaces, see WebSphere Voice Response for AIX:
Programming for the Signaling Interface.
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
Response for AIX: Managing and Monitoring the System.
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.
54 Problem Determination
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.
For more information on 3270 emulation, see WebSphere Voice Response for AIX:
Configuring the System.
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,
check the following:
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.
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?
Use the information provided in WebSphere Voice Response for AIX:
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.
56 Problem Determination
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.
Are you using a signaling process that you developed yourself?
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.
58 Problem Determination
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.
60 Problem Determination
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
WebSphere Voice Response for AIX: Application Development using State
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.
62 Problem Determination
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 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.
64 Problem Determination
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
Development using State Tables.
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
66 Problem Determination
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
68 Problem Determination
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
Development using State Tables book.
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
WebSphere Voice Response for AIX: Application Development using State
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.
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.
70 Problem Determination
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.
72 Problem Determination
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.
74 Problem Determination
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
Development using State Tables book.
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,
check the following:
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
Response for AIX: Application Development using State Tables book.
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.
76 Problem Determination
For information about debugging a 3270 server, see the WebSphere
Voice Response for AIX: Application Development using State Tables book.
Custom server does not start
When an OpenHostServerLink action fails to start the specified custom server,
check the following:
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
Response for AIX: Application Development using State Tables book.
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:
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>
78 Problem Determination
<audio scr=PIN.wav />
</prompt>
</form>
</vxml>
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.
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
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.
80 Problem Determination
system parameter called Voice Message Compression Type, which is in the
Application Server Interface group . It can be set to compressed (default) or
uncompressed.
VoiceXML -> state table -> ... -> state table -> VoiceXML
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:
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
For the change in dtj.ini to take effect, you must restart VRBE.
Note: The parameter change will have an affect on all MRCP responses, not
just grammar compilation.
82 Problem Determination
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?
WebSphere Voice Response starts the processes listed in the
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
84 Problem Determination
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
Response for AIX: Managing and Monitoring the System.
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.
Use the information provided in WebSphere Voice Response for AIX:
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.
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
86 Problem Determination
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
Response for AIX: Managing and Monitoring the System.
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
88 Problem Determination
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
90 Problem Determination
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.
Are you using a signaling process that you developed yourself?
Check whether your signaling process is still running. Message 32011
in the error log indicates that a signaling process has terminated.
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
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
92 Problem Determination
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.
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.
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
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.
94 Problem Determination
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 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
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.
96 Problem Determination
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.
Trace elements
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)
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 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.
98 Problem Determination
Q921 DT/6000 12:50:01 TEI=00 Cmd
SAPI=00 U FRAME - SABME
Q921 DT/6000 12:50:02 TEI=00 Cmd
SAPI=00 U FRAME - SABME
Q921 DT/6000 12:50:03 TEI=00 Cmd
SAPI=00 U FRAME - SABME
Q921 DT/6000 12:50:04 TEI=00 Cmd
SAPI=00 U FRAME - SABME
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.
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.
Outbound calls
Figure 7 on page 103 shows the flow of call related events for an outbound
call from WebSphere Voice Response:
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.
Call clearing
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
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.
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.
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.
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)
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.
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.
Messages by severity
This section lists the numbers of the WebSphere Voice Response messages in
each color category.
Table 2 Red
Red messages
Table 2. WebSphere Voice Response messages classified as Red
17906 UNUSED
17918 UNUSED
17919 UNUSED
17956 UNUSED
17957 UNUSED
17958 UNUSED
17964 Adapter card not set up with high enough interrupt priority
17976 UNUSED
27046 SDI failed to enable pack because signalling process was missing
27047 SDI: pack type changed while WebSphere Voice Response was
running
29400 Invalid ISDN Layer 3 task number passed from call control
29601 Invalid ISDN Layer 2 task number passed from call control
29612 ISDN Layer 2 had an error trying to start its child process
Yellow messages
Table 3. WebSphere Voice Response messages classified as Yellow
406 No profile ID
407 No profile ID
1100 Could not initialize local variable table. Cannot start check.
13017 License request has failed because the license is not installed
and distributed.
25103 OAM bad return code from ioctl: speech recognition statistics
25104 OAM bad return code from malloc: speech recognition statistics
1101 Could not reinitialize local variable table. Creating new table.
25097 OAM test message with both strings and decimals on the
console
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
Threshold criteria
Threshold criteria
Threshold criteria
Threshold criteria
Threshold criteria
You can find the stand-alone migration log, restoreDT.log, in the directory
from which you invoked restoreDT.
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
specified WebSphere Voice Response Version 4.2
database table. Explanation: An error occurred opening the
specified WebSphere Voice Response Version 4.2
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
recovery is complete, retry the migration process.
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
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,
recovery is complete, retry the migration process.
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
for a description of the WebSphere Voice
migration process again.
Response database return codes. If the return
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.
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
29200 “ISDN signaling process and ISDN call control” on page 316
Example Message
Session Manager/CHP
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.
Destination: Log, System Monitor
Severity: Yellow
114 Could not turn play off Destination: Log, System Monitor
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.
Destination: Log, System Monitor
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
Destination: Log, System Monitor
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
Destination: Log, System Monitor
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
Destination: Log, System Monitor
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
errors and follow the appropriate steps for
of the cache.
dealing with them. Check that the process named
Severity: Yellow UPSERVER is still running. If not, this is the
probable cause of this error. Check for core files
Destination: Log, System Monitor
in /var/adm/ras/dirTalk and contact IBM
Support. If the system load is high, try to reduce
207 DBIM request timeout it.
Severity: Yellow
400 Profile not found
Destination: Log, System Monitor
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
errors and follow the appropriate steps for
Destination: Log, System Monitor
dealing with them. Check that the process named
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
Destination: Log, System Monitor
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
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.
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
Destination: Log, System Monitor
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
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
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
Destination: Log, System Monitor
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
User response: None. The channel process has Destination: Log, System Monitor
recovered from the error.
Severity: White 1201 Line problem
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.
Destination: Log, System Monitor
Severity: White
Destination: Log, System Monitor
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.
Destination: Log, System Monitor
Severity: Yellow
Destination: Log, System Monitor
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 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
Destination: Log, System Monitor
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
Destination: Log, System Monitor
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
Destination: Log, System Monitor
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
Destination: Log, System Monitor
Destination: Log, System Monitor
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
User response: Check for excessive disk, CPU,
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.
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.
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
persists, contact IBM Support.
-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.
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
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
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.
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.
-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.
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
Destination: Log, System Monitor, Alertable
parameters to determine if this error is being
produced because of an application error.
5005 Notify_appl() failed
Severity: Yellow
Explanation: A database server could not send
Destination: Log, System Monitor
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
Destination: Log, System Monitor, Alertable
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.
Severity: White
5036 File delete failed
Destination: Log, System Monitor
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
Destination: Log, System Monitor
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).
User response: If this problem persists, call IBM Destination: Log, System Monitor
Support.
Severity: Yellow 5046 Segment create 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
Destination: Log, System Monitor
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
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
Destination: Log, System Monitor
errno or database return code received.
User response: Refer to the description of
5068 Get record by key failed
WebSphere Voice Response database return codes
(dmsgetk)
in the Problem Determination book.
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
WebSphere Voice Response database return codes
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
Destination: Log, System Monitor
return code received.
User response: Refer to the description of
5069 Get record sequentially failed
WebSphere Voice Response database return codes
(dmsgets)
in the Problem Determination book.
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.
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
WebSphere Voice Response database return codes
Destination: Log, System Monitor
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
WebSphere Voice Response database return codes
Destination: Log, System Monitor
in the Problem Determination book.
Severity: Yellow
5074 Commit failed (dmscmit)
Destination: Log, System Monitor
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
User response: Refer to the description of
WebSphere Voice Response database return codes
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
value is set to the AIX errno or database return
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.
Destination: Log, System Monitor
User response: Refer to the description of
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
User response: Refer to the description of
appropriate indication returned to the
WebSphere Voice Response database return codes
application.
in the Problem Determination book.
User response: Restart WebSphere Voice
Severity: Yellow
Response. If the problem persists, call IBM
Destination: Log, System Monitor Support.
Severity: Yellow
5086 Fetch row failed (dmsftch)
Destination: Log, System Monitor
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
User response: Refer to the description of
files, or message files is full. This is caused by
WebSphere Voice Response database return codes
the improper definition of system parameters.
in the Problem Determination book.
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
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
Destination: Log, System Monitor, Alertable
Destination: Log, System Monitor
Severity: Green
5318 Incorrect Mailbox Count Detected
Destination: Log, System Monitor, Alertable
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.
taking calls until the problem is fixed.
Severity: White
User response: See below for SQL diagnostic
Destination: Log, System Monitor
message. Investigate network and DB2.
Severity: Red
5319 Invalid msg creation time detected
Destination: Log, System Monitor
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):
User response: Investigate network and DB2.
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.
Explanation: The DBHEALTH process
periodically checks files under CUR_DIR. An Severity: Yellow
attempt to write and read the file identified
Destination: Log, System Monitor
below failed. WebSphere Voice Response will
cease taking calls until the problem is fixed.
5320 System clock jumped
User response: Investigate network and DB2.
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.
Destination: Log, System Monitor, Alertable
User response: If conflicting clock deamons are
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.
Destination: Log, System Monitor, Alertable
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
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.
12010 Invalid message type
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
User response: This error can be caused by
Support.
other error conditions in the system. Review the
Severity: Yellow WebSphere Voice Response error logs and try to
correct other problems first. If the problem
Destination: Log, System Monitor
persists after shutting down and restarting
WebSphere Voice Response, and shutting down
12008 Attachq() failed and restarting AIX, call IBM Support.
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
Destination: Log, System Monitor
requesting will not function properly.
User response: Check the reason for the failure
13008 License request has failed because
using License Use Management documentation.
of hard-stop
Check that License Use Management is correctly
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.
Destination: Log, System Monitor
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
Destination: Log, System Monitor
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
Destination: Log, System Monitor
using License Use Management documentation.
Check that License Use Management is correctly
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.
Destination: Log, System Monitor
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 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
Destination: Log, System Monitor
Destination: Log, System Monitor
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: Review the hardware and
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.
Severity: Yellow Severity: Yellow
Destination: Log, System Monitor Destination: Log, System Monitor
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
problem persists, call IBM Support.
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
Destination: Log, System Monitor
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.
Destination: Log, System Monitor, Alertable
Severity: Yellow
Destination: Log, System Monitor
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.
Severity: Yellow Severity: Yellow
Destination: Log, System Monitor Destination: Log, System Monitor
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
Destination: Log, System Monitor, Alertable
Destination: Log, System Monitor
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.
User response: Call IBM Support.
User response: Restart WebSphere Voice
Severity: Red
Response. If the problem persists, call IBM
Destination: Log, System Monitor, Alertable Support.
Severity: Red
14024 SMSI: MWI NAK retry failure
Destination: Log, System Monitor, Alertable
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
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
Support and give them: - Details of your
the MWI Number Length parameter. It is invalid.
configuration for the Exchange Data Link. - A
The error parameters indicate the expected
copy of the error log showing one or more
number length, whether padding is enabled, the
examples of this error condition. - A system trace
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
Support and give them: - Details of your
Severity: Yellow
configuration for the Exchange Data Link. - A
Destination: Log, System Monitor copy of the error log showing one or more
examples of this error condition. - A system trace
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
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
User response: Call IBM Support.
Explanation: The cache manager received a
Severity: White message with missing information. Requests for
voice segments can time out.
Destination: Log, System Monitor
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
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.
that all cable connectors are firmly seated. Run
Severity: Red
the diagnostics described in the Problem
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
beyond the WebSphere Voice Response
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)
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
Response, and the receive side of the terminating
Severity: Red equipment are probably functioning correctly.
Destination: Log, System Monitor, Alertable User response: Check the telecommunication
cables and connections to the network. Check
that all cable connectors are firmly seated. Run
17008 E1 excessive error qualified alarm
the diagnostics described in the Problem
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.
Response, and the receive side of the terminating
Severity: Yellow
equipment are probably functioning correctly.
Destination: Log, System Monitor
User response: Check the telecommunication
cables and connections to the network. Check
that all cable connectors are firmly seated. Run 17010 E1 multiframe alignment loss
the diagnostics described in the Problem qualified alarm
Determination book. If the cable and WebSphere
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
(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.
User response: Check the telecommunication
cables and connections to the network. Check Severity: Yellow
that all cable connectors are firmly seated. Run
Destination: Log, System Monitor
the diagnostics described in the Problem
Determination book. If the cable and WebSphere
Voice Response are OK, the problem is with the 17012 T1 or ethernet loss-of-signal
terminating equipment or the transmission path qualified alarm
beyond the WebSphere Voice Response
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
Destination: Log, System Monitor
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
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
Destination: Log, System Monitor, Alertable
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
Destination: Log, System Monitor, Alertable
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
call that has already been hung up by the clears: 17042, 7043, 17045
application.
Severity: Yellow
User response: Check the application for
Destination: Log, System Monitor
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
the problem, have the following available when
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
Destination: Log, System Monitor
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 -
the problem persists, call IBM Support. To help
Details of the version of WebSphere Voice
solve the problem, have the following available
Response you are using, along with details of
when you call: - Details of the switch and
any PTFs that have been applied - A system-level
WebSphere Voice Response telephone setup -
trace of the problem
Details of the version of WebSphere Voice
Response you are using, along with details of Severity: Green
any PTFs that have been applied - A system-level
Destination: Log, System Monitor
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.
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.
the problem, have the following available when
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
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
the problem persists, call IBM Support. To help
Severity: Yellow
solve the problem, have the following available
Destination: Log, System Monitor when you call: - Details of the switch and
WebSphere Voice Response telephone setup -
Details of the version of WebSphere Voice
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
the problem persists, call IBM Support. To help
Group D could not complete. This can be caused
solve the problem, have the following available
by an incorrect dialed number format, or because
when you call: - Details of the switch and
Feature Group D is not enabled on the switch.
WebSphere Voice Response telephone setup -
Note: Outbound Feature Group D is supported
Details of the version of WebSphere Voice
only on the E&M and DID protocols.
Response you are using, along with details of
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
Response you are using, along with details of
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
Destination: Log, System Monitor Destination: Log, System Monitor
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
Destination: Log, System Monitor
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
/tmp/dt6umstmp1, /tmp/dt6umstmp2, and may be using the ODM database, or have locked
/tmp/dt6umstmp3. it. Try again later.
Severity: White Severity: White
Destination: Log, System Monitor Destination: Log, System Monitor
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
Explanation: Cannot open line output device User response: If the problem persists, call IBM
file dev/acpa0llcd. Support with details.
Severity: Red
17610 TDM clock fork failed
Destination: Log, System Monitor, Alertable
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
persists, call IBM Support.
User response: Call IBM Support.
Severity: Red
Severity: Red
Destination: Log, System Monitor, Alertable
Destination: Log, System Monitor, Alertable
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
unit. If the problem persists, call IBM Support.
Severity: Red 17807 Failed to access adapter
components
Destination: Log, System Monitor, Alertable
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,
User response: Try to re-run the startup
it means either that the test card is not a
procedure. If the problem persists, run the
telephony adapter or that the vital product data
stand-alone diagnostics to get more information
(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
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
User response: Try to re-run the startup
adapter card during the startup diagnostics.
procedure. If the problem persists, call IBM
User response: Try to re-run the startup Support.
procedure. If the problem persists, run the
Severity: Red
stand-alone diagnostics to get more information
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
Destination: Log, System Monitor, Alertable
Explanation: During the startup procedure, the
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.
User response: Try to re-run the startup
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
Destination: Log, System Monitor, Alertable
Destination: Log, System Monitor, Alertable
17820 Telephony adapter diagnostics
17811 AIB diagnostics cannot open cannot open device driver
SC4000 device driver
Explanation: During the startup procedure, the
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
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
Destination: Log, System Monitor, Alertable
Destination: Log, System Monitor, Alertable
17821 Unexpected software error during
17812 Unexpected software error during pack startup diagnostics
AIB startup diagnostics
Explanation: During the startup procedure, the
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
User response: Try to re-run the startup
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.
User response: Try to re-run the startup
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
User response: If the problem persists, call IBM User response: Call IBM Support.
Support.
Severity: Red
Severity: Red
Destination: Log, System Monitor, Alertable
Destination: Log, System Monitor, Alertable
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.
the problem persists, call IBM Support.
Severity: Red
Severity: Red
Destination: Log, System Monitor, Alertable
Destination: Log, System Monitor, Alertable
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: Try restarting the pSeries system
User response: Make sure that all WebSphere unit. If the problem persists, call IBM Support.
Voice Response filesets are installed correctly. If
Severity: Red
the problem persists, call IBM Support.
Destination: Log, System Monitor, Alertable
Severity: Red
Destination: Log, System Monitor, Alertable
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.
Destination: Log, System Monitor, Alertable
User response: Call IBM Support.
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
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.
Severity: Red Severity: Red
Destination: Log, System Monitor, Alertable Destination: Log, System Monitor, Alertable
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
User response: Try restarting the pSeries system
needs to be removed before it can be added.
unit. If the problem 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
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
User response: Try restarting the pSeries system
Voice Response devices. All devices need to be
unit. If the problem persists, call IBM Support.
made unavailable before dtdd_undef can be
Severity: Red called.
Destination: Log, System Monitor, Alertable User response: Try restarting the pSeries system
unit. If the problem persists, call IBM Support.
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
Destination: Log, System Monitor, Alertable
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
Explanation: As part of the WebSphere Voice
Destination: Log, System Monitor, Alertable
Response startup procedure, several hardware
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
Explanation: As part of the WebSphere Voice
data known as the vital product data (VPD). The
Response startup procedure, several hardware
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
Response startup procedure, several hardware
devices are configured. To configure a device, the
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
Explanation: As part of the WebSphere Voice
configured. To avoid race and deadlock
Response startup procedure, several hardware
conditions, the ODM database has a lock which
devices are configured. To configure a device, the
must be obtained before it can be used. The
configuration method for that device is 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
User response: Backup the error log. Try Destination: Log, System Monitor, Alertable
restarting the pSeries system unit. If the problem
persists, send the error log to IBM Support.
17951 Configuration method called with
Severity: Red device already available
Destination: Log, System Monitor, Alertable Explanation: As part of the WebSphere Voice
Response startup procedure, several hardware
devices are configured. To configure a device, the
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
17952 Configuration method failed to
this with the error log to IBM Support.
load kernel extension into
Severity: Red memory
Destination: Log, System Monitor, Alertable Explanation: As part of the WebSphere Voice
Response startup procedure, several hardware
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
User response: Backup the error log. Try
this device.
restarting the pSeries system unit. If the problem
User response: Backup the error log. Try persists, call IBM Support.
restarting the pSeries system unit. If the problem
Severity: Red
persists, call IBM Support.
Destination: Log, System Monitor, Alertable
Severity: Red
Destination: Log, System Monitor, Alertable
17955 Configuration of logical device
failed
17953 Configuration method failed to
Explanation: As part of the WebSphere Voice
allocate a major number
Response startup procedure, several hardware
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
User response: Backup the error log. Try
problem in the device driver. The I/O subsystem
restarting the pSeries system unit. If the problem
cannot use this device.
persists, call IBM Support.
User response: Backup the error log. Try
Severity: Red
restarting the pSeries system unit. If the problem
Destination: Log, System Monitor, Alertable persists, call IBM Support.
Severity: Red
17954 Configuration of logical device
Destination: Log, System Monitor, Alertable
failed
Explanation: As part of the WebSphere Voice
17956 UNUSED
Response startup procedure, several hardware
devices are configured. To configure a device, the Explanation: UNUSED
configuration method for that device is used. The
User response: 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
User response: Backup the error log. Try Destination: Log, System Monitor, Alertable
restarting the pSeries system unit. If the problem
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
Destination: Log, System Monitor, Alertable
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
Destination: Log, System Monitor, Alertable
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:
Destination: Log, System Monitor, Alertable
- 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,
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
persists, call IBM Support.
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
Destination: Log, System Monitor, Alertable
persists, call IBM Support for assistance.
Severity: Red
17973 Telephony adapter driver detected
invalid size on primitive Destination: Log, System Monitor, Alertable
Explanation: The WebSphere Voice Response
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
Explanation: WebSphere Voice Response has
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.
Destination: Log, System Monitor, Alertable
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
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
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
Destination: Log, System Monitor, Alertable
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
Destination: Log, System Monitor, Alertable
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
Destination: Log, System Monitor, Alertable
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
Explanation: WebSphere Voice Response failed
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
Response. Try restarting the pSeries system unit.
User response: Plug the cable. Replug the cable.
If the problem persists, call IBM Support.
Replace the cable with a known good T1 or E1
cable. If the problem persists, call IBM Support Severity: Red
for assistance.
Destination: Log, System Monitor, Alertable
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
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
Destination: Log, System Monitor, Alertable
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
Destination: Log, System Monitor, Alertable
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.
Destination: Log, System Monitor
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
User response: Call IBM Support.
Destination: Log, System Monitor, Alertable
Severity: Red
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
the problem persists, call IBM Support.
during normal operations.
Severity: Yellow
User response: Restart the custom server
control program and all the custom servers. If Destination: Log, System Monitor
the problem persists, call IBM Support.
Severity: Yellow 20005 Channel process link ID returned
is invalid
Destination: Log, System Monitor
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.
Destination: Log, System Monitor
Severity: Yellow
Destination: Log, System Monitor
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
User response: Restart the custom server
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.
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.
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.
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.
Destination: Log, System Monitor
Severity: White
Destination: Log, System Monitor
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
Destination: Log, System Monitor User response: Depends on the custom server.
Severity: Red
Destination: Log, System Monitor, Alertable
SM_SRVR
see if it is there and complete.
23001 Invalid message received
Severity: Yellow
Explanation: Unexpected message received on
the server queue. Destination: Log, System Monitor
User response: If the problem persists, call IBM
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.
User response: Call IBM Support.
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.
Destination: Log, System Monitor, Alertable
User response: Call IBM Support.
23003 Error attaching queue Severity: Yellow
Explanation: Cannot attach server's queue. Destination: Log, System Monitor
User response: Call IBM Support.
23009 SMSERVER discarding statistics
Severity: Red
messages
Destination: Log, System Monitor, Alertable
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.
CTRL3270
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.
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
Destination: Log, System Monitor
User response: Correct the script. User response: Verify that the 3270 script is
valid, and retry the operation.
Severity: White
Severity: Yellow
Destination: Log, System Monitor
Destination: Log, System Monitor
24507 Script attempted invalid
arithmetic operation 24511 Script attempted invalid jump
operation
Explanation: An internal error occurred while
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.
User response: Verify that the 3270 script is
valid, and retry the operation. User response: Verify that the 3270 script is
valid, and retry the operation.
Severity: Yellow
Severity: Yellow
Destination: Log, System Monitor
Destination: Log, System Monitor
24508 Script attempted invalid
comparison operation 24512 Exception definition or handler
load failed
Explanation: An internal error occurred while
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
User response: Verify that the 3270 script is
condition (EX_NO_SCRIPT), it is called.
valid, and retry the operation.
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.
Destination: Log, System Monitor User response: Verify that the 3270 script is
valid, and retry the operation.
Severity: Yellow did not match the number that were contained in
the chain.
Destination: Log, System Monitor
User response: None.
24703 Internal function (NotifyAppl) Severity: Yellow
failed
Destination: Log
Explanation: An internal error occurred while
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
Destination: Log, System Monitor
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: None.
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
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.
Destination: Log, System Monitor
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
Destination: Log, System Monitor
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.
User response: None.
Severity: White
Severity: White
Destination: Log, System Monitor
Destination: Log
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
Destination: Log, System Monitor
library
Explanation: The WebSphere Voice Response
SNA library failed to allocate some memory.
User response: Check real and paged memory
usage for resource over-commitment.
Severity: Red
Destination: Log, System Monitor
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
Severity: Yellow Support.
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
WebSphere Voice Response.
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.
User response: If the problem persists, call IBM
25010 OAM received unknown Support.
notification
Severity: Yellow
Explanation: OAM received a notification of an
Destination: Log, System Monitor
unknown type from another component of
WebSphere Voice Response.
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
Destination: Log, System Monitor
persists, call IBM Support.
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
WebSphere Voice Response.
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.
Destination: Log, System Monitor
Severity: Yellow
25012 OAM message receive failed Destination: Log, System Monitor
Explanation: OAM message receive (msgrcv)
failed. `errno' 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
User response: Check for and correct other
Destination: Log, System Monitor
errors, and if the problem persists, call IBM
Support.
25015 OAM received invalid request for
Severity: Yellow
periodic report
User response: Check for and correct other Destination: Log, System Monitor
errors, and if the problem persists, call IBM
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
WebSphere Voice Response.
25022 OAM problem with file access User response: Check for and correct other
errors, and if the problem persists, call IBM
Explanation: OAM tried to access a file, but Support.
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: None, ignore this message.
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
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
errors, and if the problem persists, call IBM
Destination: Log, System Monitor
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
User response: If the problem persists, call IBM
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
Destination: Log, System Monitor, Alertable
errors occurring inWebSphere Voice Response .
User response: Check for and correct other
25046 OAM test for in task recovery
errors, and if the problem persists, call IBM
Explanation: This message is used for test Support.
purposes only.
Severity: Yellow
User response: None, ignore this message.
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
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: None, ignore this message.
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.
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
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
User response: Check for excessive disk, CPU,
Explanation: This clears the performance
or network load, which cause delays in retrieving
degradation reported by an earlier error 25204.
voice data from local disk or a remote SSI server.
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
Destination: Log, System Monitor, Alertable
Destination: Log, System Monitor, Alertable
Destination: Log, System Monitor, Alertable Destination: Log, System Monitor, Alertable
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
Destination: Log, System Monitor, Alertable
IBM Support.
Severity: White
Destination: Log, System Monitor, Alertable
Sometimes after pack configuring a partial CAS `odmerrno' 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.
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
27016 Diagnostics failed
Destination: Log, System Monitor
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
User response: Examine the error log for
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.
Destination: Log, System Monitor, Alertable
Check the `rc' field against $VAE/db/
current_dir/ca/include/slcommon.h.
27017 Diagnostics failed
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
User response: Examine the error log for
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
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
Destination: Log, System Monitor
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
Destination: Log, System Monitor
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
User response: Restart WebSphere Voice
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.
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
Destination: Log, System Monitor, Alertable
Destination: Log, System Monitor, Alertable
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
Destination: Log, System Monitor, Alertable
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.
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.
Destination: Log, System Monitor, Alertable
Severity: Yellow
Destination: Log, System Monitor, Alertable
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
User response: Check your signalling process
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
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
Destination: Log, System Monitor, Alertable
are indicated and the problem occurs repeatedly,
contact IBM Support for further problem
27071 SDI failed accessing error channel diagnosis and resolution.
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
Destination: Log, System Monitor
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
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
Destination: Log, System Monitor
Destination: Log, System Monitor
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.
Destination: Log, System Monitor
Severity: Yellow
Destination: Log, System Monitor
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
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
without further problems. If further problems do
Destination: Log, System Monitor
occur, stop and restart the ISDN signalling
process using the Custom Server Manager. If the
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.
User response: The system may continue
Severity: White without further problems. If further problems do
occur, stop and restart the ISDN signalling
Destination: Log, System Monitor
process using the Custom Server Manager. If the
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
/var/tmp directory as soon as the error occurs.
Explanation: One of the ISDN protocol
components tried to put a message onto a Severity: White
message queue from the holding bay, but this
Destination: Log, System Monitor
failed. A software problem in the ISDN protocol
is the probable cause of this error.
29110 ISDN environment services buffer
User response: The system may continue
pool audit problems
without further problems. If further problems do
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.
/var/tmp directory as soon as the error occurs.
User response: The system may continue
Severity: Yellow without further problems. If further problems do
occur, stop and restart the ISDN signalling
Destination: Log, System Monitor
process using the Custom Server Manager. If the
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
/var/tmp directory as soon as the error occurs.
Explanation: One of the ISDN protocol
components tried to allocate a buffer, but there Severity: Yellow
are no buffers available.
Destination: Log, System Monitor
User response: The system may continue
without further problems. If further problems do
29111 Insufficient disk space for ISDN
occur, stop and restart the ISDN signalling
environment services
process using the Custom Server Manager. If the
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.
/var/tmp directory as soon as the error occurs.
User response: The name of the directory in
Severity: Yellow which the ISDN environment services files are
stored, the space required, and the space
Destination: Log, System Monitor
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
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
using the Custom Server Manager menu option.
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.
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
User response: If this error occurs frequently it
Destination: Log, System Monitor may indicate a problem with WebSphere Voice
Response. Stop and restart the signalling process
29212 ISDN call state machine invalid using the Custom Server Manager menu option.
primitive If this does not work, shut down and restart
WebSphere Voice Response. If none of the above
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.
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
none of the above is successful call IBM Support.
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
User response: If this error occurs frequently it
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.
ISDN D Layer 3
User response: If this error occurs frequently it
29400 Invalid ISDN Layer 3 task
may indicate a problem with WebSphere Voice
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
User response: Check the error log for other
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.
occurs frequently it may indicate a problem with
WebSphere Voice Response. Disable and Severity: Red
re-enable the trunk on which the error occurred
Destination: Log, System Monitor
and try again. If the problem persists, stop and
restart the signalling process using the Custom
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
User response: If this error occurs frequently it
Destination: Log, System Monitor may indicate a problem with WebSphere Voice
Response. Disable and re-enable the trunk on
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
Destination: Log, System Monitor
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
Destination: Log, System Monitor
detected a recoverable internal error. Individual
calls may be cleared by these errors.
29402 ISDN Layer 3 initialization
User response: If this error occurs frequently it
parameter error
may indicate a problem with WebSphere Voice
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
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.
process are disabled. If this does not solve the
User response: This message is for information
problem shut down and restart WebSphere Voice
only.
Response. If none of the above is successful call
IBM Support. Severity: White
Severity: Yellow Destination: Log, System Monitor
Destination: Log, System Monitor
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
User response: This message is for information
Destination: Log, System Monitor
only.
Severity: White
29406 ISDN Layer 3 primary data link
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.
29410 ISDN Layer 3 primary data link
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.
User response: This message is for information
29407 ISDN Layer 3 backup data link only.
layer activated Severity: White
Explanation: The backup ISDN Layer 2 has Destination: Log, System Monitor
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
User response: If this error occurs frequently it
against the Installation book or Configuring the
may indicate a problem with WebSphere Voice
System book. Save any changes. Try to re-enable
Response. Disable and re-enable the trunk on
the trunk on which the error occurred. If this
which the error occurred and try again. Have the
does not solve the problem, shut down and
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
none of the above is successful call IBM Support.
call IBM Support.
Severity: Red
Severity: Red
Destination: Log, System Monitor
Destination: Log, System Monitor
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.
Destination: Log, System Monitor
User response: If this error occurs frequently it
may indicate a problem with WebSphere Voice
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
problem persists, stop and restart the signalling
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
which the error occurred and try again. If the
Destination: Log, System Monitor problem persists, stop and restart the signalling
process using the Custom Server Manager menu
option. All other trunks using the signalling
29610 ISDN Layer 2 detected invalid
process are disabled. If this does not solve the
incoming frames
problem shut down and restart WebSphere Voice
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
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.
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
User response: If this error occurs frequently it
Explanation: The ISDN Layer 1 reading process
may indicate a problem with WebSphere Voice
has stopped discarding incoming ISDN Layer 2
Response. Disable and re-enable the trunk on
and 3 signalling messages. Buffers in the pool are
which the error occurred and try again. If the
now available for passing these to Layer 2.
problem persists, stop and restart the signalling
Signalling has been restarted. A loss of some
process using the Custom Server Manager menu
incoming calls or incoming call clearing
option. All other trunks using the signalling
messages may have occurred while the messages
process are disabled by taking this action. If this
were being discarded. If this error occurs
does not solve the problem, shut down and
frequently, the system is running very close to
restart WebSphere Voice Response. If none of the
the limit of the current buffer pool.
above is successful call IBM Support.
User response: If this error occurs frequently it
Severity: Red
may indicate a problem with WebSphere Voice
Destination: Log, System Monitor Response. Disable and re-enable the trunk on
which the error occurred and try again. If the
problem persists, stop and restart the signalling
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.
may indicate a problem with WebSphere Voice
Explanation: The buffer pool used for
Response. Disable and re-enable the trunk on
processing calls is almost exhausted. New
which the error occurred and try again. If the
incoming calls will be released until there are
problem persists, stop and restart the signalling
VoIP
User response: Report this error to your IBM
29800 VoIP Media (UPA) Internal
development support
Failure
Severity: Yellow
Explanation: An unexpected error occurred in
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
Explanation: An unexpected error occurred in
Severity: Red the VoIP SIP signalling process. This is a hard
failure and the media process has halted.
Destination: Log, System Monitor
Detailed information about the error is logged.
User response: Report this error to your IBM
29801 VoIP Media (UPA) Internal
development support
Warning
Severity: Red
Explanation: An unexpected error occurred in
the VoIP Media process. This is a warning only. Destination: Log, System Monitor
Detailed information about the error is logged.
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
Destination: Log, System Monitor
only. Detailed information about the error is
logged.
29802 VoIP H323 signalling process
User response: Report this error to your IBM
Internal Failure
development support
Explanation: An unexpected error occurred in
Severity: Yellow
the VoIP H323 signalling process. This is a hard
failure and the media process has halted. Destination: Log, System Monitor
Detailed information about the error is logged.
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.
Destination: Log, System Monitor
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
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
above is successful call IBM Support.
Destination: Log, System Monitor
Severity: Yellow
Destination: Log, System Monitor
29807 VOIP signalling process channel
state machine error
29809 VOIP signalling process
Explanation: An unexpected error occurred in
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
WebSphere Voice Response. If none of the above
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
Explanation: An unexpected error occurred in
problem with WebSphere Voice Response. Stop
the VOIP signalling process trunk state machine.
and restart the signalling process using the
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.
User response: Check the error log for other
Severity: Yellow
errors within the VOIP signalling process, which
may identify the origin of the error. If this error Destination: Log, System Monitor
occurs frequently it may indicate a problem with
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.
may indicate a problem with WebSphere Voice
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
restartWebSphere Voice Response . If none of the
Severity: Yellow above is successful call IBM Support.
Destination: Log, System Monitor Severity: Yellow
Destination: Log, System Monitor
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
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
none of the above is successful call IBM Support.
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
Destination: Log, System Monitor
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.
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
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.
Destination: Log, System Monitor
Severity: Yellow
Destination: Log, System Monitor
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
Destination: Log, System Monitor
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
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.
User response: Restart WebSphere Voice
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
Destination: Log, System Monitor
SS7
Destination: Log, System Monitor
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.
Destination: Log, System Monitor, Alertable
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
Destination: Log, System Monitor
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
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
Destination: Log, System Monitor, Alertable Destination: Log, System Monitor, Alertable
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.
Destination: Log, System Monitor, Alertable
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: 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
Explanation: The SS7_D7 custom server has
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.
Destination: Log, System Monitor, Alertable
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.
Destination: Log, System Monitor, Alertable
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.
Destination: Log, System Monitor, Alertable
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
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.
Destination: Log, System Monitor, Alertable
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
Destination: Log, System Monitor, Alertable Destination: Log, System Monitor, Alertable
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
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
Destination: Log, System Monitor, Alertable
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
Explanation: SS7_D7 Custom Server has
Destination: Log, System Monitor, Alertable
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
Destination: Log, System Monitor, Alertable
a couple of messages to correct.
Severity: Green
30112 Block Pending SS7 Error message
Destination: Log, System Monitor, Alertable
Explanation: SS7_D7 Custom Server has
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
Destination: Log, System Monitor, Alertable
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
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.
30211 Machine added to SS7/D7 Cluster
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
Destination: Log, System Monitor
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.
Destination: Log, System Monitor, Alertable
User response: No response if required..
30213 SS7/D7 Stack - Link/LSet Severity: Green
recovered.
Destination: Log, System Monitor
Explanation: This is reporting a recovered
condition with a Link within a LinkSet.
30217 SS7 - Distributed7 Inter Machine
Heartbeat failure
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.
Timeslot Management
Destination: Log, System Monitor
30500 TDM connection management:
connection server error (log-only)
30503 TDM connection management:
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
error. The meaning is defined by the specific
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
Destination: Log, System Monitor
30501 TDM connection management:
connection server error (white)
30504 TDM connection management:
Explanation: A connection server logged an
connection server error (red)
error. The meaning is defined by the specific
connection server. Explanation: A connection server logged an
error. The meaning is defined by the specific
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, System Monitor
Severity: Red
Destination: Log, System Monitor
30502 TDM connection management:
connection server error (green)
30505 TDM connection management
Explanation: A connection server logged an
error
error. The meaning is defined by the specific
connection server. Explanation: An error occurred in TDM
connection management.
User response: Look at the error text for more
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.
the error log entry.
Severity: Yellow
Severity: Green
Destination: Log, System Monitor
Pack Configuration
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
problem persists, call IBM Support.
Explanation: The WebSphere Voice Response
Severity: Red signalling interface has encountered an error on a
poll() system call, and has terminated. This
Destination: Log, System Monitor, Alertable
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.
Explanation: The WebSphere Voice Response
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
Destination: Log, System Monitor
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.
Explanation: The WebSphere Voice Response
Severity: Red signalling interface has received an unexpected
returned event from a poll() system call.
Destination: Log, System Monitor, Alertable
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
User response: If you are not using common does NOT indicate an error inWebSphere Voice
channel signalling or a signalling process, this Response .
error should not occur. If you are using common
Severity: Yellow
channel signalling or a signalling process, this
message is for information only. Destination: Log, System Monitor
Severity: White
32013 Signalling interface: error event
Destination: Log, System Monitor
with no signalling process
Explanation: The WebSphere Voice Response
32011 Signalling interface: signalling
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
User response: If you are not using common
process has terminated.
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 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
the problem persists, call IBM Support.
Severity: White
Severity: Yellow
Destination: Log, System Monitor
Destination: Log, System Monitor
32012 Signalling interface: signalling
process failed to clear call 32014 Signalling interface: device driver
queue for CCS full
Explanation: The WebSphere Voice Response
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
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
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
Explanation: See “SpeechServer custom server.”
server. If the error persists, restart WebSphere
Voice Response. User response: Restart the SpeechServer custom
server. If the error persists, restart WebSphere
Severity: Red (error_id= 20504)
Voice Response.
Destination: Log, System Monitor
Severity: Yellow (error_id = 20502)
Destination: Log, System Monitor
35001 SpeechServer failed to send
request
35004 SpeechServer CA_Get_Parameters
Explanation: See “SpeechServer custom server.”
failed
User response: Restart the SpeechServer custom
Explanation: See “SpeechServer custom server.”
server. If the error persists, restart WebSphere
Voice Response. User response: Restart the SpeechServer custom
server. If the error persists, restart WebSphere
Severity: Yellow (error_id = 20502)
Voice Response.
Destination: Log, System Monitor
Severity: Yellow (error_id = 20502)
Destination: Log, System Monitor
35002 SpeechServer has detected an
unknown error
35005 Reco channel table could not be
Explanation: See “SpeechServer custom server.”
allocated for process
User response: Restart the SpeechServer custom
Explanation: See the introduction to these
server, if the error persists you should restart
messages.
WebSphere Voice Response.
User response: Restart the SpeechServer custom
Severity: White (error_id = 20501)
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.
35013 Process could not add function to 35017 Process failed to open channel
timer queue
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: Red (error_id= 20504)
Severity: White (error_id = 20501)
Destination: Log, System Monitor
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.
Severity: White (error_id = 20501)
Severity: Red (error_id= 20504)
Destination: Log
Destination: Log, System Monitor
35015 Recochannel could not be found
for referenced ID 35019 Packet could 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)
Destination: Log Destination: Log
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
Severity: White (error_id = 20501)
the custom server.
Destination: Log
Severity: Red (error_id= 20504)
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
User response: Restart the SpeechServer custom
problem occurred.
server. If the error persists, restart WebSphere
Voice Response. User response: Check that the voice recognition
units are active.
Severity: White (error_id = 20501)
Severity: Yellow (error_id = 20502)
Destination: Log
Destination: Log, System Monitor
35022 File could not be read
35027 Error occurred in SpeechServer
Explanation: See the introduction to these
statistics collection
messages.
Explanation: See the introduction to these
User response: Restart the SpeechServer custom
messages.
server. If the error persists, restart WebSphere
Voice Response. User response: Restart the SpeechServer custom
server. If the error persists, restart WebSphere
Severity: White (error_id = 20501)
Voice Response.
Destination: Log
Severity: White (error_id = 20501)
Destination: Log
35024 SpeechServer detected unexpected
channel error
35028 Error occurred in reco download
Explanation: See the introduction to these
process
messages.
Explanation: See the introduction to these
User response: Restart the SpeechServer custom
messages.
server. If the error persists, restart WebSphere
Voice Response. User response: Restart the SpeechServer custom
server. If the error persists, restart WebSphere
Severity: Yellow (error_id = 20502)
Voice Response.
Destination: Log, System Monitor
Severity: Yellow (error_id = 20502)
Destination: Log, System Monitor
35025 SpeechServer could not acquire
recochannel
35029 SpeechServer detected bad socket
Explanation: See the introduction to these
or file handle
messages.
Explanation: See the introduction to these
User response: Restart the SpeechServer custom
messages.
server. If the error persists, restart WebSphere
Voice Response. User response: Restart the SpeechServer custom
server. If the error persists, restart WebSphere
Severity: Red (error_id= 20504)
Voice Response.
Destination: Log, System Monitor
Severity: White (error_id = 20501)
User response: Restart the SpeechServer custom Destination: Log, System Monitor
server. If the error persists, restart WebSphere
Voice Response. 35061 Connection to remote port
Severity: White (error_id = 20501) unexpectedly closed
With any of these errors, if you have followed the suggestions in the User
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.
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
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
Configuring the System.
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.
Destination: Log, System Monitor
User response: Record the return code and the
configuration parameters and see CP008.
CP007 Bad argument in command line
Severity: White (error_id = 20501)
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
Explanation: Not issued.
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
Severity: White (error_id = 20501)
Destination: Log, System Monitor CP012 Failed to open message trace file
Explanation: Not issued.
CP008 Cannot connect to signaling User response: Not applicable.
library. Exiting...
Severity: Yellow (error_id = 20502)
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.
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
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.
User response: Check the white errors and resolve the problem contact IBM Support.
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
Destination: Log, System Monitor
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
Severity: White (error_id = 20501)
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.
User response: None.
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
Configuring the System.
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
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
Severity: Red (error_id = 20504)
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
User response: Take a trace of this failure and
contact IBM Support. CP056 CallPath call STLISN
(Identify_Server_Name) failed
Severity: Red (error_id = 20504)
Explanation: STLISN failed during CallPath
Destination: Log, System Monitor
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
Severity: Red (error_id = 20504)
before the custom server will work properly.
Destination: Log, System Monitor
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.
Severity: White (error_id = 20501)
Explanation: The custom server received a
Destination: Log, System Monitor
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
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)
is available, and can be reached by the
Destination: Log, System Monitor
WebSphere Voice Response system. To check that
it is available, from WebSphere Voice Response
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
available before the custom server will work
properly. Explanation: STLINIT failed during CallPath
Server link initialization. This notification is
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
Destination: Log, System Monitor
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
message. The CallPath return code and the
can be reached by the WebSphere Voice Response
parameters passed to and from the call are
system. To check that it is available, from
printed in the error.
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
Check the CallPath return code. This might give
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:
Programmer's Guide and Reference.
“WebSphere Voice Response to CallPath Server
Interface”. Severity: White (error_id = 20501)
User response: Check that the CallPath Server Destination: Log, System Monitor
is available, and can be reached by the
WebSphere Voice Response system. To check that
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
Explanation: STLMONS failed during CallPath return codes, see the : CallPath Server
Server link initialization. This notification is Programmer's Guide and Reference.
normally issued just before a CP053 or CP054
Severity: White (error_id = 20501)
message. The CallPath return code and the
parameters passed to and from the call are Destination: Log, System Monitor
printed in the error.
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.
available before the custom server will work
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
WebSphere Voice Response system. To check that
Severity: White (error_id = 20501) it is available, from WebSphere Voice Response
run ping server_name, and check that you get a
Destination: Log, System Monitor
valid response. The CallPath Server must be
available before the custom server will work
CP064 CallPath call STLSAA properly.
(Set_Automatic_Answer) failed
Check the CallPath return code. This might give
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.
message. The CallPath return code and the
Severity: White (error_id = 20501)
parameters passed to and from the call are
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
User response: Check that the CallPath Server
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.
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.
valid response. The CallPath Server must be
STLDISC drops a transfer request when the
available before the custom server will work
transfer has timed out.
properly.
User response: Check that the CallPath Server
Check the CallPath return code. This might give
is available, and can be reached by the
the reason for the STLSHPB 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
Severity: White (error_id = 20501) valid response. The CallPath Server must be
available before the custom server will work
Destination: Log, System Monitor
properly.
Check the CallPath return code. This might give
CP067 CallPath call STLSRR
the reason for the STLDISC failure. For CallPath
(Set_Return_Response) failed
return codes, see the : CallPath Server
Explanation: STLSRR failed during CallPath Programmer's Guide and Reference.
Server link initialization. This notification is
Severity: White (error_id = 20501)
normally issued just before a CP053 or CP054
message. The CallPath return code and the Destination: Log, System Monitor
parameters passed to and from the call are
printed in the error.
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.
it is available, from WebSphere Voice Response
v There is an invalid parameter in the STLDISC
run ping server_name, and check that you get a
call.
valid response. The CallPath Server must be
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.
return codes, see the : CallPath Server
Programmer's Guide and Reference.
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
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.
Severity: White (error_id = 20501)
Severity: White (error_id = 20501)
Destination: Log, System Monitor
Destination: Log, System Monitor
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.
Severity: White (error_id = 20501)
Destination: Log, System Monitor STLIMMT performs a single step transfer on
switches that support this call.
you are does not exceed that allowed for your Programmer's Guide and Reference.
switch.
Severity: White (error_id = 20501)
For more information see the entry for STLIMMT
Destination: Log, System Monitor
in the CallPath reference guide for your switch.
Severity: White (error_id = 20501)
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.
from the call are printed in the error.
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.
User response: If this problem occurs
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.
Destination: Log, System Monitor
User response: If this problem occurs
frequently, make sure that the CallPath Server
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
is available, and can be reached by the
WebSphere Voice Response system. To check that
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
return codes, see the : CallPath Server
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
User response: If this problem occurs
Programmer's Guide and Reference.
frequently, trace it and contact IBM Support.
Severity: White (error_id = 20501)
Severity: White (error_id = 20501)
Destination: Log, System Monitor
Destination: Log, System Monitor
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
User response: Check that the CallPath Server
the reason for the STLXTND failure. For CallPath Destination: Log, System Monitor
return codes, see the : CallPath Server
Programmer's Guide and Reference.
CP093 CallPath call STLXTND
Severity: White (error_id = 20501) (Extend_Call) - unknown problem
Destination: Log, System Monitor Explanation: STLXTND failed because of an
unexpected or unknown error. The CallPath
return code and the parameters passed to and
CP092 CallPath call STLXTND
from the call are printed in the error.
(Extend_Call) - program problem
STLXTND performs a single step transfer on
Explanation: STLXTND failed for one of the
switches that support this call.
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.
Destination: Log, System Monitor
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.
Severity: White (error_id = 20501)
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
Severity: White (error_id = 20501)
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.
User response: Correct the error and resubmit
the request.
DTJ1013 I/O error reading from
configuration file filename
DTJ1019 Missing ';' in...
Explanation: The command is not able to read
the file. Explanation: All primary keywords must be
delimited by a ';'.
User response: Review the StackTrace on stdout
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
User response: Correct the error and resubmit
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...
User response: Correct the error and resubmit
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...
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
User response: Correct the error and resubmit
the request.
DTJ1030 The following RecoType or TTSType
line in filename contains a locale
DTJ1024 The following NumToApp line
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.
User response: Correct the error and resubmit
User response: Correct the error and resubmit
the request.
the request.
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
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.
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.
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
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
Explanation: The variant field of the locale
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)
Explanation: The variant field of the locale
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.
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
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
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
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
User response: Check the syntax of the
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
User response: Check the syntax of the
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
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
User response: Check the appropriate
problem finding an appropriate speech
WebSphere Voice Response and telephony service
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
User response: Check the appropriate
dtj.home environment variable was not set.
WebSphere Voice Response and telephony service
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
Module: VXML2BrowserLauncher
DTJ7025 AudioService play unable to open
Severity: Error
audio proxy, Exception: exception
Stack trace: trace
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
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
Module: VXML2BrowserLauncher
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
value specified for parameter
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: 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%
value specified for parameter
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
Module: VXML2BrowserLauncher
User response:
Severity: Error
Module: DTGrammarCache
Severity: Information
DTJ7040 IOException while getting FSG:
exception Stack trace: trace
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%
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 .
Module: DTGrammarCache
Severity: Error
With any of these errors, if you have followed the suggestions in the User
Response, and you are unable to solve the problem, contact IBM Support.
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...
Severity: Red (errorid = 20504)
Explanation: The custom server could not fork()
Destination: Log, System Monitor.
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
Destination: Log, System Monitor.
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
Destination: Log, System Monitor.
ISDN_XFER001.
User response: Restart WebSphere Voice
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
Destination: Log, System Monitor.
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
an AIX system trace while re-creating the
Destination: Log, System Monitor. problem. Specify the -d command line parameter
for the custom server.
the other parameters for the failure reason. If this internal message queues is not functioning
does not help, before calling IBM Support, take correctly.
an AIX system trace while re-creating the
User response: Restart the ISDN_Call_Transfer
problem. Specify the -d command line parameter
custom server.
for the custom server.
If the problem persists, take an AIX system trace
Severity: Red (errorid = 20504)
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
User response: Check the CA_errno given in
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.
for the custom server.
If the problem persists, take an AIX system trace
Severity: White (errorid = 20501) while re-creating the problem. Specify the -d
command line parameter for the custom server.
Destination: Log, System Monitor.
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.
User response: Restart the ISDN_Call_Transfer
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.
command line parameter for the custom server.
Then call IBM Support. Severity: Yellow (errorid = 20503)
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
Destination: Log, System Monitor.
AIX system trace while re-creating the problem.
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
Destination: Log, System Monitor.
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
If the problem persists, take an AIX system trace
incoming application before the TransferCall
while re-creating the problem. Specify the -d
action is performed.
command line parameter for the custom server.
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.
Severity: Yellow (errorid = 20503)
If the problem persists, take an AIX system trace
Destination: Log, System Monitor.
while re-creating the problem. Specify the -d
command line parameter for the custom server.
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
Destination: Log, System Monitor.
and the ISDN_Call_Transfer custom server has
not yet received a notification.
ISDN_XFER019 GetUserStatus is not valid at
User response: If the problem persists, take an
this time
AIX system trace while re-creating the problem.
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
Severity: Yellow (errorid = 20503)
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
User response: Check that the state tables
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.
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
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.
With any of these errors, if you have followed the suggestions in the User
Response, restarted the Juke_Box 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.
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
Severity: White (error_id = 20501)
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,
Severity: Yellow (error_id = 20502)
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'.
Severity: White (error_id = 20501)
Explanation: The Juke_Box custom server could
Destination: Log, System Monitor
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.
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
Severity: Yellow (error_id = 20502)
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.
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'.
Severity: Yellow (error_id = 20502)
Explanation: The AIX system call sigaction()
Destination: Log, System Monitor
failed. The Juke_Box custom server was trying to
register a handler for the SIGCHLD event.
JB034 Cannot destroy message queue.
User response: Check rc and errno for the
rc='number' errno='number'
sigaction() call in the AIX documentation.
Explanation: AIX system call msgctl() failed.
Severity: Yellow (error_id = 20502)
User response: Check rc and errno for the
Destination: Log, System Monitor
msgctl() call in the AIX documentation.
Severity: White (error_id = 20501)
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 and errno for the
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)
Destination: Log, System Monitor
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.
Explanation: The Juke_Box custom server could
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
Severity: White (error_id = 20501)
the catalog, but has different parameters
Destination: Log, System Monitor
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
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.
Destination: Log, System Monitor
Severity: White (error_id = 20501)
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.
Severity: White (error_id = 20501)
Severity: White (error_id = 20501)
Destination: Log, System Monitor
Destination: Log, System Monitor
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
Destination: Log, System Monitor
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
Severity: White (error_id = 20501)
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
Severity: White (error_id = 20501)
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
permission to read the file. User response: If this problem persists, call IBM
Support.
Severity: White (error_id = 20501)
Severity: White (error_id = 20501)
Destination: Log, System Monitor
Destination: Log, System Monitor
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
Severity: White (error_id = 20501)
the configuration file, then restart the Juke_Box
custom server. Destination: Log, System Monitor
Severity: White (error_id = 20501)
JB082 State table requested music title
Destination: Log, System Monitor
'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.
Severity: White (error_id = 20501)
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'
Destination: Log, System Monitor
Explanation: The Juke_Box custom server could
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
Explanation: The Juke_Box custom server could
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
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.
User response: If this problem persists, call IBM
Explanation: This flag must be followed by a
Support.
number. This flag has been ignored.
Severity: White (error_id = 20501)
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'
Severity: White (error_id = 20501)
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'
Severity: White (error_id = 20501)
Explanation: The value of this flag must be an
Destination: Log, System Monitor exact multiple of the specified number. The
music player adjusts the value by rounding it Severity: White (error_id = 20501)
down, and uses this value.
Destination: Log, System Monitor
User response: Correct the value in the music
player parameter string either in the
JBS014 CA_Open_Music_Channel()
configuration file, or in the state table when the
failed. rc='number'
music title is dynamically added to the music
CA_errno='number'
catalog. Restart the Juke_Box custom server.
errno='number'
Severity: White (error_id = 20501)
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:
Explanation: This flag must be followed by a
Custom Servers book.
number in the allowed range.
Severity: White (error_id = 20501)
User response: Correct the value in the music
player parameter string, either in the Destination: Log, System Monitor
configuration file, or in the state table when the
music title is dynamically added to the music
JBS016 No flag letters found after '-'
catalog. Restart the Juke_Box custom server.
Explanation: The music player found a dash
Severity: White (error_id = 20501)
character in the parameter string with no flag or
Destination: Log, System Monitor numeric characters following.
User response: Correct the value in the music
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.
Destination: Log, System Monitor
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.
Severity: White (error_id = 20501)
Explanation: This flag must be followed by the
Destination: Log, System Monitor directory name.
User response: Correct the value in the music
JBS012 Cannot allocate 'number' bytes of player parameter string, either in the
voice-buffer configuration file, or in the state table when the
music title is dynamically added to the music
Explanation: The music player used the AIX
catalog. Restart the Juke_Box custom server.
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
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 CA_Get_Segment() failed. User response: Check rc and errno for fopen() in
CA_errno='number' the AIX documentation.
errno='number'.
Severity: White (error_id = 20501)
Explanation: The WebSphere Voice Response
Destination: Log, System Monitor
custom server API function CA_Get_Segment()
failed.
JBE054 Cannot query size of source file
User response: For more information, check
'number' using stat()
CA_errno in the WebSphere Voice Response for AIX:
Custom Servers book. Explanation: The music player used the AIX
system call stat() to find out how big the music
Severity: White (error_id = 20501)
data source file is. The system call failed.
Destination: Log, System Monitor
User response: Check rc and errno for stat() in
the AIX documentation.
JBS048 CA_Get_Segment() failed to read
Severity: White (error_id = 20501)
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.
Destination: Log, System Monitor
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
Severity: White (error_id = 20501)
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.
Severity: White (error_id = 20501)
Explanation: The filename associated with the -f
Destination: Log, System Monitor
flag is missing.
User response: Correct the value in the music Severity: White (error_id = 20501)
player parameter string, either in the
Destination: Log, System Monitor
configuration file, or in the state table when the
music title is dynamically added to the music
catalog. Restart the Juke_Box custom server.
Severity: White (error_id = 20501)
Destination: Log, System Monitor
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.
With any of these errors, if you have followed the suggestions in the User
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
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
Severity: Red (error id = 20504)
to allow sufficient processes per user.
Destination: Log, System Monitor.
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
Severity: Red (error id = 20504)
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
TROMBONE008 Polling for messages failed TROMBONE011 Internal message could not
be received
Explanation: A call to CA_Poll() failed.
Explanation: An internal message could not be
User response: Check the CA_errno given in
received, which probably means that one of the
the other parameters for the failure reason. If this
internal message queues is not functioning
doesn't help, re-create the problem and take an
correctly.
AIX system trace (specify the -d command-line
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
take an AIX system trace (specify the -d
Destination: Log, System Monitor.
command-line parameter for the custom server),
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.
AIX system trace (specify the -d command-line
User response: Re-start
parameter for the custom server), before calling
IBM_Trombone_Custom_Server.
IBM Support.
If the problem persists, re-create the problem and
Severity: White (error id = 20501)
take an AIX system trace (specify the -d
Destination: Log, System Monitor. command-line parameter for the custom server),
before calling IBM Support.
TROMBONE010 Internal message could not Severity: Yellow (error id = 20503)
be sent
Destination: Log, System Monitor.
Explanation: An internal message could not be
sent, which probably means that one of the
TROMBONE013 CA_TDM_Connect() failed
internal message queues is not functioning
correctly. Explanation: A request to connect two TDM
PortSets failed.
User response: Re-start
IBM_Trombone_Custom_Server. User response: Re-create the problem and take
an AIX system trace (specify the -d
If the problem persists, re-create the problem and
command-line parameter for the custom server),
take an AIX system trace (specify the -d
before calling IBM Support.
command-line parameter for the custom server),
before calling IBM Support. Severity: Yellow (error id = 20503)
Severity: Yellow (error id = 20503) Destination: Log, System Monitor.
Destination: Log, System Monitor.
TROMBONE014 CA_TDM_Disconnect() failed
IBMTromboneOut state table for the correct input WebSphere Voice Response has shutdown.
parameters).
User response: If the problem persists and is
Severity: Yellow (error id = 20503) causing operational problems, 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.
TROMBONE025 CA_Close_CHP_Link() failed
Severity: White (errorid = 20501)
Explanation: A call to CA_Close_CHP_Link()
Destination: Log, System Monitor.
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
implementing the trombone are doing this
Destination: Log, System Monitor.
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
AIX system trace (specify the -d command-line
shutdown
parameter for the custom server), before calling
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
Severity: White (errorid = 20501)
Voice Response has shutdown.
Destination: Log, System Monitor.
User response: If the problem persists and is
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
server), before calling IBM Support.
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
Destination: Log, System Monitor.
happen if the default state tables have been
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
User response: Check that the state tables
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
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.
With any of these errors, if you have followed the suggestions in the User
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.
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,
User response: Check that the interrupted
InitSessionString=value.
speech recognition session has now restarted on
Explanation: If a backup server has been the backup server.
configured, this error is logged after message
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
InitSessionString=value.
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
User response: Check that the interrupted
returns something problematic, such as a code
speech recognition session has now restarted on
indicating no free sessions.
the backup server.
User response: If a backup server has been
configured, check that MRCP message 1008060
1008048 Attempting to open new session
has also been issued.
with backup server,
InitSessionString=value.
Explanation: If a backup server has been
configured, this error is logged after message
10080491 when the initial connection to the
speech recognition server cannot be made.
User response: Check that the interrupted
speech recognition session has now restarted on
the backup server.
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.
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.
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: 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.
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 following paragraph does not apply to the United Kingdom or any
other country where such provisions are inconsistent with local law:
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.
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.
Java and all Java-based trademarks and logos are trademarks of Oracle
and/or its affiliates.
UNIX is a registered trademark of The Open Group in the United States and
other countries.
Notices 453
454 Problem Determination
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.
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,
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
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
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
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.
WebSphere Voice Response.
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
A WebSphere Voice Response
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.
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.
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.
Integrated Services Digital 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.
Integrated Services Digital Network
(ISDN) two B-channel transfer IP See intelligent peripheral.
A call transfer feature that is
defined by Bellcore GR-2865-CORE
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.
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
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
WebSphere Voice Response
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
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,
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.
WebSphere Voice Response
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
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
WebSphere Voice Response
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
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
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
Glossary 487
488 Problem Determination
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 .
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 CCITT Blue book (1988) Q.711 - Q.714
v ITU-T White book (1993) Q.711 - Q.714
v CCITT Blue book (1988) Q.721 - Q.724
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 CCITT Blue book (1988) Q.761 - Q.764
v ITU-T White book (1992) Q.761 - Q.764
v CCITT Blue book (1988) Q.771 - Q.775
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
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
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
Y
yellow alarm 90, 111
Index 499
500 Problem Determination
GC34-7087-07