<?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 Are all servers the same in Collaboration Applications</title>
    <link>https://community.cisco.com/t5/collaboration-applications/jabber-location/m-p/2922378#M11285</link>
    <description>&lt;P&gt;Are all servers the same version? and using the same Jabber client version?&lt;/P&gt;</description>
    <pubDate>Thu, 28 Apr 2016 14:35:28 GMT</pubDate>
    <dc:creator>Jaime Valencia</dc:creator>
    <dc:date>2016-04-28T14:35:28Z</dc:date>
    <item>
      <title>Jabber Location</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-location/m-p/2922377#M11284</link>
      <description>&lt;P&gt;Hello All.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Ok.. so we have 2 Jabber clusters both with 2 cups servers in each.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;When you are assigned to&amp;nbsp;a Cups server on&amp;nbsp;Cluster1 Locations&amp;nbsp;are not being displayed. If I move the user over to&amp;nbsp;one of the Cups&amp;nbsp;servers on&amp;nbsp;&amp;nbsp;Cluster&amp;nbsp;2&amp;nbsp;all locational setting are displaying.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I have logged on to al 4 Cups server and all services are up and running. Can anyone assist with this issue?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thank you in advance.. &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 18 Mar 2019 01:04:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-location/m-p/2922377#M11284</guid>
      <dc:creator>james.grieve21</dc:creator>
      <dc:date>2019-03-18T01:04:17Z</dc:date>
    </item>
    <item>
      <title>Are all servers the same</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-location/m-p/2922378#M11285</link>
      <description>&lt;P&gt;Are all servers the same version? and using the same Jabber client version?&lt;/P&gt;</description>
      <pubDate>Thu, 28 Apr 2016 14:35:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-location/m-p/2922378#M11285</guid>
      <dc:creator>Jaime Valencia</dc:creator>
      <dc:date>2016-04-28T14:35:28Z</dc:date>
    </item>
    <item>
      <title>Hi Jamie,</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-location/m-p/2922379#M11286</link>
      <description>&lt;P&gt;Hi Jamie,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks for you response. All 4 servers are the same version.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I tested this on one user who is on&amp;nbsp;Jabber Client&amp;nbsp;11.1.1, &amp;nbsp;Presence User Assigned to Cluster 1 got no location. Assigned the same user to Cluster 2 and they can see location settings.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;It may not sound like much of an issue but we work out of about 20 different offices so this option is a big deal for us.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Apr 2016 14:42:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-location/m-p/2922379#M11286</guid>
      <dc:creator>james.grieve21</dc:creator>
      <dc:date>2016-04-28T14:42:09Z</dc:date>
    </item>
    <item>
      <title>OK, I actually thought you</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-location/m-p/2922380#M11287</link>
      <description>&lt;P&gt;OK, I actually thought you meant this happened when moving in the same subcluster.&lt;/P&gt;
&lt;P&gt;First thing I'd check, is if location is actually enabled in cluster 1 in the jabber-config.xml, and if clients are actually getting the config file.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Apr 2016 14:45:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-location/m-p/2922380#M11287</guid>
      <dc:creator>Jaime Valencia</dc:creator>
      <dc:date>2016-04-28T14:45:17Z</dc:date>
    </item>
    <item>
      <title>First thing first... are you</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-location/m-p/2922381#M11288</link>
      <description>&lt;P&gt;First thing first... are you using BDI, EDI or UDS?&lt;/P&gt;
&lt;P&gt;If you're using EDI or UDS, then unless you purposely disabled the Location feature through the jabber-config.xml file and uploaded the xml file to your TFTP server, then you should be Ok. By default, the following parameters are defined as;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Location_Enabled = True&lt;/P&gt;
&lt;P&gt;LOCATION_MATCHING_MODE&amp;nbsp;= MacAddressOnly&lt;/P&gt;
&lt;P&gt;Location_Mode = ENABLED&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;As far as I know, there's no way to advertise or bulk the same 20 locations for all users. The location settings are fully customizable (i.e. users can add/edit/delete locations) and they are considered unique&amp;nbsp;to&amp;nbsp;each user.&lt;/P&gt;
&lt;P&gt;I agree with Jaime, please check your Cisco Unified Communications Manager TFTP servers and make sure the jabber-config.xml files exist, and they are accessible. You should be able to quickly view your jabber-config.xml by going to; &lt;A href="http://&amp;lt;TFTP_Server&amp;gt;:6970/jabber-config.xml&amp;nbsp;" target="_blank"&gt;http://&amp;lt;TFTP_Server&amp;gt;:6970/jabber-config.xml&amp;nbsp;&lt;/A&gt;; If you have two TFTP servers within the same cluster, then please check both jabber-config.xml files since they might be different.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Apr 2016 22:02:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-location/m-p/2922381#M11288</guid>
      <dc:creator>Mark Swanson</dc:creator>
      <dc:date>2016-04-28T22:02:25Z</dc:date>
    </item>
  </channel>
</rss>

