The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Cisco Jabber Guest supports a three-server cluster. Three operational servers are required for full redundancy. Cisco Jabber Guest will function properly with two operational servers in the cluster; however, we recommend to only run with two operational servers for short periods of time, for example, when upgrading the servers in a Cisco Jabber Guest cluster. Cisco Jabber Guest will not function properly if only one server in the cluster is operational.
Configure the reverse proxy to send requests to only one server in the cluster at a time. You set the order in which requests are sent on the Cisco Expressway-C, from the Priority field in . All Cisco Jabber Guest servers should have a different priority. Requests are sent to a different server only if a server becomes unresponsive.
Cisco Jabber Guest can be administered from any server in the cluster; however, to simplify troubleshooting, we recommend that you use one server in the cluster for administration purposes.
Data That Replicates |
Data That Does Not Replicate |
---|---|
Users |
Settings > Local SSL Certificate |
Links |
Settings > Call Control and Media (Local) |
Services > Passwords |
Logs |
Settings > Links |
|
Settings > Mobile |
|
Settings > Secure SIP Trust Certificate |
|
Settings > Call Control and Media |
The upper latency limit is 15 milliseconds.
In this procedure, we refer to the primary server as primary and to the two secondary servers as node A and node B.
When a secondary server joins a cluster, all of the data on the secondary server is discarded. If you need to retain the data for future use, back up the secondary server before joining it to the cluster.
Step 1 | Deploy the .OVA to all three servers. |
Step 2 | For all three Cisco Jabber Guest servers, make sure that you set the FQDN. For more information, see Set FQDN of Cisco Jabber Guest Server. |
Step 3 | Sign in to each server as root. |
Step 4 | To establish
the primary, on one of the three servers:
|
Step 5 | To join node A
to the cluster, on one of the remaining servers:
|
Step 6 | To join node
B to the cluster, on the remaining server:
|
Step 7 | Allow node A
to communicate with node B:
|
Step 8 | Allow node B
to communicate with node A:
|
For each of the three servers in the cluster, configure the appropriate SIP trunk in Cisco Unified Communications Manager or zones in Cisco TelePresence Video Communication Server, depending on the type of servers deployed in your network.
You can modify the IP address or hostname of a server in the cluster if it changes for any reason.
In this procedure, we refer to the server that we change the IP address or hostname of as the target server.
If you are using a self-signed certificate, you must generate a new certificate after you change the IP address or hostname of the server.
You can demote or stepdown a primary server to a secondary server. For example, if you need to do maintenance on the primary server.
A new primary server is elected from the remaining servers in the cluster.
In this procedure, we refer to the primary server as node A and to the two secondary servers as node B and node C.
After a server is removed from a cluster, it cannot be run as a standalone Cisco Jabber Guest instance. To do this, the server must be reinstalled.
In this procedure, we refer to the secondary server that we want to remove as node A, and to the other secondary server as node B