<?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 i see the following in Collaboration Applications</title>
    <link>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-invalid-username-password/m-p/2482817#M20115</link>
    <description>&lt;P&gt;i see the following information mentioned in the document;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/9_7/CJAB_BK_C606D8A9_00_cisco-jabber-dns-configuration-guide/CJAB_BK_C606D8A9_00_cisco-jabber-dns-configuration-guide_chapter_010.html#CJAB_RF_S2C1A378_00&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;"You should use the fully qualified domain name (FQDN) as the hostname in the SRV record."&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;in your case the hostname look to be ip address. If this is a lab setup can you try to ensure you correct this to FQDN( note this will also need A records) once done re test the log in. If this is a production setup kindly ensure you accommodate downtime before trying this.&lt;/P&gt;</description>
    <pubDate>Tue, 15 Apr 2014 16:38:48 GMT</pubDate>
    <dc:creator>Amit Kumar</dc:creator>
    <dc:date>2014-04-15T16:38:48Z</dc:date>
    <item>
      <title>Cisco Jabber Invalid Username/Password</title>
      <link>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-invalid-username-password/m-p/2482814#M20112</link>
      <description>&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;upgraded my cisco callmanager to 9.1.2SU1 (Previous version 9.1.1a) and add UDS COP file and now i have problem to login internal (via finding service , Manual is OK)&lt;/P&gt;&lt;P&gt;Any advice&lt;/P&gt;&lt;P&gt;Thanks for your help&lt;/P&gt;</description>
      <pubDate>Sun, 17 Mar 2019 23:06:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-invalid-username-password/m-p/2482814#M20112</guid>
      <dc:creator>c.carrion</dc:creator>
      <dc:date>2019-03-17T23:06:45Z</dc:date>
    </item>
    <item>
      <title>i see that it is trying to do</title>
      <link>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-invalid-username-password/m-p/2482815#M20113</link>
      <description>&lt;P&gt;i see that it is trying to do a UDS SRV query;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;PRE&gt;
About to make a dns request against _cisco-uds._tcp.domain.com.pe.
-- 2014-04-15 00:27:54.731 INFO [b2b8000] - [csf.dns][makeQuery] Making an SRV record request. _cisco-uds._tcp.domain.com.pe.&lt;/PRE&gt;

&lt;P&gt;and fails with the following message;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;PRE&gt;
Ucm Locator query has failed with FAILED_TO_FIND_HOME_UDS
-- 2014-04-15 00:27:54.761 WARNING [b0f5000] - [csf.config][fetchXmlFileSet] No information available after doing a fetch.
-- 2014-04-15 00:27:54.761 DEBUG [b0f5000] - [csf.config][fetchXmlFileSet] Returning: FAILED_TO_FIND_HOME_UDS
-- 2014-04-15 00:27:54.761 INFO [b0f5000] - [csf.config][fetchXmlFileSet] Time taken to complete the ucm-config library fetchXmlFileSet(): 0 seconds.
-- 2014-04-15 00:27:54.762 INFO [b0f5000] - [service-discovery][authenticate] Ucm90 Library Returned with Code FAILED_TO_FIND_HOME_UDS&lt;/PRE&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;is the UDS SRV record provisioned in the network ; or do you have _cuplogin record configured.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Apr 2014 15:59:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-invalid-username-password/m-p/2482815#M20113</guid>
      <dc:creator>Amit Kumar</dc:creator>
      <dc:date>2014-04-15T15:59:00Z</dc:date>
    </item>
    <item>
      <title>Hi, My srv records.&gt; set type</title>
      <link>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-invalid-username-password/m-p/2482816#M20114</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My srv records.&lt;/P&gt;&lt;P&gt;&amp;gt; set type=srv&lt;BR /&gt;&amp;gt; _cisco-uds._tcp.domain.com.pe&lt;BR /&gt;Server:&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;10.251.25.101&lt;BR /&gt;Address:&amp;nbsp;&amp;nbsp; &amp;nbsp;10.251.25.101#53&lt;/P&gt;&lt;P&gt;_cisco-uds._tcp.domain.com.pe &amp;nbsp;&amp;nbsp; service = 0 0 8443 10.251.1.10.&lt;BR /&gt;&amp;gt; _cuplogin._tcp.domain.com.pe&lt;BR /&gt;Server:&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;10.251.25.101&lt;BR /&gt;Address:&amp;nbsp;&amp;nbsp; &amp;nbsp;10.251.25.101#53&lt;/P&gt;&lt;P&gt;_cuplogin._tcp.domain.com.pe &amp;nbsp;&amp;nbsp; service = 0 0 8443 10.251.1.16.&lt;BR /&gt;&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your help&lt;/P&gt;</description>
      <pubDate>Tue, 15 Apr 2014 16:20:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-invalid-username-password/m-p/2482816#M20114</guid>
      <dc:creator>c.carrion</dc:creator>
      <dc:date>2014-04-15T16:20:02Z</dc:date>
    </item>
    <item>
      <title>i see the following</title>
      <link>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-invalid-username-password/m-p/2482817#M20115</link>
      <description>&lt;P&gt;i see the following information mentioned in the document;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/9_7/CJAB_BK_C606D8A9_00_cisco-jabber-dns-configuration-guide/CJAB_BK_C606D8A9_00_cisco-jabber-dns-configuration-guide_chapter_010.html#CJAB_RF_S2C1A378_00&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;"You should use the fully qualified domain name (FQDN) as the hostname in the SRV record."&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;in your case the hostname look to be ip address. If this is a lab setup can you try to ensure you correct this to FQDN( note this will also need A records) once done re test the log in. If this is a production setup kindly ensure you accommodate downtime before trying this.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Apr 2014 16:38:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-invalid-username-password/m-p/2482817#M20115</guid>
      <dc:creator>Amit Kumar</dc:creator>
      <dc:date>2014-04-15T16:38:48Z</dc:date>
    </item>
  </channel>
</rss>

