TIPS Clearly Anywhere messaging

[kmcdaniel]

Will messaging work with DIDs with other providers on the app? Or does the DID and messaging need to be with ClearlyIP?

 

[KNERD]

It depends on the provider, and if the end side has it set up

 

[kmcdaniel]

It depends on the provider, and if the end side has it set up

skyetel? BulkVS?

 

[kenn10]

Are you aware of @billsimon open SMS module?

New open source SMS Connector module

I’m excited to share with the community a module I have been working on over the past few weeks and ask for your collaboration to make it better: a generic, expandable connector for using third-party SMS providers with FreePBX’s SMS subsystem. Right now I have it working with Telnyx and...

community.freepbx.org

 

[kmcdaniel]

Are you aware of @billsimon open SMS module?

New open source SMS Connector module

I’m excited to share with the community a module I have been working on over the past few weeks and ask for your collaboration to make it better: a generic, expandable connector for using third-party SMS providers with FreePBX’s SMS subsystem. Right now I have it working with Telnyx and...

community.freepbx.org

Can you use this with clearly anywhere app?

 

[Samot]

Will messaging work with DIDs with other providers on the app? Or does the DID and messaging need to be with ClearlyIP?

Straight from their documentation:

The SMS integration with Clearly Anywhere is tied into the FreePBX SMS system and supports SMS and MMS from any providers who hook into the FreePBX Messaging system, including ClearlyIP's own SIP trunking service.

 

[kmcdaniel]

Straight from their documentation:

Thanks! @billsimon would you be able to point me in the right direction to implement this part of the installation?

For inbound SMS/MMS and outbound MMS to work, you will need an HTTPS path inbound to your PBX from your provider(s). This means:

• Import or generate a TLS certificate in Certificate Manager
• Enable it on the web server using Sysadmin Pro or by manually configuring Apache
• Allow your provider(s) webhook addresses through the FreePBX Firewall and/or your network firewall
• Set the public DNS name in the AMPWEBADDRESS setting: Advanced Settings -> FreePBX Web Address

Sending of SMS/MMS requires verification and registration performed through your provider and is outside of the scope of this module or document.


OR is this not recommended on PBX2027 to open up 443?

The module looks outstanding and I can't wait to give it a try with BulkVS and Voip.ms

 

[billsimon]

In short, providers that use a RESTful API for messaging (most) want to send messages to you over HTTPS, so you have to have your server listening and available on port 443 and have a valid certificate configured.

Some providers post the IP address from which the webhooks will come. Others (Twilio) do not and require you to open port 443 widely, which isn't great.

So - is it "recommended...to open up 443?" It's required if you want inbound messaging to work, and best with providers that let you know where they are sending from so that you can open only those IPs on your firewall. Note - there is a little bit of dialplan middleware written specifically for a Voip.ms integration that allows you to receive SMS over SIP instead of HTTPS. Search the forum or nerdvittles for Ward's write-up on that.

I have been using this module personally and working with others who use it extensively, since I released it over a year ago. I have personally tested all providers in the module except Bandwidth.com and Voxtelesys which were contributed code.

 

[kmcdaniel]

In short, providers that use a RESTful API for messaging (most) want to send messages to you over HTTPS, so you have to have your server listening and available on port 443 and have a valid certificate configured.

Some providers post the IP address from which the webhooks will come. Others (Twilio) do not and require you to open port 443 widely, which isn't great.

So - is it "recommended...to open up 443?" It's required if you want inbound messaging to work, and best with providers that let you know where they are sending from so that you can open only those IPs on your firewall. Note - there is a little bit of dialplan middleware written specifically for a Voip.ms integration that allows you to receive SMS over SIP instead of HTTPS. Search the forum or nerdvittles for Ward's write-up on that.

I have been using this module personally and working with others who use it extensively, since I released it over a year ago. I have personally tested all providers in the module except Bandwidth.com and Voxtelesys which were contributed code.

Thanks @billsimon. Question for you, I deleted a number under the list numbers section in the SMS Connector and now I want to add it back but it's saying that the DID already exist, however it is not listed there in PBX. Is there a way to make sure deleted so I can re-add the DID?

 

[billsimon]

Thanks @billsimon. Question for you, I deleted a number under the list numbers section in the SMS Connector and now I want to add it back but it's saying that the DID already exist, however it is not listed there in PBX. Is there a way to make sure deleted so I can re-add the DID?

I haven't seen this bug. Delete and add again works for me. If you can reproduce the bug please open a ticket on the github repo so that I can fix it. What version of smsconnector are you running? Latest is 16.0.17.

 

[JacobyBarr]

I’ve found that pairing your setup with something like the whatsapp business api can make your workflow smoother, especially if you’re juggling chatbots and system integrations. The quick onboarding and simple HTTP calls help a lot when you just want to plug things in without jumping through hoops. I also like that it handles media cleanly across PHP, Python, and Node.js, so you’re not stuck wrestling with odd workarounds.