>From my testing with the linksys ata's they only accept an ip address of the tftp server in the option 66 reply. I've tried using both the full provisioning url and just the fqdn of the tftp server in the option 66 without any luck though. After the ata gets its lease the ata then connects to option66 tftp server and requests /spa2102.cfg. The spa2102.cfg tells the ata to set the profile_rule to the actual config file and resync the config after a few seconds.
I've pre-provisioned hundreds of spa2102's using this method. I also provision defaulted/factory Polycom, Grandstream, and Panasonic phones using the same option66 values. >From the linksys provisioning document: TFTP TFTP is convenient for managing small deployments of IP Telephony Devices within an office LAN environment. It is also useful for in-house preprovisioning of IP Telephony Devices in preparation for remote deployment. However, once deployed remotely, HTTP offers greater provisioning reliability, given NAT and router protection mechanisms. The IP Telephony Device is able to obtain a TFTP server IP address directly from the DHCP server through DHCP option 66. If this is done, a Profile_Rule need be configured only with the profile filepath on that TFTP server. The Profile_Rule provided with the factory default configuration is as follows: /device.cfg For example, on a SPA962, the filename is spa962.cfg. The device resyncs to this file on the local TFTP server, if that is specified via DHCP option 66. Note that the specified filepath is relative to the TFTP server virtual root directory. Gerard On Tue, May 3, 2011 at 10:46 PM, Josh Luthman <[email protected]> wrote: > I don't think that's necessary as I wasn't required to do that with MT or > dhcpd. Is it for text URLs? > On May 3, 2011 9:53 PM, "Gerard Dupont" <[email protected]> wrote: >> You have to convert it into hex.. The line below should work. You need >> to add the option to your network. Then you will then need to put the >> attached file in /usr/local/NetSapiens/ndp/frm >> on your ndp server. If you don't host your own ndp server you will >> need to run your own separate tftp to serve up the spa2102.cfg file. >> >> /ip dhcp-server option >> add code=66 name=option66 value=0x36362e3138352e3136372e3131350d0a >> >> Gerard >> >> >> >> >> On Tue, May 3, 2011 at 7:22 PM, Dave Crim <[email protected]> wrote: >>> I'm trying to get my router to advertise Option 66, but maybe I'm doing >>> something wrong. I need to advertise >>> http://prov.rapidwave.net/cfg/spa$MA.cfg for my Linksys ATA devices. >>> >>> When an ATA requests this option, my log shows "Unknown(66)" with a >>> bunch of hex after it. I've tried this with the URL above, and I have >>> also tried converting that URL to hex. When I converted to hex, the log >>> did show that value being offered to the device, but I don't think the >>> device can understand it in that form. I also tried just an IP address, >>> and it the ATAs still won't accept the option. >>> >>> >>> >>> Any ideas? >>> >>> -------------- next part -------------- >>> An HTML attachment was scrubbed... >>> URL: < > http://www.butchevans.com/pipermail/mikrotik/attachments/20110503/d369eaa1/attachment.html >> >>> _______________________________________________ >>> Mikrotik mailing list >>> [email protected] >>> http://www.butchevans.com/mailman/listinfo/mikrotik >>> >>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik > RouterOS >>> >> -------------- next part -------------- >> A non-text attachment was scrubbed... >> Name: spa2102.cfg >> Type: application/octet-stream >> Size: 179 bytes >> Desc: not available >> URL: < > http://www.butchevans.com/pipermail/mikrotik/attachments/20110503/3f79628f/attachment.obj >> >> _______________________________________________ >> Mikrotik mailing list >> [email protected] >> http://www.butchevans.com/mailman/listinfo/mikrotik >> >> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik > RouterOS > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://www.butchevans.com/pipermail/mikrotik/attachments/20110503/5b8f80a9/attachment.html> > _______________________________________________ > Mikrotik mailing list > [email protected] > http://www.butchevans.com/mailman/listinfo/mikrotik > > Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS > _______________________________________________ Mikrotik mailing list [email protected] http://www.butchevans.com/mailman/listinfo/mikrotik Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
