I installed Asterisk 22.8.0 by downloading it, compiling it (and adding a patch) and installing it, then installed FreePBX with the –noasterisk option Everything worked
I then downloaded and patched and compiled Asterisk 22.8.2 and did a backup from FreePBX and then did a make uninstall from the 22.8.0 build dir, and a make install from the 22.8.2 dir
Calls into the system got dead air when the incoming route transferred them into the IVR. I could still press the options and dial in the extensions and get transferred and so on, but the prompts I had recorded were not playing.
I then did a restore from the FreePBX backup and all was well.
The documentation I’ve read said that doing a make install on a new version of Asterisk isn’t supposed to trash the config files and prompts but it obviously trashed something. I had only made the FreePBX backup “just in case”
Is there an “official method” of making a trivial patch update of Asterisk when you are running your own private compile of Asterisk?
I believe the make install will still deploy an /etc/asterisk/asterisk.conf file which if not configured the same as before may point to a different sounds location. So you will not hear any recordings. Should be evident from the log file.
How annoying. Unfortunately, the make install command seems not to create an install log. make pbx is supposed to install the asterisk.conf file. Thank you for the tip I will add this to my notes to check for in the future.
Well not now, of course, since it’s working. I can’t see anything in that log for the prior overwrite, though, I just remember seeing something like that in the log displayed in the FreePBX GUI. Sadly the log files are copious and full of stuff like the following in the “full” log:
[2026-02-15 04:38:02] WARNING[1280] res_pjsip_pubsub.c: No registered publish handler for event presence from 803
Even though extension 803 is working fine. (that extension is a test extension using MicroSIP which Asterisk seems to hate for some reason)
Plus there’s tons of complains about various php things being deprecated.
So it’s kind of hard to dig around in those and find anything.
This wasn’t an overwrite. You uninstalled your current build of Asterisk which does exactly that, uninstalls Asterisk including your current configs and the files (like your sound files). Then you installed a fresh install of Asterisk.
Generally when you are updating to a new version of Asterisk you don’t uninstall the current version because it would remove your current setup. So yeah, you needed to restore a backup to put all the files you removed back into place.
Under Asterisk, the command to uninstall the config files is
make uninstall-all
A regular make uninstall only uninstalls the binaries and, canned sound files. Now, in this case I guess it ALSO uninstalls the recorded sound files which leads to another problem, the instructions in the Asterisk make file say to do a make uninstall or manually delete libraries and run an ldconfig because some libraries are not uninstalled when you do an overwrite install.
I STARTED with a simple overwrite install and got that error. The maker checks and carps about older libraries and tells you to do a make uninstall first OR manually delete older libraries and do an ldconfig. It would sure be nice if it actually told you WHAT libraries it was carping about.
In addition, any reasonable person would assume that a recorded sound file is part of the configuration done to the system AFTER it’s installed. But obviously THAT ship has sailed.
Being the suspicious type I always do whatever backups I can before doing anything, so I’m not really affected but for sure, this is one of those trap doors that is GOING to catch someone.
So in summary, the correct way of doing this is:
Do the new build of the newer Asterisk version
do an overwrite make install
Go on a treasure hunt for whatever older versions of libraries the make install is bitching about and delete them
do an ldconfig
And take a backup before doing any of this, since the instructions are not really that clearly defined.