+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: T4x Series (/forumdisplay.php?fid=31)
+--- Thread: Deliver DHCPv6-Option with autoprovisioning server IP to phone (/showthread.php?tid=1656)
Pages: 1 2
Deliver DHCPv6-Option with autoprovisioning server IP to phone - GeorgSchwarz - 04-28-2014 06:15 AM
I have been infiormed by Yealink that as of now there is no equivalent to DHCPv4 option 66. We would need the phone to honor an option containing the Autoprovisioning server IP address.
Is it planned to be iomplemented? If yes by when?
RE: Deliver DHCPv6-Option with autoprovisioning server IP to phone - Yealink Support - 04-28-2014 11:24 AM
You can filll your option 66 in "Custom Option(128~254)" .Go to the webpage->Settings->Auto Provision, fill your custom option.
RE: Deliver DHCPv6-Option with autoprovisioning server IP to phone - bluefifa - 05-27-2014 02:46 PM
Reference，thanks
RE: Deliver DHCPv6-Option with autoprovisioning server IP to phone - GeorgSchwarz - 05-28-2014 10:02 AM
(04-28-2014 11:24 AM)Yealink Support Wrote: You can filll your option 66 in "Custom Option(128~254)" .Go to the webpage->Settings->Auto Provision, fill your custom option.
Hi!
Thanks for your effort. Due to other problems we only got around to test it now. What i can see from wireshark is that the phone does not request the option and therefore the DHCP server does not deliver it. (See attachment)
The option number has been set to 150 on the phone
Test phone was a T46G v28.72.0.25, DHCP server is isc-dhcpd-4.2.5...
Maybe you tell us which DHCP-Server Yealink uses for testing its IPv6 deployment so that we can try to figure it out
TIA
best,
George
RE: Deliver DHCPv6-Option with autoprovisioning server IP to phone - Yealink Support - 06-03-2014 10:47 AM
Do you auto provisioning phone by other methods too?
When a Yealink phone boots it will try and obtain a provisioning server address in the following order.
If RPS is enabled, then:
Yealink RPS
Zero -Touch
PnP Server
DHCP custom option
DHCP option 66
DHCP option 43
Phone Flash（TFTP/FTP/HTTP/HTTPS）
RE: Deliver DHCPv6-Option with autoprovisioning server IP to phone - GeorgSchwarz - 06-03-2014 12:25 PM
(06-03-2014 10:47 AM)Yealink Support Wrote: Do you auto provisioning phone by other methods too?
Hi, Thanks for answering
No, currently not. We are trying to port our existing environment to an IPv6-only network solution.
With IPv4 we were using DCHPv4 Option 66 for a zero-touch autoprovisioninng over TFTP and we are looking for a suitable IPv6/DHCP equivalent that allows us to have some kind of zero-touch autoprovisioning... (apart from setting the phone to IPv6 DHCP initially)
Would any of the ways mentioned by you give us zero-touch Autoprovisioning on IPv6? (The network is a private IPv6-only network not connected to the internet)
My problem mainly is how to get the information where to find autoprovisioning data to the phone...
From what I've figured out so far, setting the Autptovisioning server manually to something like tftp://[2008:db8:caffe::1] works like a charm, just delivering that option via DHCPv6 is a bit of a catch...
Cheers,
George
RE: Deliver DHCPv6-Option with autoprovisioning server IP to phone - Yealink Support - 06-03-2014 02:56 PM
Hi George ,
Please send trace to support@yealink.com or your technical specialist.
How to Get the Correct Syslog, Config.bin and Trace
RE: Deliver DHCPv6-Option with autoprovisioning server IP to phone - GeorgSchwarz - 06-11-2014 08:01 PM
Hi!
As always, thanks for your support. We have now added the issue to our open case that we have running over our distributor. In order not to do things twice, we'll leave it there, so that we do not cause you guys at Yealink additional work....
Cheers,
George
RE: Deliver DHCPv6-Option with autoprovisioning server IP to phone - Yealink Support - 06-12-2014 08:39 AM
Thanks for your understanding and sorry again for the inconvenience.
RE: Deliver DHCPv6-Option with autoprovisioning server IP to phone - FSchulz - 09-10-2014 09:28 PM
Something new here? Got the same issue ...