Roll back a phone load image - 6961

[Brendan Marmont]

Hi, I would like to roll back to an older version of firmware - SCCP 9.2.1.0 (Active Load) to SCCP 9.0.2.0 (Inactive Load)

We are using CUCM 7.3.1

Tried to manually assign the Phone Load Name on the device to "SCCP69xx.9-0-2-0" [device][phone][ext][phone load name] - After applying the phone image it reboots, however the active/inactive loads stay the same?

Where else can we look to acheive this?

Thanks in advance,

Brendan

[William Bell]

Brendan,

Where are you attempting to manually assign the phone load name? Also, what UCM platform? CUCM or CME? If CUCM, then you should be able to set the phone load at the Device Level or at the Device>Device Defaults configuration page.

HTH.

Regards,

Bill

[Brendan Marmont]

Thanks for replying, I updated the details above, CUCM 7.3.1, made the change manually on the [device][phone load name] field.

I don't want to change the device defaults as it will affect all our phones? We only updated 4 phones as a test prior to rolling it to the whole fleet. Now it has proven to have an issue we want to keep the status quo, ie the older image version.

Cheers,

Brendan

[William Bell]

Brendan,

OK. Well, if your default load (Device>Device Defaults) is already 9.0.2.0 then you only need to clear (delete/blank) the firmware parameter on the device and reset/apply configuration. If that isn't working then I recommend enabling Detailed Level tracing for TFTP and repeat your downgrade test (i.e. reset the phone). Look at the traces to ensure that the phones are requesting the new binary and to see if there are any errors.

You may also be able to pull the TFTP config file for one of the phones (using a TFTP client on your desktop) to ensure that the changes you are making are reflected in the TFTP config file. This was a problem once but shouldn't be in your CUCM version.

HTH.

Regards,

Bill

[Brendan Marmont]

Thanks Bill,

What you suggested didn't work for us (default load (Device>Device Defaults) is already 9.0.2.0 then you only need to clear (delete/blank) the firmware parameter on the device and reset/apply configuration)

I need to enable the trace settings, I have not done this before, where do I find the debug settings?

Thanks again,

Brendan

[William Bell · Accepted solution]

Brendan,

Go to the serviceability portal on your CUCM publisher. You can get to it from the admin portal by going to the Navigation box in the top-right of the admin page. Another approach is to go to https:///ccmservice. In the serviceability portal go to Trace>Configuration. Select the following:

Server - Your TFTP server

Service Group - CM Services

Service - Cisco TFTP (Active)

The trace should be on. If not, turn it on. Also set the debug level to either Significant or Detailed.

You can retrieve the trace file from RTMT (

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/service/7_1_2/rtmt/rtintro.html)

You can also retrieve trace files from the command line.

HTH.

Regards,

Bill

[Brendan Marmont]

Hi Bill,

Thats a nifty little tool, I'll have a play around in there!

Apparently once you install firmware newer than v9.0.3.0, Cisco had enabled a security feature that meant we could not roll back to a version previous to this FW release. We would unfortunately fall into this catagory.

Thanks again for your help,

Brendan

[art.tumanik]

Hi Bill,

I just hit a bug on a 6941 on CME 9.0.  FW 9.2.1 (skinny) which is recommended by Cisco breaks internal MOH between phones. I tried a fresh 6941 with the factory load of 9.0.2 - surprise, surprise, MOH works without a problem!

Now I need to figure out how to downgrade the firmware..

Do you know how to switch from Active Load (9.2.1) to Inactive Load (9.0.2) on 6941 on CME? Is it possible to do the rollback on the phone itself if I do not have the original 9.0.2?