startpage.php error during hosted outbound call

[dking]

I queue a call. The call goes through and I answer the phone. Then an error occurs. What's going on? Here's the session log:


Tue 07 Sep 2004 03:57:01 PM EDT:
Call connected
Writing status success to outboundStatusURL: http://outbound.plumgroup.com/outboundl ... lee_type=2
Attempting to fetch http://outbound.plumgroup.com/outboundl ... lee_type=2
Beginning tel session
Beginning prompt session
Beginning rec session
Call Start Event: ANII 16174172151 DNIS 0111 VURL /usr/local/plumvp/config/director.vxml
DocumentParser::FetchDocument()
Previously playing audio (if any) has finished
Previously playing audio (if any) has finished
DocumentParser::FetchDocument(/usr/local/plumvp/config/director.vxml)
Attempting to fetch file:///usr/local/plumvp/config/director.vxml
VXI::var_element(name="ani" expr = "session.telephone.ani")
VXI::var_element(name="dnis" expr = "session.telephone.dnis")
VXI::var_element(name="id" expr = "session.id")
VXI::var_element(name="callee_type" expr = "session.telephone.callee_type")
http://outbound.plumgroup.com/outboundlib/startpage.php
Previously playing audio (if any) has finished
Previously playing audio (if any) has finished
DocumentParser::FetchDocument(http://outbound.plumgroup.com/outboundlib/startpage.php)
Attempting to fetch http://outbound.plumgroup.com/outboundlib/startpage.php
VXI::var_element(name="session_id" expr = "session.id")
VXI::var_element(name="callee_type" expr = "session.telephone.callee_type")
Previously playing audio (if any) has finished
Previously playing audio (if any) has finished
DocumentParser::FetchDocument(startpage.php)
Attempting to fetch http://outbound.plumgroup.com/outboundl ... 1094586945
DocumentParser::FetchDocument - Parse error in file "startpage.php", line 11, column 108 - Unterminated entity reference
errno: 205 uri startpage.php
received event: error.badfetch
bargein set to true
INPUTMODES set to "DTMF VOICE"
Audio segment added to prompt queue from TTS text/plain;charset=wchar_t for:
---------

A serious error of type
---------
bargein set to true
INPUTMODES set to "DTMF VOICE"
Audio segment added to prompt queue from TTS text/plain;charset=wchar_t for:
---------
error.badfetch
---------
bargein set to true
INPUTMODES set to "DTMF VOICE"
Audio segment added to prompt queue from TTS text/plain;charset=wchar_t for:
---------
has occured. Exiting.
---------
VXI::exit_element()
Previously playing audio (if any) has finished
Newly queued prompts are now being played

Tue 07 Sep 2004 03:57:06 PM EDT:
Previously playing audio (if any) has finished
Call End Event
Ending session
Sending sessionID for notifyOutboundDisconnect: http://outbound.plumgroup.com/outboundl ... 1094586945
Attempting to fetch http://outbound.plumgroup.com/outboundl ... 1094586945

Tue 07 Sep 2004 03:57:07 PM EDT:
Ending Session On Channel 2

[support]

Hello,

The IVR error is being caused by the URL formatting you are using. You seem to be using URL encoded get variables, however, you are not properly escaping &. For correct URL encoding & should be encoded as &. The IVR error you are seeing is related to this parsing issue.

However, in this case it should be pointed out that plum provides the POST variables call_parameters and campaign_parameters for the IVR outbound API. These should be used if you need to submit arbitrary data to a given IVR outbound start URL. When the IVR outbound HTTP POST is performed you should assign these variables for posting data to your script.

Hope This Helps

The Plum Support Staff

[dking]

I need to submit arbitrary data to the call result url as well. How would I accomplish that? There is no call_parameters POST variable for the call result url.

[support]

That's correct. There is no call_parameters POST variable on IVR systems for the call result URL. The call_parameters variable is only intended for submitting arbitrary data to the start URL. Since the call parameters are invariant anyway (on a per queued call basis) you should be able to correlate any call parameters you originally sent with the call ID that's returned in your initial POST to queuecall.php. The call ID is one of the variables POSTed back to your result URL so you should be able to then do a look up for the original call parameters in your database. Alternatively, you can embed information in the customizable message reference field as well.

The Plum Support Staff