We have a client with over 1500 792x wireless phones (nearly all 7925Gs) which need to be migrated from an old CUCM 8.5.1.10000-26 cluster to a new 10.5.2.13901-2 cluster. The customer manually migrated a test phone from the old cluster to the new and back again without issue. We were skeptical of this since we believed they would have run into the ITL issue seen when moving phones from one cluster to another in the post 8.0 CUCM world. However, we were able to duplicate the result with a couple of test phones. Suspecting a bug in the CUCM version or with the 7925 firmware we opened a TAC case. TAC advised that we should set the old cluster to pre-8.0 rollback and reset the phones - which is in line with what we expected would have to happen - but couldn't answer the question of why did this work. I haven't been able to find any information on this and was hoping someone else in the community has seen this before. The customer is reluctant to set the cluster to pre-8.0 rollback as we have seen all devices reset after changing this between false/true and they want to avoid resetting all of the devices if possible (24x7 hospital situation). 7925 firmware is CP7925G-1.4.5.3.LOADS. I did see a vague reference to 7925s and SBD here: https://supportforums.cisco.com/sites/default/files/legacy/6/6/6/125666-CUCM-Security-Webcast_Final.pdf but could find no other information on the bug mentioned, CSCsz46363.
If you run a report under Unified Serviceability for phone features, and use Security by default as filter, you'll ge the list of phoned that do use SBD/ITL, the 792X are not listed there.
If you run a report under Unified Serviceability for phone features, and use Security by default as filter, you'll ge the list of phoned that do use SBD/ITL, the 792X are not listed there.
