Cisco 3500 MCU - Resolving Quality Issues in Cascaded Conferences; Resolving Endpoint Disconnection Issues; Resolving Unexpected Conference Termination

1-5
Troubleshooting Guide for Cisco Unified Videoconferencing 3500 MCU Release 5.1
OL-12051-01
Chapter 1 Troubleshooting the Cisco Unified Videoconferencing 3500 MCU
Resolving Quality Issues in Cascaded Conferences
Resolving Quality Issues in Cascaded Conferences
This section describes what to do if a cascaded conference suffers long delays or bad lip synchronization.
Resolving Endpoint Disconnection Issues
This section describes what to do if endpoints unexpectedly drop out of the MCU conference.
Resolving Unexpected Conference Termination
This section describes what to do if a conference on the MCU unexpectedly terminates.
Possible Causes Verification Steps
Unsuitable topology used (for example, chain
topology used unnecessarily).
• One single central MCU should invite all
other cascaded MCUs.
• We recommend that you do not have more
than one level of cascaded MCUs.
• Use a star topology, where the central MCU is
in the center of the star, and other cascaded
MCU modules are on the arms of the star.
Possible Causes Verification Steps
Unreliable network link. Check network link quality (round trip time
should be less than 300 msec).
Possible Causes Verification Steps
The Ad hoc conferences terminate when option in
MCU > Settings > Advanced is set to Conference
creator leaves and the conference creator has left
the conference.
Set the Ad hoc conferences terminate when option
in MCU > Settings > Advanced to Last participant
leaves.
Unreliable network link between the MCU and the
gatekeeper.
Check network link quality (round trip time
should be less than 300 msec).