Solving the “jabber-config.xml” File Mystery
The jabber-config.xml file is an essential piece of configuration for the Jabber client. Sure, the client has the ability to operate just fine without this file. Video calling, deskphone control, instant messaging, etc. all work flawlessly. However, if you need to add any additional options, policies, or directory integrations, the jabber-config.xml file becomes necessary. Within the realm of the CCIE Collaboration certification, we are specifically concerned about two different configurations: UDS Directory Integration and SIP URI Dialing.
User Data Service (UDS) simply put, is the name for the End User database within Cisco Unified Communications Manager (CUCM). It contains all relevant information about that user, as would any other directory. UDS, however, is not enabled by default on the Jabber client. In fact, Jabber is geared towards integration with an LDAP source “out of the box”. This means that we must instruct the Jabber client to use UDS if we would like to be able to search the CUCM database to communicate with other users. Since this will have to be done by using the jabber-config.xml file, we must first determine how to create it. Thankfully, the Cisco documentation does not disappoint in this regard. From the Continue reading
A new use case explains how on-premise vCPE virtualizes common network functions to a commercial, off-the-shelf (COTS) platform.
Explore how VIRL can integrate Cisco virtual routers, switches, firewalls, controllers, as well as 3rd party applications in this Cisco DemoFriday!
Discover how virtualized residential gateways are driving the delivery of enhanced residential services.
Talari's SD-WAN product wins over two banks in Minnesota.