Jabber for Windows 10.6 and EDI Directory Integration

[Rene Mueller]

Hi,

I want to setup J4W to use always the same Global Catalog (GC) Server for Directory Integration (we do have more than one GC). For this to setup, I want to be sure, that I understand the design of directory Integration in IM+P 10.5 correctly.

As the Deployment Guide tells me that there are EDI and BDI as Connection Types to connect to GC. And there is the possibility to setup a Service Profile in CUCM and/or to setup all these parameters in jabber-config.xml (Service Profile will have priority).

Also, the deployment guide tells me, that BDI is used with Jabber for IOS/Android and EDI is used with J4W. If J4W is automatecially using EDI, does it mean, it always does a SRV Record discovering to get it's gc?

In the deployment Guide, there is a parameter _gc._msdcs._tcp.domain.com for discovery.

I did a test and delete all the directory stuff out of my jabber-config.xml and put in a single GC to my Service Profile in CUCM. Anyway. When I start Jabber and do a Wireshark capture, I can see, that Jabber is connected to another GC, not that one I configured in my service Profile.

Hope someone can help.

Rene

[Jaime Valencia]

Hardcode the GC connection in the jabber-config.xml for those Windows clients.

Otherwise as you have seen, you'll use whatever SRV record it can find and connect to.

[Rene Mueller]

So does it mean, that jabber-config.xml takes preference over SRV Record Discovery?

[Jaime Valencia]

Correct

[Rene Mueller]

Hi,

can you explain which DNS Record Jabber is using to find his DC/GC? In the Guide I can find _gc._msdcs._tcp.domain.com but we don't have this Record in our DNS. But Jabber is able to connect to a DNS. UC Service Profile and jabber-config.xml are empty with no directory Servers.

Regards