Failed unattended upgrade (hosted) and SMS is gone

[Creighton]

I'm staring at my 3CX configuration and scratching my head over missing SMS configurations that we've been using for ages. My main trunk no longer has SMS configured, and I also get a 404 error when I click on the Facebook & SMS link under messaging in the dashboard.

Anybody have a clue what happened to me here? I'm not seeing anything obvious in logs, appreciate any pointers on what to consider or look for.

Re-configuring SMS setup now, mostly concerned about it happening again.

 

[Charles_3CX]

Please let us know where you are looking at the configuration? are you in the management console or the admins webclient?

3cx Hosted systems are moving to update 6, so this will be a little different from what you were used to and suggest you check the guides here

 

[Creighton]

Hi Charles, thanks. Yes, it looks like my web browser was caching old features, which was giving me some extra consternation.

Having reconfigured SMS for the update, I still have a broken element in the webhook. I was passing SMS messaging from a Studio Flow in Twilio via a webhook here: https://messaging.3cx.com/v2/webhook/xxxxxxxxxxxxxxxx/twilio/sms/xxxxxxxx

This was just passing through a standard SMS JSON payload just like originates from Twilio, but the webhook now terminates under our host domain name, but I can't successfully pass a message using the same formatting. Have any idea if the JSON formatting has changed? Anything new about authentication? Seems like this should work the exact same way, so I'm wondering if I'm missing some configuration step.

 

[Creighton]

Hi Charles, disregard! For the sake of documentation, things have moved on the Twilio side as well. Previously, to the best of my knowledge, when programmatically manipulating the messaging service, and kicking the end session out via webhook to 3CX, it wasn't necessary to have the Webhook integration configured on the messaging service, and we worked with this configuration inside of what Twilio calls conversations. Now that SMS payload won't hand off via the programmatic webhook call without the webhook also being configured in the Messaging Service / Integrations. Back to testing tomorrow to see if that breaks any of the rest of our programming stack.