Filter
Top Products
System Management and Maintenance
Polycom, Inc. 369
Alert 4001
MCU <MCUname> is currently busied out.
Someone busied out the specified MCU.
Click the link to go to the Network > MCU > MCUs page.
See also:
Alerts
Alert 4002
MCU <MCUname> is currently out of service.
Someone took the specified MCU out of service.
Click the link to go to the Network > MCU > MCUs page.
See also:
Alerts
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 Network > MCU > MCUs page for more information.
See also:
Alerts
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 doesn’t 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 Network > MCU > MCUs page.