| How do Hotlinks work? |
| Categories: Audium Call Services 3.4.x and 3.5, Audium Studio (3.4.x) |
| Article ID: | 56 |
| Last updated: | January 18, 2011 |
| User Opinions |
100%
0%
(1 vote)
|
|
Thank you for rating this answer.
|
SUMMARY
This article describes how to use Hotlinks in your applications, and how they work.
SYMPTOMS
Developer would like to include a Hotlink in an application's callflow, but is not sure how it works.
RESOLUTION
Many voice applications require an utterance or key press that can be produced by the caller at any time during the call, and result in the application performing a specific action. One common example is the utterance "operator" (and/or pressing "0") transferring callers to a live representative. In Audium, these actions are referred to as hotlinks.
Hotlinks are not elements in that they do not generate VoiceXML or execute any custom code. Instead, a hotlink acts as a pointer (or link) to direct the call somewhere or throw a VoiceXML event when the right word or key press is detected. An application can utilize any number of hotlinks.
In-line grammars can be specified for the Hotlink in the Hotlink's configuration. When one of these grammars is recognized, the Hotlink will be visited, and then the Hotlink will exit with the "goto" exit state, or throw a developer-designated event. Most developers use the exit state to send the caller to a new part of the application, rather than throwing an event.
Note that if any voice element has bargein disabled, the Hotlink cannot be triggered during the prompt of that voice element. Additionally, if a voice element accepts caller input, then the Hotlink grammar will not be recognized. One final note is that Hotlink grammars will not be matched while the user is recording audio for a Record element.
|
| Visitor Comments |
|
No visitor comments posted. Post a comment
|
| Attachments |
|
No attachments were found.
|
Search the Knowledgebase
Jump to ID
Browse by Category
Print this page
Post a comment