Dear Valued Customer,
As of 10:58 P.M. on June 24th, 2025, all Hosted PBX systems running version 6.0 have been successfully upgraded from v6.0.44 to v6.0.48.
Systems running version 5.7 also received backend updates this week, though their version number remains unchanged.
🧾 Summary of Weekly Activity
- Two upgrades were deployed for 6.0 PBXs:
- v6.0.47 was deployed Monday morning.
- v6.0.48 was deployed late Tuesday evening.
- Upgrade Freeze in Effect: Due to several issues reported post-upgrade—primarily related to the PBX reporting engine—we are pausing further upgrades to 6.0 PBXs. Development resources are now fully dedicated to identifying and resolving these report-related bugs before resuming the upgrade cycle.
- We’ve also delivered critical fixes and improvements to:
- The PBX Command Center (PBXCC)
- Operator Panels
- Desktop Communicator
🔒 Upgrade Suspension: Reporting Issues Under Review
No further 6.0 upgrades will be performed this week.
All reported defects impacting reporting features in 6.0 are being actively triaged and addressed. These include duplicate entries, broken templates, malformed exports, and delivery issues in scheduled reports.
A full list of these known issues is available in the Upcoming Fixes and Improvements section below.
🔍 Detailed Changelog – PBX v6.0 Releases
📦 6.0.48
- Call Reports – Duplicate Entries Calls routed to a Dial Group step were being logged multiple times in Call Detail Reports. This led to bloated or misleading reporting. This release includes a fix that suppresses duplicate records from appearing. PBX-3639
📦 6.0.47
- Music on Hold – Choppy Playback Inconsistent playback quality (described as choppy and high-pitched) was traced to an improper stream encoding to slin16 rather than slin. Additionally, new Music on Hold groups were not initializing correctly in the dialplan, compounding troubleshooting efforts. PBX-3647, PBX-3632
📦 6.0.46
- Queue Recordings – Playback Errors Call recordings from queue calls were unplayable via the Apps → Call Recordings interface due to nonstandard filename formatting. The playback link incorrectly redirected users to the PBX status page. PBX-3630
- Call Volume Report – Graph Not Rendering A JS initialization failure caused the call volume graph to remain blank. This issue has been resolved. PBX-3619
📦 6.0.45
- Removed Legacy SMS Page Link Residual links to the deprecated Apps → SMS page were removed from email notifications generated by SMS features. PBX-3602
- PBXCC – IP Block Handling + Whitelist Enforcement Two related security issues were resolved:
- Blocked IPs were able to maintain pre-existing sessions and continue traffic.
- The master whitelist was not being checked correctly at runtime. PBX-3628, PBX-3547
- Operator Panels – Stability + Feature Fixes The Panels system received backend and UI improvements:
- Now logs to syslog instead of /var/asterisk/log
- Resolved:
- Inability to log in to queues
- Failure to park calls
- Errors dialing from company directory
- Incorrect queue agent presence indicators PBX-3519, PBX-3625
- Mirrored Extensions – Parking Behavior Calls from mirrored extensions (excluding Salesforce and Desktop Communicator) were parking in the default lot instead of the lot assigned to their parent extension. Fixed. PBX-3623
- Status Page – Undefined Active Call Count “Total calls” showed as blank or “undefined” due to a failed regex match introduced during earlier 6.0 changes. PBX-3613
- User API – Contact Update Failures + Visibility Bugs
- Updating contact details failed when modifying both number and type.
- Some global contacts were being returned as personal in the API. Both issues are resolved. PBX-3616
📡 Version 5.7 PBXs
No changes to the version number.
Only backend updates were applied.
We will only be updating 5.7 systems further in the event of critical or service-impacting issues.
💬 Desktop Communicator – Version 2.3.62
A new feature in DTC v2.3.62 (6.0 only) introduces:
- Personal Contact Creation Users can now create a personal contact from call, voicemail, or SMS logs. A new button labeled “Create a Personal Contact” appears next to non-associated records, opening a simplified contact creation form prefilled with known data.
- Visual and UX Improvements
- New styling for records tied to existing contacts
- Refreshed UI for action buttons
🔧 Upcoming Fixes and Improvements
The following open issues are being prioritized as part of our reporting improvement push:
| ISSUE | Description |
|---|---|
| PBX-3639 | Over-detailed reporting on 6.0 |
| PBX-3555 | Report scheduler creates excessive filesystem bloat |
| PBX-3551 | Inconsistent report headers |
| PBX-3651 | Fax report splits outbound faxes |
| PBX-3650 | Scheduled report emails not sending |
| PBX-3649 | Scheduled reports fail via SFTP |
| PBX-3644 | Channel Event Log errors with 5.7 data |
| PBX-3638 | Script error in report history UI |
| PBX-3636 | Exported .xlsx reports cannot be opened |
| PBX-3635 | Hyphens in SIP names break call recordings |
| PBX-3617 | Inbound filter includes wrong call types |
| PBX-3605 | Follow Me marks internal as inbound |
| PBX-3600 | Call Quality report includes excluded extensions |
| PBX-3581 | Unanswered calls showing recordings |
| PBX-3553 | Template creation fails in Call Routing Reports |
| PBX-3554 | Call transfers not reporting correctly |
| PBX-3529 | Time zone mismatch hides calls in reports |
🎉 Wrapping Up
Thank you for your attention and continued feedback as we work through these updates. Our next report will contain progress on the above fixes and any resumed upgrade activity.
Happy Wednesday!
— The DLS Development Team