<?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 federate CUPS 8.5 with cisco.com in Unified Communications Infrastructure</title>
    <link>https://community.cisco.com/t5/unified-communications-infrastructure/federate-cups-8-5-with-cisco-com/m-p/1772371#M60684</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have not. Extremely frustrating. We are getting the exact error as you are with the &lt;NOT-AUTHORIZED&gt; deal on server dialback. We are using a CA issued certificate.&lt;/NOT-AUTHORIZED&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 10 Jul 2012 15:29:53 GMT</pubDate>
    <dc:creator>Ethan Haberman</dc:creator>
    <dc:date>2012-07-10T15:29:53Z</dc:date>
    <item>
      <title>federate CUPS 8.5 with cisco.com</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/federate-cups-8-5-with-cisco-com/m-p/1772366#M60679</link>
      <description>&lt;P&gt;We are a cisco partner.&amp;nbsp; I would like to federate our presence domain to cisco.com so we can collaborate across jabber.&amp;nbsp; I've got it working to google talk.&amp;nbsp; Are there special requirements to make this work with cisco.com?&lt;/P&gt;</description>
      <pubDate>Tue, 19 Mar 2019 10:56:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/federate-cups-8-5-with-cisco-com/m-p/1772366#M60679</guid>
      <dc:creator>joshw</dc:creator>
      <dc:date>2019-03-19T10:56:45Z</dc:date>
    </item>
    <item>
      <title>federate CUPS 8.5 with cisco.com</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/federate-cups-8-5-with-cisco-com/m-p/1772367#M60680</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Most likely no. I'll keep it to any others saying otherwise.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CUPS XMPP federation Guide with WebEx Connect&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/voice_ip_comm/cups/8_6/english/integration_notes/Federation/Planning_chapter.html"&gt;http://www.cisco.com/en/US/docs/voice_ip_comm/cups/8_6/english/integration_notes/Federation/Planning_chapter.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Nov 2011 23:14:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/federate-cups-8-5-with-cisco-com/m-p/1772367#M60680</guid>
      <dc:creator>Md Hasan</dc:creator>
      <dc:date>2011-11-14T23:14:59Z</dc:date>
    </item>
    <item>
      <title>federate CUPS 8.5 with cisco.com</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/federate-cups-8-5-with-cisco-com/m-p/1772368#M60681</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you had any luck with this? We are attempting the same federation.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Feb 2012 17:09:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/federate-cups-8-5-with-cisco-com/m-p/1772368#M60681</guid>
      <dc:creator>Ethan Haberman</dc:creator>
      <dc:date>2012-02-14T17:09:46Z</dc:date>
    </item>
    <item>
      <title>federate CUPS 8.5 with cisco.com</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/federate-cups-8-5-with-cisco-com/m-p/1772369#M60682</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No.&amp;nbsp; I've worked with several folks from Cisco on this but you yet had any luck.&amp;nbsp; Can anyone please chime in and offer some assistance?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Feb 2012 17:40:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/federate-cups-8-5-with-cisco-com/m-p/1772369#M60682</guid>
      <dc:creator>joshw</dc:creator>
      <dc:date>2012-02-14T17:40:00Z</dc:date>
    </item>
    <item>
      <title>federate CUPS 8.5 with cisco.com</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/federate-cups-8-5-with-cisco-com/m-p/1772370#M60683</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you ever have any luck with getting your CUP federation up to cisco.com?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jun 2012 20:01:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/federate-cups-8-5-with-cisco-com/m-p/1772370#M60683</guid>
      <dc:creator>joshw</dc:creator>
      <dc:date>2012-06-28T20:01:09Z</dc:date>
    </item>
    <item>
      <title>federate CUPS 8.5 with cisco.com</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/federate-cups-8-5-with-cisco-com/m-p/1772371#M60684</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have not. Extremely frustrating. We are getting the exact error as you are with the &lt;NOT-AUTHORIZED&gt; deal on server dialback. We are using a CA issued certificate.&lt;/NOT-AUTHORIZED&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jul 2012 15:29:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/federate-cups-8-5-with-cisco-com/m-p/1772371#M60684</guid>
      <dc:creator>Ethan Haberman</dc:creator>
      <dc:date>2012-07-10T15:29:53Z</dc:date>
    </item>
    <item>
      <title>federate CUPS 8.5 with cisco.com</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/federate-cups-8-5-with-cisco-com/m-p/1772372#M60685</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Still we are trying to federate with cisco.com but no luck yet. Everything is looks fine. both domain (&lt;/P&gt;&lt;P&gt;my domain and cisco domain) &lt;SPAN style="font-size: 10pt;"&gt;is resolved from outside through XMPP port &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;5269 &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;. I can talk to gtalk but not cisco.com.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Jul 2013 09:48:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/federate-cups-8-5-with-cisco-com/m-p/1772372#M60685</guid>
      <dc:creator>Muaaz El Kamali</dc:creator>
      <dc:date>2013-07-16T09:48:02Z</dc:date>
    </item>
    <item>
      <title>federate CUPS 8.5 with cisco.com</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/federate-cups-8-5-with-cisco-com/m-p/1772373#M60686</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm not positive that WebEx Messenger (which Cisco.com uses, not on-prem) supports DNS dialback. If memory serves you need to set TLS Optional and *uncheck* "Require client-side security certificates" on CUPS. I spent a few minutes hunting but cannot find documentation to backup the lack of dialback support; treat this as a hunch.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, your CA-signed certificate:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Does the server's domain match the presence domain specified under System Topology &amp;gt; Settings?&lt;/LI&gt;&lt;LI&gt;Is the server's FQDN resolvable from external DNS to the NATed IP(s)?&lt;/LI&gt;&lt;LI&gt;Is the certificate installed in the xmpp-server store (and the signing CA(s) in the xmpp-server-trust store) or only Tomcat?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please remember to &lt;A _jive_internal="true" href="https://community.cisco.com/docs/DOC-6212"&gt;rate helpful responses&lt;/A&gt; and identify &lt;A _jive_internal="true" href="https://community.cisco.com/community/help#discussions_questions"&gt;helpful&lt;/A&gt; or &lt;A _jive_internal="true" href="https://community.cisco.com/community/help#discussions_correct"&gt;correct&lt;/A&gt; answers.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Jul 2013 13:45:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/federate-cups-8-5-with-cisco-com/m-p/1772373#M60686</guid>
      <dc:creator>Jonathan Schulenberg</dc:creator>
      <dc:date>2013-07-16T13:45:13Z</dc:date>
    </item>
    <item>
      <title>federate CUPS 8.5 with cisco.com</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/federate-cups-8-5-with-cisco-com/m-p/1772374#M60687</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The problem we had was that our domain i.e."company.com" was registered as a web-ex connect domain.&amp;nbsp; In other words, it was being hosted by cisco webex.&amp;nbsp; In order to correct the problem, I had to open a trouble ticket with webex connect and they had to do something to flush our domain from their system.&amp;nbsp; They told me that it would require a change-control on their end and implied that it was "major".&amp;nbsp; Once they made their correction, we were able to federate our on-prem CUP server to cisco.com.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Jul 2013 14:31:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/federate-cups-8-5-with-cisco-com/m-p/1772374#M60687</guid>
      <dc:creator>joshw</dc:creator>
      <dc:date>2013-07-16T14:31:34Z</dc:date>
    </item>
    <item>
      <title>federate CUPS 8.5 with cisco.com</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/federate-cups-8-5-with-cisco-com/m-p/1772375#M60688</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ah! They had to de-provision your domain from WebEx Messenger/Connect. Nice catch.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Jul 2013 15:04:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/federate-cups-8-5-with-cisco-com/m-p/1772375#M60688</guid>
      <dc:creator>Jonathan Schulenberg</dc:creator>
      <dc:date>2013-07-16T15:04:48Z</dc:date>
    </item>
  </channel>
</rss>

