The web call logs now include the unrecognised utterances from callers when the ASR is used. The unrecognised utterances are grouped into one log, which is output just before the object being used is exited, or a hangup is processed.

The Innovaphone Connector Service is upgraded to .net 8 Core

The name of the task scheduler job is now shown in the call log under the column “Calling Party Number”.

It is now possible to delete non-call logs from the portal that are older than a maximum age parameter.

The paramater name is “Portal.Statistics.CallHistoryPartA.NonCallLogs.MaxAgeDays”.

OAUTH2 authentication for the IMAP mail connector has been implemented.

Note - since Microsoft 365 no longer supports OWA / Exchange Mail Services, replacement of the exchange mail connector will be necessary on systems which use older style access to Microsoft email services in the cloud. If you require assistance with this, please contact your jtel partner or check out this link: https://wiki.jtel.de/x/PQA0Bw

On outdials when the call was refused by the connected party, the CONNRES values could be incorrect. This problem has been fixed.

When you select just a part of the Groups to be visible in Acd Supervisor, the Totals in the table “Agent” shows wrong values including the Groups which are not visible for some of the columns. This problem has been fixed.

The IVR object InputMenuDTMFASR is not using the error announcement or the error TTS text. This problem has been fixed.

When an agent performs a click to dial using the new blazar telephony server, an exception is produced in the blazar error.blog file if the option “Run Routing Application after Agent Call (Outbound)” is set on the service number. This does not cause an operational problem on the server or within the call flow.

The parameters “service level seconds” and “hangup seconds” were used the wrong way round when calculating the report. This problem has been fixed.

A cache control filter has been implemented in the portal, to control how the following files are updated by the browser:

• ttf (font) files
• png, svg (image) files
• css (cascading style sheet) files
• js (javascript) files

This should alleviate the problem that incorrect CSS and JS and images could still be displayed after a portal update.

When clicking the blinking envelope in Mini Client while having an active call, the Tab was changing to a wrong Tab while it should be changed to Media Event Tab “ME“. This has been fixed.

The calculation of Acd Post Calls Duration and Average in the Report “ACD Agent Report 3 - ACD-A-007” was wrong. This has been fixed.

Very old report subscriptions were created without the ClientsID parameter, which would cause them to fail with an error. This problem has been fixed.

An Agent who has an open mandatory transaction code popup was still able to receive media events. This has been fixed and the event is now distributed only after he sets the transaction code and closes the popup.

When creating a manual callback event, the message template was not updated when the ACD group was changed. This problem has been fixed.

Using the IVR object REST query leads to the following error: curl not exist. This problem has been fixed and the curl command could be executed by 8server or blazar.

Sometimes subscription emails could be sent without an attachment. This problem has been fixed.

The chat should be distributed to the previous agent if it is only one free option.

The Synonyms import in Acd Groups was not working properly, the following two problems existed:

• Tarif could not be empty which not the case anymore.
• Phone numbers (Number to Announce and Physical Number fields) where not checked.

This is now fixed.

The list tab in Transaction codes was misbehaving: it shows duplicated Transaction codes for every group mapping. This is now fixed and the list shows no duplicates.

Sometimes, an outdial from within a callback event would fail with “No Selected ACD Group”. This problem has been fixed.

Click to Dial fails with a configuration error popup if the check whether the instance is a sandbox or production URL fails. Now this logic has been changed to use the following strategy:

• if the URL starts with cs. it is a sandbox (customer sandbox)
• if the URL container .sandbox. it is a sandbox
• If the url starts with dev- it is a sandbox (developer)
• If the url contains dev-ed. it is a sandbox (developer edition)