DLS Hosted PBX version 6.1 - Released April 15, 2026

Current release: 6.1.7 (September 16, 2026)

DLS Hosted PBX 6.1 brings a redesigned, responsive web interface, voicemail and call transcription with call summaries, the Mobile Communicator, Desktop Communicator improvements, a guided SMS campaign registration wizard with hosted opt-in pages, personal call blacklists, and an expanded User and Systems API.

• More programmable keys on Yealink handsets. Supported T4x and T5x models can now use their full multi-page key capacity (for example up to 27 keys on a T46 or T54W, and 15 on a T41/T42), reached with the phone's page button, instead of being limited to the first page.

• Added personal blacklists. Users can now create and maintain their own list of blocked numbers, in addition to the system-wide blacklist an administrator manages. Personal blacklists can also be managed through the User API, which allows the Desktop Communicator to offer call blocking directly.

• Improved the Call Routing page for office-hours groups. A routing step that depends on an office-hours group now shows whether it is currently active or inactive, the same way steps that use a single office-hours rule already did. Clicking an office-hours rule or group from the Call Routing page now opens the current Office Hours page instead of the retired one.

• Voicemail transcriptions are now available through the User API. Voicemail responses include the transcription when one exists, and requesting a voicemail that has not been transcribed yet triggers the transcription and returns it. Applies to PBXs with voicemail transcription enabled.

• Call recording transcription. Recorded calls can now be transcribed and their transcripts viewed from the call details, with transcription retention configurable separately from recording retention. Transcription is enabled per PBX; contact DLS to have it turned on.

• Voicemail transcription in Apps → Voicemail. Each message now has a transcript icon next to the play and download buttons, the voicemail list can be searched by keywords or phrases, and a voicemail notification email can be resent from the page. The transcript option is hidden when transcription is not enabled for the PBX.

• Follow Me is now available through the User API. Applications can see whether Follow Me is enabled for a user, turn it on or off, read and update its selective hours, and check the current Follow Me status with those hours taken into account. The Desktop Communicator is notified whenever Follow Me changes so its display stays in sync.

• Yealink T46G handsets can now use all 27 programmable keys across three pages.

• Redesigned web interface. The DLS Hosted PBX web application now uses a single, modern front-end throughout: one consistent header, sidebar and login, standardized forms, tables and dialogs, and layouts that adapt to smaller screens. White-label branding is preserved. Pages are being migrated to the new framework progressively, so a few screens may still carry the previous look until they are converted.

• Clarified the Call Routing configuration form. It is now obvious how to return from a step's configuration to the action selection, and the correct tab is highlighted when editing an existing step.

• Systems API: added read-only Call Records endpoints. Administrators can retrieve call detail records for their tenant with the same date, caller, callee and other filters the Reports → Call Records page offers, scoped by the caller's report and user permissions.

• Guided SMS campaign registration. Registering a 10DLC brand and campaign is now a step-by-step wizard with an AI assistant that helps write the campaign description, sample messages and opt-in details in the form the registry expects, followed by a DLS staff review before submission. Rejected campaigns can be corrected and resubmitted from the same screen.

• Hosted opt-in pages for SMS campaigns. DLS now hosts a public opt-in page for every registered campaign, organized under a brand page that carries the shared privacy policy and terms. The page address is reserved while the campaign is being drafted and is included in the campaign's call-to-action, which addresses the common "opt-in not findable" rejection during carrier review.

• Call transcription details expanded. The information extracted from a call transcription is now shown in the call details pop-up, in addition to the sentiment and sentiment reason that were already displayed.

• Call summaries: extracted data in the Metrics tab. When call summaries are enabled, the data points identified in a call (which vary by the industry persona configured for the user or queue) are listed in the Metrics tab of the Apps → Call Recordings pop-up, with a tooltip describing each field. A field is shown only when the detail actually came up in the call.

• Shared extensions can now have keys in their base configuration, before any user is logged in. This lets a shared-login feature key sit in the same place on every shared phone, so a user can press the key to log in instead of dialing the feature code.

• Restyled the Users → Groups page to match the redesigned interface. Adding users to a group keeps the pop-up selector with search and checkboxes introduced in 6.0.

• Added support for the Poly Trio C60 conference phone.

• Improved the text-to-speech voice used by the voicemail menu and feature codes such as the weather forecast. Prompts are now read with a steady, even inflection instead of the disjointed delivery some users reported.

Version 6.1.5 - Released September 2, 2026

• Attended transfers now carry the original caller ID to the destination. When a call is announced and transferred, the receiving phone shows the caller's number rather than the transferring extension, so the recipient can return the call if needed.

• Resolved an issue where provisioning the Acrobits softphone by scanning a QR code failed with an "invalid username and password" error on 6.1 PBXs.

Version 6.1.3 - Released August 19, 2026

• Apps → Desktop Communicator now offers an MSI installer for Windows, which simplifies deployment through group policy and other software distribution tools.

• DB Access now exposes the call recordings table, so customers who query their PBX database directly can report on recordings. The transcription text column is not included in this table.

DLS Hosted PBX version 6.0 - Released March 11, 2025

Current release: 6.0.114 (September 16, 2026)

DLS Hosted PBX 6.0 is the platform release that moved every PBX to Asterisk 18 and a rebuilt web application. Highlights include a new reporting engine with background report generation and a Report History page, Microsoft Teams integration for the Desktop Communicator, an expanded User API, call recording and voicemail transcription, the new Systems API for administrators, routing loop detection, and support for newer HP Poly and Yealink handsets. Weekly maintenance builds since March 2025 are listed below.

Version 6.0.114 - Released September 16, 2026

• Resolved a permissions gap on shared virtual PBXs where giving a client access to reporting could expose calls belonging to other clients when no user filter was applied. Report results are now limited to the client's own users.

Version 6.0.111 - Released August 26, 2026

• Custom agent pause reasons. In addition to the built-in reasons such as Break and Meeting, queue administrators can now define their own pause reasons (for example After Call Work or Voicemail), which are available to agents and reflected in the queue reports.

Version 6.0.110 - Released August 19, 2026

• Resolved an issue where logging into a shared extension did not take effect until the phone was rebooted.

• Resolved a discrepancy between the Queue Activity Summary and the Queue Calls reports, which could disagree on the number of answered calls for the same period.

Version 6.0.108 - Released August 5, 2026

• Resolved an issue where the column selection saved with a custom report was not restored when the report was reopened, so the columns had to be re-selected on every run.

Version 6.0.107 - Released July 29, 2026

• Resolved a secure-audio (SRTP) handshake failure on Polycom SoundPoint IP 450, 550 and 650 handsets by updating the TLS certificate setting those phones are provisioned with.

• Added a Handle NAT option to SIP peers. It is on by default and corrects call setup for gateways that advertise a different address than the one they actually send from; it can be turned off per peer where it is not wanted.

Version 6.0.106 - Released July 22, 2026

• Cisco SPA 504G handsets can now use all four of their programmable keys; previously only two could be assigned.

• Resolved an issue in shared SMS inboxes where a picture (MMS) message sent by one agent was visible only to that agent and the recipient. Every agent in the shared conversation can now see it, in the Desktop Communicator and through the API.

Version 6.0.103 - Released July 1, 2026

• Call summaries for users and queues. Users whose plan includes AI features can enable call summaries in Users → Preferences, and queues can override that setting and choose the industry profile used to summarize their calls. Summarized calls include highlights and extracted data points; calls without a matching profile receive a general summary.

• Apps → Desktop Communicator now offers separate Apple silicon (ARM) and Intel downloads for macOS, so users on newer Macs get the native build.

Version 6.0.102 - Released June 24, 2026

• Call reports can now be restricted to defined office hours. Choose an office-hours rule or group when generating a call report to see only the calls that took place during those hours, for example weekdays 7am to 6pm excluding holidays, without exporting and filtering the full report by hand.

• Systems API: added Music on Hold endpoints. Administrators can read, create and update music-on-hold groups, upload, remove and reorder their audio files, and configure stream-based groups.

Version 6.0.100 - Released June 10, 2026

• Systems API: added Office Hours endpoints. Administrators can list, create, update and delete office-hours rules and office-hours groups, following the same permissions as the web interface.

Version 6.0.99 - Released June 3, 2026

• Added a security measure to prevent constant URL redirects when a PBX is attacked with many HTTP requests. Previous to this release, a PBXs resources could be strained if a malicious actor attempted to reach the PBX with various HTTP requests to a resource on the PBX that did not exist, which would cause the PBX to redirect the request to the login page, which would run a query in the background each time. We have prevented this vulnerability by responding to requests to non-existing resources with a proper HTTP 404 response.

Version 6.0.88 - Released March 11, 2026

• Call recording transcription. Recorded calls can now be transcribed and their transcripts viewed from the call details, with transcription retention configurable separately from recording retention. Transcription is enabled per PBX; contact DLS to have it turned on.

Version 6.0.81 - Released January 21, 2026

• Resolved an issue that caused acrobits softphone users to be unable to see some or all of their contacts/company directory due to a failure to pull various configuration files from the PBX during the provisioning process. This fix has removed a reoccurring error in our error logs as well as providing a more stable and consistent user experience for acrobits softphone users.

• At a customers request, we have now added support to add a background/wallpaper on a Yealink T46S device. This can be done via the System->Phone Logo page on the PBX web UI. The Yealink T46S handset supports PNG or JPEG images with 4-bit grayscale or monochrome at a 236x82 scale.

