jameskemp

I had this when our network guys reconfigured our IP network.

It means that the phone is connecting to the Data VLAN and is getting is trying to get its DHCP from Option 125. Not sure how we fixed it here but basically you need to program Option 125 on the DHCP server to point the phone at the 3300 to get its IP.

I did have some docs on this, will try to look them up for you.

JB007

it's kind of weird...i connected the set into another netwokr node and it worked without problems???

i have checked the switch node and it is well configured, it's on the right VLAN , and everything goes ok...what else can be causing this??

OK its done...for some reason...somebody changed the port on the switch....and placed it on another vlan....i just changed the port and everythign goes ok now....tanks for your answers

jameskemp

Ah, wrong VLAN then, at least its sorted!

DPGumby

I think earlier Mitel used a couple of DHCP options that have more recently become more popular in IT circles for something else. Option 125 can now be used as a replacement should you find the other options already in use

lundah

Yes, the previous DHCP options that were used to set up the Mitel IP phones were re-allocated by a new RFC a few years ago, took Mitel a bit to get the firmware in place to play nice with the new standard.

Basically any phone that works with 6.1 and up should work either with the old DHCP options (128-133) or the new (43 or 125).

Also, if you're using an external DHCP server, I've run into issues with Windows and Linux servers not working with option 125, and having to use 43 for these configurations.

marklamond

I've managed to get option 125 working well with Netware and Windows DHCP servers, it's not exactly straight forward but if anyone needs help i can post a tutorial.

We have have pretty much standardised on 125 and removed the old options, the only gotcha is if you get an "old" 5212 etc that has been sitting around a warehouse that does not understand 125 until it upgrades its firmware.

JB007

I have again the option 125 issue......
i have this:
i had a set(a) plugged into a node (1), and it was working...i unplugged the set(a), and plugged it again...and then the option 125 message appeared.....i plugged this set(a) into another node (2), and didn't work....then i pugged another set(b) on the firs node(1) and it worked without problems...what can be causing these problem????

marklamond

Is your DHCP option 125 formatted correctly?

Do you run any form of NAC (network access control) or intruder detection / QOS on the network?

Are VLAN's set up statically or is this done dynamically with GVRP?

I strongly advise you use Wireshark to sniff what the phone is doing on the network, it can solve problems like this in seconds.