Upgrading CUCM 5.1(3) to 6.1(2)

Unanswered Question
Jan 15th, 2009
User Badges:


I have an upcoming upgrade for a customer from 5.1(3) to 6.1(2) and then soon onto 6.1(3).

We have everything ready to go, except the customer is worried about the need to re-login all EM profiles. We have a LOT of phones.

Is this going to affect us? I could see how this is the case from 4.x, using DMA, but any experience welcome.



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
pradeepde Wed, 01/21/2009 - 06:44
User Badges:
  • Bronze, 100 points or more

Before Upgrade disable the Cisco Extension Mobility service. Navigate to Cisco Unified Serviceability > Tools > Service Activation. Be aware that when you deactivate the Cisco Extension Mobility service, Cisco Extension Mobility users will not be able to log in and log out of phones that support Cisco Extension Mobility.


cjhunt Wed, 01/21/2009 - 07:00
User Badges:


Thanks for your response. I'm not sure about the relevance of the 4.1 to 6.1 document you sent, as I'm doing 5.1(3) to 6.1(2).

Stopping the EM service will in my view only prevent any users changing their phone's state.

I don't see this being a problem as the phone's active profile is stored in the database, so this should be preserved, right?

FYI one of my colleagues already did a 5.1(3) to 6.1(2) upgrade this weekend and it DID NOT log out the users, so there's my answer then.


iptuser55 Thu, 01/22/2009 - 07:06
User Badges:
  • Silver, 250 points or more

I think you also need a S/W feature license to go to 6.x from 5.x

cjhunt Thu, 01/22/2009 - 07:12
User Badges:


Yes, we used the procedure for the Product Upgrade Tool to obtain this.



Naoufal KERBOUTE Mon, 02/09/2009 - 02:53
User Badges:


Can you please give some informations about the upgrade from CUCM 5.1 to 6.1.

Thank you.

cjhunt Mon, 02/09/2009 - 03:26
User Badges:

Sure, I can provide some information.

I performed the upgrade just this Saturday and it seems to have gone just fine.

Here's what we did in a nutshell:

Customer purchased the upgrade licenses (SASU contract) and we used the PUT (Product Upgrade Tool) to register these and obtain the licenses and software for the upgrade.

We registered the PAK codes using the publisher MAC address.

We were sent software for 6.1(3) with the upgrade - this is what Cisco are shipping now, not 6.1(2-x). We thus went straight to this version using the 6.1(3) upgrade disk (CUCM Upgrade 5.x to 6.1(3) media).

We did the publisher first choosing NOT to switch to the upgraded partition.

We then did the primary TFTP server in the cluster and then the subscribers.

Once we had all nodes ready, we switched partitions in the same order as above.

Monitoring was maintained using RTMT (you'll need to download the newer plugin once your 6.1(x) is running). After around 15 minutes after the final node was switched, DB Replication was good throughout the cluster.

Are there any specific things you want to know? I followed the Cisco documentation where possible and all seems to have worked just fine.


Naoufal KERBOUTE Mon, 02/09/2009 - 04:16
User Badges:

Hi chris,

Thank you a lot for your answer.

i need just some Url for cisco documentation??

best regards



This Discussion