Search results

While that's probably the better approach long-term (updating the code to work with new version of the API), one other option might be to set the API version that you are using to V1.

Happens to the best of us. Glad to hear that it's working. You're welcome.

Might be best to start a new thread and just link to it here. If you do, please include details on what you have tried, and what exactly is or is not happening (Does thinQ show the receipt of the message? Do they show errors? Does the message get delivered to the endpoint but doesn't look...

In your sms_hook_bandwidth.php, just before the } else { line, add this: return $response->withStatus(200) ->write("OK"); Again, this isn't something that I can test, so you'll have to just try it and see if that gives back the response that Bandwidth is expecting.

The current version that is available on GitHub should work. Just follow the directions in the readme. You do need to add your secret key to the default setting for "telnyx_secret_key" in the SMS section and enable all the telnyx settings, also in that section.

I was estimating the cost at about half of the $459/month price, so yeah, quite a bit--and a fraction of that setup fee. Your mileage may vary, of course. A lot of the higher setup costs are for things like professional design and marketing. There are a couple of dozen different package...

Yes, I was confused about that as well. As I said, we haven't actually signed up for it, but we did start the process, to check it out, and that's where we found out their approach is that you can opt for only pieces of it. Even though it is a lower price than the $459/month, as @ad5ou said...

After looking a little closer at what you are getting from Bandwidth, I'm amazed that inbound is working at all. It looks like they've changed the data layout from the way this was set up originally. In theory, the following code should match what they are sending now (make sure to make a copy...

I found some code in the sms_email.php that has a little different syntax for array access. If the above doesn't work, try this: if ($debug) { error_log('[SMS] REQUEST: ' . print_r($data, true)); if (gettype($data)=="array") { error_log('[SMS]...

Replace your debug section with this: if ($debug) { error_log('[SMS] REQUEST: ' . print_r($data, true)); if (gettype($data)=="array") { error_log('[SMS] data-type(from array): ' . print_r($data[0]['type'])); //error_log('[SMS]...

No, it does not go through that file on outbound. The "hook" file is only for inbound. But the "callback" from Bandwidth is coming back just like an inbound message, so it DOES go through the "hook" file. All you need to do is to have that "if" statement properly catch the message type and...

Ok, then some variation of that "if" statement should allow you to filter out the "callback" and avoid the error.

Just FYI, it looks like the $459/month and so on pricing is for if you need the entire package of white label benefits. They let you customize your package, and I suspect that most people will be able to get by with half or less of what they are including in that price. That's not to say that...

If your recipient is not getting the outbound message, you might confirm with Bandwidth that they are seeing the OB message and if they can tell you why they aren't delivering it.

Sorry, I can't test this, but try it with this tweak in that one line: if ($data->type != "message-received") { It's the "separate delivery callback" that is causing the error. Also, is the outbound message being received by the recipient? All we're trying to do with these code...

Sorry, I'm using Telnyx API v1. But I thought I remembered someone in that other very long thread mentioning that they got it working with Telnyx v2 API

Try this: <?php include "../root.php"; require_once "resources/require.php"; require_once "../sms_hook_common.php"; if ($debug) { error_log('[SMS] REQUEST: ' . print_r($_SERVER, true)); } if (check_acl()) { if ($_SERVER['CONTENT_TYPE'] == 'application/json; charset=utf-8') {...

Another user, @inder.singh has done some work on the Bandwidth integration for SMS. Maybe he will chime in here. Fair warning, I don't use Bandwidth for SMS, so I can't confirm the following. However, based on this line in the response you got from Bandwidth: [type] => message-received I...

Check your nginx logs, but it's probably already replying with a HTTP 200 code. If so, maybe add an echo "ok"; before the "route_and_send_sms"? If it's not replying with a HTTP 200, have a look here for info on that.

Glad you got the provisioning working! Make sure you re-enable authentication. I am using 0 in "Resync Periodic". This field is only for if you want the phone to reach out and reprovision automatically every X seconds. In most cases, that's not needed. But I doubt this is causing the call...