Table of Contents
Advertisement
Chapter 1
Troubleshooting the Cisco Unified Videoconferencing 3500 MCU
Resolving MCU Conference Initiation Failure
This section describes what to do if MCU conference initiation fails.
Possible Causes
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.
The MCU is set to prevent endpoints from creating
conferences.
There are not enough MCU resources available for
the desired conference.
The service requires one EMP video processor, but
no EMP module appears to be registered with the
MCU.
OL-12051-01
Troubleshooting Guide for Cisco Unified Videoconferencing 3500 MCU Release 5.1
Resolving MCU Conference Initiation Failure
Verification Steps
Verify that the External conference authorization
policy option is set to None in in MCU > Settings
> Advanced.
Verify that the MCU IP address is correctly
configured in the authorization server.
Verify that the Conferences can be created using
option is set to Scheduler, Web, Control API and
dial-in in MCU > Settings > Advanced.
Verify that the service you are using reserves
•
the minimum number of parties (2) and allows
expansion up to the required number of
parties.
•
Verify that current calls are not utilizing all
resources by check the available MCU
capacity and then trying to disconnect other
calls in order to find the problem.
Ping the EMP module.
•
•
Open a Telnet connection to the IP address of
the required EMP module.
•
Open a serial connection to the EMP module
if there is no response from the IP address.
Type the advanced command
•
modifyTargetDevice to ensure that the EMP is
configured to work with the correct MCU.
You can perform this operation using the serial
connection via the countdown menu visible after
rebooting the EMP.
•
Reboot the EMP after modifying the
controlling MCU.
1-3
Advertisement
Table of Contents
