05-18-2018 07:27 AM - edited 03-17-2019 07:32 PM
Hello,
we currently run Jabber Version 11.5.5 with CUCM 11.5 SU3 and everything is fine. We now want to upgrade to a current release and just found out, that contact/name resolution for incoming caller ID is not working for us with Jabber 11.8 onwards. We tested the latest versions of 11.8, 11.9, 12.0. With Version 11.7 it is working fine.
We use CDI/LDAP as Directory Integration. No UDS. All Jabber Clients are connect to the same Domain Controller.
The incoming caller ID will only be showed as E164+ number. So I have just this number in my call history. When I now search the user in Jabber within the search field I will get a match and then the "unknown" number in the call history list will then be turned into the correct name.
We setup Directory Integration via UC Service profiles in CUCM. Out Jabber-config.xml which is assigned to the user's CSF device is blank/empty.
Both Jabber clients are registered to the same CUCM, but they are not at the same location. Test Jabber 1 is located to a branch office and the call comes in via ISDN as external call. After the caller ID comes in via H.323 Gateway, there are Directory Lookup rules who transform the caller ID from 006732… into +496732… This number will be looked up to the LDAP Directory. That's my undestanding of this process.
Please let me know if someone has an idea or if I am wrong in something.
Regards
Rene
Solved! Go to Solution.
09-03-2018 03:08 AM
05-19-2018 05:17 AM
09-03-2018 03:08 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide