The Meeting Server supports federation with Microsoft Lync. This allows calls to be made from the Meeting Server to any Lync domain and vice versa.
To allow inbound calls you must:
create the DNS SRV record _sipfederationtls._tcp.domain.com that points to the FQDN of the Meeting Server. This step is required as Call Bridge will need to have a public IP, and NAT is not supported in this scenario.
add a DNS A record that resolves the FQDN of the Meeting Server to a public IP address.
- upload a certificate and certificate bundle to the Meeting Server that complies with the following:
- the certificate must have the FQDN as the CN, or if using a certificate with a SAN list then ensure that the FQDN is also in the SAN list. Note: if the certificate contains a SAN list, then Lync will ignore the CN field and only use the SAN list.
- the certificate must be signed by a real CA.
- the certificate bundle must contain the Root CA’s certificate and all intermediate certificates in the chain in sequence, so that a chain of trust can be established.
Note: for more information on certificates refer to the Introduction in the Certificate Guidelines.
- Open the appropriate Firewall ports as stated in the Cisco Meeting Server Deployment Guide for example: TCP 5061, UDP 3478, UDP 32768-65535, TCP 32768-65535
For outbound calls from the Meeting Server:
- create an outbound dial rule, leave the Domain and SIP proxy fields blank, and set Trunk type as Lync. Also set the appropriate Local contact domain and the Local from domain fields.