I personally dislike the mixing of data entry and menu control. This is a carry-over from the older IVRs where each key was being passed up and there was no buffering, so you could get this sort of control. I think it’s very old school, although I have made your proposed system work – precisely with the STAR key. I don’t know why it does not work for you.

I would prefer to separate menu selection and number entry:


1. If you know your account number, please press 1.

2. If not, press 2 to return to the previous menu.

Then if they press 1 –“please enter your 3 – 10 digit account number followed by pound”

Regards,
Geoff

Patrick,

>>> Your condescending tone and answer "Mine works, I don't know why it does not work for you." is not at all helpful.

Sorry, I did not intend to be condescending in any way. Merely providing my view – you are crochety today.

>>>Are you running 7.0(2)?

No, CVP 8.0.

>>>is the call in fact going down the hotlink path?

Of course it does. Jeez!

>>>are you deploying onto a vxmlserver where you actually are dialing a phone to check the call flow?

It’s in production and has been so for over a year. So yes.

>>>Old school? I will take old school. Heck, I think I mentioned we have a DTMF only application that should have made it clear where I'm coming from. I am also over 50 so I am allowed to wear black socks with sandals and drive down the freeway with my blinker on.

Old school – yes, I’m over 60. DTMF only – yes, what is your point?

I’ll dig out the application and see if I can provide some hints. I can’t post a picture, but the XML file says:

<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>

Are you using a Form? You need to use a Form

<settings>
<setting name="inputmode">dtmf</setting>
<setting name="noinput_timeout">5s</setting>
<setting name="form_max_noinput_count">3</setting>
<setting name="form_max_nomatch_count">3</setting>
<setting name="confirm_max_noinput_count">3</setting>
<setting name="confirm_max_nomatch_count">3</setting>
<setting name="max_disconfirmed_count">3</setting>
<setting name="dtmf_grammar">builtin:dtmf/digits?maxlength=11</setting>
<setting name="dtmf_keypress"></setting>
<setting name="help_dtmf_keypress"></setting>
<setting name="modal">false</setting>
<setting name="field_name">foundation_fld</setting>
<setting name="slot_name"></setting>
<setting name="slot_element_data"></setting>
<setting name="secure_logging">false</setting>
</settings>

Regards,
Geoff

Hi Patrick,
When you are using DTMF-Only, the default is that if you are using a Digits element, or (equivalently) using a Form element with DTMF-Grammar setting 'builtin:dtmf/digits' then a * key from the caller causes a NoMatch event - EVEN if you set \* as a HotLink (local hotlink or global hotlink).
 
If you want to be able to accept * as a HotLink while collecting digits, then you have to add 'vxml allow star-digit' to the vxml gateway CLI. And now if you set the Hotlink to listen for \* (as you already are doing) then it'll be recognized and exit down your Local-Hotlink exit state (or jump to your global HotLink, if that's where you have it configured).
 
 

>>>> I am just imagining me giving my co-workers high-fives when we get this to work while someone is wondering why the star key is misbehaving when accessing their voice mail.

Yeah, that would be a bummer. But this is just a command for VXML, so it “should” not affect others (but you know how that goes). Do you have a lab system you can try it on?


Regards,
Geoff