B179 firmware update fail

[formerNECguy]

Does anyone have an idea why my firmware updates are failing by looking at the following text? I was able to go from 2.3.8 to 2.4.3.4 with no problem. Now I'd like to go to 2.5.4 and I get failure every time I try. This is on at least three separate B179 conference phones. Not sure why it would say wrong phone type as the file came from the same support.avaya page. I am using the web interface. Thank you!

Running upgrade
Wed Feb 28 13:09:28 UTC 2018
Archive: /tmp/upload/KT300IP.kt
inflating: 001-phone-model_1.1.5486M_arm926.ipk
inflating: alsa-lib_1.0.15-utumno-1_arm926.ipk
inflating: bridge-utils_1.2_arm926.ipk
inflating: busybox_R2.1.15.2-avaya-5245_arm926.ipk
inflating: devmgnt_1.1.5245_arm926.ipk
inflating: dropbear_0.51-utumno-1_arm926.ipk
inflating: expat_2.0.1_arm926.ipk
inflating: glibc_2.6.1_arm926.ipk
inflating: haserl_0.9.24-utumno-1_arm926.ipk
inflating: ipkg_0.99.163-utumno-2_arm926.ipk
inflating: kernel-modules_R2.2.6.24-avaya-5245_arm926.ipk
inflating: konfsip_1.1.5486M.5193_arm926.ipk
inflating: konftelintro_1.2.5310_arm926.ipk
inflating: kt300ip-dsp-firmware_1.2.3363_arm926.ipk
inflating: kt300ip-modules_1.1.3363_arm926.ipk
inflating: kt300ip-utils_1.2.5048_arm926.ipk
inflating: libiw29_29-utumno-1_arm926.ipk
inflating: libncurses5_5.5_arm926.ipk
inflating: libstdc++_4.2.1_arm926.ipk
inflating: linux-kernel_R2.2.6.24-avaya-5245_arm926.ipk
inflating: lldpd_0.9.4-1_arm926.ipk
inflating: lua_5.1.3-utumno-2_arm926.ipk
inflating: lua-iconv_r5-utumno-1_arm926.ipk
inflating: luaxml_080218-utumno-3_arm926.ipk
inflating: mini-httpd_k01-1.23_arm926.ipk
inflating: module-init-tools-depmod_3.2.2_arm926.ipk
inflating: mtd-utils_1.0.1-utumno-1_arm926.ipk
inflating: ncurses-data_5.5-utumno-1_noarch.ipk
inflating: netplug_1.2.9.1-utumno-3_arm926.ipk
inflating: netplug_1.2.9-utumno-3_arm926.ipk
inflating: ntpdate_4.2.4p4-utumno-2_arm926.ipk
inflating: openssl-lib_1.0.2c-utumno-1_arm926.ipk
inflating: Packages
inflating: Packages.filelist
inflating: procps_3.2.7_arm926.ipk
inflating: prod-fs_1.1.5245_noarch.ipk
inflating: startup-sound_1.1-avaya-3363_arm926.ipk
inflating: udev_112-utumno-2_arm926.ipk
inflating: webif_1.1.5486M_noarch.ipk
inflating: version_2.5.0.4_arm926.ipk
inflating: wget_u-1.10.2-kt-1_arm926.ipk
inflating: vlan_1.9_arm926.ipk
inflating: wpa-supplicant_0.7.3-utumno-2_arm926.ipk
inflating: zlib_1.2.3_arm926.ipk
Downloading file:///opt/upgrade/Packages
Updated list of available packages in /usr/lib/ipkg/lists/base
Successfully terminated.
Upgrading busybox on root from R2.1.15.2-avaya-5167 to R2.1.15.2-avaya-5245...
Downloading file:///opt/upgrade/busybox_R2.1.15.2-avaya-5245_arm926.ipk
Wrong phone model detected, aborting
Terminated
2018-02-28 13:10:24
Upgrade failed (2)

 

[Okkie26]

First question. Why update?

Is something not working?

 

[Manie3]

Are you using the encrypted TLS upgrade file on a non encrypted phone?

ACSS (Manieee on a new account)

 

[TheSmash]

Suspect this has something to do with it...

"Wrong phone model detected, aborting"

ACSS (SME)

 

[Manie3]

@TheSmash That's what made me ask the question above. Same thing happened to me at C Street back in the day.

ACSS (Manieee on a new account)

 

[formerNECguy]

Thanks for the replies:
Okkie26 - 2 reasons I guess one being our IT security guy wants every piece of equipment under the roof at the latest firmware level but more importantly, problems with one of our B179s locking up periodically which was described in the firmware release notes as a known issue.

Manie3 - Actually I've tried both files thinking I had the wrong one the first time. How can I tell if my phones are encrypted or not? Being that I was able to update the firmware from 2.3.8 to 2.4.3.4 which are the non encrypted files, I will assume non encrypted.

At the start, all phones were at 2.3.2 and I tried to go to 2.5 straight away. Once this failed (wrong phone model), I stepped to 2.3.8 then 2.4.3.4 (successful) then 2.5.4 (failed). So, the upgrade process has worked but I just can't get to the latest.

Thanks again all and I appreciate your time on this.