This is an old revision of the document!
The <error> element is short for <catch event=“error”> and catches all events of type error. Some common error are error.badfetch (failure to fetch remote script) and error.disconnect.hangup (when the user hangs up the phone).
|count||(defaults to 1) The occurrence of the event. The count allows you to handle different occurrences of the same event differently. Each <form>, <menu>, and form item maintains a counter for each event that occurs while it is being visited; these counters are reset each time the <menu> or form item's <form> is re-entered. The form-level counters are used in the selection of an event handler for events thrown in a form-level <filled>. Counters are incremented against the full event name and every prefix matching event name; for example, occurrence of the event “event.foo.1” increments the counters associated with handlers for “event.foo.1” plus “event.foo” and “event”.|
|cond||(defaults to true) An expression that must evaluate to true after conversion to Boolean in order for the event to be caught.|
<?xml version="1.0"?> <vxml version="2.0"> <form> <block> <prompt> Hello. Let's move to another script. </prompt> <goto next="nonexistant_file.php"/> </block> <error> <prompt> A serious error of type error.badfetch has occurred. Exiting. </prompt> <exit/> </error> </form> </vxml>
This script mimics the default functionality for when the IVR fails to fetch a remote file.
The output of the above script would be:
Computer: Hello. Let's move to another script.
Computer: A serious error of type error.badfetch has occurred. Exiting.