Solved FlowRoute SMS Issues

[healthy]

I have attempted using SMS through Flowroute and have already followed the guides and the earlier thread from 12/10/20 but have been unsuccessful.

I have created a new API (v. 2.1 listed as the latest on Flowroute)
I can send SMS texts out, and they are successfully routed to the proper extension.
When I attempt to reply in, the messages never make it to the proper extension.
If I look in the Flowroute Messaging stats, I can see both sides of the conversation.

Any help is most appreciated

 

[[email protected]]

I have attempted using SMS through Flowroute and have already followed the guides and the earlier thread from 12/10/20 but have been unsuccessful.

I have created a new API (v. 2.1 listed as the latest on Flowroute)
I can send SMS texts out, and they are successfully routed to the proper extension.
When I attempt to reply in, the messages never make it to the proper extension.
If I look in the Flowroute Messaging stats, I can see both sides of the conversation.

Any help is most appreciated

Did you remember to set the "Route" in the second tab? That was my mistake in my initial configuration. SS is attached for reference. I'm using Telnyx, but the process within the admin console would be identical.

 

[healthy]

Thanks @[email protected]
I do have a route configured. I even have it simplified to be to just one extension, and even so, it never makes it.

 

[ChrisC_3CX]

Just so that we better understand the situation, are you able to send SMS just fine but you can never receive replies or new messages?

If this is the case, have you made sure to include the number in E.164 format without any spaces (ex: +123456789) in the "Route" tab of Flowroute's SMS entry?

Also, do make sure that the SMS test passes by editing the Flowroute SMS entry and clicking on "Test" at the top.

 

[healthy]

Yes, ChrisC,
SMS Passes Test, I can send OUTBOUND from 3CX, but INBOUND replies do not get received. If I look in Flowroute's console, logs, I can see my message traffic both ways.

My phone number is formatted as +12345678901 and I have created a whole new config with a new API to rule out something being amiss in my initial configuration.
What's more, I even added the DID in my SIP trunk, but with it enabled or not, the result is the same. Inbound SMS messages are NOT received.

 

[ChrisC_3CX]

In that case, you might need to look into this a bit further. I'd recommend enabling Verbose Logging mode under Dashboard >> Activity Log >> Settings and then replicating the issue again by sending an inbound SMS message. Note down the exact time you sent it, wait for at least a minute and then download and have a look through the 3CX Management Console Log to check if the message does indeed reach the 3CX PBX or not.

You can download the log from Dashboard >> Activity Log >> Logs >> Instance >> 3cxManagementConsole.log

 

[healthy]

I just ran the tests and see the following in the log:

ManagementConsoleJS.Controllers.SmsController (3CXManagementConsole).
2021/04/12 12:03:36.552|5216|0020|Trc|received from MS: {
"provider_id": 12005,
"type": "message",
"from": "+OUTSIDECELLPHONE#",
"to": "+INSIDEFLOWROUTE# ",
"conversation_id": "CONVERSATION-0A350FB5-78ECABA9-E5EA9C5C-5BCAEEAC",
"message_id": "MESSAGE-6C23170B-F44F2EBA-FD19CFFF-17103AF0",
"provider_signature": "",
"provider_timestamp": 1618243433749,
"provider_message_id": "mdr2-ad8275929ba811eb991efaf17f381d98",
"provider_conversation_id": "",
"timestamp": 1618243433749,
"message": "Test back. To show non-receipt"
}
2021/04/12 12:03:36.553|5216|0020|Err|Cannot find provider for salt cnet2eld0m8dtq
2021/04/12 12:03:36.553|5216|0020|Trc|[Microsoft.AspNetCore.Mvc.Infrastructure.ObjectResultExecutor] Executing ObjectResult, writing value of type '<>f__AnonymousType74`2[[System.String, System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e],[System.String, System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]]'.
2021/04/12 12:03:36.553|5216|0020|Trc|[Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker] Executed action ManagementConsoleJS.Controllers.SmsController.Index (3CXManagementConsole) in 1.0455ms
2021/04/12 12:03:36.553|5216|0020|Trc|[Microsoft.AspNetCore.Routing.EndpointMiddleware] Executed endpoint 'ManagementConsoleJS.Controllers.SmsController.Index (3CXManagementConsole)'
2021/04/12 12:03:36.553|5216|0020|Dbg|#138363 (traceid=0HM6KH8CVSIL9:00000001) STOP: POST https://MYADDRESS.3cx.us/messaging/cnet2eld0m8dtq processed 00:00:00.0016531
2021/04/12 12:03:36.553|5216|0020|Trc|[Microsoft.AspNetCore.Hosting.Diagnostics] Request finished in 1.9398ms 200 application/json; charset=utf-8

I'm not sure where the cnet2eld... is, it doesn't match any of the settings I can see.

 

[ChrisC_3CX]

There's a good chance this is happening because the webhook url in the Flowroute SMS configuration on 3CX (seen under messaging >> flowroute) does not match the webhook url in your flowroute account (portal).

Please try the following:

• Access the Management Console and go to Messaging
• Provided you only have one FlowRoute account setup, edit it and check the webhook URL in step 4
• Look at the very last string, it should match the one you see in the logs: cnet2eld0m8dtq

If it does not, it may mean that the Flowroute SMS entry on the PBX got deleted and recreated without updating the flowroute account accordingly. I'd recommend setting up the SMS configuration from scratch by following the steps provided.

 

[healthy]

Thanks for the reply ChrisC,
After completely ripping out the API specifics with no success, I stumbled upon another thread here which had the following command which has resolved the issue for me:

curl https://api.flowroute.com/v2/numbers/FlowrouteDID/relationships/sms_callback -H "Content-Type: application/vnd.api+json" -X POST -d '{"data": {"attributes":{"callback_url": "3CXWebhook"}}}' -u acesskey:apikey