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?

 

[amir_]

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.

Yep - our issue was that we were ACL'ing inbound source IP ranges in our FW. Once that FW ACL was modified, inbound SMS began to flow.

 

[Block5]

Hey all!
With flowroute, I am able to receive inbound but not send outbound. I get the "401: Authentication failed" error. This is the most functionality I can get. My number is configured per instructions. I'm running this demo box at Vultr with no firewall enabled. Hopefully I'm just missing something obvious.

Thanks 3CX! Looking forward to using this integration.

 

[StefanW]

I would assume the API is not right, the message you see is generated by the provider.

 

[Block5]

I would assume the API is not right, the message you see is generated by the provider.

That's what I thought at first, too. I recreated the API for this integration and have confirmed the key and secret are correct. The 'test' is successful. not sure what else I can do. I'll probably reach out to flowroute next

 

[StefanW]

unfortunately, from what I see, you configured on the PBXside and that the test passes, I would contact their support to determine the cause.

 

[healthy]

I am having similar issues. I can send out TXTs from the 3CX APP, and they are received by the phone recipient, but replies don't make it back. Looking in FlowRoute's console, I can see the entire text of the messaging going back and forth, but the replies from external SMS don't make it either directly to an extension or to the queue I want it going to.

 

[J.Fanning]

I am having similar issues. I can send out TXTs from the 3CX APP, and they are received by the phone recipient, but replies don't make it back. Looking in FlowRoute's console, I can see the entire text of the messaging going back and forth, but the replies from external SMS don't make it either directly to an extension or to the queue I want it going to.

I see the same thing on a DID line, however our mainline to another extension works both ways...

 

[healthy]

I see the same thing on a DID line, however our mainline to another extension works both ways...

Ok, so do you think the problem lies with Flowroute or with the config in 3CX?
I have checked and 443 is open, as is 5001, I don't seem to be blocking anything related to Flowroute. Maybe I'll look and see if they have specific IPs I should be whitelisting.

 

[J.Fanning]

Ok, so do you think the problem lies with Flowroute or with the config in 3CX?
I have checked and 443 is open, as is 5001, I don't seem to be blocking anything related to Flowroute. Maybe I'll look and see if they have specific IPs I should be whitelisting.

I think the problem lies with 3CX, but not sure it's our config. We are hosting on aws lightsail and the fact that we are getting sms working on the Direct line both ways would indicate ports aren't an issue. Still on DID lines we can send out sms from 3cx, but not receiving incoming sms in 3cx, but we can see all messages in flowroute incoming and outgoing. I wonder if there's a bug in how 3cx handles messages on DIDs to extensions?

Does anyone have multiple sms lines to multiple extensions working with Flowroute?

 

[cobaltit]

Firewall is not relevant if you are getting an authentication error. Authentication error means the traffic went out, but the other side didn't like it.

 

[J.Fanning]

I think the problem lies with 3CX, but not sure it's our config. We are hosting on aws lightsail and the fact that we are getting sms working on the Direct line both ways would indicate ports aren't an issue. Still on DID lines we can send out sms from 3cx, but not receiving incoming sms in 3cx, but we can see all messages in flowroute incoming and outgoing. I wonder if there's a bug in how 3cx handles messages on DIDs to extensions?

Does anyone have multiple sms lines to multiple extensions working with Flowroute?

Update:
I can get all DID numbers to send and receive sms messages except for one. I've assigned it to multiple extensions to no avail. It's like any sms sent to that DID evaporates in PBX. I was able to send, but not receive and the issue is only related to one DID#. Insights are appreciated.

 

[Matjes]

Update:
I can get all DID numbers to send and receive sms messages except for one. I've assigned it to multiple extensions to no avail. It's like any sms sent to that DID evaporates in PBX. I was able to send, but not receive and the issue is only related to one DID#. Insights are appreciated.

We are having a similar problem. Having 3 DIDs with Flowroute, all 3 are sending fine but only one is receiving. All messages are logged inside the Flowroute console but the ones to 2 DIDs just disappear. Where can we find the 3CX log for SMS messages? Or does someone know why this has to be like that?

 

[J.Fanning]

We are having a similar problem. Having 3 DIDs with Flowroute, all 3 are sending fine but only one is receiving. All messages are logged inside the Flowroute console but the ones to 2 DIDs just disappear. Where can we find the 3CX log for SMS messages? Or does someone know why this has to be like that?

