5320e DHCP timeout?

[Microfiche]

Hopefully I haven't bricked the refurb phone I just bought...
Set up the phone as a 5320e in the system and set the MAC address (replacing old 5312 phone)
Plugged the phone into the switch and got an exception error, so I reset the phone to factory defaults.
Plugged in again and got same error, so I erased the main load, which worked on another 5312 I was having issues with before.
No errors now, but it is now timing out trying to reach the DHCP server?
I can get a DHCP address on other devices plugged into same switch, including a 6920 plugged into same switch.
Is there something different about the 5320e series?
Not using VLAN, Windows Server 2012 DHCP server.
Any help appreciated!

[Microfiche]

Just to check, I plugged in another of the phones - got same error after plugging in (see attached)
Before the error phone was displaying "contacting RCS" - which is what was happening with the 5312 that was fixed by erasing the main load.

Boot version coming up is 5.01.00.17
Our 3300 running MiVoice Business 9.0.1.23

[johnp]

Try putting it in teleworker mode and see if will upgrade the firmware

[acejavelin]

Wait... So the new and old phone are both doing the exact same issue? Does a working phone plugged into that switch port boot up, and does this phone boot up on a different port?

You stated the old phone was a 5312 and the new one is a 5320e, did you change the set type in the MiVB controller for that user?

[Microfiche]

Sorry - I bought 3 refurbished 5320e's - 2 of them do the same thing, didn't try the third.
The first one I tried factory reset after I got the error in my second post, and then erased the main load.
It now just times out trying to find DHCP.
The second 5320e I just tried to see if I would get the same error as I did on the first one - which I did (in the picture)
A 5312 boots up fine in that port, as does a 6920.
I did change the set type in the MiVB controller when I updated the MAC address.

I am guessing I can't boot the one I erased into Teleworker, if I hold in the 7 and boot the second one, that should boot into Teleworker?

[acejavelin]

Sorry - I bought 3 refurbished 5320e's - 2 of them do the same thing, didn't try the third.
The first one I tried factory reset after I got the error in my second post, and then erased the main load.
It now just times out trying to find DHCP.
The second 5320e I just tried to see if I would get the same error as I did on the first one - which I did (in the picture)
A 5312 boots up fine in that port, as does a 6920.
I did change the set type in the MiVB controller when I updated the MAC address.

I am guessing I can't boot the one I erased into Teleworker, if I hold in the 7 and boot the second one, that should boot into Teleworker?

DHCP is a pretty simple thing... What is the exact error message? Do you have the correct VLAN set in the phone if required? What if you put it in Teleworker mode (hold 7 and enter the IP address of the ICP)?

[Microfiche]

Yeah - that is why I am finding this weird, not sure why it can't see or negotiate with the DHCP server.
I took the second phone (with the main load intact) and set it into Teleworker mode and pointed it at the 3300
It updated the firmware.
Rebooted, deleted the Teleworker info and rebooted again.
Still seems to be having issues negotiating with the DHCP server.
There are at least 50 IP addresses available. No VLAN.
I made an animated GIF - hopefully this is viewable.

[Microfiche]

Plugged the 2nd phone in again and did a DHCP trace and it said it had an IP address? Pinged the 3300 no problem.
So I pulled out the 3rd refurbished phone and plugged it in.
Reset to defaults.
It does pick up an IP address - it goes to discovery, then contacting RCS, and then I get the fatal exception (see previous attachment)
I looked in the DHCP leases and found that they are all getting assigned IPs - despite the phone displays that are saying DHCP is timing out.
Then they are going into contacting RCS and then crashing.
Sorry - I assumed DHCP time out meant they were not getting to the DHCP server...

[x-man]

Put option 128,129 and 130 in to the DHCP server and it should negotiate and then run from option 125 or the other one.

[acejavelin]

1) Unplug the phone
2) Hold "7" button
3) Plug in phone, continuing to hold the "7" button until the display says "CONFIG TELEWORKER", then press "*" for Yes
4) At the "DELETE/NEW SETTINGS?" prompt, press "#" for New
5) At the "IP ADDRESS TYPE:" prompt, press "*" for IPV4
6) At the "TELEWORKER GATEWAY:" prompt, enter the IP address of the Mitel server. For example, if it is 192.168.10.10, enter "192168010010" or "19216810#10#". STAR is backup, # is "." if less than 3 digits in the octet.
7) Press "VOL DN" button
8 ) At "STORE CHANGES?" prompt, select "*" for YES

The phone should reboot and come online.

This process will cause the phone to ignore any Mitel specific options (which appear to not be setup) and contact the system directly after getting base DHCP information.

[Microfiche]

Put option 128,129 and 130 in to the DHCP server and it should negotiate and then run from option 125 or the other one.

  Thank you! That did it! All 3 phones (including the wiped one) worked immediately once those options were set.

From what I have read, now that they are updated, I should be clearing those options because they were reclassed to public at some point? Or does it not really matter?

I had already updated one phone by enabling teleworker, but it still would not work until I set those options in DHCP.

[x-man]

I always cleared the options just to make sure that the phones worked OK just in case IYSWIM. Its easy enough to put them back in if needed to do the same again.