« Back to CVP - All Versions

Form element # [value] doesn't work with dtmf only...

Combination View Flat View Tree View
Threads [ Previous | Next ]
As I am sure most of you know, using the format # in the form element can be used to change what is saved in the value variable for the form element. Unless you are using DTMF only, and then it doesn't work. However, you can still specifiy a value in brackets, it will jsut be ignored. 
I wsa trying to do this in a script I am creating, to use it as a sort of comment field so you cna easily see what each menu option represents. Then, when evaluating the value, I use the number, not the value. 
This works fine when deployed. However, when trying to debug in Call Studio, the debugger uses the value instead of the number, and this causes the script which works when deployed, to not function properly.
 
Does anyone know how I mgith make the Call Studio debugger behave the same as the production CVP server?
 
Also, does anyone know what Cisco has said about this functionality? Is the limitation on using the feature when you are only using dtmf a bug, or is it a limitation of VXML?

It looks like it's probably a limitation of the regex dtmf grammar language on the gateway. A Studio Form element creates something like this: <grammar mode="dtmf" type="application/grammar+regex">1 2</grammar> However, the N_Option_Menu elements, create something like this, allowing you to assign a value other than the DTMF entered: <option value="sales" dtmf="1">1</option> <option value="marketing" dtmf="2">2</option> So, if Cisco had the resources to, they could modify the gateway adapter for DTMF-Only to allow assigning a different interpretation than what the caller is entering. Janine