FusionPBX 5.4 Released

M

markjcrane

Active Member
Staff member
Jul 22, 2018
677
243
43
50
FusionPBX 5.4 Released.
- Release date: 15 July 2025

New Features
- WebSockets
- Realtime Active Calls
- Realtime CPU
- Call Recordings, click where you want it to play
- upgrade.php --help
- Provisioning improvements for multiple phones.
- Assign or unassign a group to multiple items in the menu.
- Better Call Detail Record handling.
- Call Detail Record Details - Added Call Flow Icons for each application.
- Updated class and interface autoloader.
- Many bug fixes, more polish, and more efficient code
- Optional add-on for Open ID authentication
- And more...

Additional Information
- Release notes on the website. https://www.fusionpbx.com
- Upgrade Notes. https://docs.fusionpbx.com/en/latest/advanced/version_upgrade.html (UPDATED)
- Github notes on the release. https://github.com/fusionpbx/fusionpbx/releases/tag/5.4.4
 
Last edited:
  • Like
Reactions: wouam31, babak, voipBull and 2 others
Mark, why doesn't active calls work anymore? I run two separate servers, and they both do the same thing: show nothing in active calls during active calls. I am running up-to-date versions of 5.4.
 
The new active calls works but require setting up the websocket configuration in NGINX. Look for the websocket section at the following link.

https://docs.fusionpbx.com/en/latest/advanced/version_upgrade.html

  • Make sure you are using the latest code on the git branch you are using.
  • If you are using a proxy as a firewall in front of your NGINX it could need adjustments, or it could prevent websockets from working.

Another option the original Active Calls feature is still available. In the menu manager edit the default menu then find Active Calls

Advanced -> Menu Manager
Title: Active Calls
Link: /app/calls_active/calls_active.php
Click to expand...

If you need more help, a phone call to the FusionPBX support number could be beneficial.
 
Last edited:
Thanks Mark for your prompt response. I followed the doc and got it working on both servers. The icon with the number is green now on both servers.
 
@markjcrane in the new version, when a call is received by IVR and by option or by direct dial goes to any extension, call records does not work. All extension are set to record All
 
Bug reports should be in their own thread. So they can be discussed on their own. The user_record dialplan is not a bug.

You can review the complete user_record dialplan here.
https://github.com/fusionpbx/fusion...rces/switch/conf/dialplan/050_user_record.xml

You would find this in the dialplan. There are two ways to record the call used here, one is enabled and one is disabled by default.
- api_on_answer=uuid_record enabled by default
- record_session is disabled by default

<action application="set" data="api_on_answer=uuid_record ${uuid} start ${record_path}/${record_name}" inline="false" enabled="true"/>
<action application="set" data="record_answer_req=true" enabled="true"/>
<action application="record_session" data="${record_path}/${record_name}" enabled="false"/>
Click to expand...

This makes it possible for you to easily adjust the dialplan and use one type of record over another by disabling one and enabling the other.
 
Last edited:
Is FusionPBX 5.4 with the latest stable Debain Trixie v13 suitable for production?
Should we install FPBX with Debian wormwood v12 for production?
Many thanks!
 
You must log in or register to reply here.
Top Bottom