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: null on 27-02-2006 03:36:15 PM Once in a while(abouve 1% od the the time), we are getting the above error when the following java code is executed from a audio element (Welcome_init2). Below is also the log trace indicating the error. We are using Audium 3.3 version. Could you give any hints as to why this could be happening ?
Subject: RE: A VoiceXML exception occurred Replied by: Vance Vagell on 28-02-2006 03:50:48 PM Hi Deepak,
When your Audium error logs indicate a VoiceXML error, we recommend that you examine your voice browser's log for details. Most voice browser logs include detailed information regarding VoiceXML processing errors, such as the problematic line and column number. Please refer to your voice browser's documentation for information about debugging options which may need to be enabled.
Regards, Vance
Subject: RE: A VoiceXML exception occurred Replied by: null on 01-03-2006 07:00:02 PM Below is the trace I see in the tellme platform. It says that the repeat event is not caught. Can you shed some light on what this means ? And how we can disable the repeat event from getting generated ?
Subject: RE: A VoiceXML exception occurred Replied by: Vance Vagell on 01-03-2006 07:30:45 PM Hi Deepak,
Based on your TellMe log, it looks as though the caller provided the speech input "repeat". Since the log also complains about an event called "repeat" not being caught, it seems as though you may have a HotLink element in your callflow which listens for the "repeat" keyword and then throws a "repeat" event. Is this the case?
Regards, Vance
Subject: RE: A VoiceXML exception occurred Replied by: null on 03-03-2006 03:36:56 PM We are using the pre defined Audio element from the Audium Builder to play a wav file when this error occurs. I don't understand how a repeat event got generated when the Audio element doesn't provide any means of speech input.
I noticed that the bargein mode is set to both. Could this cause generation of VXML allowing voice input but no handling of the repeat event. This could be a Audium bug. Can we set the bargein mode to dtmf to circumvent this problem ?
Deepak
Subject: RE: A VoiceXML exception occurred Replied by: Vance Vagell on 03-03-2006 04:00:43 PM Hi Deepak,
Please note that although your Audio element does not itself accept input, there may be active link grammars that do. For example, you may have a HotLink elsewhere in your application that is triggered by the keyword "repeat". This HotLink element may be configured to throw a repeat event when it is triggered.
You mentioned that the bargein VoiceXML property is set to "both". This is not a valid value for this property, per section 6.3.4 of the VoiceXML 2.0 specification. You may have meant inputmode, which does accept this value. In that case, changing the inputmode VoiceXML property to dtmf would force voice input to be ignored.
However, the best solution would be to determine what grammar in your application is listening for the keyword "repeat", and address the problem at that level.
Another possible culprit is your voice browser, which may include one or more proprietary universals (global keywords, such as "cancel", "help", or "exit"). Your voice browser may provide a "repeat" keyword, and throw a repeat event when it is matched. If you are not using these universals, you can disable them by setting the "universals" VoiceXML property to "none". You can set this VoiceXML property in your application's root document, by defining it in the application's properties dialog in Audium Studio:
1) Right-click on your Audium application in the Navigator pane of Audium Studio 2) Choose "Properties" 3) Select "Audium - Root Doc Settings" 4) Enter the property and value in the table on the left 5) Click OK 6) Redeploy your Audium application
Hope this helps, Vance
Subject: RE: A VoiceXML exception occurred Replied by: null on 03-03-2006 04:36:23 PM We are using Audium 3.3 where we have the settings page and there I found the VXML property table. I added an entry universals with a value of none.
Please verify if what I did was right ?
Thanks
Deepak
Subject: RE: A VoiceXML exception occurred Replied by: Vance Vagell on 06-03-2006 07:37:38 PM Hi Deepak,
Yes, setting the VoiceXML property in that location is equivalent to the instructions we gave for how to do it in Audium Studio.
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: