Phone Provisioning (RESOLVED)

I had to learn this the hard way too, but this is an issue specific to configuring a Cisco DHCP server, I’m not sure where it would go in the FreePBX wiki.

1 Like

It isn’t a FreePBX problem, it’s in the way that option 66 is declared in the DHCP server.

If you want to fix it in the FreePBX (and anyone else’s) wiki, I’d suggest something like:

“When setting option 66, be sure you include values that are appropriate for your specific DHCP server. Some use STRING objects and some use IPADDRESS objects. They are entered differently. For more information on the specifics of your DHCP server settings, please check the header of your dhcpd.conf file or your DHCP server vendor.”

I’m having a very similar problem with the new Custom Ringtones option in the Endpoint Manager.

I’ve gone back to a separate FreePBX install that I had working. (It was a practice one). Provisioning was working just fine on this one. I can’t get the ringtones to upload on this one either. I’m still getting the read(ack): Connection refused error in the tftp transmission.

I’m also using Windows Server 2008 r2 for my dhcp over a vlan. I have played around with my option 66 data. I’ve tried 10.x.x.210, “10.x.x.210”, and tftp://10.x.x.210. None of them solve the problem.

I’ve tried it with firmware 2.0.4.15 and 2.0.4.14. And Endpoint Manager 13.0.83

Aug 31 14:02:43 betapbx xinetd[22785]: START: tftp pid=22880 from=10.x.x.13 Aug 31 14:02:43 betapbx in.tftpd[22881]: RRQ from 10.x.x.13 filename sangoma/1/fw40.rom Aug 31 14:02:43 betapbx in.tftpd[22881]: sending NAK (1, File not found) to 10.x.x.13 Aug 31 14:02:43 betapbx in.tftpd[22882]: RRQ from 10.x.x.13 filename sangoma/1/fw46.rom Aug 31 14:02:43 betapbx in.tftpd[22882]: sending NAK (1, File not found) to 10.x.x.13 Aug 31 14:02:43 betapbx in.tftpd[22883]: RRQ from 10.x.x.13 filename sangoma/1/fw100.rom Aug 31 14:02:43 betapbx in.tftpd[22884]: RRQ from 10.x.x.13 filename sangoma/1/ Aug 31 14:02:43 betapbx in.tftpd[22884]: sending NAK (0, Is a directory) to 10.x.x.13 Aug 31 14:02:44 betapbx in.tftpd[22883]: tftpd: read(ack): Connection refused Aug 31 14:02:59 betapbx in.tftpd[22885]: RRQ from 10.x.x.13 filename factory0700.bin Aug 31 14:02:59 betapbx in.tftpd[22885]: sending NAK (1, File not found) to 10.x.x.13 Aug 31 14:02:59 betapbx in.tftpd[22886]: RRQ from 10.x.x.13 filename /cfg0700.xml Aug 31 14:03:01 betapbx in.tftpd[22888]: RRQ from 10.x.x.13 filename /cfg0050585011b6 Aug 31 14:03:01 betapbx in.tftpd[22888]: sending NAK (1, File not found) to 10.x.x.13 Aug 31 14:03:01 betapbx in.tftpd[22889]: RRQ from 10.x.x.13 filename /cfg0050585011b6.xml Aug 31 14:03:04 betapbx in.tftpd[22924]: RRQ from 10.x.x.13 filename ringtones/formatted//ring4.bin Aug 31 14:03:04 betapbx in.tftpd[22924]: sending NAK (1, File not found) to 10.x.x.13 Aug 31 14:03:04 betapbx in.tftpd[22925]: RRQ from 10.x.x.13 filename ringtones/formatted//ring5.bin Aug 31 14:03:04 betapbx in.tftpd[22925]: sending NAK (1, File not found) to 10.x.x.13 Aug 31 14:03:04 betapbx in.tftpd[22926]: RRQ from 10.x.x.13 filename ringtones/formatted//ring6.bin Aug 31 14:03:04 betapbx in.tftpd[22927]: RRQ from 10.x.x.13 filename ringtones/formatted//ring7.bin Aug 31 14:03:04 betapbx in.tftpd[22927]: sending NAK (1, File not found) to 10.x.x.13 Aug 31 14:03:04 betapbx in.tftpd[22928]: RRQ from 10.x.x.13 filename ringtones/formatted//ring8.bin Aug 31 14:03:04 betapbx in.tftpd[22928]: sending NAK (1, File not found) to 10.x.x.13 Aug 31 14:03:04 betapbx in.tftpd[22929]: RRQ from 10.x.x.13 filename ringtones/formatted//ring9.bin Aug 31 14:03:04 betapbx in.tftpd[22929]: sending NAK (1, File not found) to 10.x.x.13 Aug 31 14:03:04 betapbx in.tftpd[22930]: RRQ from 10.x.x.13 filename ringtones/formatted//ring10.bin Aug 31 14:03:04 betapbx in.tftpd[22930]: sending NAK (1, File not found) to 10.x.x.13 Aug 31 14:03:04 betapbx in.tftpd[22931]: RRQ from 10.x.x.13 filename sangoma/1/fw40.rom Aug 31 14:03:04 betapbx in.tftpd[22931]: sending NAK (1, File not found) to 10.x.x.13 Aug 31 14:03:04 betapbx in.tftpd[22932]: RRQ from 10.x.x.13 filename sangoma/1/fw46.rom Aug 31 14:03:04 betapbx in.tftpd[22932]: sending NAK (1, File not found) to 10.x.x.13 Aug 31 14:03:04 betapbx in.tftpd[22933]: RRQ from 10.x.x.13 filename sangoma/1/fw100.rom Aug 31 14:03:05 betapbx in.tftpd[22934]: RRQ from 10.x.x.13 filename sangoma/1/fw700.rom Aug 31 14:03:05 betapbx in.tftpd[22926]: tftpd: read(ack): Connection refused Aug 31 14:03:06 betapbx in.tftpd[22933]: tftpd: read(ack): Connection refused Aug 31 14:03:06 betapbx in.tftpd[22934]: tftpd: read(ack): Connection refused

