Specifications

Troubleshooting the SCOPIA Elite MCU | 61
RADVISION | Administrator Guide for SCOPIA Elite 5100 Series MCU Version 7.7
Solution If the problem is caused by the ECS rejecting all calls, verify that the Accept calls option is
checked in ECS > Settings > Calls.
Solution If the MCU is set to work with an authorization server and no authorization server is configured,
perform these steps: verify that the External conference authorization policy option is set to None
in Maintenance > Advanced parameters > External conference policy authorization.
1. Access the MCU Administrator interface.
2. Select the Maintenance options button , and then select Advanced parameters.
The Advanced parameters window is displayed.
3. Locate the Allows/Disallows external authorization servers to connect parameter.
4. Select the Review button .
This parameter section is displayed.
Solution If the MCU is set to work with an authorization server, but the authorization server is not
configured properly, verify that the MCU IP address is correctly configured in the authorization
server.
Solution If there are endpoint-related interoperability issues, perform this procedure:
Procedure
Step 1 Verify the MCU and the endpoint are registered properly:
• For SIP endpoints, verify that both the MCU and the SIP endpoint are properly registered
with the SIP proxy.
• For H.323 endpoints, verify that both the MCU and the H.323 endpoint are properly
registered with the ECS.
• For 3G endpoints, verify that both the MCU and the 3G endpoint are properly registered with
the SIP proxy and/or ECS.
Step 2 If the registration is correct, collect logs and wireshark traces and send them to RADVISION
Customer Support.
Solution If the initiating LAN endpoint is not registered with the ECS, verify that the initiating endpoint
appears in the ECS Endpoints table correctly.
Solution If the MCU service is not defined in the ECS Services table, perform these steps:
1. Verify that the service is defined in the MCU.
2. Verify that the MCU service prefix appears in the ECS Services table. If it does not, add it
manually.
3. Verify that the service prefix is not a subset of another service prefix.
Solution There are not enough MCU resources available, verify that current calls are not utilizing all
resources by checking the available MCU capacity and then trying to disconnect other calls in
order to find the problem.