Webex connect federation with IBM, Microsoft, etc?

[eugene_oz]

Hi

Has anyone managed to configure federation between webex connect and

- IBM

- Microsoft itself

- Companies with Lync edge depolyments

- Google+

Are there any step by step guides as to what needs to be done on each side?

E.g. at the moment our existing Sametime users can federate with IBM by simply pointing their client to extst.ibm.com (they require ibm.com user ID's though)

Thanks,

Eugene

[mvild]

You can refer to the WebEx Connect Admin guide (search for federation): http://www.webex.com/webexconnect/orgadmin/help/index.htm

The main requirement it to enter the SRV records into DNS (documented in the Connect guide).

The SIP/SIMPLE based systems (MS and IBM) require an XMPP gateway to talk to the XMPP world.

Hope that helps.

[eugene_oz]

Thanks for the answer.

Sorry to be a pain, however to me it sounds like:

Step 1: configure SRV records

Step 3: enjoy the federation

What about Step 2? Is there anything else that need to be done in the Admin Console? What needs to be done on the partner side? Do they need to point explicietely to our domain? Whitelist it? How about a fairly common setup when the other side is running a Lync edge server?

[mvild]

Hi Eugene,

That's pretty much it. Did you go to the Admin guide I referred you to and searched for Federation? The first link it this and it will give you the details: http://www.webex.com/webexconnect/orgadmin/help/17169.htm 

That is pretty much it.  No need to add to whitelist in OrgAdmin

As for the OCS/Lync/BM side, we do not document those explicit instructions other then the the fact that they need an XMPP gateway to reach other XMPP systems.

Hope that further clarifies.

[eugene_oz]

Thanks for the reply.

How about Facebook: it provides options for various XMPP clients - iChat, Pidgin, etc - https://www.facebook.com/sitetour/chat.php

.... however Jabber client does not seem to allow to connect both to facebook and webex connect.

Is there a way around it (since facebook does notallow s2s federation)?

thanks

Eugene

[bjames]

Just to be clear the Cisco side uses the XMPP stanard/protocol. The others not so much, however if those companies implement an XMPP gateway then yes you can.

Sadly even Microsoft themselves don't use the XMPP gateway, but I heard it will be built into the next version of Lync, but it still has to be enabled.

Hope that helps

Bob James

[mvild · Accepted solution]

Yes, to your statement:

Just to be clear the Cisco side uses the XMPP stanard/protocol. The others not so much, however if those companies implement an XMPP gateway then yes you can.

[Ethan Haberman]

Are you aware of specific requirements for an organization to federate with WebEx Connect customers? We are using Cisco Unified Presence Server 8.6.4 and are trying to federate with partners in the WebEx Connect Cloud Service. (i.e. Cisco, NetApp, etc) We have configured all settings according to the Federation Guide provided in Cisco's documentation, but are receiving a <stream:error><not-authorized xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></stream:error> when attempting to add a contact. We are using a CA supplied certificate for the XMPP-S2S certificate and have succussfully federated with other XMPP domains such as gmail.com, but have not had any luck with WebEx Connect domains. The error I provided above seems to indicate a certificate error. (The Receiving Server enforces a policy which requires a valid x509 certificate containing the identity of the Sender Domain for dialback requests and the Originating Server did not provide a certificate with an identity that matches the Sender Domain.)

Any ideas?

[keglass]

ehaberman,

This community does not provide technical support and is not staffed with technical support experts.  I recommend you post this and future technical support questions to the Cisco Support Community (https://supportforums.cisco.com/index.jspa) where our Cisco technical support experts provide assistance.   Another option is to open a ticket with the Cisco Technical Assistance Center (www.cisco.com/go/support) to get expert debugging assistance. If you think this is a problem with Webex, then you can report this problem to Webex Customer Support at support.webex.com, which is available 24/7.

We do encourage you to participate in the Cisco Collaboration Community and to also join our Cisco Collaboration User Group program!  In the community, we encourage your discussion/sharing around collaboration topics and Cisco Collaboration Solutions, including business and IT requirements, industry trends, process, culture/organization issues, how collaboration can be used to transform businesses, vendor selection, adoption, training, architecture, licensing, and product features/functionality. If you are a customer or partner, you can also join the user group program to be eligible for member-only events and influence product direction.

We hope to hear from you again.

Kelli Glass

Moderator for the Cisco Collaboration Community

[bjames]

ehaberman,

Open a ticket with Webex, but asked to be escalated right away. The off-shore support guys will try to hold on to the ticket (hard) but will not give you the support you need.

The back-end guys will help you resolve this,

Bob James