Page 1 of 1

Error 205: Expected an element name

Posted: Thu Jun 11, 2009 9:57 am
by PSN
We have a hosted site for IVR that works without an issue at this time. We also have a test site setup that is causing an issue when we try to test and troubleshoot updates. Whenever we use the test site (Phone # 617-712-3696) I can get no farther than selected "1" to make a payment when the system indicates an error has occurred.

The log for the call is only about 15 seconds long (as expected) and always ends with the same error:
DocumentParser::FetchDocument - Parse error in file "https://psntest.paymentservicenetwork.c ... r_Util.asp", line 1, column 2 - Expected an element name
errno: 205 uri "https://psntest.paymentservicenetwork.c ... r_Util.asp"

The area "line 1, column 2"... is this:
<?xml version="1.0"?>

This is at the top of EVERY file we use. This is direct code from our production page we copied onto our test server to ensure we have 100% correct code and this page works perfectly with our toll-free numbers (877-390-7368 and 877-885-7968)

-- Do we need to set a certain configuration on our test server?
-- Is there a setting on your end that needs to be corrected?
-- Any other suggestions?

Thank you in advance for your assistance. Please let me know if you need any further information.

Reconfigure IVR test server

Posted: Thu Jun 11, 2009 1:16 pm
by support
It appears that your test server is misconfigured. Your IVR server needs to execute the ASP code that you are hosting there, but it is not doing so and serving it unprocessed. If you go into Call Logs > Recent Calls, you will be able to see the last IVR log for that phone number. Find the links that say "Click here to view saved VoiceXML script" and you will be able to see what our IVR server fetched. The first few lines of the IVR script being fetched are not a valid XML header, but instead:

Code: Select all


<%@ LANGUAGE=vbscript  LCID=1033 %>

<% sActiveInstance = True %>
...
which are not valid VoiceXML. In fact, if you try to access the https://psntest.paymentservicenetwork.c ... r_Util.asp URL yourself from a web browser you can see that the inline ASP scripting is being served as-is instead of being interpreted.