500-450 · Question #64
While a voice gateway accesses webservices elements, it times out and throws an error badfetch event. Which two options are common ways to reduce such errors?
The correct answer is A. Set FetchAudioDelay timeout C. Set FetchAudioMinimum timeout. In VoiceXML, a badfetch event fires when the gateway cannot retrieve a resource (audio, grammar, or document) within the allowed time. FetchAudioDelay (A) controls how long the gateway waits before playing hold audio during a fetch - tuning it gives the web service more…
Question
Options
- ASet FetchAudioDelay timeout
- BSet mediafetchDelay
- CSet FetchAudioMinimum timeout.
- DSet mediafetchDelay timeout.
How the community answered
(26 responses)- A73% (19)
- B19% (5)
- D8% (2)
Explanation
In VoiceXML, a badfetch event fires when the gateway cannot retrieve a resource (audio, grammar, or document) within the allowed time. FetchAudioDelay (A) controls how long the gateway waits before playing hold audio during a fetch - tuning it gives the web service more headroom before a timeout is declared. FetchAudioMinimum (C) sets the minimum duration that fetch audio must play, which prevents the gateway from cutting off the fetch attempt too early and triggering an error prematurely. Together, these two properties directly manage the timing window around resource retrieval and are the recognized VoiceXML mechanisms for reducing badfetch occurrences.
B and D are wrong because mediafetchDelay is not a valid VoiceXML or standard voice gateway property - it is a fabricated term. The fact that D adds "timeout" doesn't make it real; it's still the same non-existent attribute.
Memory tip: Both correct answers contain the word "Audio" - think "FetchAudio properties fix audio fetch problems." Any answer using the made-up word "mediafetch" is a trap.
Topics
Community Discussion
No community discussion yet for this question.