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 :
@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?
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 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
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?
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 ?
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.