can the URLS in outbound dialing use non-standard ports?

[ban]

When making outbound calls, is there any problem with sending Plum a StartVXMLURL with a different port number specified?

I can't seem to make an outbound call. The script is fine (I've verified this by setting the Application Setup URL to point to it.)

I keep getting an error of badfetch.buttery? None of the script is read.

[support]

No it shouldn't be a problem in using whatever port the webserver is running at, provided you specify the port correctly in the URL where you use it. Here is an IVR example:

Code: Select all

<submit next="http://www.samplehost.com:XXXX/serverscript.php"/>

where XXXX is the nonstandard port number
Hope this helps!

Plum Support Staff

[ban]

Thanks, but the syntax of the URI/port is correct.

(As I mentioned, the voiceXML can be correctly interpreted and read from this same URI for an inbound call. it just doesn't work for the outbound call.)

Any other ideas, please let me know.

[support]

Hello:

Can you provide the URL to the IVR script you are trying to run? Perhaps we can attempt to run it here and see if we can replicate your IVR issue.


sincerely,

Plum Support

[ban]

I'd rather not post the URL here.

I have another question. Is the startVXMLURL variable supposed to have a capital S or not? I've seen both startVXMLURL and StartVXMLURL in the documentation.

The last callID that failed is 494

[support]

If you want to email the URL with your IVR script to support@plumvoice.com and put FORUM QUESTION, RE: CHRIS in the subject, we can test your URL.

It doesn't matter whether you use capital or lowercase characters; POST variables are not case sensitive


Plum Support