Cisco Jabber windows call option and user addition issue
After uploading the jabber-config.xml (EDI-BDI) on the CUCM, the call option for new user contacts started appearing but the already existing contacts in Jabber client have still no call option. Also when we add new contacts to the Jabber client, it just disappears as such. Any one faced similar issue before. Below are the details and attached jabber-config.xml and LDAP profile snap.
We are using employeeNumber as attribute in LDAP configuration.
CUCM - 220.127.116.1100-4 UCCX - 18.104.22.16800-20
Jabber for windows - 9.7.0 (Tried with earlier version of jabber as well)
Just right click on the contacts which do not have the call option and select view profile, then see if those contacts that are added are they from the Outlook or the AD, if its AD then they will have a contact number and as such they will have the Call Option enabled.
If they are from outlook then delete the users and readd them by checking the view profile option to verify they are being pulled from AD.
Also if i assumed the issue differently then what it is please explain the whole scenario.
Note-: In case of J4W it will not connect to the directory using the LDAP profile info, it automatically verified and cnnects to the domain using your login creds.
The issue was because the LDAP attribute used was EmployeeNumber rather than the default attribute SAMAccount. I added the below string to the EDI-BDI file and restarted the services which fixed the issue.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...