PB418407
Configuration
Nuance SWMS with Nuance OpenSpeech Recognizer and RealSpeak
• Modify server.transport.sessionTimeout to -1.
• Modify server.resource.2.url to /recognizer and uncomment this line.
• Modify server.ossrec.cache.maxNumber so that it matches the number of Nuance OpenSpeech Recognizer (OSR) licenses and uncomment this line.
• Modify server.session.ossrec.mrcp.startOfSpeechOnDTMF to 0.
• Modify server.resource.4.url to /synthesizer and uncomment this line.
• Modify server.realspeak4.cache.maxNumber to match the number of Nuance RealSpeak licenses and uncomment this line.
Nuance MRCP 1.0 with Nuance 8.5 Speech Recognition and Vocalizer
• No change is needed.
• Modify the Nuance startup file. The path name to the startup file follows this format: C:\Nuance\V8.5.0\mrcp\watcher.startup.
• Make the following modifications as appropriate:
– Add the parameter tts.ResourceName=en-US-female to the command line for the Nuance Vocalizer TTS process (for the U.S. English female voice, which is the default). Also remember to update this value appropriately for different voice packs; for example, for the Australian English male voice, set the parameter to en-AU-male.
– If you are running two or more vocalizer TTS processes on the same machine, you must set tts.Port and dictionary.Port parameters for all except one TTS process. The default value for tts.Port is 32323, and the value for dictionary.Port is 22552. For every additional vocalizer process, this parameter needs to be explicitly set to a number other than the default.
• If you are using the default 2-port license included with the Nuance Vocalizer installation and have not purchased licenses, you need to make the following changes to enable TTS to work. This is usually the case if you are setting up TTS for demo or lab purposes. The Nuance startup file by default points to an invalid Nuance Vocalizer 4.0 license file. To correct it, modify the existing line for TTS nlm as follows:
From: nlm %MRCP%/voclicense.txt
To: nlm %VOCALIZER%/license.txt
IBM WebSphere Voice Server
1. Stop IBM WebSphere Voice Server.
2. Choose Start > All Programs > IBM WebSphere > Application Server v5.1 > Administrator Console.
3. After logging in, you should see a page displaying voice servers. Select the desired server and click Stop.
4. Open a DOS window and browse to the folder C:\Program Files\WebSphere\VoiceServer\samples.
5. Type the following command at the DOS prompt (you may want to use cut and paste to minimize errors):
putParam com.ibm.voice.server.rtspbridge.recourl /recognizer true
6. Make sure there are no errors. Then restart IBM WebSphere Voice Server.
7. Launce IBM WebSphere Application Server V5 - server1 from the Services window.
8. Choose Start > All Programs > IBM WebSphere > Application Server v5.1 > Administrator Console.
9. After logging in, you should see a page displaying voice servers. Make sure the status indicates "Started."
1. Stop IBM WebSphere Voice Server.
2. Choose Start > All Programs > IBM WebSphere > Application Server v5.1 > Administrator Console.
3. After logging in, you should see a page displaying voice servers. Select the desired server and click Stop.
4. Open a DOS window and browse to the folder C:\Program Files\WebSphere\VoiceServer\samples.
5. Type the following command at the DOS prompt (you may want to use cut and paste to minimize errors):
putParam com.ibm.voice.server.rtspbridge.synthurl /synthesizer true
6. Make sure there are no errors. Then restart IBM WebSphere Voice Server.
7. Launch IBM WebSphere Application Server V5 - server1 from the Services window.
8. Choose Start > All Programs > IBM WebSphere > Application Server v5.1 > Administrator Console.
9. After logging in, you should see a page displaying voice servers. Make sure the status indicates "Started."