As of 10:44 P.M. Central, all Hosted PBX systems on version 6.0 have been updated from v6.0.57 to v6.0.58.
PBXs running version 5.7 remain on v5.7.89 with no changes this week.
There were no updates to the Desktop Communicator, though improvements are coming soon.
🌟 Overview
This week’s release brings thoughtful fixes and forward-looking improvements. We’ve resolved several long-standing issues — including BLF call pickup on supported desk phones and some edge-case problems with reports and Panels. We’ve also quietly introduced transcription capabilities into 6.0, though they remain disabled while in testing.
While we aren’t upgrading any new PBXs to 6.0 this week, these changes are now live on all 6.0 systems.
🚫 No PBX Upgrades Scheduled This Week
We’re continuing to prioritize stability for version 6.0. No new upgrades are scheduled this week while we work through final refinements and broader feedback.
🔍 In-Depth Changes
✅ Version 6.0.58 Highlights
📞 Call Pickup via BLF Keys Restored
Users with Polycom and Yealink phones can now once again pick up calls using their BLF (Busy Lamp Field) keys. This functionality has been broken in 6.0 for some time and was previously attempted (unsuccessfully) in version 6.0.52.
This time, rather than patching Asterisk — which introduced registration issues for some devices — we rebuilt the call pickup logic entirely in the Dialplan. The result is a more stable, predictable feature that works across a broader range of supported phones.
References: PBX-3408, PBX-3715
🧩 Operator Panels Now Handle Special Characters Gracefully
In some rare cases, Panels would completely fail to load if a user’s name included a backslash (\) or a quote (“). The issue was caused by improper escaping in the JSON sent to the web interface.
We’ve updated our backend to sanitize these values correctly so the Panels remain fully functional, regardless of naming quirks.
Reference: PBX-3325
📄 No More “Empty Error” Emails from the Report Scheduler
Our operations team had been receiving blank “error” alerts from the report scheduler, caused by stray newline characters in the report output. While the reports themselves completed successfully, these extra lines triggered false alarms.
This has now been resolved — no more empty error messages.
Reference: PBX-3726
🗣 Voicemail & Call Transcription (In 6.0 – Staff-Enabled Only)
Transcription support for voicemails — and eventually, full calls — is now included in version 6.0. However, this feature is not yet available to end users and must be manually enabled by DLS staff in limited cases.
We’re not actively promoting or recommending its use yet, as it’s still undergoing evaluation and refinement.
We recognize that this capability has been available in other platforms for some time. However, our focus has been on building a smarter implementation — one that not only transcribes audio, but also aims to:
- 🧠 Automatically determine how many people are on the call
- 🗣 Separate out who said what through speaker diarization (in development)
These enhancements are still being tested internally. When they’re ready, our goal is to provide transcription that’s both more accurate and more useful than typical implementations.
Reference: PBX-3359
📊 Fix for Broken SMS Report Exports
We resolved an issue where the “SMS Detail Without Content” report could not be exported to PDF, CSV, or other formats due to malformed internal data.
Exports now function correctly.
Reference: PBX-3697
🖋 Report Header Formatting Is Now Consistent
Several reports had inconsistent header formatting between the web version and exported documents — especially when filters were applied. This has now been cleaned up.
Reference: PBX-3551
🔐 TLS Certificates Now Generate Correctly for All Users
Some users on version 6.0 had problems with missing or invalid TLS certificates, which affected secure SIP registration and encrypted audio.
This issue has now been resolved.
Reference: PBX-3654
📈 More Accurate Call Detail Reporting
We’ve made two key improvements to the Call Detail Report:
- Transferred calls now display the correct duration when filtered by user
- Calls that go to voicemail now appear in the report, even if unanswered
These updates provide a more complete and accurate view of call activity.
Reference: PBX-3709
🕔 Version 5.7
No changes this week. With most of our efforts focused on version 6.0, updates to 5.7 are now limited to critical or service-impacting fixes.
💻 Desktop Communicator
No new version this week, but we’re wrapping up testing on several improvements that should be ready for release next week.
🔧 Coming Soon – In Final Testing
The following fixes are completed and pending final review:
- Outbound MMS issues from Acrobits softphones (under live test with Asterisk patch)
- Call quality report adjustments (fixes unregistered peer count)
- User API now returns proper permission-denied status codes
- Cleanup and clarification in SMS campaign registry interfaces
👀 In Progress or Under Investigation
These issues are currently in development or under active investigation:
- SMS campaign forms rejecting punctuation in opt-in messages
- Login logs bloated by silent background SMS activity
- “Follow Me” calls being misclassified as external
- Polycom VVX600 park button becomes unresponsive after one press
- Outbound fax email notifications default to off
- Agent state reports overstating time in some scenarios
- Call center login time doubled in certain edge cases
References: PBX-3668, PBX-3661, PBX-3605, PBX-3627, PBX-3678, PBX-3732, PBX-3734
ℹ️ Other Notes
We also investigated a support ticket related to conferencing on Polycom VVX phones. The issue was caused by codec negotiation failure when a video-capable handset initiated a conference using SRTP/TLS.
We were able to resolve the problem by changing the preferred video codec from h264 to h263, which is more reliably supported by Asterisk.
To apply this, go to:
System → General Settings → Handset Options → Video Codec Precedence
No code changes were needed in this case.
Thanks for reading and for your continued trust in DLS.
If you have questions about anything in this release — or want to discuss how features apply to your environment — we’re here and happy to help.
– The DLS Development Team 🛠