Solution Prerequisites

Single Server Hardware Requirements

Following are the prerequisites for setting up Hybrid Chat solution. 

Redundant Server (HA) Hardware Requirements

The solution is designed to provide complete failover between 2 systems (with an Arbiter) in case site-A goes down, site-B takes over. Following three nodes are required for an HA  setup.

Software Requirements

• Host Operating System - Cent OS 7
• Docker Community Edition 18+
• Docker Compose 1.26 or above
• Git Client 1.8+
• Mandatory Linux utilities: 
  • wget
  • curl

• Developer Tools installed on the Linux host. (optional)

  yum group install "development tools"

• For system monitoring and to assist in troubleshooting, following utilities are recommended.
  • strace
  • htop
  • dstat
  • atop
  • sysstat
  • iftop
  • nethogs
  • nmap or ss
  • tcpdump 

• MS SQL (for reports in Cisco CUIC) - Recommended version- Microsoft SQL Server 2014, 2016, or later 
  
  • Hardware & software requirements for MS SQL Server 2016/17
    • For database replication & high availability, two VMs are required with recommended hardware.
  • MS SQL flavour should support TLS 1.2. For TLS 1.2 support, see this Microsoft article.

TLS Certificate Requirements

• Certificates from a valid signing authority or Domain signed certificate required for https protocol support. For applying certificates, see Applying TLS Certificates. 

System Access Requirements

• Administrative privileges (root) on the host machine are required to proceed with installation.

System Configuration Requirements

• Setup an FQDN to access Hybrid Chat that should be resolved to the IP address of the host. In HA setup, FQDN of all the nodes should be setup.

• Docker daemon service should be configured to auto start on all systems.

  systemctl enable docker

• Setup Docker log rotation following Docker Logs Retention. 

  if the logs rotation using above mentioned procedure is not enabled, logs will occupy the whole disk space resulting in unusable system.

Network Requirements

1. In HA deployment, network latency can be range between 10ms  to 20 ms, where lower is always good to have.
2. SocketIO connections remain on polling and even though it tries to switch to WebSocket it doesn't work. This could be due to the a network firewall sitting between chat-server and agent-gadget ( Both Hybrid-Chat components ). Customer environment needs to be configured to upgrade the standard HTTPS communication to Secure WebSockets(WSS), so that the  WSS based communication between the agent-gadget and chat-server  can be streamlined. This can be achieved by adding/updating the mainstream Firewall configuration like below:

    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";

This is a snippet from NGINX configuration to upgrade the HTTPS traffic to WSS and can be adapted to other network routing devices.

Mobile version compatibility

Browser Compatibility

Agent Gadget

Browser	Compatibility	Version	Limitations
Google Chrome		86.0.4240.75 (64-bit)	-
Mozilla Firefox		81.0.2 (64-bit)	-
Internet Explorer		11.508.19041.0	Browser Notifications are not supported by IE Some GUI issues are expected In Internet Options>General>Settings>Temporary Internet settings, under "Check for newer versions of stored pages", following option must be selected: "Every time I visit the webpage".

Customer Gadget

Browser	Compatibility	Version	Limitations
Google Chrome		86.0.4240.75 (64-bit)	-
Mozilla Firefox		81.0.2 (64-bit)	-
Safari (OSX)
Safari (Windows)		-	-
Internet Explorer		11.508.19041.0	Browser Notifications are not supported by IE Some Emoji icons may not be visible. In Internet Options>General>Settings>Temporary Internet settings, under "Check for newer versions of stored pages", following option must be selected: "Every time I visit the webpage".
Microsoft Edge		86.0.622.38 (64-bit)

Port Utilisation

For Product Installation

Ports mentioned in this section must be open to install the product. 

For Product connectivity with internal and external components

Ports mentioned in this section should be open for the mentioned product connectivity with different internal and external components.

For Cisco Finesse integration

See Cisco Finesse Integration with Chat Solution.