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 07-09-2007 07:09:04 PM Every time I use a record element I am getting the error:
SERVER ERROR: A VoiceXML exception occurred: error.badfetchs
Is there a way I can find out what the record element is trying to access?
Subject: RE: BadFetch with Record Element Replied by: Vance Vagell on 07-09-2007 07:38:42 PM Hi Greg,
That error means that your voice browser tried to fetch something (VoiceXML, audio, etc.) but it either failed completely or timed out. Your voice browser log should have more information; however, you may need to increase your voice browser's logging level to get enough detail.
You might also want to take a look at this KB article, which talks about this issue in more detail.
Regards, Vance
Subject: RE: BadFetch with Record Element Replied by: null on 11-09-2007 02:32:07 PM Vance,
I have been looking through all of my logs and I find no reference to the bad fetch error except for in the application log. Could you please point me in the right direction to help me solve this problem?
I am using CVP 3.1.
Subject: RE: BadFetch with Record Element Replied by: Vance Vagell on 11-09-2007 02:38:48 PM Hi Greg,
I recommend you place a test call in isolation, so that you can be sure all the logs you're looking at only apply to that one call. The test flow would be something like this:
1) Delete (or temporarily move) all Call Services logs in AUDIUM_HOME/logs and AUDIUM_HOME/applications/YOUR_APP_NAME/logs.
2) Clear the voice browser logs. On the CVP voice browser, you can do this with the "clear log" CLI command.
3) Enable more extensive voice browser logging, to ensure that the badfetch error will be logged. For very extensive logging, you could enable "debug voip application vxml all" on the CVP browser. Note that you'd never want to do this in production; it will produce a lot of data.
4) Run a single test call, to reproduce the error.
5) Review the Call Services and browser logs, and coordinate the timestamp in the Call Services logs to see when the badfetch error occurs in the matching voice browser logs (you can see the voice browser logs with "show log").
The voice browser log should have a lot of information about what's leading up to and ultimately causing the badfetch. Once you're done testing like this, please revert your voice browser's logging level to whatever you normally have it set to.
Regards, Vance
Subject: RE: BadFetch with Record Element Replied by: null on 11-09-2007 07:20:41 PM I don't seem to be able to clear the Voice Browser logs. How do I start the voice browser? Once it is started how do I clear the log. These my seem like very basic question but I am very new to CVP.
Subject: RE: BadFetch with Record Element Replied by: null on 11-09-2007 07:41:33 PM This is what I get when I run the getVersions script.
----- Cisco CVP VoiceXML Server v3.1: Unable to obtain version because the manifest of the JAR file "C:\Cisco\CVP\Tomcat 4.1\webapps\CVP.war" does not properly contai n a version number. CVP API: Unable to obtain version because the manifest of the JAR file "C:\Cisco \CVP\Server\lib\framework.jar" does not properly contain a version number. CVP Administration: 3000 CVP SNMP: 3000
CVP Elements / Say It Smart Plugins
----- Core CVP Elements: 3000 CVP Say It Smart Plugins: 3000
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: