Hi,
One possible failure that could occur is if a data element made reference to a remote xml file that did not exist. The IVR error log would look something like this:
Code: Select all
Attempting to fetch http://www.example.com/~victor/baddatatag2.xml
HTTP/1.1 404 Not Found - http://www.example.com/~victor/baddatatag2.xml
DocumentParser::FetchXML - could not open URL: http://www.example.com/~victor/baddatatag2.xml
errno: 203 uri http://www.example.com/~victor/baddatatag2.xml
received event: error.badfetch
Another possible failure that could occur is if the data element made reference to a bad xml file with an error in it.
For an IVR example, here's a what a bad xml file would look like:
Code: Select all
<?xml version="1.0"?>
<boolean>
<asdf>
false
</boolean>
The IVR error log would show:
Code: Select all
Attempting to fetch http://www.example.com/~victor/baddatatag.xml
Parse error in file "http://www.example.com/~victor/baddatatag.xml", invalid XML
errno: 205 uri http://www.example.com/~victor/baddatatag.xml
received event: error.badfetch
However, for a successful data element transfer, the IVR log would show something like this:
Code: Select all
Attempting to fetch http://www.example.com/~victor/datatag.xml
bargein set to true
INPUTMODES set to "DTMF VOICE"
Audio segment added to prompt queue from TTS text/plain;charset=wchar_t for:
---------
Basically, the IVR application would accept the valid xml from the remote xml file and move on with the rest of the script.
Hope this helps.
Regards,
Plum Support