Warning: This version is now end-of-support. For more information, click here for our End-of-support policy.
This document contains a list of the updates and current versions of Anywhere365 software and components.
Note: To streamline our support process, before raising a support ticket you need to ensure that the client used is upgraded to the version of the bundle and so the log provided with the ticket is inline with the Bundle. Please note that we will be unable to process support tickets raised on unsupported version.
|Ucc.Creator template (SharePoint template)
|Power BI (desktop template)
|Inflight Wallboard (desktop client)
|Snapper (desktop client)
(Minimum required version for this bundle) Learn More
|+= updated in this bundle.
|Prevent Supervisor initiated audio-invites to respect their call forwarding settings.
When a Supervisor triggers a join (listen) action to an established audio-call but does not (or cannot) pick-up their call ringing, the hunt will now ignore any call-forwarding settings the supervisor may have set on their Microsoft Teams account.
|Text Sessions now respect Business hours for shift from wintertime to summertime.
The time-offset when summertime started was not always respected when summertime started, resulting in Text sessions getting queued an hour after configured business hours for the UCC A Unified Contact Center, or UCC, is a queue of interactions (voice, email, IM, etc.) that are handled by Agents. Each UCC has its own settings, IVR menus and Agents. Agents can belong to one or several UCCs and can have multiple skills (competencies). A UCC can be visualized as a contact center “micro service”. Customers can utilize one UCC (e.g. a global helpdesk), a few UCC’s (e.g. for each department or regional office) or hundreds of UCC’s (e.g. for each bed at a hospital). They are interconnected and can all be managed from one central location..
|Callback CallBack, an IVR menu feature for voice, enables the customer to leave his / her number to be called back by an available agent during business hours. TTS uses default CultureInfo when using Microsoft Speech Synthesizer engine.
After the Callback IVR Interactive Voice Response, or IVR, is a telephone application to take orders via telephone keypad or voice through a computer. By choosing menu options the caller receives information, without the intervention of a human operator, or will be forwarded to the appropriate Agent. became compatible with other cloud speech engines (MS Cognitive Services and Google Cloud TTS), the CultureInfo for specifically the legacy MicrosoftSpeechSynthesizer was not taking this into account anymore. This fixes this by passing the language along with the speech text.
|Dialogue Studio - UCC not playing correct cache file when audio files have been replaced.
Newer IVR audio file is now correctly played through Dialogue Studio if the audio file is replaced with a new audiofile with the same name, on SharePoint.
|Extreme large voicemails cannot be saved in SharePoint.
Large voicemail files (6 hours +) caused the whole voicemail storage mechanism to stop working. Now large voicemail files are being prevented from writing to SharePoint, allowing newer voicemail files to be stored and processed correctly.
|Retain domains if Graph GetDomains Query fails.
Graph will now retain all previously known domains if, during nightly query to graph for added or removed domains in the tenant, the connection to graph cannot be established.
|Enhanced queue handling in WebAgent and Attendant Console for Dialogue Cloud
In the scenario that multiple clients (WebAgent orAttendant Console for Dialogue Cloud) are signed in by the same user, it could happen that after a transfer the call would show as queued instead of connected.
|Formal status now visually updates in the WebAgent when in Reason Code
If the Agent selected a Reason Code the Formal toggle icon didn't visually update after changing the formal state.
|Improved sign in and token behavior.
Snapper has improved Dialogue Cloud and Graph token retention mechanism. This should mitigate the behavior that sometimes a renewed login was requested when Snapper had succesfully been used previously.