Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Created by: Brien Williams on 26-10-2005 04:11:47 PM Using CVP 3.0 in a very limited environment (no Voice Borwser) to test very simple callflow and following the directions to navigate in a Web browser from the auidum knowledge base (I've used this successfully in the past.) At this point, no matter what I use for an inline grammar, I can't force a nomatch on a Form element. For example, if I have a Voice keyword of "grape" the following URL still takes me to the done exit state:
Activity log provides no insight on this - shows the form field data value and exit state with no comploaints.
Subject: RE: Testing with Web Browser, problem with forcing a nomatch Replied by: Vance Vagell on 26-10-2005 04:48:54 PM Hi Brien,
Using a web browser you can simulate max nomatch (as configured in Audium Studio) by passing the "maxNoMatch" parameter in the URL, with a value of "yes". An example of a URL with this parameter is:
(Note that foundation_fld will have a value that is specified in the element's grammars, since the ASR engine [i:237560da18]only[/i:237560da18] recognizes words from active grammars. Your example of "apple" would never occur, unless "apple" is in the grammars.)
However, you cannot simulate each individual nomatch event, since these would normally be handled by the voice browser, without relying on Audium Call Services. After the final nomatch event or after a successful input, log entries are sent back to Audium Call Services to log any previous nomatch events.
For future support requests, please contact Cisco TAC.
Regards, Vance
Subject: RE: Testing with Web Browser, problem with forcing a nomatch Replied by: Brien Williams on 26-10-2005 05:45:06 PM THanks Vance,
My customer's lab is about to come on line, so mostly I'm just trying to get the Audium part of my brain restarted - and that you did. And, the Web browser navigation is really useful in it's own right - for seeing the VXML the VB has to work with, not for running a complete callflow like I was trying to do.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: