Current Publication | x
Close

Alerts

On various pages and Dashboard panes, the alert icon is used to indicate an abnormal condition, problem, or just something you should be aware of. Hover over the icon to see details.

A summary of alert status appears in the menu bar, showing how many alerts exist across all clusters of a supercluster and how many are new (that is, that you have not viewed yet).

When you click the summary data, an expanded alerts list appears, displaying the date and time, alert code, and description of each alert. In many cases, the alert description is a link to the relevant page for investigating the issue. A Help button to the right of the alert description displays the help topic for that alert, which contains additional information about the causes and recommendations for dealing with the alert.

The following topics describe the alerts by category, followed by the alerts contained in the category:

Supercluster Status (1000 series)

Territory Status  (1100 series)

Asynchronous Operation (1200 series)

RealPresence Resource Manager System Integration  (2000 series)

Active Directory Integration (2100 series)

Exchange Server Integration (2200 series)

Database Status (2400 series)

Skype for Business Integration (2600 series)

Signaling (3000 series)

Certificate (3100 series)

Licenses (3200 series)

Networks (3300 series)

Server Resources (3400 series)

Data Synchronization (3600 series)

System Health and Availability (3800 series)

Cluster Features (3900 series)

MCUs (4000 series)

Endpoints (5000 series)

Conference Manager (6000 series)

Conference Status (6100 series)

Skype for Business Presence Publishing (6200 series)

Call Server (7000 series)

Call Bandwidth Management (7100 series)

Supercluster Status

The following alerts provide information on changes in cluster and supercluster status.

Alert 1001

Cluster <cluster> is busied out as of YYYY-MM-DD HH:MM GMT+/-H[:MM].

You or another administrator busied out the cluster, perhaps for maintenance.

A busied-out cluster allows existing calls and conferences to continue and accepts new calls for existing conferences, but does not accept other new calls and conferences.

Once all existing calls and conferences have ended, the cluster is out of service.

Click the link to go to the DMAs page.

Alert 1002

Cluster <cluster> is out of service as of YYYY-MM-DD HH:MM GMT+/-H[:MM].

You or another administrator took the cluster out of service (or busied out the cluster, and now all calls and conferences have ended).

An out-of-service cluster is still running and accessible via the management interface, but does not accept any calls or registrations.

Click the link to go to the DMAs page.

Alert 1003

Cluster <cluster> is orphaned.

The replication link with the specified cluster seems to be corrupted.

Click the link to go to the DMAs page. Try removing that cluster from the supercluster and then rejoining.

Alert 1004

Cluster <cluster> is not reachable. Last heartbeat received YYYY-MM-DD HH:MM GMT+/-H[:MM].

The specified cluster is not sending scheduled heartbeats. Possible reasons include:

The cluster may simply be very busy and have fallen behind in sending heartbeats.

An internal process could be stuck.

The servers may be offline or rebooting.

There may be a network problem.

Click the link to go to the DMAs page.

Territory Status

The following alerts provide information on changes in territory status.

Alert 1103

No clusters assigned to <list of territories>.

The specified territory or territories are not assigned to a cluster, so any responsibilities assigned to the territories are not being fulfilled.

Click the link to go to the Territories page. Assign a primary and backup cluster for every territory in your site topology.

Alert 1105

<alerting-cluster>: Primary cluster <p-cluster> and backup cluster <b-cluster> are not reachable. Territory <territory> may not be functioning.

The cluster from which the alert originated is unable to communicate with the specified territory’s primary and backup clusters.

This may be a temporary problem, in which case this alert will be cleared as soon as the alerting cluster is once again able to communicate with the clusters in question.

If this alert reoccurs frequently but quickly goes away, that suggests intermittent spurious network problems. If it persists for more than about 15-30 seconds, it may indicate serious network problems. It is also possible that someone shut both clusters down, or shut down one and the other then failed, or both failed (unlikely).

Click the link to go to the Territories page. To enable conferencing to continue in the territory (at diminished capacity), assign it to some other cluster.

Alert 1106

<alerting-cluster>: Cluster <cluster> is not reachable. Territory <territory> may not be functioning.

The cluster from which the alert originated is unable to communicate with the specified territory’s primary cluster, and there is no backup cluster.

This may be a temporary problem, in which case this alert will be cleared as soon as the alerting cluster is once again able to communicate with the cluster in question.

If this alert reoccurs frequently but quickly goes away, that suggests intermittent spurious network problems. If it persists for more than about 15-30 seconds, it may indicate serious network problems. It is also possible that someone shut the cluster down or that it failed.

Click the link to go to the Territories page. To enable conferencing to continue in the territory (at diminished capacity), assign it to some other cluster.

We recommend assigning a backup cluster for each territory.

Alert 1107

<alerting-cluster>: Primary cluster <p-cluster> associated with territory <territory> is not reachable. But backup cluster <b-cluster> is reachable.

The cluster from which the alert originated is unable to communicate with the specified territory’s primary cluster, but can communicate with the backup cluster.

This may be a temporary problem, in which case this alert will be cleared as soon as the alerting cluster is once again able to communicate with the cluster in question.

If this alert reoccurs frequently but quickly goes away, that suggests intermittent network problems. If it persists, it will be followed by Alert 1108 , indicating that the territory has failed over to the backup cluster. The backup cluster allows conferencing to continue in the territory (at diminished capacity) and fulfills any other responsibilities assigned to the territory.

Click the link to go to the Territories page. Determine whether the cluster was deliberately shut down. If not, try pinging the cluster’s IP addresses.

If this is a two-server cluster, and you cannot ping either the virtual or physical IP addresses, look for a network problem. It is unlikely that both servers have failed simultaneously.

If you can ping the cluster, the OS is running, but the application may be in a bad state. Try rebooting the servers.

Alert 1108

<alerting-cluster>: Territory <territory> has failed over from <p-cluster> to <b-cluster>.

The territory’s primary cluster is unreachable, and its backup cluster has taken over.

This may indicate a network problem. It is also possible that someone shut the cluster down or that it failed.

The backup cluster allows conferencing to continue in the territory (at diminished capacity) and fulfills any other responsibilities assigned to the territory.

Click the link to go to the Territories page. Determine whether the cluster was deliberately shut down. If not, try pinging the cluster’s IP addresses.

If this is a two-server cluster, and you can’t ping either the virtual or physical IP addresses, look for a network problem. It’s unlikely that both servers have failed simultaneously.

