Recommendations when recompling Asterisk

Asterisk Asterisk General
1

Hello,

I’m planning to upgrade Asterisk version on several hosts. I want to to minimize downtime and off-hours work.

Sometimes, running Asterisk version is the one packaged by the OS. Often, this running version comes from locally compiled source code. For all hosts, target Asterisk will be the latest available 22.X with “casual” compilation options. All hosts are amd_64 Debian hosts.

I was thinking on the following alternatives:

  1. local compilation
  2. compiling on one host and pushing binaries on target hosts
  3. compiling on one host and pulling binaries from target hosts

Have you ever experiment options 2 or 3 above ? Would you recommend any ?

When recompling locally, I usualy:

  1. download source code
  2. stop Asterisk
  3. ./configure, make && make install
  4. start Asterisk

Can I (safely) optimize these steps ? Specifically, I was thinking of having several Asterisk instances on each host and switching from one to an other using symbolic links.

Best regards

2

I use FreePBX but on one of them I have a locally compiled Asterisk.

In order to eliminate downtime on all my PBXes I virtualize the PBX. When building a new PBX I always start with a virgin virtual image, compile it, test it, make sure everything is gold, run the backup and restore to it - then swap IPs with the 2 VMs.

This also makes backups a snap - just shut down the PBX VM, make a copy, restart the VM. I use KVM+qemu.

I would bet all your PBXes are running on hosts that are loafing along with tons of unused resources. Unless you are running antique servers or something ridiculous like a Raspberry Pi.

The PBX is not the only server in my enterprise that is like this. In fact the only servers I have that are bare metal are fileservers - all application servers are VM’s and other than the fileservers, all other hoses are hypervisors - usually Ubuntu some Windows Server.

3

Though using VM has strong advantages, in my question, I was inclined to explore `m̀ake` options, if such options exist, so that I could compile sources into parallel directories and use symbolic links to select the appropriate Asterisk version as with

/usr/lib/asterisk-22.6.0/modules

/usr/lib/asterisk-22.7.0/modules

/usr/lib/asterisk/modules →/usr/lib/asterisk-22.7.0/modules

Is it possible to pass some argument to make in make arg1=val1 && make install arg2=val2 to accomplish this ?

4