Skip to end of metadata
Go to start of metadata

About FreePBX Distro and AsteriskNOW 5.211.65 Stable releases

Below is an outline of this version

  • FreePBX 2.11
  • SHMZ OS 6.5 (Derived from CentOS)
  • Asterisk 1.8.x or 11.x
  • DAHDI 2.10
  • Full support for FreePBX HA Final

System Impact

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

Upgrade scripts

Upgrade Scripts

Above is a list of shell upgrade scripts officially released to update an existing FreePBX Distro 5.211.65 system to a specific minor release version. The scripts will update the entire distribution, including all FreePBX web components and all OS-level components (such as the kernel and kernel modules).

All upgrades need to be installed in numeric ascending order. Do not skip any upgrade step. Upgrade scripts are not cumulative. Each upgrade script should be run in ascending order to get to the desired final version.

The upgrade path is one-way. These scripts cannot be used to downgrade to an earlier version of the FreePBX Distro. The only way to reverse the effects of the upgrade procedure is to restore the system from a backup.

How to check the current FreePBX Distro version

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

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

Step 1: Check the current FreePBX Distro version

Display the current version file (as above) to confirm the current installed version of FreePBX Distro.

Step 2: Download and run the applicable upgrade script

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.

cd ~
mkdir upgradescripts
cd upgradescripts

chmod +x

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

Step 3: Specific script instructions

Note any special instructions displayed at the end of the upgrade if any are displayed, such as to reboot the system.

Step 4: Confirm the new FreePBX Distro version

Cat the updated (now current) version file (as above) to confirm the current installed version of FreePBX Distro is the expected newer version.

Upgrade option 2: Upgrade using commercial System Administration Pro module

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.


Command line


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

    • ntp.conf: this file is updated in this release to disable NTP server functionality due to concerns about keeping this component securely configured. Delete the old saved file to clean up

      rm /etc/ntp.conf.rpmsave
    • Important: Any devices that may have been using the FreePBX Distro server to get time information (such as phones) should be reconfigured to use a different NTP server by editing the NTP server settings distributed to phones by EndPoint Manager (OSS or Commercial)

    • Delete the default package fail2ban configuration file. FreePBX Distro generates a customized version of this file

      rm /etc/fail2ban/jail.local.rpmnew
    • Delete the old file "/etc/httpd/conf.d/freepbx.conf.rpmsave" to clean up

      rm /etc/httpd/conf.d/freepbx.conf.rpmsave
    • MySQL activity logging to /var/log/mysql/mysql.log is disabled in this release. This MySQL log file can be quite large, depending on server usage loads. Delete this file after the update to reclaim this disk space.

      rm /var/log/mysql/mysql.log
    • Replace the old version of /etc/dahdi/modules with the updated version of the file

      mv /etc/dahdi/modules.rpmnew /etc/dahdi/modules
    • Reboot as instructed


CentOS is a Trademark of Red Hat and we do not claim to have any relationship with either Red Hat or CentOS

Asterisk and AsteriskNOW are registered trademarks of Digium Inc.


  • No labels


  1. I recently updated to the 6.12.65 track using the script supplied.
    But experienced (even on a clean 5.211.65-21 install) that the upgrade process will fail because the system downloads signed *.tgz.gpg files which it can't handle.I don't know why it is doing this but this is a one-time problem because it uses old code (prior FreePBX 12) to download stuff intended for FreePBX 12. If you manage to update however, the code causing the error will be replaced. There is a simple trick to make it update.

    Basically we need to force it to download the non-signed versions of the new modules.
    So here is what I did before starting the script:

    • use your favorite editor, in my case nano to modify the file responsible for downloading modules:
      nano /var/www/html/admin/libraries/module.functions.php
    • search for  !$url)  (press Ctrl-W), you should find the line where it says

      if (!$headers || !$url) {
    • after the closing  }  (two lines later) you add
      $url = str_replace(".tgz.gpg", ".tgz", $url);


    You can save the file and exit the editor. The update script should then be able to install all new modules.
    Removing of the patched line afterwards doesn't seem to be necessary, because it looks like the new version of the file has a different name.
    FreePBX will complain (in the web interface) about unsigned modules but following the advice given along with the error that is resolved easily.

    1. This has been resolved on the mirror server and will no longer happen