Solved No inbound sms on second number, first number working fine

[KeithTX]

3CX Version: Enterprise 18.0.237
Server OS: Debian 10
Hosted: On-Prem
Trunk: Flowroute

I'm having an issue with incoming SMS on a second number. The first number I added for SMS works fine for both inbound and outbound, the second number can send but not receive.

I have confirmed that the DID in Flowroute has the proper route and that messaging is enabled. In 3CX under SMS routes I have confirmed that the second number is entered in the proper format.

According to Flowroute the Messaging Stats the inbound texts are being sent. In 3CX, after enabling verbose logging, I cannot find any entries for the inbound message in the 3cxManagementConsole.log file.

Again, the first number I added works fine for both in and outbound messages.

Anyone have any ideas on what may be wrong?

-Keith

 

[NickD_3CX]

Hi Keith,

We are currently investigating an issue that Flowroute has brought to our attention that happens on SOME DIDs of SOME users, without a obvious pattern to it.

Given that can't easily replicate it, I will send you a PM shortly with something easy to do that will help us a lot track this down and determine if it is something on the 3CX or Flowroute side.

 

[N0NAME]

I also have a DID that can send but not receive SMS with Flowroute. I had previously tested the DID with FlowSMS, I assumed that this caused the issue. The message does show up in messaging stats on the Flowroute dashboard, but doesn't make it to 3CX. I have not reached out to Flowroute about the issue.

 

[NickD_3CX]

I also have a DID that can send but not receive SMS with Flowroute. I had previously tested the DID with FlowSMS, I assumed that this caused the issue. The message does show up in messaging stats on the Flowroute dashboard, but doesn't make it to 3CX. I have not reached out to Flowroute about the issue.

If you haven't confirmed with Flowroute, best first do that as we want to stay focused on cases that are confirmed for the time being.
Let me know if Flowroute confirms that they are not getting a response, or getting and error response, from the messaging server.

 

[N0NAME]

If you haven't confirmed with Flowroute, best first do that as we want to stay focused on cases that are confirmed for the time being.
Let me know if Flowroute confirms that they are not getting a response, or getting and error response, from the messaging server.

Thanks, I opened a ticked with Flowroute.

 

[NickD_3CX]

|I am removing the "Under Investigation" label from this thread as the issue of the OP was resolved.

A small recap of the situation is initially Flowroute support was saying that they were getting an error message when sending to the 3CX Messaging Server.
On our side, we were not seeing anything hitting your servers.

 

[NickD_3CX]

After assisting Flowroute in their investigation, the issue was found and Flowroute is taking actions to fix it on their end.

As far as we are aware, there are no actions that are required on your end, but whoever had a problem should wait up to 48 hours, and if they continue having a problem, contact Flowroute support.

As there is nothing that we can do on the 3CX side, I am setting this to "Solved".