Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

The upgrade procedures outlined below will stop Asterisk and may also require a system reboot to fully apply. Perform the system upgrade using a scheduled maintenance window.

Release Notes

Release Notes Here

  • 4.211.64-1- Click on link for release notes.

  • 4.211.64-2- Click on link for release notes.

  • 4.211.64-3- Click on link for release notes.

  • 4.211.64-4- Click on link for release notes.

  • 4.211.64-5- Click on link for release notes.

  • 4.211.64-6- Click on link for release notes.

  • 4.211.64-7- Click on link for release notes.

  • 4.211.64-8- Click on link for release notes.

  • 4.211.64-9- Click on link for release notes.

  • 4.211.64-10- Click on link for release notes.

  • 4.211.64-100- Click on link for full release notes.  This will take your 4.211.64 version system to a 5.211.65-1 version and track.  Run this script

...

You can check your current FreePBX Distro version by going to the Web GUI sysadmin module or, from the Linux command line, do a:

Code Block
cat /etc/asterisk/freepbxdistro-version
 
on older systems and
 
cat /etc/schmooze/pbx-version
 
on newer systems

Upgrade option 1: Manual upgrade using version upgrade scripts

...

To install an update script via the Linux command line, use the following commands, substituting the proper scripts from above. Download the upgrade script matching the current version of FreePBX Distro installed, mark it as executable and run it.

Code Block
cd ~
mkdir upgradescripts
cd upgradescripts
 
wget http://upgrades.freepbxdistro.org/stable/4.211.64/upgrade-4.211.64-2.sh
chmod +x upgrade-4.211.64-2.sh
./upgrade-4.211.64-2.sh

The Distro upgrade script will update both FreePBX components (Asterisk, the FreePBX web GUI) and all base CentOS components.

...

If you have sysadmin module installed and have also purchased the SysAdmin Pro commercial license for the sysadmin module, you can use either the FreePBX web GUI to perform an update or run the following script from the command line to auto-update your system to the latest version.

Web GUI

Command line

Code Block
/usr/sbin/sysadmin_update_system

Resolving OS configuration file changes

Some upgrade scripts will result in .rpm package updates that need configuration files to be manually cleaned up afterwards. The general procedure is described in the page Cleaning up files from a RPM update.

Specific update notes

  • upgrade-4.211.64-5.sh

    • "REBOOT SYSTEM NOW FOR DAHDI AND WANPIPE CHANGES TO TAKE EFFECT"

  • upgrade-4.211.64-6.sh

    • "REBOOT SYSTEM NOW FOR DAHDI AND WANPIPE CHANGES TO TAKE EFFECT"

  • upgrade-4.211.64-7.sh

    • "REBOOT SYSTEM NOW FOR DAHDI AND WANPIPE CHANGES TO TAKE EFFECT"

  • upgrade-4.211.64-10.sh

    • "REBOOT SYSTEM NOW FOR DAHDI AND WANPIPE CHANGES TO TAKE EFFECT"

  • upgrade-4.211.64-to-5.211.65-1.sh

    • /etc/fail2ban/jail.local.rpmnew

      • the .rpmnew version should not be used as the /etc/fail2ban/jail.local is auto-generated – delete the .rpmnew file to clean up

        Code Block
        rm /etc/fail2ban/jail.local.rpmnew
    • /etc/prosody/prosody.cfg.lua.rpmnew

      • the .rpmnew version is a default sample and can be deleted

        Code Block
        rm /etc/prosody/prosody.cfg.lua.rpmnew
    • /etc/dahdi/modules.rpmnew

      • the .rpmnew version should replace the original configuration file as the new file has additional Digium modules added

        Code Block
        mv /etc/dahdi/modules.rpmnew /etc/dahdi/modules
    • /etc/ntp.conf.rpmnew

      • the .rpmnew version should be deleted as the /etc/ntp.conf file has custom contents

        Code Block
        rm /etc/ntp.conf.rpmnew
    • /etc/ssh/sshd_config.rpmnew

      • the .rpmnew version should be deleted as the /etc/ssh/sshd_config file has custom contents

        Code Block
        rm /etc/ssh/sshd_config.rpmnew

...