Sinch Community

We have decided to cease supporting the legacy agent user interface CDT from our Sinch Contact Pro on-premise offering. The last on-premise version with CDT support will be FP20, and from FP21 onwards we cannot guarantee that CDT will further function. The reasons behind this decision are (1) We have not developed CDT for some time as our focus is on Communication Panel. And (2) CDT is based on Internet Explorer technology, which doesn’t meet today’s security requirements.   We highly recommend that you start adopting the modern and more capable agent user interface, Communication Panel (CP). The CP agent interface has already proven its power in our Contact Pro cloud offering, and we encourage you take advantage of its capabilities! Kindly watch this demo on YouTube  Sinch Contact Pro: Communication Panel overview and feel free to contact us in case of any questions.   What does sunsetting CDT mean? Although, FP21 (and onwards until announced) will continue to contain the CDT code and its associated components, we will no longer run any quality assurance testing of CDT. Development of new features in Contact Pro may mean CDT functionality is excluded. Note that this also affects all components that are used by or with CDT, such as terminal, mctabuff, and vwvideo.   Steps towards using Communication Panel Certain changes are required in your Contact Pro infrastructure before you can use Communication Panel: You must add Embedded Communication Framework (ECF) components to your Contact Pro installation. This package enables user interfaces such as Communication Panel and Dashboard. To enable voice in Communication Panel you need to have a WebRTC proxy device in your network infrastructure. Our recommendation is to use AudioCodes, for which we'll provide configuration guidance. Q & A Q: If I wish to continue using CDT, should I stay on FP20? A: Yes.   Q: Does FP20 have a longer maintenance period because of this? A: No. Sinch will consider extended maintenance periods on a per-customer basis. Each case will be evaluated separately by Sinch. Please create a ticket for such a request. Q: How long is FP20 maintained? A: Please see Maintenance Cycle (sinch.com). Q: What happens to Online Monitoring (OM)? A: Online Monitoring will continue to be supported; however, Dashboard will eventually replace Online Monitoring. Q: Are other WebRTC-capable proxies supported? A: We ensure compatibility only with AudioCodes. However, we are aware of customers and partners who have implemented an open-source alternative called Kamailio, which has proven to work well. For help with implementation project, you can reach a partner directly, the partners are Prominion (EMEA & MENA) and Covington (NA). Q: I have a custom softphone that runs next to CDT. What should I do? A: We recommend you get familiar with the functionality of Communication Panel, as Microsoft is planning to drop Edge IE-mode by 2029. You should stay on FP20 if you wish to continue using your custom softphone.   Q: I want to move to Communication Panel and consider moving to cloud at the same time. Can someone help? A:  Sinch can help with this. See our post Considering moving to cloud        ... View more