If you can ping the cluster, the OS is running, but the application may be in a bad state. Try rebooting the servers.

Asynchronous Operation

The following alerts provide information on asynchronous states between servers in a cluster or supercluster.

RealPresence Resource Manager System Integration

The following alerts provide information on RealPresence Resource Manager system integration events and changes in integration status.

Alert 2001

<formatted string from server>

An error occurred when the cluster responsible for RealPresence Resource Manager integration tried to synchronized data with the Polycom RealPresence Resource Manager system. The alert text describes the nature of the problem, which may require remedial action on the Polycom RealPresence Resource Manager system.

Alert 2002

Resource management system <system-name> unreachable. Last contact on: YYYY-MM-DD HH:MM GMT+/-H[:MM].

The cluster responsible for RealPresence Resource Manager integration was unable to connect to the Polycom RealPresence Resource Manager system.

This may indicate a network problem or a problem with the Polycom RealPresence Resource Manager system.

Try logging in to the Polycom RealPresence Resource Manager system. If you can do so, make sure the login credentials that the RealPresence DMA system uses to connect to it are still valid.

Alert 2004

Resource management server <system-name> has inconsistent territory definitions in its site topology.

The system is integrated with a Polycom RealPresence Resource Manager system, and there is a problem with the territory definitions or responsibility assignments in the site topology data imported from that system.

On the Polycom RealPresence Resource Manager system, configure territories properly (for instance, no duplicate names) and in way that meets the needs of the RealPresence DMA system. Assign responsibilities (primary and backup) for the territories to the appropriate RealPresence DMA clusters. A territory can only host conference rooms if it’s assigned to a RealPresence DMA cluster.

Active Directory Integration

The following alerts provide information on changes in Active Directory integration status.

Alert 2101

Active Directory user and group cache update was not successful on cluster <cluster>.

The cluster responsible for Active Directory integration was unable to update the cache of user and group data.

This may indicate a network problem or a problem with the AD.

If the cluster was unable to log in to the AD server, alert 2107 is also generated.

Click the link to go to the Microsoft Active Directory page and check the Active Directory Connection section.

Alert 2102

Zero enterprise conference rooms exist on cluster <cluster>.

The cluster responsible for Active Directory integration successfully retrieved user and group data, but no conference rooms were generated.

This may indicate that no directory attribute was specified from which to generate conference room IDs, or that the chosen attribute resulted in empty (null) conference room IDs after the system removed the characters to remove.

Click the link to go to the Microsoft Active Directory page and check the Enterprise Conference Room ID Generation section. If necessary, check the Active Directory and determine an appropriate directory attribute to use.

Alert 2104

Active Directory service is not available. Both primary cluster <p-cluster> and backup cluster <b-cluster> are not operational.

The primary and backup cluster for the territory responsible for Active Directory integration are both unreachable.

This may indicate serious network problems. It is also possible that someone shut both clusters down, or shut down one and the other then failed, or both failed (unlikely).

Click the link to go to the DMAs page to begin troubleshooting. Determine whether the clusters were deliberately shut down. If not, try pinging the clusters’ IP addresses.

Other clusters can continue using the shared data store from the last cache update, so there is no immediate AD-related problem. But the unavailable clusters probably have other territory-related responsibilities (conference manager and/or call server), so you may need to assign the affected territory to some other cluster(s).

Alert 2105

Active Directory service is not available. Cluster <p-cluster> is not operational.

The primary cluster for the territory responsible for Active Directory integration is unreachable, and it has no backup cluster.

This may indicate a network problem. It is also possible that someone shut the cluster down or that it failed.

Click the link to go to the DMAs page to begin troubleshooting. Determine whether the cluster was deliberately shut down. If not, try pinging the cluster’s IP addresses.

Other clusters can continue using the shared data store from the last cache update, so there is no immediate AD-related problem. But the unavailable cluster probably has other territory-related responsibilities (conference manager and/or call server), so you may need to assign the affected territory to some other cluster.

Polycom recommends assigning a backup cluster for each territory.

Alert 2106

Cluster <cluster>: Failed connection from <server> to Active Directory for user authentications at YYYY-MM-DD HH:MM GMT+/-H[:MM].

The specified server tried to connect to the Active Directory in order to authenticate a user’s credentials and was unable to do so. This may indicate a network problem or a problem with the AD itself.

If the network and the AD itself both appear to be OK, the connection attempt may have failed because the cluster was unable to log in to the AD server.

Click the link to go to the Microsoft Active Directory page. Make sure the login credentials that the RealPresence DMA system uses to connect to Active Directory are still valid and update them if necessary.

Alert 2107

Failed connection from <cluster> to Active Directory for user caching at YYYY-MM-DD HH:MM GMT+/-H[:MM].

The cluster responsible for Active Directory integration was unable to log into the AD server.

Click the link to go to the Microsoft Active Directory page.

Alert 2108

<alerting-cluster>: Active Directory primary cluster <p-cluster> associated with territory <territory> is not reachable. But backup cluster <c-cluster> is reachable.

The territory’s primary cluster assigned to do Active Directory integration is not reachable. The territory’s backup cluster assigned to do Active Directory integration is reachable.

This may indicate a network problem. It’s also possible that someone shut the primary cluster down or that it failed.

Click the link to go to the Integrations > DMA page. Log in to the affected cluster, if possible, and check the health of the cluster. Determine whether the cluster was deliberately shut down. If not, try pinging the cluster’s IP addresses.

Exchange Server Integration

The following alerts provide information on changes in Exchange server integration status.

Alert 2201

Exchange server integration primary cluster <p-cluster> is not operational. Integration by backup cluster <b-cluster>.

The primary cluster for the territory responsible for Exchange server integration is unreachable, and its backup cluster has taken over responsibility for monitoring the Polycom Conferencing user mailbox and accepting or declining the meeting invitations received.

This may indicate a network problem. It’s also possible that someone shut the cluster down or that it failed.

Click the link to go to the DMAs page to begin troubleshooting.

Alert 2202

Exchange server integration is not available. Both primary cluster <p-cluster> and backup cluster <b-cluster> are not operational.

The primary and backup clusters for the territory responsible for Exchange server integration are both unreachable.

This may indicate serious network problems. It is also possible that someone shut both clusters down, or shut down one and the other then failed, or both failed (unlikely).

Click the link to go to the DMAs page to begin troubleshooting. Determine whether the clusters were deliberately shut down. If not, try pinging the clusters’ IP addresses.

Alert 2203

Exchange server integration is not available. Cluster <p-cluster> is not operational.

The primary cluster for the territory responsible for Exchange server integration is unreachable, and it has no backup cluster.

This may indicate a network problem. It’s also possible that someone shut the cluster down or that it failed.

Click the link to go to the DMAs page to begin troubleshooting.

Database Status

The following alerts provide information on database events and changes in database status.

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.

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.

Skype for Business Integration

The following alerts provide information on changes in Microsoft Skype for Business integration.

Alert 2601

Cluster <cluster>: Cannot reach Lync server <lyncserver> for presence publishing.

The cluster cannot communicate with the specified Skype for Business server at the currently configured Next hop address. This could indicate a network problem, or a problem with the Skype for Business server.

Click the link to go to the Integrations > External SIP Peers page to begin troubleshooting. Try to ping the Skype for Business server’s Next hop address to verify basic connectivity.

Alert 2602

Cluster <cluster>: Cannot authenticate with <lyncserver> for presence publishing.

The cluster cannot authenticate with the specified Skype for Business server; presence will not be published for Polycom conference contacts.

This could indicate incorrect RealPresence DMA system or Skype for Business server configuration. Begin troubleshooting by verifying that the Presence Publishing settings on the Service Config > Conference Manager Settings > Conference Settings page are correct.

Click the link to go to the Integrations > External SIP Peers page.

Alert 2603

Cluster <cluster>: Invalid Lync account URI configured for Lync server <lyncserver>.

The system is unable to authenticate with the Skype for Business server using the currently configured Skype for Business account URI.

Click the link to go to the Integrations > External SIP Peers page to begin troubleshooting. Try reentering the Skype account URI for the Skype for Business server on the Skype Integration tab.

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 Skype for Business server at the currently configured Next hop address. Attempts to connect to a Skype for Business conference through the RealPresence DMA system will fail.

This could indicate a network problem, or that someone has shut down the Skype for Business server.

Click the link to go to the Integrations > External SIP Peers page to begin troubleshooting. Try pinging the specified Skype for Business 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 <cluster>: Cannot authenticate with <lyncserver> to resolve conference IDs for RealConnect TM conferences.

The system cannot authenticate with the specified Skype for Business 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 Integrations > External SIP Peers page to begin troubleshooting. Verify that the Transport Type is set to TLS, and that the Skype account URI on the Skype Integration tab is correct. If the RealPresence DMA system configuration is correct, investigate the Skype for Business server’s configuration.

Signaling

The following alerts provide information on signaling events and changes in signaling status.

Alert 3001

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

The specified cluster does not have 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 are logged in to that cluster, click the link to go to the Signaling Settings page. If not, log into that cluster and go to Admin > Server > Signaling Settings.

Certificate

The following alerts provide information on changes in certificate status such as certificate expirations and incompatibilities.

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 are logged in to that cluster, click the link to go to the Certificates page. If not, log in to that cluster (your browser will warn you not to do this, and you will have to override its advice) and go to Admin > Server > Certificates.

Alert 3102

Cluster <cluster>: The server certificate will expire within 1 day. All system access may be lost.

The specified cluster’s server certificate is about to expire. This is the public certificate that the cluster uses to identify itself to devices configured for secure communication. If you allow it to expire, the cluster will no longer be able to communicate with any such devices, including MCUs, endpoints, the AD server, and the Exchange server.

If you are logged in to that cluster, click the link to go to the Certificates page. If not, log in to that cluster and go to Admin > Server > Certificates.

Alert 3103

Cluster <cluster>: The server certificate will expire within <count> days. All system access may be lost.

The specified cluster’s server certificate will soon expire. This is the public certificate that the cluster uses to identify itself to devices configured for secure communication. If you allow it to expire, the cluster will no longer be able to communicate with any such devices, including MCUs, endpoints, the AD server, and the Exchange server.

If you are logged in to that cluster, click the link to go to the Certificates page. If not, log in to that cluster and go to Admin > Server > Certificates.

Alert 3104

Cluster <cluster>: One or more CA certificates have expired.

The specified cluster has an expired CA certificate or certificates. When a CA certificate expires, the certificates signed by that certificate authority are no longer accepted. Depending on its security settings, the cluster may refuse connections from devices presenting a certificate signed by a CA whose certificate has expired, including MCUs, endpoints, the AD server, and the Exchange server.

If you are logged in to that cluster, click the link to go to the Certificates page. If not, log in to that cluster and go to Admin > Server > Certificates.

If that cluster has Skip validation of certificates for inbound connections turned off, you will not be able to log into it. Contact Polycom Global Services.

Alert 3105

Cluster <cluster>: One or more CA certificates will expire within 30 days.

The specified cluster has a CA certificate or certificates that will expire soon. When a CA certificate expires, the certificates signed by that certificate authority are no longer accepted. If you allow the CA certificate(s) to expire, depending on its security settings, the cluster may refuse connections from any devices presenting a certificate signed by a CA whose certificate has expired, including MCUs, endpoints, the AD server, and the Exchange server.

If you are logged in to that cluster, click the link to go to the Certificates page. If not, log in to that cluster and go to Admin > Server > Certificates.

Alert 3108 

Cluster <cluster>: The server SSL certificate is incompatible with the cluster's network settings.

The specified server’s SSL certificate does not match the cluster’s domain information or other network configuration. Perhaps the network configuration was changed, and the SSL certificate is now out of date.

If you are logged in to that cluster, click the link to go to the Certificates page. If not, log in to that cluster and go to Admin > Server > Certificates. Try regenerating the SSL certificate in question.

Licenses

The following alerts provide information on changes in licensing status.

Alert 3201

Cluster <DMA URL> has no license. Either apply license key(s) or configure Clariti licenses through the Polycom Licensing Center. System will allow up to 10 concurrent calls.

You have not entered the license key(s) for the specified cluster.

If you are logged in to that cluster, click the link to go to the Licenses page. If not, log in to that cluster and go to Admin > Server > Licenses.

Without a valid license, the cluster is limited to ten simultaneous calls.

Alert 3202

Invalid license key(s) applied to cluster <cluster>. System will allow up to 10 concurrent calls.

The specified cluster has an invalid license key or keys.

If you are logged in to that cluster, click the link to go to the Licenses page. If not, log in to that cluster and go to Admin > Server > Licenses.

Without a valid license, the cluster is limited to ten simultaneous calls.

Alert 3203

The EULA for cluster <cluster> has not been accepted. All calls are blocked on this cluster.

The system version has changed, and the End User License Agreement has not yet been accepted. The specified cluster will not accept any inbound calls or place outbound calls, until a user with Administrator privileges accepts the agreement upon login.

Click the link to go to the Licenses page, where you can view the EULA acceptance status and details.

Alert 3204

Cluster <cluster>: Cannot connect to licensing server <lserver>.

The specified cluster cannot connect to the licensing server, or there is no licensing server configured for this cluster.

If you are logged in to that cluster, click the link to go to the Licenses page to view licensing details. Check the status of licensing by logging in to the RealPresence Platform Director system

Alert 3205

Cluster <cluster>: DMA VE Soft RPP version is incompatible with license. No calls are permitted.

The specified cluster’s version of software is not compatible with the installed license. The system will not permit calls until a license that has been activated for this version of software is installed.

Click the link to go to the Licenses page to install the proper license activation key.

Alert 3206

Cluster <cluster>: DMA is not licensed for any calls.

The current license for the specified cluster does not include the ability to make calls.

Click the link to go to the Licenses page to view licensing details or install a different license activation key.

Networks

The following alerts providek information on network errors and connectivity.

Alert 3301

Cluster <cluster> is configured for 2 servers, but only a single server is detected.

One of the servers in the specified cluster is not responding to the other server over the private network that connects them.

This could be a hardware problem, or the server in question may just need to be rebooted. It is also possible that the private network connection between the two servers has failed. Check the Ethernet cable connecting the GB 2 ports (Polycom Rack Server 630 or 620-based systems) or the Port 1 ports (Polycom Rack Server 220-based systems) and replace it if necessary.

Alert 3302

Cluster <cluster> is configured for 1 server, but the private network interface is enabled and active.

Either the cluster contains two servers but was incorrectly configured as a single-server cluster, or there is only one server in the cluster but something is connected its GB 2 port (Polycom Rack Server 630 or 620-based systems) or Port 1 port (Polycom Rack Server 220-based systems).

On a single-server cluster, do not use the server’s GB 2 port (Polycom Rack Server 630 or 620-based systems) or Port 1 port (Polycom Rack Server 220-based systems) for anything.

Alert 3303

Cluster <cluster>: A private network error exists on <server>.

The specified server has detected a problem with the private network that connects the two servers in the cluster.

For systems installed on a Polycom Rack Server 630 (R630) or 620 (R620), this could be a problem with the GB 2 Ethernet port (eth1 interface). For systems installed on a Polycom Rack Server 220 (R220), this could be a problem with the Port 1 Ethernet port (eth1 interface).

This could also be a problem with the Ethernet cable connecting the eth1 interfaces of the two systems. Or, the server in question may just need to be rebooted.

Alert 3304

Cluster <cluster>: A public network error exists on <server>.

The specified server has detected a problem with the management (or combined management and signaling) network connection.

For systems installed on a Polycom Rack Server 630 (R630) or 620 (R620), this could be a problem with the GB 1 Ethernet port (eth0 interface). For systems installed on a Polycom Rack Server 220 (R220), this could be a problem with the Port 0 Ethernet port (eth0 interface).

This could also be a problem with the Ethernet cable connecting the server to the enterprise network switch, or that switch.

Or, the server in question may just need to be rebooted.

Alert 3305

Cluster <cluster>: A signaling network error exists on <server>.

The specified server has detected a problem with the signaling network connection.

For systems installed on a Polycom Rack Server 630 (R630) or 620 (R620), this could be a problem with the GB 3 port (eth2 interface). For systems installed on a Polycom Rack Server 220 (R220), this could be a problem with the GB 1 port (eth2 interface).

This could also be a problem with the Ethernet cable connecting the server to the enterprise network switch, or that switch. Or, the server in question may just need to be rebooted.

Alert 3306

DNS <address of DNS server> settings are inconsistent with network configuration on Cluster <cluster>: <issue-text>.

The system has found issues with the DNS configuration on the Admin > Server > Network Settings page for the specified cluster. This could indicate one of the following possible problems:

The virtual or management host name A or AAAA record configured in the specified DNS server is missing

The virtual or management host name A or AAAA record configured in the specified DNS server references the incorrect address

The alert text describes the nature of the problem, which may require additional configuration of the DNS server(s) or network settings for the cluster.

Refer to the Polycom RealPresence DMA System Operations Guide for more information regarding DNS configuration.

Click the link to go to the Admin > Server > Network Settings page.

Alert 3309

Cluster <cluster>: DNS <address of DNS server> is unresponsive. <service> at <FQDN> <referenced by> {will use <IP address> | cannot be reached}.

One or more configured DNS servers are not responding to requests from the specified cluster. The system will use the last cached IP address for the DNS server, but if no IP address is known, this DNS server is considered unreachable.

This could indicate a network problem, or that a DNS server is out of service.

Click the link to go to the Admin > Server > Network Settings page.

Alert 3310

Cluster <cluster>: DNS <address of server> cannot resolve <FQDN>. <service> <referenced by> cannot be reached.

The specified cluster cannot resolve the domain name of this Active Directory, MCU, ISDN gateway, or DMA cluster. The specified service is currently unreachable.

This could indicate a network problem, or that the specified domain name entry is incorrect in the DMA cluster’s configuration.

If the alert originated from a different cluster, log in to that cluster and go to the Admin > Server > Network Settings page to begin troubleshooting. If you are already logged in to the originating cluster, click the link to go to the Admin > Server > Network Settings page.

Server Resources

The following alerts provide information on changes in the resources of the server or cluster.

Alert 3401

Cluster <cluster>: Available disk space is less than 15% on server <server>.

The specified cluster is running out of disk space.

Suggestions for recovering and conserving disk space include:

Delete backup files (after downloading them).

Remove upgrade packages.

History data is written to the backup file nightly. Reduce history retention settings so the same history data is not being repeatedly backed up.

Roll logs more often (compressing the data) and make sure Logging level is set to Production.

Alert 3403

Cluster <cluster>: Log files on server <server> exceed the capacity limit and will be purged within 24 hours.

Log archives on the specified cluster exceed the capacity limit for logs. After midnight, the system will delete sufficient log archives to get below the limit.

Click the link to go to the System Log Files page. We recommend routinely downloading archived logs and then deleting them from the system.

Alert 3404

