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 is deployed as a virtual server and requires a VMware server to act its host. The server operating system is CentOS. Cisco Jabber Guest is an on-premises deployment: all services are set up, managed, and maintained on your corporate network.
Cisco Jabber Guest is delivered as an OVA image and deployed manually.
For a summary of the Cisco Unified Communications Manager to Cisco Expressway configuration, see the Cisco Unified Communications Manager/Cisco Expressway Configuration Checklist.
Do one of the following:
To turn on the virtual machine after it has been created, in the console window select Power On.
Configure the appropriate SIP trunk in Cisco Unified Communications Manager or zones in Cisco TelePresence Video Communication Server depending on the type of server deployed in your network.
Note | If the virtual machine cannot acquire the IP address of your VLAN, it shows a bootup failure related to network eth0. |
To turn on the virtual machine after it has been created, in the console window, select Power On.
Note | The virtual machine is set up with DHCP by default. If you want to configure the virtual machine with a static IP address, edit the following properties: IP address, network mask, hostname, gateway IP address, and at least one DNS server IP address. |
Configure the appropriate SIP trunk in Cisco Unified Communications Manager or zones in Cisco TelePresence Video Communication Server depending on the type of server deployed in your network.
Note | If the virtual machine cannot acquire the IP address of your VLAN, it shows a boot up failure related to network eth0. |
The Cisco Jabber Guest server is set up with default credentials.
You can access Cisco Jabber Guest Administration on Windows with:
Google Chrome 18 or later
Microsoft Internet Explorer 8 or later (32-bit, or 64-bit running 32-bit tabs only)
Mozilla Firefox 10 or later
You can access Cisco Jabber Guest Administration on Mac with:
Your session times out after 30 minutes of inactivity.
When you install Cisco Jabber Guest, a self-signed certificate is installed by default. If you want, you can:
Install a certificate that is signed by a third party (a trusted certificate authority).
Install a certificate with additional distinguished name information.
Install a certificate that includes the intermediate certificate or the entire certificate trust chain.
Cisco Jabber Guest supports installing DER encoded certificates and PEM encoded certificates.
The certificate signing request must be generated on the server on which you install the certificate. For this reason, we recommend that you obtain a new CA-signed certificate for your new install of Cisco Jabber Guest or use a self-signed certificate.
If you choose to use the certificate that is installed by default, you must generate a new self-signed certificate if the hostname of the server changes.
The following procedure creates a certificate signing request in which the Distinguished Name (DN) information is composed of Common Name=<ip address> only. If your organization requires you to include additional DN information in your request, follow the instructions in the procedure, Install Certificate with Additional Distinguished Name Information.
If you have deployed a Cisco Jabber Guest cluster, you must install a certificate on each server in the cluster.
When you create the new certificate signing request, the current certificate becomes invalid.
If you use Cisco Jabber Guest Administration to create a certificate signing request, the Distinguished Name (DN) information in the request is composed only of Common Name=<ip address>. If your organization requires you to include additional DN information, such as organization name and locality name, use the following procedure.
If you have deployed a Cisco Jabber Guest cluster, you must install a certificate on each server in the cluster.
When you create the new certificate signing request, the current certificate becomes invalid.
You can upload a combined certificate file that includes the Cisco Jabber Guest server certificate and your intermediate certificate or that includes the Cisco Jabber Guest server certificate, your intermediate certificate, and your root certificate.
If you have deployed a Cisco Jabber Guest cluster, you must install a certificate on each server in the cluster.
When you create the new certificate signing request, the current certificate becomes invalid.
If you make a mistake adding the certificate trust chain, use the following procedure to replace the existing certificate.
Step 1 | Sign in to Cisco Jabber Guest Server command-line interface. | ||
Step 2 | Change directory to /etc/opt/cisco/webcommon/security/ssl: /etc/opt/cisco/webcommon/security/ssl | ||
Step 3 | Create an empty file named server.csr: touch server.csr | ||
Step 4 | Change directory to /etc/opt/cisco/webcommon/.security/ssl: /etc/opt/cisco/webcommon/.security/ssl | ||
Step 5 | Copy server.pem and rename new_server.pem: cp server.pem new_server.pem | ||
Step 6 | In the
Cisco Jabber Guest
certificate, after
-----END
CERTIFICATE-----, paste the entire body of your intermediate
certificate.
| ||
Step 7 | (Optional)If you want to include the root certificate in the combined
certificate file:
| ||
Step 8 | Make sure that there is no additional formatting in the file. | ||
Step 9 | Save the combined certificate file. | ||
Step 10 | Sign in to Cisco Jabber Guest Administration as an administrator. | ||
Step 11 | Click Settings, and then click Local SSL Certificate. | ||
Step 12 | Click
Choose
File, open the combined certificate file, and click
Install a Certificate Authority Signed Certificate.
Under
Certificate Status, the following message appears:
This system has a certificate authority signed certificate | ||
Step 13 | Restart the virtual machine: |
If you are using the self-signed certificate that is installed by default and the hostname of the server changes, you must generate a new self-signed certificate.
When you generate a new self-signed certificate, the current certificate becomes invalid.
The Cisco Jabber Guest server command-line interface (CLI) is set up with default credentials.
By default, the server time zone is set to Coordinated Universal Time (UTC). To change the time zone, use the following procedure.
The time zone change takes effect immediately.
Step 1 | Sign in to the server as root. |
Step 2 | Check the current time zone by executing the command: date. The date and time appear in the format: ddd mmm dd hh:mm:ss UTC yyyy. For example: Fri Dec 20 16:57:18 UTC 2013. |
Step 3 | Change directory to /opt/cisco/webcommon/scripts: cd /opt/cisco/webcommon/scripts |
Step 4 | Execute the timezone script: ./timezone |
Step 5 | Follow the on-screen instructions. |
Step 6 | At the confirmation message, type 1 for Yes. |
Step 7 | Verify that the server is set to your time zone by executing the command: date. |
Step 8 | Restart Tomcat: service tomcat-as-standalone.sh restart |