Certificates. See also | Polycom 3725-76302-001O instruction

Click the link to go to the Network > External SIP Peers page to begin troubleshooting. Try pinging the specified Lync server’s IP address. If it is reachable, verify that the Next hop address, Port, and Transport type settings on this page are correct.

Alert 2605

<cluster>: Cannot authenticate with <lyncserver> to resolve conference IDs.

The system can’t authenticate with the specified Lync server, preventing Lync conference ID resolution. Attempts to connect to a Lync conference through the RealPresence DMA system will fail.

Click the link to go to the Network > External SIP Peers page to begin troubleshooting. Verify that the Transport Type is set to TLS, and that the Lync account URI on the Lync Integration tab is correct. If the RealPresence DMA system configuration is correct, investigate the Lync server’s configuration.

Alert 3001

No signaling interface is enabled for cluster <cluster>. SIP or H.323 must be configured to allow calls.

The specified cluster has neither H.323 nor SIP signaling enabled and is unable to accept calls.

To use the cluster for anything other than logging into the management interface, you must enable signaling.

If you’re logged into that cluster, click the link to go to the Signaling Settings page. If not, log into that cluster and go to Admin > Local Cluster > Signaling Settings.

Alert 3101

Cluster <cluster>: The server certificate has expired.

The specified cluster’s server certificate has expired. This is the public certificate that the cluster uses to identify itself to devices configured for secure communication. The cluster can no longer communicate with any such devices, including MCUs, endpoints, the AD server, and the Exchange server.

If you’re logged into that cluster, click the link to go to the Certificates page. If not, log into that cluster (your browser will warn you not to do this, and you’ll have to override its advice) and go to Admin > Local Cluster