Yealink T46G doesn't use dhcp option 66

[engin411]

Went to slap a few new Yealink T46G's into service, but they don't autoprovision.

3CX, did something change in the autoprovisioning world in SP6.1? This worked great earlier this year for the Yealinks.

I can power up a new phone but it doesn't appear in the Phones node.
3CX shows this to be the autoprovisioning URL: http://192.168.3.200:5000/provisioning/uniquefoldername
My router hands out this: dhcp-option=66,http://192.168.3.200:5000/provisioning/uniquefoldername/$MA.xml
Since the ending /$MA.xml is for a few Cisco's here, I removed it to make dhcp-option=66,http://192.168.3.200:5000/provisioning/uniquefoldername, but no joy.
I can ping 192.168.3.200.

Ideas?

 

[Pierre_3CX]

Hi there, your DHCP option 66 seems correct.
Can your windows firewal on server interfere? (try disabling)
Does the phones have a route to the PBX ? (id not, make one, phones must be able to access their template)

 

[dangmoss]

I have this problem also
Same subnet phones will not show up

Firewall is disabled on server

 

[ian.watts]

It is simple enough first to verify there will be a matching "file" which the web service will serve by browsing the Provisioning folder in your file system.
Second.. try your web browser to see if you can open an "instantiated" template.. or an instance.. config file.. it should open just fine and display the content to you in the browser.

How do I mean? Construct the URI yourself and see if it opens.. http://your.pbx.here:5000/provisioning/qwertyuiop/DEADBEEF69.xml based on whatever MAC on a handset which you have already provisioned..

If you can't open the file in the browser, the phone will never be able to open it, either. Thus, your problem may lie there.
Haven't don't a Yealink "recently" but was fairly painless. At least I didn't have to tweak ("customize") the template any to get what I wanted done.

 

[craigreilly]

I've seen some T46 firmware issues causing issues in other posts.