How to Upgrade CUCM 7.1.3 to 8.6 to a new server


Sep 4, 2012 5:13 AM
Sep 4th, 2012

There are two methods to do the Upgrade

Method 1

When trying to upgrade from CUCM 7.1.3 to 8.6 the following steps need to be considered if you are having a new server.

  • Install CUCM 7.1.3 in the new server
  • restore since  you need to consider the following before you restore Cisco Unified Communications Manager, ensure that the  Cisco  Unified Communications Manager version that is installed on the  server  matches the version of the backup file that you want to restore.  The Disaster Recovery System supports only matching versions of Cisco  Unified Communications Manager for restore. For example, the Disaster  Recovery System does not allow a restore from version 7.0(1).1000-1 to  version 7.1(2).1000-1, or from version 7.1(2).1000-1 to version  7.1(2).1000-2.  (The last parts of the version number change when you  install a service  release or an engineering special.) In essence, the  product version  needs to match, end-to-end, for the Disaster Recovery  System to run a successful Cisco Unified Communications Manager database  restore. Disaster Recovery System adheres to strict version checking  and allows restore only between matching versions of Cisco Unified  Communications Manager.
  • After restoring the CUCM 7.1.3 to the new server do upgrade for version 8.6

Method 2

When there is a hardware migration  use the Bulk   Import feature in BAT to provision the entire system.

  • Handle the stations/user using BAT to export data and    formulas/macros in a spreadsheet to normalize them to the new record    format.
  • Import End User (unless LDAP sync [via DirSync] is  leveraged.
  • Import the Phones (All-Details).
  • Run a  user update to  bring in the rest of the user attributes (this is needed  whether you  use DirSync or not)

This method is faster than   installing software, using DRS, and then doing a restore.

Problem :- CallManager 6.x to 8.x Migration BAT Issue

While migrating between Callmanager 6.x and 8.x, for UDPs in particular, you are  experiencing errors importing UDP CSV files into CUCM 8.6. These UDP  CSVs have been exported directly from CUCM 6.1.

Seeing errors such as the following:

USER HOLD AUDIO SOURCE is not a supported field.

You are able to see the differences in the exported UDP CSV file headings, such as the following, which may point to the problem:

User Hold Audio Source (6.x)

User Hold MOH Audio Source (8.x)


When you import  from a CUCM 6.x server to CUCM 8.x all the  mandatory fields should be present, and that the column headers must match.

Here the issue is the headers for a number of fields have been modified between these two versions.

Perform the following steps to resolve the issue:

  • You need  to map the column headings from the CUCM 6.x output to those  which you have exported from CUCM 8.x
  • You are also required to map the device pools and other values in the spreadsheet from the existing ones to new ones
  • On top of that you need to migrate some phones to a split pair of EM  profiles and phones, or vice versa (merge an EM profile and a phone to  make one 'static configured' phone).

What  you need to do is to compare the CUCM 6.x export to a  test export from CUCM 8.x. This will help you to list the matched/changed headers, and then you need to generate a mapping file that you would then apply for further  exports from CUCM 6.x

With the remapped values you will be able to do the export to CUCM 8.x with the help of BAT.

The CUCM compatibility matrix is available here:

Related Information


Average Rating: 5 (2 ratings)


Login or Register to take actions

This Document

Posted September 4, 2012 at 5:13 AM
Comments:0 Avg. Rating:5
Views:3113 Contributors:0
Tags: upgrade, cucm_8.6

Related Content

Documents Leaderboard