Overview
Keeping your PBX system up to date ensures access to the latest features, security enhancements, and performance improvements. Before performing any update, it is critical to create a current backup of your system.
With a valid backup, any issues encountered during the update process can be resolved by restoring the backup, returning your system to its previous operational state.
Important: Verify Available Disk Space Before Updating
New PBX releases often include database schema changes that require modifications to MySQL tables, including the Call Detail Record (CDR) database. During this process, existing CDR records must be updated to include new fields.
Disk Space Requirement
Before starting an update, ensure you have available disk space equal to or greater than the size of your CDR database.
Example:
CDR Database Size: 10 GB
Required Free Disk Space: Minimum 10 GB
Failure to meet this requirement may cause the update process to fail or result in database issues.
Check CDR Database Size
SSH into your PBX server.
pbx# ssh user@YOUR_PBXWARE_IP -p2020
pbx# du -sh /opt/pbxware/pw/var/lib/mysql/pbxware
Example output:
1 4G /opt/pbxware/pw/var/lib/mysql/pbxware
Check Available Disk Space
pbx# df -h
Review the available space on the partition where PBXware is installed and verify that sufficient free space exists.
Filesystem Size Used Avail Use% Mounted on devtmpfs 10M 0 10M 0% /dev /dev/sda3 9.7G 3.6G 5.7G 39% / <----- 4GB CDR Database - Drive Space OK
Updating the PBX
Verify Project Version Before Updating
Before proceeding, ensure the update script references the latest project for your currently running PBX version.
pbx# sed -i -E '13 { s/(PROJECT="(pbxware|httpd)-)(7\.[0-5])"/\17.6"/; s/(PROJECT="(pbxware|httpd)-)8\.0"/\18.1"/ }' /opt/httpd/sh/update
pbx# sed -i -E '13 { s/(PROJECT="(pbxware|httpd)-)(7\.[0-5])"/\17.6"/; s/(PROJECT="(pbxware|httpd)-)8\.0"/\18.1"/ }' /opt/pbxware/sh/updateStop Services
Before beginning the update, stop the PBX and HTTP services:
/opt/pbxware/sh/stop /opt/httpd/sh/stop
Perform the Update
Web Services
pbx# /opt/httpd/sh/update -v update
Update PBXware:
pbx# /opt/pbxware/sh/update -v update
Start Services
Once the updates are complete, start the PBX
pbx# /opt/pbxware/sh/pbxware start
Post-Update Tasks
After the update completes, run the following commands:
pbx# /opt/pbxware/sh/pbxware http_api resave pbx# /opt/pbxware/sh/asterisk -rx 'restart now'
Monitoring the CDR Database Upgrade
After logging back into the PBX web interface, you may see an “Update in Progress” notification.
Selecting this notification will open the Setup Wizard where you can:
- Monitor CDR database conversion progress.
- Verify that the update is actively running.
- Ensure the system is not restarted during the process.
Important
Existing CDR records may be temporarily unavailable while the database is being updated. Once the process completes, all historical CDR records should become available again.
If Progress Appears Stuck
If the progress remains at 0% or stops advancing for an extended period:
Contact Fireline Communications Technical Support immediately.
Do not reboot or interrupt the update process unless directed by support personnel.
Verify CDR Functionality
Once the update is complete:
Place several test calls.
Confirm new CDR records are being generated.
If new CDR records are not appearing, restart PBXware:
/opt/pbxware/sh/pbxware restart
If CDR records still do not generate after the restart, contact Fireline Communications Technical Support.
Best Practices
We strongly recommend performing update validation immediately after the upgrade and before normal business operations begin.
Benefits include:
Confirming system functionality before users return.
Allowing time for troubleshooting.
Providing an opportunity to restore from backup before production data is generated.
Backup Restoration Considerations
If you restore a backup from before the update:
Any data created after the backup was taken will be lost.
For example, restoring a backup taken one day ago will result in the loss of one day of call records and configuration changes.
Support Notice
Important: System updates for self-hosted or non-hosted PBXware deployments are not typically included as part of standard support agreements.
If you would like Fireline Communications to perform the update on your behalf, professional service fees may apply. Please contact our support team for scheduling and pricing information.
Last Updated on October 22, 2026