<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
Hi Aaron,<br>
<br>
<p>The auto-discovery feature in the Jabber client that you are speaking of uses DNS service discovery records (SRV). For the Jabber client, internally, it is looking for _cisco-uds._tcp.<i>domain.tld</i><i>
</i>(externally it would be looking for _collab-edge._tls.<i>domain.tld</i>)<i>. </i>
You can research the topic more at:</p>
<p><br>
</p>
<p><a title="Ctrl+Click or tap to follow the link" id="LPlnk352606" href="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">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</a></p>
<br>
<p>If you already have the internal SRV record created per Cisco's Documentation, and it still isn't working correctly, the user's login suffix (@domain.tld) could potentially be provisioned by Cisco's cloud-based WebEx Meeting service, in which case the Jabber
client will always prefer that as an authentication mechanism (unless you exclude the method in the jabber-config.xml file). The Jabber mobile clients work a little differently when it comes to preventing them to authenticate with Cisco's cloud-based WebEx
Meeting service. My guess is though, if the domain were provisioned for the service, you would likely already know about it.</p>
<p><br>
</p>
<p>Beyond that, and assuming the SRV record is created correctly, the client itself may have other issues related to DNS lookups. You may try a simple client reset / clear the cache files, if you have not already. If you would like to collect the PRT logs and
send them to this list I'm sure someone can look through them for you.</p>
<p><br>
</p>
<p>Hope this helps,</p>
<p><br>
</p>
<p>Ryan<br>
</p>
<p><br>
</p>
<p><i></i><br>
</p>
<div style="color: rgb(0, 0, 0);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" color="#000000" face="Calibri, sans-serif"><b>From:</b> cisco-voip <cisco-voip-bounces@puck.nether.net> on behalf of Aaron Banks <amichaelbanks@hotmail.com><br>
<b>Sent:</b> Wednesday, November 4, 2015 10:16 AM<br>
<b>To:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> [cisco-voip] Jabber - auto detect server</font>
<div> </div>
</div>
<div>
<div dir="ltr">I've had some trouble getting jabber to auto detect the IM&P server. Every time a new user signs in, they have to put in the IP of the server. Anyone have tricks to offer to avoid using the IP or FQDN?<br>
</div>
</div>
</div>
</div>
</body>
</html>