Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Moving-Intergrating CCM/Unity 3.X cluster to 4.2 cluster

Unanswered Question
Jun 20th, 2008
User Badges:

We are working on incorporating or upgrading a 3.2 cluster to 4.2. for CCM and Unity. Can we BAT the profiles User/Devices from one to the other. Also what are some of the challenges that we may encounter.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Rob Huffman Fri, 06/20/2008 - 18:21
User Badges:
  • Super Red, 40000 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi James,

I'm just going to speak to the CCM question for now (pretty complicated) Just as an FYI CCM 4.2 has been announced as EoL (see below) I really like 4.2(3) but I just wanted you to know (you may already :)

End-of-Life Milestones and Dates for the Cisco Unified CallManager Version 4.2

End-of-Sale Date

The last date to order the product through Cisco point-of-sale mechanisms. The product is no longer for sale after this date.

May 15, 2008

Last Ship Date:

App. SW

The last-possible ship date that can be requested of Cisco and/or its contract manufacturers. Actual ship date is dependent on lead time.

August 13, 2008

End of SW Maintenance Releases Date:

App. SW

The last date that Cisco Engineering may release any final software maintenance releases or bug fixes. After this date, Cisco Engineering will no longer develop, repair, maintain, or test the product software.

May 15, 2009

End of New Service Attachment Date:

App. SW

For equipment and software that is not covered by a service-and-support contract, this is the last date to order a new service-and-support contract or add the equipment and/or software to an existing service-and-support contract.

May 15, 2009

End of Service Contract Renewal Date:

App. SW

The last date to extend or renew a service contract for the product.

August 11, 2010

Last Date of Support:

App. SW

The last date to receive service and support for the product. After this date, all support services for the product are unavailable, and the product becomes obsolete.

May 15, 2011

End-of-Life and End-of-Sale Notices


For a CCM 3.2 to CCM 4.2;

This type of upgrade uses a multi-step approach to migrate the data from CCM 3.2 to 4.2(3). There are different considerations depending on whether or not the Servers are being replaced etc.

Upgrading Your Cisco Unified CallManager Server (When You Are Not Replacing Hardware)


You cannot upgrade directly from Cisco CallManager Release 3.2 or earlier to Cisco Unified CallManager Release 4.2. If your server runs a version of Cisco CallManager Release 3.2 or earlier, you must first upgrade every server in the cluster to the latest version of Cisco CallManager Release 3.3, 4.0, or 4.1 before you can upgrade to a version of Cisco Unified CallManager Release 4.2. For information on upgrading to Cisco CallManager Release 3.3, refer to the latest version of Upgrading Cisco CallManager Release 3.3.


Note If you are upgrading from Cisco CallManager 3.3, you must use the disks from the Cisco Unified CallManager 4.2(3) software kit.


If all you want from the 3.2 database is the phone/user info, you may be able to use the BAT Export from 3.2 and then BAT Import on 4.2. Be careful with the actual BAT format between versions as they will not match exactly for sure. With some tweaking this would probably work. Try some example Export/Imports to fine tune the .csv or BAT.xlt details before going for the lot.

Hope this helps!



This Discussion