Polycom 7000 User Manual

Page of 437
 
System Management and Maintenance
Polycom, Inc. 
358
 
Alert 2603 
Cluster <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:
Alert 2604 
Cluster <cluster>: Cannot reach Lync server <lyncserver> to resolve conference IDs for 
RealConnect
TM
 conferences.
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.
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 addressPort, and Transport 
type
 settings on this page are correct.
See also:
Alert 2605
Cluster <cluster>: Cannot authenticate with <lyncserver> to resolve conference IDs for 
RealConnect
TM
 conferences.
The system can’t authenticate with the specified Lync server, preventing RealConnect
TM
 conference ID 
resolution. Attempts to connect to RealConnect
TM
 conferences 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. 
See also:
Signaling
The following alerts provide information on signaling events and changes in signaling status.
Alert 3001 
No signaling interface 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.