Cluster <cluster>: Log files on server <server> are close to capacity and may be purged within 24 hours.

Log archives on the specified cluster have reached the percentage of capacity that triggers an alert, set on the Alerting Settings page.

Click the link to go to the System Log Files page. We recommend routinely downloading archived logs and then deleting them from the system.

Alert 3405

Server <server> CPU utilization >50% and <75%.

The specified server’s CPU and/or I/O bandwidth usage is unusually high.

This can be caused by activities such as backup creation, CDR downloading, logging at too high a level, or refreshing an extremely large Active Directory cache.

The cause may also be a system health problem or a runaway process. Go to Admin > Troubleshooting Utilities > Top to see if a process is monopolizing CPU resources.

Create a new backup and download it, and then contact Polycom Global Services.

Alert 3406

Server <server> CPU utilization > 75%.

The specified server’s CPU and/or I/O bandwidth usage is exceptionally high.

This can be caused by activities such as backup creation, CDR downloading, logging at too high a level, or refreshing an extremely large Active Directory cache.

The cause may also be a system health problem or a runaway process. Go to Admin > Troubleshooting Utilities > Top to see if a process is monopolizing CPU resources.

Create a new backup and download it, and then contact Polycom Global Services.

Data Synchronization

The following alerts provide information on changes in data synchronization between servers in the cluster.

Alert 3601

Cluster <cluster>: System version differs between servers.

The specified cluster is supposed to have two servers, but a software version mismatch makes it impossible for them to form a redundant two-server cluster.

Possible explanations:

Someone upgraded one server of the cluster while the other was turned off or otherwise unavailable.

An expansion server was added to a single-server cluster, but the new server was not patched to the same software level as the existing server.

An RMA replacement server was not patched to the same software level as the existing server.

If you are logged in to that cluster, click the link to go to the Software Upgrade page. If not, log in to that cluster and go to Admin > Software Upgrade. Check Operation History.

Log into the physical address of the server that was unable to join the cluster and upgrade it to match the other server. After it restarts, it will join the cluster.

Alert 3602

Cluster <cluster>: Local time differs by more than ten seconds between servers.

The time on the two servers in the specified cluster has drifted apart by an unusually large amount. This may indicate a configuration issue or a problem with one of the servers. Contact Polycom Global Services.

Alert 3603

Cluster <cluster>: Active Directory integration is not consistent between servers.

In the specified cluster, the Active Directory integration status information is different on the two servers, indicating that their internal databases are not consistent.

Try to determine which server’s data is incorrect and reboot it.

Alert 3604

Cluster <cluster>: Enterprise conference rooms differ between servers.

In the specified cluster, the enterprise conference room counts are different on the two servers, indicating that their internal databases are not consistent.

Try to determine which server’s data is incorrect and reboot it.

Alert 3605

Cluster <cluster>: Custom conference rooms differ between servers.

In the specified cluster, the custom conference room counts are different on the two servers, indicating that their internal databases are not consistent.

Try to determine which server’s data is incorrect and reboot it.

Alert 3606

Cluster <cluster>: Local users differ between servers.

In the specified cluster, the local users are different on the two servers, indicating that their internal databases are not consistent.

Try to determine which server’s data is incorrect and reboot it.

System Health and Availability

The following alerts provide information on changes in the health and availability of the system.

Alert 3801

<d-cluster>: Cluster <f-cluster>/server <f-server> failover to <b-server> due to <component> failure: <details of failure>

The cluster from which the alert originated is reporting that a server in a different cluster has failed over to an alternate server because of an internal software component failure. The alert includes details on what component experienced the failure.

This alert is cleared when the condition that caused the alert is resolved.

Use the failure details as a starting point for troubleshooting. If the failure is not hardware or network related, and you are unable to access the server, it may need to be rebooted.

Click the link to go to the Integrations > DMA page.

Alert 3802

<d-cluster>: Cluster <f-cluster>/server <f-server> restarted due to <component> failure: <details of failure>

The cluster from which the alert originated is reporting that a server in a different cluster has restarted because of an internal component failure. The alert includes details on what component experienced the failure.

Use the failure details as a starting point for troubleshooting. If the failure is not hardware or network related, and you are unable to access the server, it may need to be physically powered off and powered back on.

Click the link to go to the Integrations > DMA page.

Alert 3803

<d-cluster>: Cluster <f-cluster>/server <f-server> is operating in an impaired state due to <component> issue: <details of impairment>

The cluster from which the alert originated is reporting that a server in a different cluster has experienced one or more software component issues, and is running in an unhealthy state. The alert includes further details of the impairment of the system.

Use the impairment details as a starting point for troubleshooting. If the impairment is not hardware or network related, and you are unable to access the server, it may need to be rebooted.

Click the link to go to the Integrations > DMA page.

Cluster Features

The following alerts provide information on the status of certain cluster operations.

Alert 3901

<cluster>: Scheduled backup at <date-time> failed because the remote server address could not be resolved.

The specified cluster could not resolve the hostname or IP address of the remote backup server, causing the backup scheduled at <date-time> to fail.

This alert is cleared the next time a scheduled backup is successful, regardless of any configuration changes.

Click the link to go to the Admin > Server > Backup Settings page. Ensure the hostname or IP address for the remote backup server is correct, and that the server is reachable from the RealPresence DMA system.

Alert 3902

<cluster>: Scheduled backup at <date-time> failed because there was no response from the remote server.

The specified cluster did not receive a response from the configured remote backup server, causing the backup scheduled at <date-time> to fail.

This alert is cleared the next time a scheduled backup is successful, regardless of any configuration changes.

Click the link to go to the Admin > Server > Backup Settings page.

Alert 3903

<cluster>: Scheduled backup at <date-time> failed because the configured login/password for the remote server are invalid.

The specified cluster was unable to authenticate with the configured remote backup server using the configured login and password, causing the backup scheduled at <date-time> to fail.

This alert is cleared the next time a scheduled backup is successful, regardless of any configuration changes.

Click the link to go to the Admin > Server > Backup Settings page. Ensure the credentials for the remote backup server are correct.

Alert 3904

<cluster>: Scheduled backup at <date-time> failed because there was a data transfer error with the remote server.

A communications error with the backup server caused the backup scheduled at <date-time> to fail.

This alert is cleared the next time a scheduled backup is successful, regardless of any configuration changes.

Click the link to go to the Admin > Server > Backup Settings page. Ensure the network link between the RealPresence DMA system and the remote backup server is reliable.

