| Hotevents |
| Categories: User Guide Ch1: Introduction |
| Article ID: | 155 |
| Last updated: | January 12, 2007 |
| User Opinions |
|
No users have voted.
|
|
Thank you for rating this answer.
|
SUMMARY
This article describes Hotevents from a high-level perspective.
SYMPTOMS
N/A
RESOLUTION
While hotlinks are caller utterances that trigger an action, there are times when the occurrence of a VoiceXML event is expected to trigger an action. The event can be user-triggered (such as a noinput event), asynchronous (which would be thrown by the voice browser), or developer-defined (such as a hotlink that throws an event). In each case, the developer may wish to play audio, store data, or move to another part of the call flow when the event is triggered. In Audium, these are referred to as hotevents.
|
Hotevent |
A global event that when caught, executes developer-specified actions. |
Like hotlinks, hotevents can act as pointers to direct the call somewhere. They may also specify VoiceXML to execute when the event is triggered. An application can utilize any number of hotevents, each activated by a different event.
Note that a hotevent is triggered by a VoiceXML event, not a server-side event such as a Java exception or an error such as a database being down.
|
| Visitor Comments |
|
No visitor comments posted. Post a comment
|
| Related Questions |
|
No related questions were found.
|
| Attachments |
|
No attachments were found.
|
Search the Knowledgebase
Jump to ID
Browse by Category
Print this page
Post a comment