Having trouble with SMS via VoIP.ms

wwdotcomputers

SMB User
Joined
Dec 27, 2024
Messages
6
Reaction score
0
I am having trouble periodically sending SMS out. Inbound works fine, and it is a periodic problem. I have tried redoing the BEARER TOKEN. The logs show that there is an authentication error. VoIP.ms says it is on 3CX side. I used the default VoIP.ms template when I set up the SIP trunk. I think this just started happening in v20.
 
Solution
VoIP.MS has confirmed that they released a fix for the authentication issue. We tested on our end and it seems to be resolved. Please let us know if you are still having issues.
I've been having this same issue for a month. None of the configuration guides seem to address the issue. Appears to occur more frequently with other users.
 
Do you see an error in the Event Log of the PBX ? If so what does it say exactly?
 
SeverityWarning
Event ID30030
Date10/29/2026 11:52 AM
DetailsFailed to send message(s) to the provider 'generic' from '+125XXXXXXX.generic' to '+125YYYYYYY'. Exception: { "data": { "event_type": "message.finalized", "payload": { "id": "51008820261029125233", "record_type": "message", "to": [ { "status": "delivery_failed" } ], "errors": [ "missing_credentials" ] } } }
 
Thank you. We will look into it with the provider to get to the bottom of this
 
Thank you. We will look into it with the provider to get to the bottom of this
Hi Yiannis, we're having the same issue. Messaging works fine on the SIP trunk provider (voip.ms) however, 3CX errors out as follows. Can you please provide a solution?

Severity WarningEvent ID 30030Details Failed to send message(s) to the provider 'generic' from 'generic' to ''. Exception: { "data": { "event_type": "message.finalized", "payload": { "id": "123", "record_type": "message", "to": [ { "status": "delivery_failed" } ], "errors": [ "missing_credentials" ] } } }
 
Hello,
We are having the same issue as well. It stated for us around October 5th. We get the same error on about every 3 out of 4 texts. Not exactly that but around that. Some succeed.
 
Hello,
We are having the same issue as well. It stated for us around October 5th. We get the same error on about every 3 out of 4 texts. Not exactly that but around that. Some succeed.
I just checked again and 5 out of 5 succeeded. This has probably been fixed.
 
  • Like
Reactions: KyriacosS_3CX
Hi everyone, also wanted to let you know that after about 3 weeks of having this issue, SMS messaging seems to be wroking today for the first time.
 
  • Like
Reactions: KyriacosS_3CX
Thank you for reporting back.
 
VoIP.MS has confirmed that they released a fix for the authentication issue. We tested on our end and it seems to be resolved. Please let us know if you are still having issues.
 
Solution
Good day everyone,
I have just setup the SMS integration to VoIP.ms. Inbound and outbound SMS is working fine, but I do not see the option to start a new SMS from the 3CX app. I would appriciate any feedback?

Thank you
 
Good day everyone,
I have just setup the SMS integration to VoIP.ms. Inbound and outbound SMS is working fine, but I do not see the option to start a new SMS from the 3CX app. I would appriciate any feedback?

Thank you
Under the chat option. Press the plus sign and you should see send SMS. If you do not. You need to enable SMS under the management of that number in voip.ms and/or set up the api webhook url and set the dialing mode to NANPA.
 
Thanks Phased, I do not see the SMS option. I do have enabled SMS under voip.ms, configured SMS/MMS Webhook URL and changed dialing mode to NANPA. I will try to restart the system and update you all.
 
Did you assign an SMS capable number to a user or to a queue as a DID?
 
Yes the SMS capable number is assigned directly to the user's extension. Same situation with multiple users.
 
Do you have a Pro or higher license? Are you self hosted or paying for hosting?
 

Forum statistics

Threads
112,535
Messages
593,087
Members
165,747
Latest member
Hugh_Wilson