Alert 3905

<cluster>: Scheduled backup at <date-time> failed because the backup file could not be created.

The RealPresence DMA system was unable to create the backup file on the remote backup server, causing the backup scheduled at <date-time> to fail.

This alert is cleared the next time a scheduled backup is successful, regardless of any configuration changes.

Click the link to go to the Admin > Server > Backup Settings page. Check the remote backup server’s file system permissions to ensure the RealPresence DMA system can create and write to files there.

MCUs

The following alerts provide information on changes in the status of connected MCUs.

Alert 4001

MCU <MCUname> is currently busied out.

Someone busied out the specified MCU.

Click the link to go to the Integrations > MCU page.

Alert 4002

MCU <MCUname> is currently out of service.

Someone took the specified MCU out of service.

Click the link to go to the Integrations > MCU page.

Alert 4003

MCU <MCUname> has <count> warning(s).

The MCUs page is displaying warnings related to the specified MCU.

Click the link to go to the Integrations > MCU page for more information.

Alert 4004

MCU <MCUname> is configured with insufficient user connections.

The system was unable to establish an additional management session connection to the specified MCU.

Possible explanations:

IP connectivity between the system and the MCU has been lost.

This MCU does not allow sufficient connections per user.

Polycom MCUs use synchronous communications. In order to efficiently manage multiple calls as quickly as possible, the Polycom RealPresence DMA system uses multiple connections per MCU. By default, a RealPresence Collaboration Server or RMX MCU allows up to 20 connections per user (the MAX_NUMBER_OF_MANAGEMENT_SESSIONS_PER_USER system flag). We recommend not reducing this setting. If you have a RealPresence DMA supercluster with three conference manager clusters and a busy conferencing environment, we recommend increasing this value to 30.

After a connection attempt fails and this alert is triggered, the system tries every 60 seconds to establish 5 connections to this MCU. If it succeeds, this alert is automatically cleared.

Click the link to go to the Integrations > MCU page.

Alert 4005

MCU <MCUname> is disconnected.

The reporting cluster is unable to connect to the specified MCU.

This may indicate a network problem. It is also possible that someone shut the MCU down or that it failed.

Click the link to go to the Integrations > MCU page for more information.

Alert 4009

MCU <mcu> disconnect rate is > 1 and < 4.

The RealPresence DMA cluster has lost connection with the specified MCU between one and four times in the past 24 hours.

This most likely indicates a network problem, but it could also indicate that the MCU or RealPresence DMA system is under very heavy load. If the MCU stays connected for more than 24 hours, this alert is cleared, but if the RealPresence DMA system loses connection with this MCU more than 4 times in 24 hours, this alert is replaced with Alert 4010.

Click the link to go to the Integrations > MCU page to begin troubleshooting. Check the network connection between this MCU and the RealPresence DMA cluster.

Alert 4010

MCU <mcu> disconnect rate is > 4.

The DMA cluster has lost connection with the specified MCU more than four times in the past 24 hours.

This most likely indicates a network problem, but it could also indicate that the MCU or RealPresence DMA system is under very heavy load.

Click the link to go to the Integrations > MCU page to begin troubleshooting. Check the network connection between this MCU and the RealPresence DMA cluster.

Alert 4011

MCU <mcu> call failure penalty is > 0.4 and < 0.8.

The specified MCU’s number of consecutive failed calls has changed, and the calculated failure penalty metric is now between 0.4 (some calls are failing) and 0.8 (most calls are failing).

The RealPresence DMA system keeps track of per-MCU call failure penalties not only to alert administrators to call failures, but also to ensure that calls will be routed less often to MCUs with high call failure penalties.

Click the link to go to the Integrations > MCU page to begin troubleshooting.

MCU Availability and Reliability Tracking

Alert 4012

MCU <mcu> call failure penalty is > 0.8.

The specified MCU’s number of consecutive failed calls has changed, and the calculated failure penalty metric is now above 0.8.

This indicates that most of the specified MCU’s calls are failing. The RealPresence DMA system keeps track of per-MCU call failure penalties not only to alert administrators to call failures, but also to ensure that calls will be routed less often to MCUs with high call failure penalties.

Click the link to go to the Integrations > MCU page to begin troubleshooting.

MCU Availability and Reliability Tracking

Alert 4013

MCU <mcu> is connected with no port capacity.

The specified MCU has no ports available for call traffic.

This could indicate that the specified MCU is at capacity, or possibly a network problem. This alert appears as soon as the port capacity of this MCU becomes 0, and is automatically cleared after two minutes.

Click the link to go to the Integrations > MCU page to begin troubleshooting.

Alert 4014

MCU <mcu> video port capacity changed from <oldcapacity> to <newcapacity>.

The video port capacity of the specified MCU has changed.

This could indicate a license change, video / voice port configuration change, or hardware change for the MCU (perhaps a media card has been removed or added). This alert appears as soon as the video port capacity of this MCU becomes 0, and is automatically cleared after two minutes.

Click the link to go to the Integrations > MCU page.

Alert 4015

MCU <mcu> voice port capacity changed from <oldcapacity> to <newcapacity>.

The voice port capacity of the specified MCU has changed.

This could indicate a license change, video / voice port configuration change, or hardware change for the MCU (perhaps a media card has been added or removed). This alert appears as soon as the voice port capacity of this MCU becomes 0, and is automatically cleared after two minutes.

Click the link to go to the Integrations > MCU page.

Alert 4016

MCU <mcu> has been automatically busied out due to <N> consecutive failures to start conferences. Investigate the MCU state and logs.

The specified MCU has been automatically busied out because it failed to start <N> number of conferences in a row. This condition is likely caused by an MCU software issue. Non-consecutive failures to start calls do not trigger this condition.

Once the MCU is busied out, when the last conference ends on the MCU, the MCU automatically changes to the Out of Service state. Once that happens, this alert is replaced with Alert 4017 .

Click the link to go to the Integrations > MCU page.

Alert 4017

MCU <mcu> has been automatically placed out of service due to <N> consecutive failures to start conferences. Investigate the MCU state and logs.

The specified MCU has been placed in the Out of Service state after it was automatically busied out because it failed to start <N> number of conferences in a row. This condition is likely caused by an MCU software issue.

This alert replaces Alert 4016 .

Click the link to go to the Integrations > MCU page.

Alert 4018

MCU <mcu> MCCF connection limit exceeded. Some conference features will not work.

