- Configure Cisco Expressway-E and Cisco Expressway-C
- Change MTU Size
- Configure Signaling and Media
- Configure Static NAT Mode on Cisco Expressway-E
- Configure TURN Credential Provisioning
- Set Up TURN Server Information
- Set FQDN of Cisco Jabber Guest Server
- Set Domain Used for Links
- Set Redirect URL for Mobile Clients
- Customize Cisco Jabber Guest Clients
Perform Initial Setup
Configure Cisco Expressway-E and Cisco Expressway-C
Do one of the following:
- Configure Cisco Expressway-E and Cisco Expressway-C: Cisco Expressway-E with Single NIC Deployment
- Configure Cisco Expressway-E and Cisco Expressway-C: Cisco Expressway-E with Dual NIC Deployment
Configure Cisco Expressway-E and Cisco Expressway-C: Cisco Expressway-E with Single NIC Deployment
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.
Configure Cisco Expressway-E and Cisco Expressway-C: Cisco Expressway-E with Dual NIC Deployment
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.
Change MTU Size
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.
Configure Signaling and Media
Do one of the following:
BFCP Screen Share
Existing Cisco Expressway and Cisco Unified Communications Manager deployments that use Binary Floor Control Protocol (BFCP) should not need any configuration changes to enable Cisco Jabber Guest for BFCP screen share. If you're not sure if your deployment has BFCP enabled, see Check BFCP Settings for Screen Sharing.
- Configure Signaling and Media: Cisco Expressway-E with Single NIC Deployment
- Configure Signaling and Media: Cisco Expressway-E with Dual NIC Deployment
Configure Signaling and Media: 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-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.
Configure Signaling and Media: Cisco Expressway-E with Dual 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.
Configure Static NAT Mode on Cisco Expressway-E
Configure TURN Credential Provisioning
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.
Set Up TURN Server Information
The Cisco Jabber Guest client needs to know which Cisco Expressway-E to use for TURN relays.
Set FQDN of Cisco Jabber Guest Server
What to Do Next
Make sure that you populate the Cisco Jabber Guest local FQDN field for each node in the Cisco Jabber Guest cluster.
Set Domain Used for Links
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.
Set Redirect URL for Mobile Clients
If ports are not remapped in front of Cisco Expressway-E, you must add port 9443 in the Redirect URL fields, for mobile clients.
Note | The configuration of port 9443 in the Redirect URL fields is supported only in Cisco Jabber Guest 10.6(9) and its later releases. |
Customize Cisco Jabber Guest Clients
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.
Customize Long Polling and Call Session Expires
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. |