Thanks Lonnie Yep I knew about 1) and 2).
Actually I have gone down a different path of provisioning which there is no turning back now. I use the SPA500 series phones (and previously Aastra) which come straight out of the box and are plugged in. They auto register and present an XML login which writes the MAC -> Extension pairing to astdb and presents the config to the phone via HTTP on the fly. No collecting MAC Addresses. TFTP is only used for the initial profile rule collection however from what I am reading (and you pointed out), it looks like I can actually put an HTTP URL in Option 66. If this works, I will be kicking myself that I didn’t know this before. All these issues will go away then! I also like the idea of changing the provisioning URL’s based on MAC address in dnsmasq.static. That removes the interim TFTP step if you use different phone types. Thanks for the info. Regards Michael Knill On 25 Oct 2014, at 1:05 am, Lonnie Abelbeck <[email protected]> wrote: Hi Michael, The dnsmasq options can be confusing. To make sure we are on the the page, the dnsmasq.conf is something the web interface generates and you do not edit, and the dnsmasq.static is something you can edit. A few points the may help: 1) dnsmasq acts as the TFTP server (if enabled). By default the TFTP server is available for any interface with DHCP enabled and binds to each DHCP interface's IP address. 2) Starting with AstLinux 1.1.4, dnsmasq added an option to allow the TFTP server on interfaces other than DHCP enabled interfaces, that is done via dnsmasq.static and "enable-tftp" and a list of interface names, for example: -- enable-tftp=eth1,eth2,eth3 -- or -- enable-tftp=eth* -- Given that, why are you still using TFTP ? :-) It would seem HTTP/HTTPS might be a better choice... In the SVN we just added this to the default dnsmasq.static file for added information: -- ## IP Phone Provisioning ## More Info: http://doc.astlinux.org/userdoc:tt_ip_phone_provisioning ## Yealink HTTPS provisioning #dhcp-mac=set:yealink,00:15:65:*:*:* #dhcp-option=tag:yealink,option:tftp-server,"https://pbx/phoneprov/yealink/"; ## SNOM HTTPS provisioning #dhcp-mac=set:snom,00:04:13:*:*:* #dhcp-option=tag:snom,option:tftp-server,"https://pbx/phoneprov/snom/"; -- Which makes another point... 3) The dnsmasq.static file may define the: dhcp-option=option:tftp-server,"..." which can be set to a URL the IP Phone will use for it's provisioning rather than the default TFTP server IPv4 address. 4) When configuring dnsmasq.static, a handy CLI utility in AstLinux is "dhcpdump <-i interface> [-h macaddress]" to monitor what is going on. And finally, consider using the new'ish "PhoneProv Tab" feature of AstLinux: http://doc.astlinux.org/userdoc:tt_ip_phoneprov_howto Lonnie On Oct 24, 2014, at 3:44 AM, Michael Knill <[email protected]> wrote: > Hi group > > Could someone please let me know how the TFTP Server address is determined. > > My standard build uses VLAN’s and on LAN2 DNS/DHCP is configured where LAN1 > has just DNS. > The TFTP server is given as an IP Address in dnsmasq.conf > > If however I don’t have a Voice VLAN and everything is on LAN1 with DNS/DHCP > then the TFTP Server address is the hostname. > Why is it different? It makes it messy if the interface is not the DNS server > for the network. > > Obviously not a big one as I can adjust in dnsmasq.static, I was just > wondering why! > > Regards > Michael Knill ------------------------------------------------------------------------------ _______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [email protected]. ------------------------------------------------------------------------------ _______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [email protected].
