<?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 you referring to login in Collaboration Applications</title>
    <link>https://community.cisco.com/t5/collaboration-applications/how-keep-the-jabber-client-configuration/m-p/2864379#M11078</link>
    <description>&lt;P&gt;Are you referring to login through internal or external network?&lt;/P&gt;
&lt;P&gt;Either way, you should be able to setup proper SRV record to instruct the Jabber client to find proper server to login with. In that case, you don't need to key in any server / TFTP info.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;You can refer to Jabber deployment guide for how to set up that.&lt;/P&gt;
&lt;P&gt;Basically:&lt;/P&gt;
&lt;P&gt;_collab-edge._tls."your domain" -&amp;gt; External&lt;/P&gt;
&lt;P&gt;_cisco-uds._tcp."your domain" -&amp;gt; internal&lt;/P&gt;
&lt;P&gt;_cuplogin._tcp.&lt;SPAN&gt;"your domain" -&amp;gt; internal&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 20 Apr 2016 04:03:15 GMT</pubDate>
    <dc:creator>weihan-lu</dc:creator>
    <dc:date>2016-04-20T04:03:15Z</dc:date>
    <item>
      <title>How keep the jabber client configuration?</title>
      <link>https://community.cisco.com/t5/collaboration-applications/how-keep-the-jabber-client-configuration/m-p/2864377#M11076</link>
      <description>&lt;P&gt;Hi team,&lt;/P&gt;
&lt;P&gt;My jabber client on android is working properly. But Everytime when I make a logou and login I must put the configuration like TFTP server IP again.&lt;/P&gt;
&lt;P&gt;So, How Can I keep this configuration like default?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;regards&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 18 Mar 2019 01:02:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/how-keep-the-jabber-client-configuration/m-p/2864377#M11076</guid>
      <dc:creator>Jean Lofrano</dc:creator>
      <dc:date>2019-03-18T01:02:46Z</dc:date>
    </item>
    <item>
      <title>Who can help me please?</title>
      <link>https://community.cisco.com/t5/collaboration-applications/how-keep-the-jabber-client-configuration/m-p/2864378#M11077</link>
      <description>&lt;P&gt;Who can help me please?&lt;/P&gt;</description>
      <pubDate>Tue, 19 Apr 2016 19:53:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/how-keep-the-jabber-client-configuration/m-p/2864378#M11077</guid>
      <dc:creator>Jean Lofrano</dc:creator>
      <dc:date>2016-04-19T19:53:47Z</dc:date>
    </item>
    <item>
      <title>Are you referring to login</title>
      <link>https://community.cisco.com/t5/collaboration-applications/how-keep-the-jabber-client-configuration/m-p/2864379#M11078</link>
      <description>&lt;P&gt;Are you referring to login through internal or external network?&lt;/P&gt;
&lt;P&gt;Either way, you should be able to setup proper SRV record to instruct the Jabber client to find proper server to login with. In that case, you don't need to key in any server / TFTP info.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;You can refer to Jabber deployment guide for how to set up that.&lt;/P&gt;
&lt;P&gt;Basically:&lt;/P&gt;
&lt;P&gt;_collab-edge._tls."your domain" -&amp;gt; External&lt;/P&gt;
&lt;P&gt;_cisco-uds._tcp."your domain" -&amp;gt; internal&lt;/P&gt;
&lt;P&gt;_cuplogin._tcp.&lt;SPAN&gt;"your domain" -&amp;gt; internal&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Apr 2016 04:03:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/how-keep-the-jabber-client-configuration/m-p/2864379#M11078</guid>
      <dc:creator>weihan-lu</dc:creator>
      <dc:date>2016-04-20T04:03:15Z</dc:date>
    </item>
  </channel>
</rss>

