<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Cisco Jabber Directory in Collaboration Applications</title>
    <link>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-directory/m-p/3870027#M40040</link>
    <description>Ideally it should query _gc._tcp.cyz.com instead it queries _gc._tcp.drm-gc.xyz.com&lt;BR /&gt;&lt;BR /&gt;drm-gc is HOSTNAME for BDI&lt;BR /&gt;</description>
    <pubDate>Sun, 09 Jun 2019 15:28:38 GMT</pubDate>
    <dc:creator>Shri2</dc:creator>
    <dc:date>2019-06-09T15:28:38Z</dc:date>
    <item>
      <title>Cisco Jabber Directory</title>
      <link>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-directory/m-p/3867919#M39970</link>
      <description>&lt;P&gt;I am aware that W4J uses EDI directory type. But if machine is registered to AD domain, then we don't need to configure EDI type configuration in CUCM as&amp;nbsp;jabber client automatically discovers the directory and connects to a Global Catalog server in that domain&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our customer setup.&lt;/P&gt;&lt;P&gt;We have configured BDI for endpoints other than J4W. We have not configured EDI/UDS.&lt;/P&gt;&lt;P&gt;BDI has been configured with host name drm-gc.xyz.com ( xyz.com is domain )&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For J4W, ideally jabber should do the SRV query to global catalog as&amp;nbsp;_gc._tcp.pfizer.com&lt;/P&gt;&lt;P&gt;But in the logs, i can see jabber is doing SRV as below&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;About to make DNS SRV record query '_gc._tcp.drm-gc.xyz.com.'&lt;/P&gt;&lt;P&gt;DNS query _gc._tcp.drm-gc.pfizer.com. has failed: DNS name does not exist&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So why jabber is querying to gloabl catalog by adding drm-gc which was configured for BDI.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Another strange is, as we haven't configured EDI/UDS so ideally J4W shouldn't connect to directory but it successful connects to drm.gc.xyz.com which is conigured for BDI....&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2019 07:23:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-directory/m-p/3867919#M39970</guid>
      <dc:creator>Shri2</dc:creator>
      <dc:date>2019-06-05T07:23:46Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Jabber Directory</title>
      <link>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-directory/m-p/3868026#M39974</link>
      <description>on a domain machine can you open a command prompt and run the following:&lt;BR /&gt;nslookup&lt;BR /&gt;set type=SRV&lt;BR /&gt;_gc._tcp.drm-gc.xyz.com&lt;BR /&gt;&lt;BR /&gt;See if the record is properly reachable from a basic lookup.&lt;BR /&gt;&lt;BR /&gt;Also for what its worth, I have alsways found the most success (and less headache) with UDS, as long as CUCM is syncing with LDAP properly. UDS functions across all platforms, including MRA where BDI can be limited.</description>
      <pubDate>Wed, 05 Jun 2019 11:49:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-directory/m-p/3868026#M39974</guid>
      <dc:creator>Mike_Brezicky</dc:creator>
      <dc:date>2019-06-05T11:49:16Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Jabber Directory</title>
      <link>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-directory/m-p/3868249#M39983</link>
      <description>I tried that it doesn’t work.. srv query works for _gc._ldap.xyz.com&lt;BR /&gt;</description>
      <pubDate>Wed, 05 Jun 2019 16:00:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-directory/m-p/3868249#M39983</guid>
      <dc:creator>Shri2</dc:creator>
      <dc:date>2019-06-05T16:00:06Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Jabber Directory</title>
      <link>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-directory/m-p/3868276#M39985</link>
      <description>&lt;P&gt;&lt;A href="https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-adts/c1987d42-1847-4cc9-acf7-aab2136d6952" target="_blank"&gt;https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-adts/c1987d42-1847-4cc9-acf7-aab2136d6952&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The creation of DNS Resource Records is specified in [RFC2136].&lt;/P&gt;
&lt;P&gt;The name of an SRV Resource Record is in the following form:&lt;/P&gt;
&lt;P&gt;Service.Proto.Name TTL Class SRV Priority Weight Port Target&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2019 16:53:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-directory/m-p/3868276#M39985</guid>
      <dc:creator>Jaime Valencia</dc:creator>
      <dc:date>2019-06-05T16:53:22Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Jabber Directory</title>
      <link>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-directory/m-p/3868379#M39987</link>
      <description>Thanks for the response Jaime,&lt;BR /&gt;I looked into the link you have provided, couldn’t find what I am looking for...&lt;BR /&gt;</description>
      <pubDate>Wed, 05 Jun 2019 19:10:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-directory/m-p/3868379#M39987</guid>
      <dc:creator>Shri2</dc:creator>
      <dc:date>2019-06-05T19:10:06Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Jabber Directory</title>
      <link>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-directory/m-p/3868492#M39990</link>
      <description>&lt;P&gt;Which one is RFC compliant??&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;_gc._tcp.xyz.com OR&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;_gc._ldap.xyz.com?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2019 22:34:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-directory/m-p/3868492#M39990</guid>
      <dc:creator>Jaime Valencia</dc:creator>
      <dc:date>2019-06-05T22:34:52Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Jabber Directory</title>
      <link>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-directory/m-p/3870027#M40040</link>
      <description>Ideally it should query _gc._tcp.cyz.com instead it queries _gc._tcp.drm-gc.xyz.com&lt;BR /&gt;&lt;BR /&gt;drm-gc is HOSTNAME for BDI&lt;BR /&gt;</description>
      <pubDate>Sun, 09 Jun 2019 15:28:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-directory/m-p/3870027#M40040</guid>
      <dc:creator>Shri2</dc:creator>
      <dc:date>2019-06-09T15:28:38Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Jabber Directory</title>
      <link>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-directory/m-p/3870097#M40041</link>
      <description>&lt;P&gt;What is the login you use on Jabber? is it the same you use on your laptop?&lt;/P&gt;
&lt;P&gt;You can always hard-code the configuration with the service profile and that would avoid any issue.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jun 2019 02:57:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-directory/m-p/3870097#M40041</guid>
      <dc:creator>Jaime Valencia</dc:creator>
      <dc:date>2019-06-10T02:57:25Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Jabber Directory</title>
      <link>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-directory/m-p/3870685#M40054</link>
      <description>Yes same login as laptop&lt;BR /&gt;</description>
      <pubDate>Tue, 11 Jun 2019 06:21:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-directory/m-p/3870685#M40054</guid>
      <dc:creator>Shri2</dc:creator>
      <dc:date>2019-06-11T06:21:38Z</dc:date>
    </item>
  </channel>
</rss>

