Have a completely vanilla Debian 12 system, with FreePBX 17, did an apt-get update apt-get upgrade back in December no problem.
Just did one Feb 28th - and the /tftpboot directory was wiped clean. 80 phone configs gone.
“those Fing lazy bastards” was the first thought that came to mind when I discovered it - 3 days later, natch. Fortunately the phones save their configs in the phone so if they reboot it’s OK but the syslog was filling up with “file not found” entries.
I’m not interested in trying to reproduce or doing the work to file an upstream bug. Just warning you to watch your asses.
Also curious if you are manually building those or if they are output from Endpoint Manager module automatically based on the GUI-based configuration ?
Once upon a time long ago I supported some Mitel phones. They had the capability to output (write) their config - I thin I had to connect to the web browser in the phone and then do a save/export config from the browser. It ended up on my local hard drive, copy to tftpboot
I know those Mitel phones I have a box of 15 of them along with the HX PBX they used to be connected to. Never tried setting them up, though. Mitel’s latest firmware for them changes them so they can’t register into a SIP server anymore.
In this case though I had a backup. It’s just the sheer lack of responsibility on the Debian maintainer of tftpd-hpa to bother adding 1 or 2 lines in their update script that would preserve the tftpboot directory. Particularly because my tftpboot directory isn’t in the standard location that tftpd-hpa puts it in so they had to go out of their way to overwrite the directory.