Alternatively, you can use vMotion, Veeam/SCP, or DRS to migrate CUC if you don't want to be bothered with setting up a new cluster.
I like doing this because it means a fresh start on config and you can test the new integration with a few users before moving everyone over. Install a NEW CUC 12.5 cluster on the new vSphere, integrate it with CUC via SIP (your old one is probably using SCCP), test it, then use COBRAS to migrate users, messages, and call handlers from the old CUC 11.5 cluster.Use PCD to upgrade/migrate CUCM to 12.5 on the new vSphere.Upgrade UCCX to the latest version that supports CUCM 10.5, which is UCCX 11.6.Upgrade CUC to the latest version that supports CUCM 10.5, which is CUC 11.5.CUC will probably need a two stage upgrade as well, because CUC 12.5 does not support CUCM 10.5 - if you have SCCP phones then you're going to run into issues with call transfers from Unity 10.5 to CUCM 12.5. You're right that UCCX is going to be a two stage upgrade if you don't want to completely break the cluster for the duration of the upgrade.
0 kommentar(er)
