skip to content »

Error updating locale cisco phone

error updating locale cisco phone-6

Once you have upgraded to version 8.5(2), you can upgrade your IP Phone to version 8.5(2)SR1 or later.

error updating locale cisco phone-79error updating locale cisco phone-29error updating locale cisco phone-44

When they are booting up, the phones attempt to upgrade via TFTP to the current firmware specified in CUCM, but they fail and display "Auth Fail" on their screen.The phone should find that it needs to upgrade itself until you stop editing the file with new firmware information. After the phone gets to SCCP version 8.0.9, all you have to do is just download the version of SIP firmware you want, and then extract it into a seperate directory.Point the tftpd32 program to use that directory, copy the xml file to that directory and edit the load Information tag with the POS-xxx filename which is located in that directory and reboot the phone.The 79×1/79×2/79×5/7970 phones take a bit longer to fully complete the flashing process since they use more numerous and larger files than the 7940/60 series phones.If the phones just sit like they arent doing anything, wait a bit longer and they should come back up.Then the phones reboot and come up on the previous factory firmware load on the device. Most likely this is caused by a phone running on a firmware older than 8.5(2) being upgraded to something newer.

This is a known issue, documented in the release notes for SCCP firmware release 8.5.(2)SR1: For all SCCP firmware upgrades from firmware release versions earlier than 8.3(3) to version 8.5(2)SR1 or greater, you must first upgrade your firmware to version 8.5(2).

Upon reboot, the phone will grab an ip address from the dhcp server on the windows machine running the dhcp server.

Tftpd32 will also assign an ip address for the tftp server to the phone using option 150, and the phone should start pulling down files from the server after it obtains an ip address. If you are doing an incremental upgrade to get to version 8.0.9, just keep editing the xml file with the next version of firmware and save, then reboot the phone (after it has completed loading both the bootloader and application).

Without an auto-provisioned tftp server address, the phone will only complete half the upgrade and come up with an error message of “protocol application invalid.” This just means that the phone could not complete the second half of the upgrade and needs the tftp ip address to be specified.

Only problem is since there is no application running, there is no place to specify the address!

The phone will then wipe the flash and load whatever firmware is specified in the tftpd32 directory – if the phone just keeps downloading the term.defaults file constantly, just do an incremental upgrade to the firmware version that you want).