Resolving Conference Access Failure; Resolving Cascading Failure - Cisco 3500 MCU Troubleshooting Manual

Resolving Conference Access Failure

Resolving Conference Access Failure
This section describes what to do if an endpoint cannot be invited to a conference or dial into the
conference.
Possible Causes
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.

Resolving Cascading Failure

This section describes what to do if MCU conference cascading fails.
Possible Causes
The invited conference does not exist, and the
remote MCU is not in Ad Hoc (Scheduler, Web,
Control API and dial-in) mode.
Service prefixes are not unique and there is service
prefix conflict.
The remote MCU module is not registered with its
gatekeeper.
Not enough ports are available to accomplish
cascading.
Note
Services are not synchronized.
Troubleshooting Guide for Cisco Unified Videoconferencing 3500 MCU Release 5.1
1-4
Cascading requires one port from each
conference.
Chapter 1 Troubleshooting the Cisco Unified Videoconferencing 3500 MCU
Verification Steps
Check if the endpoint is authorized in the
authorization server.
Confirm that the endpoint is not busy/in a call.
Remove one of the current participants to verify
that the endpoint can join successfully.
Verification Steps
• Using the remote MCU web interface, verify
that the remote conference exists or that the
Conferences can be created using option is set
to Scheduler, Web, Control API and dial-in in
MCU > Settings > Advanced.
If ad hoc conferencing is not allowed for the
•
remote MCU, and the remote conference does
not exist, create the conference and then
cascade it (web/dial invite).
Verify that all cascaded MCU modules have
unique service prefixes.
Verify proper registration of all MCU modules
with their respective gatekeepers.
Check that the number of free ports on each EMP
used is not zero.
Verify that service definitions do not include
differences such as H.235 being enabled on one
conference only.
OL-12051-01