I’m mainly interested in inbound call processing at the moment and would prefer to use Tropo but if OpenVBX doesn’t have this issue and TropoVBX does (there’s also no indication on GitHub when it’s likely to be fixed), then I’ll have to go with what works.

Most customers that need serious Twitter support in their application already bypass Tropo and write directly to the Twitter API.

According to Constant Contact’s TOS, all your users must agree to receive such emails – as such, Constant Contact allows the users a way to opt-out, in case people have attempted to nefariously use Constant Contact as a spam server. If a user opts-out, their contact information is removed entirely, which not only removes any email addresses associated with the contact but the phone number as well.  If a user opts-out, the SMS application will also be effectively disabled for that user.  Additionally, if a user was sent an SMS that they felt was unsolicited, harassing or abusive and reported it to their carrier, the carrier would relay the report to us and the traffic would be blocked. While there are ways to send out spam SMS, we do our best to ensure that we’re not enabling that type of behavior

Even if I had opted in to their email list, receiving SMS is something else entirely, and sending SMS spam is not legal last I checked.

Here is my hosted php code:

$answers = array(“It is certain”,”It is decidedly so”,”Without a doubt”,”Yes – definitely”,”You may rely on it”,”As I see it, yes”,”Most likely”, “Outlook good”,”Signs point to yes”,”Yes”,”Reply hazy, try again”,”Ask again later”,”Better not tell you now”,”Cannot predict now”, “Concentrate and ask again”,”Don’t count on it”,”My reply is no”,”My sources say no”,”Outlook not so good”,”Very doubtful”);

$rand_keys = array_rand($answers, 2);

$answer = $answers[$rand_keys[0]];

if($currentCall->network == “SMS” && $numberToDial == ”){ say($answer); }