The MCCF (Media Control Channel Framework) connection limit for the specified MCU has been exceeded, because there are too many RealPresence DMA systems connecting to this MCU.

Additional RealPresence DMA systems will connect to this MCU without MCCF, but some IVR, VEQ, passcode, and CDR features will not work correctly.

To correct this problem, reduce the number of RealPresence DMA systems simultaneously connecting to this MCU.

Click the link to go to the Network < MCU > MCUs page.

Endpoints

The following alerts provide information on communication issues with endpoints.

Alert 5001

<Model> ITP system attempting to register with ID <H.323 ID or SIP URI> is improperly configured.

A device that identifies itself as an ITP (Immersive Telepresence) system has registered with the call server, but the H.323 ID or SIP URI of the device doesn't specify its endpoint number or the number of endpoints in the ITP system, as it should.

The H.323 ID or SIP URI must be updated on the endpoints of the ITP system.

Naming ITP Systems for Recognition by the Polycom RealPresence DMA System

Alert 5002

One or more endpoints are sending too much <signaling_type> signaling traffic. They have been temporarily blacklisted and may have been quarantined.

At least one device, in violation of protocol standards, is sending too much of the specified type of signaling traffic (H.323 or SIP) to the RealPresence DMA system.

If there are many such ill-behaved devices, it could affect the RealPresence DMA system’s ability to provide service, so the system temporarily blacklists any such device (ignoring all signaling from it until it stops sending messages more frequently than the specification permits). Depending on the registration policy, it could also be quarantined, and it remains so until manually removed from quarantine.

Click the link to go to the Network > Endpoints page, where you can search for endpoints with Registration status of Quarantined or Quarantined (Inactive).

Alert 5003

The <device model> device identified by [<device identifier>] is no longer registered to the call server.

The specified device has unregistered or its registration has expired. This alert appears only if it has been enabled for this endpoint or MCU. This alert is automatically cleared after two minutes.

Click the link to go to the Endpoints page.

Alert 5004

<sigtype> call from <originator> to <dial string> was dropped due to routing loop.

As the system tried to route the H.323 or SIP call from its source to the destination, a dialing loop in the site topology was detected, and the call was dropped.

Click the link to go to the Reports > Call History page and view more information about the call. See Suggestions for Modifying the Default Dial Plan for common ways to avoid dialing loops.

Conference Manager

The following alerts provide information on possible problems with conference manager functionality.

Alert 6001

No territories configured to host conference rooms.

You must enable a territory to host conference rooms in order to use the cluster responsible for the territory as a conference manager. You can enable up to three territories to host conference rooms.

Click the link to go to the Service Config > Site Topology > Territories page.

Alert 6002

Shared number dialing VEQ <VEQnum> references entry queue <EQname> which is not configured on any MCUs.

The specified entry queue used by the VEQ <VEQnum> is not configured on an MCU. If the VEQ is a Direct Dial VEQ, <VEQnum> is “Direct Dial”.

Click the link to go to Service Config > Conference Manager Settings > Shared Number Dialing to begin troubleshooting. Ensure that at least one MCU configured in Integrations > MCU has the specified entry queue configured.

Shared Number Dialing

Conference Status

The following alerts provide information on some types of call failures.

Alert 6101

Call failed: Preset dialout from conference VMR <VMR> to <destination> failed. Cause: <cause>

A preset dialout from the conference using the conference room identifier <VMR> has failed for the specified reason. This alert automatically clears after two minutes.

Click the link to go to the Network > Users page to find the specified VMR number and begin troubleshooting.

Alert 6102

Conference <VMR> on MCU <MCU> failed to start: <reason>.

A conference using the conference room identifier <VMR> has failed to start for the specified reason. If no MCU was selected, <MCU> is “unresolved”. This alert automatically clears after two minutes.

Click the link to go to the Network > Users page to find the specified VMR number and begin troubleshooting.

Alert 6103

Ongoing conference <VMR> on MCU <MCU> failed: <reason>.

A conference using the conference room identifier <VMR> has been aborted for the specified reason. This alert automatically clears after two minutes.

Click the link to go to the Network > Users page to find the specified VMR number and begin troubleshooting.

Alert 6104

Ongoing conference <VMR> on MCU <MCU1> failed over to MCU <MCU2>: <reason>.

A conference using the conference room identifier <VMR> has been moved from <MCU1> to <MCU2> for the specified reason. This alert automatically clears after two minutes.

Click the link to go to the Network > Users page to find the specified VMR number and begin troubleshooting.

Alert 6105

Integrations > Microsoft Active Directory > Lync RealConnect TM  Callback contacts OU value, ‘<OU>’, does not exist in Active Directory.

The system is unable to find the specified OU in Active Directory, and will be unable to start RealConnect TM  conferences using external Lync systems.

When you integrate with an external Lync system, the RealPresence DMA system uses an Active Directory contact from the OU specified in this field to receive calls forwarded from the external Lync system.

Click the link to go to the Integrations > Microsoft Active Directory page. Verify that the value for the Callback contacts OU field is correct and contains valid contacts that the system can use for this purpose.

Alert 6106

RealConnect TM  conference with external Lync system cannot start. There are no available callback contacts.

The system is unable to find any callback contacts to use in the OU specified on the Integrations > Microsoft Active Directory page. RealConnect TM  conferences with external Skype for Business systems will not start.

When you integrate with an external Skype for Business system, the RealPresence DMA system uses an Active Directory contact from the OU specified on this page to receive calls forwarded from the external Skype for Business system.

Click the link to go to the Integrations > Microsoft Active Directory page. Verify that the value for the Callback contacts OU field is correct and contains valid contacts that the system can use for this purpose.

Alert 6107

Conference factory - all generated dynamic conference IDs are in use.

The system is unable to create a conference because the maximum number of dynamic conference IDs have been generated.

Alert 6108

Conference factory - too many conference factory requests received.

The system is unable to create a conference because protection against Denial of Service (DOS) attacks has been activated.

Skype for Business Presence Publishing

The following alerts provide information on problems the system may encounter when publishing presence for Polycom conference contacts.

Alert 6201

Cluster <cluster>: Errors in presence publication for Lync server <lyncserver>. Presence for <NN> of <MM> Polycom conference contacts will not be published due to Lync server configuration ‘MaxEndpointExpiration’ value <expire>.

The system was unable to publish presence status for the specified number of Polycom conference contacts because the Skype for Business server has been configured with a maximum endpoint logon period of <expire> seconds.

