Académique Documents
Professionnel Documents
Culture Documents
Version 5.1.3
Tenth Edition (April 2006) This edition applies to IBM WebSphere Voice Server version 5, release 1.3. This edition applies to all subsequent releases and modifications until otherwise indicated in new editions. A form for readers comments appears at the back of this publication. If the form has been removed, address your comments to: International Business Machines Corporation Department MMOA P.O. Box 12195 Research Triangle Park, North Carolina 27709-2195 When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation 2005, 2006. All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Chapter 1. Product overview . . . . . . 1
Speech in e-business . . . . . . . . . . . Brief introduction to speech . . . . . . . . Product description . . . . . . . . . . . Features . . . . . . . . . . . . . . . Accessibility . . . . . . . . . . . . Administrative ease of use . . . . . . . . Compatibility with IVRs and gateways . . . Continuous access . . . . . . . . . . Scalability . . . . . . . . . . . . . Rapid problem determination . . . . . . . Security . . . . . . . . . . . . . . Product GUIs and tools . . . . . . . . . . Relationship to other versions of WebSphere Voice Server products . . . . . . . . . . . . WebSphere platform and related software . . . About this information . . . . . . . . . Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 2 4 6 6 7 8 8 9 9 9 9 Installing interim fixes and fix packs for the product . . . . . . . . . . . . . . . Installing deployment manager . . . . . . . Installing WebSphere Voice Server console extensions on a deployment manager . . . . . Installing the WebSphere Edge Component: Load Balancer . . . . . . . . . . . . . . Customizing the options response file . . . . Installation: Resources for learning . . . . . Installation tips . . . . . . . . . . . . Using the installation verification test. . . . . . Installation verification test command . . . . firststeps command . . . . . . . . . . . Installing the IBM TTS Connector for Genesys Voice Platform for WebSphere Voice Server . . . . . . Prerequisites for the IBM TTS Connector for Genesys Voice Platform . . . . . . . . . Uninstalling the product . . . . . . . . . . Uninstalling TTS and ASR languages . . . . . Uninstalling Network Deployment . . . . . Uninstalling base WebSphere Application Server Manually uninstalling WebSphere Application Server . . . . . . . . . . . . . . . Uninstalling the IBM TTS Connector for Genesys Voice Platform for WebSphere Voice Server . . . . 79 80 81 82 83 83 83 83 85 85 86 88 88 89 90 90 90 91
11 12 13 15
Chapter 2. Developing . . . . . . . . 17
Standards for developing . . . . . . . . . Understanding VoiceXML . . . . . . . . Developing a speech application . . . . . . Testing grammars . . . . . . . . . . . Tuning speech resources for effective applications Preparing a lexicon of ASR pronunciations . . Canadian French phonetic pronunciation . . German phonetic pronunciation . . . . . Japanese phonetic pronunciation . . . . . Latin American Spanish phonetic pronunciation Simplified Chinese phonetic pronunciation . . UK English phonetic pronunciation . . . . US English phonetic pronunciation . . . . . . . . . . . . . . . 17 17 18 18 19 20 20 22 24 26 27 38 39
Chapter 5. Configuring . . . . . . . . 93
Configuring using the administrative console . . . 93 Configuring ASR settings . . . . . . . . . 93 Configuring TTS settings . . . . . . . . . 94 Configuring using scripting and command line tools 95 Adding a voice server . . . . . . . . . . 96 Removing a voice server . . . . . . . . . 99 Creating custom scripts for configurations . . . 101 Configuration Service MBean . . . . . . . 102 Configuring default and available TTS voices 104 Configuring a MIME map on your customer Web server . . . . . . . . . . . . . . . . 105 Configuration parameters . . . . . . . . . 105 Configuring WebSphere Voice Server to support Genesys . . . . . . . . . . . . . . . 112 Configuring WebSphere Voice Server to support WebSphere Voice Response . . . . . . . . . 112 Configuring the IBM TTS Connector for Genesys Voice Platform for WebSphere Voice Server . . . 113
Chapter 3. Planning . . . . . . . . . 43
Understanding the speech application environment Estimating resources for ASR engines . . . . . Estimating resources for TTS engines . . . . . Estimating resources for a LAN . . . . . . Identifying hardware and software requirements . Compatibility with IVRs and gateways . . . . Single machine topology . . . . . . . . . Multiple machine topology . . . . . . . . Establishing multiple machine environments . . . . . . . . . . 43 47 47 48 48 50 50 53 54
Chapter 4. Installing . . . . . . . . . 57
Installing WebSphere Voice Server . . . . . WebSphere Voice Server package . . . . Installing the product . . . . . . . . . Prerequisites . . . . . . . . . . . Using the LaunchPad to start the installation Installing version 5.1.2 and earlier versions . Installing version 5.1.3 . . . . . . . . Installing silently . . . . . . . . . Installing additional languages . . . . .
Copyright IBM Corp. 2005, 2006
. . . . . . . . .
. . . . . . . . .
57 58 59 60 61 62 68 76 78
iii
Security . . . . . . . . . . . Managing using scripting . . . . . . getParam sample . . . . . . . . putParam sample . . . . . . . . startVoiceServer sample . . . . . . stopVoiceServer sample . . . . . . statusVoiceServer sample . . . . . backupVoiceServerConfig sample . . . restoreVoiceServerConfig sample . . . Automatically restarting server processes . Starting and stopping the IBM HTTP Server
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
125 126 127 128 129 130 131 132 134 135 142
Chapter 7. Tuning
. . . . . . . . . 145
. . . . . . 145 145 146 147 147 148
Tuning your configuration . . . . . . . . Tuning WebSphere Voice Server . . . . . Tuning WebSphere Application Server . . . Tuning AIX . . . . . . . . . . . . Tuning Linux: Red Hat 3.0 and SUSE 8.0 . . Tuning threading on SUSE 8.0 with SP2a . . Tuning Windows Server 2003 Enterprise and Standard editions . . . . . . . . . . Tuning the Cisco gateway . . . . . . .
. 149 . 150
Using IBM Support Assistant . . . . . . . . Troubleshooting by component: What is not working? . . . . . . . . . . . . . . . Installation troubleshooting tips . . . . . . Administration and administrative console troubleshooting tips . . . . . . . . . . Security troubleshooting tips . . . . . . . IBM HTTP Server troubleshooting tips . . . . TTS troubleshooting tips. . . . . . . . . ASR troubleshooting tips . . . . . . . . IBM TTS Connector for Genesys Voice Platform for WebSphere Voice Server troubleshooting tips Gateway communication problems . . . . . voiceTest troubleshooting tips . . . . . . . Troubleshooting by task: What are you trying to do? . . . . . . . . . . . . . . . . . Troubleshooting installation problems . . . . Troubleshooting testing and first time run problems . . . . . . . . . . . . . . Troubleshooting application runtime and management problems . . . . . . . . .
460 460 461 461 462 462 463 467 473 474 474 475 475 476 477
Chapter 9. Resources for learning . . 479 Chapter 10. Notices and trademarks 481
iv
Speech in e-business
Speech technology has come of age, and IBM WebSphere Voice Server draws on more than 30 years of worldwide speech research and technology expertise to bring you state-of-the-art functionality. What does speech offer your e-business? Simply put, speech technology offers customer satisfaction. You have heard the common approach to telephone-based customer service: For x, press 1. For y, press 2. For z, press 3. This clunky form of interaction relies on keypad presses and limited numerical user input, creating a confusing maze of menus and a less-than-satisfactory customer experience. At the same time, using live operators for customer service results in inconsistent service quality and significant expense. Speech technology is the future of e-business because it enables more natural, intuitive, and engaging customer service for less cost. Implementing speech technology means your business is always accessible to your customers. Speech applications often provide return on investment in as few as three to six months. Speech technology means that your customer service representatives can handle the complex service tasks for which they are best equipped, instead of simple, repetitive customer transactions. With speech, simple customer service needs might be handled by technology to promote a more cost-effective customer service strategy in your e-business. In addition, a well-designed speech user interface can improve customer satisfaction and loyalty over Web site self-service by giving your customers the flexibility to receive their service anywhere, anytime from their telephone, the most common personal technology. The numerous benefits of speech technology for e-business include: v Interaction with callers is easier and more natural. v Menus can be eliminated or flattened, for more subtle and intuitive navigation. v Call durations can be minimized, meaning less cost per transaction. v Interaction with customers can occur 24 hours a day, 7 days a week. v Customers interact with your business using their telephone or cellular telephone, resulting in continuous access to the customer base regardless of their location. v Individuals with physical or perceptual disabilities might have greater access to e-business services. v Enterprise branding is extended to a new channel phone-based interaction. v Overall customer service costs are decreased. v Return on investment for speech application development often occurs in as few as three to six months.
v Opportunities for integrating and streamlining business processes arise as speech applications are developed. v New business opportunities can arise using speech technology. These benefits combine to increase customer satisfaction and loyalty, meaning that speech technology is central to effective, efficient e-business on demand.
Lexicon The set of words in a given language or system. A lexicon refers to the set of files that comprise the vocabulary of an application or system. Lexicons are used by the ASR engine to increase its recognition accuracy. See Preparing a lexicon of ASR pronunciations for a sample lexicon.
Product description
IBM WebSphere Voice Server offers a Media Resource Control Protocol (MRCP) server that conforms to draft four of the MRCP version 1 specification definition for speech technology.
ASR support
Automatic speech recognition (ASR) is the technology that matches spoken input to the expected input (grammar) in a speech application. WebSphere Voice Server offers eight languages with significantly improved performance in noisy environments, especially in reducing false barge-ins. These languages include: v Australian English v Canadian French v German v Japanese v Latin American Spanish v Simplified Chinese v U.K. English v U.S. English
TTS support
TTS converts written text into spoken words and often provides the voice of a speech application. WebSphere Voice Server provides improved synthesis and signal processing algorithms. TTS supports: v Speech Synthesis Markup Language (SSML) v SSML lexicons v Persistent lexicons TTS also offers several advanced TTS male and female voices for the following languages: v Australian English (The TTS for Australian English uses the UK English TTS) v Canadian French (one male voice, one female voice)
German (one male voice, one female voice) Japanese (one male voice, one female voice) Latin American Spanish (one male voice, one female voice) Simplified Chinese (one female voice) U.S. English (one male voice, two female voices, two fifth generation female voices) v U.K. English (one male voice, two female voices, one fifth generation female voice) v v v v v Restriction: v TTS supports adult voices only. v Fifth generation voices are smoother and more natural sounding, but also larger. Depending on the capacity of your WebSphere Voice Server, the number of voices that can be loaded might be limited to one fifth generation voice and an additional voice. To install and use the fifth generation voices, install fix pack 1 for WebSphere Voice Server 5.1.3 and then install the fifth generation voices you plan to use. Download the fix pack and voices from the WebSphere Voice Server support site.
MRCP server
The Internet Engineering Task Force (IETF) defines MRCP as a protocol for controlling media service resources, such as a speech recognizer or a speech synthesizer. The following figure shows the relationship of WebSphere Voice Server to a partner platform and the application server.
The WebSphere Voice Server base provides the features of the MRCP server that conform to draft four of the MRCP version 1 specification definition. When you add a language support package, the MRCP server acts as a recognizer, providing a standard interface into the ASR resources. The Concatenative TTS package supports the synthesizer functions defined in the MRCP specifications. When you deploy WebSphere Voice Server, you can install both recognition and synthesis resources on the same physical server, or on separate servers. Scaling of the MRCP server is available using the WebSphere Load Balancer. The Load Balancer enables multiple physical servers to present a single server name to which the MRCP clients can connect.
Features
By leveraging the features and functions that an administrator uses for an application server, WebSphere Voice Server provides administrative ease of use to voice server administrators. For e-businesses, speech allows an alternate means of access to business services and transactions, especially for individuals with disabilities. Using an architectural foundation provided by WebSphere Application Server, IBMs premier product for e-business technology, the WebSphere Voice Server also provides extensive administrative and performance benefits for complex speech technology architectures, including the following.
Accessibility
Accessibility features enable users with physical disabilities, such as restricted mobility or limited vision, to use software products.
IBMWebSphere Voice Server for Multiplatforms is a voice application enabler, which appeals to the major user groups impacted by speech technology system administrators, application developers, and application users. WebSphere Voice Server provides the following accessibility features for each user group: System Administrators v Provides accessible administration and monitoring interfaces for speech technology resources. v Offers text through standard system function calls or through an open application programming interface (API), which supports interaction with assistive technology. v Provides accessible documentation. Telephone Callers (users) v Offers the capability of providing people with visual, manual, and or mobility impairments access to business data and services using auditory user interfaces. v Helps businesses comply with Section 508 of the Americans with Disabilities Act. Application Developers v Provides an accessible development environment for speech applications. The administrative console is the primary interface for interacting with the product. This console displays within a standard Web browser. By using an accessible Web browser, such as Microsoft Internet Explorer, administrators are able to: v Use screen-reader software and a digital speech synthesizer to hear what is displayed on the screen. v Use voice recognition software to enter data and to navigate the user interface. v Operate features by using the keyboard instead of the mouse. You can also configure and administer product features by using standard text editors and scripted or command line interfaces instead of the graphical interfaces provided. When appropriate, the documentation for specific product features contains additional information about the accessibility of the features.
The console is also a centralized configuration tool. Administrators can use the console panel to configure the ASR and TTS engines, preloaded grammars, lexicons, and installed voices. Finally, for administrators who prefer to administer using scripts, WebSphere Voice Server provides several example Jacl scripts to help you quickly learn the skills to produce your own unique administration code.
Continuous access
Your speech applications provide customer service and business transactions, save money, and streamline e-business processes. WebSphere Voice Servers ability to support complex architectures ensures that your business will always be available to your customers. Availability and failover support Avoid a single point of failure and maximize system availability by ensuring that the topology has some degree of process redundancy. High-availability topologies typically involve horizontal scaling across multiple machines. Load balancing capability A Load Balancer server performs intelligent load balancing to determine where to send a TCP/IP request. It can direct client RTSP/MRCP requests to available voice servers, bypassing any that are offline. Another server can back up the Load Balancer server, to eliminate it as a single point of failure. Workload management of voice servers also improves availability and failover support. Failover support distributes client RTSP/MRCP requests to the remaining servers, which ensures continued client access without significant interruptions. Maintainability The ability to update hardware and software is another important consideration for many speech technology infrastructures. WebSphere Voice Server allows you to create multiple Load Balancer cells (horizontal scaling) that can make a system easier to maintain because you can take individual machines offline without interrupting other machines that are running a speech application. Although taking a system offline in a cell can reduce overall throughput, for those applications that must continue running in the event of maintenance, WebSphere Voice Servers flexibility allows you to design your system appropriately. Dynamic cell management Modifying a Voice Server cell deployment without interrupting its operation enhances the manageability and flexibility of the overall system. For instance, administrators can add or remove cell members or nodes, to handle variations in the client load, change server characteristics, propagate changes to its cell members, and temporarily stop servers for maintenance.
Scalability
Adding more machines increases processing power, which is important for rapid exchanges in speech applications. WebSphere Voice Server provides horizontal scalability, adapting readily to a greater or lesser intensity of use, volume, or demand. Horizontal scaling creates additional WebSphere Voice Server processes on multiple physical machines to take advantage of additional processing power. You can use WebSphere Application Server Edge (Load Balancer) with horizontal scaling to provide a single system view of multiple physical machines.
Security
IBM WebSphere Voice Server uses the security infrastructure and mechanisms provided by WebSphere Application Server. WebSphere Application Server allows administrators to protect a server using two security features: Global Security and Java 2 Security. These security features are managed through the Security panel on the administrative console. Important: Java 2 Security cannot be enabled in order for WebSphere Voice Server to function properly. If you need security, enable Global Security in the WebSphere Voice Server administrative console. Do not select the option to enforce Java 2 Security. Before you enable global security read the technote about using Local operating system user registries. For detailed information about the WebSphere approach to security, refer to Welcome to Security in the WebSphere Application Server Information center.
10
moment-in-time monitoring provided by the WebSphere Voice Server administrative console. For more information, see Tivoli Performance Viewer. Voice Trace Analyzer The latest version of WebSphere Voice Toolkit includes the Voice Trace Analyzer, which lets you examine recognition data from a WebSphere Voice Server system only. It can read multiple trace.log files to build a comprehensive overview of your systems recognition performance and improve the awareness of recognition problems.
Red Hat Enterprise Linux WS/ES/AS for Intel 3.0 with Update 1 only (2.4 Kernel) - supported in WebSphere Voice Server versions 5.1.1 and 5.1.2 v SUSE LINUX Enterprise Server 8, powered by United Linux 1.0 (SLES-8) (Intel) with Service Pack 2a or 3 v Windows Server 2003 Enterprise or Standard editions with or without Service Pack 1 v Note: If you are using Service Pack 1, download and apply the WebSphere Voice Server interim fix, IC47845, from the product Support site. Also refer to the WebSphere Voice Server product page to find the current list of platforms supported.
11
12
The following products collaborate to help you achieve business agility by integrating applications and automating business processes: v WebSphere Business Integration This software creates the nimble infrastructure needed to support the business imperatives of your dynamic enterprise. For more information, see http://www.ibm.com/software/integration/. v WebSphere MQ Integrator This software helps you to flexibly connect and integrate their assets within the enterprise and with trading partners. For more information, see http://www.ibm.com/software/integration/.
13
Edition Edition 9
Updates Updates to the following topics: v Installing the product v Installation prerequisites Also updates for Genesys Voice Platform (GVP) and for the support of Windows Server 2003 Service Pack 1.
Edition 8
November 3, 2005
Information center refreshed with updates for the support of AIX and the installation of multiple languages on one machine. Information center refreshed with updates for the support of the latest releases of WebSphere Voice Response and WebSphere Voice Toolkit. Information center refreshed with Eclipse framework. Updates to the following topics: v Planning v Installing the product v Configuring v Tuning your configuration v Troubleshooting
Edition 7
Edition 6
May 5, 2005
Edition 5
Updates to the following topics: v Planning v Installing the product v Installation prerequisites v Developing v Configuring v Tuning your configuration v Troubleshooting
Edition 4
Updates to the following topics: v Installing the product v Installation prerequisites v Tuning your configuration v Message IDs
14
Edition Edition 3
Updates New topics including: v Phonetic pronunciation tables for German and Canadian French languages. Updates to the following topics: v Tuning your configuration v TTS troubleshooting tips
Edition 2
November 5, 2004
New topics including: v Compatibility with IVRs and gateways v Installing interim fixes, cumulative fixes, and fix packs v Installing the IBM TTS Connector for Genesys Voice Platform for WebSphere Voice Server v Uninstalling the IBM TTS Connector for Genesys Voice Platform for WebSphere Voice Server v Configuring WebSphere Voice Server to support Genesys v Configuring the IBM TTS Connector for Genesys Voice Platform for WebSphere Voice Server v IBM TTS Connector for Genesys Voice Platform for WebSphere Voice Server troubleshooting tips Updates to the following topics: v Installing the product v Installation prerequisites v Tuning your configuration v Message IDs
Edition 1
Initial information center that was included on the WebSphere Voice Server Version 5.1 product CDs.
Conventions
The guide uses several typeface conventions for special terms and actions. These conventions have the following meanings.
15
Bold
Lowercase and mixed-case commands, command options, and flags that appear within text appear like this, in bold. Graphical user interface elements, except for titles of windows and dialogs and names of keys also appear like this, in bold. Variables, values you must provide, new terms, and words and phrases that are emphasized appear like this, in italic type. Commands, command options, and flags that appear on a separate line, code examples, output, and message text appear like this, in monospace type. Names of files and directories, text strings you must type, when they appear within text, names of Java methods and classes, and HTML and XML tags also appear like this, in monospace type. Information marked with this icon applies to WebSphere Voice Server version 5.1 Information marked with this icon applies to WebSphere Voice Server version 5.1 and subsequent versions. Information marked with this icon applies to WebSphere Voice Server version 5.1.1. Information marked with this icon applies to WebSphere Voice Server version 5.1.1 and subsequent versions. Information marked with this icon applies to WebSphere Voice Server version 5.1.2. Information marked with this icon applies to WebSphere Voice Server version 5.1.2 and subsequent versions. Information marked with this icon applies to WebSphere Voice Server version 5.1.3.
Italic Monospace
The following variables are used in this documentation: $WVS_ROOT is a variable for Linux and AIX that is defined during the installation of WebSphere Voice Server. Typing echo $WVS_ROOT at a command prompt shows you the path where WebSphere Voice Server is installed, such as . /opt/WebSphere/VoiceServer on Linux or . /usr/WebSphere/VoiceServer on AIX. %WVS_ROOT% is a Windows variable defined during the installation of WebSphere Voice Server. Typing echo %WVS_ROOT% at a command prompt shows you the path where WebSphere Voice Server is installed, such as C:\Program files\WebSphere\VoiceServer. WAS_ROOT is a variable representing the installation path of WebSphere Application Server. For reference, the WebSphere Voice Server default installation paths are the following: /usr/WebSphere/VoiceServer /opt/WebSphere/VoiceServer C:\Program Files\WebSphere\VoiceServer
16
Chapter 2. Developing
This document concentrates on tasks associated with WebSphere Voice Server product usage and administration. There are many sources of excellent information on developing speech user interfaces and applications. The speech development environment provided with WebSphere Voice Server is the WebSphere Voice Toolkit, which can help streamline application design activities. Although application development activities are typically not performed by the same professionals as voice server administration, use the sections below for an overview of the tasks involved in developing.
Understanding VoiceXML
WebSphere Voice Server is a Media Resource Control Protocol (MRCP) version 1 draft 4 server. Thus, Voice Extensible Markup Language (VoiceXML) browsers that support the MRCP version 1 draft 4 standard can be used with WebSphere Voice Server. A VoiceXML browser is part of a comprehensive speech solution provided with the gateway. VoiceXML is the industry-standard markup language for interactive speech applications. With VoiceXML, you can use a Web-centric programming model and a markup language specially designed to bring the speed and flexibility of Web-based development and content delivery to interactive speech applications. In other words, development skills in HTML transfer to VoiceXML, improving the time to code speech applications. VoiceXML dialogs provide a flexible presentation layer on top of the logic and data layers of your business applications. Using VoiceXML, you can build sophisticated dialogs that enable the caller to use either speech or key-presses to provide input, and to hear responses as either synthesized or prerecorded speech. The speech
17
input from callers can be either recognized or recorded. VoiceXML enables you to build usable and flexible voice interfaces to your business. In addition to accessing your business data, VoiceXML applications can also access telephony information such as called and calling number and perform simple call transfers. The recommended approach is to develop dialogs using VoiceXML in the complete solution. This can include host data accessed through Enterprise JavaBeans (EJBs) and JavaServer programs (JSPs).
Testing grammars
When developing a speech application, you must also test your grammars. WebSphere Voice Server provides two different tools to test grammars the WebSphere Voice Toolkit and the voiceTest tool. The Voice Toolkit provides three GUI utilities for testing: v A grammar test tool that interfaces with a remote WebSphere Voice Server v Pronunciation migration tools for the new lexicon file format v Lexicon file support for custom pronunciations
18
The command-line tool, voiceTest, also allows you to create a lexicon file using the -lexicon tag when defining a grammar. Both the Voice Toolkit and the voiceTest tool allow you to build lexicon files that can improve grammars. To get the command line parameter information for voiceTest, issue the following: Note: Where the WVS_ROOT variable is listed, substitute the complete path for the installation directory.
cd /$WVS_ROOT/lib ./voiceTest.sh
cd /$WVS_ROOT/lib ./voiceTest.sh
cd %WVS_ROOT%\lib voiceTest.bat
For more information on the tools provided in WebSphere Voice Toolkit, see the WebSphere Voice Toolkit Information Center.
Chapter 2. Developing
19
For the TTS languages, use the Symbolic Phonetic Representation (SPR) tables listed in Using IBM Text-to-Speech Technology and Speech Synthesis Markup Language. This guide is also provided as a related document with the WebSphere Voice Toolkit Information Center. WebSphere Voice Server run-time pronunciation errors are sometimes caused by the stress placed on the vowel sounds. If you experience pronunciation errors on certain words, modify the baseforms, to improve ASR. See Preparing a lexicon of ASR pronunciations for instructions on how to do this. Use the tables in this section to assist you in correcting baseform phonetic sounds.
The name of the pronunciation lexicon document must be declared in the grammar source document. See Speech Recognition Grammar Specification (SRGS) 1.0 http://www.w3.org/TR/speech-grammar/ See Tuning speech resources for effective applications for details of the character symbols used to specify phonetic pronunciations and the sounds they represent in each supported language.
20
Table 1. Guide to the Canadian French phonetic alphabet Symbol | (pipe symbol) X D$ _B. _CH _D. _DF _F. _G. _H. _JJ _K. _L. _M. _N. _NG _P. _R. _RR _S. _SH _T. _T2 _TH _V. _W. _Y. _YU _Z. _Z1 _ZH A_N A_S A6S Description Word Boundary Phone The silence phone at the end of each word. The silence phone at the beginning and end of a sentence. b as in bois ch as in the English word church d as in doigt th as in the English word this f as in foire g as in gateau h as in the English word house g as in the English word page c as in coin l as in loin m as in mer n as in neuf ng as in the English word song p as in poids or p as in the English word map English r as in three French r as in noir s as in signe or s as in the English word sun ch as in chien or sh as in the English word shade t as in trois tt as in Ottowa th as in the English word thick v as in vigne or v as in the English word vote o as in loin or w as in the English word wet i as in tiers or y as in the English word you u as in huit z as in zro tz as in Fitzgerald j as in jouet or s as in the English word pleasure an as in sans a as in repas er as in the English word water
Chapter 2. Developing
21
Table 1. Guide to the Canadian French phonetic alphabet (continued) Symbol AAL AES AVS AWD AXS AYD E_A E_N E_S E3L E9S EAA EUN EUS EYD I_L I_S ILS O_A O_N O_S OAA OAL OWD OYD U_L U_S ULS Y_S Description a as in the English word star a as in the English word back u as in the English word plum ou as in the English word out e as in ceci or e as in the English word novel i as in the English word five e as in pied, in final syllables only in as in cinq as in tude, in all non-final syllables or as in the English word word eu as in neuf e as in sept or e as in the English word devil un as in un eu as in deux ei as in the English word eight ea as in the English word sea i as in ici or i as in the English word traffic i as in sinn or i as in the English word zip o as in mot, in final syllables only on as in donc o as in roman, in all non-final syllables o as in sol, in final syllables only a as in the English word wall o as in the English word old oi as in the English word oil o as in the English word who ou as in cours u as in the English word push u as in mur
22
Table 2. Guide to the German phonetic alphabet (continued) Symbol AXS A_N A_S A_S A_S EAS EAS EAS EUS EUS EUS E_S E_S E_S I_S I_S I_S O_N O_S O_S O_S U_S U_S U_S Y_S Y_S Y_S A_S U_S A_S I_S O_S I_S _?? _B. _C2 _CH _D. _F. _G. _H. _JJ Description obligatorisches Schwa nasaliertes a (kurz oder lang) kurzes a langes a kurzes offenes langes offenes kurzes offenes oder geschlossenes langes geschlossenes kurzes geschlossenes e langes geschlossenes e kurzes geschlossenes i langes geschlossenes i nasaliertes o kurzes offenes geschlossenes oder unsilbisches o langes geschlossenes o kurzes geschlossenes oder unsilbisches u langes geschlossenes u kurzes offenes geschlossenes oder unsilbisches langes geschlossenes au-Diphthong ei-Diphthong eu-Diphthong silbeninitialer Knacklaut b-Laut (bilabialer Plosiv stimmhaft) ich-Laut (palataler Reibelaut stimmlos) tsch-Laut (postalveolare Affrikate stimmlos) d-Laut (alveolarer Plosiv stimmhaft) f-Laut (labiodentaler Reibelaut stimmlos) g-Laut (velarer Plosiv stimmhaft) h-Laut (glottaler Reibelaut stimmlos) dsch-Laut (postalveolare Affrikate stimmhaft) As in sieb_e_n, sein_e_ or_an_ge, Ch_an_son h_a_t, _a_cht W_ah_l, B_a_d h__tte, _E_nde Ger__t, __ra V__lker, __ffnung b__se, sch__n M_e_thode, _e_gal z_eh_n, S_ee_ m_i_t, _i_n v_ie_l, Part_ie_ Sais_on,_ Pavill_on_ v_o_n, _o_ft l_o_s, B_oo_t B_u_s, _u_nd F_u_, g_u_t K__ste, B__ro m__de, gr__n _au_s, k_au_m m_ei_n, M_ai_ L_eu_te, M_u_se __aber, zu__erst _B_all, a_b_er ni_ch_t, Re_ch_t deu_tsch,_ Lan_dsch_aft _D_atum, Pa_dd_el _f_allen, A_ff_e _g_enau, Re_g_en _H_aus, Be_h_lter _Dsch_ungel, Mana_g_er
Chapter 2. Developing
23
Table 2. Guide to the German phonetic alphabet (continued) Symbol _K. _KH _KS _L. _M. _N. _NG _P. _PF _R. _S. _SH _T. _V. _Y. _Z. _Z1 Description As in
k-Laut (velarer Plosiv stimmlos) _K_ost, La_ck_ ach-Laut (velarer Reibelaut stimmlos) ks-Laut (alveolare Affrikate stimmlos) l-Laut (alveolarer Lateral) m-Laut (bilabialer Nasal) n-Laut (alveolarer Nasal) ng-Laut (velarer Nasal) p-Laut (bilabialer Plosiv stimmlos) pf-Laut (labiodentale Affrikate stimmlos) r-Laut (Vibrant) s-Laut (alveolarer Reibelaut stimmlos) sch-Laut (postalveolarer Reibelaut stimmlos) t-Laut (alveolarer Plosiv stimmlos) Bu_ch_, do_ch_ e_x_trem, Pra_x_is _L_and, vo_ll_ _M_onat, i_mm_er _N_atur, Ha_n_d la_ng_, E_ng_e _P_ost, Schu_pp_en Ko_pf_, _Pf_anne _r_und, P_r_eis ein_s_, Wa_ss_er fal_sch,_ _S_port _T_ag, Zei_t_
w-Laut (labiodentaler Reibelaut _V_ase, _W_etter stimmhaft) j-Laut (palataler Reibelaut stimmhaft)/unsilbisches i s-Laut (alveolarer Reibelaut stimmhaft) tz-Laut (alveolare Affrikate stimmlos) _j_a, Reg_i_on ro_s_a, _s_o _z_ehn, Ka_tz_e
24
Table 3. Guide to the Japanese phonetic alphabet (continued) Symbol Qp Qpy Qs Qsh Qt Qts Qz _n a a: b by ch d dy e e: f g gy h hy i i: j k ky m my n ny o o: p py r ry s sh t Description sokuon+p sokuon+py sokuon+s sokuon+sh sokuon+t sokuon+ts sokuon+z hatsuon vowel long vowel ba gyou youon cha gyou da gyou dya gyou vowel long vowel fa gyou ga gyou gya gyou ha gyou hya gyou vowel long vowel ji ka gyou kya gyou nasal m mya gyou nasal n nya gyou vowel long vowel pa gyou pya gyou ra gyou rya gyou sa gyou sha gyou ta gyou
Chapter 2. Developing
25
Table 3. Guide to the Japanese phonetic alphabet (continued) Symbol ts u u: w y z Description tsu vowel long vowel wa youon za gyou
26
Table 4. Guide to the Latin American Spanish phonetic alphabet (continued) Symbol LL MH NF NG NH NO OA OO OS PH RH RO RR SH SO TH UO US WH ZH ZS Description billete mar infame cinco nueve con lograr voto voto peso oro mar tierra reloj signo mes tres lugar muro cuatro cinco mismo
BI
bi as in
BU
bu as in
Chapter 2. Developing
27
Table 5. Guide to the Simplified Chinese phonetic alphabet (continued) Symbol C Description c as in
CU
cu as in
CH
ch as in
CHU
chu as in
d as in
DI
di as in
DU
du as in
f as in
g as in
GS
GU
gu as in
h as in
HU
hu as in
JI
ji as in
JU
ju as in
k as in
28
Table 5. Guide to the Simplified Chinese phonetic alphabet (continued) Symbol KU Description ku as in
l as in
LI
li as in
LU
lu as in
LYU
l as in
m as in
MI
mi as in
MU
mu as in
n as in
NI
ni as in
NU
nu as in
NYU
n as in
p as in
PI
pi as in
QI
qi as in
QU
qu as in
Chapter 2. Developing
29
Table 5. Guide to the Simplified Chinese phonetic alphabet (continued) Symbol R Description r as in
RU
ru as in
s as in
SU
su as in
SH
sh as in
SHU
shu as in
t as in
TI
ti as in
TU
tu as in
w as in
XI
xi as in
XU
xu as in
y as in
YU
yu as in
z as in
ZU
zu as in
30
Table 5. Guide to the Simplified Chinese phonetic alphabet (continued) Symbol ZH Description zh as in
ZHU
zhu as in
A1
a1 as in
A2
a2 as in
A3
a3 as in
A4
a4 as in
A5
a5 as in
AI1
ai1 as in
AI2
ai2 as in
AI3
ai3 as in
AI4
ai4 as in
AI5
AN2
an2 as in
AN3
an3 as in
AN4
an4 as in
Chapter 2. Developing
31
Table 5. Guide to the Simplified Chinese phonetic alphabet (continued) Symbol AN5 Description an5 as the last vowel in
AG2
ag2 as in
AG3
ag3 as in
AG4
ag4 as in
AG5
AO2
ao2 as in
AO3
ao3 as in
AO4
ao4 as in
AO5
ao5 as in
no tone. E1 e1 as in
E2
e2 as in
E3
e3 as in
E4
e4 as in
32
Table 5. Guide to the Simplified Chinese phonetic alphabet (continued) Symbol E5 Description e5 as in
EI2
ei2 as in
EI3
ei3 as in
EI4
ei4 as in
EI5
ei5 as in
EN2
en2 as in
EN3
en3 as in
EN4
en4 as in
EN5
en5 as in
EG2
eg2 as in
EG3
eg3 as in
EG4
eg4 as in
Chapter 2. Developing
33
Table 5. Guide to the Simplified Chinese phonetic alphabet (continued) Symbol EG5 Description eg5 as in
ER3
er3 as in
ER4
er4 as in
ER5
no tone. I1 i1 as in
I2
i2 as in
I3
i3 as in
I4
i4 as in
I5
i5 as in
IE2
ie2 as in
IE3
ie3 as in
IE4
ie4 as in
34
Table 5. Guide to the Simplified Chinese phonetic alphabet (continued) Symbol IE5 Description ie5 as in
IH2
ih2 as in
IH3
ih3 as in
IH4
ih4 as in
IH5
IN2
in2 as in
IN3
in3 as in
IN4
in4 as in
IN5
IG2
ig2 as in
IG3
ig3 as in
IG4
ig4 as in
Chapter 2. Developing
35
Table 5. Guide to the Simplified Chinese phonetic alphabet (continued) Symbol IG5 Description ig5 as the last vowel in
no tone. O1 o1 as in
O2
o2 as in
O3
o3 as in
O4
o4 as in
O5
o5 as in
OG2
og2 as in
OG3
og3 as in
OG4
og4 as in
OG5
OU2
ou2 as in
OU3
ou3 as in
OU4
ou4 as in
36
Table 5. Guide to the Simplified Chinese phonetic alphabet (continued) Symbol OU5 Description ou5 as in
no tone. U1 u1 as in
U2
u2 as in
U3
u3 as in
U4
u4 as in
U5
UN2
un2 as in
UN3
un3 as in
UN4
un4 as in
UN5
YU2
yu2 as in
YU3
yu3 as in
YU4
yu4 as in
Chapter 2. Developing
37
Table 5. Guide to the Simplified Chinese phonetic alphabet (continued) Symbol YU5 Description yu5 as he last vowel in
no tone.
38
Table 6. Guide to the UK English phonetic alphabet (continued) Symbol OAS ILS _P. _R. _S. _SH _T. _TH ULS U_S U_S _V. _W. X _Y. _Z. _ZH Description As in OIl avOId toy As in Park suPPle gaP As in Right fRom thRee As in Sit miSt maSS As in SHarp naTIonal fiSH As in To aTTend paT As in Thing auThor paTH As in gOOd shOUld pUt As in OOze bOOt whO As in Very oVer saVe As in White Was tWenty Silence, such as a pause As in Yet Use bEAUty As in Zip siZe waS As in treaSure uSually viSion
uh
AH
One come
Uh or double the Very rarely wrong; following letter sometimes an unstressed sound is used instead. So spell Merom as Meromm. or Very rarely wrong. Try spelling Audi as Ordi. If ow is mispronounced as oh try switching to au or ou. The unstressed eh sound as in moment or enable but not as in enter.
Short o
AO
au
AW
Ou au ow
eh
AX
enable moment
eh
Chapter 2. Developing
39
Table 7. Guide to the US English phonetic alphabet: vowels (continued) Sound er Symbol AXR As in Suggested Comments The unstressed er sound as in another over or or but not as in her . Rare but if Byron is mispronounced more like Birron then try spelling it as Bairon or Byeron or even Byre-on. Rare but replacing the vowel letter or letters by eh usually works. For example if pleasant were mispronounced as pleesant then plehsant corrects it. Never observed but er should work. If Wacome is mispronounced Wah-come then one of Waicome Waycome or Weycome should fix. The short I sound as in it if or pick but not as in lasting. Piro should be pronounced with a short I and is mispronounced as pyro then pihro should work. The unstressed short i sound as in discuss budgeted decided or saving. If Matrio was mispronounced as mah-try-oh then matreeo matreeoh or mahtreeoh should fix. bow should be right for Beau and Dohl should work for Dole. The long i sound (or oi sound) as in avoid employ dive or why.
another over er or
Long i
AY
Y ai add an e
eh
EH
Enter pleasant
eh
er
ER
er
Long a
EY
Ai ay ey
Short i
IH
If it pick
ih
ix
IX
ix
Long e
IY
Ee ey ie
Long o
OW
Quote open go
Oh ow oe
oi
OY
40
Table 7. Guide to the US English phonetic alphabet: vowels (continued) Sound Short u Symbol UH As in Good full could put Suggested uh Comments The short u sound as in good put full or could. If Clough should be pronounced as in cluf then cluhf should work. The stressed long u sound as in to use you or view. Try Bloomehn for the German pronunciation of Blumen.
Long u
UW
Oo yoo
Usually nonvowel sounds are not a problem for the Run Time baseform engine unless the name is of foreign extraction, as in the British pronunciation of Schedule (Schxhule). The table below lists the consonant sounds if you need to select a different sound than that produced by the automatic pronunciation rules.
Table 8. Guide to the US English phonetic alphabet: consonants Sound b bd ch As in be able sob tab blurb cheap child Comments The b sound as in be or able. The hard b sound at the end of a word. The soft c sound before h. The ch sound as in cheap. The D sound as in David or and. The D sound at the end of a word. the either The voiced th sound as in the or either but NOT as in thesis or thing. The very short T or D sound as in butter greater reagarding or order. A dummy sound that marks the beginning and end of a sentence. father rough again peg log tug here who jeep roger because dark scale The soft f sound. The hard g sound. The G sound at the end of a word. The h sound. The soft g sound. The k sound but not the J sound at the beginning of a word. The k sound at the end of a word. The L sound.
Chapter 2. Developing
d dd dh
and David
dx
d$
f g gd hh jh k
kd L
41
Table 8. Guide to the US English phonetic alphabet: consonants (continued) Sound m n As in am must final not none Comments The m sound. The starting N or the unaccented N in the middle of a word as in final not or none. The n followed by a g or k sound. The p sound but not at the beginning of a word. The p sound at the end of a word. The r sound followed by a vowel sound in the same syllable. The s not followed by an h sound. The sh sound. The t (not th) sound not at the beginning of a word. The t sound at the end of word. The unvoiced th sound but NOT as in the or either. The ts sound at the end of a word. eleven improve very frequent way question anywhere emulate yes senior you pans goes zero Asia pleasure Zho The v sound. The w sound. The y sound that leads into a vowel. The z sound. The soft z sound.
ng p
pd r
s sh t
td th
ts v w y z zh
42
Chapter 3. Planning
This section explains what you need to consider when you plan a speech system using WebSphere Voice Server. The requirements of the voice server system will vary depending on the following issues: v The number of telephone lines or channels supported v v v v The call characteristics The speech application characteristics The language/voice installed The size and complexity of the grammars used (automatic speech recognition (ASR) only)
Planning your WebSphere Voice Server system involves the following steps: 1. Understanding the speech application. 2. Estimating speech resources for ASR and text-to-speech (TTS) engines. 3. Estimating resources for a LAN. 4. Identifying hardware and software requirements. 5. Creating a system topology: Single machine or multiple machines.
Application load
To estimate the application load on the system, you need to know the following: v The number of telephony channels required to handle the number of calls you expect for applications using WebSphere Voice Server technology. You must consider how long on average each caller is expected to wait before being answered.
43
v The call frequency and distribution whether the number of calls likely to be made is the same throughout the day, or if the call pattern is likely to vary significantly, with peaks and troughs in demand. Your WebSphere Voice Server system should be able to handle the maximum demand for speech resources. That is, the resources needed at the peak calling hour rather than a days average number of hourly calls. The primary speech resource is the ASR or TTS engine. The demand for engines is influenced by both the frequency of calls and how they are distributed. If all the incoming calls use the same application and start at the same time, each call will need an engine at the same time so the demand will be high. If, on the other hand, calls are distributed normally, the number of engines needed simultaneously can be considerably smaller. For your applications, you must determine the acceptable performance or desirability of an engine being available for a call without a significant delay. Delays can cause performance degradation, such as not recognizing speech input or stuttering output. If a degradation of performance is acceptable during peak utilization, fewer engines will be required. v The time that engines are allocated, or assigned, as a proportion of a call. This is known as the allocation duty cycle. ASR and TTS engines are dynamically allocated on an as needed basis, which means they are allocated to perform a single operation (recognition or synthesis) and then immediately freed. v The time that engines are active (recognizing speech or synthesizing text to be played) as a proportion of a call. This is known as the active duty cycle. This can vary considerably, depending on the design of your voice applications and their complexity. These factors determine the number of concurrent ASR and TTS sessions that are required. The number of concurrent ASR and TTS sessions, in turn, determines the number of processors required and how powerful they must be. Similarly, these two variables number and speed of the processors dictate the number and size of the machines needed for your WebSphere Voice Server installation. For example, a non-barge-in application using long prompts of synthesized text together with a simple grammar is likely to be actively engaged in recognition for only a short proportion of the length of a call. It will have a short active duty cycle for ASR but a long active duty cycle for speech synthesis. A barge-in application using shorter prompts of synthesized text together with a complex grammar is likely to spend more time actively engaged in recognition. In this case, the active duty cycle for ASR will be longer and the active duty cycles for speech synthesis shorter. If a system is underspecified, an engine might not be available at the start of a call. The following figures show a comparison of ASR and TTS engine allocation. In this figure, a barge-in application is being used.
44
Figure 2. ASR and TTS engine allocation comparison (speech recognition with barge-in)
Chapter 3. Planning
45
Figure 3. ASR and TTS engine allocation comparison (speech recognition without barge-in)
Application design
Some applications can be designed so that most callers are likely to complete their business and hang up quickly, thus freeing resources for another call. For more information about application design, refer to the WebSphere Voice Toolkit Information Center.
System resource
Once you know the maximum number of concurrent sessions required for ASR and TTS, the recognition languages and voices to be used, and the complexity of your voice recognition applications, you can determine how many WebSphere Voice Server machines are necessary. You can also determine the minimum specifications for the machines, which are also dependent on the operating system you select. Remember: WebSphere Voice Server must run on its own machine. A minimum base memory of 2 GB is required on each WebSphere Voice Server recognition server machine. You can minimize the number of machines required by installing multiple high-speed processors and additional memory in each machine. The actual number of WebSphere Voice Server engines that will run on each machine is solution-dependent. A solution must be tested to verify that a system can handle a condition where all of the WebSphere Voice Server engines are fully utilized. It also is important to ensure that the qualified compatible gateway system can support all of the attached server machines and engines.
46
Related information Estimating resources for ASR engines Use this section to understand the resources required for automatic speech recognition (ASR) engines. Estimating resources for TTS engines Use this section to understand the resources required for text-to-speech (TTS) engines.
47
v The size of the cache (default is 20 MB) Note: The fifth generation voices require more memory and CPU than the other voices. Depending on the capacity of your WebSphere Voice Server, you might need to do the following when using these voices: v Reduce the number of channels supported v Increase the memory or CPU During initialization of WebSphere Voice Server, all available voices for the installed languages are loaded into a shared memory for use by any TTS engine. The voices remain in memory until the WebSphere Voice Server is stopped. In addition, an output cache is created in shared memory to hold recently synthesized phrases. The use of an output cache can improve synthesis processing, depending on the design of the application and whether the same phrase is used repeatedly. Also refer to Configuring default and available TTS voices on page 104 and TTS troubleshooting tips on page 463 for tips on optimizing the performance of your WebSphere Voice Server.
48
Additionally for AIX, make sure you provide adequate disk space for the following directories: v 450 MB for the /usr/WebSphere/AppServer directory The installation root directory includes the base WebSphere Application Server product code. v 600 MB for the /tmp directory The temporary directory is the working directory for the installation program. v 20 MB for the /usr/IBMHttpServer directory The IBM HTTP Server requires this space. v 35 MB for the /usr/IBM/gsk7 directory The Tivoli Global Security Kit requires this space.
Table 10. Text-to-speech (TTS) server disk space requirements by voice Language WebSphere Voice Server Male French Canadian German Japanese Latin American Spanish Simplified Chinese UK English US English 177 MB 287 MB 63 MB 184 MB Female/2nd 292 MB 339 MB 322 MB 349 MB Fifth generation
628 MB 265 MB 317/321 MB Kate - 1.3 GB (600 MB RAM) Julie - 1.6 GB (600 MB RAM) Lisa - 1.5 GB (600 MB RAM)
Software requirements
WebSphere Voice Server supports the following operating systems: v v AIX 5L version 5.3 with maintenance level (ML) 3 Red Hat Enterprise Linux WS/ES/AS for Intel 3.0 with Update 1, Update 3, or Update 4 (2.4 Kernel) - supported in WebSphere Voice Server version 5.1.3
Red Hat Enterprise Linux WS/ES/AS for Intel 3.0 with Update 1 only (2.4 Kernel) - supported in WebSphere Voice Server versions 5.1.1 and 5.1.2 v SUSE LINUX Enterprise Server 8, powered by United Linux 1.0 (SLES-8) (Intel) with Service Pack 2a or 3 v v Windows Server 2003 Enterprise or Standard editions with or without Service Pack 1 Note: If you are using Service Pack 1, download and apply the WebSphere Voice Server interim fix, IC47845, from the product Support site.
Chapter 3. Planning
49
See the WebSphere Voice Server system requirements page for the latest information about supported operating systems.
50
WebSphere Voice Server supports Media Resource Control Protocol (MRCP) acting as an MRCP Server. MRCP is defined in the Internet Engineering Task Force (IETF). A VoiceXML browser that supports MRCP is considered an MRCP Client. A qualified VoiceXML browser and gateway allows for telephony access to WebSphere Voice Server. If the VoiceXML browser runs inside a gateway, an HTTP Server might be required to provide the VoiceXML documents, audio, and grammar files because the gateway might be constrained regarding memory.
Chapter 3. Planning
51
For development purposes, a limited set of functionality is provided to test WebSphere Voice Server without requiring a VoiceXML browser, gateway, and telephony infrastructure. This functionality is provided by the voiceTest program acting as an MRCP Client. The voiceTest program enables: v Testing a grammar against a prerecorded audio utterance and receiving the recognition result. v Synthesizing a text document and saving the synthesized speech to an audio file. The audio file can be played to hear the results. v Enhancing the lexicon documents referenced by a grammar. When using the voiceTest program as the MRCP client, access to local audio and grammar files is provided by the file URI. An optional HTTP server can be used to provide the audio and grammar files, however, it must be installed on a separate machine (see the preceding Voice Test environment figure). For more information on command line parameter information for voiceTest refer to the Testing grammars section in this information center. For more information on the tools provided in WebSphere Voice Toolkit, see the WebSphere Voice Toolkit Information Center.
52
The preceding figure shows Network Deployment managing a cell of voice servers with different languages installed. An HTTP server is required to provide audio and grammar files to WebSphere Voice Server. Refer to the Administering section for more information.
Chapter 3. Planning
53
implement configurations that address these issues. These scaling techniques are generally combined to maximize benefits and minimize problems associated with multiple machine systems. Topologies that incorporate more than one cell also have the following advantages: v Isolation of hardware failure. If one cell goes offline due to hardware problems, the others can still process client requests. v Isolation of software failure. Running different voice servers in two or more cells isolates any problems that occur within a cell, while the other cells continue to handle client requests. This isolation is helpful in a variety of situations: v When rolling out a new voice server or a revision of an existing voice server. You can bring the new voice server or revision online in one cell, and test it in a live situation while other cells continue to handle client requests with the production version of the voice server. v When deploying a new version of the WebSphere Voice Server and WebSphere Application Server software. You can bring the new version into production, and test it in a live situation without interrupting service. v When applying fixes or patches to the WebSphere Voice Server and WebSphere Application Server software. You can take each cell offline to upgrade it, without interrupting the application. If an unforeseen problem occurs with the new software, using multiple cells can prevent an outage to an entire site. You can also rollback to a previous software version more quickly. You can handle hardware and software upgrades on a cell-by-cell basis during off-peak hours.
54
Important: Make sure you run the installation verification test (IVT) for WebSphere Voice Server before federating a server into a cell. 2. Install the WebSphere Application Server deployment manager on the system administration machine. Remember: v Only one deployment manager host machine is allowed for each cell. As the deployment manager federates, or joins, base WebSphere Application Server nodes, it expands the cell that it manages. v Unless you have a machine with the capacity to host both products, do not install a base WebSphere Application Server on the same machine as the deployment manager in a production environment. v The only functions supported in the deployment manager installation are the deployment manager and its associated administrative programs, such as the administrative console. 3. Start the deployment manager process. There are two ways to start the deployment manager server: v As a monitored process, which restarts automatically if a failure occurs. v As an unmonitored process, which is what the startManager.sh or startManager.bat script does. Depending on your operating system run the startManager.sh or startManager.bat script from the /bin directory of the installation root of the deployment manager. For production systems, running the deployment manager as a monitored process is recommended. 4. Run the addNode.sh or addNode.bat script on every node that you plan to federate into the cell. The addNode.sh and addNode.bat scripts incorporate a base WebSphere Voice Server product node into a deployment manager cell. You must run this tool on every system that you plan to make part of a Network Deployment cell. There are several parameters for use with the addNode command, but the minimum required set are the host name of the deployment manager node, the JMX connector type, the JMX port of the deployment manager node, and the includeapps flag. For example:
addNode wvsdmgr 8879 -includeapps
The example adds the base node on which the command runs to the cell managed by the wvsdmgr deployment manager node, using the default SOAP JMX connector type at port 8879. The command includes all applications on the base node into the cell. As it federates the base node in response to the addNode script, the deployment manager also instantiates the node agent process,nodeagent, on the WebSphere Voice Server node. 5. Start the newly federated WebSphere Voice Server. 6. Complete the set up of the new WebSphere Voice Server by configuring performance monitoring infrastructure (PMI) monitoring for the newly federated node. 7. If necessary, enable the appropriate level of security after the installation is complete.
What to do next
Now that you have created a WebSphere Voice Server cell, use the administrative console or other administrative tools to monitor and control the incorporated
Chapter 3. Planning
55
nodes, and the resources on these nodes. The console provides a central location for configuring, monitoring, and controlling all voice servers on all nodes within the cell.
56
Chapter 4. Installing
WebSphere Voice Server uses a graphical LaunchPad and interface wizard that will guide you through the installation process. After installation, a First Steps interface provides a convenient place to explore the product. For WebSphere Voice Server version 5.1.x, the LaunchPad and the installer wizard are in English. Installing WebSphere Voice Server includes the following steps: 1. Determine the type of installation: Single machine or multiple machines 2. Start the installation using the installation wizard or install silently. 3. Verify the installation. 4. Explore WebSphere Voice Server.
57
This task describes how to set up multiple nodes into a group or cell of voice servers, with centralized configuration under the control of the deployment manager node and its distributed node agents. 6. Automatically restart WebSphere Application Server processes. This task describes how to set up WebSphere Application Server processes for the operating system to monitor and restart. By default, WebSphere Voice Server starts when WebSphere Application Server starts.
Results
The WebSphere Voice Server product is installed. See Uninstalling the product for information about uninstalling WebSphere Voice Server and its related products.
58
Red Hat Enterprise Linux WS/ES/AS for Intel 3.0 with Update 1 only (2.4 Kernel) - supported in WebSphere Voice Server versions 5.1.1 and 5.1.2 v SUSE LINUX Enterprise Server 8, powered by United Linux 1.0 (SLES-8) (Intel) with Service Pack 2a or 3 v Windows Server 2003 Enterprise or Standard editions with or without Service Pack 1 v Note: If you are using Service Pack 1, download and apply the WebSphere Voice Server interim fix, IC47845, from the product Support site. Read these topics before installing the product: v WebSphere Voice Server system requirements page v Platform-specific tips for installing and migrating v Installation prerequisites v Using the LaunchPad to start the installation v Installing silently If you encounter a problem such as not having enough temporary space or not having prerequisite packages on your system, cancel the installation, make the required changes, and restart the installation. The LaunchPad tool lets you access the Getting Started Guide and or other related documents. After starting the LaunchPad, click the Install the product option to begin the installation wizard, which: v Automatically checks prerequisites v Asks the user for a full installation (which includes the WebSphere Application Server and the IBM HTTP Server installation) or custom installation.
Chapter 4. Installing
59
Remember: To install or uninstall using a Linux or an AIX platform, log in as a root user. To install or uninstall using a Windows platform, log in as a user with Administrator privileges.
Installing
v Installing version 5.1.3 on page 68 v Installing version 5.1.2 and earlier versions on page 62
Prerequisites
Before installing WebSphere Voice Server, identify the hardware and software you require, and then refer to the topics below for any additional prerequisites.
60
v v v v v
These packages can be found in the Red Hat Legacy S/W Development and Development tools packs. Also see the WebSphere Voice Server system requirements page for the latest information about supported operating systems.
61
Note: If it does not start automatically, open the Windows Explorer to the drive the CD is in and double-click on the Launchpad.exe file. The LaunchPad opens in English only. 2. Use the LaunchPad to access the product overview and the Getting Started Guide. 3. Click Install the product to launch the installation wizard.
Installing on Linux
Tip: WebSphere Application Server and any required fix packs are installed silently with WebSphere Voice Server. While existing installations of WebSphere Application Server are supported, installing WebSphere Application Server before installing WebSphere Voice Server is not necessary. 1. Prepare your operating system platform for installation by verifying that you have adequate disk space and that you have the necessary installation prerequisites before starting installation. 2. Insert the WebSphere Voice Server for MRCP Linux CD. The LaunchPad tool automatically launches the Installation wizard, which is an InstallShield for MultiPlatforms (ISMP) application. The Installation wizard is in English. You can also start the Installation wizard from the product CD using the LaunchPad (launchpad.sh). Always use the fully qualified path to the launchpad.sh when installing the product. The following examples show how to start the launchpad.sh when installing from the product CD on a Linux system:
62
a. Place the CD in the drive. b. Issue the appropriate command for your Linux version in order to mount the CD and start the LaunchPad tool. For Red Hat:
cd / mount /mnt/cdrom /mnt/cdrom/launchpad.sh
For SUSE:
cd / mount /media/cdrom /media/cdrom/launchpad.sh
To unmount the CD, issue the following commands: For Red Hat:
cd / umount /mnt/cdrom
For SUSE:
cd / umount /media/cdrom
Failing to use the correct path can cause ISMP errors that stop the installation. Tip: You can start the installation using the install.sh command in the dist directory of the CD to bypass the LaunchPad. This is required for silent installation. The rest of this procedure assumes that you are using the Installation wizard, launched from either install.sh or LaunchPad. Corresponding entries in the response file exist for every prompt that is described as part of the wizard. Review the description of the response file for more information. Comments in the file describe how to customize its options. The LaunchPad Welcome panel displays. Click Install the product to continue. In the InstallShield Welcome panel, click Next to continue. The license agreement appears for you to read. Click the radio button beside the I accept the terms in the license agreement message if you agree to the license agreement and click Next to continue. After you accept the licensing terms, the installation wizard checks for prerequisites and for previous versions. Next, the language panel for WebSphere Voice Server displays. Select one of the languages for WebSphere Voice Server language capability, as well as for TTS and ASR capabilities.
3. 4. 5.
6.
Note: WebSphere Voice Server supports only one language installation. 7. The Setup screen prompts you to select either a Full or Custom installation. v Select the Full radio button if you are installing WebSphere Application Server and WebSphere Voice Server. Click Next to continue. v Select the Custom radio button if you are installing WebSphere Voice Server on an existing instance of WebSphere Application Server. Click Next to continue. 8. If you are installing WebSphere Application Server for the first time, you will be prompted for the following: a. Choose installation directories for WebSphere Application Server and for the IBM HTTP Server. b. Choose a node name and a host name for WebSphere Application Server.
Chapter 4. Installing
63
If you already have WebSphere Application Server installed, you are prompted to choose to use an existing instance and click the appropriate radio button. Then click Next to continue. If an incorrect location for WebSphere Application Server is displayed, enter the correct location in the field at the bottom of the panel and click Next to continue. Configure your WebSphere Application Server as a service when prompted. Choose the destination directory for WebSphere Voice Server. Click Next to continue. A summary panel displays your installation selections. Click Next to start the installation process. You are then prompted to provide various CDs or image locations for each component.
Note: The TTS installation is lengthy. Do not cancel out of it. The Summary panel indicates when the installation is complete and displays the installation status. 13. A summary panel of the installation with instructions to reboot appears. Click Finish to close the installation wizard. 14. Prior to rebooting your system, add the wvs_install_path/wvs.setenv line to your shells startup profile (.bash_profile if you are using the bash shell on RedHat Linux). Edit the appropriate operating system level shell startup file and add the line:
. /opt/WebSphere/VoiceServer/wvs.setenv
Ensure that the startup profile runs during start up. 15. If you receive any warnings during installation, examine the /tmp/CWVOptInstall.log file to verify that there were no file system problems or other unusual errors. If there are problems, correct them, uninstall the product, and then reinstall it. 16. Restart the system and run the WebSphere Voice Server firststeps command on page 85. The command script is located at $WVS_ROOT/firststeps/firststeps.sh, where $WVS_ROOT is a variable defined during the installation of WebSphere Voice Server. Issue the following commands at a command prompt:
cd $WVS_ROOT/firststeps ./firststeps.sh
On the First Steps panel, click Start the server. Then, once you receive the Open for e-business message that indicates the server started, click Verify installation to make sure that all is well with your installation. If any failures are reported, see Installation troubleshooting tips on page 461. Remember: The Linux firewall must be disabled for the Interactive Voice Response (IVR) to communicate with WebSphere Voice Server. 17. Apply the appropriate tuning parameters. 18. Install the most current fix pack for WebSphere Voice Server. Remember: The Linux firewall must be disabled for the Interactive Voice Response (IVR) to communicate with WebSphere Voice Server.
64
4. Copy the fix pack file that you downloaded, was51_fp1_linux.tar.gz, to the new directory. 5. Unzip and untar the file:
gunzip was51_fp1_linux.tar.gz tar -xvf was51_fp1_linux.tar
6. Reboot the system and ensure that WebSphere Application Server, IBM HTTP Administration Server, and IBM HTTP Server are stopped. 7. Set up the WebSphere Application Server command line:
cd WAS_installation_directory/bin . ./setupCmdLine.sh
WAS_installation_directory is the installation directory where you installed WebSphere Application Server. When you run the setupCmdLine.sh command, the $WAS_HOME variable is defined for this location. 8. Change to the fix pack directory and start the update wizard to install the fix pack:
cd /tmp/WAS511/ ./updateWizard.sh
9. Install the fix pack by following the instructions in the wizard and selecting the defaults. 10. Reboot the system. 11. After installing fix pack 1 for WebSphere Application Server 5.1 and starting WebSphere Application Server, rerun the WebSphere Voice Server firststeps command and verify your installation again. 12. Then restore the WebSphere Voice Server Collector. Change directory to $WAS_HOME/bin and issue the restoreWVSCollector.sh command.
Chapter 4. Installing
65
Note: If you are using Service Pack 1, download and apply the WebSphere Voice Server interim fix, IC47845, from the product Support site. 1. Prepare your operating system platform for installation by verifying that you have adequate disk space and that you have the necessary installation prerequisites before starting installation. 2. Insert the WebSphere Voice Server for MRCP Windows Server 2003 CD. The LaunchPad tool automatically launches the installation wizard. If necessary, you can also start the installation wizard from the product CD by double-clicking the launchpad.exe file. This action launches the installation wizard in English. Tip: You can start the installation using the install.bat command in the base directory of the CD to bypass the LaunchPad. This is required for silent installation. The LaunchPad Welcome panel displays. Click Install the product to continue. The system displays an Install program has been launched message. Click OK. In the InstallShield Welcome panel, click Next to continue. Click the radio button beside the I accept the terms in the license agreement message if you agree to the license agreement and click Next to continue. After you accept the licensing terms, the installation wizard checks for prerequisites and for previous versions. Next, the language panel for WebSphere Voice Server displays. Select one of the languages for WebSphere Voice Server language capability, as well as for TTS and ASR capabilities.
3. 4. 5. 6.
7.
Note: WebSphere Voice Server supports only one language installation. 8. The Setup screen prompts you to select either a Full or Custom installation. v Select the Full radio button if you are installing WebSphere Application Server and WebSphere Voice Server. Click Next to continue. v Select the Custom radio button if you are installing WebSphere Voice Server on an existing instance of WebSphere Application Server. Click Next to continue. 9. If you are installing WebSphere Application Server for the first time, you will be prompted for the following: a. Choose installation directories for WebSphere Application Server and for the IBM HTTP Server. b. Configure both WebSphere Application Server and HTTP Server as a service. c. Enter a logon user ID and a password. Make sure that the logon user ID belongs to the administrator group and has the following advanced user rights: v Act as part of the operating system v Log on as a service d. Choose a node name and a host name for WebSphere Application Server. If you already have WebSphere Application Server installed, you are prompted to choose to use an existing instance and click the appropriate radio button. Then click Next to continue.
66
If an incorrect location for WebSphere Application Server is displayed, enter the correct location in the field at the bottom of the panel and click Next to continue. 10. Choose the destination directory for WebSphere Voice Server. Click Next to continue. 11. A summary panel displays your installation selections. Click Next to start the installation process. 12. You are then prompted to provide various CDs or image locations for each component. Note: The TTS installation is lengthy. Do not cancel out of it. The Summary panel indicates when the installation is complete and displays the installation status. 13. A summary panel of the installation with instructions to reboot appears. Click Finish to close the installation wizard. 14. If you receive any warnings during installation, examine the %TEMP%\CWVOptInstall.log file to verify that there were no file system problems, or other unusual errors. If there are problems, correct them, uninstall the product, and then reinstall it. 15. Restart the system and run the WebSphere Voice Server firststeps command on page 85. The command script is located at %WVS_ROOT%\firststeps\firststeps.bat, where %WVS_ROOT% is a variable defined during the installation of WebSphere Voice Server. Issue the following commands at a command prompt:
cd %WVS_ROOT%\firststeps firststeps.bat
On the First Steps panel, click Start the server. Then, once you receive the Open for e-business message that indicates the server started, click Verify installation to make sure that all is well with your installation. If any failures are reported, see Installation troubleshooting tips on page 461. 16. Apply the appropriate tuning parameters. 17. Install the most current fix pack for WebSphere Voice Server.
2. 3. 4. 5.
67
6. 7. 8. 9.
10.
WAS_installation_directory is the installation directory where you installed WebSphere Application Server. When you run the setupCmdLine.bat command, the %WAS_HOME% variable is defined for this location. Change to the fix pack directory and issue the updateWizard.bat command. To complete the installation, follow the instructions in the wizard, selecting the defaults. Reboot the system. After installing fix pack 1 for WebSphere Application Server 5.1 and starting WebSphere Application Server, rerun the WebSphere Voice Server firststeps command and verify your installation again. Then restore the WebSphere Voice Server Collector. Change directory to %WAS_HOME%\bin and issue the restoreWVSCollector.bat command.
Post-installation steps
1. Confirm that the IBM HTTP Server starts successfully by entering http://localhost:80 in a browser. This should display the Welcome to IBM HTTP Server main page. If you did not configure the IBM HTTP Server as a service during the installation, refer to Starting and stopping the IBM HTTP Server on page 142 for steps to manually start the server. 2. Use the firststeps tool to verify the installation. 3. To launch the WebSphere Application Server administrative console, enter: http://your host name:9090/admin, where your host name is the fully qualified name of your host system or your host IP address, in a browser. 4. Navigate to the Voice System View panel to confirm that WebSphere Voice Server is started. Refer to the firststeps section of the WebSphere Voice Server Information Center for more details.
Results
You have now successfully installed WebSphere Voice Server and the features you selected. The Installation wizard configures the product. You are not required to perform further configuration at this time.
68
v v v v v
Installing on AIX Installing on Linux on page 71 Installing on Windows Server 2003 Enterprise or Standard editions on page 73 Post-installation steps on page 76 Results on page 76
Installing on AIX
Tip: WebSphere Application Server and any required fix packs are installed silently with WebSphere Voice Server. While existing installations of WebSphere Application Server are supported, installing WebSphere Application Server before installing WebSphere Voice Server is not necessary. 1. Prepare your operating system platform for installation by verifying that you have adequate disk space and that you have the necessary installation prerequisites before starting installation. 2. Check to see if you have the WebSM Service enabled on your machine by issuing the following command: lslpp -h sysmgt.websm.framework If the command fails, then you do not have the WebSM Service installed. Make sure that the port 9090 is commented out of the /etc/services file, and proceed to the next step. If you do have the WebSM Service enabled, disable it by issuing the following command: /usr/websm/bin/wsmserver -disable Important: There is a port number conflict between the WebSphere Application Server administrative console and WebSM service on AIX. Both use port 9090. The port 9090 conflict on AIX is a known WebSphere Application Server issue. Ensure that no other applications are using this port, and make sure that the port 9090 is commented out of the /etc/services file. 3. Insert the WebSphere Voice Server for MRCP AIX CD. The LaunchPad tool automatically launches the Installation wizard, which is an InstallShield for MultiPlatforms (ISMP) application. The Installation wizard is in English. You can also start the Installation wizard from the product CD using the LaunchPad (launchpad.sh). Always use the fully qualified path to the launchpad.sh when installing the product. The following examples show how to start the launchpad.sh when installing from the product CD: a. Place the CD in the drive. b. Issue the appropriate AIX command in order to mount the CD and start the LaunchPad tool.
Chapter 4. Installing
69
Failing to use the correct path can cause ISMP errors that stop the installation. Tip: You can start the installation using the install.sh command in the dist directory of the CD to bypass the LaunchPad. This is required for silent installation. The rest of this procedure assumes that you are using the Installation wizard, launched from either install.sh or LaunchPad. Corresponding entries in the response file exist for every prompt that is described as part of the wizard. Review the description of the response file for more information. Comments in the file describe how to customize its options. The LaunchPad Welcome panel displays. The Getting Started Guide link in the LaunchPad is to the docs\gettingstarted_aix_en.html file on the base product CD. Choose to read the Product Overview or the Getting Started Guide, or click Install the product to continue. The system displays an Install program has been launched message. Click OK. In the InstallShield Welcome panel, click Next to continue. Click the radio button beside the I accept the terms in the license agreement message if you agree to the license agreement and click Next to continue. After you accept the licensing terms, the installation wizard checks for prerequisites and for previous versions. The Setup screen prompts you to select either a Full or Custom install. v Select the Full radio button if you are installing WebSphere Application Server and WebSphere Voice Server. Click Next to continue. v Select the Custom radio button if you are installing WebSphere Voice Server on an existing instance of WebSphere Application Server. Click Next to continue. If you are installing WebSphere Application Server for the first time, you will be prompted for the following: a. Choose installation directories for WebSphere Application Server and for the IBM HTTP Server. b. Choose a node name and a host name for WebSphere Application Server. If you already have WebSphere Application Server installed, you are prompted to choose an existing instance or to install a new instance. Click the appropriate radio button and then click Next to continue. If an incorrect location for WebSphere Application Server is displayed, enter the correct location in the field at the bottom of the panel and click Next to continue. Next, the installation wizard prompts you for the WebSphere Application Server fix pack CD to install the required WebSphere Application Server fix packs.
4.
5. 6. 7.
8.
9.
10.
Note: If you already have WebSphere Application Server installed, you will not see this prompt from the wizard. 11. Choose the destination directory for WebSphere Voice Server. Click Next to continue.
70
12. Next, the language panel for WebSphere Voice Server displays. Select the WebSphere Voice Server TTS and/or ASR capabilities that you require. Click Next to continue. 13. A summary panel displays your install selections. Click Next to start the installation process. 14. You are then prompted to provide various CDs or image locations for each component. Note: The TTS installation is lengthy. Do not cancel out of it. The Summary panel indicates when the installation is complete, and displays the installation status. 15. A summary panel of the installation with instructions to reboot appears. Click Finish to close the installation wizard. The Welcome panel appears. Choose to read the Product Overview or the Getting Started Guide, or Exit. 16. If you receive any warnings during installation, examine the /tmp/CWVOptInstall.log file to verify that there were no file system problems, or other unusual errors. If there are problems, correct them, uninstall the product, and then reinstall. If there are no problems recorded in the /tmp/CWVOptInstall.log file, verify or troubleshoot the installation in step three described in Installing WebSphere Voice Server on page 57. 17. Restart the system and run the firststeps command on page 85. The command script is located at $WVS_ROOT/firststeps/firststeps.sh, where $WVS_ROOT is a variable defined during the installation of WebSphere Voice Server. Issue the following commands at a command prompt:
cd $WVS_ROOT/firststeps ./firststeps.sh
The installation of WebSphere Voice Server includes configuration tuning for WebSphere Application Server and your operating system. To see tips on additional ways to improve the performance of your WebSphere Voice Server, refer to the topic on Chapter 7, Tuning, on page 145. 18. To use a Web browser with AIX, download and install the Mozilla browser from Web browsers for AIX.
Installing on Linux
Tip: WebSphere Application Server and any required fix packs are installed silently with WebSphere Voice Server. While existing installations of WebSphere Application Server are supported, installing WebSphere Application Server before installing WebSphere Voice Server is not necessary. 1. Prepare your operating system platform for installation by verifying that you have adequate disk space and that you have the necessary installation prerequisites before starting installation. 2. Insert the WebSphere Voice Server for MRCP Linux CD. The LaunchPad tool automatically launches the Installation wizard, which is an InstallShield for MultiPlatforms (ISMP) application. The Installation wizard is in English. You can also start the Installation wizard from the product CD using the LaunchPad (launchpad.sh). Always use the fully qualified path to the launchpad.sh when installing the product. The following examples show how to start the launchpad.sh when installing from the product CD on a Linux system: a. Place the CD in the drive.
Chapter 4. Installing
71
b. Issue the appropriate command for your Linux version in order to mount the CD and start the LaunchPad tool. For Red Hat:
cd / mount /mnt/cdrom /mnt/cdrom/launchpad.sh
For SUSE:
cd / mount /media/cdrom /media/cdrom/launchpad.sh
To unmount the CD, issue the following commands: For Red Hat:
cd / umount /mnt/cdrom
For SUSE:
cd / umount /media/cdrom
Failing to use the correct path can cause ISMP errors that stop the installation. Tip: You can start the installation using the install.sh command in the dist directory of the CD to bypass the LaunchPad. This is required for silent installation. The rest of this procedure assumes that you are using the Installation wizard, launched from either install.sh or LaunchPad. Corresponding entries in the response file exist for every prompt that is described as part of the wizard. Review the description of the response file for more information. Comments in the file describe how to customize its options. The LaunchPad Welcome panel displays. The Getting Started Guide link in the LaunchPad is to the docs\gettingstarted_linux_en.html file on the base product CD. Choose to read the Product Overview or the Getting Started Guide, or click Install the product to continue. The system displays an Install program has been launched message. Click OK. In the InstallShield Welcome panel, click Next to continue. Click the radio button beside the I accept the terms in the license agreement message if you agree to the license agreement and click Next to continue. After you accept the licensing terms, the installation wizard checks for prerequisites and for previous versions. The Setup screen prompts you to select either a Full or Custom install. v Select the Full radio button if you are installing WebSphere Application Server and WebSphere Voice Server. Click Next to continue. v Select the Custom radio button if you are installing WebSphere Voice Server on an existing instance of WebSphere Application Server. Click Next to continue. If you are installing WebSphere Application Server for the first time, you will be prompted for the following: a. Choose installation directories for WebSphere Application Server and for the IBM HTTP Server. b. Choose a node name and a host name for WebSphere Application Server. If you already have WebSphere Application Server installed, you are prompted to choose an existing instance or to install a new instance. Click the appropriate radio button and then click Next to continue.
3.
4. 5. 6.
7.
8.
72
If an incorrect location for WebSphere Application Server is displayed, enter the correct location in the field at the bottom of the panel and click Next to continue. 9. Next, the installation wizard prompts you for the WebSphere Application Server fix pack CD to install the required WebSphere Application Server fix packs. If you already have WebSphere Application Server installed, you will not see this prompt from the wizard. Note: As you are prompted to insert additional CDs throughout the installation, make sure the default location for the CD is correct in the installation wizard when prompted. For example, /mnt/cdrom. Choose the destination directory for WebSphere Voice Server. Click Next to continue. Next, the language panel for WebSphere Voice Server displays. Select the WebSphere Voice Server TTS and/or ASR capabilities that you require. Click Next to continue. A summary panel displays your install selections. Click Next to start the installation process. You are then prompted to provide various CDs or image locations for each component.
10. 11.
12. 13.
Note: The TTS installation is lengthy. Do not cancel out of it. The Summary panel indicates when the installation is complete, and displays the installation status. 14. A summary panel of the installation with instructions to reboot appears. Click Finish to close the installation wizard. The Welcome panel appears. Choose to read the Product Overview or the Getting Started Guide, or Exit. 15. If you receive any warnings during installation, examine the /tmp/CWVOptInstall.log file to verify that there were no file system problems, or other unusual errors. If there are problems, correct them, uninstall the product, and then reinstall. If there are no problems recorded in the /tmp/CWVOptInstall.log file, verify or troubleshoot the installation in step three described in Installing WebSphere Voice Server on page 57. 16. Restart the system and run the firststeps command on page 85. The command script is located at $WVS_ROOT/firststeps/firststeps.sh, where $WVS_ROOT is a variable defined during the installation of WebSphere Voice Server. Issue the following commands at a command prompt:
cd $WVS_ROOT/firststeps ./firststeps.sh
The installation of WebSphere Voice Server includes configuration tuning for WebSphere Application Server and your operating system. To see tips on additional ways to improve the performance of your WebSphere Voice Server, refer to the topic on Chapter 7, Tuning, on page 145. Remember: The Linux firewall must be disabled for the Interactive Voice Response (IVR) to communicate with WebSphere Voice Server.
Chapter 4. Installing
73
WebSphere Application Server are supported, installing WebSphere Application Server before installing WebSphere Voice Server is not necessary. Note: If you are using Service Pack 1, download and apply the WebSphere Voice Server interim fix, IC47845, from the product Support site. 1. Prepare your operating system platform for installation by verifying that you have adequate disk space and that you have the necessary installation prerequisites before starting installation. 2. Insert the WebSphere Voice Server for MRCP Windows Server 2003 CD. The LaunchPad tool automatically launches the installation wizard. If necessary, you can also start the installation wizard from the product CD by double-clicking the launchpad.exe file. This action launches the installation wizard in English. Tip: You can start the installation using the install.bat command in the base directory of the CD to bypass the LaunchPad. This is required for silent installation. The rest of this procedure assumes that you are using the Installation wizard, launched from either install.bat or LaunchPad. Corresponding entries in the response file exist for every prompt that is described as part of the wizard. Review the description of the response file for more information. Comments in the file describe how to customize its options. 3. The LaunchPad Welcome panel displays. The Getting Started Guide link in the LaunchPad is to the docs\gettingstarted_win_en.html file on the base product CD. Choose to read the Product Overview or the Getting Started Guide, or click Install the product to continue. 4. The system displays an Install program has been launched message. Click OK. 5. In the InstallShield Welcome panel, click Next to continue. 6. Click the radio button beside the I accept the terms in the license agreement message if you agree to the license agreement and click Next to continue. After you accept the licensing terms, the installation wizard checks for prerequisites and for previous versions. 7. The Setup screen prompts you to select either a Full or Custom install. v Select the Full radio button if you are installing WebSphere Application Server and WebSphere Voice Server. Click Next to continue. v Select the Custom radio button if you are installing WebSphere Voice Server on an existing instance of WebSphere Application Server. Click Next to continue. 8. If you are installing WebSphere Application Server for the first time, you will be prompted for the following: a. Choose installation directories for WebSphere Application Server and for the IBM HTTP Server. b. Configure both WebSphere Application Server and IBM HTTP Server as a service. c. Enter a logon user ID and a password. Make sure that the logon user ID belongs to the administrator group and has the following advanced user rights: v Act as part of the operating system v Log on as a service
74
Important: When installing WebSphere Application Server as a Windows service, do not use a user ID that contains spaces. A user ID with spaces cannot be validated, and the user is not allowed to proceed with the installation. To work around this problem, install with a user ID that does not contain spaces, or do not choose to install services. d. Choose a node name and a host name for WebSphere Application Server. If you already have WebSphere Application Server installed, you are prompted to choose an existing instance or to install a new instance. Click the appropriate radio button and then click Next to continue. If an incorrect location for WebSphere Application Server is displayed, enter the correct location in the field at the bottom of the panel and click Next to continue. 9. Next, the installation wizard prompts you for the WebSphere Application Server fix pack CD to install the required WebSphere Application Server fix packs. Note: If you already have WebSphere Application Server installed, you will not see this prompt from the wizard. Choose the destination directory for WebSphere Voice Server. Click Next to continue. Next, the language panel for WebSphere Voice Server displays. Select the WebSphere Voice Server TTS and/or ASR capabilities that you require. Click Next to continue. A summary panel displays your install selections. Click Next to start the installation process. You are then prompted to provide various CDs or image locations for each component.
10. 11.
12. 13.
Note: The TTS installation is lengthy. Do not cancel out of it. The Summary panel indicates when the installation is complete, and displays the installation status. 14. A summary panel of the installation with instructions to reboot appears. Click Finish to close the installation wizard. The Welcome panel appears. Choose to read the Product Overview or the Getting Started Guide, or Exit. 15. If you receive any warnings during installation, examine the %TEMP%\CWVOptInstall.log file to verify that there were no file system problems, or other unusual errors. If there are problems, correct them, uninstall the product, and then reinstall. If there are no problems recorded in the %TEMP%\CWVOptInstall.log file, verify or troubleshoot the installation in step three described in Installing WebSphere Voice Server on page 57. 16. Restart the system and run the firststeps command on page 85. The command script is located at %WVS_ROOT%\firststeps\firststeps.bat, where %WVS_ROOT% is a variable defined during the installation of WebSphere Voice Server. Issue the following commands at a command prompt:
cd %WVS_ROOT%\firststeps firststeps.bat
The installation of WebSphere Voice Server includes configuration tuning for WebSphere Application Server and your operating system. To see tips on additional ways to improve the performance of your WebSphere Voice Server, refer to the topic on Chapter 7, Tuning, on page 145.
Chapter 4. Installing
75
Post-installation steps
1. Confirm that the IBM HTTP Server starts successfully by entering http://localhost:80 in a browser. This should display the Welcome to IBM HTTP Server main page. If you did not configure the IBM HTTP Server as a service during the installation, refer to Starting and stopping the IBM HTTP Server on page 142 for steps to manually start the server. 2. Use the firststeps tool to verify the installation. 3. To launch the WebSphere Application Server administrative console, enter: http://your host name:9090/admin, where your host name is the fully qualified name of your host system or your host IP address, in a browser. 4. Navigate to the Voice System View panel to confirm that WebSphere Voice Server is started. Refer to the firststeps section of the WebSphere Voice Server Information Center for more details.
Results
You have now successfully installed WebSphere Voice Server and the features you selected. The Installation wizard configures the product. You are not required to perform further configuration at this time.
Installing silently
This topic describes how to perform a silent installation of the product as the root user on an AIX or Linux system, or as an administrative user on a Windows 2003 operating system.
76
For Windows:
install.bat -silent -options full_path_to_response_file responsefile.txt
Note: The responsefile.txt is your customized copy of the wvs51response.txt, located in the cdrom/responsefilesample directory. The full path is required to your customized copy of the response file. The log.txt file is in the logs directory in the root of the installation path of WebSphere Voice Server. For reference, the default installation paths are the following: /usr/WebSphere/VoiceServer /opt/WebSphere/VoiceServer C:\Program Files\WebSphere\VoiceServer
Results
You can view the log file to verify the install is complete. Examine the log.txt file for lines similar to these:
(Jun 30, 2004 2:53:17 PM), CWVIN, com.ibm.wps.install .ExternalCommandAction$OutputWatcher, msg2, StdOut: ADMA6016I: Add to workspace adminconsole.war/WEB-INF/struts-config_1_0.dtd (Jun 30, 2004 2:53:17 PM), CWVIN, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut: ADMA6017I: Saved document /opt/WebSphere/AppServer/wstemp/fd76e74534/workspace/cells/ngbuild1/ applications/adminconsole.ear/deployments/adminconsole/adminconsole.war/ META-INF/MANIFEST.MF (Jun 30, 2004 2:53:17 PM), CWVIN, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut: ADMA6016I: Add to workspace adminconsole.war/META-INF/MANIFEST.MF (Jun 30, 2004 2:53:17 PM), CWVIN, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut: ADMA6017I: Saved document /opt/WebSphere/AppServer/wstemp/fd76e74534/workspace/cells/ ngbuild1/applications/ adminconsole.ear/deployments/adminconsole/adminconsole.war/ WEB-INF/web.xml (Jun 30, 2004 2:53:17 PM), CWVIN, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut: ADMA6016I: Add to workspace adminconsole.war/WEB-INF/web.xml (Jun 30, 2004 2:53:17 PM),
Chapter 4. Installing
77
CWVIN, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut: ADMA5037I: Starting backup of app at /opt/WebSphere/AppServer/wstemp/fd76e74534/workspace/cells/ngbuild1/ applications/adminconsole.ear (Jun 30, 2004 2:53:29 PM), CWVIN, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut: ADMA5038I: Completed backup of app at /opt/WebSphere/AppServer/wstemp/fd76e74534/workspace/cells/ngbuild1/ applications/adminconsole.ear/adminconsole.ear (Jun 30, 2004 2:53:29 PM), CWVIN, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut: ADMA6011I: Deleting directory tree /tmp/app_fd76e74937 (Jun 30, 2004 2:53:44 PM), CWVIN, com.ibm.wps.install.ExternalCommandAction, msg2, Return code = 0 (Jun 30, 2004 2:53:44 PM), CWVIN, com.ibm.wps.install.ExternalCommandAction, msg2, Executing command: completed (Jun 30, 2004 2:53:45 PM), CWVIN, com.ibm.wps.install.DeleteDirectoryOnExitAction, msg1, Deleting directory tree on exit: /tmp/wvslaunch
This indicates that you have successfully installed the product. Related information Customizing the Network Deployment options response file You can customize the response file to silently install the WebSphere Application Server Network Deployment product from a command line without the Installation wizard.
78
The Summary panel indicates when the installation is complete, and displays the installation status. 9. A summary panel of the installation with instructions to reboot appears. Click Finish to close the installation wizard. 10. After restarting your machine, run the firststeps command on page 85 to make sure that the product and any newly installed ASR or TTS languages are installed correctly.
WebSphere Application Server 5.1.1 fix pack required for WebSphere Voice Server 5.1.1 and 5.1.2
Remember: If you are using WebSphere Voice Server version 5.1.3, this fix pack was applied during your WebSphere Voice Server installation. Obtain fix pack 1 for WebSphere Application Server Version 5.1 Base and Network Deployment from the WebSphere Application Server support site and install it on your Linux and Windows systems using the steps below. 1. Locate WebSphere Application Server 5.1 fix pack 1 and download the package appropriate for your Linux or Windows operating system, either Linux on Intel Base or Windows Base. Note: If you are applying fix pack 1 to your Deployment Manager installation, download the Linux on Intel ND or Windows ND package. 2. Create a temporary directory for the fix pack that does not contain any spaces in the name. For example:
cd /tmp mkdir WAS511
3. Copy the fix pack file that you downloaded, was51_fp1_linux.tar.gz or was51_fp1_win.zip, to the new directory and extract its contents. For Linux, unzip and untar the file. For example:
gunzip was51_fp1_linux.tar.gz tar -xvf was51_fp1_linux.tar
4. Ensure that WebSphere Application Server and IBM HTTP Server are stopped. 5. Set up the command line. For Linux:
cd WAS_installation_directory/bin . ./setupCmdLine.sh
For Windows:
cd WAS_installation_directory\bin setupCmdLine.bat
WAS_installation_directory is the installation directory where you installed WebSphere Application Server. When you run the setupCmdLine command, the $WAS_HOME variable is defined for this location. 6. Change to the fix pack directory and start the update wizard to install the fix pack. For Linux:
Chapter 4. Installing
79
cd /tmp/WAS511/ ./updateWizard.sh
For Windows:
cd c:\temp\WAS511/ updateWizard.bat
7. Install the fix pack by following the instructions in the wizard and selecting the defaults. 8. Reboot the system. 9. After installing WebSphere Application Server 5.1 fix pack 1 and startingWebSphere Application Server, rerun the firststeps command on page 85 and verify your installation again. 10. Then restore the WebSphere Voice Server Collector. a. Change the directory to $WAS_HOME/bin if you are using a Linux platform or %WAS_HOME%\bin if you are using a Windows platform. b. Issue the ./restoreWVSCollector.sh command if you are using a Linux platform or the restoreWVSCollector.bat if you are using a Windows platform.
80
Linux - ND, Linux - SDK Windows - ND, Windows - SDK 5. Install the WebSphere Voice Server administrative console extensions.
3. 4. 5. 6. 7.
See Uninstalling Network Deployment for uninstallation instructions for WebSphere Application Server Network Deployment and the WebSphere Voice Server administrative console extensions. Related information Installing deployment manager on page 80
Chapter 4. Installing
81
4.
82
Installation tips
This topic describes tips specific to installing WebSphere Voice Server. Refer to the following links for detailed tips for installation: v Non-ASCII special characters are not supported in the name of the installation directory v Verifying the system cp command when using emacs or other freeware
Chapter 4. Installing
83
2. Open a terminal window and change directory to where the firststeps script is located: $WVS_ROOT/firststeps/firststeps.sh $WVS_ROOT/firststeps/firststeps.sh %WVS_ROOT%\firststeps\firststeps.bat 3. If you are using WebSphere Voice Server version 5.1, 5.1.1, or 5.1.2, you must select Start the Server before selecting Verify Installation. Selecting to verify the installation for WebSphere Voice Server does not automatically start the server on versions 5.1, 5.1.1, and 5.1.2. Important: Do not select any other options from the First Steps panel after selecting the Start the server option until the server is started. After selecting the Start the server option, an output screen displays with status messages. The success message informs you that the server is open for business (Server your_server_name open for e-business). Then the menu item changes to Stop the server (on WebSphere Voice Server versions 5.1, 5.1.1, and 5.1.2). The server must be running before proceeding to the next step. If you are using WebSphere Voice Server version 5.1.3, skip to the next step. The server is automatically started on WebSphere Voice Server version 5.1.3. 4. Confirm the server is running and select Verify Installation. The IVT runs a series of verification tests and reports the results in the First Steps output window. Do not select any other First Steps panel options while the installation verification is running. The WebSphere Voice Server IVT program validates that your ASR language and TTS voices are installed correctly.
Sample output
Below is a sample of a successful IVT report. Note that the language and voice name would be different based on your installation choices.
WebSphere Voice Server Installation Verification Test - Begin ================================================================ Starting WebSphere Application Server if its not already running ====================== Verification for Text-to-Speech voice: Andrew ============== [05/09/29 15:06:39:844 EDT] Thread-1 sysmgmt A CWVSY1002I: WVS installation verification has started. [05/09/29 15:06:39:844 EDT] Thread-1 sysmgmt A CWVSY1003I: WVS installation verification executing for TTS voice Andrew ... [05/09/29 15:06:41:625 EDT] Thread-1 sysmgmt A CWVSY1005I: WVS installation verification is validating results ... [05/09/29 15:06:41:625 EDT] Thread-1 sysmgmt A CWVSY1004I: WVS installation verification worked successfully. [05/09/29 15:06:41:625 EDT] Thread-1 sysmgmt A CWVSY1008I: WVS installation verification successfully created a sample audio file, named Andrew.au and located in the $WVS_ROOT/ivt directory. [05/09/29 15:06:41:625 EDT] Thread-1 sysmgmt A CWVSY1006I: WVS installation verification is complete. ====================== Verification for Text-to-Speech voice: Allison ============== [05/09/29 15:06:42:172 EDT] Thread-1 sysmgmt A CWVSY1002I: WVS installation verification has started. [05/09/29 15:06:42:172 EDT] Thread-1 sysmgmt A CWVSY1003I: WVS installation verification executing for TTS voice Allison ... [05/09/29 15:06:43:828 EDT] Thread-1 sysmgmt A CWVSY1005I: WVS installation verification is validating results ... [05/09/29 15:06:43:828 EDT] Thread-1 sysmgmt A CWVSY1004I: WVS installation verification worked successfully. [05/09/29 15:06:43:828 EDT] Thread-1 sysmgmt A CWVSY1008I: WVS installation verification successfully created a sample audio file, named Allison.au and located in the $WVS_ROOT/ivt directory. [05/09/29 15:06:43:828 EDT] Thread-1 sysmgmt A CWVSY1006I: WVS installation verification is complete. ====================== Verification for Automatic Speech Recognition Language: en_US ===
84
[05/09/29 15:06:44:391 EDT] Thread-1 sysmgmt A CWVSY1002I: WVS installation verification has started. [05/09/29 15:06:44:391 EDT] Thread-1 sysmgmt A CWVSY1003I: WVS installation verification executing for ASR language en_US ... [05/09/29 15:06:49:062 EDT] Thread-1 sysmgmt A CWVSY1005I: WVS installation verification is validating results ... [05/09/29 15:06:49:062 EDT] Thread-1 sysmgmt A CWVSY1004I: WVS installation verification worked successfully. [05/09/29 15:06:49:062 EDT] Thread-1 sysmgmt A CWVSY1006I: WVS installation verification is complete. ===================================================================================== WebSphere Voice Server Installation Verification Test - End Please check the log shown above for any unsuccessful test results. If any are reported, see the Troubleshooting section of the Infocenter for further information.
What to do next
Return to Installing WebSphere Voice Server to continue.
firststeps command
The firststeps command starts the First Steps tool. First Steps is a post-installation ease-of-use tool for directing WebSphere Voice Server elements from one place. Options dynamically appear on the First Steps panel, depending on features you install. With all options present, you can use First Steps to start and stop the server (on WebSphere Voice Server versions 5.1, 5.1.1, and 5.1.2), verify the installation, or access the information center. First Steps must be started by the command line once the system has been rebooted, after the end of installation. If you try to verify the installation without rebooting, the system will not pass. The location of the First Steps script for each operating system is listed in the Summary panel when you finish your installation. The paths are also listed here:
Chapter 4. Installing
85
Installing the IBM TTS Connector for Genesys Voice Platform for WebSphere Voice Server
In order to use IBM WebSphere Voice Server Text-to-Speech (TTS) on the Genesys Voice Platform (GVP) NE 6.5.4 or EE 6.5.5, the IBM TTS Connector must be installed. The IBM TTS Connector is no longer needed with GVP 7.0.3. The steps in this topic are not required if you are using only automatic speech recognition (ASR).
86
Stop the Watchdog service. a. Open the Services dialog. b. Select Start Control Panel Administration Tools Services. c. Right-click the Watchdog service and select Stop. 3. Insert the IBM TTS Connector for GVP for WebSphere Voice Server CD into your CD-ROM drive. 4. Add a fully-qualified host name entry to the Windows GVP hosts file for WebSphere Voice Server. For example, navigate to the C:\WinNT\System32\ Drivers\etc\hosts file and add the following entry: 2.
34.34.130.1 wvs.ibm.com wvs
Installing
1. To begin the software installation, verify that the setupTTSConn.exe file is in the root directory of the IBM TTS Connector CD. 2. Then, either double-click the setupTTSConn.exe file, or launch the file from a command window. To use the command window, go to Start Programs Accessories Command Prompt and change directory to the letter containing the CD-ROM drive. 3. Follow the instructions on the installation panels. Note: For the Media Resource Control Protocol (MRCP) DNS value on the User Input panel, enter the fully-qualified host name of your WebSphere Voice Server. For example, setmrcp.wvs.ibm.com. Next type the number of channels the male voice will use, and the number of channels the female voice will use. Then select the TTS languages. Refer to Estimating resources for TTS engines on page 47 to ensure you allocated the proper number of channels. 4. When the TTS registration dialog appears after the Post-Install Summary panel, enter the following information: v TTS Name: IBM v Language Code: en-US For example: en-AU is Australian English fr-CA is Canadian French de-DE is German ja-JP is Japanese es-MX is Latin American Spanish zh-CN is Simplified Chinese en-GB is UK English en-US is US English v TTS Engine Language Code: en-US (this must match what you selected in step 3) v DLL Name: IBMTextToSpeech.DLL 5. Check the box for Male or Female Voice to reflect what you are using. 6. Enter the following information: v Voice Name: male (or female, matching the Genesys male/female panel) v Number of Channels: 16 (this number must match what you selected in step 3)
Chapter 4. Installing
87
7.
13.
Note: If you are installing another voice, repeat steps 5 and 6 and for your additional voice. Leave the Server Address and Server Port fields blank. If GVP NE is used and Directory Services are enabled, enter the Lightweight Directory Access Protocol (LDAP) user name and password. If you are not sure if Directory Services are enabled, check with your system administrator. If you have an LDAP server enabled, then entering the user name and password in this registration screen will register the IBM TTS Connector in the GVP configuration. Click OK. Repeat steps 4 through 8 for each language you selected in the earlier IBM TTS Connector registration panel. Click Yes when asked if you really want to register. Click Close. Restart the GVP: a. Open the Services dialog by going to Start Control Panel Administration Tools Services. b. Right-click the Watchdog service and select Restart. When the restarting progress bar closes, make a call to confirm that TTS is working properly.
If you need to update any of these fields after the installation process, refer to Configuring WebSphere Voice Server to support Genesys on page 112 for detailed instructions.
Prerequisites for the IBM TTS Connector for Genesys Voice Platform
This section lists any installation prerequisites for the IBM Text-to-Speech (TTS) Connector for Genesys Voice Platform (GVP). Before installing the TTS Connector on your Windows platform, GVP must be installed on the system.
88
$WVS_ROOT/uninstall/uninstall.sh $WVS_ROOT/uninstall/uninstall.sh %WVS_ROOT%\uninstall\uninstall.bat 2. Follow the screen options to uninstall WebSphere Voice Server, WebSphere Application Server, and your text-to-speech (TTS) and automatic speech recognition (ASR) languages. Note: The WebSphere Application Server may not appear in the uninstallation wizard list. It can be uninstalled later using its own uninstallation procedure. For reference, the commands to uninstall WebSphere Application Server are: For AIX and Linux:
$WAS_ROOT/_uninst/uninstall
For Windows:
%WAS_ROOT\_uninst\uninstall.exe
3. After the uninstall wizard finishes, remove the VoiceServer directory. 4. If the WebSphere Voice Server uninstallation program also uninstalled the WebSphere Application Server then remove the $WAS_HOME directory, such as /opt/WebSphere/AppServer. 5. Check for the entries listed in the vpd.properties file. Important: For users of WebSphere Voice Server 5.1.2 and earlier versions on Linux, remove the wvs_install_path/wvs.setenv line from your shells startup profile. For AIX users, the tuning changes applied to the root user will not be removed when you uninstall WebSphere Voice Server.
2. 3. 4. 5. 6.
Chapter 4. Installing
89
90
Uninstalling the IBM TTS Connector for Genesys Voice Platform for WebSphere Voice Server
This task describes how to uninstall the IBM TTS Connector for GVP for WebSphere Voice Server. 1. First, unregister the IBM TTS Connector: a. Navigate to the cn\bin\ folder in the TTS Connector installation directory, such as C:\Connector, on your Windows machine. b. Double-click the ttsreg.exe file to launch the registration panel. c. Type IBM as the TTS Vendor and click Enter. d. Click Unregister. e. Click Close. f. Restart Watchdog. 2. Go to the Start Control Panel and launch Add or Remove Programs. 3. Select the IBM TTS Connector from the list of programs displayed and click Remove. 4. Follow the instructions on the uninstallation panels.
Chapter 4. Installing
91
92
Chapter 5. Configuring
This topic covers the configuration of voice servers. After WebSphere Voice Server is installed, system administrators might want to modify several default settings. The Configuring topics in this documentation are geared towards your initial configuration and customization of the product, although you can adjust the product at any time. The product has been designed to require minimal setup, whenever possible. The primary interface for configuring WebSphere Voice Server is the administrative console. Below are the configuration tasks and topics for administrators of WebSphere Voice Server:
93
Preinstalling grammars
Preinstalling grammars improves the performance of a speech application, especially if the grammar is very large. Use the following steps to specify the location of a grammar file for preinstallation: 1. Select which voice server you want to configure (for example, wvssvr1_server1), and click that voice server hyperlink in the Voice Servers panel. 2. Click the Configuration tab. 3. Navigate to the Preinstalled grammars parameter in the ASR configuration table. Place your cursor in the input box and type the path and file name of the desired grammars. Multiple grammars can be separated by commas. Grammar examples:
http://vxidev1/pub/commands.grxml
or
http://vxidev1/pub/commands.grxml, http://vxidev1/pub/drinks.grxml
4. Click Apply to save your configuration changes and remain on the specific voice server view. Click OK to save your current configuration settings and return to the Voice Servers panel.
Languages installed
The Languages installed parameter in the ASR configuration table is a read-only field that specifies the recognition languages installed on your system. The languages for ASR are determined at installation.
Preloading lexicons
Like preloading grammars, preloading lexicons also improves the performance of a speech application. Use the following steps to specify the location of a lexicon to preload:
94
1. Select which voice server you want to configure (for example, wvssvr1_server1), and click that voice server hyperlink in the Voice Servers panel. 2. Click the Configuration tab. 3. Navigate to the Lexicon pre-loads parameter in the TTS configuration table. Place your cursor in the input box and type the path and file name of the desired lexicon. Multiple lexicons can be separated by commas. There is no specific extension for lexicon files; however, you must specify the URLs using either Hypertext Transfer Protocol (HTTP) or a local file protocol. Hypertext Transfer Protocol over Secure Socket Layer (HTTPS) is not supported. Lexicon examples:
http://www.example.com/lexicon.file
or
http://www.example.com/lexicon.file, http://www.example.com/pronunciation.file
Note: All preloaded lexicon files must be encoded as UTF-8. TTS does not support lexicons for Japanese and Simplified Chinese. 4. Click Apply to save your configuration changes and remain on the specific voice server view. Click OK to save your current configuration settings and return to the Voice Servers panel.
Voice(s) installed
The Voice(s) installed parameter in the TTS configuration table is a read-only field that indicates the current TTS voice(s) and languages installed on your system. TTS voices installed on your system are presented in a list, showing the languages, genders, and voice names. The languages for TTS are determined at installation. The voices that are available for use are denoted by an asterisk (*) on the administrative console. You can use the WebSphere Voice Server administration console to view voices installed on a specific voice server, or manually query the same information using the WebSphere Application Server wsadmin scripting tool. For examples, see Viewing the installed voices on a specific server on page 105.
Chapter 5. Configuring
This documentation provides information on creating custom scripts for configuration. These scripts only work on local servers and nodes. They cannot operate on a remote server or node. To administer a remote server, you can use the wsadmin tool connected to the Deployment Manager for the cell in which the target server or node is configured. For more details about scripting, refer to the WebSphere Application Server Network Deployment 5.1.x Information Center.
96
Important: Be sure to back up your WebSphere Voice Server configuration before adding a voice server to a cell using the backupVoiceServerConfig command-line utility. To add a node to a deployment environment using the administrative console, see Managing nodes.
Syntax
The command syntax is:
addNode deploymgr host deploymgr port -includeapps [paramter]
The deploymgr host and deploymgr port arguments are required. The default port number is 8879 for the default Simple Object Access Protocol (SOAP) port of the deployment manager. SOAP is the default Java Management Extensions (JMX) connector type for the command.
Parameters
The following parameters are available for the addNode command: -nowait Tells the addNode command not to wait for successful initialization of the launched node agent process. -quiet Suppresses the progress information that the addNode command prints in normal mode. -logfile filename Specifies the location of the log file to which information gets written. -trace Generates trace information into a file for debugging purposes.
-replacelog By default, the addNode command appends to the existing trace file. This option causes the addNode command to overwrite the trace file. -noagent Tells the addNode command not to launch the node agent process for the new node. -username name Specifies the user name for authentication if security is enabled. Acts the same as the -user option. -user name Specifies the user name for authentication if security is enabled. Acts the same as the -username option. -password password Specifies the password for authentication if security is enabled. -conntype type Specifies the JMX connector type to use for connecting to the deployment manager. Valid types are SOAP or RMI, which stands for Remote Method Invocation. -startingport portNumber Supports the specification of a port number to use as the base port number for all node agent and Java Messaging Service (JMS) server ports created
Chapter 5. Configuring
97
during the addNode command. With this support you can control which ports are defined for these servers, rather than using the default port values. The starting port number is incremented to calculate the port number for every node agent port and JMS server port configured during the addNode command. -help -? Prints a usage statement. Prints a usage statement.
Usage scenario
The following examples demonstrate correct syntax for Linux and AIX:
./addNode.sh testhost 8879 -includeapps ./addNode.sh testhost 8879 -includeapps (from the remote node command line) ./addNode.sh deploymgr 8879 -includeapps -trace (produces the addNode.log file) ./addNode.sh host25 8879 -includeapps -nowait (does not wait for a node agent process)
Where 8879 is the default port. Example output from a Linux machine:
[superuser@mynode bin] ./addNode.sh my_ibm_host 8879 -includeapps ADMU0116I: Tool information is being logged in file /opt/WebSphere/AppServer/logs/addNode.log ADMU0001I: Begin federation of node ibm_node with Deployment Manager at my_ibm_host:8879. ADMU0009I: Successfully connected to Deployment Manager Server: my_ibm_host:8879 ADMU0505I: Servers found in configuration: ADMU0506I: Server name: server1 ADMU2010I: Stopping all server processes for node ibm_node ADMU0510I: Server server1 is now STOPPED ADMU0024I: Deleting the old backup directory.
98
ADMU0015I: Backing up the original cell repository. ADMU0012I: Creating Node Agent configuration for node: ibm_node ADMU0014I: Adding node ibm_node configuration to cell: ibm_cell ADMU0016I: Synchronizing configuration between node and cell. ADMU0018I: Launching Node Agent process for node: ibm_node ADMU0020I: Reading configuration for Node Agent process:nodeagent ADMU0022I: Node Agent launched. Waiting for initialization status. ADMU0030I: Node Agent initialization completed successfully. Process id is: 2382 ADMU0523I: Creating queue manager for node ibm_node on server jmsserver ADMU0525I: Details of queue manager creation can be seen in the file: createMQ.ibm_node_jmsserver.log ADMU9990I: ADMU0300I: Congratulations! Your node ibm_node has been successfully incorporated into the ibm_cell cell. ADMU9990I: ADMU0306I: Be aware: ADMU0302I: Any cell-level documents from the standalone ibm_node configuration have not been migrated to the new cell. ADMU0307I: You might want to: ADMU0303I: Update the configuration on the ibm_cell Deployment Manager with values from the old cell-level documents. ADMU9990I: ADMU0003I: Node ibm_node has been successfully federated.
99
The removeNode command only removes the node-specific configuration from the cell. This command does not uninstall any applications that were installed as the result of executing an addNode command. Such applications can subsequently deploy on additional servers in the Network Deployment cell. As a consequence, an addNode command with the -includeapps option run after a removeNode command does not move the applications into the cell because they already exist from the first addNode command. The resulting application servers added on the node do not contain any applications. To deal with this situation, add the node and use the deployment manager to manage the applications. Add the applications to the servers on the node after it is incorporated into the cell. Depending on the size and location of the new node you remove from the cell, this command can take a few minutes to complete. Note: To remove a node from a deployment environment using the administrative console, see Managing nodes.
Syntax
The command syntax is:
removeNode [parameter]
Parameters
The following parameters are available for the removeNode command: -quiet Suppresses the progress information that the removeNode command prints in normal mode. -logfile fileName Specifies the location of the log file to which information is written. -replacelog Replaces the log file instead of appending to the current log. -trace Generates trace information into a file for debugging purposes.
-statusport portNumber Specifies that an administrator can set the port number for the node agent status callback. -username name Specifies the user name for authentication if security is enabled. Acts the same as the -user option. -user name Specifies the user name for authentication if security is enabled. Acts the same as the -username option. -password password Specifies the password for authentication if security is enabled. -force Cleans up the local node configuration regardless of whether you can reach the deployment manager for cell repository cleanup. After using the -force parameter, you can need to use the cleanupNode command on the deployment manager. -help Prints a usage statement.
100
-?
Usage scenario
The following example demonstrates correct syntax for Linux and AIX:
./removeNode.sh -quiet ./removeNode.sh -trace (produces the removeNode.log file)
Chapter 5. Configuring
101
The following Jacl code uses an WVSAdminConfig script command statement to update the number of automatic speech recognition (ASR) engines:
# Query WVS configuration object full name set tmpCfg [$AdminControl queryNames *:*,type=WVSAdminConfig] # Query current number of ASR engines set asreng [$AdminControl invoke $tmpCfg get com.ibm.voice.server.recognizer.asr.pool] puts stdout "Current ASR engines: $asreng" # Update number of ASR engines $AdminControl invoke $tmpCfg put {com.ibm.voice.server.recognizer.asr.pool 2 true} # Query new number of ASR engines set asreng [$AdminControl invoke $tmpCfg get com.ibm.voice.server.recognizer.asr.pool] puts stdout "New ASR engines: $asreng"
Example 2 The following Jacl code uses an WVSAdminConfig script to set TTS pre-lexicon load values:
# Query WVS configuration object full name set tmpCfg [$AdminControl queryNames *:*,type=WVSAdminConfig] # Query current TTS lexicon preload value set ttslex [$AdminControl invoke $tmpCfg get com.ibm.voice.server.synth.engine.preload-lexicons] puts stdout "Current TTS lexicon preloads: $ttslex" # Update TTS lexicon preload value $AdminControl invoke $tmpCfg put { com.ibm.voice.server.synth.engine.preload-lexicons file:///tmp/grammar/lexi1.lex true} # Query new TTS lexicon preload value set ttslex [$AdminControl invoke $tmpCfg get com.ibm.voice.server.synth.engine.preload-lexicons] puts stdout "New TTS lexicon preloads: $ttslex"
You should also review Modifying nested attributes with the wsadmin tool.
102
Note: The wild card (*) attribute does not have to be after a period. For example, com.ibm.voice.server.asr*. Usage: getList parameter wild card get Returns the value of the specified parameter name. Usage: get parameter put Updates the value for the specified parameter. Neither the parameter name nor the parameter value can be null. The last parameter must be true so that changes made are saved. Usage: put parameter parameter value true Remember: Configuration changes will only take effect after the voice server is stopped and restarted.
Sample code
The following sample shows you how to find and access the WVSAdminConfig MBean interface and services.
wsadmin> set wvscfg [$AdminControl queryNames *:*, type=WVSAdminConfig] WebSphere:cell=nextgen,name=WVSAdminConfig, mbeanIdentifier=cells/nextgen/ nodes/nextgen/servers/server1/serverl.xml#CustomService_1079378808193, type=WVSAdminConfig,node=nextgen,process=server1 wsadmin> $Help operations $wvscfg Operation java.util.Properties getList(java.lang.String) java.lang.String get(java.lang.String) void put(java.lang.String, java.lang.String) void put(java.lang.String, java.lang.String, boolean) void put(java.util.Properties, boolean) void backup(java.lang.String) void restore(java.lang.String) wsadmin> $AdminControl invoke $wvscfg get com.ibm.voice.server.rr.fetchthreads 11 wsadmin> $AdminControl invoke $wvscfg getList * {com.ibm.voice.server.synth.mrcp.Zhou-Hong.speech-language zh_CN} {com.ibm.voice.server.synth.mrcp.Shizuka.voice-age adult} {com.ibm.voice.server.synth.mrcp.Allison.voice-age adult} {com.ibm.voice.server.synth.mrcp.Shizuka.prosody-range 10} {com.ibm.voice.server.synth.mrcp.Daichi.prosody-rate 50} {com.ibm.voice.server.synth.mrcp.Shizuka.speech-language ja_JP} {com.ibm.voice.server.synth.mrcp.Shizuka.prosody-pitch 268} {com.ibm.voice.server.synth.mrcp.Andrew.prosody-rate 50} {com.ibm.voice.server.synth.mrcp.Zhou-Hong.prosody-range 10} {com.ibm.voice.server.rr.cachefilesize 9} {com.ibm.voice.server.synth.mrcp.Shizuka.prosody-rate 50} {com.ibm.voice.server.synth.mrcp.Zhou-Hong.prosody-pitch 137} {com.ibm.voice.server.rr.caching true} {com.ibm.voice.server.synth.mrcp.Daichi.voice-age adult} {com.ibm.voice.server.synth.mrcp.David.voice-age adult} {com.ibm.voice.server.synth.mrcp.Zhou-Hong.prosody-rate 50} {com.ibm.voice.server.synth.mrcp.Andrew.voice-age adult} . . . wsadmin> $AdminControl invoke $wvscfg put
Chapter 5. Configuring
103
{com.ibm.voice.server.rr.fetchthreads 20 true} wsadmin> $AdminControl invoke $wvscfg putProperties {{{com.ibm.voice.server.rr.fetchthreads 20} {com.ibm.voice.server.synth.pool-size 3} {com.ibm.voice.server.common.codec G711ulaw} } true}
This example uses Jacl to run the WebSphere Application Server wsadmin scripting tool.
wsadmin> set wvscfg [$AdminControl queryNames *:*,type=WVSAdminConfig] WebSphere:cell=nextgen,name=WVSAdminConfig, mbeanIdentifier=cells/nextgen/nodes/nextgen/servers/server1/serverl.xml#CustomService_1079378808193, type=WVSAdminConfig,node=nextgen,process=server1 wsadmin> $AdminControl invoke $wvscfg put {com.ibm.voice.server.synth.default-voice Andrew true}
This example uses Jacl to run the WebSphere Application Server wsadmin scripting tool.
wsadmin> set wvscfg [$AdminControl queryNames *:*,type=WVSAdminConfig] WebSphere:cell=nextgen,name=WVSAdminConfig, mbeanIdentifier=cells/nextgen/nodes/nextgen/servers/server1/serverl.xml#CustomService_1079378808193, type=WVSAdminConfig,node=nextgen,process=server1 wsadmin> $AdminControl invoke $wvscfg put {com.ibm.voice.server.synth.voices Andrew,Dawn true}
104
For more information about the installed and default voices for TTS, refer to Configuring TTS settings on page 94.
Configuration parameters
This section lists configuration parameters by categories of parameters related to the cache, automatic speech recognition (ASR) configuration, text-to-speech (TTS) configuration, and Real Time Streaming Protocol (RTSP) Bridge resources.
Cache-related parameters
WebSphere Voice Server has two different levels of caches for each server. It has a resource first level cache available to hold external files provided by the customer such as grammars, lexicon documents, and prerecorded audio files. It has a grammar second level cache available to hold the compiled grammars. These two levels of caches allow for the quick loading of grammars that are shared between ASR engines. The following parameters control the two levels of caching for each server. They identify the size and location of the caches. If you are developing your application, disable the first level cache until any application errors have been fixed.
Chapter 5. Configuring
105
General (first level) com.ibm.voice.server.rr.cachefilesize Default Cache Size (MB) Default general file cache capacity
9 MB
General (first level) com.ibm.voice.server.rr.fetchexpires Default Expiration Time Default value for all resources if expiration is not provided by the fetched resource
86400000 ms
General (first level) com.ibm.voice.server.rr.cachename Cache Location Location of the first level general cache
$WVS_ROOT/rrcache
Must be a valid US-ASCII directory on the local file system (optionally ending in the file separator character such as /) A positive integer value in megabytes
General (first level) com.ibm.voice.server.rr.cachememsize Memory Cache Size General first level memory cache capacity
2 MB
True
True/False
106
com.ibm.voice.server.recognizer.asr.pool-size Number of ASR engines to be started. Zero (0) means that no ASR support for that language is configured. Grammar preloads Note: The value for this parameter matches the number of Grammar pre-loads on the administrative console ASR configuration table. com.ibm.voice.server.recognizer.grammar.preload Defines a list of grammars to be preloaded when the system is started. If the URI represents the source of the grammar, it will be compiled before it is loaded. Empty A list of URIs separated by commas. For more information, refer to Preinstalling grammars on page 94.
Chapter 5. Configuring
107
U.K. English David adult male Dawn and Sally adult female voices Kate adult fifth generation female voice U.S. English Andrew adult male Allison and Tyler adult female voices Julie and Lisa adult fifth generation female voices Note: v The parameters in this table can be updated using scripting. v Depending on the capacity of your WebSphere Voice Server, the number of voices that can be loaded might be limited to one fifth generation voice and an additional voice. The configurable (unless otherwise indicated) parameters for these voices are listed below.
Table 13. TTS voice configuration parameters
Name Pitch Technical name and description com.ibm.voice.server.synth.mrcp.voicename.prosody-pitch Speakers base pitch in hertz (Hz) Default value Allison = 226Hz Andrew = 109Hz David = 105Hz Dawn = 200Hz Daichi = 101Hz Dieter = 98Hz Erika = 146Hz Julie = 192Hz Kate = 174Hz Lisa = 168Hz Louise = 180Hz Pierre = 124Hz Rafael = 128Hz Sally = 171Hz Shizuka = 268Hz Sofia = 182Hz Tyler = 226Hz Zhou-Hong = 137Hz Valid values 40 - 422Hz
108
Chapter 5. Configuring
109
Additional parameters for the systems voices are the ones that map to the TTS configuration table in the administrative console. For more information on the parameters from the console view, see Configuring TTS settings. Note: The parameters in this table can be updated using scripting or through the administrative console.
Table 14. Additional TTS voice configuration parameters
Name Available voices Technical name and description com.ibm.voice.server.synth.voices A list of voices installed in the TTS engine. Default value Installed voice names Valid values A list of voices separated by commas, to make available to Voice Server client requests. For more information on how to configure available voices, refer to Configuring default and available TTS voices. Lexicon preload com.ibm.voice.server.synth.engine.preloadlexicons A list of lexicon files to be pre-loaded for all TTS engines. Empty A list of URIs separated by commas.
110
Default voice com.ibm.voice.server.synth.default-voice Note: The value for this parameter Default voice name used by all TTS engines. matches the number of Default voice settings on the administrative console TTS configuration table.
Australian English = David French Canadian = Pierre German = Dieter Japanese = Daichi LA Spanish = Rafael Simplified Chinese = Zhou-Hong UK English = David US English = Andrew
A voice name available for use. For more information on default voices, refer to Default voice settings on page 95. For more information on how to configure available voices, refer to Configuring default and available TTS voices on page 104.
RTSP parameters
These parameters define the port and URL to use when contacting the WebSphere Voice Server from the qualified compatible Interactive Voice Response (IVR) system. Note: The parameters in this table can be updated using scripting.
Table 15. RTSP parameters
Name RTSP Port Technical name and description com.ibm.voice.server.rtspbridge.port The port from which the RTSP server listens RTSP Recognizer URL RTSP Synthisizer URL RTSP Teardown com.ibm.voice.server.rtspbridge.recourl RTSP media resource URL for the recognizer com.ibm.voice.server.rtspbridge.synthurl RTSP media resource URL for the synthesizer com.ibm.voice.server.rtspbridge.oneteardown Allows the server to accept one teardown from the client in order to clean up all resources. If you set the value to true, the server will only expect one RTSP Teardown. However, if you set it to false (the default), then the server will expect an RTSP Teardown for both ASR and TTS. RTSP Socket Time Out com.ibm.voice.server.rtspbridge.sockettimeout The amount of time RTSP Bridge will wait for a request from the client before timing out while in an established session 300 A positive integer Note: Set the default to value in seconds 0 when using WebSphere Voice Server with the Genesys Voice Platform (GVP) NE 6.5.4 or EE 6.5.5. G711ulaw G711ulaw or G711alaw False True/False /media/ synthesizer Any valid relative URL /media/ recognizer Any valid relative URL Default value 554 Valid values Any available port
Chapter 5. Configuring
111
112
/opt/WebSphere/AppServer/bin C:\Program Files\WebSphere\AppServer\bin 3. Make sure that Global Security is disabled on WebSphere Application Server. The script to configure WebSphere Voice Response must be run with WebSphere Application Server Global Security disabled. 4. Run the ./configureWVR.sh file for AIX or Linux, or the configureWVR.bat file for Windows platforms. 5. Stop and then restart WebSphere Application Server.
Configuring the IBM TTS Connector for Genesys Voice Platform for WebSphere Voice Server
This section identifies the configurable parameters in the IBMTextToSpeech.ini file. The IBMTextToSpeech.ini file is located in the cn\config folder in the TTS Connector installation directory on your Windows machine. The following parameters are replaced in the IBMTextToSpeech.ini by the TTS Connector installation. Please verify that these values are accurate for your installation. v SERVERNAME v TOTALCHANNELS v LOGDIR v LANG v FEMALECHANNELS v MALECHANNELS If you change any of these parameters, you need to stop and restart Windows Watchdog in order for the new values to take effect: 1. Access Watchdog from Start Control Panel Administrative Tools Services. 2. Select the Watchdog application from the list of Services. 3. Click Stop the service. 4. Run the TTS registration dialogue as documented in the installing the TTS Connector section. 5. Then click Start the service.
Table 16. IBMTextToSpeech.ini file parameters
Parameter MrcpUrl Description The URL of the synthesizer resource on the Media Resource Control Protocol (MRCP) server. mrcpurl=rtsp://SERVERNAME /media/synthesizer Channels The number of channels of all the voices used. Channels=TOTALCHANNELS The TOTALCHANNELS variable must be equal to the sum of NumTTSEngines of all the voices used. The number must equal the number of text-to-speech (TTS) engines configured in the server. Valid values The SERVERNAME is the name of your MRCP server.
Chapter 5. Configuring
113
114
Chapter 5. Configuring
115
116
Chapter 6. Administering
Administration is the set of tasks by which you modify, control, and monitor your voice server system for general use. The primary interface for system administration is the administrative console. However, a command line interface also provides these capabilities. Use the tasks and topics below when administering WebSphere Voice Server: v Using the administrative console Filtering on the administrative console on page 121 Enabling Security Monitoring voice servers and resource status on page 122 Starting voice servers on page 125 Stopping voice servers on page 125 v Managing using scripting on page 126 v Automatically restarting server processes on page 135 v Starting and stopping the IBM HTTP Server on page 142
To access the administrative console, you must start it and then log in. After you finish working in the console, save your work and log out.
Change all occurrences of port 9090 to the desired port for the console. Alternatively, shut down the other application that uses the conflicting port before starting the WebSphere Voice Server product. 2. A Login page appears after the console starts. Log into the console: a. Enter your user name (user ID). Changes made to server configurations are saved using the specified user ID. Temporary server configurations are saved to the user ID if there is a session timeout or if the user logs out without saving the configuration changes. A user ID lasts for the duration of the session for which it was used to log in. If you enter an ID that is already in use (and in session), you are prompted to do one of the following: v Force the existing user ID out of session. The configuration file used by the existing user ID is saved in the temporary area. v Wait for the existing user ID to log out or time out of the session. v Specify a different user ID. b. If the console is secure, you must also enter a password for the user name. The console is secure if the following steps have been performed: 1) Specified security user IDs and passwords 2) Enabled global security c. Click OK. 3. Stop the administrative console. Click Save on the console taskbar to save work that you have done and then click Logout to exit the console. Note that if you close the browser before saving your work, when you next log in under the same user ID, you can recover any unsaved changes.
What to do next
If you have difficulty using the administrative console on Linux, try using the Netscape Communicator 7.1 browser based on Mozilla 1.0. The browser release is
118
not officially supported by the WebSphere Voice Server product, but users have been able to access the console successfully with it. If you have difficulty using the administrative console on AIX, try using the Netscape Communicator 4.8 (or later) browser.
Login settings
Use this page to specify the user for the WebSphere Voice Server administrative console. If you are using global security, then you must also specify a password. Specifying a user allows you to resume work done previously with the product. After you type in a user ID, click OK to proceed to the next page and access the administrative console. To view this page, start the administrative console. The following are fields and settings relevant to the login window. User ID Specifies an entry identifying the user. The user ID must be unique to the administrative server. While logged in, any changes you make during the session are saved to a configuration identified by your user ID. The next time you log in to the console with your user ID, your work will be restored. If you are logging in from a client machine that currently has a browser open on the administrative console and you connect to the same server, your two connections might share the same HTTP session object, whether or not you are logging in under different user IDs. You must use two different types of browsers (for example, Microsoft Internet Explorer and Netscape Communicator) to log in to the administrative console from the same client machine in order to work from two different HTTP session objects, whether or not you use the same user ID. That is, if you need two concurrent sessions on the same client machine, access the administrative console from two different browser types. Note that you can use the same browser type to log in twice to the console, and use different user IDs. For example, suppose that Joe logs into the administrative console under the user ID joe on the physical host myhost1 using an Internet Explorer browser. Joe can log into the same console a second time using an Internet Explorer browser, but he must use a different user ID (such as peggy). Another user is currently logged in with the same user name Specifies whether to log out the user and continue work with the user ID specified or to return to the Login page and specify a different user ID or wait for the user to log out. This field appears if the user closed an administrative console browser window without logging out, then opened a new browser and tried accessing the administrative console, or if there is already another user logged in under the same name. Work with the master configuration When enabled, this setting specifies that you want to use the default administrative configuration and not use the configuration last used for the users session. Changes made to the users session since the last saving of the administrative configuration will be lost.
Chapter 6. Administering
119
This field appears only if the user changed the administrative configuration and then logged out or closed the Web browser without saving the changes. Recover changes made in prior session When enabled, this setting specifies that you want to use the same administrative configuration last used for the users session. Recovers unsaved changes to the administrative configuration during the last users session. This field appears only if the user changed the administrative configuration and then logged out without saving the changes.
120
console features mentioned in the WebSphere Application Server information center are available in WebSphere Voice Server. v Information on buttons v Page features v Console navigation v Taskbar actions For details specific to the WebSphere Voice Server administrative console, see Monitoring voice servers and resource status
Chapter 6. Administering
121
type *server* in the filter field and click Go. The name and status of each machine with server in the name are displayed the Overall Status table.
Voice Server Name This column displays the names of your voice servers using the convention node name_server1. Click a server link, such as wvssvr1_server1, to display detailed configuration and runtime status. Status An icon depicts the status of your individual voice servers. A Refresh icon updates the status icons for all voice servers when clicked. WebSphere Status Use the WebSphere Status area of the administrative console to view error and runtime event messages returned by WebSphere Voice Server. The WebSphere Status area displays along the bottom of the console and remains visible as you navigate from the Voice Servers panel to other pages.
122
The area displays two frames: WebSphere Configuration Problems and WebSphere Runtime Messages. Click Previous or Next to toggle between the frames. Click the Refresh icon in the upper-right of the area to refresh the information displayed. You can adjust the interval between automatic refreshes in the Preferences settings. WebSphere Configuration Problems Displays the number of workspace files. This frame also displays the number of problems with the administrative configuration for the user ID. Click the number to view detailed information on the problems. WebSphere Runtime Message Displays the number of messages returned by WebSphere Voice Server as well as the number of error messages (x icon), warning messages (! icon), and informational messages (i icon). Click the number of messages to view details.
Chapter 6. Administering
123
single-server environment when you install WebSphere Voice Server. To enable PMI services in WebSphere Application Server Network Deployment, see the topics below: v Single-server environment (enabled automatically when you install WebSphere Voice Server): Enabling performance monitoring services in the application server through the administrative console. v Mutliple-server environment (cell): Enabling performance monitoring services in the Node Agent through the administrative console . ASR Status This table provides general resource status for ASR resources. The first column shows the status item name, the second column provides a graphical or text display of the current status, and the third column presents a short description of the status item. The three status items are ASR Engines, Active Sessions, and Languages installed. The ASR engine status is shown using an icon. Click the ASR engine status icon to display the status name. v If the ASR engine status icon is a filled-in green arrow ( component is started. ), the
v If the ASR engine status icon is a white arrow outlined in green ( the component is partially started. v If the ASR engine status is a red X ( ), the component is stopped.
),
If the number of active ASR sessions is less than the total, then the WebSphere Voice Server is not running to its full configuration capacity. If this number is always less than the total, then the total number of ASR engines could be reduced to save system resources. If this number is always equal to the total, check the logs to make sure a sufficient number of ASR engines are configured. You might need to increase the total number of configured ASR engines. TTS Status This table provides general resource status for TTS resources. The first column shows the status item name, the second column provides a graphical or text display of the current status, and the third column presents a short description of the status item. The four status items are TTS Engines, Active Sessions, Default voice, and Voice(s) installed. TTS voices that are available for use are marked with an asterisk (*) on the administrative console. For details about the differences between installed voices and available voices for TTS, refer to Configuring default and available TTS voices on page 104. TTS engine status is shown using an icon. Click the TTS engine status icon to display the status name. v If the TTS engine status icon is a filled-in green arrow ( component is started. ), the
v If the TTS engine status icon is a white arrow outlined in green ( the component is partially started. v If the TTS engine status is a red X ( ), the component is stopped.
),
If the number of active TTS sessions is less than the total, then the WebSphere Voice Server is not running to its full configuration capacity. If
124
this number is always less than the total, then that the total number of TTS engines could be reduced to save system resources. If this number is always equal to the total, check the logs to make sure a sufficient number of TTS engines are configured. You might need to increase the total number of configured TTS engines.
Alternatively, you can use the startVoiceServer wsadmin sample to start a single voice server from the command line using wsadmin.
Alternatively, you can use the stopVoiceServer wsadmin sample to stop a single voice server from the command line using wsadmin.
Security
IBM WebSphere Voice Server uses the security infrastructure and mechanisms provided by WebSphere Application Server. WebSphere Application Server allows administrators to protect a server using two security features: Global Security and Java 2 Security. These security features are managed through the Security panel on the administrative console.
Chapter 6. Administering
125
Important: Java 2 Security cannot be enabled in order for WebSphere Voice Server to function properly. If you need security, enable Global Security in the WebSphere Voice Server administrative console. Do not select the option to enforce Java 2 Security. Before you enable global security read the technote about using Local operating system user registries. For detailed information about the WebSphere approach to security, refer to Welcome to Security in the WebSphere Application Server Information center.
Sample scripts
The sample scripts assist with common administrator tasks that can be performed using wsadmin scripts. These samples are provided for convenience and to serve as examples. They include the following: v getParam sample on page 127 v putParam sample on page 128 v startVoiceServer sample on page 129 v stopVoiceServer sample on page 130 v statusVoiceServer sample on page 131
126
v backupVoiceServerConfig sample on page 132 v restoreVoiceServerConfig sample on page 134 These sample scripts are installed into and are available from the samples directory in the root of your WebSphere Voice Server installation directory.
getParam sample
The getParam sample queries and displays WebSphere Voice Server configuration parameters from any node (or nodes) in the cell. Note: WebSphere Application Server must be started in order for this script to work correctly. If WebSphere Voice Server has global security enabled, then sample utilities must be updated to use name and password parameters. To use this sample on AIX or Linux, issue the following:
cd $WVS_ROOT/samples ./getParam.sh
Syntax
The samples syntax is as follows:
getParam parameter scope
parameter This variable is the parameter for which you are requesting information. A terminal wild card is allowed in a parameter name. Use the dollar ($) character to denote a wild card, such as com.ibm.$. scope This variable is the host name of the target. A terminal wild card is allowed in a parameter name. Use the dollar ($) character to denote a wild card, such as wvssrv$. Note: The scope is optional if you are not using Deployment Manager. The target defaults to localhost if no other value is specified. If you are using a Deployment Manager environment, you must define the scope.
Examples
getParam com.ibm.voice.server.synth.mrcp.Andrew.$ getParam com.ibm.voice.server.synth.mrcp.Andrew.$ ttssrv3 getParam com.ibm.voice.server.synth.mrcp.Andrew.$ ttssrv$
Other sample scripts putParam sample The putParam sample sets WebSphere Voice Server configuration parameters for any node (or nodes) in the cell. startVoiceServer sample The startVoiceServer sample starts WebSphere Application Server and WebSphere Voice Server.
Chapter 6. Administering
127
stopVoiceServer sample The stopVoiceServer sample stops the WebSphere Voice Server Enterprise Archive (EAR). statusVoiceServer sample The statusVoiceServer sample obtains the current status of a voice server. backupVoiceServerConfig sample The backupVoiceServerConfig sample script backs up the WebSphere Voice Server configuration and saves it to a zipped file. This sample should only be run on a machine where the WebSphere Voice Server has been installed. restoreVoiceServerConfig sample The restoreVoiceServerConfig sample restores the WebSphere Voice Server configuration captured in a previous backupVoiceServerConfig for the same machine. You should only run this sample on a machine where WebSphere Voice Server has been installed.
putParam sample
The putParam sample sets WebSphere Voice Server configuration parameters for any node (or nodes) in the cell. Note: WebSphere Application Server must be started in order for this script to work correctly. If WebSphere Voice Server has global security enabled, then sample utilities must be updated to use name and password parameters. To use this sample on AIX or Linux, issue the following:
cd $WVS_ROOT/samples ./putParam.sh
Syntax
The samples syntax is as follows:
putParam parameter value scope
parameter This variable is the parameter you want to set. value This variable is the value assigned to a specified parameter. Note: To set this variable to spaces ( ), use the value of null or NULL. scope This variable is the host name of the target. A terminal wild card is allowed in a parameter name. Use the dollar ($) character to denote a wild card, such as wvssrv$. Note: The scope is optional if you are not using Deployment Manager. The target defaults to localhost if no other value is specified. If you are using a Deployment Manager environment, you must define the scope.
128
Examples
putParam putParam putParam putParam com.ibm.voice.server.synth.pool-size 10 com.ibm.voice.server.synth.pool-size 10 ttssrv3 com.ibm.voice.server.synth.pool-size 10 ttssrv$ com.ibm.voice.server.recognizer.grammar.preload null
ttssrv$
Other sample scripts getParam sample The getParam sample queries and displays WebSphere Voice Server configuration parameters from any node (or nodes) in the cell. startVoiceServer sample The startVoiceServer sample starts WebSphere Application Server and WebSphere Voice Server. stopVoiceServer sample The stopVoiceServer sample stops the WebSphere Voice Server Enterprise Archive (EAR). statusVoiceServer sample The statusVoiceServer sample obtains the current status of a voice server. backupVoiceServerConfig sample The backupVoiceServerConfig sample script backs up the WebSphere Voice Server configuration and saves it to a zipped file. This sample should only be run on a machine where the WebSphere Voice Server has been installed. restoreVoiceServerConfig sample The restoreVoiceServerConfig sample restores the WebSphere Voice Server configuration captured in a previous backupVoiceServerConfig for the same machine. You should only run this sample on a machine where WebSphere Voice Server has been installed.
startVoiceServer sample
The startVoiceServer sample starts WebSphere Application Server and WebSphere Voice Server. On a base WebSphere Voice Server without Network Deployment, you must use the WebSphere Application Server startServer command line utility before running the startVoiceServer.jacl script. Use the startServer command as follows: To use this sample on AIX or Linux, issue the following:
cd WAS_ROOT/bin ./startServer.sh server1
On Windows:
cd WAS_ROOT\bin startServer server1
WAS_ROOT is where WebSphere Application Server is installed and server1 is the name of your default WebSphere Application Server. If WebSphere Voice Server has global security enabled, then sample utilities must be updated to use name and password parameters. To use this sample on AIX or Linux, issue the following:
cd $WVS_ROOT/samples ./startVoiceServer.sh
129
cd $WVS_ROOT\samples startVoiceServer
The startVoiceServer script performs either one or both of the following actions: v Starts the default WebSphere Application Server, server1. v If the WebSphere Voice Server EAR is not started, this utility will start it.
Syntax
The samples syntax is as follows:
startVoiceServer [parameter]
Parameters
The following parameter is available for the startVoiceServer sample: --help Prints a usage statement. Other sample scripts getParam sample The getParam sample queries and displays WebSphere Voice Server configuration parameters from any node (or nodes) in the cell. putParam sample The putParam sample sets WebSphere Voice Server configuration parameters for any node (or nodes) in the cell. stopVoiceServer sample The stopVoiceServer sample stops the WebSphere Voice Server Enterprise Archive (EAR). statusVoiceServer sample The statusVoiceServer sample obtains the current status of a voice server. backupVoiceServerConfig sample The backupVoiceServerConfig sample script backs up the WebSphere Voice Server configuration and saves it to a zipped file. This sample should only be run on a machine where the WebSphere Voice Server has been installed. restoreVoiceServerConfig sample The restoreVoiceServerConfig sample restores the WebSphere Voice Server configuration captured in a previous backupVoiceServerConfig for the same machine. You should only run this sample on a machine where WebSphere Voice Server has been installed.
stopVoiceServer sample
The stopVoiceServer sample stops the WebSphere Voice Server Enterprise Archive (EAR). If WebSphere Application Server has global security enabled, then sample utilities must be updated to use name and password parameters. To use this sample on AIX or Linux, issue the following:
cd $WVS_ROOT/samples ./stopVoiceServer.sh
130
This sample uses the stopVoiceServer.jacl script to perform the following actions: v If the WebSphere Voice Server EAR is started, this script will stop it. v If the -wvsonly parameter is not specified, then the default WebSphere Application Server will be stopped. For information on the WebSphere Application Server stopServer command, see the WebSphere Application Server Network Deployment 5.1.x Information Center.
Syntax
The sample syntax is as follows:
stopVoiceServer [parameter]
Parameters
The following parameters are available for the stopVoiceServer sample: -wvsonly Stops only the WebSphere Voice Server EAR. --help Prints a usage statement. Other sample scripts getParam sample The getParam sample queries and displays WebSphere Voice Server configuration parameters from any node (or nodes) in the cell. putParam sample The putParam sample sets WebSphere Voice Server configuration parameters for any node (or nodes) in the cell. startVoiceServer sample The startVoiceServer sample starts WebSphere Application Server and WebSphere Voice Server. statusVoiceServer sample The statusVoiceServer sample obtains the current status of a voice server. backupVoiceServerConfig sample The backupVoiceServerConfig sample script backs up the WebSphere Voice Server configuration and saves it to a zipped file. This sample should only be run on a machine where the WebSphere Voice Server has been installed. restoreVoiceServerConfig sample The restoreVoiceServerConfig sample restores the WebSphere Voice Server configuration captured in a previous backupVoiceServerConfig for the same machine. You should only run this sample on a machine where WebSphere Voice Server has been installed.
statusVoiceServer sample
The statusVoiceServer sample obtains the current status of a voice server. If WebSphere Application Server has global security enabled, then sample utilities must be updated to use name and password parameters. To use this sample on AIX or Linux, issue the following:
cd $WVS_ROOT/samples ./statusVoiceServer.sh
Chapter 6. Administering
131
This sample uses the statusVoiceServer.jacl script to perform the following actions: v Queries the status of the WebSphere Voice Server Enterprise Archive (EAR) application, WVS5.1-node. If the EAR is installed and started, and if the managed bean (MBean), WVSAdminControl is not found, the voice server is stopped. v If WebSphere Voice Server EAR is started, then the WVSAdminControl MBean getStatus operation is queried for additional runtime status such as Started, Stopped, Partial Start.
Syntax
The sample syntax is as follows:
statusVoiceServer [parameter]
Parameters
The following parameter is available for the statusVoiceServer sample: --help Prints a usage statement. Other sample scripts getParam sample The getParam sample queries and displays WebSphere Voice Server configuration parameters from any node (or nodes) in the cell. putParam sample The putParam sample sets WebSphere Voice Server configuration parameters for any node (or nodes) in the cell. startVoiceServer sample The startVoiceServer sample starts WebSphere Application Server and WebSphere Voice Server. stopVoiceServer sample The stopVoiceServer sample stops the WebSphere Voice Server Enterprise Archive (EAR). backupVoiceServerConfig sample The backupVoiceServerConfig sample script backs up the WebSphere Voice Server configuration and saves it to a zipped file. This sample should only be run on a machine where the WebSphere Voice Server has been installed. restoreVoiceServerConfig sample The restoreVoiceServerConfig sample restores the WebSphere Voice Server configuration captured in a previous backupVoiceServerConfig for the same machine. You should only run this sample on a machine where WebSphere Voice Server has been installed.
backupVoiceServerConfig sample
The backupVoiceServerConfig sample script backs up the WebSphere Voice Server configuration and saves it to a zipped file. This sample should only be run on a machine where the WebSphere Voice Server has been installed. If WebSphere Application Server has global security enabled, then sample utilities must be updated to use name and password parameters.
132
This sample uses the backupVoiceServerConfig.jacl script to perform the following actions: v The WebSphere Voice Server Enterprise Archive (EAR) will be stopped. This ensures that the configuration documents are not locked by WebSphere Voice Server and will not change while it is being backed up. You will have to restart WebSphere Voice Server EAR after the backup is complete. v If the backup_file parameter (where backup_file is a name you have selected) is not specified, then the script creates a file in the current directory using the following name (overwriting the file if it exists already): WVSConfig_yyyy-mm-dd.zip where yyyy is the current year, mm is the current month and dd is the current day v Uses the WVSAdminConfig managed bean (MBean) backup operation to store the Voice Server configuration into the backup_file (zipped file format). The backupVoiceServerConfig sample does not capture the product binaries or capture application data stored elsewhere (including on an HTTP Server). As such, the backupVoiceServerConfig utility is not a substitute for a comprehensive system backup facility.
Syntax
The sample syntax is as follows:
backupVoiceServerConfig [option]
Note: If you are backing up a server, you must specify the node name.
Parameters
The following parameters are available for the backupVoiceServerConfig sample: backup_file An optional variable that specifies the location of the backup file to which information gets written. --help Prints a usage statement. Other sample scripts getParam sample The getParam sample queries and displays WebSphere Voice Server configuration parameters from any node (or nodes) in the cell. putParam sample The putParam sample sets WebSphere Voice Server configuration parameters for any node (or nodes) in the cell. startVoiceServer sample The startVoiceServer sample starts WebSphere Application Server and WebSphere Voice Server.
Chapter 6. Administering
133
stopVoiceServer sample The stopVoiceServer sample stops the WebSphere Voice Server Enterprise Archive (EAR). statusVoiceServer sample The statusVoiceServer sample obtains the current status of a voice server. restoreVoiceServerConfig sample The restoreVoiceServerConfig sample restores the WebSphere Voice Server configuration captured in a previous backupVoiceServerConfig for the same machine. You should only run this sample on a machine where WebSphere Voice Server has been installed.
restoreVoiceServerConfig sample
The restoreVoiceServerConfig sample restores the WebSphere Voice Server configuration captured in a previous backupVoiceServerConfig for the same machine. You should only run this sample on a machine where WebSphere Voice Server has been installed. If WebSphere Application Server has global security enabled, then sample utilities must be updated to use name and password parameters. To use this sample on AIX or Linux, issue the following:
cd $WVS_ROOT/samples ./restoreVoiceServerConfig.sh
You must specify the name of the zip file generated by thebackupVoiceServerConfig utility. This sample uses the restoreVoiceServerConfig.jacl script to perform the following actions: v The WebSphere Voice Server Enterprise Archive (EAR) will be stopped. This ensures there are no sharing or read conflicts between the Voice Server and the restore processing. You will have to restart the Voice Server EAR after the restore is complete. v Uses the WVSAdminConfig managed bean (MBean) restore operation to restore the WebSphere Voice Server configuration from the backup_file (zip file format), overwriting the current configuration.
Syntax
The sample syntax is as follows:
restoreVoiceServerConfig backup_file [option]
Parameters
The following parameters are available for the restoreVoiceServerConfig sample: backup_file A required file name that specifies the location of the backup file to use for restoring the configuration.
134
--help Prints a usage statement. Other sample scripts getParam sample The getParam sample queries and displays WebSphere Voice Server configuration parameters from any node (or nodes) in the cell. putParam sample The putParam sample sets WebSphere Voice Server configuration parameters for any node (or nodes) in the cell. startVoiceServer sample The startVoiceServer sample starts WebSphere Application Server and WebSphere Voice Server. stopVoiceServer sample The stopVoiceServer sample stops the WebSphere Voice Server Enterprise Archive (EAR). statusVoiceServer sample The statusVoiceServer sample obtains the current status of a voice server. backupVoiceServerConfig sample The backupVoiceServerConfig sample script backs up the WebSphere Voice Server configuration and saves it to a zipped file. This sample should only be run on a machine where the WebSphere Voice Server has been installed.
135
2. Create the ibmhttpd and was scripts using the sample scripts below for reference and place them in the /etc/rc.d/rc5.d directory. Make sure to set the executable flag in the scripts. The ibmhttpd script is the system initialization script that is used to automatically start the IBM HTTP Server at system initialization time. The was script is the system initialization script that is used to automatically start WebSphere Application Server and WebSphere Voice Server. Each script should have options for starting and stopping the desired modules. Important: Be sure to validate the order in which the start and stop script links are run in the rc5.d directory. These links all have a Snn or Knn designation, where the nn is a numerical value which determines the start order for those scripts. The Snnibmhttpd and Snnwas scripts must have a value which will enable them to start after the network has been started. Similarly, the Knn scripts (if they exist) must be run before the network stop script. For example, the following four files would be in your rc5.d directory:
S1_ibmhttpd.sh S2_was.sh K1_was.sh K2_ibmhttpd.sh
At startup, the S1_ibmhttpd.sh script runs first, and then the S2_was.sh runs. During shutdown, the K1_was.sh script is called first, and then the K2_ibmhttpd.sh script. 3. Test the autostart scripts by rebooting your system and verifying that the desired processes have started.
136
Important: Each of these commands has two of the hyphen characters repeated. A single hyphen will not work when using the full text name of the tag. The chkconfig --add commands add the script entries into the services table and the chkconfig --level commands indicate the runlevels at which Red Hat should automatically run the scripts. 4. Test the autostart scripts by rebooting your system and verifying that the desired processes have started.
Important: Each of these commands has two of the hyphen characters repeated. A single hyphen will not work when using the full text name of the tag. The chkconfig --add commands add the script entries into the services table and the chkconfig --set commands indicate the runlevels at which SUSE should automatically run the scripts. The chkconfig --set commands create links in the rc5.d directory which are run at system initialization and shutdown. These links all have a Snn or Knn designation, where the nn is a numerical value which determines the start order for those scripts. Important: Each of these commands have two of the hyphen characters repeated. A single hyphen will not work when using the full text name of the tag. Also, be sure to validate the order in which the start and stop script links are run in the rc5.d directory. The Snnibmhttpd and Snnwas scripts must have a value which will enable them to start after the network has been started. Similarly, the Knn scripts (if they exist) must be run before the network stop script. For example, the following four files would be in your rc5.d directory:
Chapter 6. Administering
137
At startup, the S1_ibmhttpd.sh script runs first, and then the S2_was.sh runs. During shutdown, the K1_was.sh script is called first, and then the K2_ibmhttpd.sh script. 4. Test the autostart scripts by rebooting your system and verifying that the desired processes have started.
138
For a standalone WebSphere Voice Server system, the start script only needs to start the default server1. The sample script described is listed in the following example. Example of a was autostart script:
#!/bin/bash # # apache # # description: Start up the WebSphere Application Server. RETVAL=$? WAS_HOME="/usr/WebSphere/AppServer" case "$1" in start) if [ -f $WAS_HOME/bin/start_server1.sh ]; then echo $"Starting IBM WebSphere Application Server" $WAS_HOME/bin/start_server1.sh fi ;; stop) if [ -f $WAS_HOME/bin/stopServer.sh ]; then echo $"Stop IBM WebSphere Application Server" $WAS_HOME/bin/stopServer.sh server1 fi ;; status) if [ -f $WAS_HOME/bin/serverStatus.sh ]; then echo $"Show status of IBM WebSphere Application Server" $WAS_HOME/bin/serverStatus.sh server1 fi ;; *) echo $"Usage: $0 {start|stop|status}" exit 1 ;; esac exit $RETVAL
Once you have federated your WebSphere Voice Server into a deployment manager cell, you need to start the node agent as well as the default server1. Note that this script also issues the iptables command which is needed by the WebSphere Edge Component Load Balancer. If you do not use Load Balancer, be sure to remove that line. Example of a wasNode script:
#!/bin/bash # # apache # # description: Start up the WebSphere Application Server. RETVAL=$? WAS_HOME="/usr/WebSphere/AppServer" # added line to ensure that environment variables are set correctly . /usr/WebSphere/VoiceServer/wvs.setenv case "$1" in start) if [ -f $WAS_HOME/bin/start_server1.sh ]; then echo $"Starting IBM WebSphere Node Agent and Application Server" $WAS_HOME/bin/start_nodeagent.sh $WAS_HOME/bin/start_server1.sh # added line to set iptables entry for Edge Load Balancer support iptables -t nat -A PREROUTING -d 9.42.171.99 -j REDIRECT fi ;;
Chapter 6. Administering
139
stop) if [ -f $WAS_HOME/bin/stopServer.sh ]; then echo $"Stop IBM WebSphere Application Server" $WAS_HOME/bin/stopServer.sh server1 $WAS_HOME/bin/stopNode.sh fi ;; status) if [ -f $WAS_HOME/bin/serverStatus.sh ]; then echo $"Show status of IBM WebSphere Application Server" $WAS_HOME/bin/serverStatus.sh server1 fi ;; *) echo $"Usage: $0 {start|stop|status}" exit 1 ;; esac exit $RETVAL
For a standalone WebSphere Voice Server system, the start script only needs to start the default server1. The sample script described is listed in the following example. Example of a was autostart script:
140
#!/bin/bash # # apache # # chkconfig: 5 90 10 # description: Start up the WebSphere Application Server. RETVAL=$? WAS_HOME="/opt/WebSphere/AppServer" case "$1" in start) if [ -f $WAS_HOME/bin/start_server1.sh ]; then echo $"Starting IBM WebSphere Application Server" $WAS_HOME/bin/start_server1.sh fi ;; stop) if [ -f $WAS_HOME/bin/stopServer.sh ]; then echo $"Stop IBM WebSphere Application Server" $WAS_HOME/bin/stopServer.sh server1 fi ;; status) if [ -f $WAS_HOME/bin/serverStatus.sh ]; then echo $"Show status of IBM WebSphere Application Server" $WAS_HOME/bin/serverStatus.sh server1 fi ;; *) echo $"Usage: $0 {start|stop|status}" exit 1 ;; esac exit $RETVAL
Once you have federated your WebSphere Voice Server into a deployment manager cell, you need to start the node agent as well as the default server1. Note that this script also issues the iptables command which is needed by the WebSphere Edge Component Load Balancer. If you do not use Load Balancer, be sure to remove that line. Example of a wasNode script:
#!/bin/bash # # apache # # chkconfig: 5 90 10 # description: Start up the WebSphere Application Server. RETVAL=$? WAS_HOME="/opt/WebSphere/AppServer" # added line to ensure that environment variables are set correctly . /opt/WebSphere/VoiceServer/wvs.setenv case "$1" in start) if [ -f $WAS_HOME/bin/start_server1.sh ]; then echo $"Starting IBM WebSphere Node Agent and Application Server" $WAS_HOME/bin/start_nodeagent.sh $WAS_HOME/bin/start_server1.sh # added line to set iptables entry for Edge Load Balancer support iptables -t nat -A PREROUTING -d 9.42.171.99 -j REDIRECT fi ;; stop) if [ -f $WAS_HOME/bin/stopServer.sh ]; then echo $"Stop IBM WebSphere Application Server" $WAS_HOME/bin/stopServer.sh server1
Chapter 6. Administering
141
$WAS_HOME/bin/stopNode.sh fi ;; status) if [ -f $WAS_HOME/bin/serverStatus.sh ]; then echo $"Show status of IBM WebSphere Application Server" $WAS_HOME/bin/serverStatus.sh server1 fi ;; *) echo $"Usage: $0 {start|stop|status}" exit 1 ;; esac exit $RETVAL
On a Windows platform
Accept the default WebSphere Voice Server configuration, and install IBM HTTP Server Apache as a Windows service, so that IBM HTTP Server starts automatically with your machine, and keeps running after you log off. Once Apache for Windows is configured as a Windows Service, follow the samples below to manage starting and stopping IBM HTTP Server. Remember: Replace the version of the service name with the one appropriate for your installation.
142
Issue the following command from a console window to start the IBM HTTP Server: NET START IBM HTTP SERVER 1.3.28 Confirm that IBM HTTP Server started successfully by opening a browser and typing in your server name in the address box. Issue the following command from a console window to stop the IBM HTTP Server: NET STOP IBM HTTP SERVER 1.3.28 If the IBM HTTP Server does not start, or you did not accept the default WebSphere Voice Server configuration to install IBM HTTP Server Apache as a Windows service, do the following: 1. Change directory to IBM HTTP Server\bin. 2. Run the apache.exe file from a command line.
Chapter 6. Administering
143
144
Chapter 7. Tuning
Use the topic below to adjust the configuration and improve the performance of WebSphere Voice Server.
Tuning WebSphere Voice Server for Avaya, Cisco, and WebSphere Voice Response
Tune the WebSphere Voice Server configuration parameters to the following values: v The number of ASR engines should equal the number of channels. v The number of TTS engines should equal half the number of channels.
145
Note: The number of engines listed above are suitable for initial settings. Your individual configuration will depend on your application requirements.
v The RTSP Socket Timeout parameter should equal 0 (com.ibm.voice.server.rtspbridge.sockettimeout=0). This value should already be set by the configureGenesys.sh or configureGenesys.bat file. Also, if you are using Genesys Voice Platform (GVP) 7.0.3 with voice over IP (VoIP) only, and your TTS delay to first audio is long, then configure the TTS audio size using the following steps: 1. Open the Genesys Voice Portal Manager (VPM) and the Server Explorer. Note: You can access the Server Explorer by going to http://localhost/VPM, and then clicking Server Explorer. 2. Expand the link on the left and navigate to the tts_mrcp link. 3. Click the tts_mrcp link. On the right you should see a panel titled tts_mrcp. 4. Click Add New Attribute. The panel refreshes with two new fields. 5. In the Name column, enter minaudiodnldsize, with a value of 2048 and click Save. You now have a new attribute on this screen called Minimum Audio Download Size in Kb and it is set to 2048. 6. Restart the Watchdog for the new value to take effect.
146
For more information on how to change the Maximum Heap Size or Initial Heap Size, refer toJava virtual machine settings in the WebSphere Application Server Information Center.
Tuning AIX
The information in this section applies to tuning WebSphere Voice Server version 5.1.3 only. The tuning in this section was applied during your installation of WebSphere Voice Server 5.1.3. The installation added the following commands to the WebSphere Voice Server section of your /etc/profile file:
ulimit -n 4096
Note: If you have modified the default values of ulimit to be greater than 4096, then your default value will remain in the /etc/profile file. The installation may have added the following commands to the WebSphere Voice Server section of your /etc/rc.net file.
no no no no no -o -o -o -o -o tcp_timewait=2 tcp_nodelayack=1 sb_max=1048576 udp_recvspace=1048576 udp_sendspace=1048576
Make note of the following conditions that affect these command settings: v If tcp_timewait is not changed from the default, then it equals 1 (tcp_timewait=1). If the current value for tcp_timewait is greater than 2, then the setting is changed to 2 (tcp_timewait=2). v If sb_max is less than 1048576, it will be set to in order to 1048576 (sb_max=1048576). v The values for udp_recvspace and udp_sendspace are always set to 1048576 (udp_recvspace=1048576 and udp_sendspace=1048576). In addition, the installation set the following settings for the user root account on which WebSphere Application Server runs:
Soft Soft Soft Soft Hard Hard Hard Hard FILE Size CPU Time STACK Size CORE File Size FILE Size CPU Time STACK Size CORE File Size -1 -1 -1 -1 -1 -1 -1 -1
Important: If you are using an Interactive Voice Response (IVR) system on AIX with WebSphere Voice Server, such as WebSphere Voice Response, make sure that you set no -o tcp_nodelayack=1 in the /etc/rc.net file on the IVR for the best results.
Chapter 7. Tuning
147
Important: The tuning recommended in this section is not persistent for all command windows or after a reboot unless permanently saved or added to the startup profile. Edit your startup file to ensure the commands run on boot up. The following services should be stopped and disabled.
Table 17. Linux services Service description Redundant Array of Independent Disks (RAID) Support Common UNIX Printer System Background Scheduler Send Mail Red Hat Network Support (this service does not apply to SUSE) Service name mdmpd cups crond sendmail rhnsd
To disable these services on Red Hat, use the following steps: 1. Select System Settings Server Settings Services from the main menu to get a list of services. 2. Stop each service, as applicable. 3. Remove the check mark beside each service you want to disable. 4. Save your updated configuration before exiting. To disable these services on SUSE, issue the following command for each service you want to disable, where service_name is the name of a service listed in the table above:
service service_name stop
Note: Disable sendmail on SUSE by issuing: chkconfig sendmail off Remember: The Linux firewall must be disabled for the Interactive Voice Response (IVR) to communicate with WebSphere Voice Server. Set the following minimal values for Linux by issuing the following commands: v ulimit -n 4096 v sysctl -w net.core.rmem_default=8388608 v sysctl -w net.core.wmem_default=8388608 v sysctl -w net.core.rmem_max=16000000 v sysctl -w net.core.wmem_max=10485760 v sysctl -w net.ipv4.tcp_keepalive_time=30 Restriction: Do not set this last tuning parameter when using the Genesys Voice Platform (GVP) NE 6.5.4 or EE 6.5.5.
148
The pthread lib in SUSE 8.0 with SP2a limits a process to only 1024 threads. To overcome this limitation, SUSE provides an updated pthread.lib in the UnitedLinux Extension Pack for Lotus Domino. For optimal tuning with SUSE and WebSphere Voice Server, complete the following steps: 1. Download and install the UnitedLinux Extension Pack for Lotus Domino. If the link has moved, perform a search using, UnitedLinux Extension Pack for Lotus Domino for the updated link. 2. Update the wvs.setenv script file provided by the WebSphere Voice Server installation to include the updated pthread.lib. For example:
export LD_LIBRARY_PATH= /opt/dominowrap/domino6:$SPCH_ROOT/bin:$LD_LIBRARY_PATH export LD_PRELOAD= /opt/dominowrap/domino6/libpthread.so:/opt/dominowrap/domino6/librt.so
3. In the right pane of the registry editor, look for the TcpTimedWaitDelay value name. If it is not there, add it by selecting Edit New DWORD Value from the menu bar. Type the value name TcpTimedWaitDelay in the name box that appears with the flashing cursor. Note: If you do not see the a flashing cursor and New Value # inside the box, right-click inside the right panel and select Rename from the menu, then type the value name TcpTimedWaitDelay in the name box. 4. Repeat this step for the following value names: MaxUserPort, MaxHashTableSize, and MaxFreeTcbs 5. Double-click inside the right pane again to set the value of TcpTimedWaitDelay. Select Decimal as the Base, and enter 30 in the Value data field. 6. Repeat step 5 for the following value names with the indicated value data: v MaxUserPort = 65534 (Decimal) v MaxHashTableSize = 65536 (Decimal) v MaxFreeTcbs = 16000 (Decimal) See the Microsoft Web site for additional information about setting TCP/IP parameters in the registry.
Chapter 7. Tuning
149
150
Note: Setting this value between 6 to 10 seconds should ensure that the WebSphere Voice Server is responding. Any time set over 10 seconds may result in an MRCP client disconnect. If you have further questions, or need additional MRCP client configurations, issue the mrcp client ? command for a listing of all available MRCP client configuration commands.
Chapter 7. Tuning
151
152
Chapter 8. Troubleshooting
As an activity, troubleshooting or problem determination encompasses a wide range of tasks that might need to be performed at any phase in product usage. In addition to built-in preventative measures, the product provides a variety of tools to make problem determination easier. The troubleshooting section of the documentation helps you understand why your voice server or product installation is not working, and helps you resolve the problem. To effectively troubleshoot a WebSphere Voice Server problem, use the following steps: 1. Understand messages and alarms 2. Understand log messages 3. Enable and monitor trace 4. Collect information for IBM Support You may also troubleshoot according to the component of your WebSphere Voice Server and its environment, or according the particular task you are attempting (such as installation or administration). Additional information on both approaches is also provided to streamline your troubleshooting process: v Troubleshoot by component v Troubleshoot by task type
153
Several tools provided with WebSphere Voice Server provide messages and alarms to alert administrators about system events: v Administrative console Manage and view log and trace files and view alarms (console messages). The Voice Servers panel automatically refreshes every 60 seconds, but may be configured to refresh on a different schedule. v Voice Trace Analyzer Examine recognition data in multiple trace.log files to build a comprehensive overview of your systems recognition performance and improve the awareness of recognition problems. v WebSphere Application Server system log Errors, warnings, and informational messages. The log file is located at WAS_ROOT/logs/server1/ SystemOut.log. System logs cannot be disabled by a system administrator; they are always created and used anytime the system is operational. Trace logs can be enabled or disabled as needed by a system administrator or by technical support.
Messages by component
This section describes the WebSphere Voice Server messages, which use a 10-character format. CWVSSNNNNT Where: CWV = IBM-registered three-character prefix identifying WebSphere Voice Server. The elements of the CWV code appear below: v SS = Used to identify the WebSphere Voice Server components within the product. See the chart below for more information. v NNNN = Numeric message ID (4-digits). v T = Severity type (Information, Warning, or Error). Click a component identifier below to see all the messages for that component. Note: The message number is any 4-digit number associated with the log message.
Table 18. Component log messages Component identifier CWVAB on page 155 CWVAC on page 160 CWVAE on page 164 Component ASR Bean ASR Control Interface ASR Engine
154
Table 18. Component log messages (continued) Component identifier CWVCC on page 240 CWVGC on page 241 CWVGM on page 244 CWVMC on page 244 CWVMD on page 250 CWVPT on page 252 CWVRB on page 259 CWVRR 0000 - 4999 on page 269 CWVRR 5000 - 9999 on page 270 CWVRT on page 272 CWVSB on page 276 CWVSM on page 281 CWVSY 1000 - 2999, 9000 - 9999 on page 281 CWVSY 3000 - 3999 on page 287 CWVTE on page 289 TTS Engine RTSP Bridge Synthesizer Session Manager System Management and Configuration Component Common Grammar Compiler Grammar Manager Media Converter MRCP Message Dispatcher Product Tools Recognizer Resource Resolver
CWVAB
CWVAB0001E: ASR allocation failed: VALUE_0
Explanation: Failed to allocate an ASR resource. User response: Check for additional errors in the SystemOut.log file to further diagnose the problem. Refer to Troubleshooting section of the Information Center for possible solutions.
Chapter 8. Troubleshooting
155
index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
156
157
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAB0017E: Invalid ASR Engine codepage VALUE_0 - using default character set VALUE_1
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAB0018W: ASR Engine codepage not provided, using default character set VALUE_0
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
158
Chapter 8. Troubleshooting
159
CWVAC
CWVAC0015E: VALUE_0 Socket error detected on a VALUE_1 function call - return code: VALUE_2, reason: VALUE_3
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
160
Chapter 8. Troubleshooting
161
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
162
CWVAC0031E: VALUE_0 Invalid ASRControl Message Handler State VALUE_1 for VALUE_2 request
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAC0033E: VALUE_0 Unrecoverable condition detected during ASR processing - ASRControl process preparing for shutdown
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAC0036E: VALUE_0 VALUE_1 data is missing from the body of the ASR Request message
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
163
CWVAE
CWVAE0001W: %s %s: Failed to allocate storage for %s
Explanation: Insufficient virtual memory for the process. User response: Check available paging space.
164
165
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
166
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0017W: %s %s: Number of baseform spellings %d does not match number of offsets %d
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0018W: %s %s: Failed to load sounds like spelling for %s, number of baseforms do not match
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
167
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
168
CWVAE0026W: %s %s: Questions file %s length %d is not a multiple of the number of phones %d.
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0027W: %s %s: Questions file %s length %d is not a product of the number of phones %d and the number of questions %d
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0028W: %s %s: Number of trees %d in %s does not match number in header %d from %s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
169
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
170
Chapter 8. Troubleshooting
171
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0042W: %s %s: Mode specified is 0x%x, but no personal or temp pool exists
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0044W: %s %s: Acoustic Addword not enabled, no Acoustic-File entry in task file
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0045W: %s %s: Acoustic Addword only using the first of the %d utterances specified
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/
172
index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0047W: %s %s: Failed to add spelling %s to temp pool for acoustic addword
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
173
CWVAE0056W: %s %s: Failed to auto-addword using sounds-like spelling %s, return code %d
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0057W: %s %s: Failed to make word from file %s, return code %d
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
174
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0061W: %s %s: Specified tags span utterance boundary when processing spelling %s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0062W: %s %s: Specified tag (%d:%d) not associated with any vocabulary owned by client when processing spelling %s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/
Chapter 8. Troubleshooting
175
index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0063W: %s %s: Vocabulary %s associated with tag (%d:%d) has no appendix when processing spelling %s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
176
CWVAE0070W: %s %s: Error return code %d from dc_iter, forcing microphone off
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0071W: %s %s: Failed to define vocabulary for silence word %s. Baseform may be missing or empty
Explanation: This is an unexpected error. The cause cannot be immediately determined.
Chapter 8. Troubleshooting
177
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
178
Chapter 8. Troubleshooting
179
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0081W: %s %s: Failed to remove words from vocabulary %s, return code %d
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
180
Chapter 8. Troubleshooting
181
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
182
183
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
184
CWVAE0104W: %s %s: Failed to accept socket connection on listen socket %d, errno %d
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
185
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
186
index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0114W: %s %s: Missing audio video library name, processing audio only
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0115W: %s %s: Audio visual dimension %d does not match feature dimension %d
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
187
CWVAE0116W: %s %s: V dimensionality %d does not match MSHMM visual prototype dimension %d
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0118W: %s %s: Initialization of audio compression failed, return code %d - continuing without audio compression
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
188
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0125W: %s %s: Audio buffer overflow, audio buffer size %d, audio bytes returned %d
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
189
190
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
191
192
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0145W: %s %s: Map buffer contains %d bytes but expected %d (4 * number of words)
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0146W: %s %s: Specifying a map file is valid only when creating new files
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
193
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
194
CWVAE0154W: %s %s: Failed to build c0 histogram with %d samples limited (%f to %f)
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
195
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
196
197
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
198
CWVAE0171W: %s %s: Missing pronunciations for external vocabulary %s in file %s needed by vocabulary %s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
199
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
200
CWVAE0181W: %s %s: Vocabulary %s is already defined, but needs to be defined as an external by vocabulary %s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
201
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
202
203
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
204
CWVAE0198W: %s %s: Read %d bytes from %s, but expected %d, return code %d
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0199W: %s %s: Number of rows (%d) in file %s is less than the minimum rank position (%d or %d)
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
205
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0203W: %s %s: Failed to map shared acoustic image (%s) from file %s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
206
CWVAE0209W: %s %s: Failed to determine the name of the initial mean normalization file
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
207
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
208
209
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
210
211
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
212
CWVAE0236W: %s %s: The next letter sequence is not in the range 0-31
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0239W: %s %s: Attempting to delete overridden sel %d (word %d V%d) with %d extensions
Explanation: This is an unexpected error. The cause cannot be immediately determined.
Chapter 8. Troubleshooting
213
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
214
Chapter 8. Troubleshooting
215
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
216
Chapter 8. Troubleshooting
217
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0260W: %s %s: Specified userid %s does not match currently initialized userid %s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0261W: %s %s: Specified enrollid %s does not match currently initialized enrollid %s.
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/
218
index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0262W: %s %s: Specified taskid %s does not match currently initialized taskid %s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0263W: %s %s: Specified audio type %s does not match currently initialized audio type %s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0264W: %s %s: Specified audio library %s does not match currently initialized audio library %s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
219
220
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0274W: %s %s: Reserved flags have been set to 0x%x by client 0x%x
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
221
CWVAE0275W: %s %s: Invalid format in archive file %s, header id %s, header version %d
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0278W: %s %s: Concurrent recognition session not supported with current enrollment session
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
222
CWVAE0279W: %s %s: Requested userid %s is currently being used exclusively by another application
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
223
index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
224
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
225
226
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0299E: %s %s: Failed to connect to listening socket for internal messages, errno %d
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
227
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0305W: %s %s: Current api version %s does not match client api version %s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0306W: %s %s: Current run directory %s does not match specified run directory %s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
228
CWVAE0309W: %s %s: Disk space required for training (%4.1f), exceeds available disk space (%4.1f)
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
229
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0314W: %s %s: Calculated CRC value 0x%x does not match stored CRC value 0x%x in archive %s.
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
230
231
index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0321W: %s %s: Failed to determine asynchronous notification socket handle for application %s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
232
CWVAE0325W: %s %s: A SMAPI session is not open. Unable to send requests or receive replies
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0329W: %s %s: SM Session API send or receive error: %d, disconnecting from engine
Explanation: This is an unexpected error. The cause cannot be immediately determined.
Chapter 8. Troubleshooting
233
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0331W: %s %s: Failed to establish a connection with the speech recognition engine, connect code %c
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
234
235
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0406W: %s %s: Failed detailed match for silence at (%d %d %d) with return code %d
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVAE0409W: %s %s: LM n-gram file size is %d but the index file expects %d
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
236
237
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
238
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
239
CWVCC
CWVCC0001E: Failed to register control channel with selector channel was closed - port number: VALUE_0
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVCC0002E: Atypical unrecoverable error in selector - leaving listener thread - reason: VALUE_0
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
240
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVGC
CWVGC2001E: Compiler property name is null
Explanation: Error occurred while setting the compilers property. User response: No user action needed.
Chapter 8. Troubleshooting
241
CWVGC2005E: Cannot set null value for compilers object property VALUE_0
Explanation: Error occurred while setting the compilers object property. User response: No user action needed.
242
CWVGC2035E: VALUE_0 property must be set to build package for voice grammar
Explanation: Cannot build a compiled grammar package without the required property. User response: No user action needed.
Chapter 8. Troubleshooting
243
CWVGM
CWVGM1000E: Grammar document declares invalid meta data
Explanation: The application provided grammar declares invalid meta data attributes using the meta tag. User response: Ensure the syntax conforms to the specified SRGS grammar format.
CWVMC
CWVMC0001W: Failed to load configuration parameter VALUE_0 defaulting to VALUE_1
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
244
CWVMC0002E: The Media Converter TTS subsystem was unable to send audio output to the RTP host VALUE_0 and port VALUE_1
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVMC0003W: The Media Converter TTS subsystem experienced VALUE_0 underrun(s) of audio data from the TTS engine. At time to send TTS output - no audio data was available - additional info follows: media server port=VALUE_1, media client port=VALUE_2
Explanation: The WebSphere Voice Server may be over capacity and not able to produce the RTP audio stream for the SYNTHESIZER resource at a consistent interval to the MRCP client. User response: Verify that the tuning parameters for your operating system are applied as described in the section on tuning operating systems in the WebSphere Voice Server Information Center. Also, reduce the number of expected speech resources or lessen the MRCP client load on WebSphere Voice Server.
CWVMC0004W: The Media Converter TTS subsystem was unable to create audio trace file VALUE_0
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVMC0005W: The Media Converter TTS subsystem was unable to send a speak complete message to the TTS engine process
Explanation: This warning can occur if an MRCP session teardown is issued to the synthesizer while a turn of audio is ending. User response: If the MRCP synthesizer session was undergoing a teardown when this occurred - ignore the warning.
CWVMC0006W: The Media Converter TTS subsystem was unable to write to audio file trace VALUE_0
Explanation: This is an unexpected error. The cause cannot be immediately determined.
Chapter 8. Troubleshooting
245
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVMC0007W: The Media Converter was unable to obtain the ASR installation config value
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVMC0008W: The Media Converter was unable to obtain the TTS installation config value
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVMC0009W: The Media Converter was unable to obtain the ASR buffer size config value
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVMC0010W: The Media Converter ASR subsystem was unable to deliver hotword bargein event
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/
246
index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVMC0011W: The Media Converter ASR subsystem was unable to deliver speech bargein event
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVMC0012W: The Media Converter ASR subsystem received 0 RTP packets on port=VALUE_0 recognize mode=VALUE_1
Explanation: The WebSphere Voice Server did not receive any RTP packets from the MRCP client during the RECOGNIZE request for the specified session. The RECOGNIZE request was processed correctly. However, the RECOGNITIONCOMPLETE event that the MRCP client will receive may contain unexpected results since WebSphere Voice Server cannot process the audio stream for recognition. User response: Verify that the tuning parameters for your operating system are applied as described in the section on tuning operating systems in the WebSphere Voice Server Information Center.
CWVMC0013W: The Media Converter ASR subsystem did not accept an ASR media connection recognize mode=VALUE_0, number of audio bytes buffered=VALUE_1
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVMC0014E: The Media Converter ASR subsystem encountered an IOException VALUE_0 packets received, number of audio bytes buffered=VALUE_1, number of audio bytes sent to ASR=VALUE_2
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/
Chapter 8. Troubleshooting
247
index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVMC0015E: The Media Converter ASR subsystem encountered an IOException=VALUE_0 while processing an ASR recognition match message
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVMC0017E: The Media Converter ASR subsystem encountered an IOException=VALUE_0 while processing an ASR recognize request
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVMC0018E: The Media Converter ASR subsystem encountered an IOException=VALUE_0 while processing a TTS end of prompt message
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
248
CWVMC0019E: The Media Converter ASR subsystem encountered an IOException=VALUE_0 while processing a TTS start of prompt message
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVMC0020E: The Media Converter ControlSocket=VALUE_0 encountered an IOException=VALUE_1 while in the main run loop
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVMC0021E: The Media Converter MediaSocket encountered an IOException=VALUE_0 while in the main run loop
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVMC0022W: The Media Converter TTS subsystem encountered an IOException=VALUE_0 while processing an ASR bargein detected message
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
249
CWVMC0023W: The Media Converter TTS subsystem experienced a delay of VALUE_0 ms before receiving audio from the TTS engine.
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVMC1000E: Unable to obtain a home object for the EJB using the JNDI name VALUE_0
Explanation: The Media Converter found an error when trying to access the specified JNDI name. User response: Make sure the WebSphere Voice Server enterprise application has been successfully deployed. Check the logs for more detail.
CWVMD
CWVMD0001E: Failed to setup session for ASR - reason: VALUE_0
Explanation: WebSphere Voice Server could not establish a session for a MRCP Recognizer resource. User response: Check the WebSphere Voice Server Admin Console. Ensure the ASR engine status is green, and that there are available ASR engines. Check the logs for more detail.
250
that there are available engines. If the runtime status is green, check the logs for more detail.
CWVMD0005E: Failed to send MRCP VALUE_0 event back to the MRCP client - reason: VALUE_1
Explanation: WebSphere Voice Server could not send the specified event back to the MRCP client. User response: Check the logs for more detail.
CWVMD0009E: Invalid MRCP active request id list was specified in the MRCP STOP request
Explanation: WebSphere Voice Server received a MRCP STOP request with an invalid list of request IDs. User response: This is an error in the MRCP client. Report the error to the MRCP client provider.
Chapter 8. Troubleshooting
251
CWVMD0013E: Failed to process MRCP request targeting verifier resource. Reason: VALUE_0
Explanation: Check the reason text for the cause of this error. User response: Check the logs for more detail.
CWVPT
CWVPT0000I: OK
Explanation: OK User response: No user action needed.
252
Chapter 8. Troubleshooting
253
254
index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
255
index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
256
Chapter 8. Troubleshooting
257
258
CWVPT0055I: Elapsed time from the start of audio: VALUE_0 ms, from the end of the audio: VALUE_1 ms
Explanation: Information User response: No user action needed.
CWVPT0099I: <<VALUE_0>>
Explanation: Trace message User response: No user action needed.
CWVRB
CWVRB0001E: Illegal value for parameter VALUE_0: VALUE_1
Explanation: The value provided for the given parameter is invalid. User response: If the invalid parameter is from WebSphere Voice Server, refer to the Information Center for the range of valid values.
259
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
260
261
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVRB0015E: ASR setup error for locales VALUE_0: VALUE_1. ASR engine allocation interrupted
Explanation: An error occurred while attempting to set up the engines. User response: Ensure that the installation was successful for all languages and the system has enough hardware resources to run this configuration.
CWVRB0020E: Recognizer setup must be invoked prior to VALUE_0. Reason: null context
Explanation: MRCP SET-UP for Recognizer must be received prior to other requests.
262
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
263
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVRB0029E: Specifying multiple grammar languages in one RECOGNIZE request is not supported -languages detected: VALUE_0, VALUE_1
Explanation: RECOGNIZE request must contain grammars for a single language. User response: Correct the application.
CWVRB0031E: Error starting failover thread to recover ASR engines. Reason: VALUE_0
Explanation: Error starting a background thread to recover the system. System may be running low on resources. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/
264
index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
265
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
266
index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
267
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVRB0049I: Recognizer initialization for VALUE_0 is complete. VALUE_1 out of VALUE_2 configured ASR engine(s) available
Explanation: Informs the initialization status of the Recognizer. User response: None
CWVRB0050W: WARNING: Received NO-INPUT from same source that sent INPUT-STARTED!
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
268
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVRB1000E: Unable to obtain a home object for the EJB using the JNDI name VALUE_0
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
269
270
271
CWVRT
CWVRT0001W: Unable to validate RTSP configuration property VALUE_0 - defaulting to port VALUE_1
Explanation: There was either a problem loading the WebSphere Voice Server configuration file(s), or the value was not properly specified. User response: Make sure the configuration file(s) exist and/or they are in the correct directory, and make sure the value specified is correct.
CWVRT0002W: Unable to validate RTSP configuration property VALUE_0 - defaulting server timeout to VALUE_1 seconds
Explanation: There was either a problem loading the WebSphere Voice Server configuration file(s), or the value was not properly specified. User response: Make sure the configuration file(s) exist and/or they are in the correct directory, and make sure the value specified is correct.
CWVRT0003W: Unable to validate RTSP configuration property VALUE_0- defaulting socket timeout to VALUE_1 seconds
Explanation: There was either a problem loading the WebSphere Voice Server configuration file(s), or the value was not properly specified. User response: Make sure the configuration file(s) exist and/or they are in the correct directory, and make sure the value specified is correct.
CWVRT0004W: Unable to validate RTSP configuration property VALUE_0 - defaulting reco media url to VALUE_1
Explanation: There was either a problem loading the WebSphere Voice Server configuration file(s), or the value was not properly specified. User response: Make sure the configuration file(s) exist and/or they are in the correct directory, and make sure the value specified is correct.
CWVRT0005W: Unable to validate RTSP configuration property VALUE_0 - defaulting synth media url to VALUE_1
Explanation: There was either a problem loading the WebSphere Voice Server configuration file(s), or the value was not properly specified. User response: Make sure the configuration file(s) exist and/or they are in the correct directory, and make sure the value specified is correct.
272
CWVRT0011E: MRCP Client was unable to provide a read/write stream for the WebSphere Voice Server - additional information follows: MRCP Client: VALUE_0 Error Message: VALUE_1
Explanation: This will happen when a socket connection is made and the RTSP Bridge is unable to get the input and output stream from the socket. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVRT0012W: Unable to validate RTSP configuration property VALUE_0 - defaulting to Boolean value VALUE_1
Explanation: There was either a problem loading the WebSphere Voice Server configuration file(s), or the value was not properly specified.
Chapter 8. Troubleshooting
273
User response: Make sure the configuration file(s) exist and/or they are in the correct directory, and make sure the value specified is correct.
CWVRT0013W: Time out has occured on the session - no more requests were available from the client within the specified time limit. Additional information follows: MRCP Client: VALUE_0 Error Message: VALUE_1
Explanation: This will happen if the session thread is blocked reading the input stream for longer than the specified socket timeout (meaning there is no data to read from the socket) User response: Try increasing the socket timeout configuration parameter (com.ibm.voice.server.rtspbridge.sockettimeout) to a larger value.
CWVRT0014W: The MRCP Client has unexpectedly disconnected from an RTSP Session during a read/write operation with the WebSphere Voice Server. Additional information follows: MRCP Client: VALUE_0 Error Message: VALUE_1
Explanation: The primary socket that was established by the client for communicating with WebSphere Voice Server has been inadvertently closed by the client, causing a read/write error on WebSphere Voice Server. User response: This message indicates a problem with the Interactive Voice Response (IVR) system. Contact support for the IVR system or application you are using.
CWVRT0015W: The MRCP Client sent a malformed RTSP message to the WebSphere Voice Server. Additional information follows: MRCP Client: VALUE_0 Error Message: VALUE_1
Explanation: The RTSP message is not formatted as outlined by the HTTP 1.1 specification. All HTTP-like messages, like RTSP, must follow a strict format in order to be parsed correctly. This format is defined in the HTTP 1.1 specification and described in RFC 2326 - Real Time Streaming Protocol (RTSP). User response: This message indicates a problem with the Interactive Voice Response (IVR) system. Contact support for the IVR system or application you are using.
CWVRT0016W: The MRCP Client sent an invalid RTSP message to the WebSphere Voice Server. Additional information follows: MRCP Client: VALUE_0 Error Message: VALUE_1
Explanation: There was a problem with the RTSP message. For example, the session ID does not match the current session ID. Or, the RTSP version is not correct. User response: Typically the RTSP response code will be very clear as to why the message could not be validated. Use a packet sniffer like Ethereal, to investigate the response code.
274
CWVRT0017E: An internal WebSphere Voice Server error was detected by the RTSP Bridge component - additional information follows: MRCP Client: VALUE_0 Error Message: VALUE_1
Explanation: There was an internal problem with the RTSPBridge. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVRT0018W: An internal WebSphere Voice Server error was detected by the RTSPBridge component - additional information follows: MRCP Client: VALUE_0 Error Message: VALUE_1
Explanation: There was an internal problem with the RTSPBridge. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVRT0020W: The MRCP Client acknowledged an event from the WebSphere Voice Server with an invalid sequence number: VALUE_0 MRCP Client: VALUE_1
Explanation: This error will occur if a client initiated response cannot be validated by the WebSphere Voice Server. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVRT0021W: The MRCP Client acknowledged an event from the WebSphere Voice Server with an unexpected response: Invalid response code: VALUE_0 MRCP Client: VALUE_1
Explanation: Could not process the server initiated request (This warning will occur if the client initiated response is not a 200 Ok). User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
275
CWVRT0022E: The RTSP Server was unable to close all the session threads before continuing shutdown. There are VALUE_0 left.
Explanation: During an immediate shutdown of the RTSP Server, all session threads are expected to terminate before shutting down remaining server resources. If that is not the case, this error will be generated. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVRT1000E: Unable to obtain a home object for the EJB using the JNDI name VALUE_0
Explanation: There was a problem looking up the EJB User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVSB
CWVSB0001E: Failed to launch TTS engine process. Reason: VALUE_0
Explanation: Check the reason text for the cause of this error. User response: Check for invalid configuration settings. See the Information Center Installation Troubleshooting Tips for more information.
276
index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVSB0005E: Connection with TTS engine has been closed - the WebSphere Voice Server is starting a new TTS engine
Explanation: The MRCP Synthesizer lost a connection with a TTS engine and a new process is being started. User response: Check the logs for more detail.
CWVSB0006W: A default TTS voice has not been configured - using default voice VALUE_0
Explanation: A default TTS voice has not been configured. User response: Configure a default TTS voice using the WebSphere Voice Server Administrative Console configuration panel.
CWVSB0007E: Missing required configuration for Synthesizer - ensure the property VALUE_0 is configured
Explanation: Missing the specified configuration property. User response: Check the configuration and make sure the specified property is specified.
Chapter 8. Troubleshooting
277
CWVSB0011I: Synthesizer startup complete - status is VALUE_0 VALUE_1 out of VALUE_2 configured TTS engine(s) available
Explanation: Informational message indicating that the Synthesizer has started. User response: Check the status and make sure all configured TTS engines are available.
CWVSB0019I: FAILOVER: Starting a new TTS engine - VALUE_0 out of VALUE_1 attempts
Explanation: Informational message indicating that a new TTS engine is being started.
278
User response: This message indicates that the Synthesizer has lost connection to one of the TTS engines. Check the log for more detail.
CWVSB0020I: FAILOVER: New engine has been started successfully pool size: VALUE_0
Explanation: Informational message indicating that a new TTS engine has been started. User response: This message indicates that the Synthesizer has lost connection to one of the TTS engines. Check the log for more detail.
CWVSB0025E: Synthesizer has failed to initialize VALUE_0 engines the startup process is being aborted
Explanation: Synthesizer startup process failed because one or more engines could not be launched. User response: Make sure TTS is correctly installed. Check configuration settings. Check the logs for more detail.
CWVSB0026W: Failed to send trace message to the TTS engine - TTS engine trace may not work correctly
Explanation: The TTS engine trace could not be set. Trace messages will not be available. User response: Make sure the TTS trace is configured correctly.
Chapter 8. Troubleshooting
279
CWVSB0030E: Failed to set parameters for MRCP SPEAK request. Error code: VALUE_0
Explanation: The TTS engine replied with an error when validating the SPEAK request parameters. User response: Check the logs for more detail.
CWVSB0032E: Synthesizer configuration error - default voice VALUE_0 does not match any of the available voices
Explanation: The Synthesizer requires the default voice to be selected from the list of available voices. User response: Check the configuration and make sure that the configured default voice matches one of the available voices.
CWVSB1000E: Unable to obtain a home object for the EJB using the JNDI name VALUE_0
Explanation: Synthesizer found an error when trying to access the specified JNDI name. User response: Make sure the WebSphere Voice Server enterprise application has been successfully deployed. Check the logs for more detail.
280
CWVSM
CWVSM0003W: The configuration property VALUE_0 was not found defaulting to value VALUE_1
Explanation: The server attempted to use a configuration property that does not exist. User response: Either the configuration is damaged, or the server was unable to load the configuation information.
CWVSM0004E: After VALUE_0 attempts - the server was unable to find an available port to create an RTP audio input server. The Last port attempted was VALUE_1.
Explanation: If the system is overloaded, resources such as ports may not be available. User response: Make sure the system is operating within an appropriate load, then retry the operation.
Chapter 8. Troubleshooting
281
CWVSY1003I: WebSphere Voice Server installation verification executing for VALUE_0 ...
Explanation: The WebSphere Voice Server installation verification test is executing for V ALUE_0 (for either ASR or TTS). User response: No user action needed.
CWVSY1007E: WebSphere Voice Server installation verification provided invalid parameter: VALUE_0.
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
282
CWVSY1008I: WebSphere Voice Server installation verification successfully created a sample audio file, named VALUE_0 and located in the $WVS_ROOT/ivt directory.
Explanation: The TTS voice has been installed correctly. The audio file was created in the $WVS_ROOT/ivt directory. User response: You may play the sample audio file in the $WVS_ROOT/ivt directory.
CWVSY2000E: Unable to create the WebSphere Voice Server logging directory VALUE_0. The exception message is VALUE_1.
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
283
CWVSY2006E: WebSphere Voice Server failed to start - see the SystemOut.log file for more information
Explanation: WebSphere Voice Server encountered an error during its initialization. User response: You should review the SystemOut.log file for the specific error. For additional information on resolving this error, please consult the IBM WebSphere Voice Server Support Website available at: http://www.ibm.com/software/ pervasive/voice_server/support/index.html. The site provides searchable databases of technotes, solutions, and e-fixes, as well as contact information for the WebSphere Support team.
CWVSY2007E: WebSphere Voice Server encountered a failure during the stop operation - see the SystemOut.log file for more information
Explanation: WebSphere Voice Server encountered an error during the stop operation. User response: You should review the SystemOut.log file for the specific error. For additional information on resolving this error, please consult the IBM WebSphere Voice Server Support Website available at: http://www.ibm.com/software/ pervasive/voice_server/support/index.html. The site provides searchable databases of technotes, solutions, and e-fixes, as well as contact information for the WebSphere Support team.
284
CWVSY2011E: WebSphere Voice Server failed to load the configuration information - see the SystemOut.log file for more information
Explanation: WebSphere Voice server failed to load the configuration information needed to start. User response: You should review the system log file for the specific error. For additional information on resolving this error, please consult the IBM WebSphere Voice Server Support Website available at: http://www.ibm.com/software/ pervasive/voice_server/support/index.html. The site provides searchable databases of technotes, solutions, and e-fixes, as well as contact information for the WebSphere Support team.
Chapter 8. Troubleshooting
285
286
index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVSY9942E: cannot get the port number from .cwvs.properties need com.ibm.voice.server.common.log.logservice-udpport=xxxx
Explanation: Native logging subsystem was unable to get UDP port number configuration value from WebSphere Voice Server configuration repository. User response: There is probably a problem with missing environment variables or installation configuration.
287
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVSY3001E: WebSphere Voice Server property name VALUE_0 does not exist in the product configuration
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVSY3002E: Specified filter parameter of null is not valid for a configuration property search
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVSY3003E: Read operation of the WebSphere Voice Server configuration file VALUE_0 failed
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVSY3004E: Write operation of the WebSphere Voice Server configuration file VALUE_0 failed
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
288
CWVTE
CWVTE0001E: unable to write ESPR to file: eXsXpXr.dbg errno = %s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
289
CWVTE0008W: returning: %s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
290
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
291
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
292
293
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
294
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
295
CWVTE0034W: returning %s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
296
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
297
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
298
299
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
300
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
301
302
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
303
304
305
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
306
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
307
CWVTE0094W: returning: %s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is
308
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0097W: size is 0
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
309
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
310
CWVTE0105W: ECIERROR_ERROR
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0106W: ECIERROR_NORESOURCES
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0107W: PARAMETERERROR
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0108W: DEVICEERROR
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is
Chapter 8. Troubleshooting
311
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0109W: ECIERROR_AUDIODEVICEBUSY
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0110W: ECIERROR_ENGINEERROR
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0111W: ECIERROR_SYNTHESIZING
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
312
313
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
314
315
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
316
317
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
318
Chapter 8. Troubleshooting
319
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0330E: You must compile with flag AARONF0 set to include ACs F0 generation code
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
320
321
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
322
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
323
324
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0362E: Pnsp, voice, and broadclass list file (aux_dur_list_file) not specified
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0364E: Phone order in %s does NOT match phone order in PNSP file - re-order
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
325
326
327
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0379E: Number of leaves in duration tree doesnt match number of medians in dur_medians file
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
328
329
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
330
331
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
332
CWVTE0405E: Number of leaves in energy tree doesnt match number of medians in en_medians file
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
333
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
334
335
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
336
337
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
338
index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
339
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
340
341
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
342
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
343
344
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0476E: Phone stream has more phones (%2$s) than we calculated earlier (%3$s)
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
345
346
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
347
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
348
index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
349
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
350
351
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
352
CWVTE0531W: at leave %s there are is zero (prevactive = 0) active nodes in the beam
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the
Chapter 8. Troubleshooting
353
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
354
CWVTE0539E: synthesis_mode says use continuity costs - but vectors are not loaded
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0540E: There are unspecified durations in the leaf level of the sentence structure
Explanation: This is an unexpected error. The cause cannot be immediately determined.
Chapter 8. Troubleshooting
355
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0541E: synthesis_mode says do pitch mark based duration costing but the pitch mark files were never processed
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
356
357
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
358
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0555E: Number of vectors loaded from %2$s is %3$s which does not match number expected by core occurrence files: %4$s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0557E: Vector %2$s has dimension %3$s which is different from the first vector with dimension %4$s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
359
CWVTE0561E: Dimension in join file %s doesnt agree with that in vectors file
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
360
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
361
CWVTE0570E: num_phones in join matrix %2$s differs from that in phonegraphs %3$s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0572E: num_internals in join matrix %2$s is different from that implied by phonegraphs %3$s
Explanation: This is an unexpected error. The cause cannot be immediately determined.
362
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
363
364
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
365
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0588E: usage stats file does not match the loaded dataset
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
366
CWVTE0593W: this command loads usage stats incremently; * zero_stat should be used prior to first use
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
367
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
368
369
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
370
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
371
CWVTE0639E: The ETI buffer is ill defined - it does not have three null chars
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
372
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
373
374
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
375
376
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
377
378
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0685E: occ file %2$s appears to be longer than the xwal file %3$s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
379
CWVTE0687E: occ file fenemes in %2$s have got out of step with xwal fenemes in %3$s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
380
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
381
382
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
383
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
384
Chapter 8. Troubleshooting
385
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0733E: There are unspecified durations in the leaf level of the sentence structure
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0734E: There are unspecified occurrences in the leaf level of the sentence structure
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0736E: Attempt to use occurrence in synthesis for which no valid synthesis information (pitch-marks) exists.
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/
386
index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
387
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
388
Chapter 8. Troubleshooting
389
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
390
391
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
392
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
393
394
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
395
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
396
397
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
398
CWVTE0796W: No pitch marks in file %2$s for leaf %3$s at time %4$s to time %5$s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the
Chapter 8. Troubleshooting
399
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
400
401
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0829E: There are two pitch_elems with the same time value
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
402
CWVTE0842E: MaxChunk size is %2$s, but requested memory size by the dataset is %3$s, which is an invalid condition
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
403
CWVTE0845E: Trying to request more memory than allocated, currentpos = %2$s, bytes requested = %3$s, TotalPSMemoryAllocated = %4$s.
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
404
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0871E: cmm::releaseNow() failed for 0x%s after addCache failed to add it into cache array
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0872E: cmm returned %2$s while creating memory for cache item %3$s - the return code should be %4$s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
405
index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0874E: cmm::releaseNow() failed for 0x%s while making space for a new cache item (using # of bytes method)
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0875E: Did not find the named (%2$s) memory while removing a item# %3$s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0876E: failed to write cachefile correctly - attempted to write %2$s items but only wrote %3$s items - clearing the cache file
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE0881E: ph_cntx[pos] is incorrect because %2$s (pos) + %3$s (offset) is a negative value
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
406
CWVTE0913E: Fastload image version %2$s does not match with the fastload build engine version %3$s
Explanation: This is an unexpected error. The cause cannot be immediately determined.
Chapter 8. Troubleshooting
407
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
408
409
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
410
411
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
412
413
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE1527E: shmat failed - unable to attach shared memory - errno = %2$s : %3$s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE1528E: inaccessible memory has key: 0x%2$s created by user: %3$s group: %4$s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
414
CWVTE1533E: memory with key: 0x%2$s created by user: %3$s group: %4$s - attempted access by user: %5$s group: %6$s.
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
415
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
416
Chapter 8. Troubleshooting
417
CWVTE1610E: semaphore: owner ID = %2$s, owner group = %3$s, permission bits = %4$s, creators ID = %5$s
Explanation: semop failed. The semaphore owner, access bits, and creators ID are listed. User response: Verify that process attempting to access the semaphore has permission to do so.
418
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
419
420
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE1645W: Could not convert character code %s to its corresponding UTF8 char
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
421
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE1652E: Unable to set initial filter environment, eci environment not available
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
422
CWVTE1663W: IPA phoneme alphabet not supported for current active language %s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE1666W: Unknown or unexpect <say-as> interpret-as vxml:date format %s, tag will be ignored
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
423
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
424
Chapter 8. Troubleshooting
425
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
426
CWVTE1750E: cannot insert token object between the first & last two syncmarks: stream = %s
Explanation: This is an unexpected error. The cause cannot be immediately determined.
Chapter 8. Troubleshooting
427
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
428
CWVTE1786E: Either Torrent library loading failed or could not create a TorrentWrap object
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the
Chapter 8. Troubleshooting
429
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
430
Chapter 8. Troubleshooting
431
432
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
433
434
available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE1829E: ioctl SNDCTL_DSP_SPEED could not set rate to %2$s, card may be locked at %3$s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
435
CWVTE1831E: Error setting number to %2$s channels, card set to do only %3$s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE1833E: Sound card does not support mono, set to %s channels only
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
436
Chapter 8. Troubleshooting
437
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE1924E: Error while attempting to allocate memory by parser, returning processed text
Explanation: Unable to allocate memory. User response: If your Unix computer has adequate memory, then if possible increase the limit for physical memory (see ulimit -m).
CWVTE1925W: Mismatched tag found by parser, synthesizing only till illegal tag
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
438
User response: If your Unix computer has adequate memory, then if possible increase the limit for physical memory (see ulimit -m).
439
440
441
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
442
index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE2041W: Cannot process load-lexicon message - TTS media control layer may not be initialized.
Explanation: You must call TTS Media Control Layer with an initialize message first User response: Initialize failed or Initialize message not received
Chapter 8. Troubleshooting
443
444
Chapter 8. Troubleshooting
445
446
User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE2065E: Failed on getting host MC address - using host MC IP=%2$s, state=%3$s, errno=%4$s(%5$s)
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
447
index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
CWVTE2067E: Failed on connecting to host MC (audio) - using audio port=%2$s, state=%3$s, errno=%4$s(%5$s)
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
448
CWVTE2073E: Error on creating socket for IBM HTTP Server state=%2$s, errno=%3$s(%4$s)
Explanation: The SynthEngine can not create the connection to IBM HTTP Server. User response: Ensure the IBM HTTP Server is started.
CWVTE2074E: Failed on connecting to host IBM HTTP Server - using port=%2$s, state=%3$s, errno=%4$s(%5$s)
Explanation: The SynthEngine can not connect to the IBM HTTP Server. User response: Ensure the IBM HTTP Server is started.
CWVTE2075E: Unable to send a message to MC using port=%2$s(MC_msg_peer port=%3$s), state=%4$s, errno=%5$s(%6$s), msg=%7$s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
449
CWVTE2076E: Unable to send audio to MC using audio port=%2$s(MC_audio_peer port=%3$s), state=%4$s, size of audio=%5$s, errno=%6$s(%7$s)
Explanation: The Media Converter might not be running on the expected port. User response: Verify that WebSphere Voice Server started successfully and check the error logs to make sure that the Media Converter component started without errors.
CWVTE2078E: Failed on sending message to IBM HTTP Server state=%2$s errno=%3$s(%4$s) msg=%5$s
Explanation: This is an unexpected error. The cause cannot be immediately determined. User response: Refer to the troubleshooting section of the WebSphere Voice Server information center for help diagnosing the problem. If necessary, submit the problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
450
problem through the IBM WebSphere Voice Server Support Web site, which is available at: http://www.ibm.com/software/pervasive/voice_server/support/ index.html. The site also provides searchable databases of technotes, solutions, and e-fixes.
Chapter 8. Troubleshooting
451
Identifier
This section describes the identifiers for WebSphere Voice Server. WebSphere Voice Server and the MRCP client (such as the VoiceXML Browser) create unique identifiers in order to exchange information. You can see examples of these identifiers in the following sample SystemOut.log message:
452
CWVAE0318W: [sid=19009.IBM.9.22.96.50][rid=12][ltag=9507:9.22.96.33::4][turn=3] [pid=0x8e1e] Mailman::Dispatch: No audio available after 10 seconds. Forcing microphone off. [t=09:39:55:589 EDT]
[sid]
Stands for MRCP session-id. WebSphere Voice Server creates this unique identifier for the session and passes it to the MRCP client. In the example above, the [sid] is 19009.IBM.9.22.96.50.
[rid]
Stands for MRCP request-id. The MRCP client creates this unique identifier for the request and passes it to WebSphere Voice Server. In the example above, the [rid] is 12.
[ltag]
Stands for MRCP logging-tag. The MRCP client creates this unique identifier and passes it to WebSphere Voice Server. In the example above, the [ltag] is 9507:9.22.96.33::4.
[turn] Stands for the WebSphere Voice Server turn identifier. WebSphere Voice Server creates and manages this identifier. WebSphere Voice Server MRCP Synthesizer and Recognizer components count the number of Recognize or Speak MRCP messages. This identifier starts at 1. In the example above, the [turn] is 3. [pid] Stands for the WebSphere Voice Server process identifier. This identifier will be generated by platform OS. In the example above, the [pid] is 0x8e1e. [t] Stands for the WebSphere Voice Server event time stamp that is associated with exact time of event generation by originating component. WebSphere Voice Server engine components generate this time stamp as part of normal event logging. In the example above, [t] is 09:39:55:589 EDT. These identifiers allow for tracking the MRCP activity throughout the system on a per-session and per-request basis. If any of the four fields are not populated, then the information is not available at the time of the request. These identifiers are readily available to match up with the logs created by the MRCP client. Related information Message IDs This section describes the WebSphere Voice Server messages, which use a 10-character format.
Chapter 8. Troubleshooting
453
The trace log shows trace events such as function entries and exits, component events, and debug. Two topics provide additional information to guide system administrators: v Enabling trace v Monitoring trace
Enabling trace
Trace for a voice server process is enabled using the administrative console. You can configure the voice server to start in a trace-enabled state by setting the appropriate configuration properties. In the administrative console, enable and configure trace by using the following steps: 1. Expand Troubleshooting in the navigation panel by clicking the plus (+). 2. Click Logs and Trace. 3. Click the name of the server, such as server1, listed in the Server column of the table. 4. Click Diagnostic Trace. When you click the Modify button under the Trace Specification section of the Configuration tab, only three of the trace groups displayed in the Modify Trace panel are relevant to WebSphere Voice Server. They are the following: IBM WebSphere Voice Server Includes all of the basic WebSphere Voice Server components.
Table 19. WebSphere Voice Server components Acronym AdminConsole Common Config DTMFBean Dispatcher GramComp GramMgr LogTrace MediaConv RRBean RTSPBridge SesMgr Synth SysMgmt Description Administrative Console Common Component Configuration Subsystem DTMF Message Dispatcher Grammar Compiler Grammar Manager Log and Trace Subsystem Media Converter Resource Resolver RTSP Bridge Session Manager Synthesizer System Management
IBM WebSphere Voice Server ASR Includes all of the ASR components.
454
Table 20. ASR components Acronym ASRAPI ASRAUD ASRAW ASRBEAN ASRCONF ASRCTRL ASRDM ASRENG ASRFM ASRLAT ASRLM ASRNBST ASRSEQ ASRSIG ASRSRCH ASRTRN ASRVOC ASRWSI RECOGNIZER Description SMAPI Messages Audio Library Add Word ASR Bean Confidence Scoring Control Interface Detailed Match ASR Engine (configuration and recognition results) Fast Match Latency Language Model N-Best results Program Execution Sequence Signal Processing Stack Search Training Vocabulary and Pronunciations Work Station Interface Recognizer Bean
IBM WebSphere Voice Server TTS Includes all of the TTS components.
Table 21. TTS components Acronym CMM DIC ECI ETI MCL MLD MOR NOR PAR PHO PRE PRO SEM SOU SSM Description Concatenative Memory Manager Dictionary ECI Interface API Common Development Library Media and Control Layer Multilevel Data Structure Morphological Analyzer Normalizer Language Parser Phonetizer Preprocessor Prosody Semaphores Sound XML Parser, SSML Processor and Filter
Chapter 8. Troubleshooting
455
Table 21. TTS components (continued) Acronym SYL TOR Description Syllable Analyzer Torrent
Important: Enable IBM WebSphere Voice Server ASR or IBM WebSphere Voice Server TTS tracing only if advised by IBM Support. Enabling these trace groups will cause performance issues. Because WebSphere Voice Server uses the common WebSphere approach to trace, the WebSphere Application Server Network Deployment 5.1.x Information Center contains detailed information on configuring trace in the administrative console. Trace Output Format, the last configuration parameter shown on the console, allows you to specify the level for trace output. Do not change this from Basic (Compatible).
Monitoring trace
WebSphere Voice Server uses the following log parameters: v Product = WVS v Manufacturer = IBM v LongName(ComponentId) = IBM WVS [component name] v ShortName(SourceId) = [component name]
Isolating audio problems between WebSphere Voice Server and the qualified IVR
Sometimes it is difficult to isolate audio problems between WebSphere Voice Server and the Interactive Voice Response (IVR). The first step toward problem determination is to ensure that the correct TTS audio is produced by the Voice Server. To do this, you can listen to the generated .pcm file for each TTS synthesis request. If the quality of the TTS audio is degraded from what you hear in the .pcm file, then the problem is most likely with the gateway. You can also listen to the .pcm files (using a tool of your choosing) for each ASR request to ensure that the correct ASR audio is produced. IBM WebSphere Voice Server MediaConv records the audio as it is received from the gateway. The ASR engine records pre- and post-endpointed audio. This allows you to hear if the ASR audio is degraded by the gateway. If entry/Exit or event is enabled for certain components, these components will log trace messages that reference binary or text files. For example, if event is enabled for the IBM WebSphere Voice Server MediaConv, then the Media Converter will create audio files to record all of the audio passed. On Linux and AIX, these additional files, including the .pcm files, are located in a WebSphere Voice Server-specific directory: WAS_ROOT/logs/server/CWV/timestamp/ For Windows Server 2003 Enterprise or Standard editions, the additional files, including the .pcm files, are located in a WebSphere Voice Server-specific directory: %WAS_ROOT%\logs\server\CWV\time-stamp\
456
Each time that WebSphere Voice Server is restarted, a new time-stamp directory is created so that no existing files are overwritten. For investigating audio problems, trace the following two components at the specified levels: 1. RTSPBridge at the all enabled trace level. 2. Media Converter (MediaConv) at the event trace level. Enabling entry/Exit or event for these components creates a lot of files on disk. You should only perform this activity at the direction of IBM Support or to investigate a specific audio problem. After you complete this activity, run the Collector Tool. The Collector Tool will also delete all information out of the CWV directory freeing up disk space. Administrative console Manage and view log and trace files and view alarms (console messages). The Voice Servers panel automatically refreshes every 60 seconds, but may be configured to refresh on a different schedule.
Table 22. Additional log files
Component Subcomponent Files created All utterances for all sessions are recorded. These recordings are endpointed audio. All utterances for all sessions are recorded. These recordings are not endpointed audio (that is, they contain extra silence). Saves data for site adaptation. SessionID.TurnID.ep.xxx (where xxx can be bsf, cep, or tag). File naming convention SessionID.TurnID.ep.pcm IBM WVS ASR - ASR If the trace level for engine subcomponent ASRAUD is set to entry/Exit, then post-endpointed audio is saved. IBM WVS ASR - ASR If the trace level for engine subcomponent ASRAPI is set to entry/exit, then pre-endpointed audio is saved.
SessionID.TurnID.pcm
IBM WVS ASR - ASR ASRTRN engine IBM WVS Media Converter If the trace level is set to event, then pre-endpointed audio is saved.
All audio for all SessionID.mc.asr.pcm sessions is recorded, meaning, or SessionID.TurnID.mc.asr.pcm the audio before it orSessionID.TurnID.mc.tts.pcm is passed to the ASR engine and the audio after it is received from the TTS engine.
457
To use the Voice Trace Analyzer for audio analysis and playback, set the appropriate trace according to what is outlined in Table 21 on page 455, to obtain the audio files created during recognition processing. Remember: Run the collector tool to capture and erase the audio files so that your disk does not fill up. The resulting output JAR file from the collector tool can be imported into the Voice Trace Analyzer.
Additional information
Detailed information about running the Collector tool may be found in the WebSphere Application Server Network Deployment 5.1.x Information Center.
458
If your system is a Windows platform, include regedit in the path. 3. Create a work directory where you can start the collector program. 4. Make the work directory the current directory. The collector program writes its output Java archive (JAR) file to the current directory. The program also creates and deletes a number of temporary files in the current directory. Creating a work directory to run the collector program avoids naming collisions and makes cleanup easier. 5. Run the collector program by entering the collector command from the command line. Using the collector command with no additional parameters gathers one copy of the node data and data from each server in the node, and stores them in a single JAR output file. Note: Set the path correctly to use the non-qualified version of the command. Please note, WAS_ROOT/bin must be in the path to locate the collector command. The WebSphere Application Server installation root directory is determined at installation. It is identified in the setupCmdLine.sh file in Linux and AIX. On Windows, the installation directory was selected automatically when you installed WebSphere Voice Server. You can enter a fully qualified path to the collector command. For example, enter these commands in a default installation: On AIX:
>mkdir work >cd work >/usr/WebSphere/AppServer/bin/collector.sh
On Linux:
>mkdir work >cd work >/opt/WebSphere/AppServer/bin/collector.sh
On Windows:
C:\>md work C:\>cd work C:\>"C:\Program Files\WebSphere\AppServer\bin\collector"
459
The Collector Tool JAR size is determined by the following: v The collection of all properties files, configuration files, and operating system details v The SystemOut.log size and number of historical files v The trace.log size and number of historical files v The amount of audio files under the CWV directory Because the SystemOut.log and trace.log files are text-based, they compress well for inclusion in the Collector JAR. If you have the SystemOut.log file using the default values (a maximum size of 1 MB and one historical file) and a single 8 MB trace.log file, then your JAR size is 3.4 MB. If you have the SystemOut.log file using the default values (a maximum size of 1 MB and one historical file) and your trace.log file values set to 20 MB for the maximum file size with 19 historical files, then your JAR size is 95 MB. When the Collector Tool is run, all audio files are deleted from the CWV subdirectory.
What to do next
Send the hostname-ND-WASenv.jar or hostname-Base-WASenv.jar file to IBM Support for analysis.
460
If you do not see a task that resembles yours, or if the information provided does not solve your problem, contact IBM Support for further assistance.
461
[9/15/05 9:23:59:062 MDT] 7b2b4323 WebGroup I SRVE0181I: [adminconsole] [/admin] [Servlet.LOG]: action: Error creating ActionForm instance of class com.ibm.ws.console.wvs.form.ServerDetailForm: java.lang.InstantiationException: com.ibm.ws.console.wvs.form.ServerDetailForm at java.lang.Class.newInstance3(Class.java(Compiled Code)) at java.lang.Class.newInstance(Class.java(Compiled Code)) at org.apache.struts.action.ActionServlet.processActionForm(ActionServlet.java:1706) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1563) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) .... [9/15/05 9:23:59:219 MDT] 7b2b4323 WebGroup E SRVE0026E: [Servlet Error]-[action]: java.lang.NullPointerException at com.ibm.ws.console.wvs.action.ServerDetailAction.perform(ServerDetailAction.java:135) at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1791) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) .... [9/15/05 9:23:59:250 MDT] 248c320 WebGroup E SRVE0026E: [Servlet Error]-[action]: java.lang.NullPointerException at com.ibm.ws.console.core.action.StatusAction.perform(StatusAction.java:56) at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1791) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
For detailed information and more tips, see the WebSphere Application Server Network Deployment 5.1.x Information Center.
462
The Listen 80 directive is needed because port 80 only binds the root process to the port. By default on a Windows system, the IBM HTTP Server listens on the AFPA socket and not on the default Windows socket. Adding the Listen 80 directive forces the Web server to listen on the default Windows socket when AFPA is disabled. 3. Stop the IBM HTTP Server. 4. Start the IBM HTTP Server.
Chapter 8. Troubleshooting
463
The embedded audio or lexicon document cannot be fetched, or the embedded audio file within the SSML document will not play
v Make certain that the IBM HTTP Server is up and running on the host system: 1. Using Linux and AIX, change directory to /opt/IBMHttpServer/bin and type ./apachectl start. 2. Then check to make sure that the server is started by running the following command: ps auxw | grep httpd. 3. On a Windows platform, view your services panel to check if the IBM HTTP Server is running. v Is the path you specified correct for the file you want? v Check the WAS_ROOT/logs/server1/SystemOut.log to see if any errors have been logged. v Does the file exist in the location specified? v Verify that the file is in the correct audio format. VoiceXML specifications require that a platform support the following playing and recording audio formats: Raw (headerless) 8kHz 8-bit mono mu-law [PCM] single channel. Raw (headerless) 8kHz 8 bit mono A-law [PCM] single channel. WAV (RIFF header) 8kHz 8-bit mono mu-law [PCM] single channel. WAV (RIFF header) 8kHz 8-bit mono A-law [PCM] single channel. Also, if the SSML processor cannot find the audio file, it will synthesize the files that it can find. This means that there is no error message rendered, but you will not hear the file played. In order to troubleshoot this error you will need to turn on tracing to see why the file was not fetched.
When the <voice> tag has a gender attribute set to neutral, the voice is not changed
Certain <voice> tag attributes, such as gender neutral and age, are not supported for any concatentive voices, including US English and Chinese voices. Also note that the variant attribute is not supported for the US English and Chinese voices.
464
The amount of text included in one speak request is limited to the amount of text that can be spoken in five minutes. The synthesized audio for larger amounts of text may be truncated.
465
2. At the command line prompt, type: attrib boot.ini You should see a response similar to the following: A SH 3. Next, type:
attrib -h -s boot.ini notepad boot.ini
C:\boot.ini
4. Carefully duplicate and edit the last line, adding /3GB as in the following, and save the file:
[boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise /3GB" /fastdetect /3GB multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /fastdetect
5. Reboot your machine, and when given the choice, select Windows Server 2003, Enterprise /3GB, or wait until the machine automatically boots the new default /3GB configuration. This configuration allows you to run additional voices, given that you have sufficient real memory and/or pagespace. If there is any problem with the /3GB configuration, you can boot from the original configuration (the second line on the boot screen) and remove the /3GB line from boot.ini. To hide the boot.ini file again, type: attrib +h +s boot.ini
466
If you have configured WebSphere Voice Server to point the General (first level) Cache and Grammar (second level) Cache to directories other than the default, then you must disable those directories as well. If scanning on the above directories is disabled, and problems are still occurring, it may be necessary to uninstall or disable the antivirus software. Updating the antivirus software may not correct the problems. If not, contact your antivirus software vendor for a solution.
General
v The ASR engine(s) will not start v Reliability issues when antivirus software installed on page 468
Grammar or lexicon
v A grammar has compilation errors on page 468 v A grammar cannot compile with special characters on page 468 v A grammar or lexicon cannot be fetched on page 469 v Compilation of a large grammar or a large lexicon is slow and times out on page 469 v An external lexicon, grammar, or audio resource has been updated but WebSphere Voice Server is using an old copy on page 469 v MIME type and universal grammars on Genesys on page 470 v The system cannot find the path specified error on page 470 v Compilation of a large grammar fails with CWVGC2041E on page 470
Recognition
v v v v v v v The environment is noisy on page 470 Large grammar concerns on page 471 No-input timeout is happening too often on page 472 No-match is happening too often on page 472 Increasing the accuracy of my grammar on page 472 False barge-ins are occurring on page 472 Circular references in SRGS semantic interpretation results on page 472
467
See the Tuning section for more information about the modifications that take place during the installation process. If this information does not solve your problem, see the IBM Support topic for further assistance.
468
Remove any illegal characters from your grammar and recompile. Refer to section 3.1 of the SRGS specification for additional details.
An external lexicon, grammar, or audio resource has been updated but WebSphere Voice Server is using an old copy
WebSphere Voice Server uses HTTP caching parameters to expire the cached resource in the general (first level) cache. A cached resource can be an external lexicon, grammar or audio file. The expiration for a cached resource can be set on the Web server, application server, or specified by the content of the lexicon or grammar using the meta tag <meta http-equiv="Expires" content="0"></meta>. If the expiration is not provided by the fetched resource, then the default expiration time is used. For example, the default expiration might be set to expire after 24 hours. The default expiration time is specified by the com.ibm.voice.server.rr.fetchexpires configuration parameter. During application development for grammar, lexicon, or audio files, disable the general cache, by setting com.ibm.voice.server.rr.caching=false. This ensures that WebSphere Voice Server fetches the most current content every time. Once application development is finished, apply the appropriate caching rules to the resource according to the VoiceXML and HTTP specifications, and enable the general cache. Note: Setting this configuration parameter to true, com.ibm.voice.server.rr.caching=true enables the general cache. If you need to delete the WebSphere Voice Server general and grammar (second level) caches, perform the following steps: 1. Shut down WebSphere Voice Server. 2. Go to the directory containing the WebSphere Voice Server general cache. This is specified by com.ibm.voice.server.rr.cachename. If you have not modified this configuration parameter, then it is $WVS_ROOT/rrcache. 3. Remove all of the files so that the entire directory is empty. 4. Go to the directory containing the WebSphere Voice Server grammar cache. This is specified by com.ibm.voice.server.gm.cachename. If you have not modified this configuration parameter, then it is $WVS_ROOT/gmcache. 5. Remove all of the files so that the entire directory is empty. 6. Restart WebSphere Voice Server.
Chapter 8. Troubleshooting
469
See the Configuration parameters on page 105 page for more information on all of the cache-related parameters.
470
Or, if you are trying to compile a grammar using voiceTest and it takes 10 minutes or more to compile, you may see an error similar to the following:
define -grammar /opt/WebSphere/VoiceServer/lib/busLssi.bnf IBM WebSphere Voice Server voiceTest IBM WebSphere Voice Server voiceTest [04/06/22 13:37:06:928 EDT] main pt A CWVPT0027I: Connecting to localhost 554... [04/06/22 13:37:07:226 EDT] Thread-1 pt A CWVPT0029I: Waiting for reply... [04/06/22 13:37:07:227 EDT] Thread-1 pt A CWVPT0030I: RTSP session: "0.IBM.34.34.130.1" [04/06/22 13:37:07:230 EDT] main pt A CWVPT0028I: RTP contact at 34.34.130.1 50002 [04/06/22 13:49:56:904 EDT] main pt E CWVPT0010E: RTSP error 500 Internal Server Error
These errors indicate that you need to increase the WebSphere Application Server Maximum Heap Size setting. The default setting is 256 MB for WebSphere Voice Server versions 5.1, 5.1.1, and 5.1.2. The default setting for WebSphere Voice Server version 5.1.3 is 512 MB. To 1. 2. 3. 4. increase the Maximum Heap Size setting, do the following: Launch and log in to the administrative console. In the left navigation pane, select Servers, and then select Application Servers. Click the name of the server you are using. By default, it is server1. On the server panel, in the Additional Properties table, click Process Definition. 5. On the Process Definition panel, in the Additional Properties table, click Java Virtual Machine. 6. On the Java Virtual Machine panel, in the Configuration table, increase the value of the Maximum Heap Size in MB. 7. Click the Apply button at the bottom of the Configuration table to save your changes to the master configuration.
Chapter 8. Troubleshooting
471
472
IBM TTS Connector for Genesys Voice Platform for WebSphere Voice Server troubleshooting tips
This topic contains troubleshooting tips for the IBM Text-to-Speech (TTS) Connector for Genesys Voice Platform (GVP) for WebSphere Voice Server. If you are experiencing problems with the IBM TTS Connector, enable trace for the IBM TTS Connector. Three parameters control the logging and tracing in the IBMTextToSpeech.ini: EnableTrace, MrcpTraceDir, and LogFile. To enable trace on the TTS Connector, set the EnableTrace parameter in the IBMTextToSpeech.ini file to 1 instead of 0 (EnableTrace=1). The log file is located at LogFile=LOGDIR\mrcplog.txt, where LOGDIR is the directory for log and trace files. The installer sets this to the directory where Genesys puts its log files, however you may wish to change it because the file has a tendency to grow quite large on systems with a lot of calls. By default (EnableTrace=0), only errors are logged in this file. MrcpTraceDir=LOGDIR is the directory where the Media Resource Control Protocol (MRCP) trace files are created. A separate file is created for each channel and will contain all the messages exchanged through the MRCP connection for that channel. The files will be named in the MRCP-xxx.txt convention, where xxx is the channel number. These files will be created only if EnableTrace=1. For more information on IBMTextToSpeech.ini file parameters, refer to Configuring the IBM TTS Connector for Genesys Voice Platform for WebSphere Voice Server.
Chapter 8. Troubleshooting
473
User Response: Type net helpmsg dddd, where dddd is the error code, at the command line. RTSP error: MMMM Explanation: MMMM contains the first line of the RTSP message. User Response: Type net helpmsg dddd, where dddd is the error code, at the command line. You can also examine the MRCP-xxx trace files for details. Malformed RTSP message: LLL Explanation: Could not parse the RTSP line, where LLL is the line. This indicates a network communication problem, like connecting to a non MRCP socket. User Response: Check the RTSP URL in the configuration file and examine the MRPC-xxx trace files. Malformed RTSP header: HHH Explanation: Could not parse the RTSP header. HHH contains the line with the invalid header. User Response: Check the MRCP-xxx trace files for more information. Could not setup synthesizer service Explanation: RTSP SETUP failed. This error is returned when a SETUP request fails for any reason other than an RTSP or network communication error. User Response: Check the MRCP-xxx trace files for more information. MRCP reply not expected: [MMMM] Explanation: MMMM contains the first line of the unexpected MRCP message. User Response: Check the MRCP-xxx trace files for more information.
To resolve this issue, specify the language attribute either in the grammar file or by using the voiceTest -speech-language command-line parameter.
474
If you have a similar error message, then your machines RPM database has been corrupted. This generally occurs if the machine is powered off midway through installing an application. This error has also occurred on systems with bad hard disk sectors. To fix the problem:
Chapter 8. Troubleshooting
475
1. Uninstall WebSphere Voice Server. 2. From a system shell running as a root user, issue the rpm --rebuilddb command. 3. Issue the rpm -qa command again to confirm that there are no error messages generated. 4. Reinstall WebSphere Voice Server.
Errors
If the WebSphere Voice Server installation program indicates that errors were encountered while installing the product, do the following: 1. Browse all of the log files in $WVS_ROOT/logs/ for clues. Pay particular attention to the main installation log file, CWVinstall.log. 2. Check the command prompt from which the installation panel was launched for error messages. 3. Look up any error or warning messages in the message reference table. 4. Review Troubleshooting the Installation.
476
v There are errors after enabling Secure Sockets Layer. v There are Errors in messaging. If you do not see a problem that resembles yours, or if the information provided does not solve your problem, see the IBM Support page. The IBM Support site provides current information available on known problems and their resolutions. IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a Problem Management Report (PMR), see the IBM Support page.
Chapter 8. Troubleshooting
477
478
479
480
Trademarks
Advanced Function Presentation, AFP, AIX, AIX 5L, DB2, developerWorks, Domino, e-business on demand, Everyplace, IBM, Lotus, Lotus Notes, POWER, pSeries, Rational, Redbooks, Tivoli, ViaVoice, WebSphere, xSeries, and z/OS are trademarks or registered trademarks of the International Business Machines Corporation in the United States, other countries, or both. Intel, Intel Inside (logos), MMX and Pentium are trademarks of Intel Corporation in the United States, other countries, or both. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others.
481
482
Glossary
2PKDP. See Two-Party Key Distribution Protocol. 3G. See third generation. ADSL. See Asymmetric Digital Subscriber Line. Advanced Function Presentation. A set of licensed programs, together with user applications, that use the all-points-addressable concept to print data on a wide variety of printers or to display data on a variety of display devices. AFP includes creating, formatting, archiving, retrieving, viewing, distributing, and printing information. Advanced Interactive eXecutive. See AIX. Advanced Mobile Phone Service (AMPS). The original analog cellular network and currently the worlds largest cellular standard. Advanced Radio Data Information Service (ARDIS). A wireless data network from American Mobile Satellite Corporation that covers more than 11,000 cities and towns in the U.S. Operating in the 806-824/851-869MHz bands, ARDIS is a packet-switched network that provides a data rate of 19.2 Kbps and is known for its deep penetration into buildings. Primarily used for field service and transportation applications, ARDIS was created by Motorola in the mid-1980s for IBMs field service division and was later spun off as a commercial service. AIX (Advanced Interactive eXecutive). A UNIX operating system developed by IBM that is designed and optimized to run on POWER microprocessor-based hardware such as servers, workstations, and blades. AMI-C. See Automotive Multimedia Interface-Collaboration. AMPS. See Advanced Mobile Phone Service. ARDIS. See Advanced Radio Data Information Service. Asymmetric Digital Subscriber Line (ADSL). A technology based on Digital Subscriber Line (DSL) technology that is for Internet access where fast downstream is required, but slow upstream is acceptable. ASYNC. See asynchronous. asynchronous (ASYNC). Pertaining to events that are not synchronized in time or do not occur in regular or predictable time intervals. For example, input events are controlled by the user; the program can read them later.
Copyright IBM Corp. 2005, 2006
asynchronous transfer mode (ATM). A communications method in which information is organized into small, fixed-length cells that recur without regular or predictable time relationships. ATM incorporates network switches and negotiated service connections. ATM. See asynchronous transfer mode. Automotive Multimedia Interface-Collaboration (AMI-C). A worldwide organization of automobile manufacturers that is involved in the standardization of automotive multimedia interfaces to motor vehicle communication networks. base station (BS). An earth-based transmitting and receiving station for cellular phones, paging services and other wireless transmission systems. Bluetooth. Technology specification created for short-range (up to 10 meters) wireless connection using low-cost transceiver chips to be embedded in mobile PCs, smart phones, and other portable devices. Provides three voice and data channels via a one-to-one connection with built-in encryption and verification. BOOTP. See Bootstrap Protocol. Bootstrap Protocol (BOOTP). A protocol that allows a client to find both its Internet Protocol (IP) address and the name of a file from a server on the network. bot. A program used on the Internet that performs a repetitive function such as searching for information. BS. See base station. CDMA. See code division multiple access. CDPD. See cellular digital packet data. cellular digital packet data (CDPD). A standard for transmitting data over a cellular network that places the data in digital electronic envelopes and sends it at high speed through underused radio channels or during pauses in cellular phone conversations. Cellular Telecommunications Industry Association (CTIA). A trade group that represents cellular, PCS, and enhanced specialized mobile radio carriers. Challenge Handshake Authentication Protocol (CHAP). An authentication protocol that protects against eavesdropping by encrypting the user name and password. See also Password Authentication Protocol.
483
CHAP. See Challenge Handshake Authentication Protocol. CLNP. See Connectionless Network Protocol. CMRS. See Commercial Mobile Radio Services spectrum. code division multiple access (CDMA). A form of multiplexing where the transmitter encodes the signal using a pseudo-random sequence, which the receiver also knows and can use to decode the received signal. Each different random sequence corresponds to a different communication channel. Commercial Mobile Radio Services spectrum (CMRS). An organization that provides cellular, PCs, mobile radio, paging, and other wireless services. Connectionless Network Protocol (CLNP). An OSI protocol for the delivery of data. It uses datagrams (packets) that include address information for routing network messages. Used in local area networks (LANs) rather than wide area networks (WANs). copper chip technology. A technology in which chips exploit the capabilities of copper circuitry, which passes electrical currents more easily than aluminum. Aluminum has been the traditional material used in the wires that connect the switches, or transistors, in silicon chips. Copper chip technology produces smaller, faster chips that have enormous capacity for holding and transmitting information. CTIA. See Cellular Telecommunications Industry Association. DARPA. See Defense Advanced Research Projects Agency. data communication equipment (DCE). A device that establishes, maintains and terminates a session on a network. It may also convert signals for transmission. It is typically the modem. Data Encryption Standard (DES). A cryptographic algorithm designed to encrypt and decrypt data using a private key. DataTAC. A technology for radio packet-data networks that was developed by Motorola. data terminal equipment (DTE). A communications device that is the source or destination of signals on a network. It is typically a terminal or computer. DB2. A family of IBM licensed programs for relational database management. DCE. See data communication equipment. DCT. See Digital Cordless Telephone.
DECT. See Digital European Cordless Telecommunications. Defense Advanced Research Projects Agency (DARPA). The United States Department of Defense agency responsible for creating ARPANET, a large TCP/IP network. This agency was formerly called the Advanced Research Projects Agency (ARPA). DES. See Data Encryption Standard. DHCP. See Dynamic Host Configuration Protocol. Digital Cordless Telephone (DCT). A cordless telephone that uses digital transmission technology to provide more security and better sound quality than a traditional analog cordless telephone. Digital European Cordless Telecommunications (DECT). A digital wireless telephone technology that is expected to make cordless phones much more common in both businesses and homes. Digital Subscriber Line (DSL). A technology that dramatically increases the digital capacity of ordinary telephone lines in the home or office. DNS. See Domain Name System. Domain Name System (DNS). The distributed database system used to map domain names to IP addresses. DSL. See Digital Subscriber Line. DTE. See data terminal equipment. Dynamic Host Configuration Protocol (DHCP). A communications protocol that is used to centrally manage configuration information. For example, DHCP automatically assigns IP addresses to computers in a network. The Dynamic Host Configuration Protocol is defined by the Internet Engineering Task Force (IETF). EDGE. See Enhanced Data GSM Environment. electronic serial number (ESN). Unique identification number embedded in a wireless phone by the manufacturer to prevent fraud. ESN differs from the mobile identification number, which is the wireless carriers identifier for a phone in the network. embedded system. A computer system that is a component of a larger machine or system. Embedded systems can respond to events in real time. Hosts of embedded systems include watches, household appliances, cars, and cellular phones. Enhanced Data GSM Environment (EDGE). A faster version of the GSM wireless service that is designed to deliver data at rates up to 384 Kbps and enable the delivery of multimedia and other broadband applications to mobile phone and computer users. The EDGE standard is built on the existing GSM standard,
484
using the same time-division multiple access (TDMA) frame structure and existing cell arrangements. EPOC. An operating system designed for mobile devices. ESN. See electronic serial number. E-TDMA. See extended time division multiple access. extended time division multiple access (E-TDMA). See also Time Division Multiple Access. Extensible Markup Language (XML). A standard metalanguage for defining markup languages that is based on Standard Generalized Markup Language (SGML). XML simplifies the process of authoring and managing structured information and transmitting and sharing structured information across diverse computing systems. File Transfer Protocol (FTP). In TCP/IP, an application protocol used for transferring files to and from host computers. fixed wireless data. Wireless service to a fixed location through antennas larger than those in mobile or portable setups. The fastest data throughputs--up to T-1 speed--are available over fixed wireless networks. FTP. See File Transfer Protocol. full user mobility. Wireless classification under which users can access data while in motion, for example, in a vehicle. gateway. A ground-based link to a mobile satellite service network. General Packet Radio Service (GPRS). A packet data communications system that allows information to be sent and received across a mobile telephone network. GPRS permits faster Internet access and improved mobile technology through continuous connectivity. GEOS. See geo-stationary Earth orbit systems. geo-stationary Earth orbit systems (GEOS). Communications system with satellites in geosynchronous orbits 22,300 miles above Earth. global mobile personal communications services (GMPCS). Future mobile satellite systems that will provide global wireless phone service. global positioning system (GPS). A satellite constellation that provides highly accurate position, velocity, and time navigation information to users. Global System for Mobile Communications (GSM). A standard for digital cellular telephone systems that originated in Europe and is now used in countries across the globe. GSM networks support voice, data, text, and facsimile transmissions.
GMPCS. See global mobile personal communications services. GPRS. See General Packet Radio Service. GPS. See global positioning system. GSM. See Global System for Mobile Communications. Handheld Device Markup Language (HDML). A specialized version of HTML designed to enable wireless pagers, cell phones and other handheld devices to obtain information from Web pages. HDML. See Handheld Device Markup Language. HLR. See home location register. home location register (HLR). A database in a cellular system that contains all the subscribers within the providers home service area. HTTP. See Hypertext Transfer Protocol. HTTP-NG. See HyperText Transfer Protocol-Next Generation. Hypertext Transfer Protocol (HTTP). An Internet protocol that is used to transfer and display hypertext and XML documents on the Web. HyperText Transfer Protocol-Next Generation (HTTP-NG). A replacement for HTTP 1.0, HTTP-NG maintains HTTP 1.0s simplicity while adding important features such as security and authentication. ICMP. See Internet Control Message Protocol. iDEN. See integrated digital enhanced network. independent software vendor (ISV). A non-IBM software vendor. infrared technology (IR). A technology that uses infrared radiation for wireless transmission between computer devices, as well as many handheld remotes for TVs and video and stereo equipment. Infrared transmission requires an unobstructed line of sight between transmitter and receiver. integrated digital enhanced network (iDEN). A Motorola-enhanced mobile radio network technology that integrates two-way radio, telephone, text messaging, and data transmission into a single network. Integrated Services Digital Network (ISDN). An international communications standard for sending voice, video, and data over digital telephone lines. Internet Control Message Protocol (ICMP). An Internet protocol that is used by a gateway to communicate with a source host, for example, to report an error in a datagram.
Glossary
485
Internet screenphone. A telephone-like appliance with a built-in display screen that may be used to call up Internet sites quickly. Internet service provider (ISP). An organization that provides access to the Internet. in-vehicle information system (IVIS). A system that enables intelligent vehicles to provide the functionality to increase the productivity and safety of the driver. IR. See infrared technology. IS-95. Spread spectrum air interface technology used in some digital cellular and personal communications services, and other wireless networks. ISDN. See Integrated Services Digital Network. ISP. See Internet service provider. ISV. See independent software vendor. ITU-2000. The new third generation global standard for mobile telecommunications, coined by the International Telecommunications Union. Also known as IMT-2000. IVIS. See in-vehicle information system. Java. An object-oriented programming language for portable interpretive code that supports interaction among remote objects. Java was developed and specified by Sun Microsystems, Incorporated. Jini. A trademark for technology licensed by Sun Microsystems. Jini is a Java-based connection technology. It allows Jini-compatible devices such as printers to connect transparently to a network and to interact. kiosk services. Solutions for business center service providers such as hotel chains, airports and office service franchises that offer document services (storing, reproduction and distribution) through shared access devices in public spaces. LAN. See local area network. LDAP. See Lightweight Directory Access Protocol. LEC. See local exchange carrier. LEO. See low earth orbit. Lightweight Directory Access Protocol (LDAP). An open protocol that uses TCP/IP to provide access to directories that support an X.500 model and that does not incur the resource requirements of the more complex X.500 Directory Access Protocol (DAP). For example, LDAP can be used to locate people, organizations, and other resources in an Internet or intranet directory.
Linux. An open source implementation of the UNIX system. LMDS. See Local Multipoint Distribution Service. LNP. See local number portability. local area network (LAN). A network that connects several devices into a limited area (such as a single building or campus) and that can be connected to a larger network. local exchange carrier (LEC). An authorized carrier that has been commissioned to provide local voice-level telecommunications services within a predetermined area. Local Multipoint Distribution Service (LMDS). A system for broadband microwave wireless transmission direct from a local antenna to homes and businesses within a line-of-sight radius; a solution to the so-called last-mile technology problem of economically bringing high-bandwidth services to users. LMDS is an alternative to installing optical fiber all the way to the user or to adapting cable TV for broadband Internet service. local number portability (LNP). Subscribers ability to switch local or wireless carriers and still retain the same phone number, as is possible now with long-distance carriers. low earth orbit (LEO). An orbit between 700 and 2,000 kilometers above the Earth that is used by mobile communications satellites. MAN. See metropolitan area network. MDSP. See Mobile Data Synchronization Protocol. MDSS. See Mobile Data Synchronization Service. MEMS. See Micro-Electric Mechanical System. metropolitan area network (MAN). A network formed by the interconnection of two or more networks which may operate at higher speed than those networks, may cross administrative boundaries, and may use multiple access methods. See also wide area network. microbrowser. A Web browser designed for small display screens on smart phones and other handheld wireless devices. Micro-Electric Mechanical System (MEMS). A technology that embeds mechanical devices such as fluid sensors, mirrors, actuators, pressure and temperature sensors, vibration sensors and valves in semiconductor chips. middleware. Software that connects two separate applications and passes data between them. For example, a type of middleware can link a database
486
system to a Web server. This allows users to request information from the database using forms displayed on a Web browser, and it enables the server to return dynamic Web pages based on the users request and profile. MNCRS. See Mobile Network Computing Reference Specification. Mobile Data Synchronization Protocol (MDSP). A protocol that defines the form of an XML document for data exchange. Insertions, modifications, and deletions of items in a data store can be described in MDSP documents. Mobile Data Synchronization Service (MDSS). The ability to synchronize data on client devices with data stored in an enterprise database. A common protocol has been developed that will eventually allow a variety of clients to synchronize with a variety of databases. Mobile Network Computing Reference Specification (MNCRS). A specification that defines a set of standards for mobile Java devices. mobile satellite service (MSS). A radiocommunication service between mobile earth stations and one or more space stations, or between space stations used by this service. mobitex. An open standard for sharing information among mobile devices using radio transmission. MQLite. A lightweight message queuing facility that provides a subset of MQ Series functionality. MQLite transmits Mobile Data Synchronization Protocol (MDSP) documents between the client and the mid-tier server. MSS. See mobile satellite service. multi-modal. Pertaining to a system that operates using multiple interfaces (e.g. both text and speech). Multi-modal paradigm user interfaces (MMUIs) will be used in next-generation devices to allow interaction via voice, touch and keyboard input. NAMPS. See Narrowband Advanced Mobile Phone Service. Narrowband Advanced Mobile Phone Service (NAMPS). A standard that combines cellular voice processing with digital signaling, increasing the capacity of Advanced Mobile Phone Service (AMPS) systems and adding functionality. National Telecommunications and Information Administration (NTIA). The United States governments authority on spectrum management. Network News Transfer Protocol (NNTP). A protocol that is used to post messages in, distribute messages to,
and retrieve messages from newsgroups and to transfer articles between news servers. NNTP. See Network News Transfer Protocol. NTIA. See National Telecommunications and Information Administration. ODBC. See Open Database Connectivity. Open Database Connectivity (ODBC). A standard application programming interface (API) for accessing data in both relational and nonrelational database management systems. Using this API, database applications can access data stored in database management systems on a variety of computers even if each database management system uses a different data storage format and programming interface. Open Service Gateway (OSG). A specification that is being defined by the Open Service Gateway initiative (OSGi), a consortium of more than 20 companies, including IBM. The OSG specification will outline open standards for the management of voice, data and multimedia wireless and wired networks.. open systems interconnection (OSI). The interconnection of open systems in accordance with standards of the International Organization for Standardization (ISO) for the exchange of information. OSG. See Open Service Gateway. OSI. See open systems interconnection. Palm OS platform. An operating system for handheld devices, designed for information management. PAN. See personal area network. PAP. See Password Authentication Protocol. Password Authentication Protocol (PAP). A type of authentication where the user name and password are transmitted in an unencrypted form. This is a more basic form of authentication than Challenge Handshake Authentication Protocol (CHAP). See also Challenge Handshake Authentication Protocol. PCMCIA. See Personal Computer Memory Card International Association. PCS. See personal communication system. PDA. See personal digital assistant. PDC. See personal digital cellular. personal area network (PAN). Experimental IBM technology that allows information devices to communicate discreetly and synchronize with one another when in close proximity, using the human body as an antenna.
Glossary
487
personal communication system (PCS). A Federal Communications Commission classification for digital wireless communication systems based on the same principles as cellular systems, but usually operating in a different frequency range and with smaller cell sizes than cellular systems. Personal Computer Memory Card International Association (PCMCIA). An international standards body and trade association founded in 1989 to establish a standard for connecting peripherals to portable computers. personal digital assistant (PDA). A handheld device that is used for personal organization tasks (such as calendaring, note-taking, and recording telephone and fax numbers), and networking functions such as email and synchronization. personal digital cellular (PDC). Technology used in digital cellular telephone communication in Japan. Personal Handy Phone System (PHS). Personal communications system used in Japan as both a digital cordless phone in homes and offices and as a cellular phone outdoors. PHS. See Personal Handy Phone System. Pocket PC. A handheld Windows-based computer that runs the Pocket PC operating system (formerly Windows CE). Point-to-Point Protocol (PPP). A data-link protocol for communication between two computers that use a serial interface, typically a personal computer connected by telephone line to a server. POP3. See Post Office Protocol Version 3. portable wireless data. A classification of networks that access the Internet through a laptop or palmtop computer and a small wireless modem. Post Office Protocol Version 3 (POP3). A mail protocol that allows clients running it to retrieve mail from a host mail server also running the protocol. PPP. See Point-to-Point Protocol. radio frequency (RF). An alternating current that generates an electromagnetic field when applied to an antenna. The generated electromagnetic field is suitable for wireless broadcasting and communications. RAM. See random access memory. random access memory (RAM). Computer memory in which any storage location can be accessed directly. RC5. An encryption technology for use in wireless clients and servers. RF. See radio frequency.
Scalable Vector Graphics (SVG). A vector graphics language written in XML. SDK. See software development kit. SDSL. See symmetric digital subscriber line. Secure Sockets Layer. A security protocol that provides communication privacy. With SSL, client/server applications can communicate in a way that is designed to prevent eavesdropping, tampering, and message forgery. set-top box. A single or multiple tuner device that enables the display of cable or satellite signals on a television. SGML. See Standard Generalized Markup Language. Short Message Service (SMS). A service that is used to transmit text to and from a mobile phone. SiGe. See silicon-germanium technology. Signaling System 7 (SS7). The international high-speed signaling backbone used for the public-switched telephone network. silicon-germanium technology (SiGe). A technology that makes possible the design of complex chips that integrate the functions of a cellular telephone, an e-mailbox and an Internet browser into a hand-held information device with rapid data transfer capability. Silicon-On-Insulator (SOI). A microchip technology that provides faster computer chips that also require less power, a key requirement for extending the life of pervasive devices. SIM. See subscriber identity module. Simple Mail Transfer Protocol. An Internet application protocol for transferring mail among users of the Internet. SMTP specifies the mail exchange sequences and message format. It assumes that the Transmission Control Protocol (TCP) is the underlying protocol. smart phone. A phone that enables connections to the Internet or Lotus Notes network so that users can access e-mail, faxes, voice mail, Web pages and other files. It can also connect to a speech recognition server by phone so that a user can dictate notes or responses and then see the recognized text as it is returned from the server. SMF. See System Management Facility. SMS. See Short Message Service. software development kit (SDK). A set of tools, APIs, and documentation to assist with the development of software in a specific computer language or for a particular operating environment.
488
SOI. See Silicon-On-Insulator. SQL. See Structured Query Language. SS7. See Signaling System 7. Standard Generalized Markup Language (SGML). A standard metalanguage for defining markup languages that is based on the ISO 8879 standard. SGML focuses on structuring information rather than presenting information; it separates the structure and content from the presentation. It also facilitates the interchange of documents across an electronic medium. Structured Query Language (SQL). A standardized language for defining and manipulating data in a relational database. subscriber identity module (SIM). A smart card inserted into GSM phones that contains the users telephone account information, and that allows the user to use a borrowed or rented GSM phone as if it were his or her own. SVG. See Scalable Vector Graphics. symmetric digital subscriber line (SDSL). A technology that uses digital pulses to send data over copper telephone lines. SDSL cannot operate simultaneously with voice connections over the same wires. System Management Facility (SMF). A z/OS facility that collects and records a variety of system and job-related information. Examples of information collected by SMF are statistics, accounting information, and performance data. TACS. See Total Access Communication System. TCP/IP. See Transmission Control Protocol/Internet Protocol. TDMA. See Time Division Multiple Access. third generation (3G). The next generation of wireless technology. Multimedia 3G networks transmit wireless data up to 2 megabits per second, making possible the integration of voice, data and video. Time Division Multiple Access (TDMA). A digital communication technology used by some carriers to provide PCS service. TDMA is a multiplexing technology used with satellites and cell phones, in which multiple channels of data are interleaved (each signal is assigned to a different time interval, and the signals are transmitted by taking turns). See also extended time division multiple access. Time-Modulated Ultra-Wide Band (TM-UWB). New wireless technology that greatly broadens bandwidth. Developed by Time Domain, TM-UWB uses short, coded pulses transmitted over a wide range of frequencies, making it useful for a broad range of
applications from networking to through-the-wall radar and secure communications. TM-UWB. See Time-Modulated Ultra-Wide Band. Total Access Communication System (TACS). An analog cellular phone system deployed mostly in Europe. It was modeled after the AMPS system in the U.S. transcoding. The operation of changing data from one format to another, such as XML to HTML, so that the output will be displayed in a manner appropriate to the device. Transmission Control Protocol/Internet Protocol (TCP/IP). An industry-standard nonproprietary set of communications protocols that provide reliable end-to-end connections between applications over interconnected networks of different types. Two-Party Key Distribution Protocol (2PKDP). A security protocol that combines bidirectional authentication with key distribution using a minimal number of messages. UDP. See User Datagram Protocol. UMTS. See Universal Mobile Telecommunications System. Universal Mobile Telecommunications System (UMTS). The third generation mobile telecommunications standard, defined by the ITU, that increases transmission speed to 2 Mbps per mobile user and establishes a global roaming standard. User Datagram Protocol (UDP). An Internet protocol that provides unreliable, connectionless datagram service. It enables an application program on one machine or process to send a datagram to an application program on another machine or process. virtual private network (VPN). An extension of a companys intranet over the existing framework of either a public or private network. A VPN ensures that the data that is sent between the two endpoints of its connection remains secure. Voice over Internet Protocol (VoIP). Sending telephony voice over Internet Protocol (IP) data connections rather than existing dedicated voice networks, switching and transmission equipment. VoIP. See Voice over Internet Protocol. VPN. See virtual private network. WAN. See wide area network. WAP. See Wireless Application Protocol. WBXML. See Wireless Binary XML.
Glossary
489
W-CDMA. See wideband code division multiple access. WDF. See Wireless Data Forum. Web pad. A handheld, touch-screen wireless device for Web browsing. wide area network (WAN). A network that provides communication services between devices in a geographic area larger than that served by a local area network (LAN) or a metropolitan area network (MAN). See also metropolitan area network. wideband code division multiple access (W-CDMA). A CDMA channel that is four times wider than the channels that are typically used in 2G networks in North America. It supports very high-speed multimedia services such as full-motion video. It uses one 5 MHz channel for both voice and data, offering data speeds up to 2 Mbps. Wideband CDMA is known as UMTS in Europe. WiFi. See Wireless Fidelity. WIN. See wireless intelligent network. WinCE. See Windows CE. Windows CE (WinCE). A version of the Windows operating system designed for handheld devices. Version 3 is often known as Pocket PC. Wireless Application Protocol (WAP). An open industry standard for mobile Internet access that allows mobile users with wireless devices to easily and instantly access and interact with information and services. Wireless Binary XML (WBXML). A succinct encoding of XML defined by the WAP Forum. MDSP documents are encoded into WBXML and the WBXML byte stream is sent by enqueuing it on an MQLite queue as a single message object. Wireless Data Forum (WDF). An industry group dedicated to promoting wireless data. Wireless Fidelity (WiFi). A high-frequency wireless local area network. WiFi technology is rapidly gaining acceptance in many companies as an alternative to a wired LAN. It can also be installed for a home network. wireless intelligent network (WIN). Wireless switched network that allows carriers to provide enhanced and customized services for mobile phones. wireless LAN. A network that uses wireless transmissions such as radio or infrared to provide communication services between devices. Wireless Markup Language (WML). A markup language based on XML that is used to present content
and user interfaces for wireless devices such as cellular phones, pagers, and personal digital assistants. wireless network. See wireless LAN. Wireless Session Protocol (WSP). A sandwich layer that links the Wireless Application Environment (WAE) to two session services: one connection-oriented, operating above the Wireless Transaction Protocol, the other connectionless, operating above the Wireless Datagram Protocol. WML. See Wireless Markup Language. WSP. See Wireless Session Protocol. XML. See Extensible Markup Language.
490
Index A
accessibility features 7 addNode command 96, 99 administrative console configuring engines 93 filtering 121 icons 120 login settings 119 navigation tree 120 starting 117 starting a server 125 stopping 117 stopping a server 125 taskbar 120 using 117 workspace 120 ASR settings languages installed 93 number of engines 93 preinstalling grammars 93
G
Genesys support 112 German phonetic alphabet 22 getParam sample 127 GVP installation prerequisites 88
P
planning voice system 43 planning resources ASR engines 47 LAN 48 TTS engines 47 post-installation 85 pronunciations 20 putParam sample 128
H
hardware requirements HTTP server starting 142 stopping 142 48
R
Red Hat prerequisites 60 removeNode command 99 response file 83 restoreVoiceServerConfig sample backup_file parameter 134 global security 134 help parameter 134
I
IBM Support collecting information 458 collector tool 458 IBM TTS Connector configuration parameters 113 IBMTextToSpeech.ini file 113 identifiers 452 Information Center 13 information conventions 15 installation errors 475 installation prerequisites 60 installation resources 83 installation tips 83 installation verification test 83 troubleshooting 476 installing fix pack 79 IP configurations 60
B
backupVoiceServerConfig sample backup_file parameter 132 global security 132 help parameter 132
S
sample scripts backupVoiceServerConfig 132 getParam 127 putParam 128 restoreVoiceServerConfig 134 startVoiceServer 129 statusVoiceServer 131 stopVoiceServer 130 scripting 95 samples 126 wsadmin tool 126 security 9, 125 Simplified Chinese phonetic alphabet software requirements 48 speech applications 18 speech technology business advantages 1 overview 2 standards for developing grammars 17 TTS 17 startServer 129 startVoiceServer sample global security 129 help parameter 129 statusVoiceServer sample global security 131 help parameter 131 stopVoiceServer sample global security 130 help parameter 130 wvsonly parameter 130
C
Canadian French phonetic alphabet collector tool 458 command line tools 95 configuration parameters 105 Configuration Service MBean 102 configuration settings 122 console extensions 81 creating custom scripts 101 21
J
Japanese phonetic alphabet 24
27
D
deployment manager 80, 81
L
Latin American Spanish phonetic alphabet 26 LaunchPad 61 Load Balancer 82 log messages 154
E
Edge Component 82 environments multiple machines 54 single machine 50
M
message IDs 154 messages 154 MIME mapping 105
F
First Steps 85 firststeps command 85
N
Network Deployment uninstalling 90 notices 481 53, 54, 80, 81
T
testing grammars 18
491
topologies multiple machines 53 tracing 453 trademarks 481 troubleshooting installation 475 installation verification test 476 messages 153 testing 476 troubleshooting tips administrative 461 ASR 467 gateways 474 IBM TTS Connector 473 installation 461 management 477 runtime 477 security 462 TTS 463 voiceTest 474 TTS settings default voice 94 number of engines 94 preloading grammars 94 voices installed 94 tuning configuration settings 145 AIX 147 Cisco gateway 150 for Avaya 145 for Cisco 145 for Genesys 145 Linux 148 SUSE 149 WebSphere Application Server 146 Windows 149 speech resources 19
WebSphere Voice Server access 8 features 6 installing 57, 59, 68 messages 153 overview 4 package 58 previous versions 11 resources for learning 479 restarting server processes 135 scalability 9 silent installation 76 tools 10 troubleshooting tools 9 uninstalling 88 WebSphere Voice Toolkit 10 WVSAdminConfig script 101
U
UK English phonetic alphabet 38 uninstalling administrative console extensions 90 US English phonetic alphabet 39 user dictionary 20
V
voice server adding 96 removing 99 Voice Servers panel configuration problems 122 runtime messages 122 server status 122 Voice Toolkit 18 VoiceXML 17
W
WebSphere Application Server manually uninstalling 90 uninstalling 90 WebSphere family 12 WebSphere Voice Response support
112
492
How satisfied are you that the information in this book is: Very Satisfied Accurate Complete Easy to find Easy to understand Well organized Applicable to your tasks h h h h h h Satisfied h h h h h h Neutral h h h h h h Dissatisfied h h h h h h Very Dissatisfied h h h h h h
h Yes
h No
When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any way it believes appropriate without incurring any obligation to you. IBM or any other organizations will only use the personal information that you supply to contact you about the issues that you state on this form.
Address
___________________________________________________________________________________________________
Fold and _ _ _ _ _ _ _ _ _ _Fold and_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please _ _ _ _ _ staple _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Tape _ _ _ _ _ _ _ _ Tape _ _ _ _ do not _ _ _ _ NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES
IBM Corporation Information Development Department MMOA P.O. Box 12195 Research Triangle Park, NC 27709-9990
_________________________________________________________________________________________ Please do not staple Fold and Tape Fold and Tape