Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Mitel 5330 Option 128 Missing

Status
Not open for further replies.

woter324

Technical User
Jan 26, 2007
179
GB
Hi,

Over the weekend, we closed down an old site. They had a 3300LX controller with a bunch of 5330 handsets. As these handsets look nicer with the LCD panel, I attempted to swap it with my Mitel 5224 handset back at HQ where we have another 3300LX controler.

But as the topic suggests, I get an error during boot up:
Code:
DHCP: Discovery
Option 128 missing

I have tried with four different devices, all with the same error.

The 3300 is the DHCP server, and Option 128 is 100% set (otherwise my old 5224 wouldn't work)

I read about performing a Hard Reset. Now the only way I have found of doing a factory reset is:

1. Power off phone
2. Power on phone pressing both up and down arrow keys
3. For No, #, #, #
4. For yes to Tools and Features, *
5. Erase Pin #=No
6. Edit 8021X Settings #=No
7. Edit LLDP settings #=No
8. Ping Test? #=No
9. DHCP Trace? #=No
10. HTML Apps Config? #=No
11. Port Options? #=No
12. Diagnostics? #=No
13. Restore Defaults? *=Yes
14. Confim? *=Yes

Please wait...

And... no difference.

When we buy 5212's, 5312, 5224 we plug them in, straight from the box without any manual configuration.

One thing that I feel should be mentioned, is that the old site that's been closed down was confirgured three years ago by a different company to the HQ system, even though they are the same hardware.

Could there be anything on the phone that I need to reset?

As all our other Mitel phone models work out the box, I wonder if the firmware is too old to recognise HQ's 3300. Could this be possible, and if so how do I force an upgrade of firmware?

Any ideas pointers etc would be gratefully received.

Many thanks

Woter
 
You could setup option 125 for those phone's
They should work with the older options but i prefer 125


RTFM.gif



ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
Hi Tlpeter,

Just to clarrify, you are suggesting I add an aditional option 125 pointing to the TFTP server?

I've just had a look at HQ's 3300 and this is what we have under DHCP options:

Code:
  3  Router  192.168.xxx.1  IP Address  Global    3  
  3  Router  192.168.291.1  IP Address  Subnet: 192_168_191_0_Subnet (192.168.xxx.0)    3  
  3  Router  192.168.292.1  IP Address  Subnet: 192_168_192_0_Subnet (192.168.xxx.0)    3  
  3  Router  192.168.193.1  IP Address  Subnet: 192_168_193_0_Subnet (192.168.xxx.0)    3  
  3  Router  192.168.194.1  IP Address  Subnet: 192_168_194_0_Subnet (192.168.xxx.0)    3  
  3  Router  192.168.195.1  IP Address  Subnet: 192_168_195_0_Subnet (192.168.xxx.0)    3  
  3  Router  192.168.196.1  IP Address  Subnet: 192_168_196_0_Subnet (192.168.xxx.0)    3  
  125  Mitel  id:ipphone.mitel.com;sw_tftp=192.168.xxx.4;call_srv=192.168.xxx.xxx;dscp=46v46s26  ASCII String  Global  1027  125  
  128  TFTP Server  192.168.xxx.xxx  IP Address  Global    128  
  129  Call Server  192.168.xxx.xxx  IP Address  Global    129  
  130  IP Phone Identifier  MITEL IP PHONE  ASCII String  Global    130  
  134  DSCP  46

As you can see, both 128 and 125 options are set.

Any other ideas?

Thanks again.
 
It should pickup 125 then and skip the rest
Something is wrong
Try factory default the phone again


RTFM.gif



ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
Fixed it. Well kind of. I had a thought that maybe there was a setting somewhere that was stopping it downloading the correct firmware, so I plugged it into the 3300 controller. It downloaded a new flash, put it back on the proper network and it now works.

I will ask our telephone engineer why this is when he gets back from Japan!

Thanks
 
My best guess is that you are using VLAN'ing and you do not have option 132 and 133 set.

Connecting directly to the controller would skip this step.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top