Mitel phones 5320e DHCP Issue

[cgashlin01]

So I am implementing vlans and am testing currently.

I am moving my DHCP server to something else(Windows 2012).

Issue.....

Phone boots and says that option 129 is missing. even though I have it in my DHCP scope as an option that is set as IP address and have it set to my phone system.


Any idea?

[cgashlin01]

I will add that I have it setup in my switch for DHCP helper. It works iwth a PC no problem.

[Tech Electronics]

cgashlin01,

Why don't use just use the DHCP server in the 5000? What we would be looking for those is option 125 or 43 though.

Thanks,

TE

[johnp]

If you have access to the option 125 config tool it would be helpful. What DCHP server are you using? The process the phone goes through on boot is to use lldp, if unavailable use dchp to learned vlan, priority, phone system address and dscp values.

Generally the first dhcp request is on the untagged default vlan, the dhcp sever would have the necessary info and after the phone learns where it go it releases that lease. Then sends out a new vlan tagged one.

The tool creates both an ascii and hex representation of option 125.

The phone will also respond to option 43 as well as the old Mitel 128, 129, 130, 132, 133, 134 values (I may have some wrong numbers) but this is a quick overview from memory.

The 125 hex string starts with the mitel vendor code followed by a lenght of string value the the hex representation of ipphone.mitel.com;tftp_srv;call_srv,l2p and other values. These all get done by the tool. You may be able to look in you system to see the true format.

If using 43 you don't need the vendor id or string length values.

[cgashlin01]

I am new to this MItel system. SO I am unware of option 125 config tool.

I am using Server 2012 DHCP Server

[Tech Electronics]

cgashlin01,

Does your switches support LLDP-MED or CDP?

Thanks,

TE

[johnp]

Found this string online

"id:ipphone.mitel.com;sw_tftp=192.168.11.10;call_srv=192.168.11.1;vlan=11;l2p=1v6s6;dscp=46v46s26;"

You could modify and use for option 43 type ascii string

sw_tftp and call_srv usually is the phones sytem, vlan would the phone vlan, l2p(layer 2 priority) (default value)v(voice value)s(signalling value) same scheme for dscp

[cgashlin01]

my vlans are untagged so it should not care about the vlan. Should this be the only option in my DHCP?

[cgashlin01]

My switch does support LLDP

[cgashlin01]

I tried LLDP and it still says option 129 missing.

My vlans are untagged.

[cgashlin01]

Using option 43:43 is all it says on the phone when i use option 43 but it does not work. Just sits there.

[johnp]

LLDP-MED support?

The recommended switch configuration of wanting to use the port on the back of the phone for the data vlan would be to configure the phone ports as untagged in data and tagged in voice. dchp server port only in data untagged, phone system only invoice untagged or tagged depending on system. some type of routing between the 2 wheter is be separate interfaces where one is only one data and the other only on voice or router on a stick where both are on the same interface and the connected port would be the same as a phone port.

You then can setup the qos queues to prioritize the voice traffic.

[cgashlin01]

Its an SG300 layer 3 switch.

[Tech Electronics]

cgashlin01,

Sorry I had to step away for a bit.

So LLDP-MED or CDP is used in order to get the phones on the right VLAN as they boot up. The command most switches use for this is the word "voice" under the Voice Vlan. This will provide the phone with the VLAN ID and its L2P [Layer 2 Priority].

As JohnP stated the ports the phones are in should be untagged for the native VLAN, which is normally data, and tagged for the voice VLAN. The port the phone system should be in should be untagged for the voice VLAN and depending on the switch No Untagged for the Data VLAN. That way no native VLAN traffic will be mistakenly sent to the 5000. So, when the phones come up they get their VLAN ID and then send out their DHCP request on the Voice VLAN and the only thing that will respond to them is the 5000. To make things better if you don't remove the flag  from Client's Vendor Class ID Must Match Name for the DHCP Server Range on the 5000 then even if a PC were to send a request it would be ignored.

Thanks,

TE

[johnp]

My comment about tagged or untagged for the phone system was the 3300 can be set to operated with a tagged value