FINAL UPDATE: Despite running on just 4H of sleep and some pop tarts for breakfast, I’ve gotten it going now… So for those who are just tuning in, welcome. If you’re in a similar situation I’m in, I have the solution now: Getting this to work on FPBX16 is IMPOSSIBLE, just upgrade to 17, I know 16 was better in some ways, but go up a version if you need this working. Let’s start there. Secondly, if you haven’t checked out the other thread “Installing FreePBX 17 on Hyper-V virtualization platform”, go check that out real quick, basically just perform some checks on your host system and with your VM platform while the guest machine is off. Anyway, The solution here is to ensure that you DON’T install the modified TFTPD client as ROOT, you will pull your hair out trying to get it to work, instead, only do the first few steps of the linked guide in this thread as root, once you get to doing apt-get source whatever, STOP BEING ROOT! Just sudo everything that needs to be done as sudo, so basically anything you can do NORMALLY, just do it without sudo, then obviously once that’s all set up, you gotta chmod the /tftpboot directory to 777, then chmod -r 666 everything inside of that, then just configure the softphone like normal (as admin obviously), and away you go.
This was VERY painful and heartbreaking as I loved 16 for the familiarity I had with whatever version I was using back in 2020, but… progress, I suppose. Needless to say, I got it all worked out now, and now I’m prepared for when the future throws this challenge at me again.
Also, word to the wise: MAKE BACKUPS OF THE MODIFIED FILES AS WELL! If you don’t, and TFTPD on FPBX constantly fails to start with no error, your in.tftpd file is MISSING! Had to learn that the hard way last night… Thankfully the fix was mostly easy… just had to remind myself to cp some stuff instead of mving it…
One more thing: I’d be extra cautious when doing this, even with the firewall wizard having been ran, apparently you can STILL set off Fail2Ban… somehow…