Print

Previous Topic

Next Topic

Supporting third party XMPP IM applications

Instead of the Cisco WebEx Connect application or Cisco WebEx Jabber application, third party applications (for example, Pidgin for Linux) that support XMPP can also be used for basic IM communication. However, organization policies cannot be enforced on third party XMPP applications. Additionally, features such as end-to-end encryption, desktop sharing, video calls, computer-to-computer calls, and teleconferencing are not supported with third party applications. A list of third party applications that support XMPP is available at the XMPP Standards Foundation website http://xmpp.org/software/clients.shtml.

To allow the use of third party applications with the Cisco WebEx Messenger service, you need to enable a setting in Cisco WebEx Administration Tool. For more information refer to Specifying IM Federation settings.

You will also need to publish a Service (SRV) record in DNS to enable third party XMPP applications to work with the Cisco WebEx Collaboration cloud. For example, the Cisco WebEx Organization, acme.com publishes the following SRV record in DNS to allow the use of third party XMPP applications:

_xmpp-client._tcp.acme.com. 86400 IN SRV 5 0 5222 c2s.acme.com.webexconnect.com

 

Notes:

  • The SRV records for your domain can be found in IM Federation under the Configuration tab. For more information, see Specifying IM Federation settings.
  • The TCP port 5222 should also be opened to enable the use of third party XMPP applications.
  • Polices cannot be enforced when users in your Cisco WebEx Organization use third party XMPP applications to connect to your domain. Policies can only be enforced on users who use the Cisco WebEx Connect or the Cisco Jabber applications.

Top of Page   Print