Appendix C: VoiceXML Errors & Exceptions Explained

Knowing that you have an error is the first step to a solution. But, in order to get closure on our error issues, we also need to know exactly what errors can get thrown in the VoiceXML environment, exactly what they mean, and how to fixt them as they happen. In this appendix, you will find a bevy of useful knowledge pertaining to what errors and exceptions can happen in particular coding circumstances. We will also go over techniques for trapping and handling the exceptions that are bound to crop up during the average development cycle of a VoiceXML application.

Overview

General Exceptions and Error types: This short section briefly describes the common error types that can crop up in all VoiceXML applications, as well as the basic error trapping techniques that a developer will commonly use.

w3c Standard Error Types: This second section on the standard w3c errors describes each of the exceptions in greater detail, and gives you the background on why each error can, (and usually does), show up in the Debugger.

Shorthand Exceptions: Covering the fine art of utilizing VoiceXML's ingrained error types, this section instructs you on the <help>, <nomatch>, <noinput>, and <error> event handlers.

Disconnect Events: This section describes, in detail, how to programmatically recognize and handle the event(s) signalling that a caller has disconnected from the application.

Transfer Exceptions: When placing an outbound call via the <transfer> element, there are several events and exceptions that can be thrown depending on the caller/callee actions. Read this section to learn the skinny on how to gracefully handle these events, adding polish to your finished application.

ANNOTATIONS: EXISTING POSTS

0 posts - click the button below to add a note to this page

Getting Support Help

| TOC

| General Exceptions and Error Types