The jtel MiniClient .EXE is now code signed. Note, this will not automatically stop the “smart screen” warnings. According to Microsoft we will just have to wait and see - it could take anywhere betweeen 2 and 4000 downloads and checks by smart screen before it stops displaying warnings, and in fact there is no guarantee that this will ever happen. The code signed .EXE should display JTel GmbH, Alte Landstr. 29, 85521 Ottobrunn, Bayern, DE as the signing entity, issued by GlobalSign GCC R45 EV CodeSigning CA 2020.

This new feature allows users to generate the embedded code to enable the chat function on the video server. If the ChatEnabled option is set to true, then the caller should have a chat button and a chat window should open automatically.

A new column called "Extra Data" in Network IVR Lists has been introduced.

This column can be used to store a larger data fields - typically in JSON format.

The List Functions and List Functions Variables IVR objects have been updated to support the new column for the function: “Add Value to List”.

The List Lookup and List Lookup Variable IVR objects have been updated to be able to store the new column value in a variable.

Note: The list lookup function only uses Field 1 to Field 4 for matching as the new column Extra Data is not indexed and not designed to be used within a search.

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

If no mailboxes were previously configured, then it was not possible to create the first new mailbox. This problem has been fixed.

The problem can be reproduced by performing a complete group transfer to a group in which no agent is connected. As soon as the call is in the queue, we connect an agent and answer the call. If the original and the target group have different TACs and the transfer type is ‘Transfer with query options’, the transferred agent receives a TAC popup with incorrect content. This problem has now been fixed.

The Dialler Result Code popup was too small to show all the content when used in Mini Client. A scrollbar has been added to the popup which allows the display of the full content, in particular when an appointment is being set.

The request callback 3 group action did not count the number of repeats correctly if no number was entered. This problem has been fixed.

The ForeignSystemID is now set to UserData when a dialler campaign is cloned. This helps identifying the campaign later.

The “jtel” login button is now disabled when “force login” is set for any other provider (Azure, Okta, OAUTH2) instead of all providers.

The ACD-G-004 Report was showing wrong percentage values for the Total, Average, Maximum and Minimum in the following columns:

• In Service
• Not In Service
• Hangup <=
• Hangup >

This has been fixed.

In the manual dialler, when a dialler contact is edited and saved or the save is cancelled, the wrong tab is displayed subsequently. This problem has been fixed.

The first person to login to the web portal after a web server restart would determine the “editability” of routing applications for all users on that webserver. If the user logged in with the mini-client or a teams client, then no users on that webserver would be able to edit routing applications. This problem has been fixed.

Sometimes when changing to manual post call when closing the transaction code window a call could still be received if the system had queued calls in this instant. This problem has been fixed.

If a call was transferred between two agents, and both recorded a TAC, then ACD_TAC-001 would show both TACs twice in the report. This problem has been fixed.

Manual post call time was not always added to the post call time for the last call. This problem has been fixed.

In the following reports, transferred calls that are not connected are not counted:

• ACD-A-001 ACD Agent Calls Report 1 - itemised agent calls by date / time
• ACD-A-001-02 ACD Agent Calls Report 1 - 02 - itemised agent calls by date / time
• ACD-A-002 ACD Agent Calls Report 2 - itemised agent calls by service number
• ACD-A-002-02 ACD Agent Calls Report 2 - 02 - itemised agent calls by service number inbound and outbound

This problem has been fixed.

Using the SAP connector to accept an incoming call does not work. This probelm has been fixed.

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

In ACD-G-014 the group rules "Request Callback 2" and "Request Callback 3" were not counted in report. 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)