Learn how to set up a cloud-based deployment with the Cisco WebEx Messenger service.
Hybrid cloud-based deployments require you to set up on-premises services. Refer to the appropriate chapter for setting up on-premises deployments for information on provisioning those services.
It is beyond the scope of this document to describe every task involved in setting up a deployment with the Cisco WebEx Messenger service. You should refer to the Cisco WebEx documentation for information on configuring your environment with the Cisco WebEx Administration Tool.
When users successfully authenticate to the Cisco WebEx Messenger service, they get instant messaging and presence functionality. You can optionally configure instant messaging and presence federation with the Cisco WebEx Administration Tool.
The following table summarizes the details for instant message encryption in cloud-based deployments:
Expected Encryption Algorithm
Client to server
XMPP within TLS
X.509 Public Key Infrastructure certificate
AES 128 bit
Server and Client Negotiation
The following servers negotiate TLS encryption with Cisco Jabber for Windows using X.509 Public Key Infrastructure (PKI) certificates with the Cisco WebEx Messenger service.
After the server and client negotiate TLS encryption, both the client and server generate and exchange session keys to encrypt instant messaging traffic.
The Cisco WebEx Messenger service uses 128 bit length session keys encrypted with the AES algorithm to secure instant message traffic between Cisco Jabber for Windows and the Cisco WebEx Messenger service.
Instant Message Logging
The Cisco WebEx Messenger service can log instant messages, but it does not archive those instant messages in an encrypted format. However, the Cisco WebEx Messenger service uses stringent data center security, including SAE-16 and ISO-27001 audits, to protect the instant messages it logs.
For more information about encryption levels and cryptographic algorithms, including symmetric key algorithms such as AES or public key algorithms such as RSA, see Next Generation Encryption.
For more information about X509 Public Key Infrastructure certificates, see the Internet X.509 Public Key Infrastructure Certificate and CRL
Users can make teleconference calls with either the default Cisco WebEx audio service or a third-party teleconference provider.
To integrate the third-party teleconference provider audio services with Cisco WebEx, you must add teleconferencing service name accounts. After you add those accounts, users can make teleconference calls with the third-party provider audio services.
For more information about adding teleconferencing service name accounts, see the Cisco WebEx Site Administration User's Guide.
You can use the following types of authentication with Cisco WebEx Meeting Center:
Tightly Coupled Integration with the Cisco WebEx Messenger Service
Tightly coupled integration refers to a configuration that you set up between Cisco WebEx Messenger and Cisco WebEx Meeting Center.
When users authenticate with Cisco WebEx Messenger, Cisco WebEx Messenger passes an authentication token back to the client. The client then passes that authentication token to Cisco WebEx Meeting Center.
See the Overview of Tightly Coupled Integration topic in the Cisco WebEx documentation for more information.
The client can pass user credentials directly to Cisco WebEx Meeting Center.
To enable direct authentication, complete the following steps:
Create user accounts for Cisco WebEx Meeting Center using the Cisco WebEx Administration Tool.
Cisco WebEx Meeting Center must validate user credentials in a direct authentication scenario. The user accounts hold the credentials so that Cisco WebEx Meeting Center can validate them when the client attempts to authenticate.
Specify Cisco WebEx Meeting Center credentials in the client interface.
See the Overview of Loosely Coupled Integration topic in the Cisco WebEx documentation for more information.