I noticed during a recent migration that this file is not backed up by the FreePBX 17 backup. However it is still recognized and used by Asterisk (obviously, only if you create it and add things to it, and have chan_sip installed which uses this) Was this deliberate or is it an accident and I should file a bug report? (yes I know chan_sip is deprecated but it’s still supported in FreePBX 17 with Asterisk 20 and 21)
You need to tell the backup module to backup ASTETCDIR if you want the custom files in /etc/asterisk.
Because, the backup entry I used in FreePBX did have that entry.
It just does a tar of the directory. It will capture everything in there.
And yet, it didn’t capture sip_custom_post.conf.
I always run FreePBX virtually and when I do a major upgrade I spin up a new VM then make sure everything is working before deleting the old VM, so I had the old file around. I saw what it’s “supposed to be doing” by watching the backup log happen in the old VM and watching the restore log in the new VM but that file was not restored, despite the tar. I still have the old backup around and I could open it up and dig around in it and see if that file was indeed captured and the problem is in the restore, but I assure you - it wasn’t in the restore done to the new install. I know what I saw. Possibly there was a rights or ownership issue - but it didn’t work.
My question was - is this normal behavior or not? If not, and if it’s supposed to have worked, as you seem to be saying here, then I will dig around and if I can figure out what happened and it wasn’t due to something I did, then I’ll file it as a bug.