Replacment 5212 Phones on a level 7.0 3300 do not boot up 1

[colpot]

We have a Customer whose Mitel 3300 cxi is on level 7.0.9.6_1 and we have tried to replace some faulty 5212's.
The replacement phones will not boot to the Mitel. They are statically assigned IP Address but the just hang with a blank screen.
The phones work when they are connected to another System on later software.
The Boot Load version of these phones is 02.05.00.04 and the version on the working phones is 02.01.00.04
Any ideas how we can get the replacement phones working on the level 7 system or do we need to upgrade the Mitel?


Colpot
(Remember - If it aint broke - fix it till it is.)

 

[kwbMitel]

They should at least attempt to download the bootload.

Most likely explaination is that the static assignments are wrong.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[colpot]

Thanks, but the static settings are definately the same (apart from the phone IP Address of course)

Colpot
(Remember - If it aint broke - fix it till it is.)

 

[kwbMitel]

I'm sorry to say that nothing else comes to mind.

Not to nag, but how sure are you? My scepticism meter is off the chart.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[colpot]

Ha Ha - I've had one of those weeks too - I am as sure as sure can be - 3 engineers (including me) who all had the same problem with different phones. I went to site and 2/3 phones were ok so I thought it was a faulty phone. Next engineer went with a replacement for the one I thought was faulty but that didnt work. Today we sent an engineer with 6 phones and only one of these worked.

Colpot
(Remember - If it aint broke - fix it till it is.)

 

[wireman50]

I have 5212 working on 7.0.22.5_5 system but they are DUAL mode since there is no entry for single mode sets and I believe that there are single mode sets....just a thought.

 

[colpot]

Solved by running loading the boot file on a laptop running tftp server and pointing the phones to the laptop rather than the ICP for TFTP.

Colpot
(Remember - If it aint broke - fix it till it is.)

 

[kwbMitel]

I am vaguely remembering a subtle change in the VLAN settings that was implemented around the time of your SW load.

Prior, you only had 1 field for Priority. Afterwards, you had 3.

With phones that were statically assigned prior to the change it was not necessary to set the priority.

Afterwards, it was.

Not saying this is/was the issue but at least it's a possibility.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[LoopyLou]

Good solution with running a local TFTP server on a laptop. My suggestion was going to be plug the sets directly into the controller

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[colpot]

LoopyLou - the problem occured with phones connected directly to the controller.
kwbMitel - may try playing with the settings next time we have the issue. Its strange that some sets work ok and others dont and the only difference seems to be the Boot Load version.

Colpot
(Remember - If it aint broke - fix it till it is.)

 

[LoopyLou]

When you say connected to the CXi did you mean via the L2 ports? I meant using a power brick and the LAN port.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[wireman50]

Wonder if its a DNS issue.....?

 

[LoopyLou]

Do the phones need DNS to boot?

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[ChrisMitel]

Hi,

It was a corrupt firmware issue on the 3300. The file the 5212 downloads and uses is BootIP5220Dpl_00.bin. This was first taken off the 3300 and tried locally and failed.

We then used a fresh file taken from downloaded version 7 software (run the software exe file extract the files and unzip tftp_ip.tar) used this locally and it worked. Replaced the old file in the 3300 for future use.

Regards

 

[wireman50]

Dunno if they need a DNS to boot but I vaguely remember that the issue with them taking a long time to boot was DNS related...IIRC.

Anyway its solved now so we know the reason.