Dear DLS Customers,
We missed publishing last week’s update, so this message includes two weeks of development and maintenance updates covering changes through May 20, 2025 .
As of:
- May 13, 2025, 11:06 PM – PBXs updated from v6.0.25 to v6.0.29
- May 20, 2025, 11:08 PM – PBXs updated from v6.0.29 to v6.0.32
Version 5.7 remains at 5.7.87 with no changes. Desktop Communicator was updated on May 14 and unchanged on May 21.
🔍 Update Overview
- Bug fixes for outbound Caller ID consistency, voicemail deletion links, API media access, and queue login behavior.
- New system settings for reporting behavior and updates page reliability.
- Salesforce Integration fixes and enhancements for call data, formatting, and logging.
- New Platypus ticket references are included alongside Jira numbers for customer-submitted issues.
🐞 Key Fixes & Features (6.0.26–6.0.32)
📞 Caller ID Fixes and Routing Improvements
- Incorrect Caller ID display: Polycom and Yealink phones were showing wrong caller ID after parking lot pickups. Change reverted, and feature re-opened for proper handling. (PBX-3433)
- Bridged call inaccuracies: Extensions calling through panels or click-to-dial showed wrong caller name or ID. Fixed to show correct originating info. (PBX-3515)
- Outbound call ID loss: In some outbound calls, the callee saw “Anonymous” even if it shouldn’t have. This happened due to how PBX routed these calls with “Dial Outbound.” Fixed with better SIP header control. (PBX-3518)
- Caller ID forwarding fix: On Verizon and others, forwarded calls were not preserving the inbound caller ID. SIP Privacy headers now ensure proper display. (PBX-3506, PLAT-340524)
⚙️ FastAGI, Logging, and Voicemail Behavior
- Stuck channel resolution: A FastAGI issue caused a channel to become unkillable without restarting Asterisk. This rare bug is now resolved. (PBX-3504)
- Voicemail deletion links: Email-based delete links broke if the message was moved from INBOX to OLD. This is now handled correctly. (PBX-3523)
📊 Reporting and Queue Behavior
- Summary report fix: Clicking “View Call Details” returned “Unknown report job ID” due to browser path issues. Fixed. (PBX-3498, PLAT-340518)
- Agent login inconsistency: Queue agents weren’t properly logged out during 6.0 upgrades, preventing them from receiving calls. The upgrade sequence was adjusted. (PBX-3530)
🔗 Salesforce Integration Enhancements
- Dialer input sanitization: Phone numbers with parentheses or dashes now work in the Salesforce dialer. (PBX-3476)
- Task “Due Date” population: Tasks from missed or completed calls now correctly include due dates. (PBX-3476)
- Call duration display: Task subjects now show the length of the call, aiding follow-up prioritization. (PBX-3476)
🛠 System Settings and API Support
- Reporting setting: You can now set “Launch Reports in Background” as pre-checked by default. (PBX-3493)
- Update page optimization: Long-running PBX updates now execute in the background to avoid timeouts. (PBX-3492)
- API media access fix: Desktop Communicator could not access call recordings once they were converted to .mp3. This is now supported. (PBX-3536)
- Unlock login log bug: Unlocking user sessions failed for users with invalid tenant references. The behavior is now corrected. (PBX-3525)
🧭 Upcoming Features and Fixes
- Operator panel: queue call visibility fix (PBX-3522)
- Agent login panel issue in 6.0 (PBX-3509)
- Presence bug in Desktop Communicator (PBX-3488)
- Scheduled reports broken in 6.0 (PBX-3532)
- Billing tenant mapping to Customer Rate IDs (PBX-3531)
- Campaign Registry document upload flow (PBX-3473)
- Improvements to DB replication visibility (PBX-3350)
- Inbound anonymous calling fix now reapplied and validated (PBX-3491, PLAT-340498)
📎 Version 5.7
No changes were made to version 5.7. Development is focused on 6.0 unless urgent issues are reported.
💻 Desktop Communicator
- v2.3.61 (May 14): Resolved hangup/cancel issue for outbound calls and added screen reader support via ARIA labels.
- No update for May 21.
Thanks for reading and for your continued support.
– The DLS Development Team