Jabber 9 (Mac), problemas com AD

Hi Jonathan,

I'm having the same problem on Jabber v9.2.1 on UCM/IMP 9.1. When is a jabber-config.xml file needed? That document says:

Cisco Jabber for Mac Configuration Requirements
In most environments, Cisco Jabber for Mac does not require any configuration. You should create a configuration file for Cisco Jabber for Mac only if the default configuration does not suit your environment or you require custom configuration.

Windows clients can directory search just fine so the back-end seems to be setup fine.

Jabber 9 (Mac), problemas com AD

The Windows client is set to use EDI by default which isn't available on any other platform. This is why the "by default" config works: the client just asks the Windows ADSI API. Since none of the 9.2 clients read the UC Service Profiles from CUCM (yet), you need to define a BDI integration.

Think of the XML file as the way to get features added into Jabber faster than they can get those changes merged into CUCM.

Jabber 9 (Mac), problemas com AD

Thanks for the reply. I understand that the Mac doesn't use EDI, but from what I can see in my logs the Mac client is reading at least some profile information from UCM or IMP. For example, it knows the UCM name for the AD bind account and if I'm not mistaken it must be reading that from UCM or IMP. So that and the information from the help file I quoted made me think the Mac Jabber client's defaults would be appropriate for the platform according to that document referenced above. For example, the default for BDILDAPServerType is 'AD', and the rest of the defaults listed look like exactly what I want. Apparently that isn't correct, but I'll follow up and post whatever works in the end next week.

Jabber 9 (Mac), problemas com AD

Hi!

I wrote an xml file format BDI, still did not work. The debug shows the values ​​of the ad, but not jabber displays pictures or contact details (coming from the ad). doing research in the contact directory, with the contacts list from AD and photos are displayed but does not show the contact information (name, phone) ..

Re: Jabber 9 (Mac), problemas com AD

I created a jabber-config.xml file and it is being downloaded onto my Mac in the right place. Problem is, packet captures show that Mac Jabber 9.2.1 is using port 3268 no matter that my jabber-config.xml file says

636. Port 3268 isn't used in our UCM config at all, so it seems the client is just defaulting to 3268 and not respecting the config file.

Jabber 9 (Mac), problemas com AD

Well here's what seems to be working for me for Active Directory for what it's worth. Maybe you can adapt it for openldap. I might not even have needed a section for windows/EDI if it weren't for the fact that I need to use a custom 'BusinessPhone' parameter at our site so I think I needed a block of xml to stick that in somewhere.

Cisco Webex Calling is a cloud service that offers enterprise-grade calling features delivered from the Cisco Webex cloud. This platform is part of the complete Webex collaboration suite that serves the calling, messaging, meeting, team collaboration and...
view more

Cisco SX20 camera moving left right and shaking continuously. We have factory reset the devices still it is a same problem. Even change the camera of working devices with issue devices still the problem.Now the software version of the device is&nbsp...
view more

Hello Experts. We would like to write macro to create a button to switch sources during a call. The only possible view today is content on upside and participants down. This is not the best experience for user's perspective. Someone, could ...
view more

Joining Webex Meetings just got significantly faster – with fewer clicks and less time that’s needed to get into your meetings on desktop and mobile apps.
With our email template simplification, you can enjoy a sin...
view more