Gateway Troubleshooting: Pressing Digit 9 Causes No-Match
(New page: == Pressing Digit 9 Causes No-Match == <table border="1"><tr><td> '''Problem Summary''' </td><td>In DTMF-only adapter, pressing digit 9 while using options causes no-match after 10 second...)
m (1 revision)
Revision as of 18:12, 18 September 2009
Pressing Digit 9 Causes No-Match
|Problem Summary||In DTMF-only adapter, pressing digit 9 while using options causes no-match after 10 seconds.|
|Possible Cause||This delay is caused by the following link grammar in the root document for the DTMF-only adapter.
<link event="nomatch"> <grammar mode="dtmf"
Since the options are created with modal=false, the link grammar remains active in the Gateway DTMF-browser. On pressing 9, the Gateway starts to match this grammar and waits for the next input instead of returning a 'no-match' immediately.
|Recommended Action||When writing a VXML Server script for a DTMF-only adapter that uses the Get Digits, Forms, or n_Option_Menu elements, follow this procedure to avoid delay in processing the digit 9 when the script is executed.
If the VXML Server script uses 3_Option_Menu, where 1, 2, and 9 are valid options, then the inline grammar can have the value 8, but cannot have the value 1, 2, or 9.
Similarly, if the VXML Server script uses 9_Option_Menu, where digits 1 through 9 inclusive are valid options, then the inline grammar can have the value 99, and the interdigittimeout must be set to 5s.
If you are using a GetDigits element and have set the follow range: min=2, max=4, then the link grammar can be 99999, and you must set the interdigittimeout to 5 seconds.
If the script contains an Option Menu as well as GetDigits elements, you only need to set the link grammar once.
|Associated CDETS #||None.|