Solution Prerequisites for Windows Deployment

Following are the prerequisites for setting up Hybrid Chat solution under different deployment profiles.

	Hybrid Chat Core	NGINX Reverse Proxy & Customer Gadget
Hardware Sizing
For up to 50 concurrent agents	8 vCPU, 12 GB RAM, 250 GB HDD	2 vCPU, 4 GB RAM, 50 GB HDD

Software Requirements
Host Operating System - Windows Server 2016 MS SQL Server - Recommended version- Microsoft SQL Server 2014 or above
Certificates for HTTPS
Certificates from a valid signing authority or Domain signed certificate required for https protocol support. Certificates should be named:certificate.pemcertificate.key
System Access Requirements
Administrative privileges on both the host machines are required to proceed with installation.

Browser Compatibility

Agent Gadget

Customer Gadget

Port Utilization

The local security policy and firewall should allow the open communication on the following ports.

Hybrid Chat Core machine:

	Type	Source Host	Port	Destination	Notes	Enable for Outside Network
1	HTTPS	hybrid-chat-core	8444	any	The external port for Chat Server	yes, only for reverse proxy machine
2	HTTPS	hybrid-chat-core	8450	any	The external port for Database Connector	yes, only for reverse proxy machine
3	HTTPS	hybrid-chat-core	8482	any	The external port for Communication Server	yes, only for reverse proxy machine
4	HTTPS	hybrid-chat-core	8443	any	The external port for Agent Gadget, Mre Frontend, Ecm Frontend, Umm and EABC	yes, only for reverse proxy machine
5	HTTPS	hybrid-chat-core	8495	any	The external port for File Engine	yes, only for reverse proxy machine
6	HTTPS	hybrid-chat-core	8095	any	The external port for Mre	yes, only for reverse proxy machine
7	HTTPS	hybrid-chat-core	8447	any	The external port for Mre Microservice	yes, only for reverse proxy machine
8

Nginx Reverse Proxy & Customer Gadget machine

	Type	Source Host	Port	Destination	Notes	Enable for Outside Network
1	HTTPS	reverse-proxy-machine	443	any	The external port for Reverse Proxy / Communication Gateway	yes

Time Synchronization

Communication between Chat Solution, client applications, Cisco Finesse and external reporting carry timestamps. If the system dates and time are not synchronized the system can produce unpredictable results. Therefore, please make every effort to adhere to the following time synchronization guidelines:

Chat Solution, client applications, Cisco Finesse and external reporting database should have their Time Zone and time configured properly according to the geographic region and synchronized. To configure the time zone, please see the instructions from the hardware or software manufacturer of NTP server. Client applications and EF Connector should be synchronized to the second. This synchronization should be maintained continuously and validated on a regular basis. For security reasons, Network Time Protocol (NTP) V 4.1+ is recommended.