• Resolved an issue reported by the support team where blacklists were not blocking anonymous/restricted calls when they were defined in the blacklist. We found that an anonymous call may have a specifically formatted identifier that we were not catching in the blacklist check. We have added this to our fix. Please notify the development team if blocking anonymous calls via system->blacklists is still an issue.

• Improved the System->Recordings page to specify what is wrong with a provided audio file when the page fails to properly upload the recording. Additionally, we have improved the conversion logic on this page so that most, if not all, WAV files will be converted to the proper format on this page, leading to a successful upload. Previously, some WAV files would outright fail to upload due to specific file headers missing, but these files could be converted to the right format. We have removed this condition to let the recordings page to attempt converting these types of file before rejecting it for upload.

• Improved the Microsoft Teams Integration page under the System tab to properly mask the client secret id value when viewing or editing the registration details for the Teams integration. This was done to help make the page more security/privacy conscious. This change has no affect on the registration or synchronization functionality with the Microsoft Teams environment and the PBX.

• Resolved an internal issue where a log stating available endpoints was not populating. This issue had no effect on availability or registration status for any users. This was simply a code maintenance bug.

• Resolved an issue where newly created tenants would cause a “features_{tenant name}” call routing branch to show up in the drop down under System->Call Routing. These branches would also show up for other drop downs where a call routing context is chosen. These branches are important contexts for Asterisk. However, these branches are not meant to be viewable or directly editable by the web ui. We have resolved this issue moving forward and have also retroactively fixed pre-existing features contexts that have this issue as well.

Version 6.0.80 - Released January 14, 2026

• Fixed a non-critical issue where the Asterisk console log would show readers incorrect queue/agent statistics when a user paused or unpaused in their queues. For example, the console would show that the user was logged in and paused in only 2 queues, when in fact they were logged into 10 queues and paused in 10 queues. However, this was a purely a display bug and did not affect end users in any way.

• Resolved an issue that some clients reports where their Music On Hold files were not found or another Music On Hold group was played when Music on Hold was triggered. This occurred only when the Music On Hold group in question was the most recently added group. In this scenario, Asterisk did not properly detect, and therefore load in, the new music on hold group to use.

• Fixed an issue where queue callback was not working on queues that configured the “Caller ID” setting in the Queue Callback section in the Users->Queues page to “Unset”. In particular, the callback request back to the originating caller did not reach the caller. This was a bug that occurred for queues created before it was possible to set the caller id field on a queue configured with queue callback. Now, if this setting is set to ‘Unset’ then the queue will use the system default number for the caller id to use when calling a user back for a callback request.

• Added the ability to filter Queue Calls by any disposition or combination of dispositions in the Queue Calls Report. Previously, the only disposition filtering that was supported was via a “Only Display Answered Calls” toggle. We have now removed this option and replaced it with a multi-select box that allows users to specify one or more specific dispositions to filter by.

• Resolved an issue where the Summary Report of Groups and Condensed Summary Report of Groups reports in Reports->Calls were not showing any results. We discovered that the report page was not passing along any group ID info, and this is why the report always yielded no results.

  Alongside this fix, we also fixed two small issues in the Queues Reports. First, hold time was showing inflated values for missed queue calls. Second, the timestamps on a queue call would differ from the timestamps present for the same queue call in the queue log call details. This occurred for any PBXs that were in a different timezone other than CST.

Version 6.0.79 - Released December 24, 2025

• Added marginal improvements to call report generation times by 10 to 15% on version 6.0 of the Hosted PBX. This was done by removing obsolete parameters the the call reporting query, which was a remnant from the call reporting engine in 5.7.

• Added the ability to enable or disable video calling for users assigned to handsets that support video calling. The "Video Calling" setting can be found in Users > Preferences under the Handset Options section, below the SRTP/TLS setting. This option only appears for handsets that support video calling, which include:

  Grandstream: GAC2500, GXV3000, GXV3140, GXV3175, GXV3275

  Polycom: Edge Series, Trio 8800, VVX501, VVX600, VVX601

  Yealink: SIP-T58A, SIP-T58W, VP530, VP59

  Cisco: 8945

  Enabling this setting means that the handset will attempt to initiate video calls wherever possible. Support and users may find this setting helpful in troubleshooting call failures due to video codec issues.

• Resolved an issue for Polycom phones where speed dial keys would not appear on VVX models if the user configured a personal contact to one of their keys, and that personal contact matched a global contact on the PBX. This was a problem because the Polycom handsets do not like duplicate contacts in the user directory on the handset. In this case, both contacts were being loaded into the user directory, but the global contact took precedence and the personal contact did not load. However, the speed-dial configuration referenced the personal contact, which is why the key on the handset failed to reference.

