<?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 Yes I know, that's what I in Collaboration Applications</title>
    <link>https://community.cisco.com/t5/collaboration-applications/jabber-for-windows-directory-question/m-p/3052834#M7515</link>
    <description>&lt;P&gt;Yes I know, that's what I usually do.&amp;nbsp; But in this case it would be better to draw the extension from CallManagers database.&amp;nbsp; Either by device or the Primary Extension listed on the End User page.&amp;nbsp; I'm pretty sure this isn't an option.&amp;nbsp; But you don't know what you don't know, so it's worth asking the hive mind.&lt;/P&gt;
&lt;P&gt;Thanks for the response!&lt;/P&gt;</description>
    <pubDate>Wed, 19 Apr 2017 16:40:58 GMT</pubDate>
    <dc:creator>jmachiggins</dc:creator>
    <dc:date>2017-04-19T16:40:58Z</dc:date>
    <item>
      <title>JAbber for Windows Directory Question</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-for-windows-directory-question/m-p/3052832#M7513</link>
      <description>&lt;P&gt;I've been looking around to see what kind of options are available for phone numbers listed in the Jabber for Windows directory.&amp;nbsp; Usually we draw numbers from AD and use the IpPhone field.&amp;nbsp; For various reasons this may not be possible in this case.&amp;nbsp; It would be ideal if the number listed could just be the primary extension of the end user.&amp;nbsp; Is there any way to do that?&amp;nbsp; I've found nothing so far, but figured someone here would know.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks in Advance,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;J&lt;/P&gt;</description>
      <pubDate>Mon, 18 Mar 2019 01:49:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-for-windows-directory-question/m-p/3052832#M7513</guid>
      <dc:creator>jmachiggins</dc:creator>
      <dc:date>2019-03-18T01:49:06Z</dc:date>
    </item>
    <item>
      <title>You can adjust the field</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-for-windows-directory-question/m-p/3052833#M7514</link>
      <description>&lt;P&gt;You can adjust the field mapping in the jabber-config.xml if you don't want to use ipPhone&lt;/P&gt;</description>
      <pubDate>Wed, 19 Apr 2017 16:36:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-for-windows-directory-question/m-p/3052833#M7514</guid>
      <dc:creator>Jaime Valencia</dc:creator>
      <dc:date>2017-04-19T16:36:23Z</dc:date>
    </item>
    <item>
      <title>Yes I know, that's what I</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-for-windows-directory-question/m-p/3052834#M7515</link>
      <description>&lt;P&gt;Yes I know, that's what I usually do.&amp;nbsp; But in this case it would be better to draw the extension from CallManagers database.&amp;nbsp; Either by device or the Primary Extension listed on the End User page.&amp;nbsp; I'm pretty sure this isn't an option.&amp;nbsp; But you don't know what you don't know, so it's worth asking the hive mind.&lt;/P&gt;
&lt;P&gt;Thanks for the response!&lt;/P&gt;</description>
      <pubDate>Wed, 19 Apr 2017 16:40:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-for-windows-directory-question/m-p/3052834#M7515</guid>
      <dc:creator>jmachiggins</dc:creator>
      <dc:date>2017-04-19T16:40:58Z</dc:date>
    </item>
    <item>
      <title>You'd need to switch to UDS</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-for-windows-directory-question/m-p/3052835#M7516</link>
      <description>&lt;P&gt;You'd need to switch to UDS to make that happen, you cannot pull some fields from LDAP and others from UDS, it's forcefully one or the other.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Apr 2017 16:42:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-for-windows-directory-question/m-p/3052835#M7516</guid>
      <dc:creator>Jaime Valencia</dc:creator>
      <dc:date>2017-04-19T16:42:58Z</dc:date>
    </item>
    <item>
      <title>So I've looked at UDS and it</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-for-windows-directory-question/m-p/3052836#M7517</link>
      <description>&lt;P&gt;So I've looked at UDS and it doesn't seem to provide any way to manipulate which field is read for the directory numbers.&amp;nbsp; I haven't found this documented anywhere yet either.&amp;nbsp; If it just reads the 'telephone number' field then this won't solve my issue as that's just pulled from AD.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Apr 2017 16:59:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-for-windows-directory-question/m-p/3052836#M7517</guid>
      <dc:creator>jmachiggins</dc:creator>
      <dc:date>2017-04-19T16:59:05Z</dc:date>
    </item>
    <item>
      <title>That's correct, field mapping</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-for-windows-directory-question/m-p/3052837#M7518</link>
      <description>&lt;P&gt;That's correct, field mapping is only for LDAP, if you're using something different in the phone field than the actual DN from the user in CUCM, you cannot map that.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Apr 2017 17:01:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-for-windows-directory-question/m-p/3052837#M7518</guid>
      <dc:creator>Jaime Valencia</dc:creator>
      <dc:date>2017-04-19T17:01:17Z</dc:date>
    </item>
  </channel>
</rss>

