MS Server 2012 - DHCP Option 125

[bptbm]

We have used the Helper files from Mitel to setup the Option 125/43 on the Win2012 R2 server. The phone (53xx series) boots up and when getting to the TFTP Main it stays there for a bit, then gets a TFTP error and it continues to boot, until it says "Contacting Server".

Any ideas of what is missing in the DHCP string? The DHCP string mirrors what the 3300 DHCP options states, meaning the "ICP and TFTP are the same address (3300 vMCD), but the phones do not come up without adding the TFTP address in the manual config of the phone.

Have we missed something in our programming?

 

[kwbMitel]

Are you using a vlan and if so are you setting the vlan in decimal or hex? (only an issue if the vlan is greater than 9)

When you say "The DHCP string mirrors what the 3300", I am concerned because the DHCP would be programmed as an array not a string and would not be a mirror at all.

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

 

[bptbm]

This site is using VLAN 2 for it's Voice VLAN, so according to your comments, that wouldn't be a problem? As to the DHCP Options Config Helper that I provided them, they seem to be doing a shortcut or workaround in their minds, not wishing to use the Helper as it would take too much time to do (that the DHCP server would need a lot of programming). To verify what you replied back, the DHCP server would not have the same Mitel String (3300 providing DHCP)? They were showing me emails, between my main contact and the guy that was implementing the DHCP options on the server, with what looked like to be the string that you would see with the Mitel providing DHCP (example: the string begins with ipphone.mitel.com, with the ICP and TFTP addresses, the Vlan 2, he l2p as 6, and the DSCP as 46).

 

[kwbMitel]

Too funny.

The exact purpose of the DHCP helper is to convert the string into an array that would take FOREVER to program manually. I need to stutter their fail is so extreme f-f-f-ail

If they "Don't Want" to use option 125 in the way it works (read designed) then maybe thay can handle the old school way?

option 128 = TFTP (IP ADDRESS)
option 129 = RTC (IP ADDRESS)
option 130 = MITEL IP PHONE (string)
option 132 = VLAN (LONG)
option 133 = PRIORITY (LONG)



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

 

[bptbm]

Thanks, come to find out the particular phone had some settings in it, that were pointing it to another TFTP server. (Phones were lent to the customer for demo purposes, and they were homed to our company's ICP as Teleworker sets. After resetting the phones to "Restore Defaults" and then "Reboot", the phones are now working with the DHCP option 125, via the MS 2012 R2 Helper Document. They also was able to use the Option 43, as was mentioned in another thread on here.

Thanks kwbMitel for your help!