• Fixed an issue preventing PBX administrators from enabling inbound SMS for users. Previously, administrators couldn't set the "Default SMS Sender ID" field in User → Preferences if the phone number lacked an active TCR campaign. This blocked users from receiving SMS entirely. However, TCR campaign requirements only apply to outbound SMS. To address this, we've removed the campaign check for inbound SMS configuration. Now, administrators can enable SMS for users with numbers that have SMS capability but no active TCR campaign. These users can receive inbound SMS but cannot send outbound messages. Our documentation has been updated to reflect this limitation.

Version 6.0.78 - Released December 17, 2025

• Removed the defunct Offer Feedback button on 6.0 PBXs as this button attempted to redirect users to our local Jira instance, which is no longer used anymore. Devops reported that on some production machines, this would cause the web UI to overuse system resources whenever the button was clicked due to repeated failed redirects. We will consider re-adding this functionality in 6.1 for users who do want to use the offer feedback option, however this feature has not been used since 2021.

• Resolved an issue where users were not able to delete some tenants on multi-tenant PBXs despite the fact a green success message would show after attempting to delete the tenant in System->General settings. The issue was caused by a foreign key constraint that failed to throw an exception when encountered. We have now added extra checks to catch these exceptions and to notify the user via an error message about what next steps need to be taken to correctly remove the tenant.

• Resolved an issue on the Call Routing Reports where timestamps on the call records in the report would disagree with the timestamp for the record when looking at the call details. This occurred on PBXs whose timezone differed from central standard time.

Version 6.0.77 - Released December 10, 2025

• In this release, we removed admin emails from the list of recipients for call recording storage capacity warnings at the request of the operations team, since several customers were complaining about receiving this email. Support and operations will still receive this email, to handle on a case by case basis.

• Resolved an issue where the Summary Report for Fax Reports would fail to generate under all circumstances. Users experienced a “Whoops! We seem to have hit a snag. Please try again later…” error message whenever they tried to generate that report. This has now been resolved.

• Resolved an issue where nightly cron jobs were spawning errors that were sent to the operations team about voicemail files failing to move to the archive directory in the file system. Some customers may now notice that some of their voicemails may have been archived, as the voicemail archiving feature should now be working properly.

• Resolved an issue where users were unable to edit some settings on their extensions in Users->Preferences. This was a bug caused by changes presented in 6.0.76, which have now been reverted. Users who are still experiencing this may need to reset their browser cache via a ‘hard refresh’ to fix this issue.

• Added the ability to allow staff to configure E911 profiles for DIDs that have not fully ported into the DLS environment. Due to a previous feature that allows customers to use/spoof their own DIDs that we do not own, E911 profiles can only be configured for numbers that are owned by DLS. This has caused a hiccup in the PBX on-boarding process where profiles need to be set before a DID ports. Moving forward, if staff runs into this issue, they can now override this by putting the PBX in upgrade mode and then creating the E911 profile.

Version 6.0.76 - Released December 3, 2025

• Resolved an issue emails created from the SMS to Email feature were showing a DLS logo for white-labeled tenants on a PBX. In this patch we also aimed to find any other locations containing hard-coded mentions of DLS or hard-coded usage of DLS logos and removed them or updated the code to dynamically update if the tenant/pbx is using the white-labeling feature.

• Resolved an issue where the Condensed Summary of Extensions report in Call Reports showed different results when generating the report with a user filter vs, generating the report without any user or group filter. The issue that was reported was that a user was showing far more calls in the Condensed Summary report when the report was ran with the user in the user filter options. The discrepancy was coming from calls that led to a dial group call. These calls would be associated to a user, even if they didn't answer it, which would be counted in the condensed summary report, when filtering by that user.

• Resolved an issue where inbound calls that never reached an extension were not showing up in the call detail report. This issue was discovered when calls that led immediately to a congestion tone did not appear on the call reports for admins that were not filtering by any users or groups. These calls previously did show up in version 5.7 and prior, but were unintentionally hidden on 6.0. Now, users with view permissions on a phone number can view inbound call records to this number that did not reach a user in the call’s history.

• Resolved an issue in multiple reporting pages where report results that included timestamps in one of the columns would not sort correctly by timestamp. Users experienced the sorting to be counter-intuitive, and would often not sort in the expected ‘oldest to earliest' or ‘earliest to oldest’ order. This issue was originally discovered on the call quality report page but the fix was applied to this page and other reports that experienced this issue.

• Resolved an issue where users were sometimes unable to add a new user to Users->Preferences if the user first filled out the user information for a primary extension, and then updated the user type to ‘Mirror’ before saving. The page would not respond to the ‘Save’ action and would not update due to previous filled out fields, which were now no longer visible, stopping the user from saving due to a input conflict. This has now been resolved.

• Resolved an issue where the call detail report would show a call record associated to a user that did not answer the call and had a call recording associated to that record that was not related to that user. This was resolved at the same time as issue PBX-3868. This issue was caused when using extension filters when generating a report. These particular records were not meant to show up for the filtered user, but were because they were associated to the call due to a dial group. This has now been resolved.

