Improved layout for bot buttons (grouped and compact display)

The Chat Connector RAG Bot tab now displays the current vectorization status (e.g. Processing, Ready, Error, Not processed).
A new Refresh button allows users to manually update the status while vectorization is running.

The IVR object Connect VoiceBot is extended to support additional SIP headers (SIP Header 1–5) including their corresponding value fields.

A new configuration option has been added to client master data to control the behavior of manual SMS messages sent from Agent Home:

• 0 – No limitation on SMS size used by agents (current behavior)
• 1 – Warn agents when 160 characters are exceeded when typing an SMS
• 2 – Limit length of SMS messages to 160 characters when created by agents

This allows each client to decide whether agents should be warned about or strictly limited to 160 characters for manual SMS.

A new field has been added to the AcdAgentStatus table - ExportKey - which can be used via the reporting API for aggregation purposes.

E-Mail Signatures are now configurable on an individual email connector basis, in the settings for the connector. If no footer is set in the connector, then the system will use the signature from the client master data, if configured.

Both the email connector and client master data now include a preview of the signature, which is particularly useful if this is in html format.

• Chat now supports custom CSS and icons/images.
• Custom styling files can be uploaded and managed directly in the portal UI.
• Styling can be configured at:
  • Chat Connector level (applies only to the selected connector)
  • Client level (applies to all chat connectors, unless overridden)
• If no custom files are provided, jtel default styling is used.
• Automatic integration is supported when using the predefined file names.
• For more information, check the wiki page
  • https://wiki.jtel.de/display/JPW/Chat+Connector+Configuration+for+LLM

The REST Query and REST Query Advanced IVR components now include a new parameter, “Timeout (seconds)”, allowing configuration of the request timeout within a range of 1 to 120 seconds. This provides more control over how long the system waits for external REST responses.

The default timeout values are 10 seconds for REST Query and 20 seconds for REST Query Advanced.

Existing IVR applications will automatically receive these default timeout settings.

The character limit for Field1, Field2, Field3, and Field4 in NetworkIVRList has been increased from 64 to 128 characters. This resolves previous limitations on input length.

It is now possible to train the RAG database from within the Web-UI of the chat connector. Capabilities include the ability to upload and manage the documents within the RAG database, and start the vectorization process for the RAG database.

The portal call log interface has been enhanced to support downloading ASR recording files from the call log.

This update enhances the embedded chat iframe to support additional configuration parameters passed via the URL.

Specifically, the embedded chat now recognizes nested chat.* parameters, such as:

chat.overrideCSS=css/override.css

Which overrides the css of the iframe.

When clicking on the copy button for teams rules in User Master Data, and then cancel, an incorrect page was displayed. This problem has been fixed.

An issue was fixed where some chat events were handled by the chatbot but had no chatbot user assigned and only a single history “Closed By Customer“. This could happen when the first message was processed by the chatbot and the chat was closed quickly, before the chat record was fully created.
The chat record is now created earlier, ensuring correct chatbot assignment and complete event history.

The system now ensures that the transaction code (TAC) pop-up window and post-call time are only displayed for successful outbound call attempts. If an outbound call is not connected, these elements will no longer appear. This enhancement eliminates unnecessary post-call actions and reduces confusion for agents by ensuring that transaction code entry and post-call processing are only required when a call has actually been established.

In acd.CallTransfer.NumberTransfer a variable was not declared, which would cause the new telephony server to log errors in a tight loop whilst the outbound call to the destination was being made. This problem has been fixed.

Previously, PBX users were still synchronized even when syncPbxUsers was set to false, so the PBX user list was recreated after deletion. The synchronization logic has been corrected so that PBX users are no longer synced when this option is disabled.
The problem has been fixed.

Sometimes deleting a service number could fail, this problem has been fixed.

When selecting one item from a dual list, a display issue occurred in the pick list

• From release 3.44 onward, this fix applies to:
  • AcdGroup – User mapping
  • Teams settings in User and Teams Profiles.
  • Location – User mapping
  • Aggregation Group – User and AcdGroup mapping
• In releases prior to 3.44, the fix only applied to AcdGroup User mapping.

For incoming calls via an ACD group, the $groupname variable was not correctly resolved in the telephone display. The variable handling has been corrected so that $groupname now reliably shows the configured ACD group name. In the Signalling → Telephone Display section you can also use many other variables (for example $agent_name, $caller, $servicenumber, etc.) as described in the documentation: https://wiki.jtel.de/display/JPW/Editing+groups+and+creating+rules.

The popup was not displayed when attempting to create some mappings (for example, agents to groups). This problem has been fixed.

In the new Portal, the “Change Status” drop-down appeared empty in the Supervisor view.
This issue has now been fixed.

In the chat client, URLs containing special characters such as “&” were not processed correctly, causing them to break or behave unexpectedly.
This has now been fixed.

Previously, when a WhatsApp message was sent from a sender whose name included emojis, the system failed to deliver the message to the Agent. This issue has now been resolved. WhatsApp messages from senders with emojis or special characters in their names are correctly processed and delivered to the Agent

An issue was identified where, after performing a blind transfer using an Innovaphone device, the agent would incorrectly remain in a busy state and was not available for new calls. This has now been fixed, ensuring that agents are correctly set to available after completing a blind transfer via Innovaphone devices.

An issue was identified where, after performing a blind transfer using an Innovaphone device, the agent would incorrectly remain in a busy state and was not available for new calls. This has now been fixed, ensuring that agents are correctly set to available after completing a blind transfer via Innovaphone devices.

Previously, the IVR object NumberSuppressed did not correctly recognize anonymous calls and processed them as normal calls. This issue has now been fixed, and anonymous calls are properly identified and handled as intended.

Previously, the AI summary block would grow without bounds, causing the transcription panel to be pushed out of view. This issue has now been resolved by introducing a new scroller within the panel AI assistant, ensuring both sections remain accessible.

The issue where preview time was not saved when a call was refused or timed out has now been resolved. With this update, the preview time will always be recorded in the DiallerContactsHistory table, ensuring accurate tracking and reporting of preview activities regardless of the call outcome.

Previously, users experienced issues in the Live Agent module where Automatic Speech Recognition (ASR) conversations were missing, and the order of conversation was incorrect when a call was transferred to an agent. This led to incomplete transcription visibility and confusion due to conversations being displayed out of sequence, particularly after call transfers. These problems have now been resolved: all ASR conversations are correctly displayed, and the conversation history maintains the proper chronological order following a transfer, ensuring agents have a clear and accurate view of customer interactions.

Previously, tasks that were scheduled outside opening times or during holidays would wait until operations resumed, and then run immediately as soon as operations resumed.
This caused an unintended extra run right after reopening, before returning to the normal schedule.

With this update, such tasks are now automatically postponed to their next valid run time.
They will no longer execute immediately when operations resume, ensuring each task runs only once at the correct scheduled time.

The Old Agent Home page, when accessed through the New Portal, was not refreshing its data (e.g., Agent, PBX Users, etc.).
This issue has been fixed, and data now updates correctly in cross-portal mode.

An issue was identified where the wrong TAC popup would appear if a call was terminated during a group transfer. This problem has now been fixed, and the TAC popup is displayed correctly when a call ends in this scenario.

With the old telephony server, even when the live agent was not used by an agent, there would be exceptions in the call flow (8-Server) logs. This problem has been fixed.

Sometimes the buttons rendered by TAC Bot in the Live Agent were empty. This problem has been fixed.

The IVR object, ConnectVariable, must reference the ID of the destination number from the CNumbers table, rather than using a variable declared.

Sometimes uploading a file to the portal (.wav file for example) would fail. This can be fixed by changing the cifs mount on the affected machines to this:

//acd-store/shared  /home/jtel/shared  cifs  user=jtel,password=<password>,uid=jtel,gid=jtel,file_mode=0755,dir_mode=0755,strictsync,actimeo=0,nobrl  0 0

The log file rotation was not working correctly in the Innovaphone PBX Connector causing the hard disk of the system or container to fill up. This problem has been fixed.

The Voice Mail Transcription via ASR would fail if the transcription contained a single quote. This problem has been fixed.

Previously, clicking the "Copy" or "CRM" button without a summary present would result in a null pointer exception. This issue has now been resolved. Users can now safely use these buttons even when no summary is available, ensuring a smoother and more reliable experience