Table of Contents
Advertisement
Resolving MCU Failure to Register with the Gatekeeper
Resolving MCU Failure to Register with the Gatekeeper
This section describes what to do if the MCU fails to register with the Cisco IOS H.323 Gatekeeper.
Possible Causes
The gatekeeper address is set incorrectly.
TCP/IP setup issue.
LAN or cable problem
The MCU cannot register to a Cisco MCM. The
Cisco MCM may not understand the syntax of the
label "MCU".
Resolving Front Panel LED Issues
This section describes what to do if MCU module front panel LEDs are off at all times, including during
the power off, power on cycle.
Possible Causes
Power supply problem
The MCU module is not inserted correctly in the
Cisco Unified Videoconferencing 3545 chassis, or
a back plane pin is bent.
Troubleshooting Guide for Cisco Unified Videoconferencing 3500 MCU Release 5.1
1-2
Chapter 1
Troubleshooting the Cisco Unified Videoconferencing 3500 MCU
Verification Steps
Verify the Gatekeeper IP address settings.
•
Verify that the MCU is assigned a unique IP
address.
•
Verify that the subnet mask and default
gateway subnet mask are set correctly.
•
Verify the switch port settings.
•
Verify that the Ethernet cable is straight
through.
•
Try another Ethernet cable.
Change the registration name of the MCU to
"GW" in the MCU Advanced Commands window.
Verification Steps
Make sure that the power supply LED is
•
green.
•
Check the AC cable and fuse.
Open the telecom latch screws and extract the
•
MCU module from its slot.
Verify that there are no bent pins on the back
•
plane (using a flashlight, if necessary).
•
Re-insert the MCU module carefully closing
the latches.
OL-12051-01
Advertisement
Table of Contents
