Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

ICM and CTIOS upgrade from 8.0(2) to 8.0(3)

Hello,

I have a live duplexed UCCE system operating with version 8.0(2).

ICM components are : ProggerA, ProggerB and AW.

In order to solve some CTIOS freezing issues, I need to install patch 8.0(3). I am planning to upgrade CTIOS as well as ICM software.

Can someone advise if the below steps are accurate?

  • Shut down the services on both Proggers and AW
  • Perform the below steps on ProggerA and ProggerB
    • Backup Logger DB using Microsoft SQL Backup and Restore
    • Backup registry key "Cisco Systems, Inc. registry"
    • Apply 8.0(3) ICM software patch
    • Apply 8.0(3) CTIOS patch
  • Perform the below steps on AW
      • Backup AWDB usingMicrosoft SQL Backup and Restore
      • Backup registry key "Cisco Systems, Inc. registry"
      • Apply 8.0(3) patch
      • Start the services on both Proggers and AW
      • Apply patch for CTIOS client as well

      Any comment or advice is highly appreciated.

      Thanks,

      Justine.

      • Contact Center
      Everyone's tags (5)
      2 REPLIES
      New Member

      ICM and CTIOS upgrade from 8.0(2) to 8.0(3)

      Hey Justine,

      You are on the right track. Additionally you can also take the system state backup using NTBACKUP utility

      Thanks,

      Dass

      Please rate useful posts :)

      ICM and CTIOS upgrade from 8.0(2) to 8.0(3)

      I would not take that approach, how I would do it.

      1. Shutdown side B, side A active.

      2. Apply patch to side B, shutdown side A, bring up side B.

      3. Test side B and validate succesful installation.

      4. Apply patch to side A, bring up side A, make side A active, test.

      david

      374
      Views
      5
      Helpful
      2
      Replies
      This widget could not be displayed.