SMS Does/Doesn't Work on Different Extensions

caldwell

Bronze Partner
Joined
Nov 8, 2010
Messages
105
Reaction score
29
We just assigned some DIDs to some users. We asked them to test the SMS capability. Carrier is VOIP.ms.

Numbers are all set up like other/previous DIDs with the webhook.
Numbers are attached to trunk.
Numbers are assigned to users.

One user sends a test SMS to a 10-digit US number, and it goes through. They can also receive.

Another user sends a test SMS to a 10-digit US number, and it fails. [They have tried multiple numbers as of this writing. All fail.]

VOIP.ms shows NO record of it in the SMS log on their end.

3CX shows the message in the Chat log, but there are no debug details to see what happened.

How do we debug this issue? And what are the problems/solutions that we likely should consider?
 
With SMS, the number must be entered in full E.164 format (+1xxxxxxxxxx) to be sent, as SMS does not use outbound rules as calls do.
 
It has been tried both ways: E164 and NANPA.

The user that successfully sent and received was using NANPA (10-digit). The user that failed tried both E164 and NANPA.
 
Also, VOIP.ms has a configuration option that SMS can be set as NANPA or E164. In the past, we have had issues with all the numbers that were (and still are) set as E164 in the VOIP.ms SMS configuration section for DIDs. This "sometimes it works and sometimes it doesn't" issue has been an ongoing problem with 3CX SMS and VOIP.ms for over a year. I'm just finally getting a chance to address it.
 
What is the error message seen by the user who tried to send to this number, and/or the error seen in the admin console event log related to these failed SMS messages?
 
USER notification: Red text: Not delivered. Red exclamation mark by message.

REDACTED Event log: Failed to send message(s) to the provider 'generic' from 'xxxyyy7777.generic' to 'xxxyyy1234'. Exception: { "data": { "event_type": "message.finalized", "payload": { "id": "41934020261119115747", "record_type": "message", "to": [ { "status": "delivery_failed" } ], "errors": [ "webhook_not_enabled", "webhook_not_enabled" ] } }}

The DID is listed as one of many DIDs on the same VOIP.ms trunk. I checked that number, and voila, for some reason it did NOT have the webhook enabled on it. Strange, since I bulk edited numbers.

Thank you!

Question: will ALL sms failures show up in the Event Log? I will have to check there for future issues.
 
  • Like
Reactions: Charles_3CX
I would also advise using the VoIP.MS trunk template, as you seem to be using a generic SIP trunk instead, but I am glad you found the issue.
 

Latest Posts

Forum statistics

Threads
112,551
Messages
593,186
Members
165,762
Latest member
LchaplinTCG