Sinch Community

Symptoms Contact Pro customers have reported various issues with the phone channel when using Google Chrome or Microsoft Edge browsers. The reported issues include: A delayed response from the Accept button The Accept button not being clickable Inability to log in to queues Based on the reported issues, we expect that the issue may not be limited to the specific problems listed above and could potentially impact the phone channel more broadly.   Solution Google Chrome and Microsoft Edge are based on the Chromium browser engine which has a bug in versions M135 and M136 (except version 136.0.7103.92/93). Therefore, we recommend upgrading your browser to version 136.0.7103.92/93.   For the Chromium error report, see https://issues.chromium.org/issues/414842421.   Note: Firefox browser isn't affected by this issue. ... View more

We're excited to announce that the full 25Q2 product documentation is now available! To view the new features and improvements, check out the What's new document. For a more visual overview, see the Show and Tell slide deck. ... View more

Contact Pro cloud and on-premise versions have dependency to Apache Tomcat component, which has been reported as vulnerable. This component is used in Communication Panel, Data Protection Officer (DPO), and Dashboard. However, neither the cloud nor the on-premise version is affected by the vulnerability CVE-2024-50379. ... View more

We've identified a significant change in Microsoft ODBC Driver version 18 that causes database connection failures due to certificate-related errors. When testing the connection, you receive the following error:   [Microsoft][ODBC Driver 18 for SQL Server]SSL Provider: The certificate chain was issued by an authority that is not trusted. We'll investigate the issue and plan a solution for a future release. In the meantime, we recommend using Microsoft ODBC Driver version 17. This applies to all versions from FP14 onwards. ... View more

Here’s some compelling reading for the holiday season to help you gear up for the first release of 2025:   Show and Tell What's new We'll publish the full 25Q1 product documentation on January 10, 2025. ... View more

Another quarterly release is approaching! We now have the Show and Tell slide deck illustrating the content of the upcoming release 24Q4. Additionally, the What's new document is available for you to see the changes and fixes made. The full 24Q4 product documentation will be available on October 11, 2024. ... View more

The following table will list released hotfixes for Sinch Contact Pro on-premise version FP20. To download the hotfixes, go to https://downloads.cc.sinch.com/ui/index.html .   Hotfix number Affected components Description 7.0.20.1 OII Collection of OII fixes made for previous releases 7.0.20.2 ECF Web Server  Collection of UI corrections 7.0.20.3 - Hotfix doesn't exist 7.0.20.4 CEM Correction to address Python vulnerabilities in CEM package   Highly recommended for all customers 7.0.20.6 - Hotfix doesn't exist 7.0.20.7 Call Dispatcher, Media Routing Server, and SIP Bridge Audio of third party in a conference was not properly included in the recording. SIP glare was not handled correctly, causing problems, such as agents not being able to hang up calls. In a complex call scenario where Quality Monitoring Server (QMS) and Multiterminal Desktop (MTD) / Simultaneous Ring Mode (SRM) are in use, hub processing failed in Media Routing Server (MRS) and caused missing RTP streams. If the Sinch Contact Pro system used either stereo recording or Quality Monitoring Server (QMS) with separate audio streams configured, and an agent transferred the customer call to another agent, the audio channels of the recording and QMS got switched. This meant that customer’s audio appeared in the agent’s channel and the other way around. 7.0.20.8 RI Incorrect value for waiting duration 7.0.20.9 ECF Web Server Connection to Agent Server silently lost 7.0.20.10 Integration Interfaces If Presence Synchronization Interface (PSI) was enabled in Infrastructure Administrator (IA) but Teams integration was not configured in System Configurator, PSI went to Near failure state for HAC. IA shows this as a yellow exclamation mark. 7.0.20.11 Reporting Database Server A subtype for internal action item was missing from reporting, which caused issues with customers' reports.  7.0.20.12 ECF Web Server Dashboard failed to send SMS to all recipients. 7.0.20.13 OII When Contact Pro is integrated with SAP CRM via the SAPphone interface and a call is answered in CP and disconnected, CP goes to wrap-up but OII ends it immediately. Now OII doesn’t end wrap-up if user is not subscribed to the ICI interface. 7.0.20.14 ECF Web Server Several fixes to Communication Panel 7.0.20.15 ECF Web Server Several fixes made related to the window sync mechanism used between embedded CP and pop-out CP ... View more

  Here’s the Show and Tell slide deck illustrating the content of the quarterly release 24Q3. In addition, we’ve just released the first version of the What’s New 24Q3 document, which lists the changes and fixes made. The full 24Q3 product documentation will be available on August 9, 2024. ... View more

Symptom When running the System Configurator (SC) from the Remote Administration Tools, the jnlp file fails to load. This happens because the Remote Administration Tools uses HTTP protocol and SC uses HTTPS (Secure Socket). The SC log shows:   com.sun.deploy.net.FailedDownloadException:Failed to load resource: http://[host ip]:[PORT]/remoteadmin/sc.jnlp at com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source)...   The limitation is in the installation media and what it writes to the sc.jnlp file. <jnlp spec="1.0+" codebase=" http://<web_address>:<http_port>/remoteadmin" href="sc.jnlp ">   Solution   Manually edit the jnlp file to change the protocol to HTTPS and port 443. This is located under the Virtual Unit (VU) where the Remote Administration Tool package has been installed in the  <VU>/web/remoteadmin folder. Recreate the client certificate by adding "KeyUsage = 0xa0" to the inf file. Replace the certificate and restart the VU.   Note All manual changes are overwritten in updates. ... View more

Symptoms: You've updated your Open Web Start to the latest version and now SC gets stuck.   Solution: The issue is caused by either the latest version of Open Web Start or Java version 21. We recommend to downgrade Java from 21 to 17. If this doesn't help, revert Open Web Start to the previous version. ... View more