Troubleshoot CVP VXML Server Badfetch Errors

Available Languages

Download Options

  • PDF     (5.7 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (65.1 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (64.6 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:September 13, 2017
Document ID:212068

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

    Introduction

    This document describes how to troubleshoot a Cisco Customer Voice Portal (CVP) Voice XML (VXML) Server Application badfetch error. 

    Prerequisites

    Requirements

    Cisco recommends that you have knowledge of these topics:

    • Cisco Customer Voice Portal (CVP)
    • Cisco VXML Server Applications
    • Cisco Call Studio
    • Cisco Unified Contact Center Enterprise (UCCE)

    Components Used

    The information in this document is based on these software versions:

    • CVP Server 9.x and above
    • UCCE 9.x and above 

    The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

    Problem Summary  

    Some calls fail and the VXML application activity logs show that its due to badfetch errors.

    Error Message: 

    VXML application activity logs shows 'badfetch' error. 

    Solution

    Possible solution: add the VoiceXML property 'fetchtimeout' to the root document

    1. In Unified Call Studio, right click on the desired project and choose Properties.
    2. Click on Call Studio - Root Doc Settings.
    3. Under VoiceXML Property enter fetchtimeout, and under Value enter the desired timeout. For example for 60 seconds enter "60s".
    TAC Authored

    Contributed by Cisco Engineers

    • Rohit Harsh
      Cisco TAC Engineer

    Was this Document Helpful?

    FeedbackFeedback

    Contact Cisco

    This Document Applies to These Products