11-10-2011 10:45 AM - edited 03-19-2019 03:56 AM
We are a cisco partner. I would like to federate our presence domain to cisco.com so we can collaborate across jabber. I've got it working to google talk. Are there special requirements to make this work with cisco.com?
11-14-2011 03:14 PM
Hi
Most likely no. I'll keep it to any others saying otherwise.
CUPS XMPP federation Guide with WebEx Connect
Thanks
02-14-2012 09:09 AM
Have you had any luck with this? We are attempting the same federation.
02-14-2012 09:40 AM
No. I've worked with several folks from Cisco on this but you yet had any luck. Can anyone please chime in and offer some assistance?
06-28-2012 01:01 PM
Did you ever have any luck with getting your CUP federation up to cisco.com?
07-10-2012 08:29 AM
We have not. Extremely frustrating. We are getting the exact error as you are with the
07-16-2013 02:48 AM
Hi
Still we are trying to federate with cisco.com but no luck yet. Everything is looks fine. both domain (
my domain and cisco domain) is resolved from outside through XMPP port 5269 . I can talk to gtalk but not cisco.com.
07-16-2013 06:45 AM
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.
Also, your CA-signed certificate:
Please remember to rate helpful responses and identify helpful or correct answers.
07-16-2013 07:31 AM
The problem we had was that our domain i.e."company.com" was registered as a web-ex connect domain. In other words, it was being hosted by cisco webex. 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. They told me that it would require a change-control on their end and implied that it was "major". Once they made their correction, we were able to federate our on-prem CUP server to cisco.com.
07-16-2013 08:04 AM
Ah! They had to de-provision your domain from WebEx Messenger/Connect. Nice catch.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide