Search results

FYI, there was an update on May 5 that says it addresses this issue. I've tried it, and it still isn't working for me, but your mileage may vary.

I can't really help on this, other than to confirm this behaviour on my system, using Grandstream phones (GRP/GXP). It would also be nice to be able to see the caller ID on the BLF button, instead of "From park". I suspect these issues are related.

As I said previously, there is no Broadcast option related to SMS. The Applications->Call Broadcast page is for phone call broadcasts, not SMS. We've looked into PlaySMS (playsms.org) as a dedicated SMS broadcast and interactive SMS application platform.

The Messages option is a built-in SMS messaging application that the author, @markjcrane, has been working for a year or two now (possibly longer). It never made it into full production, at least with support for more than one carrier. As I understand it, he is now actively working on a...

To my knowledge, there is no support built into this module for SMS Broadcast (AFAIK, the only broadcast built into FusionPBX is phone call broadcast, and even that is rudimentary). This SMS module is strictly intended as person-to-person usage though it already does have integration for...

No problem. Yes, the whole 1+ thing on responses has bitten me a time or two. Glad it's working for you! Regarding the log truncation, here's some info on that. I haven't tried changing the log_errors_max_len setting, but it sounds like that might work. Could even try the ini_set command at...

No, that's one of those "feature-bugs". There is a buffer limit on the logging. I suspect it will only write a certain amount to the log at a time. It's writing a lot to the log for each inbound message, for troubleshooting purposes. It will cut off the log in the middle of a line, somewhere...

That is a new error to me. Here's something I found that may help. I don't know why it would be exceeding the buffer, but you might try the settings in the one of the answers to the linked question.

Try browsing to this URL yourself and see what you get. The access.log shows a 301, which is a redirect. Something in your nginx config may be redirecting back to https, which then fails.

Check your nginx access.log and see if you are seeing any activity when you send a message in. If you are not seeing anything in either nginx log, then I’d review your webhook URL settings on Bandwidth. Also, try accessing the webhook url yourself to make sure it is accurate (you should get...

Robert, Note that the tips @mak_make and I are giving you are related to outbound. As far as inbound, it really depends on your error.log as to what's happening when Bandwidth tries to send to you.

Here's what I use for my "public" context section: <context name="public"> <extension name="ten-digit"> <condition field="to" expression="^(\d{10}.*)$"> <action application="set" data="final_delivery=true"/>...

I'll let @inder.singh or @mak_make weigh in on the inbound, but in general, no, FusionPBX doesn't have to reach out. They get pushed to FusionPBX by the carrier, and then the scripts in FusionPBX are responsible for either sending it via email and/or delivering it to the endpoint. It sounds...

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...