Sinch Community

Symptoms   You may come across different kinds of audio issues in Communication Panel (for example, the first call of the day being muted).   Solution   Check the following settings on the user’s workstation.   Disable Windows power-saving settings   New Windows versions introduce more aggressive power-saving behaviors. USB headsets may be in low-power mode on first use, causing the first call to be muted.   These settings can be in multiple places, depending on the computer. Go through all of the following.   Power options: Go to Control Panel (view by Large icons) > Power Options > Change plan settings (of the active power plan) > Change advanced power settings > USB settings > USB selective suspend setting. Set both On battery and Plugged in to Disabled.                        Device Manager: Go to Control Panel (view by: Large icons) > Device Manager > Universal Serial Bus controllers. Edit the properties of each controller with “Hub” in the title. Select the Power Management tab. Deselect Allow the computer to turn off this device to save power.     Install headset manufacturer-specific drivers and firmware   The Brands selection in Communication Panel audio settings can cause problems if the manufacturer-specific headset drivers and firmware are not installed.     Make sure that drivers and firmware have been installed before selecting the brand in Communication Panel audio settings. If the drivers and firmware have not been installed, select Other Brand. Otherwise, the integration may not work as expected and it can cause various other problems.   You can find more information about prerequisites for different brands in the Operation Guide document.   Ensure the browser has permission to use the microphone   Windows 11 has tightened app permission handling for microphones. On first use, the system may delay or block microphone access. This can cause the first call to have no outbound audio (agent can’t be heard). Audio works after the first conversation.   Ensure that the browser has permission to use the microphone: Chrome: Settings > Privacy and security > Site settings > Microphone Edge: Settings > Cookies and site permissions > All permissions > Microphone   We also recommend agents to: Close Communication Panel at the end of each workday. Test audio by placing a test call after a Windows reboot or recovering from sleep mode.   In on-premise environments: check the following in your infrastructure in addition to the workstation settings   NAT binding timeout (UDP media ports)   NAT/firewall closes UDP port bindings during idle periods (for example overnight). In the first call of the day, the RTP stream is sent to a now invalid NAT mapping, resulting in one-way or no audio.   To fix this: Enable RTP keep-alive on the AudioCodes SBC and/or SIP endpoints. Configure frequent enough NAT binding refreshes (for example, every 15-30 seconds). Use symmetric RTP if supported.   Codec mismatch or delayed negotiation   Codec negotiation failure or delay in SDP exchange on the first call may cause missing audio.   To fix this: Verify codec priorities and make sure common codecs (for example, G.711 and Opus) are aligned across systems. Make sure there's no asymmetric codec handling on the first session.   SBC media session not properly initialized   The first media path may not get properly opened due to the SBC being in a dormant or idle state, or media anchoring not being fully active.   To fix this: Check if media-anchoring or early media support is properly configured. Enable media timeout settings or pre-establishment of RTP on the SBC. Ensure ICE/STUN/TURN is used if endpoints are WebRTC-based or behind NAT.   Ensure that the latest firmware is installed on the SBC   It is always a good practice to keep SBC firmware as up to date as possible.   General diagnostic steps to investigate the issue   Check SBC syslog and trace files for the first call SIP and RTP behavior. Use tools like Wireshark or SBC's built-in trace tools to verify: SDP negotiation RTP stream establishment NAT behavior   ... View more

In version 25Q1, CALL_ID (known as Group ID in Dashboard) and CallGUID (known as Conversation ID in Dashboard) have been swapped in the EDI framework. Please check your EDI configurations used for calls. If you're using these IDs in your call-related configurations, your integration will not work correctly.   Property JSON data type Description Reference syntax Example values ID string Unique routing leg identifier of the contact For emails, this is the same as Group ID. For example: Can be used as the contact identifier for the /contacts resource of CMI and RMI Can be used as the contact identifier for the /emails resource of CMI In Dashboard, this is known as Conversation ID {contact.id} 1166301942A6EE11B3ED58961D1810CC Group ID string Unique group identifier of the contact For emails, this is the same as ID. For example: Can be used as the group identifier for the /chats resource of CMI Can be used as the contact identifier for /emails resource of CMI In Dashboard, this is known as Group ID. {contact.guid} 5AB6E20342A6EE11B3ED58961D1810CC ... View more

Major browsers like Google Chrome, Safari, and Firefox are phasing out third-party cookies to prevent user tracking across multiple websites. For more information, see for example https://developers.google.com/privacy-sandbox/3pcd.   The deprecation affects especially customers who use Communication Panel embedded within a host application, like SAP Service Cloud for Customer (C4C) or Salesforce.   As a short-term measure, Sinch Contact Pro is participating in Google’s third-party deprecation trial from 24q2 cloud release onwards. On-premise will include the same in an FP20 hotfix.   The long-term plan is for 24q4 cloud release to migrate Contact Pro away from third-party cookie dependencies. The same update is planned for on-premise customers in a hotfix. Follow the Contact Pro community page for updates. ... View more

Integrating Communication Panel with your web application is now easier than ever before. Instructions on using the Communication Panel Control (CPC) library for the integration are available on the Sinch Contact Pro documentation site: Instructions on how to integrate CP with your web application API reference documentation CPC is an open-source JavaScript library for easier Communication Panel integrations. It abstracts the Communication Panel Third-Party Extension Messaging API and exposes its features and capabilities as a modern async API. CPC handles a lot of the heavy lifting for you, cutting down the development time needed for the integration. ... View more

Symptoms Launching CDT or Online Monitoring with HTTPS causes crash on Windows Server 2022.   Reason Sinch Contact Pro webclient module does not support HTTP/2 which is enabled by default in IIS 10 (Windows Server 2022).   Solution Disable HTTP/2 for HTTPS binding: Open IIS Manager on the server. Navigate to the website where CDT and Online Monitoring are served from. On the right side pane, click Bindings. Select row with type https. Click Edit. Click Disable HTTP/2. Click OK. ... View more

Symptoms An agent isn't automatically set as Not Ready although they haven't accepted allocated conversations from a queue.   Prerequisites You must have rights to modify the specific queue and the user settings template.   Solution You need to define the following settings:   Setting Location Read more Activate Not-Ready Status After No Response Queue Management > Queues > [Select the queue] > Client Settings Client Settings (cloud)    Client Settings (FP19)  Timeout for Contacts to be Picked or Rejected Queue Management > Queues > [Select the queue] > Contact Management Queue's Contact Management Settings (cloud)  Queue's Contact Management Settings (FP19)    Community post: Changing how long a conversation is offered in Communication Panel.   Note: This setting is found for both the channel and queue. However, when using automatic Not Ready status, the queue-level value must be defined and must be less than the one defined for the channel. Number of Offerings Before Activating Not Ready User and Role Management > User Settings Template > [Select the template] > Communication Panel Settings Communication Panel Settings (cloud)  Communication Panel Settings (FP19)  ... View more

Symptoms A conversation is offered to an agent for a too long or short time in Communication Panel.   Prerequisites You must have rights to modify the specific queue or channel.   Solution You need to change the time on either the channel or queue level. The setting is called Timeout for Contacts to be Picked or Rejected and an administrator can find it in System Configurator: for the channel: System Management > Channels > [Open the channel's settings] The channel level setting affects queue calls and direct calls. for the queue: Queue Management > Queues > [Select the queue] > Contact Management Read more about this setting in the System Configurator document:     Channel Queue Cloud Channel Settings (cloud) Queue's Contact Management Settings (cloud) On-premise Channel Settings (FP19)  Queue's Contact Management Settings (FP19)   Note: If you're using the automatic Not Ready status in Communication Panel, this setting must be defined on the queue level and the value must be less than the one defined for the channel. Read more about setting an agent automatically as Not Ready. ... View more

Release dates for Sinch Contact Pro 23Q1 have changed. New release dates are:   Release To Test (RTT) March 28, 2023 Release To Customer (RTC)  April 15, 2023   You can find all planned release dates of cloud versions in 2023 in the Release Schedule (sinch.com). ... View more

Symptoms External Agent settings are visible in Communication Panel although the agents don’t use the External Agent service.   Solution External Agent settings must be hidden in System Configurator on user, user group, and user role levels.   To hide the settings: In System Configurator, navigate to Users, User Roles, or User Groups and find the user, role, or group you want to edit. Extend the User Rights block. In the Type dropdown, select User Service. On the External Agent row, deselect the Use setting. Save your changes.   Remember to check all three levels for the setting. ... View more

If you are updating Sinch Contact Pro on-premise version from FP15 to FP16 (or newer), please contact Sinch Contact Pro customer support to get a conversion tool needed in the upgrade. ... View more

Sinch Contact Center is now known as Sinch Contact Pro. Please note that the old name may still appear in older materials. ... View more

Symptoms The installation of the Operative Database Server fails.   Reproducing If you have version FP18 and your SQL Server is 2014 or older, the installation of the Operative Database Server fails.   Solution To successfully install the Operative Database Server with these SQL Server versions, a special script is required that updates the Operative Database Server. To obtain the script, contact our support. Or Upgrade your version of SQL Server to 2016 or above which is required for the new JSON feature for handling new contact contents. ... View more

Sinch Contact Pro (previously Sinch Contact Center) has a documentation site available for cloud customers: https://docs.cc.sinch.com/cloud/index.html    Documentation for on-premise customers can be found at: https://docs.cc.sinch.com/onpremise/latest/index.html     Discussion and FAQs will continue here in the community and the new site will be used for publishing customer documentation.    Best Regards, Sinch Contact Pro User Assistance team  ... View more