Jabber- Troubleshoot Contact Resolution Issues

hi my name is Billie Trumbo a Cisco tack in this video I'm going to show you how to troubleshoot contact resolution issues in chapter Jabar can use several sources for contact resolution these mainly consist of LDAP or UTS but jabber will also use local sources to resolve contacts to get a better understanding of this let's see what a working search looks like in jeonse jabber client he has no contacts yet so if I search on Frank we see that there is a directory result which means this contact was found on the directory source note that for an LDAP directory search to occur by default a minimum of three characters need to be typed that is not the case for you - yes so let's add Frank to the list of contacts now let's search for Frank again notice the search results for Frank appear under contacts and recents that means that the directory resource was not used since a local contact was found in the jabber cache but if I search for another user we get another directory result under the menu help and show connection status and at the bottom you can see that the directory results are shown a green check shows the connection is good and successful the protocol is LDAP so we know jabber is using the source instead of the UDS for contact resolution so now let's see an example of a fail directory search I've made a change and now when I search you see there are no results also notice that the display names for contacts are not resolved this can be your first indication that there's a contact resolution issue let's check our connection status now there is an error on the directory connection status this may or may not be an indicator of a problem however we can still see a green check for a connection to the directory source but still have issues a better step is to use a troubleshooting tool accessible with the ctrl shift C in combination this is the contact resolution tool where you can get more details on the directory source connection notice the LDAP information represented here tells us how jabber is connecting to the active directory server and the context of the searches we can type the same name to search here but there are no results the next step in this troubleshooting process is to check configuration from the Communications Manager administration page first let's check that the active directory server is configured properly under user management user settings and you see services and make sure that the directory server has the correct information next go to user management and end-user find the jabber user in question and open the end-user configuration under the service settings check the you see service profile to find out which service profile this user has assigned then go to user management user settings and service profile select the profile that this user was assigned and finally scroll down to check the director of profile investment services and I have no search base this is why the connection status showed an invalid credential error now if I was using the Communications Manager as the directory server instead of Active Directory the only thing I would need to configure here is the checkbox labeled use UDS for contact resolution that would allow jabber to use communications manager for contact resolution if I choose use logged on user credential this essentially means jabber will ignore the username and password field because it's going to apply the local jabber users credentials as the authorization to search for contacts from the Active Directory source but if I want all jabber users to access the context using a controlled account with the appropriate permissions I should leave both of these boxes unchecked and provide all information in these fields now that I have properly configured this information I can save the service profile and that takes care of the configuration from the communications manager but we should also be aware that there could be a custom configuration in the Jabbar - config dot XML that could override the communications manager configuration the easiest way to check this is to produce a problem report from jabber unzip the contents and look for the config folder the Jabbar - config dot XML file will become part of the jabber all config.xml in the problem report can be opened with a notepad application and under the store name cashed TFTP can fake store that you will find the contents of Jabbar - config.xml if you see a configuration like this it means that jabber could be using the server listed as the primary server name as well as a different username and password over what is configured in Communications Manager different jabber versions may use the Jabbar - config dot XML over the communications manager configuration or vice-versa one way you can tell is to check the cached you see m90 config store docked at section this shows the configuration jabber has received from communications manager and may also show the current LDAP credentials origin here it is the service profile from Communications Manager now that the configure is fixed I will sign out and back into jabber as you can see not only are the contact display names result but a directory search works properly let's use the contact resolution tool to perform a search for Pete again the LDAP and from a looks complete and we can see the resolution results successfully I hope you found this video helpful in troubleshooting Jabar contact resolution issues thank you for watching

Channel: Cisco

Views: 4,291

Keywords: TAC Videos, Jabber, Contact, Search, Resolution

Id: 8alOU9a26_Q

Length: 6min 39sec (399 seconds)

Published: Thu Feb 06 2020