Polycom 7000 User Manual
System Management and Maintenance
Polycom, Inc.
372
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.
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 Network > MCU > MCUs page.
See also:
Alert 4016
MCU <mcu> has been automatically busied out due to <N> consecutive failures to start
conferences. Investigate the MCU state and logs.
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.
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
to the Out of Service state. Once that happens, this alert is replaced with
.
Click the link to go to the Network > MCU > MCUs page.
See also:
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.
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.
it failed to start <N> number of conferences in a row. This condition is likely caused by an MCU software
issue.
This alert replaces
.
Click the link to go to the Network > MCU > MCUs page.
See also:
Endpoints
The following alerts provide information on communication issues with endpoints.