DHCP Custom Option 156 not working

[RobertP]

I have added a site with and MX64 and the Shoretel IP655 VoIP phones are pulling IP addresses via DHCP as expected but not the option settings. Option 156 is the Shoretel/Mitel Connect standard and works fine at all my other sites (but they are on MPLS circuits).

Things I’ve tried:

1 - Custom option 156 configservers=172.20.50.2, ftpServers=172.20.50.2, Layer2Tagging=1, VlanId=68

2 - Custom option 150 configservers=172.20.50.2, ftpServers=172.20.50.2, Layer2Tagging=1, VlanId=68

3 - Custom option 66 configservers=172.20.50.2, ftpServers=172.20.50.2, Layer2Tagging=1, VlanId=68

4 - Custom option 66 172.20.50.2 (172.20.50.2 is the tftp server that the phones pull their config from)

The following UDP ports must be open 5440, 5441, 5443. I have no ACL's in place and is open any - any.

Thank you for any light you can bring to my situation.

[KarstenI · Accepted solution]

First do a packet-capture on the port to the phone to see if the option is present in the DHCP-answer. If it is there, look for traffic from the phone to the server.

[DarrenOC]

just to confirm, are you setting your Type as Text, IP or Hex:

[RobertP]

Yes I have set it as text.

Am currently doing a capture on the LAN.

[RobertP]

Capture shows that the phones are not answering the MX's ARP request even though I can ping the phones IP.

I will try a different model phone later today to see if it behaves any differently.

[DarrenOC]

are the phones statically assigned with their TFTP/FTP settings by any chance so aren't responding?

[RobertP]

Good question, however I did a factory reset on them to eliminate any prior stored configs.

[RobertP]

We replaced the IP655 conference phone with an IP485G and it came right up, no problems.

Bringing the IP655's back to corporate LAN to determine what their issue is.

Thank you to all who replied with help.