To publish presence status for Polycom conference contacts, the RealPresence DMA system registers each contact with the Skype for Business server every ‘MaxEndpointExpiration’ seconds. Depending on how many conference contacts are configured for presence publishing, the RealPresence DMA system may be unable to publish presence for all contacts during this interval, as the system registers one conference contact per second.

If suitable for your environment, either increase the ‘MaxEndpointExpiration’ value on the Skype for Business server, or decrease the number of Polycom conference contacts configured for publishing.

Click the link to go to the Integrations > External SIP Peers page.

Alert 6202

Cluster <cluster>: Errors in presence publication for Lync server <lyncserver>. Presence for <NN> of <MM> Polycom conference contacts will not be published because the number of Polycom conference contacts configured for publishing exceeds ‘Maximum Polycom conference contacts to publish’ configured on the system.

The system was unable to publish presence status for the specified number of Polycom conference contacts because the Maximum Polycom conference contacts to publish value configured in the Skype for Business server’s External SIP Peer properties has been reached.

Click the link to go to the Integrations > External SIP Peers page to begin troubleshooting. If suitable for your environment, increase the Maximum Polycom conference contacts to publish value.

Alert 6203

Cluster <cluster>: Errors in presence publication for Lync server <lyncserver>. Presence for <NN> of <MM> Polycom conference contacts will not be published: the system is unable to complete publication within the expiration interval.

The system was unable to publish presence status for the specified number of Polycom conference contacts within the number of seconds specified by the ‘MaxEndpointExpiration’ setting on the Skype for Business server.

To publish presence status for Polycom conference contacts, the RealPresence DMA system registers each contact with the Skype for Business server every ‘MaxEndpointExpiration’ seconds. This alert could indicate heavy RealPresence DMA system load or other performance-related factors during presence publishing.

If suitable for your environment, either increase the ‘MaxEndpointExpiration’ value on the Skype for Business server, or decrease the number of Polycom conference contacts configured for publishing.

Click the link to go to the Integrations > External SIP Peers page.

Alert 6205

Cluster <cluster>: Failed to create/manage conference contacts in Active Directory; DMA time is skewed from Active Directory’s time.

The specified cluster has attempted to create or manage Active Directory conference contacts, and failed because the system time differs between the RealPresence DMA system and the Active Directory system.

If possible, ensure that the RealPresence DMA system and your Active Directory system both use the same NTP server.

Click the link to go to the Integrations > Microsoft Active Directory page.

Alert 6206 

Cluster <cluster>: Failed to create/manage conference contacts in Active Directory; DNS cannot resolve the “<setting>”, <FQDN>, configured at <page>.

The specified cluster has attempted to create or manage Active Directory conference contacts, and failed. The cluster either cannot resolve the IP address or host name configured on the Integrations > Microsoft Active Directory page, or the Next hop address configured for the specified SIP peer on the Integrations > External SIP Peers page.

Go to the page specified in the alert, and verify that the configuration is correct. If so, verify your network’s DNS configuration.

Click the link to go to the page specified in the alert.

Alert 6207 

Cluster <cluster>: Failed to create/manage conference contacts in Active Directory; invalid domain, user name, or password.

The specified cluster has attempted to create or manage Active Directory conference contacts, and failed because the domain, user name, or password is incorrect on the Integrations > Microsoft Active Directory page.

Click the link to go to the Integrations > Microsoft Active Directory page, and verify that the Domain, Domain/user name, and Password fields are correct.

Alert 6208 

Cluster <cluster>: Failed to create/manage conference contacts in Active Directory; Active Directory is not configured for Windows Remote Management.

The specified cluster has attempted to create or manage Active Directory conference contacts, and failed because the Active Directory system is not configured for Windows Remote Management.

For details on enabling Windows Remote Management on your Active Directory system, refer to the Polycom Unified Communications for Microsoft Environments - Solution Deployment Guide.

Click the link to go to the Integrations > Microsoft Active Directory page.

Alert 6209 

Cluster <cluster>: Failed to create/manage conference contacts in Active Directory; Active Directory reports error: <text>.

The specified cluster has attempted to create or manage Active Directory conference contacts, and failed. The Active Directory system has reported <text> in response to the RealPresence DMA system’s request.

Use the error text to begin troubleshooting.

Click the link to go to the Integrations > Microsoft Active Directory page.

Call Server

The following alerts provide information on issues with call server functionality.

Alert 7001

Failed registration data incomplete: cluster <cluster> history limited to <n.n> hours.

Registration data retention settings are too low for the system to determine the number of failed registrations in the past 24 hours.

Click the link to go to the Admin > Server > History Retention Settings page and increase the number of registration records to retain on each cluster.

Alert 7005

Site <sitename> has no available aliases for automatic ISDN assignment.

The specified site is configured for automatic E.164 alias number assignment, but all of the aliases within the specified range are already assigned.

Click the link to go to the Service Config > Site Topology > Sites page to begin troubleshooting. Try expanding the ISDN number ranges specified in the site’s ISDN Range Assignment section.

Alert 7006

Cluster <cluster>: External SIP peer <sippeer> is unresponsive.

The specified cluster has detected that the external SIP peer named <sippeer> is not responding.

Click the link to go to the Integrations > External SIP Peers page to view the settings of the specified external SIP peer.

Call Bandwidth Management

The following alerts provide information on possible bandwidth management issues and other bandwidth management events.

Alert 7101

<N> Calls rejected starting at <time> due to lack of bandwidth on <throttlepoint-type> <throttlepoint>.

The DMA system has disallowed the specified number of calls <N> from starting, as there is not enough bandwidth to carry the calls on the site topology segment (subnet, site, or site link) with the name <throttlepoint>.

Click the link to go to the Reports > Call History page, where the first call to be rejected during this event is displayed. If possible in your environment, increase the bandwidth available to this subnet, site, or site link.

Related Topics

Machine Translation

You are cautioned that the translation of this document is generated by a machine; therefore, the translated document may have errors and be inconsistent with the original English language version of the document.

The English language version of this document shall be considered the governing document related to the Polycom product.

If there is any contradiction between the English language version of the document and the translated version of the document, the English language version of the document shall take precedence.

The translation is provided for your convenience only. Neither Google nor Polycom shall be responsible for translated content or for the performance of the translation tool. If you require further assistance on non-translation issues, please contact Polycom support.

Translated documents are not available in PDF format.