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.
Do one of the following:
Follow the instructions in the Cisco Expressway documentation to set up Cisco Expressway security certificates and a Unified Communications traversal zone. Configure the traversal zone type between the Cisco Expressway-C and Cisco Expressway-E as Unified Communications traversal.
HTTP request goes from the Cisco Expressway-E to the Cisco Expressway-C to the Cisco Jabber Guest server.
Follow the instructions in the Cisco Expressway documentation to set up Cisco Expressway security certificates and a Unified Communications traversal zone. Configure the traversal zone type between the Cisco Expressway-C and Cisco Expressway-E as Unified Communications traversal.
HTTP request goes from the Cisco Expressway-E to the Cisco Expressway-C to the Cisco Jabber Guest server.
In some call scenarios, such as when using VPN, the default Maximum Transmission Unit (MTU) on Cisco Expressway-E is too high and can cause packet loss. The default MTU is 1500 bytes. We recommend that you lower the MTU to 1400 bytes. If you do not, callers may experience problems, such as one-way video.
Do one of the following:
We recommend enabling Session Initiation Protocol (SIP) over Transport Layer Security (TLS) for call control signaling and enabling Secure Real-Time Transfer Protocol (SRTP) for secure media. Secure media requires secure signaling.
On Cisco Expressway-C, make sure that you have created a neighbor zone for each Cisco Jabber Guest server. For more information, see Configure Cisco Expressway-E and Cisco Expressway-C: Cisco Expressway-E with Single NIC Deployment.
We recommend enabling Session Initiation Protocol (SIP) over Transport Layer Security (TLS) for call control signaling and enabling Secure Real-Time Transfer Protocol (SRTP) for secure media. Secure media requires secure signaling.
On Cisco Expressway-E, make sure that you have created a neighbor zone for each Cisco Jabber Guest server. For more information, see Configure Cisco Expressway-E and Cisco Expressway-C: Cisco Expressway-E with Dual NIC Deployment.
The Cisco Jabber Guest client needs TURN credentials to allocate TURN relays on the Cisco Expressway-E. The Cisco Jabber Guest server provisions these credentials on the Cisco Expressway-C when the Cisco Jabber Guest client connects.
The Cisco Jabber Guest server uses an HTTP-based XML API to communicate with Cisco Expressway-C.
The Cisco Jabber Guest client needs to know which Cisco Expressway-E to use for TURN relays.
Make sure that you populate the Cisco Jabber Guest local FQDN field for each node in the Cisco Jabber Guest cluster.
To create links on the Cisco Jabber Guest server, you must enter the Cisco Jabber Guest domain that is configured on the Cisco Expressway-C or the sub-domain of the Cisco Jabber Guest domain.
You also need to ensure that the appropriate DNS records exist so that the Cisco Jabber Guest client can reach the Cisco Expressway-E.
Do not to modify any files on the Cisco Jabber Guest server. For example, on the web client, editing the appearance of the Cisco Jabber Guest video window, such as the Call button, is not supported.
To change the appearance of the web page that contains the Cisco Jabber Guest video window, host the page on a server other than the Cisco Jabber Guest server.
The mobile client can be fully customized.
For more information about customizing Cisco Jabber Guest clients, go to the Cisco Jabber Guest SDK DevNet website.
Cisco Jabber Guest client sends HTTP long polling to Cisco Jabber Guest server to communicate events and keep alive. We provide two advanced settings, Client long-polling and Call session expires, to control the long polling time intervals:
Note | The Client long-polling and Call session expires field configurations are supported only in Cisco Jabber Guest 10.6(10) and its later releases. |