Version 6.0.75 - Released November 26, 2025

• Added the ability to enable or disable the following panel call management actions for each individual panel: Allow Whisper, Allow Listen, Allow Barge, Allow Transfer, Allow Transfer to Voicemail.

  Previously, these actions were only configurable at a global level, meaning that the permissions would apply to all panels existing on the PBX. Now, these settings can be configured per panel via the “Use Default Panel Permissions:” setting in Users->Panels. When unchecked, the settings for the specified actions above will be made available to toggle on/off.

  Additionally, we have also added the ability configure the Hangup action, which was previously not configurable in any matter for panels on a PBX.

  Documentation for these changes have been added the the Hosted PBX help manual.

• Resolved an issue where the archiving functionality for voicemails was not working in some scenarios. This issue was first discovered in release 5.7, but has been addressed now in the 6.0 release of the PBX.

• Resolved a small issue with office hours entries that are automatically created during first time PBX install. These office hours entries were malformed, and contained invalid characters which have previously caused these office hours to sometimes not properly execute. We have fixed the initial cause of this issue and have retroactively fixed the pre-existing office hours that already have this issue.

  The affected office hours are the following “Weekday Business Hours“, “New Year’s Day“, and “Fourth Of July”.

• Fixed a backend issue where a particular call tag was malformed for any outbound calls made via the User API. This issue did not cause any noticeable issues for users. This was resolved to avoid any possible future issues.

• Fixed an issue where changes to System->SMS->Phone Numbers were not showing up in the Change Log report. This was because changes to this page were not being tracked directly by the PBX database. This fix is not retroactive, i.e past changes to the SMS->Phone Numbers page will not show up in the Change log. Only changes made after the release of this fix will appear in the change log.

• Resolved an issue where the Channel Event Log was truncated to 20 entries when looking at call details, which meant some channel events were not being show to customers. This occurred because the pagination feature on this page was unknowingly removed during the upgrade to 6.0. We have brought back pagination to this page for the channel event log so that all call details can be investigated

• Resolved an issue with the letsmeet integration on Rocket.Chat enabled PBXs. After a recent upgrade of Rocket.Chat, whenever a user would invoke a new meeting room via the “letsmeet” message, Rocket.Chat would spawn multiple meeting room links. The number of links would range anywhere from 2 to 16.

  This issue has now been resolved. Any PBXs using Rocket.Chat and letsmeet may now resume the usage of the “letsmeet” command in their Rocket.Chat environments.

Version 6.0.74 - Released November 19, 2025

• Resolved an issue where there Call Event Log for a call record from the Call Detail Report would show the incorrect timestamp for the start of a call, when the user that was looking at this report was configured with a timezone other than America/Chicago.

• We were made aware of a customer that was having trouble utilizing the fallout context for their queue. After further investigation, we found that whenever the name for the call routing branch that the fallout context referred to was changed, the fallout context feature for the queue would fail to execute. This was caused by a missing reload of the dialplan configuration whenever a call routing branch name was changed. We have added this necessary reload to the saving logic of the call routing page. it is likely that this will also resolve other rare and difficult-to-replicate issues regarding context accessibility.

• At the request of Support and a customer, we have updated our internal wiki and the PBX help manual with a section on the network access requirements for voice devices to properly communicate with the PBX. This new section can be found under 'Firewall Configuration Requirements' in the help manual.

• We discovered a small bug where it was possible for the Desktop Communicator to encounter service impacting issues whenever the minor version of the Desktop Communicator changed (i.e 2.3.x → 2.4.x) while a user was logged into the Desktop Communicator at that time. This has been addressed by sending a SIP notify to the device on upgrade, so that the Desktop Communicator reloads its configuration to use the changes in the newer version.

Version 6.0.73 - Released November 12, 2025

• Resolved an issue where Fax confirmation emails, as well as inbound fax emails showed up with a ‘DLS Hosted PBX’ logo for customers with white labeling enabled and a custom logo configured. In these cases, the emails should contain the custom logo defined by the customer in the System->White Label page.

  The issue was introduced in the 6.0 version of the Hosted PBX.

• Resolved a few minor styling issues on the view and edit forms in the System->SMS->Phone Numbers page. The table that contained the SMS phone number information was vulnerable to broken styling whenever a phone number was set with a long description. In detial, the table would extend past the provided container the page was configured with. This was resolved by truncating long descriptions visually, while providing an on-hover title that users can use to read the full name of the description.

• Resolved an issue where the Summary Report of Extensions report would fail to generate if the user chosen in the extension filter was not a member of any group on the PBX. This was caused by the logic that aimed to determine which users to filter by once the user clicked to generate the report. The groups and user filtering options are cumulative, and because only one extension was selected, with “any group” selected in the group filter, this caused an edge case where the report believed that no user was chosen. If other users were added to the extension filter, the report would succeed in generating results, but the results for the group-less user would be missing.

