<?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 All recent clients support in Collaboration Applications</title>
    <link>https://community.cisco.com/t5/collaboration-applications/jabber-ios-directory-uri-support/m-p/2981656#M9144</link>
    <description>&lt;P&gt;All recent clients support multi-domain&lt;/P&gt;
&lt;P&gt;No, you're not forced to use UDS, you can keep using EDI for J4W or BDI for all other clients.&lt;/P&gt;</description>
    <pubDate>Thu, 01 Dec 2016 16:29:33 GMT</pubDate>
    <dc:creator>Jaime Valencia</dc:creator>
    <dc:date>2016-12-01T16:29:33Z</dc:date>
    <item>
      <title>Jabber iOS Directory URI support</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-ios-directory-uri-support/m-p/2981655#M9143</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I am changing the IM addressing scheme to directoy URI, in order to enable multi Domain support in IMP for intercluster peering in a later stage.&lt;/P&gt;
&lt;P&gt;Is this supported in Jabber iOS devices? (where would I find this info?)&lt;/P&gt;
&lt;P&gt;If so, am I forced to use UDS as directory source, as a prereq seems to be using EDI or UDS (iOS devices do not use EDI)&lt;/P&gt;
&lt;P&gt;(info from the IMP config and admin guide:&amp;nbsp;&lt;A href="http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/configAdminGuide/11_5_1/CUP0_BK_CE08159C_00_config-admin-guide-imp-1151/CUP0_BK_CE08159C_00_config-admin-guide-imp-1151_chapter_0101.html#d32848e62a1635" target="_blank"&gt;http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/configAdminGuide/11_5_1/CUP0_BK_CE08159C_00_config-admin-guide-imp-1151/CUP0_BK_CE08159C_00_config-admin-guide-imp-1151_chapter_0101.html#d32848e62a1635&lt;/A&gt;)&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Will my Jabber for Windows clients then also use UDS instead of EDI? This would not be a desired setup.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;any help is welcome,&lt;/P&gt;
&lt;P&gt;Juan&lt;/P&gt;</description>
      <pubDate>Mon, 18 Mar 2019 01:31:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-ios-directory-uri-support/m-p/2981655#M9143</guid>
      <dc:creator>Juan Lopez Hernandez</dc:creator>
      <dc:date>2019-03-18T01:31:51Z</dc:date>
    </item>
    <item>
      <title>All recent clients support</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-ios-directory-uri-support/m-p/2981656#M9144</link>
      <description>&lt;P&gt;All recent clients support multi-domain&lt;/P&gt;
&lt;P&gt;No, you're not forced to use UDS, you can keep using EDI for J4W or BDI for all other clients.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Dec 2016 16:29:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-ios-directory-uri-support/m-p/2981656#M9144</guid>
      <dc:creator>Jaime Valencia</dc:creator>
      <dc:date>2016-12-01T16:29:33Z</dc:date>
    </item>
  </channel>
</rss>

