Release Notes - Feature release DC2024.01

Upgraded server software components to .NET Framework to 4.8

UCC components on server/backend now require .NET Framework 4.8 to be installed. To learn more on which Windows Server OS-es this is required see:

.NET Framework & Windows OS versions - .NET Framework

Customizable Wrap-Up Time Increase Interval for WebAgent.

A supervisor (or UCC administrator) can now add a new setting (DischargeDurationInterval)to the UCC settings list to define the time increase interval (previously fixed at 10 seconds).

Support for Microsoft Translation Service

The translation service now supports the Microsoft Translation Service, in addition to the existing Google Translate functionality. Furthermore, it no longer relies on plugins to be loaded via the Plugins Settings. Instead, it can now fully integrate within the UCC Service. This change requires new settings to be configured. For more details, see: How to configure UCC Translation

Graph Presence re-authentication mechanism now more resilient.

The re-authentication mechanism for the Presence provider has been improved to allow for more settings changes on the Presence account if performed on customer side. This will now allow for uninterrupted re-authentication and continuity of the Presence Provider.

UCC's will now resubscribe for presence when mis-typed Teams UPN In Windows Active Directory, a User Principal Name (UPN) is the name of a system user in an email address 'like' format. A UPN (for example: john.doe@domain.com) consists of the user name (logon name), separator (the @ symbol), and domain name (UPN suffix). is corrected.

When an agent that is already an agent in another UCC on the same service, gets added to a second UCC but there is a typo in the Teams UPN which gets corrected, this resulted in a presence error for all UCC's that agent is in. This now gets resubscribed on-the-go without requiring re-adding all affected agent references or a service restart without cache.

Incremental retries for throttling Throttling, in the context of a software cloud delivery service, is the practice of temporarily suspending or diminishing access to a service offering to a cloud customer. Because cloud platforms are mostly multi-tenant, shared platforms and the usage at any moment of many customers is unpredictable, throttling is a normal and logical procedure of retaining a cloud service for all customers, sometimes at the expense of one or a handful of customers who are at that time using too many resources for the backend platform. Not only a customer itself, but also a "noisy neighbour" on the same platform can be the cause of throttling. Usually service will be resumed at a normal level after a short cool-down period, but can even take up to 24 hours or more. In Microsoft 365 throttling is usually indicated by "429 errors" or "server too busy" messages in logfiles or replies. of Events for expired UCC credentials [ SQL & SharePoint] to improve stability.

When throttling events occur due to temporary loss or expired/withdrawn authentication credentials to either SQL or SharePoint, connection retries will occur at ever increasing intervals to prevent over-exhaustion of the same event on internal systems. This will improve stability and maintenance of backend systems.

Native Teams WebAgent as an App now has working "Support" hyperlink.

When using WebAgent as an App within the Teams client, the native Teams "Support" hyperlink in the App properties view (next to "Terms Of Use" and "Privacy policy") in the App now directs to the AnywhereNow support website.

Snapper can now be set up for auto answer of all calls Microsoft's "New" Teams client.

Microsoft has spent the last year introducing a "New" Teams client to completely replace the "Classic" Teams client by March 31st 2024. AnywhereNow has added support for enabling Auto-Answer of All calls into the New Teams client. The "New" client type must be selected in Snapper settings.

See: Preferences

Fix discharge and stuck reservation on agent after double skill transfer.

When a call was Skill transferred twice by the same agent, the agent would not get wrap-up and his reservation would persist until the AgentReservationManager releases the reservation after the call had ended. This is no longer the case.

Call stuck in transfer state after failed transfer

In some rare cases failed transfer could not resume that call by agents. Transfer mechanisms have now been made more resilient.

5 second delay to disconnect Agent A during direct transfer.

Enhanced behavior when multiple transfer signals (button presses, refreshes, api etc.) to same or different destinations were sent should now result in only the main transfer to be processed.

Fixed outbound intercepted transfer to other UCC endpoint.

When an outbound intercepted call is transferred to a side instep endpoint, the original callee was called back. This is no longer the case.

DashboardService - Only set a default MSMQ queue when there are no other explicit settings.

In case of a misconfigured Snapper, the Dashboard service can spam the default MSMQ for all services on a host. In case of multi-tenant setups, it can lead to a potential security flaw. With this change, the default queue won't be created/used in case there are already specific queues configured.

Initialtalktime not correct after consult transfer.

InitialTalkTime is now set correctly when a consultative transfer completes

Recognition of SipUri's as wrapped telephone numbers tightened.

When constructing a SipUri object from a sip: URI string, there are several chances to set its IsPhone property to true. When a sip: URI is found with something claiming to be an actual phone number in it, require that that is either 'anonymous' or looks like a well-formed phone number. Previously, any string was allowed, but false positives were encountered in the wild, prompting stricter inspection.

DTMF timeout from Dialogue Studio no longer generates error in UCC log.

Read input from DTMF with (user defined) timeout reached should not result in an error in the Core UCC logs. This has now been fixed.