Version 6.0.72 - Released November 5, 2025

• Resolved an issue where the RTCP monitor service, which monitors and serves call quality statistics to the PBX, was not reloaded properly when a new user was added or whenever a users name was edited in the users->preferences page. This would cause inaccurate statistics calculations for call quality reports and notifications until the next time the RTCP monitor service was reloaded.

• In this release, we added support to the PBX to allow clients to use DIDs that we do not explicitly own with Voip Innovations for their outbound caller ids.

  When making calls outbound with these numbers, they will be signed with STIR/SHAKEN attestation B. All other calls will be signed with attestation A.

  These changes also include safeguards in the SMS phone Number and E911 configuration pages to prevent users from using these DIDs for those purposes.

  Staff may see warning messages in the PBX web interface stating that a number’s carrier could not be verified. These messages may appear when a DID is pending removal and no longer managed by our upstream carrier, or in other cases, may be an active DID that does not have a listed association to a carrier on DLS' side.

• Resolved an issue with the Summary Report of Extensions report where the secondary call detail report from this page, accessible via the “View Details” button, would fail to export when a user requested to do so. The page would show an error about an invalid report ID error. The error was caused by a malformed URL that was sent for the request.

• Resolved an issue where filtering call reports by disposition would result in incorrect results. We received a report from a customer that an answered call was showing up in call reports when filtering by “No Answer”. This occurred whenever a user had a primary and a mirror extension registered when taking on an incoming call. When the user answered with one of their extensions, the reporting engine would notate that the other extensions did not answer it as well. This is intended and provides specific detail when looking at call event logs. However, this logic was also used for filtering by disposition in the call report, which was not intended. This has now been resolved.

• Resolved an issue where the 'Retention period for reports history' setting in System->General Settings was not being honored due to a purging script that was failing on every call. This caused various database records and report job files to back up in the back-end. No affect to users other than marginal improvement to storage on PBXs.

• Fixed an issue where queue calls that left a queue when they reached the maximum wait time were not counted in the Queue Activity Summary report. In particular, these calls were meant to be counted in the unanswered section of the report but in fact did not due to a backend oversight in how the calls were designated ‘unanswered’.

• Resolved an issue where the Queue Activity Summary report was not calculating hold times correctly. Note: Hold time refers to the amount of time a caller waits in a queue before the call leaves the queue (either answered by an agent or caller leaves the queue).

  Previously, hold time was only calculating the time it took before an agent answered a call. Now, the report counts the amount of time a call waited before abandoning the queue, either explicitly or due to timeout.

  This behavior matches with the Queue Service Level report.

• Fixed an issue with the Queue Service Level reports where the “Time Slice Interval (seconds):” and “Maximum Shown Time Slice (seconds):“ were not honored in the generated Queue Service Level report. This was an issue introduced in the 6.0 upgrades due to how reports are generated in the backend.

  These filtering options, which were only accessible after the report was generated, have been moved to the main filtering page for the report, and can be applied before the report is generated. This was done to keep report filtering consistent across all reports. This also allows users to set this values in their report templates for this report.

• Resolved an issue where, for a brief time, PBX administrators were not able to access the Reports->Call Quality page even when their permission profiles had this page set to ‘admin’ permissions. The issue was occurring because this page was accidentally treated as a staff only page. For the same reason, the system->call quality page was also inaccessible. The issue was introduced in release 6.0.71.

Version 6.0.71 - Released October 29, 2025

• In this release, we improved security measures around staff only accessible resources. Previous to this release, it was possible for users to access staff only resources as long as they new the direct URL path to the page. This has now been patches. This does not affect any customers. Staff will now need to be both logged in as as an administrator, as well as logged into portal with their staff credentials, to be able to access any staff only pages on the PBX.

• Resolved an edge case with handsets that toggled DND via a feature code. Prior to this release, if a user enabled DND with a feature code, they would not be able to remove the DND state with the DND hardkey on their handsets. Now in this release, using the feature key and the hardkey can be interchanged for proper DND enabling/disabling.

• Resolved a back-end issue where some error messages were not being logged to their designated error logs. This change does not affect any customers. Staff will now be able to see any error messages related to failed API requests, or anything that causes a “Whoops, we hit a snag” error on the PBX web UI. The location for this error log can be found in the staff only wiki.

• Fixed an issue where the Agent Performance Summary report was not showing accurate statistics for average talk time for each agent. In particular, almost all agents would show up with 0:00 as the average talk time, when the total talk time was non-zero.

  This also affected the Summary Report of Extensions report in Reports->Calls, for those customers who have queue call statistics added as part of their report results. As a reminder, queue call statistics can be added to the results of the Summary Report of Extensions report by enabling the setting to do so in System->General Settings->Reporting->”Include agent summary statistics in call reports”

