Introduction
This document covers the various contact sources Webex, LDAP and UDS available for Cisco Jabber.
Jabber Contact Source
What contact sources are available for Jabber?
Jabber clients support three different contact sources,
For on-premise:
1. LDAP (Active Directory or LDAP v3 server), configured as EDI for Jabber for Windows, or BDI for all other clients
- Basic Directory Integration (BDI): LDAP integration used by Jabber for Mac, iOS and Android mobile clients.
- Enhanced Directory Integration (EDI): LDAP integration used by Jabber for Windows which is optimized for Active Directory environments. EDI LDAP provides auto discovery of directory servers and Windows Integrated authentication.
2. UDS, using CUCM as the directory source
3. Webex Contact Source (cloud)
WebEx will provide the contact list
1. UDS Contact Source Configuration (CUCM 9+)
The UDS contact source is a Unified CM based contact source which can be used for on
premise Jabber deployments. Jabber will always use the UDS contact search when using
Mobile & Remote Access via Expressway (MRA).
Configuration details
Deployment architecture - On Premise / Unified CM 9.1.2 +
Platform support - Microsoft windos, Apple OSX, Apple iOS, Google Android
Configuration Method - Service profile only
Configuration options - UDS Contact source
2. Webex contact Source (cloud)
The webex contact source is automatically selected when using Webex Messenger and no administrator configuration is required.
Configuration details
Deployment architecture - Cloud
Platform support - Microsoft windos, Apple OSX, Apple iOS, Google Android
Configuration Method - Webex admin tool / administrator
Configuration options - Webex Contact source
3. LDAP Auto discovery, Cisco Jabber for Windows only
Jabber for Windows has the ability to auto detect its directory settings and connect to a
workstations native Active Directory domain. Workstations must be members of a Windows domain to use this configuration method. The Windows OS will locate a Global Catalog server in the current domain and login using the logged on domain user credentials.
Configuration details
Deployment architecture - On Premise / Unified CM 9.1.2 +
Platform support - Microsoft windows
Configuration Method - LDAP Auto discovery / Service profile
Configuration options - LDAP Auto-discovery, Active Directory.
You can also do, Mixed jabber client with LDAP Auto discovery. - Its includes combinaiton of jabber for windows LDAP auto discovery
Configuration details
Deployment architecture - On Premise / Unified CM 9.1.2 +
Platform support - Microsoft windows, Apple OSX, Applie iOS, Google Android
Configuration Method - LDAP Auto discovery / Service profile
Configuration options - LDAP,Active Directory.
Related Information
