Janine,

I tested it with being part of the VXML Gateway CLI only. I'm not sure if there is another way for this to work properly.
It seems this command Overrides the VXML 2.0 command, default behavior, as far as I know as it is a gateway command its all or nothing.
As far as i know the only element that this really affected was the Digits element, If that helps.
We could not get the builtin:dtmf/digits?minlength=4;maxlength=7) Length checking working at all.
Luckily the built-in min / max checks are working properly in the Digits element.

Regards,
Corey Junge

I will be travelling October 5th though October 19th. If you require immediate assistance, please call the DDV Hotline at 651.686.4300.

Sorry – forgot to add that I catch it with a local hotlink

<local_hotlinks>
<local_hotlink>
<name>Star</name>
<dtmf_grammar_type>Inline</dtmf_grammar_type>
<dtmf_grammar_value>\*</dtmf_grammar_value>
<speech_grammar_type>-</speech_grammar_type>
<speech_grammar_value/>
<throws_event>false</throws_event>
<event_name/>
</local_hotlink>
</local_hotlinks>

Regards,
Geoff

I have figured how to do what I wanted to do, sort of

I am using the form element, and using the wildcards. I figured out that putting spaced in between the keypress string is no different than creating a new keypress row.
So “.. .? .?” is the same as three entries “..” “.?” “.?”
The document that Janine linked to says that if the pattern ends in a repetition operator (?, +, or *), additional digits after the patter will be matched. So, .? is the same as .*

Also, I remembered that the matching stops looking as soon as it finds a match. I was remembering incorrectly when I wrote the last post; the string I was using, “.. .? .?” matched 1 or 2 digits, and that’s it. That’s because as soon as I entered two digits, the “..” pattern was matched, and the program stopped looking.
So, to match 1-4 digits, the pattern would be: “.... .?”, or “.... .*”

I found no easy way to match 2-4 digits though. If you did the patter “.... .. .?”, as soon as you entered 2 digits the pattern would be matched.

However, the reason I needed to match 2-4 digits is to collect a year that is greater than today. So, I can assume that all 4 digit dates are going to start with 2, and I can do the following pattern:
“2... 1. 3. 4. 5. 6. .8 .9. 0. .?”
The only special case here would be trying to enter a 2-digit year that starts with 2. To handle that, I’ll just set the interdigittimeout to something like 1500ms. I’ll still have to check if the year is valid, because a user could enter 237, and that would be valid, but at least this way for most cases the input will be valid and immediately accepted without the user having to wait for the interdigittimeout to kick in.

 
Hi Asher,



I've found that with DTMF-Only gateway, you have to specify this in the
gateway CLI, otherwise it won't accept * and digits.

'vxml allow-star-digit'



If you do 'vxml allow-star-digit' in the gateway and then use a Digits
element, with MinDigits:2 and MaxDigits:4 and set the Local Hotlink to \*,

then it exits immediately down the hotlinks path if the caller presses
*. And otherwise allows 2-4 digits.



Note that with DTMF-only, you ONLY need to use \* in the Form element
and the HotLinks (both global and local), But in the Menu elements, use
just * (no backslash).



I've also found this week, much to my surprise, that the DTMF-only
doesn't behave exactly as expected when I use a Form element with the
following:

+DTMF Grammar: builtin:dtmf/digits?length=5

+DTMF Grammar: builtin:dtmf/digits?length=9



In this case, it accepts 5 or more digits, not just 5 or 9 as I'd expected.



Live and learn.