53xx series phones died after upgrade to MiVB 8.0 SP3 PR3 3

[AH64Armament]

Just a heads up. If you have rev A.xx 53xx phones and upgrade to MiVB 8.0 SP3 PR3, they will download firmware 06.05.00.18 and will kill the phone.

I've also discovered this to be the case with an upgraded MBG to the latest version.

Causes "Fatal Exception" error and the phone will countdown and reboot.

If this happens, you will need to contact support to get your site listed on the affected product list.

The solution is to install firmware from MiVB 8.0 SP3 PR2 to the TFTP folder in the PBX. This firmware version is 06.05.00.11

Then do the following:
Set the phone to factory defaults.
Static assign ALL IPV4 info - skipping any of the following items will not work... (I've tried all combinations).
IP address - an unused IP address that's outside of the DHCP scope.
Gateway address - The Gateway IP address that matches the above IP address.
Subnet mask - match your subnet.
ICP Address - your controller's IP address
TFTP server address - set to the source that you copied the 06.05.00.11 firmware to.
TFTP server port - set to 69

Save the above settings, and restart the phone. Let it upgrade (downgrade) the firmware to 06.05.00.11 and let it come all the way up.

Now set the phone to factory defaults.

It's nuts that DHCP settings will not resolve the issue, but the above does work.

 

[sarond]

Ouch that sucks.

That could be a real PITA if you have hundreds of phones.

 

[Billz66]

good one AH gave you a star
this issue has been driving me nuts at home
- i normally have between 2 and 4 TW whilst doing customer work late at night from home
- i must have got that firmware on my test handsets because all of a sudden my older phones stopped connecting to various sites
- after your post i swapped them for some newer old phones and they havent skipped a beat

Mitel just released a knowledge base article

Document ID SO4116 Version 3.0 Status Published altered 02/08/2019
Title
Fatal Exception 2 TLB on 53xxe after upgrading to 6.5.0.18 firmware
Symptoms
5330e, 5340e reset with Fatal exception 2 TLB after sets firmware upraded to 6.5.0.18..

If I never did anything I'd never done before , I'd never do anything.....

 

[techymitel]

Root cause of the issue is option 66 on the dhcp server being set to something other than ASCII String.

Either remove option 66 if it's not needed or make sure the option is set to ASCII String.

No need to manually configure phones!

 

[AH64Armament]

hmm.. I've got another site doing the same thing... only this time I've removed options 66 and 67.
The phones here are getting almost all the way up - showing the button assignments with
GetNewSoftwareLoad
Resetting phone...
at the top of the phone.

 

[Valamagules]

@ AH64Armament - if you statically assign a phone, does it complete the boot?

Clever men learns what Wise men shares!