Filter
Top Products
Contents
Issue 1.0 April 2006 23
No response for application with host interface
A voice response application that relies on a host system for data might receive no answer
intermittently or consistently.
To resolve the problem:
1. Go to the Message Log Report screen (Reports > Message Log Report) and check for
events related to the trouble.
The event HOST001 (HOST_NORESP) should appear in the log.
2. Follow the repair procedure for the event.
Calls to host dropped
When all calls to the host are dropped, take these steps:
• Type hstatus all and press Enter to check the status of the host.
If all sessions are recovering or logging in, this could cause the trouble.
• If the problem occurs frequently, consider speeding up connections between the IR
system and the host.
Speech and TTS problems
This section describes how to find and resolve problems related to speech recognition and
Text-to-Speech (TTS) features.
Speech delayed or cut off
Delayed or cut off speech can cause callers to disconnect.
When messages are cut off, make the following changes in the voice response application to
correct the problem:
• Add a few seconds of initial silence (0.2 to 0.5 seconds) to the beginning of the message
to be played.
• Construct a phrase consisting of a few seconds of silence and play that phrase first.
• Ensure that the prompt does not allow voice barge-in. If it does, any background noise or
talk by the caller will interrupt the prompt.
Speech recognition not available as resource
To resolve the problem: