Cisco Unified Videoconferencing Manager Troubleshooting Guide Release 5.0 - Troubleshooting Information for Cisco Unified Videoconferencing Manager [Cisco Unified Videoconferencing Manager]

Table Of Contents

Troubleshooting Information for Cisco Unified Videoconferencing Manager

Resolving a Port Conflict

Resolving a Scheduling Failure

Resolving a Scheduling Failure Caused by Incompatible Meeting Types

Resolving a Scheduling Failure Caused by an Incompatible MCU

Resolving a Terminal-Invitation Failure

Resolving an Incompatible Gatekeeper Registration

Resolving Unconnected MCU and Terminal Locations

Supplementary Troubleshooting Information

Resolving Meeting Creation and Meeting Invitation Issues

Troubleshooting Information for Cisco Unified Videoconferencing Manager

This chapter contains information about issues that may arise when using Cisco Unified Videoconferencing Manager. Use the troubleshooting information contained in this chapter to resolve those issues.

The Cisco Unified Videoconferencing Manager contains the following components:

•Resource Manager—The Resource Manager component of Cisco Unified Videoconferencing Manager is a simple-to-use, web-based application for managing and monitoring visual communication in multi-site organization deployments. The Resource Manager component provides scheduling, monitoring and management of Cisco Unified Videoconferencing Manager capacity, resources, and network devices for video and audio meetings.

•Network Manager—The Network Manager component of Cisco Unified Videoconferencing Manager provides a central management interface, enabling network administrators to easily and intuitively control, configure, and maintain Cisco-based collaborative communications networks. Backed by the Cisco track record for industry-leading innovation, Network Manager is the ideal choice to help you get the most out of your rich media network solutions.

•Internal Gatekeeper—The Internal Gatekeeper component of Cisco Unified Videoconferencing Manager is a simple-to-use, ITU-T H.323 version 4-compliant gatekeeper application that is essential for the management of IP telephony and multimedia communication networks.

Topics in this section include:

•Resolving a Port Conflict

•Resolving a Scheduling Failure

•Resolving a Terminal-Invitation Failure

•Supplementary Troubleshooting Information

Resolving a Port Conflict

To resolve a port conflict in the event that the port you require is in use by another application, use the following procedure.

Procedure

Step 1 In the DOS window, enter "netstat" or use a third party tool to determine which ports are currently in use.

Step 2 If port 1098 and 1099 are in use by applications other than Cisco Unified Videoconferencing Manager, then close those applications to free the ports.

Step 3 Make sure the Internal Gatekeeper/Resource Manager authorization connection is connected.

In Resource Manager, in Resource Management > Gatekeeper, the connection status should appear in the Authorization Connection column.

Resolving a Scheduling Failure

In Resource Manager, in the event of a scheduling failure, in My Meetings or All Meetings, on the Current tab, Failed appears. Click Failed to open a message that reads: "Unable to create the meeting as scheduled. Please check your meeting settings." To resolve this scheduling failure, use the procedures contained in this section.

Resolving a Scheduling Failure Caused by Incompatible Meeting Types

A scheduling failure may occur if a meeting type is downloaded, and then the meeting type is changed on the MCU but the Resource Manager does not update the meeting types.

Procedure

Step 1 To confirm that the reason for the failure is an incompatible meeting type, in the Admin > Meeting Types section, click Download.

Step 2 If the meeting type that you specified appears in the Meeting Types (Service) Conflicts list, the reason for the scheduling failure is, at least in part, an incompatible meeting type.

Note If a meeting is created even though the specified meeting type is incompatible, there may be resource-calculation errors.

Step 3 To resolve the conflict, repeat the download of the meeting type you require.

Resolving a Scheduling Failure Caused by an Incompatible MCU

If you determine that a meeting-scheduling failure is not caused by a meeting-type conflict, the reason for the failure may be an incompatible MCU. If actual MCU resources are changed after an MCU is added in Resource Manager but Resource Manager does not update or synchronize the actual MCU information, then the result may be an incompatible MCU.

Procedure

Step 1 To determine which MCU is actually assigned to the meeting, select Admin > All Meetings, and then on the Current tab, in the MCU column, check the list of MCUs.

Step 2 Click an MCU in the list.

Step 3 In the Modify MCU screen, click Update. The MCU profile is updated.

Note The Update button only appears if the MCU is online.

Step 4 Make sure the MCU gateway is configured correctly.

Step 5 Make sure the connection configuration in Admin > Network Management > IP Topology is correct.

Resolving a Terminal-Invitation Failure

If you are not able to invite a terminal to a meeting, one of the following reasons may be the cause of the failure:

•Incompatible gatekeeper registration—See "Resolving an Incompatible Gatekeeper Registration" section

•Unconnected location for an MCU and a terminal—See "Resolving Unconnected MCU and Terminal Locations" section

Resolving an Incompatible Gatekeeper Registration

The MCU may be registered to a gatekeeper that is different than the one specified in the MCU profile in Resource Manager.

Procedure

Step 1 In the Cisco Unified Videoconferencing 3545 MCU application interface, on the Protocols tab, make sure that the gatekeeper listed there is the same as the one configured in Resource Manager.

Step 2 If the gatekeeper is not the same, then in Resource Manager, select the same gatekeeper to which the MCU is registered.

Resolving Unconnected MCU and Terminal Locations

If a meeting is set up on an MCU that belongs to a specific location, and then a terminal is invited to a different location, the location to which the MCU is assigned may not be able to connect to the location to which the terminal is assigned.

Procedure

Step 1 In Resource Manager, on the IP Topology tab, check that there is a link between the two different locations.

Step 2 Make sure that if there is a connection, that Bandwidth and Location are correctly defined.

Step 3 Alternatively, assign the MCU and the terminal to the same location.

Step 4 Make sure that the gatekeeper that the terminal is assigned to is in Authorization Mode since the cascading mechanism is on the local MCU and cannot be changed.

Note Cascading between MCUs is an important function in Resource Manager. Network configuration for better cascading management is set up in Resource Manager in the Network Management section, on the IP Topology tab. If the IP Topology tab is hidden, in the Resource Manager Configuration Tool, in System Configuration > UI Settings, check IP Topology to activate the IP Topology tab.

Supplementary Troubleshooting Information

The procedures in this section are intended for use when the troubleshooting procedures suggested previously in this guide do not resolve an issue.

Resolving Meeting Creation and Meeting Invitation Issues

If previously suggested troubleshooting procedures in this guide do not resolve a meeting creation or meeting invitation issue, use the following procedure.

Procedure

Step 1 On the MCU, without using the Resource Manager, create the same meeting or invitation that caused an issue to occur

Step 2 If the meeting creation or invitation does not succeed, restart the MCU.

Step 3 If restarting the MCU does not resolve the issue, contact your MCU service representative.

	Cisco Unified Videoconferencing Manager Troubleshooting Guide Release 5.0
	Troubleshooting Information for Cisco Unified Videoconferencing Manager
Cisco Unified Videoconferencing Manager Troubleshooting Guide Release 5.0 Preface Troubleshooting Information for Cisco Unified Videoconferencing Manager Index	Download this chapter Troubleshooting Information for Cisco Unified Videoconferencing Manager Download the complete book PDF of the entire book (PDF - 510 KB) Table Of Contents Troubleshooting Information for Cisco Unified Videoconferencing Manager Resolving a Port Conflict Resolving a Scheduling Failure Resolving a Scheduling Failure Caused by Incompatible Meeting Types Resolving a Scheduling Failure Caused by an Incompatible MCU Resolving a Terminal-Invitation Failure Resolving an Incompatible Gatekeeper Registration Resolving Unconnected MCU and Terminal Locations Supplementary Troubleshooting Information Resolving Meeting Creation and Meeting Invitation Issues Troubleshooting Information for Cisco Unified Videoconferencing Manager This chapter contains information about issues that may arise when using Cisco Unified Videoconferencing Manager. Use the troubleshooting information contained in this chapter to resolve those issues. The Cisco Unified Videoconferencing Manager contains the following components: •Resource Manager—The Resource Manager component of Cisco Unified Videoconferencing Manager is a simple-to-use, web-based application for managing and monitoring visual communication in multi-site organization deployments. The Resource Manager component provides scheduling, monitoring and management of Cisco Unified Videoconferencing Manager capacity, resources, and network devices for video and audio meetings. •Network Manager—The Network Manager component of Cisco Unified Videoconferencing Manager provides a central management interface, enabling network administrators to easily and intuitively control, configure, and maintain Cisco-based collaborative communications networks. Backed by the Cisco track record for industry-leading innovation, Network Manager is the ideal choice to help you get the most out of your rich media network solutions. •Internal Gatekeeper—The Internal Gatekeeper component of Cisco Unified Videoconferencing Manager is a simple-to-use, ITU-T H.323 version 4-compliant gatekeeper application that is essential for the management of IP telephony and multimedia communication networks. Topics in this section include: •Resolving a Port Conflict •Resolving a Scheduling Failure •Resolving a Terminal-Invitation Failure •Supplementary Troubleshooting Information Resolving a Port Conflict To resolve a port conflict in the event that the port you require is in use by another application, use the following procedure. Procedure Step 1 In the DOS window, enter "netstat" or use a third party tool to determine which ports are currently in use. Step 2 If port 1098 and 1099 are in use by applications other than Cisco Unified Videoconferencing Manager, then close those applications to free the ports. Step 3 Make sure the Internal Gatekeeper/Resource Manager authorization connection is connected. In Resource Manager, in Resource Management > Gatekeeper, the connection status should appear in the Authorization Connection column. Resolving a Scheduling Failure In Resource Manager, in the event of a scheduling failure, in My Meetings or All Meetings, on the Current tab, Failed appears. Click Failed to open a message that reads: "Unable to create the meeting as scheduled. Please check your meeting settings." To resolve this scheduling failure, use the procedures contained in this section. Resolving a Scheduling Failure Caused by Incompatible Meeting Types A scheduling failure may occur if a meeting type is downloaded, and then the meeting type is changed on the MCU but the Resource Manager does not update the meeting types. Procedure Step 1 To confirm that the reason for the failure is an incompatible meeting type, in the Admin > Meeting Types section, click Download. Step 2 If the meeting type that you specified appears in the Meeting Types (Service) Conflicts list, the reason for the scheduling failure is, at least in part, an incompatible meeting type. Note If a meeting is created even though the specified meeting type is incompatible, there may be resource-calculation errors. Step 3 To resolve the conflict, repeat the download of the meeting type you require. Resolving a Scheduling Failure Caused by an Incompatible MCU If you determine that a meeting-scheduling failure is not caused by a meeting-type conflict, the reason for the failure may be an incompatible MCU. If actual MCU resources are changed after an MCU is added in Resource Manager but Resource Manager does not update or synchronize the actual MCU information, then the result may be an incompatible MCU. Procedure Step 1 To determine which MCU is actually assigned to the meeting, select Admin > All Meetings, and then on the Current tab, in the MCU column, check the list of MCUs. Step 2 Click an MCU in the list. Step 3 In the Modify MCU screen, click Update. The MCU profile is updated. Note The Update button only appears if the MCU is online. Step 4 Make sure the MCU gateway is configured correctly. Step 5 Make sure the connection configuration in Admin > Network Management > IP Topology is correct. Resolving a Terminal-Invitation Failure If you are not able to invite a terminal to a meeting, one of the following reasons may be the cause of the failure: •Incompatible gatekeeper registration—See "Resolving an Incompatible Gatekeeper Registration" section •Unconnected location for an MCU and a terminal—See "Resolving Unconnected MCU and Terminal Locations" section Resolving an Incompatible Gatekeeper Registration The MCU may be registered to a gatekeeper that is different than the one specified in the MCU profile in Resource Manager. Procedure Step 1 In the Cisco Unified Videoconferencing 3545 MCU application interface, on the Protocols tab, make sure that the gatekeeper listed there is the same as the one configured in Resource Manager. Step 2 If the gatekeeper is not the same, then in Resource Manager, select the same gatekeeper to which the MCU is registered. Resolving Unconnected MCU and Terminal Locations If a meeting is set up on an MCU that belongs to a specific location, and then a terminal is invited to a different location, the location to which the MCU is assigned may not be able to connect to the location to which the terminal is assigned. Procedure Step 1 In Resource Manager, on the IP Topology tab, check that there is a link between the two different locations. Step 2 Make sure that if there is a connection, that Bandwidth and Location are correctly defined. Step 3 Alternatively, assign the MCU and the terminal to the same location. Step 4 Make sure that the gatekeeper that the terminal is assigned to is in Authorization Mode since the cascading mechanism is on the local MCU and cannot be changed. Note Cascading between MCUs is an important function in Resource Manager. Network configuration for better cascading management is set up in Resource Manager in the Network Management section, on the IP Topology tab. If the IP Topology tab is hidden, in the Resource Manager Configuration Tool, in System Configuration > UI Settings, check IP Topology to activate the IP Topology tab. Supplementary Troubleshooting Information The procedures in this section are intended for use when the troubleshooting procedures suggested previously in this guide do not resolve an issue. Resolving Meeting Creation and Meeting Invitation Issues If previously suggested troubleshooting procedures in this guide do not resolve a meeting creation or meeting invitation issue, use the following procedure. Procedure Step 1 On the MCU, without using the Resource Manager, create the same meeting or invitation that caused an issue to occur Step 2 If the meeting creation or invitation does not succeed, restart the MCU. Step 3 If restarting the MCU does not resolve the issue, contact your MCU service representative.
	© 1992-2009 Cisco Systems, Inc. All rights reserved. Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks of Cisco Systems, Inc.