cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
500
Views
0
Helpful
3
Replies

7940 firmware 8.0(7) to 8.1(2) CM4.2SR3 to 7.1(3)

thomuff
Level 3
Level 3

We are upgrading from CM4.2SR3 to 7.1(3)

We have moved some test phones from the existing CM to the new CM and they have seemed to upgrade fine.

The release notes for 7940 8.1(2) firmware says that you can't upgrade directly to 8.1(2) from a release previous to 8.0(10).

TAC said that 8.0(7) was a higher release that 8.0(10) but 8.0(10) was released after 8.0(7)

We have 500 7940G phones.

The questions:    Should I be worried?    

Am I reading the release note wrong?

Is it because we are changing Call Manager?

I see the loader updated first then the application.

http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7960g_7940g/firmware/8_1_2/english/release/notes/796040_812.html

3 Replies 3

paolo bevilacqua
Hall of Fame
Hall of Fame

I have not see the RN you mentioned, indeed that is correct in my experience.

You should have a word with the manager of the TAC representive that claimed 8.0(10) predates 8.0(7).

Rob Huffman
Hall of Fame
Hall of Fame

Hi Thomas,

I would have to disagree with TAC on this one

8.0(7) was released 15-Aug-07

8.0(10) was released 21-Oct-08

8.1(1) was released 9-Feb-09

And here is the clip;

You cannot upgrade to firmware release 8.1(2)  directly from firmware release 8.0(10) or an earlier release. You have  to upgrade to firmware release 8.1(1) first, then upgrade from release  8.1(1) to release 8.1(2).

I would definitely upgrade the phones (via two-hop method) to 8.1(2) prior to your

CUCM 7.1(3) migration. You'll be happy you did

Cheers!

Rob

What I've found, is that actually you can upgrade from 8.0(10) to 8.1(1), but not from an earlier release.

In other words, you can have the intermediate step to either 8.0(10), or 8.1(1).

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: