Page Comparison

...

1. Prerequisite Knowledge for Linux

To deploy CloudfonCX 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.

...

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

Remove the CloudfonCX v2.x Installation

If your Linux server has installed Cloudfon CX v2.x, please follow the below steps before installing v3.x. These steps will delete all your CX data. You can back up the user data directory first.

Remove the docker instance

# stop cloudfon services instance
sh cloudfon_cc_ctl.sh stop

# remove cloudfon service instance
sh cloudfon_cc_ctl.sh rm

# remove user data folder(You can keep it or remove it. It will not be used anymore, and you MUST NOT install new version into this folder!!)
# The folder is your cloudfon v2.x installation folder 
rm -fr /root/cloudfon-cc

The above commands will deleted the Cloudfon CX v2.x docker instance. Now let us list the Cloudfon CX v2.x docker image .

# This command will list all docker images
sudo docker image list

# You can use the docker image rm command to delete the Cloudfon PCX image, the "4a16"
# is the first 4 characters of the image tag id.
sudo docker image rm 4a16

Cloud and Virtualization Environment Supported

To build a high-availability communication solution to help clients reduce cost and improve communication performance, Cloudfon 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, Cloudfon CX is able to run on PCs and servers with various CPUs ranging from Intel i3 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 Cloudfon CX is designed to be able to run on servers without FQDN specified, we recommend specifying FQGN with the following advantages:

• Easier access to Web Portal for Cloudfon 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 Cloudfon CX installed in LAN. If Cloudfon CX is installed on the public network, FQDN must be resolved correctly into the public network address for the server with CX installed.

2. 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.

...

This guide is for solving the following SSL certificate issues with Cloudfon 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

...

1. Purchase a Domain (for example, cloudfoncloudcxdemo.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.cloudfoncloudcxdemo.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. usuallyUsually, 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 . 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. 

...

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

3. 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

4. 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.

More details, please refer to this link about server specifications. Server Specifications

5. Preparing the Linux Host Machine for Installation

Tasks that MUST be completed before installing CloudCX

• Ensure the server date-time is synced correctly.

• Use the sudo to perform the installation is recommended.

• If the Linux on which CloudCX will be installed is located on a LAN, assign astatic private IP addressto the CloudCX server; if it's on a public network, assign astatic public IP address and a static private IP to the CloudCX server.

• Install all available updates and service packs before installing CloudCX.

• Do not install MySQL on your CloudCX Server.

• Ensure that all power-saving options for your system and network adapters are disabled (by setting the system to High-Performance mode).

• Do not install TeamViewer, VPN, or other similar software on the host machine.

• The CloudCX must not be installed on a host that is a DNS or DHCP server.

• The below ports must be permitted by your firewall.

  • Inbound TCP: 9006, 443

  • Outbound TCP: 8866

  • please also ensure the above ports have not been used by other applications.

• Ensure server date time is synced correctly.

6. 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.

7. Supported web browsers

CloudCX supports the following web browsers:

• Mozilla Firefox

• Google Chrome

• Chromium

• Apple Safari

• Microsoft Edge