Specifications

Troubleshooting the SCOPIA Elite MCU | 60
RADVISION | Administrator Guide for SCOPIA Elite 5100 Series MCU Version 7.7
Resolving MCU Failure to Register with the Gatekeeper
Problem The SCOPIA Elite MCU fails to register with the gatekeeper.
Possible Causes
The gatekeeper address is set incorrectly.
There is a TCP/IP setup issue.
There is a LAN or cable issue.
The ECS is in the Predefined mode.
Solution If the gatekeeper IP address is incorrect, verify the gatekeeper IP address and reconfigure the
gatekeeper IP address on the MCU.
Solution If the problem is caused by a TCP/IP setup issue, perform these steps:
Verify that the MCU is assigned a unique IP address.
Verify that the subnet mask and default gateway subnet mask are set correctly.
Attempt to the ping the MCU from the gatekeeper to verify whether the MCU is reachable.
Ensure the IP address assigned to the MCU is unique and not duplicated anywhere on the
network.
Solution If the problem is caused by a LAN or cable issue, perform these steps:
Verify the switch port settings.
Verify that the Ethernet cable is straight through.
Try another Ethernet cable.
Verify if the Link and Activity LEDs on the switch port are lit.
Solution If the ECS is in the Predefined mode, verify that the MCU is predefined on the ECS.
Resolving MCU Conference Initiation Failure
Problem Users cannot create new conferences.
Possible Causes
In ad hoc conferences, the ECS is set to reject all calls.
The MCU is set to work with an external authorization server, but no authorization server is
configured.
The MCU is set to work with an external authorization server, but the authorization server is
not configured properly to work with the MCU.
There are endpoint-related interoperability issues
There are not enough MCU resources available for the desired conference.