Hi. Installing FPBX17 from the github script setup Asterisk Version such as 20.4.0 (while today latest stable is 20.8.1). Same example for Asterisk 21 version. What’s the best way to upgrade Asterisk on this scenario? In old distro there way “System Update” providing Asterisk upgrade; in FreePBX SysUpdate is not present.
Yes as of now “System update” is disabled in Freepbx 17 UI. We will try to add back this functionality asap.
As soon as we published new asterisk rpm for the Debian then you should be able to “apt update && apt upgrade” to get the updated version.
thanks
Kapil
1 Like
Thanks a lot. So for the moment “latest” version for that scenario is 20.4.0 (in the example of Asterisk 20). Clear.
yes, we are yet to build / test the new asterisk version. Thanks
1 Like
(Just pointing out that rpm’s are an ‘alien’ concept in the debian world 
)
It really is not difficult to download whichever version of Asterisk you want and compile it yourself. I’ve been running Asterisk 21.3.0 with FreePBX-17 beta with no issues.
cd /usr/src/
wget http://downloads.asterisk.org/pub/telephony/asterisk/asterisk-21-current.tar.gz
tar xvf asterisk-21-current.tar.gz
cd asterisk-21*/
contrib/scripts/get_mp3_source.sh
contrib/scripts/install_prereq install
./configure --libdir=/usr/lib64 --with-pjproject-bundled --with-jansson-bundled
make menuselect
make
make install
make samples
make config
ldconfig
fwconsole restart
Also an alien concept with debian?
–libdir=/usr/lib64
pjproject_bundled also unnecessary, it is the default
Not sure. Some of the Debian-12 cloud provider instances needed some of the “alien” commands for Asterisk to compile correctly. Including them in the script does not cause issues so this is a band-aid. I was more than a little surprised at differences from various cloud providers.
And yes I know, that should have no influence on the configure command except when it does.
https://lwn.net/Articles/844446/
Well Debian 12 is Debian 12 from any cloud provider and wouldn’t generally look for libraries in a nonsense directory. which you could awkwardly correct by replacing your ldconfig with ldconfig /usr/lib64 but why do that?
Defaults are exposed with ./configure --help and apart from the jansson thing have worked for donkeys years.
alien on the other hand is a half hearted effort by debian to sooth the redhats (no, not those ones) who still remember their old golden retriever (I cross-reference another current thread) ;-_
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.