Microsoft Lync/Skype for Business uses the _sipfederationtls._tcp. Note: This is just an exemplary call flow scenario. This is possible through the integration and call routing using Expressway servers, as shown in the image below, which is taken from the Cisco Expressway Options with Cisco Meeting Server and/or Microsoft Infrastructure configuration guide referenced at the end of this document. ConfigureĪn example for the call flow and its configuration can be a CUCM registered endpoint which dials to a Skype client (either on-prem or off-prem, or registered in the Cloud using Office365), or vice versa - using the CMS for the conversion between Standard SIP and Microsoft protocol. The other configurations are covered in the above referenced configuration guide. The current document only focusses on the DNS and certificate requirements on the Microsoft Lync or Skype for Business end for external federation.
The configuration for this integration is as explained in the Cisco Expressway Options with Cisco Meeting Server and/or Microsoft Infrastructure documentation which is available for your version at the Cisco Expressway Series Configuration guides list. The document highlights a specific aspect of the integration with external Microsoft clients with your Cisco infrastructure using Expressway and Cisco Meeting Server (CMS). If your network is live, ensure that you understand the potential impact of any command.
All of the devices used in this document started with a cleared (default) configuration. The information in this document was created from the devices in a specific lab environment.
Cisco Meeting Server (CMS) 2.1.2 or later.
The information in this document is based on these software and hardware versions: