CUCM 7.1(3) TFTP Auth Fail

[keithknowles]

Since upgrading to CUCM 7.1.3.10000-11 any new phone plugged into the system gets an "auth fail" from the TFTP server when attempting to upgrade the firmware to the version that comes with 7.1(3). Phones that were registered prior to the upgrade work just fine. I am seeing the same behanviour on our non-production environment which is also at 7.1.3-10000-11.

Phone Firmware for 7.1(3) on 7961G set is SCCP41.8-5-2SR1S

Has anyone sle seen this behaviour before...is anyone else running 7.1(3) yet?

[aamercado]

Since this thread helped me...I wanted to share my story.

Here's my workaround on 7945 phones with "auth fail" It always failed on term45.default.loads so...

I only had 853 which wasn't working so I download 3 separate 7945 zip loads (832, 833, 852,), put it in tftp folder and via trial and error found the “right” “term45.default” load to use which was 852. I had to restart pub tftp service on each trial/error during testing.

Anyways, I was able to get all phones to 853 using the “term45.default” that came with 852. It was kinda weird as it load 852 first, reboot and load 853 next since my Device Defaults were 853. I would have thought it go straight to 853 and skip 852.

[alijames]

Hi,

Good stuff! However the above is only a partial workaround, in that it allows a new phone to be upgraded, but you have to initiate a 'Factory Reset' of the handset to start the process.

It works for all the 79xx models I have tried so far.

No response from Cisco on a fix yet via our support provider...

Cheers,

Alistair

[sebastien_michelet]

This firmware upgrade issue first appears in 8.5(2)SR1 as acknowledged in the release notes:

http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/firmware/8_5_2/english/release/notes/7900_852SR1.html#wp57602

but nobody bothered fixing it in 8.5(3) and it is still in the release notes as noted in previous post.

It would be nice to have somebody from Cisco telling us if they think the 2-step upgrade is an acceptable workaround (until all factory phones are shipped with 8.3.3 or later) or if we can expect a fix in the next firmware release.

[rutibuni]

Hi all,

My name is Rudy Tibuni and I am a product manager in IPCBU for Cisco Unified IP Phones. First, let me apologize for the issue this has created for recently purchased IP Phones. This is not something we typically do obviously, but in this case it was necessary.

First, to summarize:

The phones are currenlty shipping with 8.3(2) but must be upgraded to a firmware load greater than or equal to 8.3(3) up to a load less than or equal to 8.5(2) prior to upgrading to 8.5(3).  We realize this is an issue for new phones mostly so we are changing the default manufacturing load to be 8.3(3). The process for doing so involves testing in manufacturing as well as a control run test build.  This is being done as we speak.  The change should be in production in 2-3 weeks. For recently shipped phones, the process specified in the 8.5(3) release notes is the correct process to follow.

Why did this happen? As most of you know, Cisco firmware is signed to ensure that only Cisco-certified firmware may be loaded on our phones. It was necessary to upgrade the servers that do the signing and the loads that understand both signing keys are, not surprisingly 8.3(3) though 8.5(2). The old servers were decommissioned and no longer available so 8.5(3) only understands the new server signing keys, hence the need to upgrade first to a load that understands both keys.

[skravens0929]

I also reverted all of my default loads to the olders version I previously ran on my 4.1.3 cluster. I did this to be sure that all of my phones came back working after the upgrade. I will upgrade at a later date.

We went from 4.1.3 to 7.1.3b

[bmcghee]

Hi Rudy,

     Do you know if Cisco has a fix for this available yet?  I'm running into the same issue at a customer site and they're loking for a fix.

Thank you..

[mohammed.naviwala]

Hi Rob

any takes on this?

[nuttawut44010162]

I installed on cucm7.1.3 and got same issue with 945G

Now, I can resolve this issue.

Here are my step.

1. i download firmware 8.4(4) in ZIP format from cisco.com  (cmterm-7945_7965-sccp.8-4-4.zip)
2. extract a zip file to tftp server on my laptop. i use 3CDaemon for tftp server.
3. change the dhcp value for option 150 to tftp's ip .
4. reset the ip phone to factory default by pressing hold# and then 123456789*0# (http://www.cisco.com/en/US/products/hw/phones/ps379/products_tech_note09186a00800941bb.shtml)
5. ip phone will retrieve firmware v.8.4(4) from my laptop.
6. when downloading the modified image file finished, change the dhcp value for option 150 to cucm's ip.
7. i try to register 7945G with cucm and "Auth Fail" does not appear.

Hope this help.

Nuttawut.

[Aaron Harrison]

Hi

A quick(er) way to do this is just load the interim firmware (e.g. the contents of cmterm-7945_7965-sccp.8-4-4.zip) onto your CCM TFTP server.

When you are deploying handsets, put the firmware file name (minus the .loads extension) into the Phone Load field.

Phones will boot and upgrade to 8-4-4.

Once you have deployed all the phone you can run a BAT job to clear the Phone Load field and reset, and the phones will then upgrade to the correct release of code.

Regards

Aaron

Please rate helpful posts...

[Christian Quiroga]

Thanks friend for this... Works Perfect

[brendand05]

CallManager Build

7.1.5.33900-10

7965G IP Phone 'Auth Fail'

I have a 7965G phone that was displaying 'Auth Fail' when booting up and wouldnt update the firmware.

It would then boot up and the phone would work but it just wouldnt update the firmware to the CallManager version.

A suggestion on the Cisco Support Forums was to reset the phone by pressing '0123456789*0#'

I have done this but now the phone is not booting at all. It just cycles through the boot process below

The phone now reboots to 'Upgrading'

Then displays 'term65.defaults'....'Auth Fail'

Then displays 'term65.defaults'....'Auth Fail' (does this twice

Then displays a Cisco logo for 1-2 minutes then reboots and goes through the same cycle.

[keanej]

More than likely you have a phone shipped with a firmware cert issue - or else the default path points to something that doesnt exist.

You need to load two firmwares onto call manager.

One is called -  cmterm-7945_7965-sccp.8-5-2

This contains the following files - you need to upload them onto the tftp server (probably your publisher)

apps45.8-5-2TH1-9.sbn

cnu45.8-5-2TH1-9.sbn

cvm45sccp.8-5-2TH1-9.sbn

dsp45.8-5-2TH1-9.sbn

jar45sccp.8-5-2TH1-9.sbn

SCCP45.8-5-2S.loads

Please do NOT upload these files !!

term45.default.loads

term65.default.loads

The other is called  - cmterm-7945_7965-sccp.9-2-1

Its contains -

apps45.9-2-1ES4.sbn

cnu45.9-2-1ES4.sbn

cvm45sccp.9-2-1ES4.sbn

dsp45.9-2-1ES4.sbn

jar45sccp.9-2-1ES4.sbn

SCCP45.9-2-1SR2S.loads

Please do NOT upload these files !!

term45.default.loads

term65.default.loads

Now goto

CMADMIN - Device / Device Settings / Device Defaults

Change your Cisco 7965 to be

SCCP45.8-5-2S  (it would have been term65.default.loads)

Now finally goto serviceability

Tools / Control Center - Features Services / Select your TFTP server and GO / Check Cisco Tftp / Press restart on top.

Now you have uploaded the TFTP files and restarted the TFTP service.

reboot the phone .. it will rebuild

Now you need to upgrade the handset to the latest and greatest.

CMADMIN - Device / Device Settings / Device Defaults

Change your Cisco 7965 to be

SCCP45.9-2-1SR2S  (it would have been SCCP45.8-5-2S)

And reboot your phone.

Your 7965 should be at 9-2-1 now.