Symptoms Reporting couldn’t collect data for a specific date/time from the Monitoring database.   Solution 1. Check if the History database has data for the date/time in question.   a) Connect to the database using Microsoft SQL Management Studio. b) Go to XXX_DSArea database and select it. c) Copy the following script and execute it:   select convert(varchar(13),TimeStamp,121), count(*) from TAContactLog group by convert(varchar(13),TimeStamp,121) order by convert(varchar(13),TimeStamp,121   2. If no data exists in the DSArea database, check if the Monitoring History database server "XXX_History" has historical data for the given date/time.    a. Run the same query as above.  b. If data exists, you'll need to use the CopyLogData tool to copy the history data from the Monitoring database server  "XXX_History" into the "XXX_DSArea" database. For more information, see Copying data from History database to DSArea database.   3. If data exists, use the rollback function to delete the dates in question. This step is only needed if the report has some data. This is done to avoid duplicate values.   a. Open Online Monitoring and go to Tools > Reporting Settings. b. In the DTE Reporting view, select the date/time and click Roll Back.   4. To recollect the data, run the Data Transformation Engine (DTE) job for the days:   a. Run Command Prompt as an administrator. b. Locate the BCM_DTE.exe file. This should be under the Reporting database installation \contents\bin directory, for example C:\Sinch\Contact Pro\Reporting Database Server\contents\bin. c. Change directory to the above path and enter the following in the command line: "BCM_DTE.exe [VU_Name] "YYYY-MM-DD HH:MM:SS" "YYYY-MM-DD HH:MM:SS".  For example: BCM_DTE.exe ACME_Reporting "2013-10-30 22:00:00" "2013-10-31 13:00:00”  The time period doesn’t have to be full hours. You can use a period of 15 minutes.   NOTE: The start and end time parameters are always UTC time, so when you are recollecting the data, you need to pay close attention and convert your local time to UTC or else you could be risking missing some data.   5. If you use Micorsoft Reporting Services reports, run database full process either by:   • Executing the "XXX: Reporting OLAP database management" found in Microsoft SQL Server Management Studio -> SQL Server Agent -> Jobs -> "XXX: Reporting OLAP database management". This will run the Process Full.   or   • Manually running the Process Full directly against the OLAP database:   a. Connect to the Analysis Services Engine using Microsoft SQL Management Studio. b. Right-click on the OLAP database and then choose Process. c. Make sure the process type is set as Process Full and then click OK.   ... View more

Symptoms There is data for a particular date/time in the XXX_Monitoring_History database but the same data is not available in the XXX_DSArea database. To recollect it, you need to copy the data from the History database to the DSArea database. You do this with the CopyLogData tool. The tool is available via a support ticket.    Solution Run the CopyLogData.exe by double-clicking it. Enter the server name \instance and the Monitoring History database name as the source. If this is not a trusted connection, enter the server credentials. Click Next. Select Database and click Next. Enter the destination database information. In this case, copy to the DSArea database. Choose the date/time to be copied and click Finish. To recollect the data, follow the procedure in Recollecting reporting data.   ... View more

This information will only apply after the delivery of the 23Q3 cloud release.   The version naming of our Contact Pro cloud releases will be revised. We will move to defining the cloud versions based on their delivery quarter instead of their last development cycle. This change means that our last quarterly release for this year will be named as 24Q1 per its delivery quarter. For release dates, see Release Schedule.   Be assured, no quarterly release is being skipped and this is purely a renaming exercise for clarity when to expect Contact Pro scoped improvements.     ... View more

We are happy to announce the content of the quarterly release 23Q3. The Show and Tell slide deck highlights the key features and improvements made in this release. The advanced publication of the What's New document lists the changes and corrections made. We will publish the full 23Q3 product documentation on 3 November 2023. ... View more

We are happy to announce the content of the quarterly release 23Q2. The Show and Tell slide deck  highlights the key features and improvements made in this release.   The advanced publication of the What's New document, lists the changes and corrections made. We will publish the full 23Q2 product documentation on 4 August 2023. ... View more

The following table lists released hotfixes for Sinch Contact Pro on-premise version FP19.  To download the hotfixes, go to https://downloads.cc.sinch.com/ui/index.html.    Hotfix number Affected components Description 7.0.19.1 CEM Server Allocation issue after failed external transfer 7.0.19.2 ECF Web Server Joining calls via CPExtInterface failed. 7.0.19.3 Chat Server Connection break between Chain Matcher and Chat Server 7.0.19.4 ECF Web Server SAPUi5 moves to Patch-Level Independent Bootstrap approach. Jabra devices: ringing continued after user declined a conversation. Ringing continued in Communication Panel with auto answer. 7.0.19.5 ECF Web Server Email reply template not applied 7.0.19.6  ECF Web Server Several issues in Communication Panel 7.0.19.7 Agent Server CEM Server  Communication Panel: auto-answer issue in call transfer CDT: supervising issue in multi-CEM environment 7.0.19.8 Integration Interfaces Incorrect timestamp in RTI 7.0.19.9 ECF Web Server  Communication Panel showed History data loading failed when loading conversation history. 7.0.19.10 CEM Server Several issues 7.0.19.11 ECF Web Server Several issues in Communication Panel 7.0.19.12 Quality Monitoring Server (QMS) QMS was unable to send call events at the rate they were happening. Events piled up in a queue and were sent when the call had already been disconnected. 7.0.19.13 Integration Interfaces Presence synchronization via Presence Synchronization Interface (PSI) was interrupted due to a PSI internal error. 7.0.19.14 ECF Web Server Communication Panel Third-Party Extension Messaging API couldn't send dual tone multi-frequency (DTMF) tones. 7.0.19.15 Agent Server Agent status and profile synchronization between SAP CRM IC and Communication Panel failed. 7.0.19.16 Integration interfaces An action item may not have always been deleted (Status=Deleted) in a timely manner when requested by CRM. 7.0.19.17      Agent Server Agent's response to a customer email in CDT wasn't showing in Online Monitoring nor in reporting data. This occurred because the reporting events for an outgoing email were no longer sent to the database. ... View more

This procedure is for on-premise system integrators to customize environments.  The UI setting for this function is Forwarding Destination for Scheduled Queue Close in System Configurator > Queue Management > Contact Management.   Symptoms Queuing conversations in Queue1 need to be moved to Queue2.    Prerequisites You have access to databases via Microsoft SQL Server Management Studio.   Solution Move conversations using an SQL procedure. This works for voice, email, chat and task conversation types. Moving conversations directly to an IVR or external destination is not supported. In such cases, route via another queue. Note that conversations that are already in offering state are not moved.   From Microsoft SQL Server Management Studio: Connect to the SQL server instance hosting the operative database of the target system (for example Object Explorer > Connect > Database Engine). Open a query editor (for example Object Explorer and then right-click on the operative database and choose New Query). Paste the following in the editor, replacing source queue and destination queue with valid extension addresses/numbers or queue GUIDs (and keeping the single quotes): EXEC MoveContact 'source queue', 'destination queue' Optionally, to schedule the operation to happen at a later time, add the desired execution time (UTC) as third parameter, for example: EXEC MoveContact 'source queue', 'destination queue', '12:00' Or at later date: EXEC MoveContact 'source queue', 'destination queue', '2050-12-24 12:00' Execute the query (F5). The operation should take place either immediately, or at a given date/time.   Procedure description: @source: Source queue GUID (uppercase, with hyphens) or extension address (case sensitive) @destination Destination queue GUID (uppercase, with hyphens) or extension address (case sensitive) @validFrom Optional operation start date/time – if NULL or in the past, current UTC date/time is used @validUntil Optional operation expiry date/time – if NULL or less than start date/time, start date/time + 1 minute is used Examples: Move chats from chatqueue1 to chatqueue2 and execute immediately: EXEC dbo.MoveContacts 'chatqueue1@acme.com', 'chatqueue2@acme.com' Move calls from 150 to 151 and execute five minutes from now: DECLARE @validFrom datetime SET @validFrom = DATEADD(MI, 5, GETUTCDATE()) EXEC dbo.MoveContacts '150', '151', @validFrom Move conversations from guid1 to guid2 and execute at specific UTC time on current day: EXEC dbo.MoveContacts 'DF1AFC30-153D-49CC-97BD-CCFA17C27EFD', 'EE0B0B4F-8465-44FC-8444-F37E5B0259E2', '12:00' Move conversations from guid1 to guid2 and execute at specific UTC date/time: EXEC dbo.MoveContacts 'DF1AFC30-153D-49CC-97BD-CCFA17C27EFD', 'EE0B0B4F-8465-44FC-8444-F37E5B0259E2', '2018-12-24 08:00'     ... View more