Filter
Top Products
Polycom, Inc. 350
See also:
Alerts on page 342
Alert 2601
<cluster>: Cannot reach Lync server <lyncserver> for presence publishing.
The cluster cannot communicate with the specified Lync server at the currently configured Next hop
address. This could indicate a network problem, or a problem with the Lync server.
Click the link to go to the Network > External SIP Peers page to begin troubleshooting. Try to ping the Lync
server’s Next hop address to verify basic connectivity.
See also:
Alerts on page 342
Alert 2602
<cluster>: Cannot authenticate with <lyncserver> for presence publishing.
The cluster cannot authenticate with the specified Lync server; presence will not be published for Polycom
conference contacts.
This could indicate incorrect RealPresence DMA system or Lync server configuration.
Click the link to go to the Network > External SIP Peers page to begin troubleshooting. Verify that the Next
hop address, Port, and Transport type settings on this page are correct.
See also:
Alerts on page 342
Alert 2603
<cluster>: Invalid Lync account URI configured for Lync server <lyncserver>.
The system is unable to authenticate with the Lync server using the currently configured Lync account URI.
Click the link to go to the Network > External SIP Peers page to begin troubleshooting. Try reentering the
Lync account URI for the Lync server in the External SIP Peer configuration area.
See also:
Alerts on page 342
Alert 2604
<cluster>: Cannot reach Lync server <lyncserver> to resolve conference IDs.
The system is unable to connect to the specified Lync server at the currently configured Next hop address.
Attempts to connect to a Lync conference through the RealPresence DMA system will fail.
This could indicate a network problem, or that someone has shut down the Lync server.