5410 Will Not Upgrade

[sgrossman]

Hello All,

I am working with an IP 500v1 version 8.0(66). The customer has a 5410 that will not upgrade. When the phone is plugged in it says "Waiting for Firmware Download" and then goes to "Waiting". Below is the logs I am getting.

Monitor:

UpgradeFileReader(f527f72c:6405)::Start TFTPReader rem=192.168.0.40, file=5410_R6.bin
UpgradeFileReader(f527f72c:6405)::End of File 5410_R6.bin len=67516 reason=5 error=0

In the Manager TFTP Log, it simply shows the file being sent over and over again using a port number that is incremented by 1 each time it is attempted. The phone never budges from the "Waiting" screen.

Any ideas!?!

 

[smokinjoe2938]

go to the no user source code field and add ALLOW_5410_UPGRADES THIS IS WHY IT IS NOT UPGRADING

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[sgrossman]

Already there sir.

 

[sgrossman]

Thank you for the response though.

 

[mforrence]

There was a batch of phones in 2006 or so that, if you tried to upgrade, they became bricks.

 

[sgrossman]

I am thinking it may be a bad phone. It is a very old piece of equipment from an old customer sold as refurbished. Unfortunately, the geniuses who packaged it all up didn't think to test it.

 

[Telecomboy]

Here is the bad batch of serial numbers to look for:

07N543xxxx to 08N503xxxx

See if the phone falls into that batch

 

[Westi]

if you are on R5 then just don't upgrade except if you need the language to be Chinese. That is the only difference between R5 and R6

Joe W.

FHandw, ACSS (SME), ACIS (SME)


“This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[tlpeter]

It is looking for the 6.00 version, is this available on the tftp server?


BAZINGA!

I'm not insane, my mother had me tested!

 

[sgrossman]

The R6 bin file is available on the TFTP server. I can only assume this is what the phone is looking for since the TFTP server continuously attempts to send the file.

 

[tlpeter]

The phone is requesting the file and cannot find it.


BAZINGA!

I'm not insane, my mother had me tested!

 

[sgrossman]

In looking at Wireshark traces, the server is certainly sending it. You can see it in the Monitor traces finding the file and even reading the size of the file. You can also see it in the TFTP log sending the entire file. I am thinking bad phone. I am going to have a replacement sent out. I will update the thread with findings.

 

[budbyrd]

You would also need the fw_on.bat altered and ran. Also have found R9 needs PERMIT_FORCED_DCP_DOWNLOAD in the nouser to work.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[intrigrant]

The only thing I can think of is that the file is corrupt, I have added a correct one.