Version 6.0.63 - Released September 3, 2025

• Resolved an issue where PBXs that were in a HOLD or SUSPENDED state could not be configured with a billing id. This issue had no affect on billing for customers. This only affected infrastructure that is being set in place to improve billing tracking in the future for various features.

• We discovered an issue where some call records were not accessible in call reports for newly upgraded 6.0 PBXs. This was caused by the nightly purge script that removed old call detail records after the retention period. However, newly upgraded 6.0 PBXs incorrectly concluded that past 5.7 records were past the retention period. Fortunately, these purges were not permanent, and we were able to bring back 5.7 records for affected PBXs as well as prevent this issue from occurring moving forward.

Version 6.0.62 - Released August 27, 2025

• Fixed an issue where Cisco SPA191 devices that were provisioned to a DLS Hosted or Virtual PBX contained the wrong admin password that is used for accessing the device’s web interface. The previous password was not the expected admin password that we use for all our provisioned handsets. This has now been addressed. Staff can visit the internal wiki for more information on specifics on password values for these devices.

• Fixed an issue where PBXs configured with the Microsoft Teams integration feature experienced issues with contact and user syncing. The PBX runs an hourly script that re-syncs any contacts or new users within an organizations Microsoft 365 environment with the PBX. However, this job was failing to execute after the initial Teams set up process. These failures were most notable in the Queue Manager staff page. These failures have now been addressed.

• Fixed an issue where internal calls that included a follow-me step to another extension were incorrectly classified as inbound calls in the back-end database instead of internal calls. While we have not received reports of this causing issues, call reports filtered by call direction may have been affected by this error. Note: This fix applies only to new calls going forward and does not retroactively correct historical records.

• Resolved an issue where the ‘Strip signature from emails' seemed to not be working for some clients. After further investigation, we found that this feature was in fact working, but only for footers/signatures that followed a specific pattern. We have now revised this functionality to attempt to better detect signatures in order to strip them. Alongside these changes, we also added a test script to check if signatures will pass/fail the signature detection algorithm in this release’s changes.

• Improved how Polycom phones request data when pressing the “Application” button on most Polycom Handsets. This feature typically pulls various resources, such as Contacts, Follow Me status, features, voicemail, queue status and more. However, we discovered that whenever this page is accessed on the handset, the PBX has to do several queries each time. This can contribute to heightened resource usage on larger PBXs. We have improved this feature to cache results for a minute (10 seconds for queue status) so that any frequent polling does not add unnecessary querying stress on the PBX.

• Fixed a back-end issue where SMS Campaign IDs were not being properly associated with phone numbers in our billing system.The issue was caused by a missing database column that prevented the PBX from updating DID records with their corresponding Campaign IDs. While the DID numbers table was unaffected, SMS Campaign ID associations were not being stored.

  Note: This issue did not impact customer services or functionality.

• Resolved various small documentation issues in the User API documentation.

  1. Added a deep object declaration to the SMS endpoint documentation

  2. Updated the SMS filter option to allow Unix Timestamps and date-time strings for the To and From parameters when getting SMS results.

  3. The documentation for the Update SMS endpoint contained a trailing space for the “hidden” status value. This has been removed.

• We received a report that call reports were not honoring entries in the phone number filtering input. I.e filtering by NNN-NNN-NNNN did not filter out call records that did not involve that number. This was caused by a fix for a previous issue that was resolve din PBX-3731 where some troubleshooting related call records would not show up in the call reports for staff.

• Resolved an issue where the System->SMS Phone Numbers page was not accessible on the PBX web UI whenever The Campaign Registry was experiencing an API outage. This was due to an unhandled exception in the source code used to load the initial page data when accessing this page. Now, if the campaign registry has API issues again, users will still be able to access the page, but will see a constant error message on the page informing the user of the outage.

Version 6.0.61 - Released August 20, 2025

• In this work item, we resolved various small issues with the call detail reports.

  1. Locality icons will now show the correct locality for each call. Previously, each call showed up with a ‘Local’ icon. Now, national, international, and internal calls will show up correctly with the proper locality icon.

  2. Not all international calls were appearing in the call detail report. They will be now.

  3. There were some inconsistencies with the data present between the WebUI and the report exports for both the Summary Report of Extensions and the Condensed Summary Report of Extensions.

  4. Hairpin calls now show up as they used to in 5.7.

• Resolved an internal issue that caused bloat to our internal login logs due to our SMS monitoring infrastructure requesting logins to the USER API v2 every few minutes. This monitoring infrastructure has now been updated to keep User API Bearer tokens active for 30 days before a re-login attempt. In the cases where the bearer token is lost, or is reset elsewhere, the monitoring script will detect this and re-request a new bearer token.

