Inbound messaging not working with Flowroute

[Calvin1723]

Inbound messaging not working with Flowroute, Flowroute is showing traffic both ways. 3CX is unable to receive inbound messages

 

[NickD_3CX]

Hi!

The first thing to check is that everything is set up correctly, so please go over the instructions in the Management Console --> Messaging, in your Flowroute entry. Particularly, make sure that the webhook URL is correctly placed in the Flowroute portal.

Next, ensure that the "Test" button at the top of this page does not give you any errors.

If that is also OK, enable Verbose logging, then send a new SMS to your Flowroute DID with the text something like "Flowroute SMS Test". Wait a minute or so, then go to the Dashboard --> Activity Log --> Logs --> Instance, and in here download the "3cxManagementConsole.log" file. In this file, search for the message you sent, e.g. "Flowroute SMS Test".

If you don't find it, it may be a good idea to contact Flowroute support, because a few weeks ago they had a problem that after we investigated together with them, turned out to be an issue on their end, so you might also be affected:
https://www.3cx.com/community/threa...econd-number-first-number-working-fine.86217/

 

[jbarrett]

We are also having an issue with inbound SMS through Flowroute. We are in the process of setting up a new self-hosted 3cx server and have confirmed that everything is configured correctly according to instructions in the management console. We can also successfully send outbound SMS from the DID and associated extension we set up for testing. However, the Test button under the messaging setup returns the following error:

"The connection was refused. Please run a firewall check to identify the issue. Messages cannot be received until this issue is resolved."

The firewall checker is not returning any errors, though. We've also confirmed with Flowroute support that the inbound messages are being received on their end and delivered to the webhook url, but they are receiving a 500 response. Flowroute also did check to make sure there was no indication that it was related to the errors they were having with some DIDs a few weeks ago. As far as they could tell, everything looked correct on their end. I was hoping someone might have some ideas or be able to point me in the right direction before we break down and pay for support through 3CX.

 

[jbarrett]

Just wanted to provide an update for anyone having a similar issue. We are using the default port 5001 to access the management console. We had NAT forwarding enabled for port 443 in our firewall and it appears SMS messages are delivered via the standard HTTPS port. After updating the NAT port forwarding to send traffic using port 443 to 5001, everything started working.

We didn't see anywhere in Flowroute's or 3CX's documentation where this should be required and up to this point, the documentation has been fairly straightforward and thorough. So I'm not confident that this is a best practice solution or if something else might still be configured incorrectly. Has anyone else had to forward 443 to 5001 in order to get inbound SMS to work?

 

[NickD_3CX]

Hi @jbarrett ,

I'm glad you figured it out!

After updating the NAT port forwarding to send traffic using port 443 to 5001, everything started working.

It isn't required, if you have set up your 3CX system using port 5001 (which is the default for 3CX), that is where the SMS messages will be delivered.

Also advice for anyone else reading this, before contacting your SMS Provider, always use the "Test" button. IF that shows any errors, there is 0% chance of inbound SMS working and the reason for it failing is NOT the SMS Provider.
This needs to be fixed first, then check other things.