CUCM "Prepare Cluster for Rollback" Cisco to Avaya Migration

[impromptu]

Hi,

we are migrating Cisco phones from CUCM to Avaya.

Could anyone explain what are the real risks of using the CUCM parameter "Prepare Cluster for Rollback to Pre-8.0" on a per location/site basis?

Thanks,

Ana

[b.winter]

First: You cannot just migrate Cisco phones (which are able to register on CUCM) to any other SIP-system. You need Cisco-MPP phones or you need to convert Cisco Enterprise phones (which are for registering on CUCM) to be Cisco MPP phones (where you need licenses for). Search the internet for more info.

Second: You have to find out, if Cisco MPP phones are supported on the Avaya and vice-versa.

Third: As the "Prepare Cluster for Rollback to Pre-8.0" is an enterprise parameter, this effects every phone or none. You cannot differentiate between locations / DP's / ...
But generally, the risk is very low. The effect that the parameter has is, that is deletes the ITL file from the phone. The phones will still be registering to the CUCM.

[Nithin Eluvathingal]

You cannot simply  migrate Pone registered with CUCM to avaya system.

"Prepare Cluster for Rollback to Pre-8.0" has no role in your case.

To register the Devices on Avaya you need to convert them to MPP or try some workarounds.

"Prepare Cluster for Rollback to Pre-8.0" will remove the ITL files on the phones which help these phones to register with a new CUCM cluster

2.12.0.0

[impromptu]

Hi Bwinter and Nithin,

We have already successfully migrated one phone from CUCM to Avaya where we manually deleted the ITL file from it. After that the phone has downloaded the new firmware and everyting went well.

And yes, I know that this parameter is Enterprise one , that's why I asked what would happen for the rest of the phones registered in CUCM (the ones not migrated yet) if they go for any reason in restart while the Rollback parameter is switched to True. Will they re-register with CUCM?

Thanks,

Ana

[TONY SMITH]

There are a few things that stop working on the phones, not core functions but those that rely on SSL or HTTPS.  From memory I think the directory is one of them, and maybe Extension Mobility.

[impromptu]

Hey Tony,

Thank you very much for answering.

In fact I found the same thing so I checked all the phone services configured in CUCM and all of them were using HTTP and not HTTPS. Although I wasn't sure about Corporate Directory service so I've just checked and it says here the following:

" What is the "Service URL" field set to under the Corporate Directory service? If the URL is set to "Application:Cisco/CorporateDirectory" then, based on the phone's firmware version, the phone makes either an HTTP or HTTPS request.Phones that use firmware version 9.3.3 and later by default make an HTTPS request.  "

https://www.voipinfo.net/docs/cisco/118699-technote-directory-00.pdf

So basically it won't work if the Rollback parameter is set to True.

Thanks,

Ana