Error.badfetch
Portal > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 1 2 Previous Next 17 Replies Latest reply: Apr 5, 2016 5:32 PM by janinegraves CVP error.badfetch handling rosaxena Aug 18, 2014 4:20 AM Tweet Hello Experts,This is regarding CVP 9.0, here Media server is a dedicated separate server(not co-resident).If any prompt gets missed out in Media server by user mistake, then VXML gateway(iOS browser) returns an error badfetch and caller is getting dropped abruptly after survivability.Is there any option where this situation can be handled more gracefully through 'CVP studio' and 'VXML code', like caller moves to the next option bypassing that audio prompt and such event is logged so that necessary action can be taken timely?Regards,Rohit 2774Views Tags: none (add) cvpContent tagged with cvp, cvp_troubleshootingContent tagged with cvp_troubleshooting, cvp_studioContent tagged with cvp_studio, ucm/ucce/cvpContent tagged with ucm/ucce/cvp Reply (Login Required) 1. Re: CVP error.badfetch handling chintan2@hp.com Aug 18, 2014 3:31 PM (in response to rosaxena) You can handle this event in Your Call studio with the help of hot events.in the hot events node you can catch error.badfetch and transfer the path accordingly. Like Show 1 Like (1) Reply (Login Required) 2. Re: CVP error.badfetch handling rosaxena Aug 19, 2014 2:34 AM (in response to chintan2@hp.com) Thank you Chintan!! Like Show 1 Like (1) Reply (Login Required) 3. Re: CVP error.badfetch handling rosaxena Aug 19, 2014 6:09 AM (in response to rosaxena) Hello Chintan/Experts,I have received one problem regarding to the approach suggested by Chintan as below, your views ??"We used Hot events in case of bad fetch due to communication problem between the components and bad fetch due to unavailability of resource.But currently for any CVP application it is not recommended to handle bad fetch from application and same is not followed for any of the projects,It is recommended to handle any bad fetch issues from ICM and the same is followed in current TTSL production system.Cause : We found multiple call issue due to handling of bad fetch in the application which effected the reporting." Like Show 1 Like (1) Reply (Login Required) 4. Re: CVP error.badfetch handling tarunjain19 Aug 26, 2014 5:40 AM (in response to chintan2@hp.com) Hi All,we are also using Hot event in CVP application to capture the error and will take appropriate action according to call flow.But my CVP application quite complex a
Portal > Documents Currently Being Moderated Bad Fetch error Details in VXML Server Request Responce created by cdnadmin on Jan 24, 2014 5:29 PM, last modified by cdnadmin on Jan 24, 2014 5:29 PM Version 1 Tweet This document was generated from CDN thread Created by: Malik Ehtasham on 26-08-2013 07:36:00 AM Hello Everyone,When an IVR Application is trying to access a audio https://communities.cisco.com/thread/46162?tstart=0 file which is not available on the desire media server, then VXML server throws bad fetch error but it does not tell about exactly which file is missing. I want to know exaclty the name of the audio file which is missing. I have https://communities.cisco.com/docs/DOC-48530 printed VXML Request Responce cycle by adding this command
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click http://community.inin.com/forums/showthread.php?6648-VXML-error-badfetch the register link above to proceed. To start viewing messages, select the forum https://www.w3.org/Voice/2003/ir/voicexml20-ir.html that you want to visit from the selection below. Results 1 to 9 of 9 Thread: VXML error.badfetch Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode September 13th, 2011,06:59 #1 Renaissance View Profile View Forum Posts Member Join Date Oct 2008 Posts 29 VXML error.badfetch Hi, I am trying to use a simple "Hello World" vxml but got an error: "error.badfetch". In the logviewer i see these two lines; vxisvc::VXILogImpl::Error : Module-> StdInet Error-> 200 URL=C:\Program Files\Interactive Intelligence\Resources\VXIcache\VXML_tempFile_1001 428583.tmp vxisvc::VXILogImpl::Error : Module-> vxi Error-> 203 uri=C:\Program Files\Interactive Intelligence\Resources\VXIcache\VXML_tempFile_1001 428583.tmp Vxml's content is like this;
Candell, ComverseJerry Carter, SpeechWorksPete Danielsen, LucentJonathan Engelsma, MotorolaMike Epstein, Tellme NetworksDan Evans, NortelJim Ferrans, MotorolaWill Gardella, SAPJeff Kusnitz, IBMPaul Lamere, SunRob Marchand, VoiceGenieScott McGlashan, PipeBeachRalf Pfeiffer, BeVocalBrad Porter, Tellme NetworksKen RehorLaura Ricotti, LoquendoDavide Tosello, Loquendo Copyright ©2003 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply.Table of Contents1. Introduction1.1 Implementation Report Objectives1.2 Implementation Report Non-objectives2. Work During the Candidate Recommendation Period3. Participating in Implementation Report4. Entrance Criteria to PR5. Implementation Report Requirements5.1 Detailed requirements for Implementation Report5.2 VoiceXML Processor Coverage5.3 Notes on Testing Speech Recognition5.4 Out of Scope6. Systems7. Test ResultsAppendicesAppendix A. Test assertion XML API definitionA.1 Final status indicatorsA.2 Intermediate status indicatorsA.3 Input operationsA.4 Grammar definitionsA.5 Grammar selectionA.6 Predefined utterancesA.7 Document Type DefinitionA.8 Test examplesA.9 Sample XSLT Template DefinitionA.10 Transformation outputAppendix B. Abstract CGI (IRCGI) API definitionB.1 Processing ModelB.2 SyntaxB.3 Document Type DefinitionB.4 Test examplesB.5 UsageB.6 Transformation requirementsB.7 Reference XSLT documentsB.8 Test developer requirementsB.9 Web server administrator requirementsAppendix C. Acknowledgements1. Introduction The VoiceXML 2.0 Specification entered the Candidate Recommendation period on 28 January 2003. The planned date for entering Proposed Recommendation is 10 April 2003. Preparation of an Implementation Report is a key criteria for moving beyond the Candidate Recommendation. This document describes the requirements for the Implementation Report and the process that the Voice Browser Working Group will follow in preparing the report. 1.1 Implementation Report ObjectivesMust verify that the specification is implementable.Must demonstrate interoperability of implementations of the specification.1.2 Implementation Report Non-objectivesThe IR does not attempt conformance testing of implementations.2. Work During the Candidate Recommendation Period During the CR period, the Working Group will carry out the following activities: Clarification and improvement of the exposition of the spec