This specific problem could be a couple of things.

  1. Check the headings for your dhcpd.conf file and find out how the option 66 entry is coded. If it is a STRING, you will need to make sure the entry is in quotes. If it is an IPADDRESS entry, then the only thing that will work is the quad-number, period-delimited IP address. These entries do not have interchangeable feature - it really is a one-or-the-other thing.

  2. Your directory naming construct is not very consistent. Some of your files are specified with a leading ‘/’ and others are not. This may or may not lead to problems. Make sure that your file structure within the tftpboot directory matches what you are asking for. Also, make sure that you have both read and write access to the files and directories from the user that is running the tftpd program.

My experience with TFTP is all on Unix, so the smug answer is that it’s just because of the way M$ implements the protocol. In spite of that, there are enough peculiarities and difference between the “standard” TFTP and the “other” implementations that you might be getting jammed up with some of that.

Thanks for the help.

  1. In my post I listed my option 66 attempts, one of which was in quotes, which didn’t provision at all. Windows DHCP is string based. Leaving it as a plain 10.x.x.208 seems to work the best.

  2. I did not create any of the files or directories in the /tftpboot. They are automatically created by FreePBX. The same goes for the permissions.

Windows is not involved in the TFTP process, it’s just giving the device the IP address of the tftp server.

On a separate note, I setup EPM to use HTTP for provisioning and the Custom Ringtones did install! But I would still like to get tftp to work if possible.

Thanks,
Daniel

I believe this issue is related to my network topology. My FreePBX install is a virtual machine in Proxmox, and I think somehow the bridge interface that it uses is dropping some aspect of the client tftp response.

Were you ever able to resolve this? I am running into the same issue on a virtual install

I ended up using the http protocol. It seems to work in every situation I deal with.

Good Luck

1 Like

I tried HTTP and it worked great. Thank you!