How to setup SMS

[KaterinaK_3CX]

You can send and receive SMS and MMS messages from within 3CX and direct them to queues. This option is mainly for US & Canadian customers. In the US, DID numbers are enabled by default to send and receive SMS. This guide will help you with:

• Choosing your SMS provider
• Configuring SMS in 3CX
• Routing SMS
• Choosing who can send SMS

Read the guide.

 

[rjamesm2884]

Hello,

SMS with Flowroute will not go through it's asking to add +1 and when I do that it does it twice. I assume this is because of the outbound rules that need to be that way for Flowroute.

 

[NickD_3CX]

You don't need to change your Outbound Rules at all for SMS as they are not used.
Outbound rules are only used for Voice Calls you make.

Please re-read the guide linked above, particularly Steps #3 and #4.

 

[patricksmalley]

Is there a possibility of allowing custom/DIY connectors for SMS/MMS in the future?

 

[NickD_3CX]

For the time being it is only the Messaging PRoviders you see listed here:
https://www.3cx.com/docs/manual/sms-text/

We are looking at ways to expand this list on the future, but cannot at this point say for sure if and when this will happen.

 

[fairview]

How do you configure both voice/text to the same number as it use to work before? For example, you have a number that has an inbound rule pointing to a ring group. Before you could create a call queue and add agents, go to messaging and configure the route to that queue while simultaneously being able to use the same number for voice routing. Can someone please advise how to configure this now since the update. Thanks!

 

[cobaltit]

You can't without some hacks. This will be fixed in Update 6

 

[fairview]

You can't without some hacks. This will be fixed in Update 6

Can you elaborate on the hacks? I didn't know this function was broken.

 

[Clark-Ritchotte]

Our customers have Voice going to an IVR, and it looks like it's going to route the SMS to the IVR as well, whereas, with the old system, we can choose the queue; what is the "hack" to allow multi-inbound points per voice/SMS on the new version?

 

[Evolute IT]

Our customers have Voice going to an IVR, and it looks like it's going to route the SMS to the IVR as well, whereas, with the old system, we can choose the queue; what is the "hack" to allow multi-inbound points per voice/SMS on the new version?

Not yet possible. U6 will bring a workaround in the IVR setting (on the Webclient Admin side.)

 

[Clark-Ritchotte]

Thank you for the information, I will Disable updates for the time being, as most of my customers use it that way.

 

[BABALUCHA]

Can you elaborate on the hacks? I didn't know this function was broken.

Hello All
i guess i found the "hack" . So how i got this done is that i created a DUMMY RING GROUP and added all the extensions to that DUMMY RING GROUP that wants to receive the TEXT SMS , and programmed the RING GROUP Ring Time only 1 Second and after that "destination if no answer " pointed to IVR. i tested everything works great.
The only suck part is that 1 second Ring Time gives all those extensions 1 second ring that are in that DUMMY RING GROUP but i guess i just have to tell me client that this is the only way to get the IVR and text SMS will work for now untill the next update. Hopefully it helps

 

[SweetAction]

Actually there have been 2 "hacks"

1. Use a Queue: https://www.3cx.com/community/threads/sms-routing-ivr-allow-different-destination.116826/post-541161
2.: Register a SECOND Trunk and enable SMS on that trunk, but not enable it on the trunk that contains the voice routes. https://www.3cx.com/community/threads/sms-routing-workaround.116120/post-537962

Both prevent the second of ringing.

 

[BABALUCHA]

Actually there have been 2 "hacks"

1. Use a Queue: https://www.3cx.com/community/threads/sms-routing-ivr-allow-different-destination.116826/post-541161
2.: Register a SECOND Trunk and enable SMS on that trunk, but not enable it on the trunk that contains the voice routes. https://www.3cx.com/community/threads/sms-routing-workaround.116120/post-537962

Both prevent the second of ringing.

Thanks a lot for this info

 

[StevenMDR]

Hello all
I'm running a dedicated number from Twilio to test out direct calling/messaging with multi media on our enterprise setup and I've come across a couple of issues.

I'm hoping these can be solved currently and I'm just missing something.

When a external number sends a MMS text and image for example, 3cx will not catch the text body portion. This means we will have to take care to notify the people contacting us, that we can receive a message or a file but not both at the same time.
Regarding that issue in particular Twilio does send both the text body (in the same traditional way as before) and the file at the same time. So maybe this is a use case scenario that the devs missed?

The other issue I'm facing which is not a real problem just something really annoying from my prospective in IT. There is a MIME type issue causing errors and warning to spam me from Twilio. https://www.twilio.com/docs/api/errors/12300

To further explain..
When Twilio sends a text message (with or without media) to the 3cx webhook. Twilio expects a response from 3cx in a "application/xml", "text/xml" or "text/html" MIME type format. Of course 3cx sends a empty response back to let Twilio know it at least received a message (200 OK, I assume as I'm not seeing a status code on Twilio's side) which is correct. But the webserver of 3cx sends it's response with a ""application/json". Which causes Twilio to use it's fallback option and to store a log of the incident which again pings me on each occurrence.

Did I miss something in the guide or is this something that needs to be accounted for in a future update?

 

[Evolute IT]

Hello all
I'm running a dedicated number from Twilio to test out direct calling/messaging with multi media on our enterprise setup and I've come across a couple of issues.

I'm hoping these can be solved currently and I'm just missing something.

When a external number sends a MMS text and image for example, 3cx will not catch the text body portion. This means we will have to take care to notify the people contacting us, that we can receive a message or a file but not both at the same time.
Regarding that issue in particular Twilio does send both the text body (in the same traditional way as before) and the file at the same time. So maybe this is a use case scenario that the devs missed?

The other issue I'm facing which is not a real problem just something really annoying from my prospective in IT. There is a MIME type issue causing errors and warning to spam me from Twilio. https://www.twilio.com/docs/api/errors/12300

To further explain..
When Twilio sends a text message (with or without media) to the 3cx webhook. Twilio expects a response from 3cx in a "application/xml", "text/xml" or "text/html" MIME type format. Of course 3cx sends a empty response back to let Twilio know it at least received a message (200 OK, I assume as I'm not seeing a status code on Twilio's side) which is correct. But the webserver of 3cx sends it's response with a ""application/json". Which causes Twilio to use it's fallback option and to store a log of the incident which again pings me on each occurrence.

Did I miss something in the guide or is this something that needs to be accounted for in a future update?

See this thread: https://www.3cx.com/community/threads/issue-with-twilio-and-sms-on-18-0-update-5.116755/

 

[Clark-Ritchotte]

Do we know or have an expected date for the release of U6?

 

[SweetAction]

Do we know or have an expected date for the release of U6?

Typically the answer has been "when it's ready".

But based on past 3CX releases, from Alpha to Final is usually under 2 months. So I would guess before Feb 2023, but it's a guess.

 

[Heath]

I'm having some issues with setting up Texting, MMS, & SMS... I've read the discussion on how to enable SMS / MMS. My issue is Step #4.. I have Professional version.. So in the management portal, when I go to users and the desired extension, in the general tab, there is no option to enable SMS.. Or in any other tab...

 

[SweetAction]

I'm having some issues with setting up Texting, MMS, & SMS... I've read the discussion on how to enable SMS / MMS. My issue is Step #4.. I have Professional version.. So in the management portal, when I go to users and the desired extension, in the general tab, there is no option to enable SMS.. Or in any other tab...

In Update 6 you no longer need to enable a user for SMS. All users are enabled - as long as a DID routes to them on a SMS enabled trunk (either direct or via a queue/ringgroup) they can send and receive SMS.