| Knowledgebase Home | Contact |
 Search the Knowledgebase |
 Jump to ID |
 Browse by Category |
| How to debug VoiceXML errors | ||||||||||||
| Categories: Step-by-step debugging tips | ||||||||||||
SUMMARY This article explains how to debug VoiceXML errors events thrown by your voice browser. SYMPTOMS A voice application fails and an error message is played back to the caller. Activity and error logs have a VoiceXML error event listed as the cause of the failure. RESOLUTION The most important thing to remember is that VoiceXML error events are thrown by your voice browser. Call Services simply receives these error messages and logs them to the activity and error logs. Note that while Call Services developer can add custom VoiceXML handling in Call Services, it is always recommended to address the source of those errors. The most common events thrown by voice browsers:
The first one means that a particular resource, such as an audio file or an external grammar, cannot be found. A common cause is that the URL is not accessible by the voice browser. The following article explains the most common issues casuing error.badfetch to be thrown: The remaining two errors point to problems with either an ASR or TTS engine. It might mean that those engines are not accessible by the voice browser or that there are not enough licenses installed for those engines. Note that some VoiceXML errors may not indicate a problem and may occur as a result of high call volume. An example is error.badfetch being thrown by the voice browser when an external server cannot handle requests (e.g. for audio files) fast enough. Another example is when the ASR engine does not have enough licenses to process all the simultaneous callers and will refuse connections throwing an error. Note that VoiceXML errors are thrown by the voice browser and the voice browser will have more detailed information about the source of the error. Call Services logs can be used as a reference to match timestamps of the error occurrence. Note that the timestamps might be off with the voice browser logs. This is caused by the fact that the error is first thrown on the voice browser side and then propagated to Call Services. Please refer to your voice browser logs and vendor for help with debugging VoiceXML errors. Additionally, the following two articles describe how to enable VoiceXML debug logging in Call Services, which will log each request that a particular voice application receives (including HTTP request parameters) and the full VoiceXML response: |
Print this page
Post a comment
| Visitor Comments |
| No visitor comments posted. Post a comment |
| Related Questions |
| No related questions were found. |
| Attachments |
| No attachments were found. |