Manualsbrain.com
  1. Manuals
  2. Brands
  3. Polycom
  4. 7000
  5. User Manual

Polycom 7000 User Manual

Download
Page of 437
 
System Management and Maintenance
Polycom, Inc. 
357
 
Alert 2401 
Connection to the history/audit database for cluster <cluster> has failed.
The specified cluster is unable to communicate with its shared call history database. This may indicate a 
network problem, or a software failure within the cluster. The server(s) may need to be rebooted.
Go to the DMAs page to begin troubleshooting.
See also:
Alert 2402 
Connection to the configuration database for cluster <cluster> has failed.
The specified cluster is unable to communicate with its shared configuration database. This may indicate a 
network problem, or a software failure within the cluster. The server(s) may need to be rebooted.
Go to the DMAs page to begin troubleshooting.
See also:
Lync Integration
The following alerts provide information on changes in Microsoft Lync 2013 integration.
Alert 2601 
Cluster <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:
Alert 2602 
Cluster <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. Begin 
troubleshooting by verifying that the Presence Publishing settings on the Admin > Conference Manager 
> Conference Settings page are correct.
Click the link to go to the Network > External SIP Peers page. 
See also: