Subject: DLS Hosted PBX Update – August 2025
Hello from the DLS Developer Dungeon,
We’ve been heads down for a few weeks, deep in the code caverns, fighting bugs and tinkering with features. Thanks for your patience during the silence — hopefully the wait is worth it. This update brings together three recent releases into one big package of fixes, improvements, and a few quality-of-life upgrades some of you have been waiting for.
Overview
- All 6.0 PBXs have been updated from v6.0.58 → v6.0.61
- 5.7 PBXs remain stable at v5.7.89 (no version change)
- The Desktop Communicator has been updated from v2.3.68 → v2.3.71
To Be Upgraded PBXs
- Upgrades were paused earlier this month to focus on stability.
- As of August 20, we have resumed 6.0 upgrades for larger PBXes.
In-Depth Changes
6.0.59
(August 5)
- PBX-3742 – Duplicate SMS Threads in Acrobits Softphone: Fixed an issue where contacts with commas in their Caller ID (e.g., “Doe, John”) caused SMS history to split into two separate threads. Outbound replies failed from the secondary thread. Messages now display in a single conversation regardless of punctuation in contact names.
- PBX-3655 – Campaign Registry Supporting Documents: Improved the campaign registration process. A new notification guides users to add supporting documentation (opt-in forms, terms, privacy policies) after the campaign is created, avoiding confusion.
- PBX-3676 – Opt-In Keyword Handling: Fixed an issue where punctuation or line breaks after “YES” or “START” prevented opt-in forms from saving. Campaigns now correctly recognize keywords even with punctuation.
- PBX-3093 – Yealink SRTP Provisioning: Resolved a bug where Yealink handsets with SRTP enabled failed to download PEM/CRT files during provisioning, causing unnecessary log bloat and configuration retries.
- SMS in Desktop Communicator: Fixed a bug where outbound SMS/MMS messages showed as stuck in “sending…” even though they were successfully delivered. Status updates now display correctly.
- PBX-3745 – MMS Delivery to AT&T/Verizon: Outbound MMS messages to some AT&T and Verizon recipients were failing due to 1MB size limits. Added automatic compression for large image attachments, ensuring MMS delivery across all major carriers.
- PBX-3544 – User API Authentication Responses: Updated API behavior to properly distinguish between 401 Unauthorized (invalid token) and 403 Forbidden (insufficient permissions). This also improved Desktop Communicator by preventing incorrect “yellow icon” alerts.
- PBX-3678 – Default Fax Notifications: New PBX installs now have fax success/failure notifications enabled by default. Existing installs retain current settings but can be updated manually.
Desktop Communicator v2.3.68
- Added virtual scrolling for large lists (contacts, calls, messages, voicemail, faxes) to improve load times.
- Implemented client-side caching of API results, reducing PBX load and speeding up local navigation.
- Enhanced error logging to display explicit API errors, making troubleshooting easier.
6.0.60
(August 13)
- PBX-3235 – Queue Manager (QMAN): Staff can now terminate active QMAN jobs directly from the Web UI, eliminating the need for command-line access.
- PBX-3709 – Duplicate Call Recordings: Corrected a bug that created duplicate call recordings. Call detail reports now show a new recording symbol that opens all recordings associated with a call (e.g., transfers).
- PBX-3723 – Contact Encoding: Fixed an encoding issue where contacts with Cyrillic or non-Latin characters appeared as “???” in Desktop Communicator. Database and UI updated to fully support UTF-8 characters.
- PBX-3725 – Commas in Usernames: Fixed a bug where commas in user names caused voicemail configuration issues by being misinterpreted as field separators.
- PBX-3732 – Agent State Summary Report: Corrected inflated duration times when report end dates exceeded the current time. Also resolved edge-case counting errors.
- PBX-3734 – Agent Performance Detail Report: Fixed a defect that doubled agent login times in reports.
- PBX-3737 – Polycom VVX Feature Keys: Fixed a bug preventing BLF keys from showing when “Hide feature codes” was enabled. Keys now display correctly as BLF or Speed Dial depending on settings.
- PBX-3749 – Report Scheduler Errors: Fixed an error where reports with no results silently failed to send. Reports now complete gracefully, even if empty.
- PBX-3756 – Missing Call Reports: Corrected an edge case where reports spanning certain date ranges returned no results. Timestamp parsing was fixed to ensure all calls are displayed.
Desktop Communicator v2.3.69 → v2.3.71
- Added lazy loading feedback for large data sets.
- Improved keyboard navigation and accessibility (tab order, focus fixes, labeled inputs).
- Fixed Missed Call filter (PBX-3750): All missed calls now display, not just those routed to voicemail.
6.0.61
(August 19)
- PBX-3111 – Call Report Cleanup: Fixed incorrect locality icons (all calls marked “Local”), restored missing international calls, aligned Web UI and exports, and reintroduced hairpin call visibility consistent with 5.7.
- PBX-3661 – Login Log Flooding: Fixed an internal issue where monitoring scripts generated excessive login entries. Tokens now persist for 30 days, reducing noise.
- PBX-3724 – Call History Limits: Fixed a bug where the User API limited call history to 100 records. Now respects PBX settings for “Quick Access Call History” days. Desktop Communicator users will see more complete call history.
- PBX-3729 – Campaign Assignment Errors: Fixed an issue where PBX UI showed DIDs assigned to campaigns, but assignments failed at the carrier level once the 49-DID cap was reached. UI and backend are now in sync.
- PBX-3731 – Echo Tests in Reports: Restored visibility of echo test calls in call reports, a key staff diagnostic tool.
- PBX-3741 – Opt-In Failures: Fixed an issue where customer replies like “YES.” (with punctuation/whitespace) did not add them to campaign opt-in lists.
- PBX-3757 – White-Label Redirects: Fixed a bug where POST requests in white-label deployments defaulted to the base host URL instead of the configured custom domain.
- PBX-3765 – Report Scheduler Failures: Fixed an edge case where column mismatch errors caused Queue Call Reports in HTML/PDF to fail. Reports now generate reliably.
Upcoming Fixes & Improvements
- PBX-3762 – Queue Reports: High-priority fix for missed calls not being consistently counted in specific queue strategies.
- PBX-3746 – Login Page Caching: Optimizations to reduce PBX load during brute-force login attempts.
- PBX-3730 – SMS Phone Numbers Database: Correcting a missing column that prevented updates from syncing.
- PBX-3728 – Salesforce Calls in Reports: Ongoing fixes for call records missing from reports when originating from Salesforce softphones.
- PBX-3755 – Opt-In Retry: Planned feature to automatically retry failed opt-in message deliveries.
- PBX-3675 – Caller ID Prepend: Fix for Cloud Softphone on Android not displaying CID prepends.
- PBX-3691 – eFax Signatures: Fix for fax signatures not being stripped as configured.
- Desktop Communicator Enhancements: Continued performance improvements, UI responsiveness tweaks, and expanded accessibility features.
Summary
The past three releases addressed a wide range of issues — from reporting and SMS/MMS reliability to API stability and UI usability. With upgrades now resuming, we are monitoring closely to ensure these fixes translate into improved day-to-day reliability for all users.
Thank you again for your patience during the recent gap in communications. We are committed to returning to regular updates moving forward.
— The DLS Team