Hello!
I am trying to point my application DNIS to a remote file on my server and can open it and view it in the browser but when i click validate it says it can't find it.
any reason for this?
is there anything i should be doing specifically to make sure that calls (including subdialog) to my server are going through?
I notice when i make subdialog calls or any calls to remote files i keep getting the same error:
DocumentParser::FetchDocument - Parse error in file "http://mysite.com/ivr directory/filename", line 1, column 50 - Expected whitespace
i am trying to get the basic app up and running asap - please help!
We've Moved! Please visit our new and improved forum over at our new portal: https://portal.plumvoice.com/hc/en-us/community/topics
remote application dnis
post the contents of that return data to debug IVR issue
Hello,
You are going to have to provide more information than what you have given so far. You can find out what your web server is sending to the VoiceXML after you have completed a call. Just go to the "Application Setup" page, click "Last Log" next to the number you just called. You should be able to scroll down and find the line that says:
Clicking this will open a saved version of the page sent by your application server to our VoiceXML system. If you could post the contents (partial or complete) of that return data we can help you debug the IVR issues you are having.
Regards,
Plum Support
You are going to have to provide more information than what you have given so far. You can find out what your web server is sending to the VoiceXML after you have completed a call. Just go to the "Application Setup" page, click "Last Log" next to the number you just called. You should be able to scroll down and find the line that says:
Code: Select all
Click here to view saved VoiceXML script
Regards,
Plum Support
Last edited by support on Mon Jan 04, 2010 5:31 pm, edited 1 time in total.
Here is the information you requested: note i have replaced the accountID it is returning with # signs but the value that would be returned is correct. The vxml document looks fine - however when you view source there is about 100 lines of whitespace before the first line - i have tried everything to suppress this whitespace within the code but having no luck...is there someone else who has run into this problem? should i use a different tag than subdialog to retrieve data or perform other processing? i am very frustrated and running out of time...
<?xml version="1.0" encoding="UTF-8" ?>
- <vxml version="2.0">
<var name="accountID" expr="'#######'" />
- <form id="returnAccountID">
- <block>
<return namelist="accountID" />
</block>
</form>
</vxml>
<?xml version="1.0" encoding="UTF-8" ?>
- <vxml version="2.0">
<var name="accountID" expr="'#######'" />
- <form id="returnAccountID">
- <block>
<return namelist="accountID" />
</block>
</form>
</vxml>
IVR tags have rules about initial white space
Hello,
The reason the page is not validating is because the XML standard requires the first line of the document contain the XML header. This is not an entirely uncommon issue for certain IVR application server environments. What language are you using to generate this IVR script? For interpreted programming languages like PHP and ASP it is usually as simple as making sure the first thing your script does is print the XML header prior to doing any other processing.
Unfortunately this is not something isolated to the IVR tag, <subdialog>. You will not be able to interact with your IVR application server using any POST or GET based VoiceXML tag, they all have the same rules about initial white space in a document.
Regards,
Plum Support
The reason the page is not validating is because the XML standard requires the first line of the document contain the XML header. This is not an entirely uncommon issue for certain IVR application server environments. What language are you using to generate this IVR script? For interpreted programming languages like PHP and ASP it is usually as simple as making sure the first thing your script does is print the XML header prior to doing any other processing.
Unfortunately this is not something isolated to the IVR tag, <subdialog>. You will not be able to interact with your IVR application server using any POST or GET based VoiceXML tag, they all have the same rules about initial white space in a document.
Regards,
Plum Support