Before Started

Prerequisite Knowledge for Linux

To deploy Cloud CX on Linux, you need to have some knowledge and skills of the Linux operating system, and here are some Linux infrastructures and popular Linux distributions that will be used.

• Debian Buster 10, Debian Bullseye 11

• Ubuntu 20.04 (LTS) Focal, Ubuntu Impish 21.10, Ubuntu 22.04 (LTS) Jammy

• Docker 20.10 or higher.

• IPv4/IPv6

• Systemd

• IP tables

• Firewalld

• HTTP

It only supports 64-bit OS.

This document assumes that the Linux OS is already deployed and administrators of Cloud CX have been granted root permission to Linux.

Cloud and Virtualization Environment Supported

To build a high-availability communication solution to help clients reduce cost and improve communication performance, Cloud CX commits support to cloud services and has confirmed compatibility with the following cloud and virtualized environments:

• VMware ESX 5.X and above.

• Microsoft HyperV 2016 R2 and above

• Amazon AWS

• ALI Cloud

• Google Could

• Microsoft AZURE

• Digital Ocean

System Performance Depends On the Following Key Factors

• Maximum simultaneous chat needed for CX

• Maximum online agents needed for CX

• Conversations & Files record storage

• Maximum Flows(Bot) on CX

• Maximum Chat Queues on CX

Depending on the key features listed above, Cloud CX is able to run on PCs and servers with various CPUs ranging from Intel i5 CPUs to Xeon.

Other Requirements

• Latest Firefox, Google Chrome, Edge browser

• Knowledge of Linux and Linux Internet administration

• Ensure server date time is synced correctly.

FQDN Support

Although Cloud CX is designed to be able to run on servers without FQDN specified, we recommend specifying FQDN with the following advantages:

• Easier access to Web Portal for Cloud CX

• Easier management of clients after IP address change for CX

• Convenient access to HTTPS when accessing Web Portal

• Avoid browser warnings when accessing the WebRTC Client

The FQDN you are using must be able to be resolved correctly into the server with Cloud CX installed in LAN. If Cloud CX is installed on the public network, FQDN must be resolved correctly into the public network address for the server with CX installed.

Prepare the TLS certificate

When there is a need for additional security of the conversation traffic for Web (HTTPS) sessions, the Transport Layer Security (TLS) is used to secure the client's conversation connections. In TLS protocol, the data is encrypted and protected. TLS communication requires a certificate to authenticate the recipient of the secured data.

Preparing TLS Certificates for WSS/HTTPS

This guide is for solving the following SSL certificate issues with Cloud CX.

• After you complete the CX setting up, if you get the self-signed certificates warning in the browser when you access CX Web Portal by HTTPS, please follow up on the below steps to solve it

• The SSL certificates are expired

Please take the steps listed below.

1. Purchase a Domain (for example, cloudcxdemo.net) from the domain provider (for example, GoDaddy.) for your CX. 

2. Add an A record in the Domain DNS zone, and resolve the Domain to your CX IP, for example: point the cx.cloudcxdemo.net to CX server IP.

3. Purchase a certificate from the trust certificate provider for your domain, for example, Digicert, Thawte, GeoTrust; If you want to make it easier to manage multi-tenants, you'd better apply for a wildcard certificate.

4. Generate the CSR file and private key file according to the certificate provider’s guide, and keep the files. Usually, you will have two files: the certificate and the private key. Note, please choose the certificates for Nginx.

5. Rename the private key file as yourname_cx.key. 

6. Submit the CRS file to the certificate provider, and download the certificate files after your certificates were approved. This step will end up with two files: Intermediate CA certificate and SSL certificate . Note, some providers don't have the Intermediate CA certificate.

7. Please ignore this step if your provider doesn't provide the Intermediate CA certificate. Use a plain text editor for example Windows Notepad (do not use MS Word) to open the Intermediate CA file and SSL certificate file, copy the Intermediate CA contents to append to the SSL certificate file, and rename the SSL certificate file as yourname_cx.pem. In the Linux environment, you can use the below commands to combine the certificate files. 

# Append intermediate file to certificate file
cat intermediate.pem >> cert.pem
 
# Rename certifiate file to yourname_cx.pem
mv cert.pem yourname_cx.pem

8. Now you will have two certificate files, the certificate file yourname_cx.pem , and the private key file yourname_cx.key.