Hi,
I have CIP230 for my tests, pbx is FB17. The phone could get the config and register by auto-provision. A wiered issue I see today is that phones can not get config from our pbx. I am using redirect server and even tried using the ip address of server directly.
Phone tries to get the cfg file :
I can see the cfg file
My ip is not banned.
The only change I had in last week, was upgrading some freepbx modules.
I even reinstalled clearly Ip device today.
Any idea why this is happening?
@moghimigiti try turning on debugging and then check the output see: Debugging Commands
@reconwireless Thank you.
This is the message I have there:
Mon Jun 09 2025 22:08:59 GMT-0400 (Eastern Daylight Time): File path of /srv/tftp/cfgxxxxxxxx.xml is not valid, as it does not exist
But files are under /tftpboot Can I change this path to check /tftpboot?
Check the system log files for Clearly Devices in freepbx.
There was an issue with Clearly devices 17.0.6, which was updated to 17.0.6.1, where the http server was not pulling from /tftpboot but /srv/ftfp
Check System > System log files > clearly devices log
And
cat /etc/default/tftpd-hpa
TFTP_USERNAME=“tftp”
TFTP_DIRECTORY=“/tftpboot”
TFTP_ADDRESS=“:69”
TFTP_OPTIONS=“–secure”
Are you sure you have all the module settings correct with regards to Https, certificates etc? Usually when the CIP phones don’t get the full config, firmware download or won’t connect afterwards it’s because the module is set to use HTTPS and I either didn’t apply the ssl certificate OR I have the PBX IP set instead of the FQDN in the module and template settings.
I am using http. Not https and the error message says the directory /srv/tftp does not exist. It passes the authentication part.
Since this happened after freepbx modules update and I am using 17.0.6.1 could that be because this upgrade overwrites the fix you had in 17.0.6.1?
I fixed the issue by deleting the /srv folder.
Clearly mentioned using symbolic links back to /tftpboot, but I couldn’t get it to work.
/srv is empty anyway and is just owned by root.
Worked! I removed /srv and its working now. Thanks! 
I would not recommend changing that as the default TFTP package handles that file. In Clearly Devices 17.0.6.1 we made it so it would honor the TFTP symlink and I just tested here again and it shows to be working. Are you sure you have 17.0.6.1
I just tested here and it is able to grab the config just fine
/srv/tftp/cfg70b3d59b0070.xml found, passing content to ClearlyIP CIP270V1 2.42.6.6.1R68 70:b3:d5:9b:00:70
Yes.
Are you using FreePBX Installer or TangoPBX Installer as far as how you installed the system? If FreePBX was it their ISO or their standalone installer script?
Tom was this on a stock FreePBX install or TangoPBX install?
Just for clarification on TangoPBX install. The default path for tftp server is to save things to /src/tftp/. Instead of changing these defaults that the package provides we just symlynk /tftpboot to /src/tftp.
Our Clearly Device module has a web proxy for getting configurations and it looks to see if /src/tftp exist and uses that otherwise falls back to /tftpboot.
What we are trying to determine was did you have a /src/tftp directory ?
Freepbx , their script. Its FB17
I had /srv/tftp and it was empty.
OK that is the problem. We will have to adjust our module as we assumed wrongly if that directory was there, then tftpboot would symlink to it like it does on TangoPBX. We will get a fix in place to detect this and handle it.
It was a bash install of FreePBX 17
