Anyone get SMS to work with Flowroute?

[Cytranic]

I have everything setup correctly. Flowroute says there are texts coming in. But I'm not seeing any activity on 3cx. Has anyone setup this successfully yet?

 

[Evolute IT]

The numbers are in E164 format +13333334444

Did you assign your DIDs in flowroute to that messaging profile? Or whatever they need. I use Telnyx, not Flowroute.

 

[amir_]

where are you posting that url? in flowroute?

Your explanation is helpful and makes sense. Yes - I copied that URL from the configuration wizard in 3CX into my Flowroute configuration page and I've configured ROUTES on 3CX to pass the INBOUND SMS messages to my E164 address.

 

[amir_]

Did you assign your DIDs in flowroute to that messaging profile? Or whatever they need. I use Telnyx, not Flowroute.

Yes - the numbers are mapped to that SMS profile.

 

[Viral-Technology]

So what? That URL is not for you, it's for flowroute. It's a Webhook and it works through POST and not GET, so if you open it in a browser (which does a GET), you will see either a 404, 403 or a custom page dedicated for that.

Apparently, they knew that people would try it so they put a small text page saying : "I'm a teapot". It's either a joke or an insult to the people trying that lol

thats actually pretty funny. i never tried to browse to that url.

 

[Evolute IT]

Yes - the numbers are mapped to that SMS profile.

Try to regenerate the API secret and access key and save that again in 3CX.

Also, small thing: are you using port 443 or 5001 for HTTPS?

thats actually pretty funny. i never tried to browse to that url.

Yeah, it is lol

 

[amir_]

No in a browser tab. It isn't meant for that.

He should use that URL in flowroute but something must be wrong if he's still not receiving SMS with the E164 numbers.

I'm posting it INTO my Flowroute configuration. I stated that that URL simply publishes that text out of curiousity.

 

[amir_]

Try to regenerate the API secret and access key and save that again in 3CX.

Also, small thing: are you using port 443 or 5001 for HTTPS?


Yeah, it is lol

I thought it was funny as well. So my question is, where can I find out what port we are using for HTTPS? This is my first installation of 3CX so forgive my noobness. I'm assuming 5001 because that is the port my webclient URL is mapped to - but how can I see the actual port configuration in my 3CX linux CLI or the web console?

 

[Viral-Technology]

Yes - the numbers are mapped to that SMS profile.

The number that you have enabled for sms. is it also your main number? that way you can test flowroute side by calling your main number and making sure it rings. I know it took me a minute to figure out how to route the calls in flowroute. its a lot different from the provider I use voip.ms

 

[Evolute IT]

I thought it was funny as well. So my question is, where can I find out what port we are using for HTTPS? This is my first installation of 3CX so forgive my noobness. I'm assuming 5001 because that is the port my webclient URL is mapped to - but how can I see the actual port configuration in my 3CX linux CLI or the web console?

The HTTPS port is the web one, so yes, in your case it would be 5001. The CLI does not use a port. The installer does (5015 during setup) but it is blocked afterwards.

 

[amir_]

The number I'm testing with is my actual DID so I know it works for inbound calls. Should my INBOUND firewall ACL be modified to allow this SMS traffic? Currently, all we allow INBOUND is from Flowroute source IP ranges on SIP.

 

[Viral-Technology]

I thought it was funny as well. So my question is, where can I find out what port we are using for HTTPS? This is my first installation of 3CX so forgive my noobness. I'm assuming 5001 because that is the port my webclient URL is mapped to - but how can I see the actual port configuration in my 3CX linux CLI or the web console?

here is a list of all ports and what they do. are you using a hosted pbx or on prim?.
https://www.3cx.com/docs/ports/

 

[Evolute IT]

The number I'm testing with is my actual DID so I know it works for inbound calls. Should my INBOUND firewall ACL be modified to allow this SMS traffic? Currently, all we allow INBOUND is from Flowroute source IP ranges on SIP.

You're hosted on-premise?

Is your port 5001 accessible from the Internet? (For mobile apps and SBC/STUN phones)

 

[Evolute IT]

here is a list of all ports and what they do. are you using a hosted pbx or on prim?.
https://www.3cx.com/docs/ports/

We keep saying the same thing lol

 

[amir_]

On Prem but I don't see anything in INBOUND firewall rules besides SIP. Yet - I'm able to access from the outside via my webclient - so our firewall rules MUST be allowing 5001.

 

[Evolute IT]

On Prem but I don't see anything in INBOUND firewall rules besides SIP. Yet - I'm able to access from the outside via my webclient - so our firewall rules MUST be allowing 5001.

You should probably be opening the TCP 443 as well, as WebMeeting and Messaging are using that port I believe. It's worth trying it.

If you use the Webclient from outside your network, it does mean that the port is opened.

 

[amir_]

Yep - confirmed that we are on 5001 and everything is configured properly between Flowroute and our 3CX on prem but INBOUND is still not properly getting routed to my internal 3CX extensions.

 

[amir_]

In this related article about configuring Flowroute - Slack for SMS - it specifically requires port forwarding to be enabled for inbound SMS flow to Slack :

https://blog.flowroute.com/2017/08/23/learn-how-to-receive-inbound-flowroute-sms-with-slack/

Therefore, I suspect that it is a mis-configuration on our firewall because the firewall checker test fails the "Full Cone NAT test".

So my first check on Monday will be the firewall and then I will get back to this thread with the results. Thank you to everyone who assisted because we have confirmed a nearly complete and correct firewall configuration with the exception of the port forwarding.

 

[amir_]

We resolved the full cone nat firewall check failure we were experiencing and we are still unable to process INBOUND SMS messages. Outbound SMS message flow instantly.

 

[TechUpgrade]

Any luck getting INBOUND SMS to work with Flowroute? We are running into the same issue and Flowroute doesnt seem to give any guidance except get with 3CX.

 

[TechUpgrade]

So found the issue on my end for inbound SMS. The ROUTE in 3CX needed the phone number listed as well as a "+" in front of the E164 Formatted number. Everything is working correctly now.