We've Moved! Please visit our new and improved forum over at our new portal: https://portal.plumvoice.com/hc/en-us/community/topics

Where do you check for error code description?

Questions and answers about IVR programming for Plum DEV

Moderators: admin, support

Post Reply
ejohnson
Posts: 5
Joined: Mon Jun 28, 2004 2:40 pm
Location: San Diego
Contact:

Where do you check for error code description?

Post by ejohnson »

What does this mean? Is the error in the vxml file or the php file that is called from the vxml file?


Thanks!


Thu 01 Jul 2004 04:09:34 PM EDT (000000;000;1088712307) [vxi] ERROR: DocumentParser::FetchDocument - Parse error in file "storedb.php", line 5, column 8 - Empty content not valid for content model: '(catch|help|noinput|nomatch|error|form|link|menu|meta|metadata|property|script|var)+'
Thu 01 Jul 2004 04:09:34 PM EDT (000000;000;1088712307) [vxi] ERROR: errno: 205 uri storedb.php

support
Posts: 3632
Joined: Mon Jun 02, 2003 3:47 pm
Location: Boston, MA
Contact:

IVR Error Code Descriptions

Post by support »

Based on the IVR log lines that you posted the error is in the file storedb.php. The error being returned is a parse error, the IVR error in question is simply that the script storedb.php is not returning valid VoiceXML. Just as a web (html) form would do a submit to a page that would show content (ie - login data, confirmation, etc) so should a VoiceXML page. The IVR error seems to be implying that you are simply returning an empty VoiceXML document, somthing like:

Code: Select all

<?xml version="1.0"?>
<vxml version="2.0">


</vxml>
The VoiceXML parser is first as foremost an XML parser, and so it must follow the rules defined in the VoiceXML DTD. In this case the rule being broken is that the <vxml> tag must contain at least one of the following items:
(catch | help | noinput | nomatch | error | form | link | menu | meta | metadata | property | script | var)+
This IVR error should be resolved by simply double checking the VoiceXML output of the storedb.php file.

Hope this helps!

The Plum Support team :)

Post Reply