Note：The Cloudfon CX v3.x is an ALL NEW major release, which means it can't be upgraded from the Cloudfon CX v2.x installation automatically. Version v3.1.0 must be installed on a new server which no v2.x installed. If the server already has v2.0 installed, please follow the steps below to remove it
| Table of Contents |
|---|
...
Prerequisite Knowledge for Linux
To deploy Cloudfon 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 Cloudfon CX v2.x Installation
| Info |
|---|
Please ignore this section if you haven't installed the Cloudfon CX v2.x version. |
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
...
.
...
The above commands will deleted the Cloudfon CX v2.x docker instance. Now let us list the Cloudfon CX v2.x docker image .
| Code Block |
|---|
# 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 Cloud CX commits support to cloud services and has confirmed compatibility with the following cloud and virtualized environments:
...
Depending on the key features listed above, Cloudfon Cloud CX is able to run on PCs and servers with various CPUs ranging from Intel i5 CPUs to Xeon.
...
Latest Firefox, Google Chrome, Edge browser
Knowledge of Linux and Linux Internet administration
Ensure server date time is synced correctly.
FQDN Support
Although Cloudfon 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 Cloudfon 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 Cloudfon Cloud CX installed in LAN. If Cloudfon Cloud CX is installed on the public network, FQDN must be resolved correctly into the public network address for the server with CX installed.
...
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
...
Purchase a Domain (for example, cloudfoncloudcxdemo.net) from the domain provider (for example, GoDaddy.) for your CX.
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.
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.
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.
Rename the private key file as yourname_cx.key.
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.
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.
...