Wildcard TLS certificates are not supported in SIP or Microsoft Skype for Business / Lync environments (as per RFC 5922). While this means that this single certificate will potentially contain a relatively high number of names, the administrator only has to manage a single SAN certificate across all Conferencing Node (unless multiple domain/subdomain support is required). This type of certificate is also known as a UC certificate. Therefore, the certificate created for the Conferencing Nodes will typically need to contain multiple SANs (Subject Alternative Names). This provides support for redundant Conferencing Node deployments and multiple SIP domains for SfB/Lync federation. The on-prem and public DMZ SfB/Lync integration guidelines both recommend that the same single certificate is installed on all Conferencing Nodes. Creating a certificate signing request (CSR) * Note that where this documentation refers to ' SfB/Lync', it represents both Microsoft Skype for Business and Lync unless stated otherwise. General information on managing certificates within Pexip Infinity can be found at Managing TLS and trusted CA certificates. Configuring Windows Server Manager to use a certificate template with client and server capabilities.

Configuring the SIP TLS FQDN for a Conferencing Node.

Certificates issued by intermediate CAs.

Assigning a certificate to a Conferencing Node.

Creating a certificate signing request (CSR).

Skype download for windows 2016