CMS + Office 365 federation

[johntseung]

Hi ,

We have a test with CMS 2.2 +  Expressway C + Expressway E 8.9 for the O365 federation, but we test the federation is failed.

Certificate have public SAN for Expressway E.

Route pattern should be enough, because we use another brand SIP to SIP video call is work.

The user is registered n on CMS.

Thanks.

ms-diagnostics: 1046;reason="Failed to connect to a federated peer server";ip-address="Expressway E WAN IP";peer-type="FederatedPartner";winsock-code="10060";winsock-info="The peer did not respond to the connection attempt, or established connection failed because peer failed to respond";source="sipfed0F.online.lync.com"

[Patrick Sparkman]

Have you configured your CMS and Expressway per the Cisco Expressway Options with Cisco Meeting Server and/or Microsoft Infrastructure (Expressway X8.9.2)?

Is federation enabled for O365?

[johntseung]

Have you configured your CMS and Expressway per the Cisco Expressway Options with Cisco Meeting Server and/or Microsoft Infrastructure (Expressway X8.9.2)?

Yes, the External DNS SRV _sipfederationtls._tcp. FQDN is point to expressway E . Certificate SAN have expressway E external FQDN.

The certificate is trusted, Expressway C have configure route to CMS.

External SIP call can reach the CMS end point but Skype SIP call can't., skype can't see presence status also.

Is federation enabled for O365? Yes, it is open for accept all federations.

The federation is relate on _sipfederationtls._tcp.?