T46G and Server 2012 DHCP Policy

[engine411]

We are still having trouble. 3CX support has helped me narrow the issue down to something with our custom template. So I am thinking perhaps another approach is in order.

To refresh my issue, the problem is that when the T46G's get a DHCP IP in the 10. range, they cannot register with the PBX. When they have an address in the 192. range, all is good.

Idea #1 - So what I'd like to do is figure out how to have a 2nd DHCP scope in Windows Server 2012r2 that gives out 192. addresses only to the Yealink phones. Can someone help with how to do that? I've tried making a scope that serves addresses only to MAC's that begin with 001565, but that didn't work. I mean, none of the phones got a 192. address.

I'm new to DHCP in Server 2012r2, so any suggestions for how to accomplish this would be valued!

In the screenshot, I am not sure what the Values (In hex) should be. Does that mean 001565* (which has the wildcard appended)?

What about using a Client Identifier? What is that for Yealink phones?

Idea #2 - Also, I am wondering if I have the Option 66 string entered correctly. Perhaps that's why the phones can't register. In the Windows dialog, should this string: http://192.168.3.200:5000/provisioning/<CustomFolderName> have quotation marks around it, like this: "http://192.168.3.200:5000/provisioning/<CustomFolderName>" ?