Shorthand Exceptions

The VoiceXML spec has dictated that a number of the more common exceptions are worthy of their own shorthand tags, which saves us a bit of milage when writing the application. These particular exceptions which are accessible by both the <catch> element and their own specific elements are:

<help>
<error>
<nomatch>
<noinput>

To clarify, what we can assume from the above is that both of the below code snippets are exact, identical statements:



            <catch event="help">

              <!-- do something here -->

            </catch>



            <help>

              <!-- do something here -->

            </help>

The breakdown on each of the 'shorthand' exceptions is as follows:

Help

Links to the Universal Grammar, and can be enabled by utilizing the 'universals' property within the VoiceXML code. If not specified at all, then the 'help' utterance will not be available at all, as this is not enabled by default. If an action is not explicitly defined, it will play the default platform error wav file, and continue document execution, usually resulting in a <reprompt> event.

Error

As previously stated, the 'error' event is a 'blanket' error handler, and will get triggered by any error in the application, which is sometimes useful for creating a permanent VoiceXML error log on your server for troubleshooting purposes.

Nomatch

The 'nomatch' exception will get thrown when the caller says something or presses a DTMF key for which the application cannot match to a grammar utterance in the application. Unless specifically handled, it will play the default error wave file, and reprompt the user.

Noinput

The 'noinput' event will get thrown when the user has not given the application expected input within the default time frame of 5 seconds. If an action is not explicitly defined, it will simply reprompt the user.

ANNOTATIONS: EXISTING POSTS

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

w3c Standard Error Types

| TOC

| Disconnect Events