Karl,

The functionality of "overwriting" or disabling global hotlinks is available currently in the software.

Hotlinks, as defined in the VoiceXML 2.0 specification, will always have global scope. However developer can define local grammars that will take precedence over the global ones. hence, as a result, you can disable global Hotlinks in the particular element.

Please refer to the following KB article for more details:

Hotlink grammar scoping

Regards,
Michael

Karl,

There is no need to disable hotlinks in this scenario, both inputs will be accepted as valid inputs. Note that the actual input processing does not happen on the Call Services side but on the voice browser.

In the scenario you described you will have both the Hotlink (0) and the local date grammar, accepting inputs such as 08031980. When caller starts entering DTMF keys, voice browser will wait for the whole input. The wait time between each inputs is controlled by the [b:66d0a446f8] interdigittimeout [/b:66d0a446f8] VoiceXML property. It defines the time voice browser has to wait for another DTMF entry. Once this times elapses, or caller presses DTMF termchar, browser stops listening for input and sends the results back to Call Services.

Please refer to the VoiceXML 2.0 Specification, Section 6.3.3 and Appendix D for more details.

To sum up, in the scenario you described, both inputs, 0 and 08031980, should work without any problems and disabling hotlinks.

Hope it explains everything,
Michael