Release highlights

Starting with this release, all inbound SIP traffic will be denied by default unless the source IP address is configured on the Access Control List page.

The Access Control List page allows you to specify individual IP addresses or CIDR blocks of addresses that will be allowed for unlimited inbound SIP traffic.

Two more help buttons have been added to the user interface.

The following two modal windows now contain help buttons leading to the appropriate article in the Documentation portal:

• Edit Data Set Template
• Edit Role

We continue to make incremental security upgrades to ensure the highest compliance with security standards.

Resolved issues

Registration webhooks can now be sent for callbacks registered via API.

For any callbacks registered via API, registration webhooks were not sent. We have made an update to ensure that these callbacks can trigger registration webhooks the same as callbacks registered via voice.

We have resolved an issue affecting the voice experience when callback registration is disabled.

When callback registration is disabled, several audio prompts are played in succession, one of which should be Please try calling us again in the Connecting section of the associated Media Set.

After deprecating the customer speech input feature in a recent release, we found that the voice experience in this scenario attempted to play a similar prompt from the deprecated Speech section instead.

Custom audio files that are used in more than one Media Set will now remain available if they are removed from a single Media Set.

Previously, if a Media Set containing a custom audio file was cloned at least once, and then the audio file was removed from one of the Media Sets using it, the file would be deleted from storage and would not be usable by the other Media Sets.

We have updated the logic behind deleting custom audio files to ensure that they will not be deleted if any Media Sets still use them.

Two issues affecting the Reporting Category filter on Insights dashboards for some organizations have been resolved:

• Some reporting categories failed to populate in the Reporting Category filter.

• Some reporting categories showed no calls, even when calls were present.

Messaging keywords (@cancel, @callme, etc.) will now function when extra whitespace is present.

Previously, if a customer sent a message with a keyword containing extra spaces before the text, the keyword would not be recognized. We have updated the logic behind identifying keywords to ensure these messages are processed as intended.

We have identified and addressed two causes of stuck calls.

A stuck call occurs when a call state has progressed in reality but our records failed to update to reflect the change. By resolving two underlying causes of this issue, the number of occurrences should now be lower.

We have improved validation for Contact Center CSV uploads.

We have resolved several errors that could occur when uploading a CSV file on the Contact Center page. Previously, the system would incorrectly reject files containing certain valid configurations. With this update, the upload process now correctly handles more complex scenarios.

This update ensures the following configurations are processed without errors:

• Duplicate records will now correctly overwrite existing records instead of producing an error.

• Queues with identical Queue IDs are now permitted, as long as they have either a unique Group ID or a different platform type.