You MUST have DNS setup properly for this to work, _cisco-uds must exist and must point to the hostname of the CUCM, the actual hostname of the CUCM (for example, ) must be fully resolvable, best bet is to point the _ to, which in turn will point to the IP address of your CUCM server.you CAN force both internal and external clients to use UDS if for example, your an all-mac shop who do not use LDAP, or your cluster covers multiple AD domains, or any other reason you can think where you would rather use the CUCM database than the AD database to retrieve contacts.It prevents you from having to expose your LDAP server to the internet for jabber for iphone etc.This is designed for when users are outside your network, on the collab-edge.UDS will use the users that are part of the CUCM end user webpage as the directory entries.You can provide this information via the service profile (which is downloaded by the client) or the client configuration file. You can create a user who is able to bind to LDAP for this OR you can support an anonymous bind.This is the “Traditional” method of LDAP integration with jabber where by you must specify the LDAP server and directory information as part of the service profile for that user.When you go to “Show connection status” in your jabber client, you will not see any mention of trying to connect to the EDI directory, it will not show up in your jabber client as connected/not connected as it’s all part of the Windows API.This of course assumes your Windows Domain has been setup correctly, but you as the network engineer should not have to do anything to get this going.Other than making sure the client is a Windows PC and is actually on the domain, and that the user who is logging in is part of the domain, you should not have to perform much configuration here.A lot of Windows Applications use this Windows Directory API in a similar fashion. The way I often hear this described is that it uses the outlook address book, this isn’t actually what happens, the way EDI works is that the client uses DNS to find the local AD global catalog and binds to this using the login credentials of the user.Easiest to setup/No real setup required.With collaboration edge and other improvements, it’s a great program.Ĭisco Jabber has three directory options:
Moving country etc got in the way and their has been a delay but better late than never right? I am also finding more and more customers are asking for jabber, It’s no longer the joke compared to Microsoft Lync that it used to be. It’s been a while since I posted my Cisco Jabber huge improvements blog! I even promised you I would explain the new directory options available in jabber!
0 kommentar(er)
