Immediate callback with no response

[dorsey]

I'll give that a try, but I wanted to answer your other question first. We have two HTTP libraries, one that uses curl and another that doesn't. Depending on how PHP is built (options), the curl library will sometimes only work when executed in the context of browser response and aborts when run in a script from the command line or via cron. Since this script is run "outside" a browser, we're using the non-curl version.

The right answer is to always build PHP with the correct options, but our hosting service maintains PHP and often rebuilds it during routine maintenance without letting us know. We've learned through bitter experience (i.e., things just stop working), so we take the preventive approach.

Dorsey

[dorsey]

Removing the extra two characters solved the problem, but I thought that the HTTP specification required those as a separator. Also, we had not changed that code while moving from testing to production, so it will remain a mystery.

You really went beyond the call of duty in actually running our code. I certainly don't regret making the decision to switch to Plum Voice from our previous service.

Regards,
Dorsey