Secure LDAP CUCM Cluster 10.5 jabber client not working properly

[NOUSH]

Recently we have migrated our CUCM 10.5 cluster to LDAPS .But it looks like Jabber client machines are still communicating to LDAP server via port number 389 .Do we need to make any changes on jabber client.

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/215437-configure-cucm-for-secure-ldap-directory.html

[Vaijanath Sonvane]

Hi,

Do you have any Directory Service Type configured under UC Service which might be using port 389. The configuration is under User Management >> User Settings >> UC Service.

Also, verify your jabber-config.xml file for LDAP configuration.

[NOUSH]

Thanks Vaijananth. UC service port already changed to 636 and 3269  .Below are the all contents from my  jabber-config.xml file .

 <config version="1.0">
<Directory>
<DirectoryServerType>EDI</DirectoryServerType>
<OtherPhone>ipPhone</OtherPhone>
</Directory>
</config>

[Roger Kallberg]

I don’t think that you need to specify EDI for the directory server type in the Jabber configuration anymore. However I don’t know if this would have any impact on the problem at hand.

[Jaime Valencia]

That is expected if you only changed the LDAP integration for CUCM, Jabber has its own directory integration which can be completely different to that of CUCM and would need to be updated as well, refer to the Jabber documentation for the Jabber directory integration.

[NOUSH]

Thanks Jaime .Referred few documents but didn't get proper details .Could you please share any links

[Jaime Valencia]

Jabber documentation can be found here:

https://www.cisco.com/c/en/us/support/unified-communications/jabber-windows/products-installation-guides-list.html

[Roger Kallberg]

You should look at this configuration in CM.

We use global catalog over TLS, aka port 3269, because of that it's the recommendation from Cisco to get quicker response time for the clients.

[NOUSH]

Thanks Roger .Tried this steps .Still jabber clients communicates to LDAP server via port 389 . Can we block this from jabber configuration file?

Created new service profile and tried jabber phone only mode .That also didn't help .It looks like Jabber client automatically discovers the directory .How to block this

[Roger Kallberg]

As a reference this is the settings we use for Jabber (and now also the new Webex unified app).