Yes, including removing the old SMS config in the Messaging tab. I did notice that emojis seem to work. Wondering if there is some size issue - although the same photos work fine with Telnyx. I'll start a ticket and report back here.
I created a support ticket and confirmed we have lost the ability to split route voice from sms/mms traffic with this updates new configuration method. So if you have clients setup the old way in which there receptionists would call a client about an appt or something and the client texts back a response that they are, "in a meeting, want to reschedule to X", as they have in the past. That will no longer work if the business uses an IVR. PLEASE bring this feature back (I can't submit ideas)!
A semi workaround:
For those thinking "I'll just not update" - V18 u6 will get rid of 3CXs messaging proxy, so... that will only work for so long.
If the routing for the same DID is matched in the order it comes in on the list, set your voice first with the IVR it goes to and SMS with a different route to a queue second... I could see how that would work. I'll give that a shot!
Yep I got the drift there. Now I just need to get MMS working in both directions. I can send out to cell but can't receive.
I just confirmed this work around only really works with vary simple setups with like one SMS enabled DID, it becomes a logical rubix cube to get it to work after that. You can see my updates there.
what did you do about this?
I actually created a second SIP trunk to the provider. In the main voice trunk, I set the DIDs as *xxxxxxxxxx, then in the SMS trunk I entered the DIDs as +1xxxxxxxxxx (enter the country code needed). In the inbound routes, I have two options for these numbers, so if the main line needs to go to a DR, I can send the other SMS added DID to a queue or user as needed. So far it works, but it would be nice to be able to separate these within the single SIP trunk.