Chat log is under 'Advanced' on menu

 

[Matjes]

Thank you. I did see that one but was wondering if there is a way to see a more detailed view of the chat log.
As far as Flowroute's logs go the message is leaving there but I don't know if 3CX is receiving and discarding it or if it is getting lost inbetween. Also I would like to understand why a certain number transmits both ways and another would only send and not receive. By the way, we were using FlowSMS before and all numbers were working flawlessly.
Here is a little more to explain our situation:
We started testing with an original Flowroute DID +1386515xxxx which was only able to send. Then we tried a DID which we had ported to Flowroute a while back +1386462xxxx. This is our main number which also was only able to send. At the end we tested an 800 number that was also ported at the same time and did not expect that to work at all. What a surprise, it did send and receive!
In an ideal situation we would like the main and the 800 numbers to work and add some DIDs for certain extensions.

 

[StefanW]

You can take the logs from a pbx where it is not working and we can have a look if it is seen by the pbx.

Set the pbx to verbose logging. Send one message out and one back. Wait 10m and collect the 3CX Management Console Log. Send this to community(at)3cx.com

 

[StefanW]

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

it does have a pinch of salt to it but it is actually RFC
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/418
418 indicates that the service is operating but what it is been asked to do cannot be done (GET).

 

[StefanW]

Update:
I can get all DID numbers to send and receive sms messages except for one. I've assigned it to multiple extensions to no avail. It's like any sms sent to that DID evaporates in PBX. I was able to send, but not receive and the issue is only related to one DID#. Insights are appreciated.

In many cases, numbers you have are been ported via carriers to another and so on.
It might be that the one number is on still on a provider which does not support fully messaging or is hanging in the air. Best to connect the provider's support to get it checked out.

 

[J.Fanning]

Thank you. I did see that one but was wondering if there is a way to see a more detailed view of the chat log.
As far as Flowroute's logs go the message is leaving there but I don't know if 3CX is receiving and discarding it or if it is getting lost inbetween. Also I would like to understand why a certain number transmits both ways and another would only send and not receive. By the way, we were using FlowSMS before and all numbers were working flawlessly.
Here is a little more to explain our situation:
We started testing with an original Flowroute DID +1386515xxxx which was only able to send. Then we tried a DID which we had ported to Flowroute a while back +1386462xxxx. This is our main number which also was only able to send. At the end we tested an 800 number that was also ported at the same time and did not expect that to work at all. What a surprise, it did send and receive!
In an ideal situation we would like the main and the 800 numbers to work and add some DIDs for certain extensions.

I got this from flowroute support:
Flowsms sets the callback url on a number by number basis which overrides the account wide setting. Any number that has been set this way must continue to have the sms call back url set at the DID level.

https://developer.flowroute.com/api/numbers/v2.0/set-a-messaging-callback-url-for-phone-number/

 

[Matjes]

Thank you. I just got the same message from Flowroute. So updating the webhook and the keys works only for DIDs that have not been used for SMS with another provider before. Here is the command line that has to be used (<are the variables>):

curl https://api.flowroute.com/v2/numbers/<DID>/relationships/sms_callback -H "Content-Type: application/vnd.api+json" -X POST -d '{"data": {"attributes":{"callback_url": "<New callback URL>"}}}' -u <accessKey>:<secretKey>

Windows Powershell did not work for me but Linux terminal did.
After all it wasn't 3CX discarding the messages but Flowroutes discrete routing and as far as I'm concerned this issue is resolved. Thank you everyone.

 

[DavidA]

Having similar (and more) issues. Running under Azure/Linux fully updated Enterprise license. I got a new number on FlowRoute, opted in for SMS. Did all the setup per the instructions. I ran the test on 3cx, though it sounds like thats not that helpful. I have a green dot on my entry in SMS. I do have a trunk into Flowroute that wasnt being used, but is current. I have another trunk with FlowRoute going into my fax server. I have it setup with SIP registration for 3cx and it all says connected.

I see test sms' hitting flowroute but nothing delivered by 3cx. I have my extension in 3cx enabled for SMS. In the web client i dont have a Chat menu option like i see in the setup instructions and marketing. In the Android App (joined beta and running 16.6.2.89) I have a Chat icon, but it is greyed out. 3cx is 16.0.7.1078.

Thanks any help