Create new Client - Supervisor and Agent security groups are wrong.
The Supervisor and Agent Security groups are wrong and missing access rights when creating a new client and choosing in the options to automatically create the security groups. This has been fixed.
Exception in the filter of Agent Home - Media History.
In Agent Home - Media History, an exception is thrown when filtering by Type, Status and Acd Group. This issue has been fixed and you can now filter by specifying the TypesID and StatusID for the Type and Status filter.
ACD Skill Distribution - Bug with several timeouts
If the global "remove all skills" after timeout was used in combination with "remove skill X" after timeout, then this could cause unexpected behaviour in the distribution. The call might be distributed to an agent with no skills only once before the second timeout was executed. This problem has been fixed.
Acd Supervisor - Wallboard - tile "Agents Free" counts not registered agents as free.
The problem occurred when the SWYXv2 connector sends NotRegistered Status, in that case the “Agents Free” tile in wallboard count that as a free agent which is not the case. This has been fixed.
Two new agent report variants ACD-A-001-2 (derived from ACD-A-001) and ACD-A-008-2 (derived from ACD-A-008) have been produced. Both of these include a new field,a.IDwhich contains theStatisticsPartA.IDfor the call. The old variations of the report are still available.
Because of the client based licensing of the jtel Cloud TTS system, editing and changing TTS announcements at the sysadmin and reseller has been disabled.
Italy PBX converter bug affecting both incoming and outgoing calls
When Using the Italy PBX converter “Italy PBX - remove outside line prefix 0, remove 00 (international) or 0 (national), other numbers are mobile” in the trunk group, some incoming calls could not be made with a busy result and outbound calls have also an issue so the remote fiels containing normally the destination number is unknown. This bug has been fixed.
New Telephony Server - Increase size of number translation parameters for compatibility with Innovaphone Cloud PBX
The size of the number translation parameters in Trunk Groups has been increased for compatibility with the Innovaphone Cloud PBX which requires some handling of outgoing INVITE messages in conjunction with the registration of the domain of the client’s PBX. It is possible to route to a proxy server (i.e. the actual DNS name of the PBX) which may not correspond to the domain name being used by the PBX.
New Telephony Server - Extensions to allow for longer number parameters in outdial and converters
All relevant number converters and routines used in conjunction with trunk groups have been extended to allow for number parameters which are up to 128 characters in length.
A new object has been added to the IVR to initiate a connection to a voice bot. The object connects the call to the voice-bot by SIP, which will initiate the dialog. During the dialog, the REST API can be used to communicate back with the jtel system. This can be used to:
Query the jtel System by running any routing application. This enables queries and interactions to all backend systems to be made which have been integrated with the jtel system. Also the jtel System can be queried whether any agents are available to handle a particular topic.
Terminate the voice-bot connection and provide the result back to the jtel system. The result could be “DONE” providing a URL to the conversation history, or requesting a transfer to an agent to be made.
Starface Connector - the flag IsAcdAgent is now used for automatic Agent import - Automatic creation of PBXUsers also supported
Agents are now only created in the starface connector if the flag "IsAcdAgent" is set to true in the Starface PBX. PBXUsers are now created automatically in jtel whenever a Starface user is created.
The report ACD Agents Call Reason Report - ACD-A-012 - has been optimised to support larger time spans and be generated in a much shorter period of time.
Chat - Max Agents = 0 does not flag the logged in agent as unavailable.
The chat connector does not flag logged in agents as unavailable when the available agents have the “Max Chats per Agent” parameter equal to 0. This problem has been fixed.
Agent Home and Mini Client - Notes field sometimes loses content
Sometimes the notes field would lose its contents when a call was ended or a state change in the agent client was pushed to the browser. This problem has been fixed.
Callbacks, with option "Close all the open callbacks every successful agent call connection“. are closed after successful outbound calls
Setting the option "Close all the open callbacks every successful agent call connection“ in Acd Groups - Offline Parameters causes all open callbacks with the same caller to be closed after a successful outgoing call with the caller. This issue has been fixed - the option now only affects incoming calls.
Queue - call remains in queue if the call requires a skill and only one agent without a skill is available
If there is a call that requires some skills and only one agent is available and he has no skills, the agent will only receive the call once when the skills are ignored by using the checkbox "Ignore skills (all) if no agents with skills available". If the agent does not answer the call, the call remains in the queue until it times out. This problem has been fixed and the call will be distributed to the same agent again.
Reports - Acd One Line Call Details Report can show empty Call Status even if the call is connected.
If the call is only connected after more than 5 attempts, the Acd One Line Call Details Report returns an empty value for the Call Status. This has been extended to 10 attempts.
E-Mail Connector Processing - Prevent mail connector stop when a processsing error occurs
For the mail connectors, the method of error hanlling has been changed. E-Mails which can't be processed are moved to the Error folder and processing now continues.
ACD Change Status popup - Inconsistent use of "Portal.PhoneNumbers.Internal.Length"
The parameter "Portal.PhoneNumbers.Internal.Length" was not used in this dialog, causing the display of numbers shorter than this setting to use the international dropdown part of the phone number entry field. This problem has been fixed.
The following functions have been added to the REST API:
Calls
Retrieve the currently active calls in a client account.
Make an outbound call for a user.
Answer a call (only supported if the PBX connector supports this functionality).
Disconnect an outbound call leg in the IVR, passing a REST result back to the system with the reason for disconnect which can be used in the routing application.
Hangup a call at an agent.
Put a call at an agent on hold.
Retrieve a held call at an agent.
Agent Status
Retrieve all available agent status for a client account.
Set an agent status for a user (which can also be used to login / logout an agent also specifying the telephone number).
Languages
Retrieve all available portal languages.
Network IVR Lists
Retrieve the Network IVR Lists from a client account.
Retrieve the entries from a network IVR list from a client account.
Add an entry to a network IVR list.
Update an entry in a network IVR list.
Delete an entry from a network IVR list.
Service Numbers
Retrieve all service numbers from a client account.
R-S-001 - Rawdata - Service Numbers Itemised Call Details
A new report containing itemised raw call data has been created. This report contains itemised call details for all calls made using a selection of service numbers. The calls are reported whether they only use the IVR, the IVR and the ACD or just the ACD. Both inbound and outbound calls are reported.
Mini Client - TAC ordering is not the same during and after the call.
Unlike the full client, in mini client, the TAC ordering is not the same during the call (TAC Name order) and after the call (Display order). This has been fixed.
Outbound not possible on ISDN Trunk with more than one controller
Outbound was not possible on ISDN Trunks with more than one ISDN controller. This is due to the multiple trunk / trunk group mappings required for the same machine ID. This problem has been fixed.
A new SwYX Connector - V2 - has been implemented, which no longer requires the installation of a SwYX client to function. The installation can be made on any server which can communicate with the SwYX server via the network.
Report "ACD-006 - ACD Statistics One Line per Call" contains blank value
The statistic report "ACD-006 - ACD Statistics One Line per Call" does not overwrite empty values and assigns an empty value instead of "unknown" to all unknown calls. This problem has been fixed.
The FTP/SFTP import now creates an FTP log under Logging-FTP logs in case of an error during the download from the FTP/SFTP server. The import of the new network IVR list is done after the verification of the existing network IVR list and the file in FTP/SFTP is deleted when the list is imported successfully. An email confirmation in List FTP import is necessary to receive emails and FTP logs
The possibility to integrate a chatbot with the jtel sysadmin has been added. The chatbot uses the RASA framework to help automate chats for a domain which is specified using the configuration files. Interactions with backend systems from the chatbot are developed using the jtel routing GUI, which enables all existing backend integrations to be used. The chatbot can hand-off the chat session to an agent if it is not able to answer the user’s questions. All chat sessions with the bot are available for review via a special agent account for the chatbot.
In all reports with granularity less than or equal to 1 hour, the report could fail if the selected interval included a change to summer time. This problem has been fixed.
Report ACD-A-007 - wrong calculation for agent based on AcdStatisticsPartB
The report ACD-A-007 was calculating based on AcdStatisticsPartB which is oriented to ACD Groups. This has been changed to StatisticsPartB to correctly reflect the data required.
ACD Routing - New Checkpoint "Queue whilst waiting" added
A new checkpoint "Queue whilst waiting" has been added to the ACD.
This checkpoint is executed initially when the caller is placed in the queue, and is checked regularly thereafter. The point in time to which rules apply can be delayed by specifying "delayed rule activation".
Currently, the only type of rule which can be configured, is “Change Parameter”. The use case is to increase the priority of calls in the queue after a certain amount of time has elapsed, for example to increase the priority of low priority calls so that they are eventually distributed, after the caller has been waiting for a certain amount of time.
A new client side chat release has been made including the following features / improvements:
Better UX
Buttons integration: This feature is mainly used with the chatbot, now it is possible to direct conversations with users by using buttons for relevant choices.
Recording integration: users can record and send a voice message.
Extended Group Search - Division by 0 error during distribution when no agents are logged in
The extended group search algorithm could throw an error "division by 0" if no agents were logged into the extended group, and the minimum free percentage of agents was set to 0. This problem has been fixed.
The following columns are now available in the Current Calls table in the ACD Supervisor:
The Service Number and Name Skill 1 - the name and value of the first skill associated with the call or empty if no skill is associated Skill 2 - the name and value of the second skill associated with the call or empty if no skill is associated Skill 3 - the name and value of the second skill associated with the call or empty if no skill is associated UserData - The current user data associated with the call Additional Info - The current additional info field associated with the call
Mini Client EXE - automatic status change now ignores "settable by agent"
The Mini-Client EXE can now change status automatically using the settings in the configuration file even if the status is not flagged as "settable by agent".
Chat Event - Agent receive a chat event during a call if distribute during call is not set.
If an agent has an agent status where Distribute during call equals false, it could receive a new chat event during a call. This problem has been fixed.
REST API - Extension for running Routing Application and retrieving result
The REST API has been extended with a function allowing to run a workflow application and retrieve a result. A new IVR object "Routing Result" has been created for this purpose, which returns a JSON structure to the jrest Server, which in turn returns this to the caller.
The REST API now supports new functions to retrieve cockpit variables and set their values. The API functions are documented in the WIKI in the “Cockpit Variables REST API” section.
Active telephone number can be used for internal call signalling
New options have been added to the user configuration (User Data and User Master Data): - Agent Internal Calls with Active Tel Number - PBX Users Internal Calls with Active Tel Number - Number Internal Calls with Active Tel Number
When set, calls initiated from the web client to agents, PBX users and telephone numbers - but not including call transfers- will be signalled with the active telephone number and not the service number.