Avaya 2 Text-to-Speech problems

Contents

Issue 1.0 April 2006 33

Text-to-Speech problems

This section describes how to find and resolve problems related to the Text-to-Speech (TTS)

feature.

Speechify or RealSpeak TTS port state stays INSERV when LAN is down

The SpeechWorks Speechify or RealSpeak proxy software on the Avaya IR system does not

detect when the LAN connection to the speech server is inactive and leaves the TTS port

state as INSERV. As a result, callers hear silence, since the port on the IR system is still in

service. The caller must hang up to terminate the call, even if the LAN connection comes

back up. When the LAN connection is active again, the proxy software resets the port state

so that new calls can be handled properly.

R2.0: Returning TTS resource state to INSERV

If connectivity with RealSpeak, Speechify, or SAPI-compliant Text-to-Speech (TTS) servers

has been interrupted, you may need to set the resource state to INSERV to resume TTS

services.

To set the resource state to INSERV:

1. At the IR system command prompt, enter sproxyadm -r TTSx -d to show the

resource state.

For more information about the sproxyadm command, see sproxyadm command.

2. If the resource state is FOOS, BROKEN, or INSERV, enter sproxyadm -r TTSx -f

INSERV to change the resource state to INSERV.

3. Repeat Step 1 to check the resource state.

4. If the resource state does not change to INSERV, you must restart the TTS service on the

Windows NT server and repeat Steps 1 through 3 above.

5. For a Speechify or RealSpeak engine, if the resource state does not change to INSERV,

follow instructions in the Speechify or RealSpeak documentation to restart the TTS

service, then repeat Steps 1 through 3 above.

6. For a SAPI TTS engine, if the resource state does not change to INSERV, use the

following steps to restart the Windows NT TTS service, then repeat Steps 1 through 3

above.

a) On the Windows NT server, open the Control Panel window (Start > Settings > Control

Panel).

b) Select Administrative Tools.

c) Select Component Services.

Contents

Main Issue 1.0 April 2006 2 Troubleshooting overview Issue 1.0 April 2006 3 Page Page Troubleshooting Troubleshooting overview Requirements for successful operations The public switched telephone network (PSTN) Switches Voice response applications Connections and communications System and LAN capacity Possible malfunctions and errors Hardware malfunctions and failures Incorrect system administration Application errors Connection and communication problems Overloading Speech Identifying possible causes of problems Page Troubleshooting procedure Using IR system events Gathering information on a problem Reviewing the Display Equipment screen Monitoring live operations Checking system history Using Sun diagnostic tests Using commands Troubleshooting based on observations Investigating operations problems Call-handling problems Voice system not answering Calls dropped Calls not transferred properly No DTMF tones (WINK protocol) Poor audio quality on VoIP calls Touchtone not interpreted correctly Fax problems Typical fax problems Locating fax errors Interpreting negative fax values Reviewing fax repair procedures Fax text or file not found Host interaction problems Host sessions recover repeatedly No response for application with host interface Calls to host dropped Speech and TTS problems Speech delayed or cut off Speech recognition not available as resource Cannot configure speech recognition All ports BROKEN on speech server Speech resource bad or non-configured Speech server not running Speech response delayed Speech recognition rejecting many responses Speech recognition not working Speech not playing MRCP problems Page Page Page Page Page Text-to-Speech problems System process problems Unix commands failing or disk errors Execute Unix command failed vi editor causes core dump Database problems Checking JDBC operations Checking Oracle object size limits A word about the Tomcat server log Checking communications Checking LAN communications Typical causes of LAN problems Resources for LAN troubleshooting Troubleshooting speech server disconnections Troubleshooting database server disconnections Troubleshooting intermittent LAN problems Troubleshooting persistent server problems Pinging server connections Monitoring Ethernet packets Tracing LAN activities Detecting incorrect IP addresses (arp) Displaying network statistics (netstat) Displaying packet route (traceroute) Checking hardware Resolving a problem when the monitor does not display Checking cable connections Page Testing platform hardware Checking NMS card configuration Checking card and channel states Performing root cause failure analysis Restoring cards and channels Restoring MANOOS cards and channels Restoring NETOOS cards and channels Restoring FOOS cards and channels Restoring BROKEN NMS and VoIP cards Page Page Gathering data on card operations Performing root cause failure analysis Replacing a failed hard disk drive Checking for hard disk drive failures Running the metastat command Removing a failed hard disk drive Activating disk mirroring for a new hard disk drive Restoring the system if both hard disk drives fail Disabling disk mirroring Page Page Issue 1.0 April 2006 61 Index A C D E S T U V