Configuration Guide for Cisco Unified MeetingPlace Release 8.6
Troubleshooting Topology Management Issues
Downloads: This chapterpdf (PDF - 92.0 KB) | Feedback

Table of Contents

Troubleshooting Topology Management Issues for Cisco Unified MeetingPlace

Meeting Started from Cisco WebEx Indicates a Failure to Connect to the Telephony Bridge

Unable to Start a Personal Meeting from the Telephone User Interface (TUI)

Meeting is not Started at the Expected Location

Unable to Join Existing Meetings Using the TUI

Users with the First Name “tempUser” are in Your User Profiles

Nodes in the System Default Site are Oversubscribed

Some Conference Participants are Unable to Join a Meeting

Only One Meeting is Started on the System at Any Time

Primary Meeting Director Node Must be Replaced

Secondary Meeting Director Node Must be Replaced

Configuring an Exclusive Site

Configure a Site to Host Large Meetings

DNS is Not Configured in CUCM

Troubleshooting Topology Management Issues for Cisco Unified MeetingPlace

This module explains how to troubleshoot problems that can occur when configuring and maintaining your topology.

Meeting Started from Cisco WebEx Indicates a Failure to Connect to the Telephony Bridge

Problem It is not possible to outdial from the meeting room.

Possible Cause There are no licenses installed on the system and there is already one meeting in progress.

Recommended Action Install licenses on your Meeting Director nodes.

Recommended Action End the meeting in progress and restart it.

Possible Cause Both the primary and secondary TSP connections from Cisco WebEx to Cisco Unified MeetingPlace are disconnected.

Possible Cause There are no active conferencing nodes in the system that can host the meeting.

Recommended Action Ensure that your conferencing nodes are not in maintenance mode or otherwise inactive.

Related Topics

Unable to Start a Personal Meeting from the Telephone User Interface (TUI)

Problem It is not possible to start a personal meeting.

Possible Cause There are no licenses installed on the system and there is already one meeting in progress.

Recommended Action Install licenses on your Meeting Director nodes.

Recommended Action End the meeting in progress and attempt to restart your personal meeting.

Possible Cause There is no active Meeting Director node in the system.

Recommended Action Ensure that the Primary and Secondary Meeting Director nodes are not in maintenance mode or otherwise inactive.

Possible Cause It is not possible to refer the caller who is starting the meeting to the node that will host the meeting.

Recommended Action Ensure that the Cisco Unified Communications Manager (CUCM) configuration allows transfer of callers to each node in the system.

Meeting is not Started at the Expected Location

Problem Your meeting is started on a node in a site other than the user’s host site.

Possible Cause There is not enough capacity available on the host site.

Recommended Action Ensure that there are conferencing nodes configured in the host site.

Recommended Action If site capacity is often exceeded add additional conferencing nodes to your system.

Recommended Action Check for inactive nodes in your site. If there are inactive nodes, make them operational as soon as possible.

Possible Cause The association of the user with the site is not properly configured.

Recommended Action If you are using time zone as an association mechanism ensure that the time zone association is correct.

Recommended Action If you are using the Preferred Site as an association mechanism ensure that the Preferred Site has active nodes configured.

Related Topics

Unable to Join Existing Meetings Using the TUI

Problem A meeting is in progress on a remote node but it is not possible for users to join that meeting from a given location. The CUCM configuration has not been set so that the caller can be referred to the host node for the meeting.

Solution Ensure that the configuration at the CUCM associated with the given location has been configured successfully to refer callers to the host node of the meeting.

Users with the First Name “tempUser” are in Your User Profiles

Problem Users with the first name “tempUser” are present in your user profiles. These users have not been successfully synchronized to Cisco Unified MeetingPlace before the user started a meeting.

Solution Ensure that the user profiles are successfully synchronized to Cisco Unified MeetingPlace by resetting the PIN or issuing a manual sync operation from the Cisco WebEx personal conferencing page.

Related Topics

Nodes in the System Default Site are Oversubscribed

Problem The nodes in the System Default Site are oversubscribed.

Possible Cause There is not enough capacity available on the System Default Site to handle all unassociated users.

Recommended Action Ensure that whenever possible users are associated with another appropriate site using either time zone or Preferred Site association.

Recommended Action Add more capacity to the System Default Site.

Related Topics

Some Conference Participants are Unable to Join a Meeting

Problem Some participants fail to join a conference.

Possible Cause The maximum meeting size of the site that is hosting the meeting has been reached.

Recommended Action Increase the maximum meeting size of the site.

Possible Cause The node has reached its maximum capacity and cannot support additional users.

Recommended Action Cancel other meetings on the node to provide more capacity.

Recommended Action Add more capacity to the site to reduce the chances of reaching maximum capacity on a node.

Related Topics

Only One Meeting is Started on the System at Any Time

Problem It is not possible to start more than one meeting on the system because there are no licenses installed on the active Meeting Director node.

Solution Ensure that there are licenses installed on both the Primary and Secondary Meeting Director nodes.

Related Topics

Primary Meeting Director Node Must be Replaced

Problem Primary Meeting Director node has failed and must be replaced.

Recommended Action Move the Primary Meeting Director node to another node in the system:

Recommended Action Remove the Primary Meeting Director node and the Secondary Meeting Director node becomes the Primary Meeting Director node.


 

Related Topics

Secondary Meeting Director Node Must be Replaced

Problem Your Secondary Meeting Director node has failed and must be replaced.

Recommended Action Configure another node in your system as the Secondary Meeting Director node.

Recommended Action Remove the Secondary Meeting Director node and add a new node to your system that will automatically be configured as the Secondary Meeting Director node.

Related Topics

Configuring an Exclusive Site

Problem Configure a site so that it only hosts meetings for users who have been associated with the site.

Solution Configure a site to never allow overflow from other sites in the system.


Step 1 Sign in to the Administration Center on your Primary Meeting Director node.

Step 2 Select Topology Management > Sites.

Step 3 Select the Edit link for the selected site.

Step 4 Set Allow overflow meetings from other sites to No.

Step 5 Select Save.


 

Related Topics

Configure a Site to Host Large Meetings

Problem Your current configuration does not have the capacity to host large meetings.

Solution Configure your site to provide extra system capacity so that it can support large meetings.


Step 1 Sign in to the Administration Center on your Primary Meeting Director node.

Step 2 Select Topology Management > Sites.

Step 3 Select the Edit link for the selected site.

Step 4 Set Allow overflow meetings from other sites to No.

Step 5 Set the Average meeting size to a value representing the number of participants in a large meeting.

In general, the number of meetings that can be started on a node in one site at any time will be restricted to node capacity and average meeting size.

Step 6 Select Save.

Step 7 Ensure that a minimal set of users are associated with the site so that the number of meetings being started is restricted.


 

Related Topics

DNS is Not Configured in CUCM

Problem CUCM was configured on your Cisco Unified MeetingPlace nodes without configuring DNS. CUCM must be able to resolve by DNS the hostnames of the MeetingPlace Nodes. If CUCM is unable to DNS resolve the MeetingPlace Nodes during the REFER process, the REFER process will fail.

Solution Configure DNS using the following procedure.


Step 1 Login to the command line using the operating system administrator account.

Step 2 Enter the following:

set network dns primary x.x.x.x

and optionally

set network dns secondary y.y.y.y

Step 3 Enter the following:

Utils system restart