VXML Server: VoiceXML Application Fails to Access Another Resource

From DocWiki

Revision as of 19:17, 18 December 2009 by Docwikibot (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

VoiceXML Application Fails to Access Another Resource

Problem Summary VoiceXML application fails to access another resource, for example, to play a media .wav fail, and the IOS log contains SERVER ERROR: A VoiceXML exception occurred: error.badfetch.http.-n, where n is a negative error code.
Error Message SERVER ERROR: A VoiceXML exception occurred: error.badfetch.http.-n
Possible Cause error.badfetch.http.<errorcode> has a positive error code when a connection to the HTTP server is successful, for example; 200 (OK), 400 (Bad Request), or 404 (Not Found). When a gateway encounters an internal error, including server connection failure, it uses the following negative error codes to differentiate the error from a server response code:

-1 Client error

-2 Timeout error

-3 Message decoding error

-4 Message encoding error

-5 Message transmission error

-6 Client write queue full

-7 Connection error

-8 Client unsupported

-9 Client socket receiving error

Recommended Action Make sure the resource you are attempting to access is running. For example, if the VoiceXML application fails to access a .wav file from a media server, make sure that the media server's World Wide Web Server service is running.

Also make sure that the path to the .wav file is correct.

Release Release 7.0(2)
Associated CDETS # None.

Rating: 0.0/5 (0 votes cast)

Personal tools