Specifications

Troubleshooting the SCOPIA Elite MCU | 62
RADVISION | Administrator Guide for SCOPIA Elite 5100 Series MCU Version 7.7
Resolving Conference Access Failure
Problem An endpoint cannot be invited to a conference or dial into the conference.
Possible Causes
• The ECS is set to reject all calls.
• The endpoint is not registered with the ECS.
• The MCU is configured to work with an authorization server, but the endpoint is not
authorized and therefore the authorization server rejects the call.
• The endpoint is currently in a call.
• There are not enough MCU resources available for the desired conference.
Solution If the ECS is set to reject all calls, verify that the Accept calls option is checked in ECS > Settings
> Calls.
Solution If the endpoint is not registered with the ECS, verify that the invited/dialing endpoint appears in
the ECS table of registered endpoints. Also verify that the endpoint is online.
Solution If the MCU is configured to work with an authorization server, verify that the endpoint is
authorized in the authorization server.
Solution If the endpoint is currently in a call, confirm that the endpoint is not busy/in a call.
Solution If there not enough MCU resources, remove one of the current participants to verify that the
endpoint can join successfully. Then verify whether cascading is enabled and if the meeting is
scheduled for cascading.
Resolving Quality Issues in Cascaded Conferences
Problem A cascaded conference suffers long delays or bad lip synchronization.
Possible Causes The topology used for the conference is not suitable; for example, a chain topology is used
unnecessarily.
Solution 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.