Author Message
KumudTripathi
Joined: Jan 5, 2012
Messages: 17
Offline
Good case where valid input entered by caller:
Storing :pc_dmenu_DynMenuOpt___confidence to complex: pc_dmenu_DynMenuOpt:confidence as [1]
Storing :pc_dmenu_DynMenuOpt___inputmode to complex: pc_dmenu_DynMenuOpt:inputmode as [dtmf]
Storing :pc_dmenu_DynMenuOpt___interpretation to complex: pc_dmenu_DynMenuOpt:interpretation as [1]
Storing :pc_dmenu_DynMenuOpt___noinputcount to complex: pc_dmenu_DynMenuOpt:noinputcount as [0]
Storing :pc_dmenu_DynMenuOpt___nomatchcount to complex: pc_dmenu_DynMenuOpt:nomatchcount as [0]
no variable for complex: pc_dmenu_DynMenuOpt:rule1299792
Storing :pc_dmenu_DynMenuOpt___utterance to complex: pc_dmenu_DynMenuOpt:utterance as [1]
Storing :pc_dmenu_DynMenuOpt___value to complex: pc_dmenu_DynMenuOpt:value as [1]

Bad case where invalid input entered by caller:
Storing :pc_dmenu_DynMenuOpt___nomatchcount to complex: pc_dmenu_DynMenuOpt:nomatchcount as [1]
Storing :pc_dmenu_DynMenuOpt___noinputcount to complex: pc_dmenu_DynMenuOpt:noinputcount as [0]


massimo__croci
Joined: Jan 31, 2020
Messages: 518
Offline
Did you try to use a DTMF grammar containing all tones with two TAGS
(valid/invalid) ? Additionally, take a look at


https://www.devconnectprogram.com/forums/posts/list/384.page#p2593

and

https://www.devconnectprogram.com/forums/posts/list/24796.page?nonMobile=false
KumudTripathi
Joined: Jan 5, 2012
Messages: 17
Offline
yes I did and it works.. That is the only solution I think to do this..
massimo__croci
Joined: Jan 31, 2020
Messages: 518
Offline
That is the only workaround I found. I'm not aware of anything else. If someone has any suggestion, please post here.
Go to:   
Mobile view