3cx Upgrade from V15.5 to V16.0

[daveh82]

Upgraded last night from V15.5 to V16.0. on Windows Server 2016. Took a very long time to backup and restore, but it did work. All yealink phones needed to be updated with latest firmware, they would/will not upgrade via the 3CX console. I ended up updating them manually (100+ phones), hopefully that won't be the case next time, I've never had this issue before.I read and understood the issues and limitations with CFD not being fully implemented, based on what I read seemed like I would be okay with my very simple CFD. After the upgrade, our old CFD was no longer working, it's just a simple date time condition that should work. I opened the old CFD in the new call flow designer application, everything looks good, resaved. However, I have nowhere to update the CFD in V16. I know I need Beta to have the call flow apps under advanced.... It's not clear to me why the old CFD doesn't work in the first place as the documentation indicates most existing CFD's will work without modification.

 

[cobaltit]

So I think you might have misread things. When CFD is released (Update 1 for v16) then most old apps should work with minimal effort in converting them. But at this point no CFD stuff works unless you are running the beta, simple or otherwise.

 

[daveh82]

That's a shame, not sure why 3cx would release software that is missing previously expected and useful features.

 

[cobaltit]

They had a number of new features/improvements in v16 they didn't want to hold up while waiting for the new CFD. v15.5 is still supported so there is no need to upgrade to v16. Most of the installs we manage are stlil on v15.5 unless there is a compelling need for v16 (like transcription for those folks that missed the MS Speech API cutoff.