| Hotlink grammar scoping |
| Categories: Audium Call Services 3.4.x and 3.5, Audium Studio (3.4.x) |
| Article ID: | 134 |
| Last updated: | January 12, 2007 |
| User Opinions |
|
No users have voted.
|
|
Thank you for rating this answer.
|
SUMMARY
This article explores the consequences of using a grammar in an element that is already defined in a Hotlink.
SYMPTOMS
An application has a Hotlink, and the developer would like to capture input that is already caught by the Hotlink in another element.
RESOLUTION
Per the VoiceXML 2.0 specification, local grammars take precendence over global grammars.
For example, imagine that a Hotlink's grammar listens for the utterance "home", and a Form element also listens for "home". If this utterance is said by a caller during the Form element, then the Form element will handle it and the Hotlink will not be activated. However, if "home" is said outside of the Form element, then the Hotlink element will handle the input.
Although this is part of the VoiceXML 2.0 specification, It is recommended that you confirm that your voice browser conforms to this behavior; please refer to your voice browser's documentation for details.
|
| 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