18.0.6.908 +flowroute inbound issue after upgrade. Solved

[swiftechinc]

The upgrade broke our SMS as well as inbound call routing. We updated Everything per the notes which should have fixed everything but it did not. Inbound calls were being rejected for authentication and sms was also being rejected. I was able to solve this today and just wanted to put this here in case anybody else runs into the problem as I spent two days on it.

I still don't know exactly where the problem was but after trying a number of things I restored from a backup made just before I began making the changes stated in the official 3CX instructions. Repeated the exact same changes that I had done previously per those same instructions, and within 3 minutes everything was working properly again.

After spending roughly 7 hours troubleshooting this only to discover that restoring to a backup and doing it again for the first time fixed the problem seems rather bizarre which is why I wanted to post this. It almost seems like there is something underlying in the database that did not get properly updated and I don't know if this might be a problem others have or not. So I did want to post this here just in case somebody else runs into the problem and they're pulling their hair out, perhaps simply starting over by restoring a backup will resolve the issue.

 

[Lee Cramman]

It's annoying when that happens. You're left wondering if you missed a step or did something wrong or if the update process simply borked on you. And you'll never truly know for sure.

I find that the ease / speed with which 3CX can be redeployed from scratch and / or restored from backup makes me generally less prone to falling down a troubleshooting rabbit hole trying to fix a broken install. It's something that they deserve real praise for and one of the standout features of 3CX for me.

I came from a world of Windows servers (quite a few years ago!) where bare metal rebuilding / restoring an AD controller following a hardware failure was... a time-consuming exercise in frustration. Whereas I can redeploy and restore a 3CX install from scratch in 30 minutes using mostly mouse clicks.