1. Cisco Unity Connection
Separate ISO Feature
EDCS JAN

2. Notice
The information in this presentation is provided under Non-Disclosure agreement and should be treated as Cisco Confidential. Under no circumstances is this information to be shared further without the express consent of Cisco.
Any roadmap item is subject to change at the sole discretion of Cisco, and Cisco will have no liability for delay in the delivery or failure to deliver any of the products or features set forth in this document.

3. Agenda Introduction ISO Naming Convention Defect Integrated Release
Install/Upgrade Support
References

4. Introduction

5. Introduction
12.0 onwards Unity Connection is going to publish its own ISO separated from Call Manager
Name and build number are different from earlier ISO
No impact on Unity Connection features
COP file is required to upgrade from previous releases
No change in installation process

6. Branch Strategy
Now Unity Connection uses a new branch cuc_mainline in parallel to cc_mainline.
To get VOS defects fix in cuc_mainline, library is pulled from cc_mainline at alternate day

7. ISO Naming Convention

8. ISO Naming Convention ISO Name Build Number FCS Build: 12.0.1.10000-X
With Unity Connection 12.0 and later, the new name of ISO is: UCSInstall_CUC_ X.sgn.iso
Build Number
FCS Build: X
ES Build: Need to be decided
SU Build: Need to be decided

9. Defect Integrated Release

10. Defect Integrated Release
For Unity Connection, process is same to check build version in Integrated- releases section of CDETS.
To check VOS defect fixed in Unity Connection ES/SU builds, a new CLI is introduced:
show vos version
This CLI shows the cc_mainline VOS version, which is integrated with Unity Connection build
On the basis of VOS version, You can get the list of defect fixed.

11. Continued…
Scenario 1
To check whether Connection defect is fixed in Unity Connection build
Go to CDETS page, search a defect and check Integrated-releases.
Example:
Assuming You have Connection build
On CDETs, check the Integrated-releases section for Connection build.
If Connection build or below appears, it means defect is fixed in build

12. Continued…
Scenario 2
To check VOS defect fixed in Unity Connection ES/SU build and related defect opened on Unity Connection like PSIRT.
Go to CDETS page and search a VOS defect
Go to Related Defects tab and select corresponding Connection defect
Check Integrated-releases for build version

13. Continued…
Scenario 3
To check VOS defect fixed in Unity Connection ES/SU build, for which no related defect opened.
Assuming VOS defect is fixed in build and Unity Connection build version is
Login to Unity Connection via CLI
Run command: show vos version
If active version is or above, it means defect is fixed in Unity Connection build.
If active version is or below, it means defect is not fixed in Unity Connection build.

14. Install/Upgrade Support

15. Installation
On fresh installation only “Cisco Unity Connection” appears as product deployment on vSphere console
Installation can be performed from PCD, AFG or other supported tools.

16. Upgrade
To support upgrade from previous release to 12.0, following COP files need to be installed :
Upgrade can be performed from PCD, AFG, CLI, Cisco OS Administrator page or other supported tools.
Upgrade Path
COP File installation before Upgrade
version 8.5 or lower
ciscocm.refresh_upgrade_v1.5.cop.sgn
ciscocm.cuc_upgrade_12_0.cop
version 9.x,10.x,11.x
version 12.x
None

17. References
Install, Upgrade and Maintenance Guide for Cisco Unity Connection Release 12.x : stall_upgrade/guide/b_12xcuciumg.html