1 About FreePBX-Distro-4.211.64 Stable releases
2 System Impact
3 Release Notes
4 Upgrade scripts
5 How to check the current FreePBX Distro version
6 Upgrade option 1: Manual upgrade using version upgrade scripts
7 Upgrade option 2: Upgrade using commercial System Administration Pro module
- 7.1 Web GUI
- 7.2 Command line
8 Resolving OS configuration file changes
9 Specific update notes

About FreePBX-Distro-4.211.64 Stable releases

Below is an outline of the FreePBX Distro 4.211.64 codename "CallForward", based on these main components:

FreePBX 2.11
Schmooze Linux 6.4 (Derived from CentOS)
Asterisk 1.8.x, 10.x or 11.x
DAHDI 2.7

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

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.

Upgrade scripts

Upgrade Scripts

Below the list of shell upgrade scripts officially released to update an existing FreePBX Distro 4.211.64 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 the version of FreePBX Distro to an earlier version. 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
 
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.

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.

Web GUI

see System Admin Pro

Command line

/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
- /etc/prosody/prosody.cfg.lua.rpmnew
  - the .rpmnew version is a default sample and can be deleted
- /etc/dahdi/modules.rpmnew
  - the .rpmnew version should replace the original configuration file as the new file has additional Digium modules added
- /etc/ntp.conf.rpmnew
  - the .rpmnew version should be deleted as the /etc/ntp.conf file has custom contents
- /etc/ssh/sshd_config.rpmnew
  - the .rpmnew version should be deleted as the /etc/ssh/sshd_config file has custom contents

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