Cisco Unity Connection Separate ISO Feature EDCS 2017

Cisco Unity Connection Separate ISO Feature EDCS- © 2017 Cisco System Inc. All rights reserved JAN 01 2017 Cisco Confidential 1

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. © 2017 Cisco System Inc. All rights reserved Cisco Confidential 2

v Introduction v ISO Naming Convention v Defect Integrated Release v Install/Upgrade Support v References © 2017 Cisco System Inc. All rights reserved Cisco Confidential 3

. © 2017 Cisco System Inc. All rights reserved Cisco Confidential 4

Ø 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 © 2017 Cisco System Inc. All rights reserved Cisco Confidential 5

• 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 © 2017 Cisco System Inc. All rights reserved Cisco Confidential 6

. © 2017 Cisco System Inc. All rights reserved Cisco Confidential 7

ISO Name Ø With Unity Connection 12. 0 and later, the new name of ISO is: UCSInstall_CUC_12. 0. 1. 10000 -X. sgn. iso Build Number Ø FCS Build: 12. 0. 1. 10000 -X Ø ES Build: Need to be decided Ø SU Build: Need to be decided © 2017 Cisco System Inc. All rights reserved Cisco Confidential 8

. © 2017 Cisco System Inc. All rights reserved Cisco Confidential 9

• 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. © 2017 Cisco System Inc. All rights reserved Cisco Confidential 10

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 12. 0. 0. 97000 -67 On CDETs, check the Integrated-releases section for Connection build. If Connection build 12. 0. 0. 97000 -67 or below appears, it means defect is fixed in build © 2017 Cisco System Inc. All rights reserved Cisco Confidential 11

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 © 2017 Cisco System Inc. All rights reserved Cisco Confidential 12

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 12. 0. 0. 98000 -444 and Unity Connection build version is 12. 0. 0. 97000 -67 • Login to Unity Connection via CLI • Run command: show vos version Ø If active version is 12. 0. 0. 98000 -444 or above, it means defect is fixed in Unity Connection build. Ø If active version is 12. 0. 0. 98000 -443 or below, it means defect is not fixed in Unity Connection build. © 2017 Cisco System Inc. All rights reserved Cisco Confidential 13

. © 2017 Cisco System Inc. All rights reserved Cisco Confidential 14

Ø On fresh installation only “Cisco Unity Connection” appears as product deployment on v. Sphere console Ø Installation can be performed from PCD, AFG or other supported tools. © 2017 Cisco System Inc. All rights reserved Cisco Confidential 15

Ø To support upgrade from previous release to 12. 0, following COP files need to be installed : Upgrade Path COP File installation before Upgrade version 8. 5 or lower ciscocm. refresh_upgrade_v 1. 5. cop. sgn ciscocm. cuc_upgrade_12_0. cop version 9. x, 10. x, 11. x ciscocm. cuc_upgrade_12_0. cop version 12. x None Ø Upgrade can be performed from PCD, AFG, CLI, Cisco OS Administrator page or other supported tools. © 2017 Cisco System Inc. All rights reserved Cisco Confidential 16

• Install, Upgrade and Maintenance Guide for Cisco Unity Connection Release 12. x : https: //www. cisco. com/c/en/us/td/docs/voice_ip_comm/connection/12 x/i nstall_upgrade/guide/b_12 xcuciumg. html © 2017 Cisco System Inc. All rights reserved Cisco Confidential 17

Thank you. © 2017 Cisco System Inc. All rights reserved Cisco Confidential 18