• Resolved an issue where the User API was silently limiting Call Report results to 100 records in the Get Call Records endpoint when no explicit limit was set. This also affected the Desktop Communicator, which uses the API to retrieve call records. Now, the number of call records returned will be directly related to the 'Number of days to retain quick access call history' setting in System->General settings. This setting will be used to determine the default time span to use when querying the User API for call records when no time range or limit is set on the request. For most Desktop Communicator users, this means that they will now see more records in their call history tab. Because of the use of this setting, we can also be sure that this will not be adding any additional overhead to the PBX.

• Resolved an issue where the System->SMS->Phone Numbers page would incorrectly show that a phone number was assigned to a campaign, yet on our upstream carriers side, the campaign failed to link to the given phone number. This occurred mainly when campaigns reached their DID assignment limit of 49 assignments, in which case our upstream carrier would reject any further assignments. However, the PBX would not track this and would keep the assignment on the PBX side.

• Resolved an issue where echo tests were not showing up in the call reports for staff users. Echo tests are used to ensure outbound calling and two way audio is working as expected on a PBX. In this case, staff were not able to prove a call was established via a call report. This tool is used often during major release upgrades.

• Resolved an issue that prevented users from being successfully added to a campaign's opt-in list when their response to an opt-in message included a whitespace or period after the ‘START' or 'YES' keywords. This resolved an issue for a client that reported that their customers were responding to their opt in messages with 'YES’ but were not automatically opted in.

• Resolved an issue where POST requests did not honor white-label configurations. When white-label is enabled, requests now correctly target the configured custom URL instead of defaulting to the host URL.

• Fixed an issue with the report scheduler where scheduled Queue Call Reports to HTML or PDF format were failing for some customers. This was caused because of a mismatch between number of columns and number of column headers in the CSV file that is used to construct the HTML and PDF documents. This was an uncaught edge case which caused the scheduler to abort, which would mean the report would never send out to its intended user.

Version 6.0.60 - Released August 13, 2025

• Added an improvement to a staff only page which allows DLS staff to terminate running jobs on QMAN (Queue Manager) from the PBX Web UI. This was previously not possible when the job was running, but only when the job was queued to be ran. This will help staff terminate rogue jobs or tasks from QMAN without having to access the CLI utility to do so.

• Reverted changes made in previous releases where some calls were being recorded upon ringing extensions, resulting in duplicate recordings being created. Additionally, since a single call may contain several call recordings, (such as transferred calling) the call detail reports will now show a new recording symbol that will popup a new window for displaying multiple recordings for a call. Note, calls prior to this update will likely have duplicate recordings as a result of a prior bug that is now fixed.

  
  

• Fixed an issue where some users would see multiple question marks in place of contact names on the Desktop Communicator. This was caused by an encoding issue on names containing Cyrillic characters. We have also update the PBX Web UI to support personal contact names with Cyrillic characters and characters of other languages as well. In many cases, attempting to a create a personal character with these characters would break the Apps->Contacts page.

• Resolved an issue reported by Embark where the Agent Performance Detail Report would double the actual recorded value in the “Time Logged In” column.

• Resolved an issue where users with the 'Hide feature codes from handset directory' setting were unable to see feature codes assigned to line keys on their Polycom Handsets. Users should note that these feature keys will appear as BLF keys when the 'Hide feature codes from handset directory' setting is enabled and as Speed Dial keys when that setting is disabled.

• Resolved an issue where scheduled reports that would normally returned empty results would cause a silent error in the script that triggered that scheduled report to be sent out. This did affect customers, although this would only affect reports that yielded no results anyway.

• Fixed an issue where in very rare cases, call reports would return no results over a time range that included several calls. This was caused by a rare instance where an epoch timestamp was interpreted as a datetime string, which would force the reports to use the Quick Access Call History table, which would only retain the last 3 days of call data, for most PBXs. In the cases where the time range was outside this 30 day range, and the rare epoch interpretation occurred, the user running the report would not see any results in their call reports.

DLS Hosted PBX version 5.7

Current release: 5.7.96 (March 18, 2026)

Version 5.7.93 - Released December 17, 2025

• Resolved an issue where Call Quality reports would return empty results for PBXs that had a remote database configured. This affected 5.7 PBXs only.

Version 5.7.92 - Released December 10, 2025

• Resolved an issue where users on a 5.7 PBX were unable to retrieve call recordings from the User API when the call recording that was being retrieved was named with an mp3 extension. Call recordings ending in .wav were still accessible. This has now been resolved.

Version 5.7.91 - Released November 4, 2025

• Fixed an issue with the API V1 reporting endpoint on PBXs that had remote database querying enabled. The reporting endpoint in question is https://{pbx}.pbx.dls.net/api/v1/reports.php. Previous to this release this endpoint would always run call report queries directly on the local db instance. This is typically fine, but some PBXs have remote database configurations because these call reports can god down the system. In this release, these call report queries will run on a remote database if the PBX is configured to do so.