CUCM 9.1(2)SU1 and CUC 9.1(2)SU1 Upgrade Tips

CUCM Publisher

Upgraded from 9.1(2) to 9.1(2)SU1 [] over the weekend because of the extensive list of bugfixes.  Release notes –

Download the update here –

The publisher failed with the Common partition not having enough space.  This was a common issue in the 8.x to 9.x upgrades.

The fix is to use RTMT to clear out logs and other things in the common partition, or much easier is to use the “Free common space COP file” – ciscocm.free_common_space_v1.0.cop.sgn.cop file from here –

Once you install this COP file the common partition should have enough free space to install the upgrade.  I’ve seen this not clear out enough space in one other upgrade, but in the 9.1(2) to 9.1(2)SU1 upgrade it worked like a champ.

Unity Connection

While the Publisher was upgrading, I initiated the Unity Connection (CUC) upgrade to 9.1(2)SU1.  This install started and failed with a very nondescript error:

The solution in my case was documented in several TAC cases: Reboot the CUC server before doing the install.  I did this and the CUC upgrade completed without any issues.

One major bug fix I’ve been waiting for was a unified inbox issue where users on Exchange with very large mailboxes would have CUC quit syncing VM.  SU1 fixes that problem.

CUCM Subscribers

Once the publisher finished and was rebooted the subscribers upgraded without issue.